

Norton Ghost was mentioned and from personal experience I know it's reliable for cloning non-Advanced Format partitions up to 2TB. If it does, then the issue may be with your imaging tools and/or methods. Create and format a 2GB FAT32 test partition on the 250GB with legacy fdisk/format/sys routines, and see if it boots into C:\ on the original machine.
:max_bytes(150000):strip_icc()/startup-repair-advanced-options-152fca7d6a154c87abb5a961698b7ce5.png)
Otherwise, if you have the time do a modeled compare. Have you rechecked the obvious? Did you ensure the new drive is configured in IDE master mode? Did you reuse the existing 40-pin IDE cable or did you use another, which may be bad? copied the partion over and still sits at the black screen. I used partition commander and created a partition to 2gb and set it to active. I will mention the vm solution to them, but funds are dry. It is all real annoying and frustrating if you don't know what you are doing and there is no good feedback from the system. The syntax of the lines that need to be edited is arcane but you can Google it to figure it all out if you need to. You can change the boot.ini but it is a pain because you need to do so from some other machine that will boot with that drive in it because as it is you don't have to access to any tools to edit the drive. If you make any modification, It will all mess you up unless you modify the boot.ini file to match the change. You also need to make sure the correct partition on the drive is the active one so it will find the boot.ini file when it tries to boot. You can't just move a drive from an IDE to a SATA, or even move the drive from the first IDE port to the second, add a drive to the machine, or even change the number of partitions on a drive. When I say exactly I mean precisely that, it needs to be in the same controller with the same drive order (no extra drives, no fewer drives either) with the same number of partitions etc. Lots of disk cloning software will do things like align the partitions on sector boundaries, add extra partitions or resize them or otherwise fiddle with partition data.Īlso, if you don't put the cloned disk back exactly the same place then you will get the inaccessible boot drive error. When you clone the drive, you theoretically duplicate everything on it but that is not inherently true unless you copy the drive in RAW mode.

Those lines that contain "multi(0)rdisk(0)disk(0)partition(1)" specify the controller, the drive and the partition that is used to boot from. A typical boot.ini looks like:ĭefault=multi(0)rdisk(0)disk(0)partition(1)\WINNT In the old NT, there is a file called boot.ini that controlled the boot process.
