Then your query should have been "how to repair boot sector"
You can start the recovery console and from a command prompt issue the
command;
fixboot
to repair the bootsector.
To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %windir% or %systemroot%
(Note: If your drive controller is not natively supported then you'll want
to boot the Windows 2000 install CD-Rom. Then *F6* very early and very
important (at setup is inspecting your system) in the setup to prevent drive
controller detection, and select S to specify additional drivers. Then later
you'll be prompted to insert the manufacturer supplied Windows 2000 driver
for your drive controller in drive "A")
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
:
| Dave,
| Not to worry Dave - Everything is now working fine!
|
| I did use your suggestion to Sys C: and remove the boot.ini & other files
| from the WinMe drive. Worked fine.
|
| The problem with the Win2K drive, was that even although I moved boot.ini
| etc over to it, it would not boot - lacked system files? I was able to
| access it using a start-up Win2K diskette that contained boot.ini etc. I
| tried using the Win2K CD to repair the boot problem, but I used the fast
| repair and I suspect it overwrote some of the SP4 files and caused some
| problems. I decided rather than try fixing the installation, best option
was
| to do a fresh install of W2K (plus all the system and software updates!)
|
| Still completing the W2K installation, but in the end, I will have two
| completely separate OSs accessible by switching in BIOS from IDE WinMe
drive
| to ATA Win2K drive - More cumbersome, but a system that I prefer to dual
| booting because it keeps the two OSs completely separate from each other.
|
| Regards,
|
| GM
|
|