Kirk, I did the following. I ran fdisk with /dev/hda, which is my boot drive, and got what you said I should get. Then, I loaded a zipdisk into hdb, and ran fdisk on it with the same result. Then I loaded a CD into hdc which is my cd-rom drive, and got the same thing with the message that I couldn't rewrite partitions on this drive which is what I was expecting. Then I loaded a CD into hdd, my cd-writer, and got the same messages as with hdc. This only leaves hde, which linux isn't seeing. I ran fdisk /dev/hde, and it said it couldn't open the drive which I was expecting. ----- Original Message ----- From: Kirk Wood <cpt.kirk@xxxxxxxxx> To: <speakup at braille.uwo.ca> Sent: Sunday, December 31, 2000 8:26 AM Subject: Re: a ton of questions > Gregory, > > Try running this as an experiment: > fdisk /dev/hdc > The ideal is that you recieve a message "Command (m for help):" If you get > this, then you are able to speak to the drive. This has been the defining > method for me though there may be other/better ways. If you get this far > you can enter "p" and it will list the partitions it sees. > > I would say to keep in mind there could be many other reasons beside > hardware for your not being able to "see" the drive. In fact, that is the > last guess. The ATA66 specification and all others SHOULD fall back to the > older specifications when need be. In fact, when you first boot in Windows > it is using the bios to read the drive. If you can boot to DOS mode and > see your drive it is very unlikely that the hardware is the problem. More > likely is that somewhere you have software translation on the drive. > > ======= > Kirk Wood > Cpt.Kirk at 1tree.net > > Cluelessness > There are no stupid questions, but there are a lot of > inquisitive idiots > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
