Re: recovery console drivers.
From: Dave Patrick (mail_at_NoSpam.DSPatrick.com)
Date: 06/14/04
- Next message: Steve B: "System Blue Screens"
- Previous message: Dave Patrick: "Re: c0000218 Registry File Failure. The registry cannot..."
- In reply to: anonymous_at_discussions.microsoft.com: "recovery console drivers."
- Next in thread: Mark V: "Re: recovery console drivers."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 13 Jun 2004 21:43:36 -0600
Yes, whether you're trying to start a new install or start the recovery
console doesn't matter. You must supply the manufacturer's Windows 2000
driver for your Ultra100 controller to proceed.
You'll want to boot the Windows 2000 setup disks or CD-Rom. The set of four
install disks can be created from your Windows 2000 CD-Rom; change to the
\bootdisk directory on the CD-Rom and execute makeboot.exe (from dos) or
makebt32.exe (from 32 bit) and follow the prompts.
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 Ultra100 controller in drive "A"
Then 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%
If the software hive is corrupt, it may be possible to rename the software
hive found in;
%windir%\system32\config\software
to software.old
then copy the most recent backup found in
%windir%\repair\regback
as
%windir%\system32\config\software
If that fails you can copy/ use the file
%windir%\repair\software
This file is an image of the hive at the time the OS was installed, so you'd
have to reinstall all software. This being the case you might just as well
blow it away and start a new install. (note: this would at least allow you
to start the OS to make any necessary backups prior to wiping the drive.)
-- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect <anonymous@discussions.microsoft.com> wrote: |I have received an | error /systemroot/system32/config/software and its log | file are missing, corrupt, or unwriteable. | | I want to run the recovery console to copy the old hive... | | After booting from the cd, recovery console does not find | my drive. I did note that during startup from CD it asks | if I need to load 3rd party drivers. I have a promise | ultra 100 raid in my machine. Do I need to load the | drivers from somewhere for these? I have a disk that has | them but have never done this before.. | | led509@nospam_onecom.com
- Next message: Steve B: "System Blue Screens"
- Previous message: Dave Patrick: "Re: c0000218 Registry File Failure. The registry cannot..."
- In reply to: anonymous_at_discussions.microsoft.com: "recovery console drivers."
- Next in thread: Mark V: "Re: recovery console drivers."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
