Jump to content
Posted 20 December 2009 - 02:10 AM
Posted 20 December 2009 - 05:59 AM
Oh, yes ... that is probably the easiest way to do the job.
Is there a possible way to replace the corrupt system files manually through slave drive to repair the drive and get it working properly without reformatting?
Posted 20 December 2009 - 04:31 PM
Posted 20 December 2009 - 05:14 PM
Posted 20 December 2009 - 05:29 PM
Posted 20 December 2009 - 05:36 PM
That is normal: mup.sys is the last file to load, and that is the normal situation in a fully functioning system.
If this is important, I forgot to post what file computer stopped on during Safe Mode load - File multi(0)disk(o)rdisk(0)partition(1)\WINDOWS\System32\Drivers\Mup.sys
The process creation failure indicated by this error message can only happen during the fairly brief time that the Windows Executive is being initialized, which is during phase 4 of Windows startup. Typically there is a problem with a device driver or with a missing or corrupt system file used during Windows startup.
Posted 20 December 2009 - 05:40 PM
Edited by AustrAlien, 20 December 2009 - 05:42 PM.
Posted 20 December 2009 - 05:50 PM
Posted 20 December 2009 - 06:18 PM
After running Check Disk (chkdsk /r), hopefully you will no longer experience this "System files in Recovery Console said they could not be copied." An off-line system restore stands a good chance of getting your system up and running again, so that will be the next step I suggest that you try. I will stick with using the RC at the moment (instead of using your other Windows system), since the hdd is back in its box. If you experience anything that does not appear to work as it should (according to the instructions), please post about it before attempting to proceed further.
This last try Windows Setup actually continued to Windows XP Professional Setup without blue screening.
Edited by AustrAlien, 20 December 2009 - 06:21 PM.
Posted 20 December 2009 - 06:28 PM
Edited by Magdalena, 20 December 2009 - 06:40 PM.
Posted 20 December 2009 - 06:35 PM
Yes, that is correct: After each command press the <ENTER> key.
Do you press enter after EACH command.
cd windows (enter)
cd system32 (enter)
cd config (enter)
Posted 20 December 2009 - 06:52 PM
Posted 20 December 2009 - 07:36 PM
Very pleased to hear it, thank you Magdalena. Yes, it gets a lot of people out of trouble, without too much fuss.
WOOT! That Recovery Console walk-through worked perfectly!
* chkdsk /r is a easy instruction to provide, and it "sort of" does both the above and below jobs, but it's not quite as good as doing both jobs separately.
Any time that your computer has an "untimely" or "untidy" shut-down .... run a Disk Check.
Start > Run and type in chkdsk /f
(From the Recovery Console, this is chkdsk /p)
Download the diagnostic utility from the hard drive manufacturer's website to create a bootable floppy or CD. Boot with it, and run the short/quick test and then the long/extended test, and check the S.M.A.R.T. status.
Firstly, you need to find the brand name of your hard drive. You will find this info on the label of the hard drive (most likely you will have to remove the hard drive from the box to read the label). You will also find sufficient info to identify the drive (the model number) by looking in the BIOS Setup Menu. Another alternative is to use something like Everest or Belarc Advisor.
EVEREST Free Edition 2.20
Belarc Advisor - Free Personal PC Audit (Version 8.1b)
Hard Drive Diagnostics Tools and Utilities
Edited by AustrAlien, 20 December 2009 - 07:44 PM.
0 members, 0 guests, 0 anonymous users