ITOX

[Pascal Bouchard]

I'm currently trying to get a ITOX motherboard with Intel chipset to run
XPE; prior to do this, i must run TAP or TA; under WINPE, when i run TAP,
the program finds nothing.... here's the content of devices.pmq file :

<?xml version="1.0"?>
<!DOCTYPE HIB SYSTEM "devices.dtd">
<!-- -->
<!-- -->
<HIB>
<TOOLINFO>
<PLATFORM>Microsoft Windows XP Build 2600</PLATFORM>
<TOOL>Target Analyzer Probe Version 2.00.807.0</TOOL>
<TOOLOPTIONS>tap </TOOLOPTIONS>

If i try to run TA from WINPE, ta freezes.

Under DOS, i'm able to run TA to get the devices; is there a reason for TAP
not to return anything ?

 

[KM]

Pascal,

Wierd behaviour of TAP. I've never seen or heard of such bug of the tool.
Considering that TAP does only registry enumeration to gather the PnP information and then outputs it to PMQ file, I can't find a
good explanation. However, you can run regedit on WinPE and export the Enum branch to see if anything suspicious is there where TAP
can stumble upon.

In any case, please submit a bug directly to the Product Team:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx.

Don't run TA under Win32 OS - it is 16bit DOS app and won't run there.

KM

PS. Just to check.. You run TAP on a non-read-only media, right? So that it could write the PMQ file without problems?

 

[Slobodan Brcin \(eMVP\)]

PS. Just to check.. You run TAP on a non-read-only media, right? So that

it could write the PMQ file without problems?

This is the only valid reason why it would not work.
Try writing something to volume from which you run TAP.
Then change to USB key (for instance) and run TAP from there.


Regards,
Slobodan

 

[Pascal Bouchard]

I boot PXE-WINPE and run TAP from a network drive; this drive can be
written; i do exactly the same with 5 other kind of machines.

 

[KM]

Pascal,

I boot PXE-WINPE and run TAP from a network drive; this drive can be written;

I've had problems with TAP output on a network drive but I hope you set the server share permissions read/write accessable for the
user you are logging under for the "net share" command. Or, better, just make it temporarily available for Everyone (Read/Write).

And, certainly, try with local storages like Usb or etc.

i do exactly the same with 5 other kind of machines.

And? Does the problem show up on all of them or just one of them?

 

[Pascal Bouchard]

I finally found the problem; some dlls were missing; the reason is quite
simple : i created a new winpe image using OPK, added some drivers, but
didn't copy some dlls neither register those.

It works now.

Thank you all anyway.