boot problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am getting the message
"load needed dlls for kernel"
I copyied the xpe entire image form my hard drive
onto a compact flash disk, with enough space to hold all of the files
the installed the compact flash into the target system (it has a bootable
compact flash socket), then copyied the whole compact flash drive
to my c drive, i am booting on the c drive, not the compactflash, which is
drive
e. I seem to be loading ( i get the prgress bar), but it stops part of the
way into the load. I then copyied hal.dll and ntoskrnl.exe form the xpe
distribution
cd-rom, this did not work either. am i missing some file?
 
Robert,

Some things to check:

At the very highest node of your configuration, (Click on the top line
in the center window),
check the 'Build Type', it should always be release...

Make sure you also copied hidden and readonly files.
I use XCOPY /E /H /R /K *.* to copy files

Assuming you have been able to run Target Analyzer, and import the
resulting Devices.pmq file into Target designer, look at this MSDN
Article, particularly 'Step 3 Create a New Configuration':
http://msdn.microsoft.com/library/d...tbstutorialbuildingdeployingrun-timeimage.asp

It lists the additional components that you must add to the imported
stuff to make a working configuration. This includes, if i recall:

1) The imported list of devices from TA.exe or TAP.exe
2) A filesystem Driver (NTFS)
3) A boot loader (NT Loader or EWF NT Loader)
4) the 'User Interface Core' component
Note: If you want a regular windows-like behavior, you need to check
the settings in the component "user interface core', particularly 'Show
context Menu' entries. These enable the right click menus. Also 'Show
Run on the Start Menu' is very useful, as you can run all kinds of
things this way...

5) A 'logon' component: MinLogon or "Windows Logon"
6) A shell, either 'Explorer shell' 'Command Shell', or a custom shell
(worry about that later)
7) A language support component (i.e. English Language Support)

Then, resolve dependencies in target explorer, build, and copy to your
target



If all that's OK, look for a file on your target drive,
C:\Windows\FBA\FBALog.txt, to see if there are any error messages
there. (I am not really sure if you got far enough before it crashed
that this file will even be present...)
 
Back
Top