G
Guest
Guest
Has anybody out there run into this error?
******************************************
Stop (c0000218) Regestry file failure
The regestry cannot load the hive file
SystemRoot\System32\Config\SOFTWARE
or its log or alternate
It is corrupt, absent, or not writable
**************************************
This error occurs just after the Win2K splash screen. The starting up progress bar reaches 100%, and then it goes to the blue screen w/ the registry hive error. The system then reboots itself.
-----------------------
Here's my system setup:
Mainboard: Abit BE6-II
CPU: PII 450
Memory: 128mb Micron PC133 SDRAM
Hard Disk: Seagate ATA - connected to Ultra DMA66 primary controller.
Video Card: Diamond Viper II TNT2
Case/Power Supply: Enlight midtower - 250 Watt power supply
------------------------------------------------------------
The interesting thing about this problem is that it only seems to happen when I leave the system powered down for a while (this last time it was down for about a week). The last time I received this error I just re-installed Win2K, thinking it was a problem w/ the installation. After re-installing Win2K the system worked perfectly, until I left it powered down. Any ideas????
Any and all help is greatly appreciated.
Thanks, Dave
******************************************
Stop (c0000218) Regestry file failure
The regestry cannot load the hive file
SystemRoot\System32\Config\SOFTWARE
or its log or alternate
It is corrupt, absent, or not writable
**************************************
This error occurs just after the Win2K splash screen. The starting up progress bar reaches 100%, and then it goes to the blue screen w/ the registry hive error. The system then reboots itself.
-----------------------
Here's my system setup:
Mainboard: Abit BE6-II
CPU: PII 450
Memory: 128mb Micron PC133 SDRAM
Hard Disk: Seagate ATA - connected to Ultra DMA66 primary controller.
Video Card: Diamond Viper II TNT2
Case/Power Supply: Enlight midtower - 250 Watt power supply
------------------------------------------------------------
The interesting thing about this problem is that it only seems to happen when I leave the system powered down for a while (this last time it was down for about a week). The last time I received this error I just re-installed Win2K, thinking it was a problem w/ the installation. After re-installing Win2K the system worked perfectly, until I left it powered down. Any ideas????
Any and all help is greatly appreciated.
Thanks, Dave