troubles getign hardware to work

[Gareth Pye]

i'm trying to get a usb modem from netcomm to work with xpe, and i'm
having some trouble with getting it working fully

I've componetalised the driver for it many times following the
instructions at
http://www.microsoft.com/windows/embedded/community/tips/xp/thirdparty.asp
as i have for a few other pieces of hardware.

It all seams to work properly with no errors anywhere, (during
componentialisation or fba etc) but the fba log shows a
FBAInstallNullDriver message todo with the modem and while it shows up
as working in device manager it says that it has no driver installed
for it.

I've also noticed that the entry in component database manager under
the component tab for this driver claims that the package has 0
components.

Where have i gone wrong this time?

 

[KM]

Gareth,

Wondering if you have added "Null Device Driver" component
(Software:System:Other)?

Also, you may want to use Regmon/FileMon from www.sysinternals.com to figure
out what's missing from your image to get the driver running properly.

I did not quite get your message about the Component Database Manager
showing 0 components for "driver". What driver did you mean? You own? Then
you should check your driver component SLD file - it might not get imported
correctly.

KM

GP> i'm trying to get a usb modem from netcomm to work with xpe, and i'm
GP> having some trouble with getting it working fully

GP> I've componetalised the driver for it many times following the
GP> instructions at
GP> http://www.microsoft.com/windows/embedded/community/tips/xp/
GP> thirdparty.asp as i have for a few other pieces of hardware.

GP> It all seams to work properly with no errors anywhere, (during
GP> componentialisation or fba etc) but the fba log shows a
GP> FBAInstallNullDriver message todo with the modem and while it shows
GP> up as working in device manager it says that it has no driver
GP> installed for it.

GP> I've also noticed that the entry in component database manager under
GP> the component tab for this driver claims that the package has 0
GP> components.

GP> Where have i gone wrong this time?

 

[Gareth Pye]

Gareth,

Wondering if you have added "Null Device Driver" component
(Software:System:Other)?

no i haven't added the null device driver (at least it doesn't show in
the list of added components)

Also, you may want to use Regmon/FileMon from www.sysinternals.com to figure
out what's missing from your image to get the driver running properly.

I thourght that if the install instructions for a device were extract
..zip then point windows to that folder, then correctly giving
component designer the .inf was all that was needed to create the
component (assuming no errors)

I did not quite get your message about the Component Database Manager
showing 0 components for "driver". What driver did you mean? You own? Then
you should check your driver component SLD file - it might not get imported
correctly.

in the bit of Component Database Manager where you can see which
components are asociated with each package there is no component
asociated with the package for this driver, where there are components
asociated with packages i've made for other devices.

 

[KM]

Please see comments inline...


GP> no i haven't added the null device driver (at least it doesn't show
GP> in the list of added components)

As far as I remember the "Null Device Driver" component has visibility level
200. To see the component make sure your TD minimum visibility set to less
or equal 200.

GP> I thourght that if the install instructions for a device were
GP> extract .zip then point windows to that folder, then correctly
GP> giving component designer the .inf was all that was needed to create
GP> the component (assuming no errors)

It depends on the driver implementation. The driver might have been
developed for XP Pro only and the driver creator might have assumed some
system components are in OS by default. An XPe image, as you know, does not
necessarily have all the XP Pro components so even if the driver
installation was smooth the drvier (or app) may not work properly. That is
why pretty much all the XPe components (MS or non-MS) have to be tested
badly.

GP> in the bit of Component Database Manager where you can see which
GP> components are asociated with each package there is no component
GP> asociated with the package for this driver, where there are
GP> components asociated with packages i've made for other devices.

When you import your .inf in CD, and save the result .SLD, do you see
component there?
And again, lower you visibility level (it will apply to all XPe Tools).

GP>>> i'm trying to get a usb modem from netcomm to work with xpe, and
GP>>> i'm having some trouble with getting it working fully

GP>>> I've componetalised the driver for it many times following the
GP>>> instructions at
GP>>> http://www.microsoft.com/windows/embedded/community/tips/xp/
GP>>> thirdparty.asp as i have for a few other pieces of hardware.

GP>>> It all seams to work properly with no errors anywhere, (during
GP>>> componentialisation or fba etc) but the fba log shows a
GP>>> FBAInstallNullDriver message todo with the modem and while it
GP>>> shows up as working in device manager it says that it has no
GP>>> driver installed for it.

GP>>> I've also noticed that the entry in component database manager
GP>>> under the component tab for this driver claims that the package
GP>>> has 0 components.

GP>>> Where have i gone wrong this time?


With best regards, KM. E-mail: (e-mail address removed)

 

[Levi O'Sulliven]

Gareth,

Can you look in your runtime image and see if the driver
files are present in the correct directories? If they are
not, you should look to your repository settings for your
component in Component Designer. It's possible that the
files didn't get imported correctly.

 

[Gareth Pye]

the files appear to be in the image, i haven't checked them all, but
enough to know it seamed to do that right

Played with what i was giving database manager and managed to get the
driver to show up in its views with things actualy in the package

My visibility is set to 200 and i can't see the null device driver
component.

so i'm guessing that the current suggestion is that theres some
dependency missing that i need, is there a chance that adding a random
other supported usb modem is likly to included the needed dependency
by random?