Problems booting

  • Thread starter Thread starter Paul Floyd
  • Start date Start date
P

Paul Floyd

Hi

Yesterday when I tried to boot W2K, login failed. Today I've been trying
to find out why, without success. It's an old PC, and getting a bit
flaky.

My first thought was a problem with the disk, so I restored from my last
backup, but that has the same problem.

So far I've gotten as far as extracting a ntbtlog.txt (I can get to a
rescue command prompt). Here are the drivers that fail to load:

Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Did not load driver \SystemRoot\System32\Drivers\sglfb.SYS
Did not load driver \SystemRoot\System32\Drivers\tga.SYS
Did not load driver \??\D:\Program Files\Symantec\SYMEVENT.SYS
Did not load driver \??\D:\Program Files\Symantec\SYMEVENT.SYS
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\System32\DRIVERS\redbook.sys
Did not load driver \SystemRoot\System32\Drivers\Parport.SYS
Did not load driver \SystemRoot\System32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Did not load driver \??\D:\WINNT\system32\drivers\pmemnt.sys
Did not load driver \??\D:\WINNT\system32\drivers\symlcbrd.sys
Did not load driver \??\D:\Program Files\Symantec\SYMEVENT.SYS

I think that most of these are for exotic hardware that I don't have, or
for unused interfaces. SYMEVENT.SYS looks more of a problem though.

I did try repairing, but it couldn't find the root (curious, since the
console login did). I haven't gone through all my floppies, but I can't
locate a rescue floppy.

The other thing that I've tried was to remove all superfluous adapters
(sound, NIC), but that didn't help either.

No problems booting other OSes (Solaris 10U3, Linux RH9 and FC6, FreeBSD
6.a and OS/2 4).

Any suggestions welcome.

A bientot
Paul
 
The file system may have failed for one reason or another. (hardware or
other failure) You can try from the recovery console command line;

chkdsk /r
(/r implies /f )

I'd also download and run the manufacturer's diagnostic tools. (drive
controller and disk)


You can also try restoring your most recent registry backup by replacing the
files in;

%systemroot%\system32\config\

with those found in;

%systemroot%\repair\regback

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, %systemroot% or %windir%


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
The file system may have failed for one reason or another. (hardware or
other failure) You can try from the recovery console command line;

chkdsk /r
(/r implies /f )
Click to expand...

I did an fdisk, and double checked with Partition Magic 8. Nothing
wrong.
I'd also download and run the manufacturer's diagnostic tools. (drive
controller and disk)
Click to expand...

I'll look into that.
You can also try restoring your most recent registry backup by replacing the
files in;

%systemroot%\system32\config\

with those found in;

%systemroot%\repair\regback
Click to expand...

I'll have a look at that as well.
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, %systemroot% or %windir%
Click to expand...

I've managed to get to the Recovery Console.

Thanks for the help.

Paul
 
Back
Top