ANOTHER LAP TOP WON'T BOOT

  Rodney-211388 13:32 27 Dec 07
Locked

Aged and much travelled son's Toshiba Satellite Pro A10 with XP Pro.

On powering, goes straight to screen that begins 'We apologise for the inconvenience, but Windows did not start sucessfully etc etc. At the bottom is countdown until Windows starts normally but that is frozen.

If press F8 during the breif boot up, screen provides other start up options but nothing much happens except getting a list of six files all of which begin Multi0disk0rdisk0partition(1)\Windows system 32\

the extensions are then:
ntoskml.exe
hal.dll
KDCOM.DLL
config\system
config\system.log

At that point everything is frozen.

Fan runs OK but no beeps on start up.

Any ideas please?

  jack 13:49 27 Dec 07

What sort of XP discs do you have?
Original full?
System repair restore?

  Rodney-211388 14:43 27 Dec 07

no discs survive for this particular machine

  Rodney-211388 15:25 27 Dec 07

On further examination, I think it is likely that the HDD has failed.

  Fruit Bat /\0/\ 17:37 27 Dec 07

1. Boot the Recovery Console from a Windows XP installation CD, Lnux CD BartPE CD (this months cover DVD) or NTFS4DOS floppy

2. When you're at the Recovery Console command prompt, change into the root directory of the system drive with the cd command (i.e., cd \).

3. Change into the System Volume Information directory by typing cd system~1 on most machines, or cd "System Volume Information."

(The filenames with ~1 are generated by default to provide backwards compatibility with programs that only recognize 8.3-format filenames. It's possible to disable 8.3 filename generation on NTFS volumes to gain some speed, but the speed gained by doing this is generally pretty small and it can have the unintended consequence of making it impossible to use 8.3 filenames in contexts like this. If you can't use 8.3 filenames to navigate, 8.3 name generation might be disabled. See Microsoft's support document called How to Disable the 8.3 Name Creation on NTFS Partitions.

4. The System Volume Information directory contains a folder name _restore followed by a GUID in curly braces. Change into it by typing cd _resto~1; if that doesn't work you'll have to type cd "_restore{GUID_STRING}", with the full GUID string in place of GUID_STRING.

5. In the _restore directory are a group of subdirectories starting with the letters RP and followed by a number. These are the different restore points available for that volume.

6. Check the date on each directory and look for one that corresponds to a date before you began experiencing problems.

7. Change into the appropriate directory. If the directory is named RP74, for instance, change into it by typing RP74.

8. Inside that directory will be a subdirectory named snapshot; change into that directory as well (cd snapshot)

9. The snapshot directory holds backup copies of the SOFTWARE and SYSTEM Registry hives, named _REGISTRY_MACHINE_SOFTWARE and _REGISTRY_MACHINE_SYSTEM, respectively.

10. The target directory for these files is \Windows\System32\Config, and the hives there are named SOFTWARE and SYSTEM. Rather than overwrite those files entirely, you can rename them to something else. Typing ren \windows\system32\config\software \windows\system32\config\software.bak and ren \windows\system32\config\system \windows\system32\config\system.bak will rename them to software.bak and system.bak, respectively.

11. Copy in the backup hives: copy _REGISTRY_MACHINE_SOFTWARE \windows\system32\config\software and copy _REGISTRY_MACHINE_SYSTEM \windows\system32\config\system.

This thread is now locked and can not be replied to.

Nintendo Switch review: Hands-on with the intuitive modular console and its disappointing games…

1995-2015: How technology has changed the world in 20 years

Prehistoric Britain is laid out in these Royal Mail stamp illustrations

Best running headphones | Best sport & fitness headphones: 4 brilliant pairs of wireless…