downhiller80
Platinum Member
Right, I used to be pretty good at sorting problems out, but since installing win2k I've not had any OS related problems for over 2 years!
But yesterday I booted and got this:
"windows 2000 could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM"
So I tried to repair it by booting off of the win2k CD. First hurdle was that it couldn't find myh installation, I remembered I need to show it the Promise Ultra100 drivers, which I've now done.
Then it gives me two options; console repair or automatic repair. Automatic repair will not work because it asks for an emergency boot disc and I've no idea where it is. Pressing "L" to make it search for the installation itself is also fruitless.
Which is odd, because if I go to "console repair" it has no problems finding my winnt directory.
But I don't know what to do in the console to fix my windows problem. There's an indentically sized file called SYSTEM.ALT which I could try renaming to SYSTEM I suppose, but I suspect things might only be made worse by this 🙂
SO - how can I sort this out? My "tool" at the moment is my housemate's aging windows 98 laptop. Not going to be easy to create a win2k emergency boot disk on here is it....
CHEERS
- seb
But yesterday I booted and got this:
"windows 2000 could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM"
So I tried to repair it by booting off of the win2k CD. First hurdle was that it couldn't find myh installation, I remembered I need to show it the Promise Ultra100 drivers, which I've now done.
Then it gives me two options; console repair or automatic repair. Automatic repair will not work because it asks for an emergency boot disc and I've no idea where it is. Pressing "L" to make it search for the installation itself is also fruitless.
Which is odd, because if I go to "console repair" it has no problems finding my winnt directory.
But I don't know what to do in the console to fix my windows problem. There's an indentically sized file called SYSTEM.ALT which I could try renaming to SYSTEM I suppose, but I suspect things might only be made worse by this 🙂
SO - how can I sort this out? My "tool" at the moment is my housemate's aging windows 98 laptop. Not going to be easy to create a win2k emergency boot disk on here is it....
CHEERS
- seb