Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
MB able to Detect HD only as slave
Name: rezanur Date: February 18, 2005 at 01:44:28 Pacific OS: Win98SE DOS & WinXP CPU/Ram: Intel 2.4 GHz
Comment:
A working Master Samsung 80GB Hard disk running WinXP was installed as a slave in another computer for data transfer. The HD was wrongly jumpered to limit to 32GB size. No data was written to it or was visible during this period. Active@ Partition Recovery software was used to successfully recover all files as no data was avaiable even after correcting the jumper setting. Now the original computer refuses to boot even with a Win98SE DOS floppy boot disk. If the hard disk is removed the system boots okay with the same floppy. The BIOS is able to detect it only as a SLAVE but not Master on either of the 2 IDE cables, even by itself. It works happily as a slave using WinXP on the second computer. But even the second computer will not boot with a WIN98SE boot floppy if this HD is in place. So unable to run Fdisk. Both computers use INTEL D865 PERL Motherboard Please help.
Name: j1mbo Date: February 18, 2005 at 02:19:47 Pacific
Reply:
Try clearing your CMOS back to defaults in the original machine, and recheck those jumper settings are on master - try CS/cable select too.
You could try starting a recovery console from your windows XP Cd (see here), if it will boot from CD. Then rebuild the MBR from there (fixboot or fixmbr i >think<).
Summary: There is no jumper on the back that limits the HDD, only a jumper that determines whether it is a slave or master. I tried the method of formatting the 120gig hdd from disk management, but no luck. it...
Summary: Hi, maybe someone can help me with this problem. I was trying to fix a computer. I did the usual troubleshooting; checking and making sure everything is intact. So, when I unplug the IDE cable from th...
Summary: "1. What exactly does the error message mean?" I don't know. It may be generated by the bios, not the drive. In that case it's probably specific to the bios brand and the brand's overall bios software...