Re: unable to boot laptop


"Terry" <ryedavey@xxxxxxxxxxxx> wrote in message
news:%23tS3a0JkJHA.6124@xxxxxxxxxxxxxxxxxxxxxxx
Well first of all I would like to thank everyone for their time , effort
and patience . You have all been very helpful and I know it can't be easy
dealing with an amateur on a long distance basis .
I feel we gave it a real good effort but as you say it's time to save as
much data as I can and reinstall windows.
I did try the procedure again as Pegasus suggested paying attention to the
dates .
Using the repair console I deleted all 5 of system32\config files (system,
sam, etc) and copied the files from the repair disk, after which I checked
the dates .... default was 6/10/03, the other 4 were 12/26/03 ... rebooted
to the usual autochk problem then went back in to check the dates again .
Default was still 6/10/03 but the other 4 had changed to 02/12/09 .
I then deleted the files again and copied the files I saved from the
restore point .. all files were dated 01/30/09 ... rebooted and checked
them again ... default was still 01/30/09 but the rest were 02/12/09 .
Using the repair disk it doesn't seem to recognize the command "date" or
"time" which is the only way I know to check the processor clock . So I
created a new directory and when I checked it said it was created 02/12/09
10:04pm .. about an hour later I created another and guess what ... that's
right ...it said it was created 02/12/09 10:04pm .
I believe this laptop is possessed and needs to be put out of its misery ,
perhaps an exorcism will help !
Thanks again
Terry

Your most recent tests prove that your problem is not caused by a corrupted
registry. If it was then using the registry files from December 2003 would
have allowed you to boot up.

The date issue concerns me for two reasons:
- After you rebooted with the restored registry, the file date was 12
February, in spite of today's date being 17 February.
- When you created a test folder while in the Recovery Console (good idea!),
the computer time did not change. It should have - I tested it myself a
moment ago. This makes me wonder if you're dealing with a hardware problem.

I think you need to pull the plug and reload Windows onto a freshly
formatted disk. If you have a hardware problem then it will quickly become
apparent. I'd like to hear about the end result.

If you have the time and interest then I suggest that you create yourself a
tool that lets you deal with such situations more easily than the very basic
and very primitive Recovery Console. I'm thinking of a Bart PE boot CD. This
is a terrific tool that gives you the following facilities, even when you
can no longer start Windows:
- Full access to all files and folders on your hard disk.
- Access to external USB flash disks (great for copying otherwise
inaccessible files!)
- Full set of commands such as date, time, notepad etc. etc.
- Ability to perform the manual "System Restore" function.
- Boots much faster than the Recovery Console.
- Access to virus scanners
- Networking (depends on your network adapter)


.

Relevant Pages

  • Re: finding fail-safe default for XP laptop
    ... To salvage your files you will have to remove the disk from the laptop and then mount it to another computer. ... Using the Recovery Console is usually quite safe, you won't be installing it on the drive, you will only be booting to it with the Windows XP CD. ... Keep in mind that there is *always* a risk of data loss when you run chkdsk, this is true even if you have no perceived problems with the Windows installation. ... As I said earlier, you don't need to install the Recovery Console and you wouldn't want to even try to install it on a bad disk or while attempting to repair a broken Windows installation, you just want to run it from the Windows XP CD. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: finding fail-safe default for XP laptop
    ... To salvage your files you will have to remove the disk from the ... Using the Recovery Console is usually quite safe, ... chkdsk, this is true even if you have no perceived problems with the ... Windows installation. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: CHKDSK at startup / Win2K
    ... and rename all copies of AUTOCHK and CHKDSK ... To start the Recovery Console, start the computer from the Windows 2000 ... and fixmbr for limited disk repairs. ...
    (microsoft.public.win2000.general)
  • Re: finding fail-safe default for XP laptop
    ... To salvage your files you will have to remove the disk from the laptop and then mount it to another computer. ... Using the Recovery Console is usually quite safe, you won't be installing it on the drive, you will only be booting to it with the Windows XP CD. ... Keep in mind that there is *always* a risk of data loss when you run chkdsk, this is true even if you have no perceived problems with the Windows installation. ... As I said earlier, you don't need to install the Recovery Console and you wouldn't want to even try to install it on a bad disk or while attempting to repair a broken Windows installation, you just want to run it from the Windows XP CD. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: finding fail-safe default for XP laptop
    ... You should only attempt to repair the disk or file ... To salvage your files you will have to remove the disk from the ... Using the Recovery Console is usually quite safe, ... Windows installation. ...
    (microsoft.public.windowsxp.setup_deployment)