Computer thinks that there is 2 OS'es...

[LS20]

While I had W2k running on HDD1, i used the Disk Manager to delete all partitions on HDD2, and made it into NTFS PRIMARY PARTITION to store backup files.

Then, I backed up my multimedia files/applications onto HDD2, and proceeded to wipe out HDD1. I booted from the Windows CDROM, and from the Windows Setup, I completely wiped out HDD1 and installed a fresh copy of the OS on there.

So....

HDD1: cleaned, fresh OS
HDD2: cleaned, storage


When I boot the computer, though, it gives me the OS Selector screen asking me whether I want to Boot into Windows 2000 Professional or Windows 2000 Professional.


The first one is, ofcourse, the OS on HDD1. I *think* that it thinks there is another OS on HDD2 (which there isn't). Is that correct? or is there another explanation. If I repartitioned HDD2 to be a Logical Drive , then will this problem go away?

 

[bruincal]

as a workaround, you can have it automatically boot to the first windows 2000 in the menu without asking you...

go to Control Panel, System, Settings tab, click on Settings under Startup and Recovery, and uncheck Time to display list of operating systems ... (or just set the time to 0 )...

when you restart, it should not show the operating system menu anymore ...

and oh yeah, there isn't two OSes on your hard drives ... its just that since your second storage drive was formatted through win2000, and it has the win2000 file system stuff on it (like recycle bin, etc) .. so win2000 setup interpreted it as another OS... but in reality, if you tried to boot from the second storage hard disk, your computer would just freeze ... this happens a lot to me at work where i install win2000 on new systems ... after a format, i get the menu with choices Windows 2000 Professional and Previous Operating System .. . Even though I formatted there should be no "Previous Operating System" .. but it just does that .. so i kill the menu through the procedure above.

good luck! =)

 

[dbwillis]

Or you can try and remove it from the boot.ini file

 

[zetter]

Removing the bogus entry from the boot.ini file is a much tidier solution than setting the timeout to 0.

 

[Rhi]

Yep. Remove the entry. Go Here

-Rhi