did you connect both drives to the one ide cable? If so they are probably both master on the one cable and it is even money which the bios/os will find and won't find. If the second drive is on the second cable with the cdrom; then again you probably have the cdrom as master (hdc you did say) and the maxtor as master as well. Change t he cdrom to slave. this is often done by moving the jumper as follows: With the ide connector of the cdrom facing you working from right to left you have: 4-pin power connector, 40-pin ide connector master/slave jumpers mode jumpers red-book audio conector 4-pin. The master/slave jumper usually has 6 pins or mone in a row of 2 excuse the poor ascii art but like this: *** *** The jumper closes 2 pins and sits straight up and down. settings are given from the *right* right-most pins: drive is slave. middle pins: drive is master Left hand set of pins: drive is set to cable select. In summary from the right: master, slave cable select. This is often written on the drive as MA SL CS from the right or CS SL MA fromt heleft above or below the jumper block. Put the cdrom as slave and connect the maxtor as master to the secondary controller. Hope t hishelps. Regards, Kerry. On Fri, Jan 18, 2002 at 03:16:22PM -0500, Charles Hallenbeck wrote: > I hope someone may have an explanation or a suggestion for this > one: > > My friend has a Gateway machine with Windows 98 on a 12 GB disk > which works fine. She wants to move on up to Linux, and purchased > a second HD, a Maxtor 40 GB disk. She knows even less about > hardware than I do, and together we proceeded to just put the > disk in the machine and cable it up, without even looking at its > jumpers. > > The machine now still boots fine into Windows, and Windows can > see the second drive okay. However, Linux cannot see either the > old drive or the new one. She is going to install Slackware 8.0 > on her second disk, but when the installation boot disk and root > disk are run, and we have the login invitation as root, neither > fdisk nor cfdisk can 'open' any of the four HD devices, not even > /dev/hda. > > Reviewing the boot messages for the ramdisk installation system, > there is no mention of any HD either. It does find her CD drive > on /dev/hdc, but no other /dev/hdx devices are found. > > Anybody have any idea where to look for this problem? > > Thanks - Chuck > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>* > Visit me at http://www.mhonline.net/~chuckh > The Moon is Waxing Crescent (24% of Full) > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Kerry Hoath: kerry at gotss.net kerry at gotss.eu.org or kerry at gotss.spice.net.au
