Win2K not booting - help!
Discussion
Chaps,
OK, my desktop machine has started to play silly bu99ers. Not sure why - I closed it down as normal last night, and turning it on again this evening it produces this message:
"Windows 2000 could not start because the following file is missing or corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEM
You can attempt to repair this file by starting Windows 2000 Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair."
OK, so I stuck in the Win2K CD that I have, and booted from that. I was asked whether I wanted to install or repair windows (repair - 'r, like it told me to), and then asked whether to use the repair console or to do an emergency repair (tried both) and whether to repair everything or do it manually (tried both of these as well.)
And each time it re-boots, comes back to asking whether I want to reboot from the CD, I say 'No' and it comes back with the same error.
So, any suggestions? (The alternative is to leave the CD in there but then it just boots from the CD and asks again whether I want to install windows or repair it.)
I've tried this 6 times now, with no luck!
Any help very gratefully appreciated ... (this is being written from the lappie, so I can still access PH - phew!)
Oli.
OK, my desktop machine has started to play silly bu99ers. Not sure why - I closed it down as normal last night, and turning it on again this evening it produces this message:
"Windows 2000 could not start because the following file is missing or corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEM
You can attempt to repair this file by starting Windows 2000 Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair."
OK, so I stuck in the Win2K CD that I have, and booted from that. I was asked whether I wanted to install or repair windows (repair - 'r, like it told me to), and then asked whether to use the repair console or to do an emergency repair (tried both) and whether to repair everything or do it manually (tried both of these as well.)
And each time it re-boots, comes back to asking whether I want to reboot from the CD, I say 'No' and it comes back with the same error.
So, any suggestions? (The alternative is to leave the CD in there but then it just boots from the CD and asks again whether I want to install windows or repair it.)
I've tried this 6 times now, with no luck!
Any help very gratefully appreciated ... (this is being written from the lappie, so I can still access PH - phew!)
Oli.
Try booting into the recovery console, and running
chkdsk c: /p /r
Twice, then trying to boot up again. Failing that, if the automated repair didn't work you might be into clean reinstall territory.
The file mentioned is the system registry, the hard disk has developed either a physical or logical fault thats stopping it from being read cleanly, hence the error. chkdsk may or may not be able to fix it, its fingers crossed time!
chkdsk c: /p /r
Twice, then trying to boot up again. Failing that, if the automated repair didn't work you might be into clean reinstall territory.
The file mentioned is the system registry, the hard disk has developed either a physical or logical fault thats stopping it from being read cleanly, hence the error. chkdsk may or may not be able to fix it, its fingers crossed time!
That's sensible advice. The only thing I would add is that if you have precious data on the drive the first thing you should do is take it out of your desktop PC (or make it a slave if you have another drive in there) and copy your valuable data onto something else before you try recovering it. That shouldn't really be necessary but it's a precaution worth taking for valuable data since the drive might get more corrupted over time if it's slowly failing.
Neil,
That's not the first time you have given me IT advice on here - many thanks, once again.
As it is, the chkdsk command didn't solve the problem. I did it twice, as suggested, and the subsequent reboot gave the same problem.
So, the consensus? A new HDD, or is it worth re-formatting the partition with the Windows install on it and re-building? I did a full rebuild - the first for 4 years - about 2 weeks ago, and it was running exceptionally sweetly afterwards.
Or is it simply new PC time?
Thanks again for your help. You too Roadsweeper.
Oli.
That's not the first time you have given me IT advice on here - many thanks, once again.
As it is, the chkdsk command didn't solve the problem. I did it twice, as suggested, and the subsequent reboot gave the same problem.
So, the consensus? A new HDD, or is it worth re-formatting the partition with the Windows install on it and re-building? I did a full rebuild - the first for 4 years - about 2 weeks ago, and it was running exceptionally sweetly afterwards.
Or is it simply new PC time?
Thanks again for your help. You too Roadsweeper.
Oli.
To be honest, running 2K. Assuming it's an original from the factory 2K. The machine will be getting pretty long in the tooth, probably lacking a lot of nifty features (Dual Core, dual memory channels, SATA, non-PCI carded USB2, proper USB2 support) and so on.
Even a bottom of the rung 'upgrade bundle' (case, ram, cpu, mobo) will run rings around it. I'd give serious consideration to a new machine. But if the budget is tight, pick up a IDE HDD and use it as the master drive with the old one as a slave, this way you can copy the data off it.
Even a bottom of the rung 'upgrade bundle' (case, ram, cpu, mobo) will run rings around it. I'd give serious consideration to a new machine. But if the budget is tight, pick up a IDE HDD and use it as the master drive with the old one as a slave, this way you can copy the data off it.
The only other thing I can suggest is, there's a copy of the system registry in c:/winnt/repair from when 2K was first installed. It will be rough and not much will work but if you copy /winnt/repair/system to /winnt/system32/config/system you might get the thing to boot up, which might make backing up easier. HTH.
ThePassenger/Sarah (you're a techie Girl!),
Thanks. I know the machine is old; it's a shuttle box, with what was a fast processor in it (Athlon 1800), and a good slug of memory (1 Gb). It does have dual memory channels, but is only a single-core processor. The USB's are USB2, but I don't know whether these are non-PCI carded USB2's or whether it has proper USB2 support (and I haven't the foggiest what a SATA is!) When I built it about 5 years ago it was pretty cutting-edge, but it is dated compared to what you'd buy now. However, I rebuilt it about 2 weeks ago and it was working very nicely, and I was hoping I'd get another 9-12 months out of it before needing to build a replacement. Heigh ho. I'll see about getting it working again and then perhaps flog it on eBay, and put the money raised towards a new box.
SneakyNeil,
Thanks again. As it is, the HDD is partitioned into three drives, and the fault is obviously on the C: part of it. I have been storing programmes on the D: drive, and data on the E: drive, so I can fairly easily re-format C: and re-build on there, OR (probably better) get another HDD and rebuilt it with this, using the old HDD as a slave drive (presumably I do this by fiddling the jumpers?) and copying stuff onto the (more reliable) new HDD.
Out of interest, what causes the HDD to become unusable like this? I am presuming it is just bad luck that the bit that has failed is critical to the windows boot-up? Would the fact that I rebuilt the machine for the first time in 5 years about 2 weeks ago have contributed to this?
Oli.
Thanks. I know the machine is old; it's a shuttle box, with what was a fast processor in it (Athlon 1800), and a good slug of memory (1 Gb). It does have dual memory channels, but is only a single-core processor. The USB's are USB2, but I don't know whether these are non-PCI carded USB2's or whether it has proper USB2 support (and I haven't the foggiest what a SATA is!) When I built it about 5 years ago it was pretty cutting-edge, but it is dated compared to what you'd buy now. However, I rebuilt it about 2 weeks ago and it was working very nicely, and I was hoping I'd get another 9-12 months out of it before needing to build a replacement. Heigh ho. I'll see about getting it working again and then perhaps flog it on eBay, and put the money raised towards a new box.
SneakyNeil,
Thanks again. As it is, the HDD is partitioned into three drives, and the fault is obviously on the C: part of it. I have been storing programmes on the D: drive, and data on the E: drive, so I can fairly easily re-format C: and re-build on there, OR (probably better) get another HDD and rebuilt it with this, using the old HDD as a slave drive (presumably I do this by fiddling the jumpers?) and copying stuff onto the (more reliable) new HDD.
Out of interest, what causes the HDD to become unusable like this? I am presuming it is just bad luck that the bit that has failed is critical to the windows boot-up? Would the fact that I rebuilt the machine for the first time in 5 years about 2 weeks ago have contributed to this?
Oli.
Can you put the HDD in a different machine as a slave? That's fixed many a problem for me in the past.
Boot from the parent machine and let it fix the file system corruption. Then you can have a look at the file structure and make an informed decision about the best way to proceed and backup your data at the same time.
Boot from the parent machine and let it fix the file system corruption. Then you can have a look at the file structure and make an informed decision about the best way to proceed and backup your data at the same time.
I'm sure I posted about this a while ago, my 2K box does this all the time.
You need to boot into DOS somehow, I think there is a console boot on the NT CD.
then CD into WINNT\system32\config
there is a backup of your SYSTEM file in there called SYSTEM.ALT.
copy it over the broken (SYSTEM) one, reboot and the jobs a good un.
backup your your SYSTEM file first just in case.
so
copy SYSTEM SYSTEM.broken
copy SYSTEM.ALT SYSTEM
reboot.
best
Ex
You need to boot into DOS somehow, I think there is a console boot on the NT CD.
then CD into WINNT\system32\config
there is a backup of your SYSTEM file in there called SYSTEM.ALT.
copy it over the broken (SYSTEM) one, reboot and the jobs a good un.
backup your your SYSTEM file first just in case.
so
copy SYSTEM SYSTEM.broken
copy SYSTEM.ALT SYSTEM
reboot.
best
Ex
Lots more ideas to try - thanks chaps.
Rob, I like the idea of using it as a slave drive in another machine, the trouble is that I have only one desktop. (And a Mac G4, but I'm not sure that this would be a helpful tool in this case.)
I haven't looked at the price of new HDD's, but they can't be that much. So, if I can get it to boot and run reliably, I can copy the data over and make it run, and then think about selling it on eBay.
So, it's just the booting ... I'll try again this evening.
Oli.
Rob, I like the idea of using it as a slave drive in another machine, the trouble is that I have only one desktop. (And a Mac G4, but I'm not sure that this would be a helpful tool in this case.)
I haven't looked at the price of new HDD's, but they can't be that much. So, if I can get it to boot and run reliably, I can copy the data over and make it run, and then think about selling it on eBay.
So, it's just the booting ... I'll try again this evening.
Oli.
TheExcession said:
Oli,
Did ouir posts cross?
The technique above works everytime for me.
Adrian, Did ouir posts cross?
The technique above works everytime for me.
No, didn't quite cross, but it's very good advice all the same - thanks. I'll certainly try your suggestion, but the machine is at home and I'm at work so will have to try this evening ...
Does running the "recovery console" from the CD give me a DOS prompt? (As in, it gives me a prompt that looks like a DOS prompt, is it the same?)
Oli.
zcacogp said:
Does running the "recovery console" from the CD give me a DOS prompt? (As in, it gives me a prompt that looks like a DOS prompt, is it the same?)
Oli.
yep that's it.Oli.
I'm not sure if a Workstation CD has the option, the 2003 Server CD does. IF you're disks are NTFS then you'll need a version of DOS that will support that, otherwise you might be able to use a floppy disk DOS version, there are loads on the Internet.
You can probably download a bootable iso and burn it do disk.
best
Ade
Chaps,
Thanks for your input. I have made some progress.
Adrian - the file system.alt in the winnt/system32/config directory didn't work when renamed system. I tried it (keeping a copy of the old system.alt) and it wouldn't do anything - still produced the same error.
However, when I tried the copy of system from winnt/repair, it did work. I copied it across to winnt/system32/config, and it booted OK.
It is currently running (in front of me!), with a very simple screen resolution and what looks like 16 colours, and I haven't actually tried doing anything with it.
Given this is the situation, what are anyone's suggestions? Format the disk and start again? Buy a new HDD? Reset the screen resolution and just use it (keeping everything backed up)?
If I go for this last option (re-set the screen res and use it as it is) what are the problems of there being further problems in store?
Thanks very much to everyone for your help. It is working, without me having to spend blood, sweat, tears and greenbacks on it, so I am exceptionally grateful.
(Oh, the screensaver has just kicked in, so that is working as well.)
Oli.
Thanks for your input. I have made some progress.
Adrian - the file system.alt in the winnt/system32/config directory didn't work when renamed system. I tried it (keeping a copy of the old system.alt) and it wouldn't do anything - still produced the same error.
However, when I tried the copy of system from winnt/repair, it did work. I copied it across to winnt/system32/config, and it booted OK.
It is currently running (in front of me!), with a very simple screen resolution and what looks like 16 colours, and I haven't actually tried doing anything with it.
Given this is the situation, what are anyone's suggestions? Format the disk and start again? Buy a new HDD? Reset the screen resolution and just use it (keeping everything backed up)?
If I go for this last option (re-set the screen res and use it as it is) what are the problems of there being further problems in store?
Thanks very much to everyone for your help. It is working, without me having to spend blood, sweat, tears and greenbacks on it, so I am exceptionally grateful.
(Oh, the screensaver has just kicked in, so that is working as well.)
Oli.
Quick follow-up ...
The machine shut down and re-started OK, so good news there.
It seems to have lost a load of drivers (screen driver, sound driver etc) so these will need to be reloaded, but this is no great shakes. It has also lost all network settings, but this is not the end of the world.
Thanks again, and any suggestions on where to go from here will be welcomed.
Oli.
The machine shut down and re-started OK, so good news there.
It seems to have lost a load of drivers (screen driver, sound driver etc) so these will need to be reloaded, but this is no great shakes. It has also lost all network settings, but this is not the end of the world.
Thanks again, and any suggestions on where to go from here will be welcomed.
Oli.
Two choices, you could re-install all your drivers and just continue from there. You'll probably keep finding odd bits and bobs that don't work and also need to be reinstalled. Option two, reinstall 2K from scratch. I'd probably just make a start on getting all the drivers & applications working, and if you experience too much hassle/weirdness then consider if it's going to be less hassle in the long term to just nuke from orbit.
Ps, the drivers are most probably still there, if you right click/uninstall in device manager and then reboot it might well just find the right drivers again.
HTH
Neil
Ps, the drivers are most probably still there, if you right click/uninstall in device manager and then reboot it might well just find the right drivers again.
HTH
Neil
As has been said, the "repair" version is a bum basic registry from when the PC was first installed. You'll probably need to reinstall quite a few of your apps/drivers etc. to get it back to how you want it.
I'd run a chkdsk with surface scan before you go any further though to see what condition the disk is in.
I'd run a chkdsk with surface scan before you go any further though to see what condition the disk is in.
Chaps,
Thanks again for you input.
I am now having a problem-mette which I think is related to the loss of the registry.
I had Nero installed on the machine, but post-registry failure, it kept on asking me for the Nero disk to re-install it. I tried putting the disk in to re-install, but it didn't like it. So, I went to the Control Panel and removed the Nero software, and tried to re-install it.
However, whenever I put the disk in, it starts calling Win Installer, gets some of the way along the process then gives me the message that "The System Administrator Has Set Policies to Prevent This Installation". However, it gives me this message when I am logged on as myself (who is set as an Admin), when I as logged on as "Administrator", or when I am logged on as a new account, set up as an Admin.
I have tried a google search and come to nothing.
Any suggestions?
Thanks again.
Oli.
Thanks again for you input.
I am now having a problem-mette which I think is related to the loss of the registry.
I had Nero installed on the machine, but post-registry failure, it kept on asking me for the Nero disk to re-install it. I tried putting the disk in to re-install, but it didn't like it. So, I went to the Control Panel and removed the Nero software, and tried to re-install it.
However, whenever I put the disk in, it starts calling Win Installer, gets some of the way along the process then gives me the message that "The System Administrator Has Set Policies to Prevent This Installation". However, it gives me this message when I am logged on as myself (who is set as an Admin), when I as logged on as "Administrator", or when I am logged on as a new account, set up as an Admin.
I have tried a google search and come to nothing.
Any suggestions?
Thanks again.
Oli.
SneakyNeil said:
Slight possibility, start/run/regedit
open 'hkey classes root'
open 'installer'
open 'products'
find the randomly named key associated with Nero, and delete it.
Try the install again.
Neil, open 'hkey classes root'
open 'installer'
open 'products'
find the randomly named key associated with Nero, and delete it.
Try the install again.
Thanks, I'll try that this evening. (I've been away all weekend so haven't given it much thought.)
If it doesn't work, I'll probably (and this has looked semi-likely since it went t1ts-up) end up buying a new HDD and re-building it (again!)
Thanks for the suggestion.
Oli.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff


