Boot with disk one and keep feeding it disks until it finally loads up a "Welcome to setup" screen. At this screen press R. On the Agreement screen, press F8. On the next, select the operating system to repair (you should have only one) and press R. This should take you to a command prompt. Let me know when you're there.
Trying to fix friends pc with mahy problems
Started by
leanneqld
, Apr 25 2006 10:31 PM
#91
Posted 27 April 2006 - 09:47 PM
Boot with disk one and keep feeding it disks until it finally loads up a "Welcome to setup" screen. At this screen press R. On the Agreement screen, press F8. On the next, select the operating system to repair (you should have only one) and press R. This should take you to a command prompt. Let me know when you're there.
#92
Posted 27 April 2006 - 09:54 PM
%windir% kept coming up with "not recognized as an internal or external command"etc etc ..ok..onto the floppies
#93
Posted 27 April 2006 - 10:06 PM
We're going to replace the registry hive. This should start the machine, but it may not be pretty. We'll hope that there is a restore point waiting for us...if not, at least you should be able to recover the data.
At the Recovery Console command prompt, type the following lines exactly as they are below, pressing ENTER after you type each line:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default
copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default
Type exit to quit Recovery Console. Your computer will restart.
At the Recovery Console command prompt, type the following lines exactly as they are below, pressing ENTER after you type each line:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default
copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default
Type exit to quit Recovery Console. Your computer will restart.
#94
Posted 27 April 2006 - 10:33 PM
done....it didnt restart the setup but now all i have is a black screen
#95
Posted 27 April 2006 - 10:53 PM
Believe it or not, that's progress!
Hopefully this removed a good portion of the malware out of the registry...I think that was a big part of the problem.
Using the cd this time, boot into Recovery Console the same way you did with the floppies. Once at the command prompt, type sfc /scannow (Note the space between sfc and /) and press "Enter". You will be asked for your installation cd, so have it handy. Wait for the scan to finish (this might take up to an hour). When it's finished, Get back to command prompt and type chkdsk /r (Again...note the space) and reboot when prompted (type Y and press Enter). This will run on boot-up so restart will take a while...be patient.
If sfc /scannow won't run, move on to the chkdsk /r and run that. Try to boot to Windows.
If that won't start the machine, run the Repair again, but make sure the Lan is disabled in BIOS and the Default is still set. There should still be a viable Windows installation on the machine.
Let me know how you make out...
Hopefully this removed a good portion of the malware out of the registry...I think that was a big part of the problem.
Using the cd this time, boot into Recovery Console the same way you did with the floppies. Once at the command prompt, type sfc /scannow (Note the space between sfc and /) and press "Enter". You will be asked for your installation cd, so have it handy. Wait for the scan to finish (this might take up to an hour). When it's finished, Get back to command prompt and type chkdsk /r (Again...note the space) and reboot when prompted (type Y and press Enter). This will run on boot-up so restart will take a while...be patient.
If sfc /scannow won't run, move on to the chkdsk /r and run that. Try to boot to Windows.
If that won't start the machine, run the Repair again, but make sure the Lan is disabled in BIOS and the Default is still set. There should still be a viable Windows installation on the machine.
Let me know how you make out...
#96
Posted 27 April 2006 - 10:57 PM
i have to go into the bios first and cahnage the boot sequence first, to cd drive right?
#97
Posted 27 April 2006 - 11:08 PM
If you didn't change it to boot from the floppies, it should still be set. BUT I'd like for you to double check that the LAN is still disabled and the BIOS is still set to Default...reset it if you are unsure.
Also...are your mouse and keyboard connected via USB? If they are, if you have a PS2 keyboard and mouse available, I'd use them if you end up running the repair. Alternatively, you could unhook the keyboard and mouse during the repair...after you get it started and have finished with the part that requires their use. That may help you get past that magic 34 minute mark.
Also...are your mouse and keyboard connected via USB? If they are, if you have a PS2 keyboard and mouse available, I'd use them if you end up running the repair. Alternatively, you could unhook the keyboard and mouse during the repair...after you get it started and have finished with the part that requires their use. That may help you get past that magic 34 minute mark.
Edited by wannabe1, 27 April 2006 - 11:08 PM.
#98
Posted 28 April 2006 - 12:35 AM
hi, I haven't done a repair yet..i got to the prompt and did the chkdsk ..and noticed that the moitor kept going from green on light to amber........if i turned it off then on i had no signal...muat ne faulty......i had to reboot after chkdsk so i changed the monitor and i now have windows screen back up with all the original users and their log on pictures/passwords whicj i had previoely deleted right at the start of all this. Now i'm not sure what to do......run repair again/a clean install/get rid of all the users like i did b4 leaving just the one that i used at the start to clean off all the old programs??????????????
#99
Posted 28 April 2006 - 12:35 AM
ps, the screen looks crap...kind of dotty, but i can see
#100
Posted 28 April 2006 - 07:08 AM
Told you it wouldn't be pretty....
Check and see if there is a system restore point, but don't restore the machine yet. That point, if there, will have that wonderful collection of nasties in it...but, it will also bring the machine a little closer to where we need to be. Just let me know if there is a point to restore to.
Check and see if there is a system restore point, but don't restore the machine yet. That point, if there, will have that wonderful collection of nasties in it...but, it will also bring the machine a little closer to where we need to be. Just let me know if there is a point to restore to.
#101
Posted 28 April 2006 - 07:33 AM
hey, i can't check at the moment..remember i said the monitor died and i got another?..well it aint the monitor...it's the video card cause the 2nd monitor is doing the same thing....green light to orange to no signal.
maybe that nvidia install part of setup caused the prob?...anyway the tower is being pulled apart as we speak to check the card...
maybe that nvidia install part of setup caused the prob?...anyway the tower is being pulled apart as we speak to check the card...
#102
Posted 28 April 2006 - 07:38 AM
Will it boot to the BIOS screen? See if you can change the setting there to reanable the nVidia or set it to run in VGA mode until we get the video issue sorted out.
#103
Posted 28 April 2006 - 07:51 AM
yeah i can get to the bios...we are debating that if its the card you cant see the bios/can see the bios......ok...we just removed the card..monitor back up.......detected ne hardware(vga) no sofware...(rolling my eyes)...anyway..screeen is all nice and clear again and YES there is a checkpoint created today in system restore
#104
Posted 28 April 2006 - 07:55 AM
I don't think that one will help...That's your current configuration.
Using the current logons (Users), can you access files and programs?
Using the current logons (Users), can you access files and programs?
#105
Posted 28 April 2006 - 08:01 AM
yes, i got into my documents/my pictures/windows movie maker/power dvd/paint
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users