Obscure error messages during PMQ import

  • Thread starter Thread starter Michael Bate
  • Start date Start date
M

Michael Bate

Does anyone know what these messages are referring to?

The first appears to have something to do with video (I assume because
it contains "Vid_"). The second appears to be about the main hard drive
(this device contains an IDE compact flash - no hard drive).

When I attempt FBA for this device, I get BSOD 7B. Someone referred to
a list of "hints" about this, but I am not sure where to find this list.

I have successfully build XPE images for other single board computers.

Thanks in advance.

Here are the messages:

Warning:Could not find a driver for Hardware Device:
HID\Vid_05a4&Pid_9860&Rev_0110&MI_01&Col01
(HID\Vid_05a4&Pid_9860&Rev_0110&MI_01&Col01).

Warning:Could not find a driver for Hardware Device: STORAGE\Volume
(STORAGE\Volume).

- Michael Bate
 
Bing,

Thank you for your reply.

Yes I do have USB devices - not sure how to proceed without them:

- USB keyboard
- USB mouse
- USB CDROM drive (to boot WINPE from)

I suppose that I could get an IDE CDROM and connect a PS2 keyboard
(mouse is not needed for WINPE, as far as I can tell).

Do you think that these USB devices are causing these messages and, more
critically, that I will then be able to get past the BSOD (error 7B) on
startup of FBA?

The BSOD appears shortly after the Windows logo is displayed. For a
second or two the subsequent screen appears and announces the Windows
version and the amount of RAM. Then another message appears but so
quickly that it cannot be read, immediately followed by BSOD. I have
edited boot.ini to add the bootlog, basevideo, sos, and safemode:minimal
options. No boot log is actually written, nor are FBA logs. No files
are changed or added to the boot CF.

The PCM-3370 comes from Advantech. Can Advantech provide any assistance
on this? If we purchased Advantech's generic WINXPE license and ran TAP
from there, would be have more success. I am told that TAP is limited
under WINPE, but cannot find information on how it is limited.

Also supposedly there is a "hints" article somewhere that addresses BSOD
on FBA. I have searched MSDN and have not found it.

Thanks again,
Michael Bate
 
I was able to solve the problem caused by these error message by taking
an entirely different approach to building the OS - essentially taking
a .SLX file for a different platform (that had been saved BEFORE Check
Dependencies) and substituting the SLD from my new TAP for the similar
SLD for the old platform, then running Check Dependencies and Build - it
worked!
 
Back
Top