Disk I/O Error

[Mastergunz]

I am having a slight problem. I have a Seagate ST3144A Hard drive that was formatted and loaded with W/95 on a bench system but when I put it back into the original system (Tandy MMPC 10, I know ha-ha-ha) I get a Disk I/O error. I have run the BIOS setup and made sure that the BIOS is setup correctly. The floopy boots just fine and when I put the hard drive back into the bench system it boots just fine. The hard drive worked fine yesterday in the Tandy system. I checked the master/slave jumpers and double checked the IDE cable. Any ideas?

 

[Snickle]

Could be the Tandy is finally dying. Did you try a different drive in the Tandy?

 

[edfair]

No explanations but an observation. I've seen the problem on multiple machines where drives from one machine won't work on another. In almost every case I've been able to use the drive after doing fdisk to remove partitions, then fdisk again to add partitions and format on the target machine. I've also seen the issue on Unix boxes where I've moved drives.
It appears to be some sort of drive timing issue built into the OS, but I've never bothered to try any further troubleshooting.
And I've never had the problem with DOS. Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[Mastergunz]

I researched this with some of my collegues and we discovered that the problem I had may be much of the same problems in many of the threads that I have read.
When you run fdisk and you hit "enter" at, or answer YES(Y) at the extended partition prompt, the default FAT is FAT32. If you answer NO(N) to the same option, the default FAT is FAT16.
Older machines with older BIOS may or may not recognise FAT32 partitions. You can do one of two things, revert to FAT16 or update your BIOS to enable your system to recognise FAT32 partitions. Since I had to run fdisk and load the drive on a bench system I had completly forgotten about the age of the system that the drive was being installed into. So, I had to put the drive back on the bench and re-fdisk using FAT16.
The system BIOS in the old PC I was working on could not be updated so I after I reverted to FAT16, everything was fine.