Re: lost cluster at io.sys file stopping boot
From: Licensed to Quill (fountainpen_at_amexol.net)
Date: 06/27/04
- Next message: WoofWoof: "Re: Default Desktop"
- Previous message: JT: "Re: Domains & Authentication"
- In reply to: Dave Patrick: "Re: lost cluster at io.sys file stopping boot"
- Next in thread: Dave Patrick: "Re: lost cluster at io.sys file stopping boot"
- Reply: Dave Patrick: "Re: lost cluster at io.sys file stopping boot"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Jun 2004 10:45:25 -0400
Many thanks: I presume having System Commander will vitiate a lot of what
you said so I should probabaly merely go into the box and disconnect the C
drive which is the Windows 98 one so that the BIOS only sees that Windows
2000 one, and sees it as simply a C drive with no particularly complex boot
sectors.
I can easily create some Windows 2000 recovery discs on another machine
although I have already created some (6) with the XP system I have and
tried most of what you suggested without the detail (it wouldnt let me use
the setup50.exe file on the i386 CD without being in Windows, although I may
try that again if it would make things easier? It probably wont and I will
have to repair whatever is wrong with the 2000 installation and THEN put the
C drive back in line and THEN have system commander sniff around and see
which OSs are present. I am hoping that when it does so, it will let each
OS see itself as the C drive.
But for some mysterious reason the whole OS suddenly can tsee the CD ROM
although it does see the D drive so I am beginning to wonder if ther eis
some problem with the jumper setting on the D drive which is conflicting
with the CD-ROM? (This will presumably be corrected if I disconnect the 98
drive and move the jumper to the MASTER position on the 2000 drive)
FP
"Dave Patrick" <mail@NoSpam.DSPatrick.com> wrote in message
news:%23RcpFx4WEHA.3596@tk2msftngp13.phx.gbl...
> AFAIK there is no 'io.sys' used in Windows 2000 Certainly not part of the
> 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.
> Press ENTER at the "Setup Notification" screen. Press 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:
> %systemroot% and %windir%
>
> Or try creating a boot floppy. For the floppy to successfully boot Windows
> 2000 the disk must contain the "NT" boot sector. Format a diskette (on an
NT
> machine, not a DOS/Win9x, so the NT boot sector gets written to the
floppy),
> then copy ntldr, ntdetect.com, and boot.ini to it; and possibly
> ntbootdd.sys. Edit the boot.ini to give it a correct ARC path for the
> machine you wish to boot.
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "Licensed to Quill" <fountainpen@amexol.net> wrote in message
> news:OT76xg4WEHA.1152@TK2MSFTNGP09.phx.gbl...
> | (SEE OTHER THREADS, - or don't bother as this is reasonably
> | self-explanatory)
> |
> | I think I have traced the problem I was having to what Norton Disc
Doctor
> | told me was a lost cluster in the io.sys file which seems bad enough
> | (curiously it reported what it thinks is a corrupted io.sys file as a
> | non-critical error which is a bit mysterious?). It surely would cause
the
> | system to not boot? (the mobo manufacturer claims that windows 2000 is
> | designed to work equally with all sorts of different disc controllers
and
> | that updating some controller driver is never the cause of a non-boot
> | problem)
> |
> | What I was wondering is whether I can merely copy an io.sys backup file
to
> | the root or if there is some more full method of making the disc
bootable
> | again which I need to use (such as running SFC /scannow from a Windows
98
> | boot disc, as suggested elsewhere, presumably checking the boot files?).
> Is
> | there a way of running setup from the i386 directory on a CD to
reinstall
> | just the boot files and/or check all files including the boot files in
> | WIndows 2000?
> |
> | FP
> |
> |
>
>
- Next message: WoofWoof: "Re: Default Desktop"
- Previous message: JT: "Re: Domains & Authentication"
- In reply to: Dave Patrick: "Re: lost cluster at io.sys file stopping boot"
- Next in thread: Dave Patrick: "Re: lost cluster at io.sys file stopping boot"
- Reply: Dave Patrick: "Re: lost cluster at io.sys file stopping boot"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
