Hi KM,
The post-FBA image show the BSOD only when booted via CD.
If I boot from the hard disk any attempt to access to the file system will
give error.
I have added the /SOS parameter to the boot.ini of the post FBA image, I see
that the system dll and devices are loaded without problems, the last one is
the disk.sys device driver after that a blue windows with the system
information start but I have immediately a BSOD.
The FBALOG.txt is too big, I have showed only the last information logged.
Tuesday, November 21, 2006
7:16:23 AM - [FBASetProgressText] Setting PNP Flag...
7:16:30 AM - [FBASetProgressText] Initializing...
7:16:30 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll,
FBAInitialize
7:16:30 AM - [FBASetProgressText] Setting SystemPrefix...
7:16:31 AM - [FBASetProductKey] Evaluation product key
7:16:31 AM - [FBASetProgressText] Initializing User Profiles...
7:16:31 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll, FBAStep1
7:16:31 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll,
FBASetSetupInfo
7:16:31 AM - [FBASetProgressText] Installing System Security...
7:16:40 AM - [FBAInstallSecurity] Successfully set security!
7:16:40 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbasec.dll,
FBAInstallSecurityPhase1
.............................
7:20:45 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll,
FBALaunchOCM
7:20:45 AM - [FBASetProgressText] Installing Components...
7:20:48 AM - [FBALaunch] C:\WINDOWS\system32\regsvr32.exe /s /i
C:\WINDOWS\system32\swprv.dll (ExitCode: 0x0)
7:20:48 AM - [FBALaunch] C:\WINDOWS\system32\regsvr32.exe /s /i
C:\WINDOWS\system32\eventcls.dll (ExitCode: 0x0)
7:20:48 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbareg.dll,
FBAMigrateRegistryKeys
7:20:48 AM - [FBAChangeDisplaySettings] Settings: [800, 600, 32, 60]
7:20:48 AM - [FBAChangeDisplaySettings] Settings not found!
7:20:48 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll,
FBAChangeDisplaySettings
7:20:48 AM - [FBAChangeDisplaySettings] Settings: [800, 600, 32, 60]
7:20:48 AM - [FBAChangeDisplaySettings] Settings not found!
7:20:48 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll,
FBAChangeDisplaySettings
7:20:48 AM - [FBASetProgressText] Resetting Setup Flag...
7:20:49 AM - [FBARemoveRestart] Updated BootExecute!
7:20:49 AM - [CallEntryPointThread] C:\WINDOWS\FBA\fbalib.dll,
FBAResetSetup
7:20:49 AM - [FBASetProgressText] Replacing System Hives...
7:20:52 AM - [FBAFlushFilesToDisk] FlushFileBuffers(C:\) succeeded!
7:20:52 AM - [FBASetProgressText] Resetting Setup Flag...
7:20:52 AM - [FBASetProgressText] Replacing System Hives...
7:20:55 AM - [FBACleanupRegistry] No *.SAV hives!
7:20:55 AM - [FBAFlushFilesToDisk] FlushFileBuffers(C:\) succeeded!
7:20:55 AM - [FBADoReboot] Sleeping...
7:21:05 AM - [FBADoReboot] Exiting process...
7:21:31 AM - ConfigureEwf() Start.
7:21:32 AM - Getting EWF config parameters from registry.
7:21:32 AM - EWF Partition Size = 0 (KBytes), Levels = 1, Volumes = 1.
7:21:32 AM - Protected Volume Config #0 :
7:21:32 AM - Disk= 0,Part= 1,DiskType= IDE,Type= RAM.
7:21:32 AM - Enable= Disabled, Optimize= 0, LazyWrite= N.
7:21:32 AM - Found 2 Hard Disks.
7:21:32 AM - Searching for El Torito disk.
7:21:32 AM - Disk0 signature = 0x65BA7007.
7:21:33 AM - Disk1 signature = 0x4F544C45.
7:21:33 AM - Disk1 is an ElTorito disk.
7:21:33 AM - Checking Start value in
System\CurrentControlSet\Services\redbook key.
7:21:33 AM - Resetting Start value.
7:21:34 AM - Checking Start value in
System\CurrentControlSet\Services\Imapi key.
7:21:34 AM - Disk #0 layout info:
7:21:34 AM - PRIMARY partition,start=0x0000000000007e00,
len=0x0000000025421a00, type= 11
7:21:34 AM - FREE partition,start=0x0000000025429800,
len=0x000000049ffd5e00, type= 0
7:21:34 AM - Allocating EWF in PRIMARY partition,
start=0x0000000025429800, len=0x000000000000fc00.
7:21:34 AM - Created EWF partition on Disk = 0, partition = 2,size =
0x000000000000fc00 .
7:21:34 AM - Saving EWF configuration to registry:
7:21:34 AM - Protected Volume ArcName = multi(0)disk(0)rdisk(0)partition(1).
7:21:34 AM - ewfOpen.
7:21:34 AM - EWF Volume Config on Disk#0, Partition#2:
7:21:34 AM - Segments = 0, Max Volumes = 1, Max Levels = 1
7:21:34 AM - ewfAdd.
7:21:34 AM - Protected Volume Config on Disk0\Partition1 :
7:21:34 AM - Type = RAM, State= DISABLED.
7:21:34 AM - ewfClose
7:21:34 AM - ConfigureEwf() End, status = 0x0.
7:21:34 AM - [CallEntryPointThread] C:\WINDOWS\system32\ewfdll.dll,
ConfigureEwf
7:21:34 AM - [FBASetProgressText] Resetting Setup Flag...
7:21:36 AM - [FBADoReboot] Sleeping...
7:21:47 AM - [FBADoReboot] Rebooting system.
KM said:
Robin,
I see.
Does the post-FBA image show the BSOD only when booted via CD? When happens if you boot it from the same hard disk you ran FBA
on?
If you add /SOS switch to your boot.ini of the post-FBA image you may be able to see where it is failing.
Make sure that you ran FBA on that target device with an El-Torito CD in the CD drive.
Make sure EWF is ON when you capture the post-FBA image.
Manually go [offline] to [HKLM\System\MountedDevices] key and clean up the content of the key.
Also, can you show us your FBALog.txt?
--
=========
Regards,
KM
Robin said:
Hi KM,
Thanks for your reply, I have used the Tap.exe utility to gather all the
necessary components. But what is very strange for me is that I'm able to run
the Pre FBA image without error and I have the Blue Screen only when I start
the Post FBA image.
:
http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx
--
=========
Regards,
KM
Does anybody help me?
I need to create a bootable CD-Rom for three PC with different motherboard.
I have created with success the bootable CD for two of them but I have the
following problem on the PC with motherboard:
MB GA-6VTXE-A (PC WIDE 566 & 866)
BIOS ver. F7, F8, F9
I have created with success a pre FBA run time Image.
The run-time image boot with success and the FBA phase complete without
problem.
The EWF is configured to protect c:.
The etprep /all command will delete the EWF volume and configure the
run-time image to boot from the CD-ROM drive.
The Post-FBA CD-ROM start but a Blue screen was shown with Error Message
STOP:0xx0000007B immediately after the white bar moves across the bottom of
the screen.
