Unable to build working reuntime XPe

G

Guest

I just downloaded XPe studio. So far I have been unable to build even one
working runtime!

I have followed the video examples on the website and my builds either bet
the blue sceen of death or hand in an endless cycle of FirstBoot.

The only thing I am doing different is importing a devices.pmq of my system
(tap).

What in the world do I need to do to make usable runtimes?

Thanks,
-Dan
 
K

KM

Dan,

Can you give us more info on the BSOD(s) you saw?
It may appear to be easier to fix those than trying to follow some tutorials.

--
Regards,
KM, BSquare Corp.


PS. If not accident, please do not multiply your same post.
 
G

Guest

Yes, I set the settings for my boot drive; J: ans set the multiboot correctly.

Yes, it is a 7B error...
 
K

KM

Dan,

Verify that you've got proper ARC path in your boot.ini on target.
Also make sure the ARC path points to the right name of the Windows directory you built image for.
 
K

KM

Dan,

The ARC path seems right.
You can try changing disk and rdisk numbers to see if it makes any difference.
But better try disconnecting the primary master driver and leave only your XPe disk (make the partition active and bootable, place
ntldr, ntdetect.com and boot.ini under root of the partition).

Make sure on the XPe partition you have a directory structure like:
\Documents and Settings
\Program files
\Windows

(not something like DriveX\...)

PS. Hope we are discussing the only boot.ini from the system partition.
 
K

KM

Dan,

You've been already given the right links to the 7B tip page.
Just make sure you've got all the critical to boot drivers in your configuration. If you are not sure, add all three the Disk drive
components.
 
G

Guest

So then it is required that the disk be the active boot disk? This may be my
problem..
 
S

Slobodan Brcin \(eMVP\)

Hi Dan,
So then it is required that the disk be the active boot disk? This may be
my
problem..

No it is not required, but you must use valid ARC path (rdisk value). This
value does not depend on master/slave primary/secondary disk configuration
but more how BIOS enumerate disks.
Usually they are given numbers acording to boot order that you specify in
BIOS.

Regards,
Slobodan
PS: We are talking here about the problems realted to no HAL.dll error.
 
G

Guest

Well, I used partiton magic and carved off a gig from then end of my C drive.
The normal os boot partition is rdisk(0)partition(1), So I set XPe for
rdisk(0)parition(2)..

I just did a build on one of the demonstration software
configurations(software/test & development/ WinLogon Sample Macro). I did
not get a BSOD this time, but now its back to the ENDLESS cycle of FIrst
boot agent > reboot
 
G

Guest

Also, this new partition is beyone cylinder 1024.. Partition magic says it
will not be bootable.. Is this true?
 
S

Slobodan Brcin \(eMVP\)

Also, this new partition is beyone cylinder 1024.. Partition magic says it
will not be bootable.. Is this true?

Usualy it can be true, but since your image switched to kernel mode then
this is not problem for you.

Regards,
Slobodan
 
G

Guest

Ok, Let me ask this question..

Am I wrong to select a design template such as INformation Appliance then
add to that my devices (from tap probe of my workstation) then build it;
expecting it to work?
 
G

Guest

Am I wrong to assume that I can get a working build by adding a templated
design like the information appliance then adding the devices imported from a
tap probe of my workstation?


BTW Thank you all for being so helpful!
 
S

Slobodan Brcin \(eMVP\)

Dan,

I do not know about Information Apliance but if you add to empty project
only "MinLogon Sample Macro" and resolve dependencies you should have
bootable image. From that point you can add TAP results and more components
if you like.

Regards,
Slobodan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top