Re: Sussed! (*Hopefully*!!!) - Re: Techie help required pls

"Old Grizzly" <me@xxxxxxxxxxx> wrote in message
news:40gnhaF19aariU1@xxxxxxxxxxxxxxxxx
> "Old Grizzly" <me@xxxxxxxxxxx> wrote in message
> news:40fsm6F1adnbgU1@xxxxxxxxxxxxxxxxx
>> "Old Grizzly" <me@xxxxxxxxxxx> wrote in message
>> news:40fgt5F19rajjU1@xxxxxxxxxxxxxxxxx
>> <snip>
>>>
>>> Ok just changed it to A in FDISK and PTEDIT confirms this
>>> with Hex 80

Nice one.
:-)

So *now* you should no longer get that
"DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"
Error Message...

>>>> Then try doing a ReBoot
>>>> (& maybe another FIXMBR &/or a FIXBOOT, from within the
>>>> Recovery Console - though you may find you need one & not
>>>> the other.
>>>
>>> A reboot gives *NTLDR IS MISSING*

Ah, yes...
That's the *next* stage of the Boot Process...

But don't worry *too* much about that, it's relatively easy to sort
that out!
:-)

Look up on the M$KB - micro$oft Knowledge Base (or elsewhere on the Web)
for plenty of Info about the "NTLDR is Missing" Error Message - that's
actually quite common, when any Boot or Partition probs happen.

>>>... so will try FIXBOOT

Actually I don't think the FIXBOOT Command is the best way to sort
out the "NTLDR is Missing" Error...

Have a look at some of these Articles...

Repairing Damaged MBRs and Boot Sectors in x86-based Computers
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_evwd.asp

Windows XP Resource Kit: Troubleshooting the Startup Process
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c29621675.mspx

Using Recovery Console to Recover from Startup Problems
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prmb_tol_zldj.asp

The computer does not start after you change the active partition
by using the Disk Management tool
http://support.microsoft.com/?kbid=315261

>>> FIXBOOT done but a reboot still gives *NTLDR MISSING press any key
>>> to start*

See above!
:-)

>>> will try FIXMBR

Nope, that only Re-Instates the MBR (Master Boot Record) & you've got
past that prob.

If it says "NTLDR is Missing", then that actually proves that
the Master Boot Record is OK!
:-)
It's actually a *good* Error to get!
:-)

>>> Tried that and it didnt work, research tells me i need to put
>>> a SYS on the h/drive with the SYS C command after booting into
>>> a XP PRO environment

Well, normally, you only need to do a "SYS C:" on it, if it's going
to be Booting into W98 (or similar), not WinXP.

>> Fixed the NTLDR Missing problem and now getting HAL.DLL missing
>> from system32 folder

Ah...

The "HAL.DLL is Missing or Corrupt" means that NTLDR (& also
NTDETECT.COM) are both OK, but it can be caused by several things...

If the BOOT.INI File is pointing to an Invalid (or non-existent)
Path to the windoze Folder, then that can cause it to not find HAL.DLL

Also if there isn't any BOOT.INI File at all, then windoze will use
the *Default* path to the windoze Folder & assume that HAL.DLL is in
the System32 Folder within that.

Remember - When*ever* windoze says anything about a File being "Missing"
you need to interpret that carefully!...
It may not *really* be Missing at all!!!
It just may be in a different place to where windoze is looking for it!
:-)

So, you either have to put it into the place where windoze expects
it to be (if it really *is* actually Missing) *or* you might need to
tell windoze where it should be looking!!!
(by Editing something like the BOOT.INI File)

>>... put the file on a floppy to copy as required but cant find
>> (even with removing attributes) a system32 folder on the drive
>> to put it in.

Oh dear!!!
Now that *is* sounding like bad news!
:-(

What did you use to look for it?
Ordinary MSDOS DIR (Directory Listing) & CD (Change Current Directory)
Commands?
Or the equivalent Recovery Console Commands?

Don't forget, since it's a FAT32 Partition, you can use also use
MSDOS (when Booted from a Floppy or w9x install CD) to look at it...
DIR /a/v (that's Adding the "All" & "Verbose" Switches) can Help

But in the Recovery Console, the DIR Command List all Files (including
Hidden & System Files) anyway.

Now, if you're using the Recovery Console, is it asking you which
Operating System Installation you want to "Log on to"?

& are you asked to enter a PassWord for it?

If *not* 9& it is just Booting straight into the Recovery Console,
with no Prompt to Log on or Prompt for Password etc,) then that means
that it can't actually *find* the existing Operating System!
:-(

& that's also bad news.
:-(

Anyway, do a DIR & see what Folders are in the *Root* of the Drive.
Remember, when you Boot up into (& Log into) the Recovery Console,
the Directory (Folder) that you're in is the System32 Folder anyway!

If you aren't in that Directory, (&/or can't get to it by Navigating
to it, from the Root, through the windoze Folder)/Directory then
there's a big prob, which will need to be sorted out.

>> So....... tried BOOTCFG /SCAN to find available operating systems
>> but that was not successfull

Doh!
So, now that you've got around the *initial* prob of the Invalid
System Disk (& then the subsequent "NTLDR is Missing", then that
means that the "HAL.DLL is Missing" Error is cos it can't actually
find the windoze\System32 Folder!!!
:-(

>... and as it suggests CHKDSK /R thats what i am doing. It has till
> the end of the day then its reinstall..........

Well, you'll just go round in circles, following those Error Messages!

But you do really need to have a look at the Disk & see what's
actually on it. (& where)

Yes, that can be a bit awkward, when you only have the Recovery Console
to look at it with (& no nice windoze GUI (Graphical User Interface)
with windoze Explorer etc!

But first, just do a DIR in the Recovery Console, to List all the
Files & Folders in the Root of the Disk.

Then, when we know what is in the Root, we can Start looking in some
of the likely sounding Folders (Directories) for the windoze stuff!

>> Len aka Old Grizzly looking at Primes Poota dying hours methinks :-(

Well, not the whole PC!
At least it's just the Hard Disk - but yes, basically, the Hard Disk
(or what's on it) *is* the PC, to a large extent!

> So! i have had to remove that drive and i have reinstalled XP on
> a new drive (leaving the horror to one side) so i am beginning
> to load Word and things

Which is a right old Faff, isn't it?
:-(

> that i need to get on with Xmas jobs LOL and hopefully stop my head
> spinning
> ;-)

OK - Leave the other (screwed up) Hard Disk for the mo & we can get
back to look at that sometime - p'raps after Xmas?

You can always just Bung it into the PC & look at it from the other
Installation, (& hopefully get it sussed out & sorted OK) now you have
another Installation of WinXP.

(Incidentally, that's yet another good reason why I (& others)
always recommend having more than just one Partition on *any* Hard
Disk...
That way, you get a "2nd Chance", whenever you have any probs like
that.
:-)

--
pmj


.

Relevant Pages

  • Re: Messed up editing registry, need previous values
    ... How to recover from a borked registry: ... Console and System Restore. ... temporary folder, back up the existing registry files ... to start the Recovery Console. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Text of KB Article Included - From error to missing system file
    ... This article describes how to recover a Windows XP system that does not start because of corruption in the registry. ... If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives. ... In part one, you start the Recovery Console, create a temporary folder, back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. ...
    (microsoft.public.windowsxp.general)
  • Re: Recovering W2K via the repair folder
    ... previous Registry) IF you're FAT32 OR have a DOS startup disk with NTFS ... after which you can do a normal ERDNT restore. ... inside your Windows or Winnt folder, you can restore at a Recovery Console ... Here's a bit more info about the Recovery Console approach using Erdnt: ...
    (microsoft.public.win2000.general)
  • Re: An Excellent XP Recovery Guide
    ... If you're using Windows XP, ... I'm going to show you how to bring your computer back to life, and restore ... and you'll see the ominous Recovery Console. ... Make sure to change C:\Windows to the appropriate windows folder if it's at ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Last known good configuration
    ... >> from registry problems in Windows XP Home Editon? ... and you'll load the Recovery Console ... > appropriate windows folder if it's at a different location. ... Type the whole command in one line, ...
    (microsoft.public.windowsxp.perform_maintain)