Hi there, I currently have NT installed on a 1Gb SCSI hard drive, which is running out of space. I cannot apply SP4 to this installation. I have recently added a 8Gb IDE drive, and tried to move my installation of NT to this new drive, but am getting a "NTLDR is missing or corrupt" message. I've tried re-installing NT on the IDE drive, but can't get it to boot. I want to restore my current settings, not losing my current configuration. Any help would be appreciated.

The reason copying didn't work is it would not have copied the registry. You would have needed to backup the registry to a tape backup first, then restored it to the new drive. As far as the old drive goes, it you don't have an Emergency Repair Disk, the settings are gone. If it doen't boot, the Master Boot Record, is probably corrupted. You may need to do a low level format on the drive to use it again. Warning a low level format will destroy any hope of recovering anything from the drive.

I can still boot off the SCSI drive. I am trying to boot from the new IDE drive with a new installation of NT, then I will restore my old drive C: (SCSI) configuration to the new one (IDE).

Hi, I'm having the same problem. I have a 1gb FAT16 drive (win98), and a 2gb NTFS drive which is the NT system partition. I ran out of space where the MFT filespace is being used, so I bought a couple 8gb IDE drives and installed both on the Primary IDE channel. No problems there. One drive was designated as C: and the second as F: through Disk Administrator. I imaged the 'NT system' onto the IDE F: 8gb drive and imaged the F: 'NTFS Data' back onto the original system 2gb SCSI drive and now I'm getting the same message. I believe it needs to be referenced correctly through the boot.ini file. Is there a guru that can help us poor chaps out on the proper config settings of the boot.ini file? I think the problem lies there..?

I'm in the middle of another problem related to integrating IDE and SCSI (just installed an IDE drive on a SCSI system and disk administrator doesn't recognize it), but I have a suggestion for your problem. I just stumbled accross this page, but in my cyber-travels I've learned that your BIOS must support SCSI and IDE booting, and I'm pretty sure (depending on your BIOS), you have to select which to boot up from. Maybe you already know this, but there it i

I recently installed SP4 on an BDC and noticed my SCSi drivers(adptec were change) so I had the wrong drive letters, It seems to be a known bug in SP4, It changes SCSi drivers, and there's a workaround but I haven't found t again(It's by Dr Bob but where I don't know) Good luck

There are some files which are accessed by the BIOS at boot time. Unfortunately your BIOS can only reach the first 2 GBytes on your disk. On most SCSI adapters 8 GBytes an be accessed by the BIOS. On a large disk even this is not always enoungh. The reason is that 1/8 of your NTFS partition is reserved for MasterFileTable ($MFT)use and the $MFT is always located on top of a partition. That means: On a 8 GByte IDE disk only the first 2 GBytes are accessible by the BIOS and the first 1 GByte is reserved for $MFT use. So all files loaded during the boot by the BIOS need to be located between the first and second GByte. To copy your NTFS partition to another disk you need to boot NT from a different third medium. (I have a minimun NT installation on a ZIP as on a JAZ drive.) To do an exact copy of the partition to the new disk I execute SCOPY X: Y: /a /o /s (SCOPY.EXE can be found in the NT resource kit.) But prior to that I have to prepare something because SCOPY copies all files in a sorted order. So I rename on the source disk NTLDR -> AAANTLDR NTDETECT.COM -> AAANTDETECT.COM BOOT.INI -> AAABOOT.INI NTBOOTDD.SYS -> AAANTBOOTDD.SYS (if there) and WINNT\SYSTEM32\CONFIG -> WINNT\SYSTEM32\AACONFIG WINNT\SYSTEM32\DRIVERS -> WINNT\SYSTEM32\AADRIVERS WINNT\SYSTEM32\FONTS -> WINNT\SYSTEM32\AAFONTS WINNT\SYSTEM32 -> WINNT\AASYSTEM32 WINNT -> AAWINNT after the SCOPY I undo all file renamings on the source and on the destination drive. Now your copy should be able to boot. As another hint I suggest to copy the ATAPI.SYS from the DRIVERS directory to the root and rename it to NTBOOTDD.SYS and replace the "nulti(0)" in the BOOT.INI by "scsi(0)". Then the NTLDR very early attempts to load the further modules in 32 bit mode. Please mention to do the copy/rename on the source disk prior to the SCOPY. Otherwise the NTBOOTDD.SYS would be outside the first 2 GBytes.