If you have installed WinXP on the second HD while having another installed WinXP on the first one - or if you even just booted with two visible WinXP installations, you _may_ have created a dependancy of the new installation towards the old one. For example WinXP tries to be "clever" and detects existing system partitions to use data like swapfile/area from there. Even if the bootup on Disk B now works - disconnecting disk A may then result in problems.
Quote:
Originally Posted by G.K Zhukov
Disk B got 3 partitions.
Two primarys, one at 95GB and one at 7.2MB (the last one was clearly a mistake), and one logical of 95GB.
|
It is crucial to have exact data to try remote diagnosing harddisk/bootup problems. Your problem could be that the MBR of disk B simply doesnt contain a valid loader even though the error message you mentioned says something different.
Use a decent tool to collect all information about your hard disk controller and partitioning info and post it here. PartitionMagic had one or you could try this:
http://www.autem.de/download/devinfo.exe which needs to be run from a dos bootdisk. They may not help in case you have the MBR loader problem though.