Re: Bootfiles suddenly missing (NTLDR,...); CONVERT don't work
From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 08/26/04
- Next message: Dwayne: "Record startup/shutdown times"
- Previous message: Yaron Maor: "Re: Set temp path by Policy"
- In reply to: XPEApplicator_at_BE: "RE: Bootfiles suddenly missing (NTLDR,...); CONVERT don't work"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 16:56:19 +0200
Hi,
This message is included in Partition boot record and not in MBR.
ntldr is always read from original partition since ewf_ntldr is the first program that start using overlay data for loading other
programs.
So if something happened as you describe then this means that disk overlay was committed or failed to protect your system partition.
Best regards,
Slobodan
"XPEApplicator@BE" <XPEApplicatorBE@discussions.microsoft.com> wrote in message
news:3D3E683A-A8E8-45DF-AEEC-37F82B48BFCC@microsoft.com...
> OK, in some cases it's impossible to restore a EWF-level (how to do if NTLDR
> is missing...that's right).
> Missing NTLDR ist reported - of course - before XPe starts(I thinks this
> message is included in the MBR). Besides, it doesn't hardly mean that files
> are really missing - they also may be corrupted (-> ??? missing or
> corrupted). I've already seen a BOOT.INI that contained absurdly ASCII-chars.
>
> Why may this file disappear?? And, where are they missing? Is it possible
> that NTLDR, NTDETECT.COM,... are loaded from the EWF-overlay instead of the
> 1. (protected) partition??
>
> On the system runs a VB-app and WAR-FTP.
> However, there are several errors that raise after some time. Restore-able
> errors, for example - are 0x0000007B or 0x0000007A. After restoring via EWF
> system is running for a while again.
> Is it possible that this occours because XPe is installed on a
> FAT32-partition? Are there any knowns problems on EWF and FAT32?? I have a
> thin assumption...
>
> Besides: Since I assume that this problem was dependiung on the FAT32 I
> tried to convert it to NTFS via "CONVERT C: /FS:NTFS /X" - sheduled for next
> boot.
> After the message "Conversion complete" the system hangs (I know that it
> should be rebooted automatically).
> I've tried the same with an older image, it worked. Now - since the new
> image has only some QFEs more than the ole one - I assume that CONVERT's
> malfunction ist caused by any of the QFE's. Does anyone know something about
> this??
>
> BR XPEApplicator@BE
>
>
>
> "XPEApplicator@BE" wrote:
>
> > Hello,
> >
> > I have a problem with XPe-image and I don't have any idea what's behind it.
> >
> > About the image
> > "I've build a image to a 4GB partition (FAT32, later NTFS) with EWF,
> > installed apps and additional drivers and commited all of them to the
> > protected volume. After ensuring that disk doesn't have any bad sectors I've
> > runt fbreseal.exe and cloned it with ghost. Applied to the new target,
> > fbreseal runs, creates the overlay (disk) and system is running fine."
> >
> > After some time (colorable) the target doesn't boot through any more and
> > stops with messages like "NTLDR is missing" or similar. Only a EWF-restore
> > makes system running again.
> >
> > I've runt a test but with many tousands restarts but didn't got such errors.
> > The only idea I have was that the target was powered off before it was
> > completely shut down, but that isn't the problem.
> >
> > What else could the matter that this files suddenly disappear??
> >
> > Best regards
> > XPEApplicator@BE
- Next message: Dwayne: "Record startup/shutdown times"
- Previous message: Yaron Maor: "Re: Set temp path by Policy"
- In reply to: XPEApplicator_at_BE: "RE: Bootfiles suddenly missing (NTLDR,...); CONVERT don't work"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
