Build w/no errors, still will not start.

  • Thread starter Thread starter Tony
  • Start date Start date
T

Tony

Background: I have a target with WinXP Pro on the first partition, and
a second partition I'm using to test XPe images. I used TA.exe to get
the device configuration. I already learned the lesson of changing
the directories in Target Device Settings to "D:\..." and the
partition to (2) on that same page. And I have downloaded all of the
relevant patches/updates from the XPe site.

Problem: I built a MinLogon project based on my TA results, resolved
all of the dependencies brought to my attention, and it STILL will not
start up. Immediately after the bios, I get a brief flash of a
progress bar (DOS-like at bottom of screen), then a black window with
an error message of the form...

"A problem has been detected and Windows has been shut down to prevent
damage to your computer."
"If this is the first time you've seen this error screen, restart ..."
"Check for viruses on your computer. Remove any newly installed hard
drives or hard drive controllers. Check your hard drive to make sure
it is properly configured and terminated. Run CHKDSK /F to check for
hard drive corruption, and then restart your computer."
"Technical information:
** STOP: 0x0000007B (0xFE232640, 0C000034, 0x00000000, 0x00000000)"

Does this point to a specific type of problem? I tried all of the
disk drive versions available, so I don't believe that is the issue.
Is there any way I can find more information from this other than "A
problem has been detected..."?

Thanks in advance.

- Tony H.
 
Tony,

7B stems from a missing disk controller component. Try running TAP instead
of TA. You can run tap from XP Pro, Windows 2K, or WinPE. You can boot to
WinPE from the first CD for XPe SP1. All the tools (tap, sdimgr, etc..) are
on the CD located in the XPE folder.

HTH,
--
Brad Combs
Imago Technologies, LLC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Thanks for the all tips on this. Since I posted this, I was able to
use the result of running TAP.exe to create a working image. I
created a component from the TAP file, then made it a Selector type
component because TD wants to throw in the kitchen sink when all the
TAP components are used. So now I just need to find out what I can
leave out and still get what I need from the OS. But it definitely
worked better for me with the TAP results.

On that note, is there a more formal process for doing this? By that
I mean is there a less ad-hoc way to determine what components are
needed to build a system with the features you want? The turn-around
time on my target (dependency check, build, file transfer, FBA, and
reboot) is around 20-55 minutes a pop. At this point, I've spent
about 2 weeks just getting as far as I have and the images we are able
to produce are a long way from where they need to be. Seems like
there should be some kind of "dependecy map" or something like that to
help people out. I would expect the "try things until it works"
philosophy from something like RT Linux, but not from a professional
product like XP Embedded. I don't mean that as an insult, but maybe I
just don't know about all the resources I have yet.

Thanks for any tips you can give me.

- Tony H.
 
There are some tutorials on msdn.microsoft.com/embedded that walk you
through a generally approved methodology of creating an OS. There is a bit
of Art, and a bit of Science when it comes to creating an embedded OS (from
any vendor). In situations where you are incorporing third party (ie: not
from the vendor, such as Microsoft) it's not often immediately apparant what
the third party needs from the operating system. There is a bit of trial
and error (art) and a bit of investigating (science) using tools like
REGSNAP, INCTRL5, etc.

Step 1 (imho) is always: Use TAP, import into CD, use selector prototype,
save SLD, import into CDB
Step 2 (imho) is usually: In TD, add your new hardware macro component and
device template. Prune NOW before checking dependancies.
Step 3 (imho) is generically stated as "choosing the union of components as
determined by your apps/drivers and your hardware".
Step 4 (imho) is tailoring the image for deployment.

Short answer: No. There isn't a 100% bulletproof list of things to do.
Not-so-short answer. Yes. There is a command set of problems to solve
using deterministic methods.
Harsh truth. Sort of. You get better at it through repetition. Exposure
to issues is what makes people able to create images faster than others.

--Gordon Smith (eMVP)
 
I appreciate your advice. Now if I can only convince my supervisor of
this fact so he will get off my back for a bit. :o) I think there was
a pointy-hair-boss-type decision to use XPe for a project with an insanely
tight schedule, and no one really looked into what would be involved.
Thanks for the advice!
- Tony H.
 
Back
Top