• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Just installed a new hard drive...**NEW PROBLEM**

  • Thread starter Thread starter
  • Start date Start date

I had win2k on my old 40gig, and I put in another 120 gigs. I was having problems with my old install, so I reinstalled win2k on the new 120 gig. I put 3 different partitions on there, and put win2k on one of them. Install goes nicely, everything is working fine. Now, I put that hard drive as my primary, and in bios I changed it to boot from that instead of the 40 gig. When I rebooted, It wont boot from the hard drive and says "Press a key to reboot." But boots fine and gives me options when I use the 40 gig to boot. The 40 gig is Drive C and the partition the new install is on is Drive F. Do I need to reformat it or change the jumper settings? Both are set to master, but the 40 gig is secondary master. Any help?

UPDATE: I tried what Scott said, and just simply unplugged the other Hard drive. However, now when I try to boot with the 120 gig only, i get this error "NTLDR is missing. Press ctrl-alt-del to reboot."
But yet, it isnt missing when the 40 gig is plugged in. ALso, under computer management in windows, it says the new operating system (the one I want to use) is "Healthy(Boot)" while the other is "Healthy(System)" The other is drive C, and it will not let me change the drive letters from windows. ANyone know how to do this from Fdisk or any other work around? Also, how do you make it so the one I want to use is both the boot and system?
 
Use FDISK. When you tell FDISK to make more than one partition, you have to manually set the "Active" partition (the boot partition). If you created the partitions in the install program, it may have not set the "active" attribute for the boot partition.

You may also want to use FDISK to remove the "active/boot" setting on the 40. Some OS get wierd when they see more than one booatable drive.

Try temporarily disconnecting the 40 until you "fer sher" have a good booting copy on the new drive.

Good Luck

Scott
 
Put your new drive on the primary channel as Master. Boot off the W2K CD, run the repair option and have it inspect the boot sector.

You need to have a boot.ini on the new drive that points to the proper disk # and partition # of the W2K install. The repair option should fix it up for you.

You are getting the NTLDR missing error because either it is not finding a boot.ini in the proper place or it is pointing to a drive/partition that doesn't exist or have the W2K boot files located on it.

 
Ok well, here we go again. Except now, I have to post from my brothers computer because windows wont even load, new harddrive or old. Ok, so I start repair on new hard drive, while the other one was unplugged. blah blah blah, starts copying files...yay! BOOOO! Says it cant load the following files:
Setupdd.sys
arcldr.exe
arcsetup.exe
ntldr
NTDETECT.COM
WTF?!?!?!

Ok, fine, I will completely reinstall the new OS...so I plug in my old hard drive, and now this message pops up:
Current File missing or corrupt
winnt\system32\CONFIG\SYSTEM
I'm going to disconnect new hard drive and put in new one, hoping that I will be able to boot. If I cant, I suppose I can reformat both and start new. After all, the info I need is already on different partitions. And yes, win2k was on the first partition.
 
When you set up windows on the 120Gb drive, I'm assuming that you had the other drive physically connected!
The OS would have put a hand full of files on what it concidered the "C" drive, which it seems 'pissed on your bonfire !'

Building W2K on a PC is best initiated with a single physical drive in the PC.
 
Back
Top