Ok I have a HUGE Problem in W2K...

DMarti

Platinum Member
Oct 15, 2000
2,419
0
0
System in my office has our time clock software installed on it. This is the only critical application I need access to but the computer won't load past the W2K splash screen. It won't boot past it. I tried to load the W2K setup DIsk (Bootable) and use the repair option but it didn't work. I feel it's a Master Boot Record issue but I have no way of repair it due to the fact when I go into Repair mode in the console the admin password is asked and I do not have it. The IT guy who set this PC up in 2001 is long gone and he left no notes on it . So I am fresh out of ideas and need advice. Would an application like Winternals NTFSDOS Professional 4.03 Pro allow me access to the MBR to allow repair? Would any Variant of Norton's Sysem Works allow me to create a rescue disk to use on this? Is there a password recovery tool to help me get admin to get access to the repir console so I can fix the MBR then extract my data then I would reformat and re-install W2K/WXP?

the files I need need to be created within the application (has to be ran in a Windows enviroment). I tried the repair option the express one did nothing to fix it and the recovery console one I can't get into without admin. I can't get into safe mode so I think the MBR is hosed.
 

OneClone

Junior Member
Aug 10, 2004
24
0
0
you can FIXMBR with that revoery console on the the boot CD you have their.

To remove the password try this:

Get the command prompt and
go to C:\winnt\sytem32\config\ and do the following commands:
attrib -a -r -h
copy sam.* a:\
del Sam.*

reboot the computer.
there should be no administrator password.
just put in administrator and hit enter.
replace the sam files to restore the password to hide intrusion.
or chagne the password to something that you want.

i hope this werks.

/CLONE
 

mikecel79

Platinum Member
Jan 15, 2002
2,858
1
81
Originally posted by: OneClone
you can FIXMBR with that revoery console on the the boot CD you have their.

To remove the password try this:

Get the command prompt and
go to C:\winnt\sytem32\config\ and do the following commands:
attrib -a -r -h
copy sam.* a:\
del Sam.*

reboot the computer.
there should be no administrator password.
just put in administrator and hit enter.
replace the sam files to restore the password to hide intrusion.
or chagne the password to something that you want.

i hope this werks.

/CLONE
You can't run that command without getting into the recovery console which you need the admin password to get into. Do a search on this forum for lost admin password and you will find a Linux boot disk that can reset the password for you.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Originally posted by: DMarti
System in my office has our time clock software installed on it. This is the only critical application I need access to but the computer won't load past the W2K splash screen. It won't boot past it. I tried to load the W2K setup DIsk (Bootable) and use the repair option but it didn't work. I feel it's a Master Boot Record issue but I have no way of repair it due to the fact when I go into Repair mode in the console the admin password is asked and I do not have it. The IT guy who set this PC up in 2001 is long gone and he left no notes on it . So I am fresh out of ideas and need advice. Would an application like Winternals NTFSDOS Professional 4.03 Pro allow me access to the MBR to allow repair? Would any Variant of Norton's Sysem Works allow me to create a rescue disk to use on this? Is there a password recovery tool to help me get admin to get access to the repir console so I can fix the MBR then extract my data then I would reformat and re-install W2K/WXP?

the files I need need to be created within the application (has to be ran in a Windows enviroment). I tried the repair option the express one did nothing to fix it and the recovery console one I can't get into without admin. I can't get into safe mode so I think the MBR is hosed.

I suspect this is another issue; if the MBR were really that hosed you wouldn't be able to boot and find the OS at all. The fact that you can find the OS suggests the drive itself is fine.

Why not just hook up the drive to another machine and copy the data you need off of it that way?