Discussion Locked

contoller error on\Device\Harddisk\DR0

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

--------------------------------------------------------------------------------
Running a dual boot (WinMe and Advanced Server) on a P3 800 with 128 megs of Ram and 1 20gig HD partioned into two 10 gig drives. ME is under FAT32 and Adv is on NTFS. Machine is used mostly as a domain controller on a very small network. Error keeps popping up in Event viewer and ive noticed machine is running very slow. I also have a strange situation with HD set up. HD is a master on the same ribbon as CD drive (slave. I cannot boot the machine if the HD is plugged into first slot on ribbon. If i plug the master into the second slot and CD into first it boots even tho CD is first on ribbon and slave drive. I know that this is causing error in Event Viewer but when i try to change the drives to correct order on ribbon wont boot. Bios settings are squared away.....what in the heck am i missing?!?!?!?

6 replies

by jesselou

examine the jumpers of your hd and adjust exactly the default settings of the manufacturer of your hd.reconnect your data cable into your first ide controller ensuring that the red stripe of your data cable will be placed on the first pin on your controller then connect to the hd with the pin near to your hd power connector.reconnect your power connector the restart your machine go to your bios first and reconfigure your hard disk there select auto detect then save and exit.

by william jay

If it is a 40 pin IDE ribbon cable, then it should make no difference which drive is at the end. That is for floppy drive ribbons, which have a twist between drive connections.
If it is an 80 pin IDE cable, then it gets more detailed.
As alreadymentioned, get the jumpers in place. Some drives require two or more jumpers set to use features properly, (ie: a master and a master w/slave), to let the drive controller to identify which commands to latch and which to ignore. Each IDE device identifies itself to the motherboard long before windos gets it, so check the startup screen carefully to see that all is as expected. **Put one line, pause, in autoexec.bat to make the time.

Once the hardware checks out, then start windows one at a time to see what else may need fixin' in either or both ...

Dual boot can be complicated by a few factors, things done at installation and afterwards, so be patient and thorough, and keep us posted, it'll get straightened out ...

by william jay

Please include details about Event Viewer Messages as fresh eyes may see a different cause or remember better when shown ...

This discussion is closed to new replies.