Re: Cannot load the Hive



Might be time for that clean install.

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 raid controller in drive "A"

If you wait and then S to specify additional drivers, then it may be too
late as Windows 2000 Setup at this point may have already assigned the
resources your drive's controller is wanting to use.

When you get to the point, delete the existing NTFS and or other partitions
found. After you delete the partition(s) abort the install, then again
restart the pc booting the CD-Rom or setup disks to avoid unexpected drive
letter assignments with your new install.

Be sure to apply these to your new install before connecting to any network.

http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE
http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx
http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx

--

Regards,

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

"DL" wrote:
> Background:
> Using Sil mirror raid, started getting intermittent event errors on Sil
> controller eg 'did not start'
> Certain apps exhibited odd behaviour.
> Broke the mirror, rebooted extreamly! slow boot.
> Rebooted a number of times with differing err msgs.
>
> Used last good config, ERD, Erdnt and recovery consul to restore backup
> and default hives, all to no effect.
> Tried a win reinstall on one hd, still get hive err.msgs.
>
> Run hd manu checking utility over both disks for a number of loops, all ok
> Run chkdsk all ok.
>
> At this stage I'm tending towards mobo problem.
> What think you?
> TY


.



Relevant Pages


Loading