Problem: [n] devices, identical HW, driver loads on some devices andnot others.

  • Thread starter Odd Erling N. Eriksen
  • Start date

O

Odd Erling N. Eriksen

Hi,

I recently ran into a problem which has left me puzzled.

My employer uses a small number of embedded computers for an operation
panel; they are all supposed to be identical, hardware-wise.

On the latest batch delivered from our sub-supplier, the driver for
the (Intel PRO/100VE-based) network adapter fails to load.
Simultaneously, the 'Found new hardware' wizard claims to have
detected a network adapter.

So - I did the obvious (to my mind, anyway) - ran TAP on one of the
units in the latest batch, and compared the resultant PMQ file to one
from an older, fully functioning unit.

The files were identical, save for the entries related to the boot
media and the keyboard attached; in other words, the networking chip
ought to be the same as it has always been. Still, the driver which
worked in the past failed to recognize the adapter.

Now, I thought that as long as the device info was the same, the
device would be the same, and, hence, a driver for any unit with the
same device ID + related info would work just fine across the board.
Obviously, I am mistaken.

Can anybody help shed any light on this issue? I am by no means an
experienced XPe developer, I basically was just given enough time to
get an image up and running on our hardware, not time to become good
at this - and I really hate not understanding what is going on!

As TAP queries the windows registry for info - would booting an image
with the wrong set of drivers for the actual hardware present confuse
it? Clutching at straws here, but, as I said initially - I am quite
puzzled by what I see...

Any advice, suggestions, rants and even flames welcome. :)

Thank you!

-Odd Erling N. Eriksen, Norway
 
Ad

Advertisements

S

Sneyers Jean-Pierre

Hi,

I recently ran into a problem which has left me puzzled.

My employer uses a small number of embedded computers for an operation
panel; they are all supposed to be identical, hardware-wise.

On the latest batch delivered from our sub-supplier, the driver for
the (Intel PRO/100VE-based) network adapter fails to load.
Simultaneously, the 'Found new hardware' wizard claims to have
detected a network adapter.

So - I did the obvious (to my mind, anyway) - ran TAP on one of the
units in the latest batch, and compared the resultant PMQ file to one
from an older, fully functioning unit.

The files were identical, save for the entries related to the boot
media and the keyboard attached; in other words, the networking chip
ought to be the same as it has always been. Still, the driver which
worked in the past failed to recognize the adapter.

Now, I thought that as long as the device info was the same, the
device would be the same, and, hence, a driver for any unit with the
same device ID + related info would work just fine across the board.
Obviously, I am mistaken.

Can anybody help shed any light on this issue? I am by no means an
experienced XPe developer, I basically was just given enough time to
get an image up and running on our hardware, not time to become good
at this - and I really hate not understanding what is going on!

As TAP queries the windows registry for info - would booting an image
with the wrong set of drivers for the actual hardware present confuse
it? Clutching at straws here, but, as I said initially - I am quite
puzzled by what I see...

Any advice, suggestions, rants and even flames welcome. :)

Thank you!

   -Odd Erling N. Eriksen, Norway
Maybe your driver componant for your Intel PRO/100VE-based is not
complet (sub model not in your SLD file). Try to create new SDL for
your driver by importing the inf file.
 

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