Removing item from os selector after upgrading to win2000 pro

  • Thread starter Thread starter William
  • Start date Start date
W

William

I recently installed win2000 pro using the clean install
method. I was running win98se and installed win2000pro on
the same partition as win98se. After installation was
complete I have what appears to be a dual boot menu with
win2000pro and win98 as my selection. This os selector
screen appears during post and after selecting win2000pro
the startup option screen appears, the one where you can
hit f8 to enter your startup preferences. If I select
win98 nothing happens, of course there is no win98 left. I
would like to know how to remove the win98 selection
option from the os selector menu. I'm not running multiple
os's so an os selector menu is not needed. Thanks for any
help with this matter.
 
Delete the option from boot.ini located in the root of the system partition.

Explorer|Tools|Folder Options|View, then radio button for "Show hidden files
and folders", then uncheck the box for "Hide protected operating system
files" to locate the files in the system partition.

You'll be removing a line similar to
C:\="Microsoft Windows"

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


:
| I recently installed win2000 pro using the clean install
| method. I was running win98se and installed win2000pro on
| the same partition as win98se. After installation was
| complete I have what appears to be a dual boot menu with
| win2000pro and win98 as my selection. This os selector
| screen appears during post and after selecting win2000pro
| the startup option screen appears, the one where you can
| hit f8 to enter your startup preferences. If I select
| win98 nothing happens, of course there is no win98 left. I
| would like to know how to remove the win98 selection
| option from the os selector menu. I'm not running multiple
| os's so an os selector menu is not needed. Thanks for any
| help with this matter.
 
Thank you very much Dave. I suspected that the boot.ini
was the culprit but could not locate it, so I again thank
you and I'll try to apply your instructions. William
 
Back
Top