last week win2k corrupted one of the Hive files and I was forced to reinsall it. During setup, the setup crashed 3 times and only after the fourth time was I able to get into windows. During the installing of drivers and such, windows continued to crash repeatedly and stoped only after I upgraded to IE5.5. It ran fine for 4 days (with the memory at100 and not 133mhz) and then gave me the same error as before reformattinga and reinstalling (corupted hive).
I tried to reinsstall it again (with memory at 133mhz), but initial setup would crash (the very first stage before it even loads the setup welcome message). I lowered the memory to 100 again and set the performance to "normal" (from bios) and was able to repair the corrupted file. At the moment win2k cannot be started (even in safe mode) because the windows logon process always crashes.
I am writing this from linux, which has crashed 3 times during the last week and I am fairly sure its the memory thats causing all these problems.
Am I right? could it be something else?
I tried to reinsstall it again (with memory at 133mhz), but initial setup would crash (the very first stage before it even loads the setup welcome message). I lowered the memory to 100 again and set the performance to "normal" (from bios) and was able to repair the corrupted file. At the moment win2k cannot be started (even in safe mode) because the windows logon process always crashes.
I am writing this from linux, which has crashed 3 times during the last week and I am fairly sure its the memory thats causing all these problems.
Am I right? could it be something else?
Facebook
Twitter