If the drive is in the boot device list the system will interrogate it at boot time. If the disk has what looks like a bootstrap loader on the boot sector then the system will try to boot from it.
However if the loader is corrupt or the disk is only partially configured as bootable or infected with malware then the boot will very likely fail, causing the system to hang.
RE: Jock
That is correct, furthermore if the cmos is set up to boot from the drive in question it most likely will lock up if it does not find the boot information on the drive. Check and or adjust the c-moss first. That will most likely fix the problem.
Regards
First of all the disk is a storage disk and works just fine with an alternate system disk on the same machine, with the same configuration.
Probably I can run chkdsk on it in the alternate configuration now, in the original config. the disk is seen as RAW, chkdsk does not run on RAW disks
It is visible in the BIOS, should have mentioned on a Promise 133 controller card, but the same on the alt. system disk w/ same O/S.
No cabling / jumper issues anticipated
Boot Sector issues ??? must be specific to single O/S installation and not the other. BTW, the disk partition was not formatted as a primary partition.
CMOS issues, ??? not expecting that either
BTW where does one find "Boot device Listing" in Win ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.