Missing "driver installer" - how to get?

[jj3000]

I have installed XP Pro and XP Embedded on the same device in order to
verify the problem with the bluetooth dongle not working under XPE.

It turns out to work fine in XP Pro.

The difference is during the driver install it asks me to plug in the
USB dongle, and then a window will pop up, saying USB device found and
immediately copy the driver to or from the system32/drivers directory.
Then the device is recognized

In XPe it does not do this. When prompt to insert the USB dongle, it
would detect the device is inserted and let me continue the last steps
of the widcomm software install, but the driver isn't actually
installed. Therefore the device still doesn't work afterwards.

So I must be missing the driver installer or wizard??

But I already have "add hardware control panel" I'm lost as to what I
need to add to gain this functionality?

Thanks in advance.

 

[Slobodan Brcin \(eMVP\)]

Hi jj,

This is problem from last week, right? Why did you created a new thread, on continuation of the same problem.

Add hardware wizards is only required for visual "pleasure"/annoyance.

1. I don't think that you have told me so far what were the results of analysis of setupapi.log file. Are there any errors reported.
2. If you have Device Manager what do you see for your USB device? Exclamation mark(what error code), correctly installed driver?
3. If you have componentized this driver by importing inf file. Try removing that component and manually copy driver files.

Best regards,
Slobodan

 

[jj3000]

Yes it is the same problem from last week, but I felt I am missing a
fundamental component therefore I'm asking a seperate question.

1. The setupapi.log I believed I looked at it and searched for the
keyword "error". I only see a couple of places and they had to do
with not recognizing the celeron CPU, not with Bluetooth.

2. In the device manager, I will not see anything as bluetooth
device. Before installation of Widcomm drivers, if I plug in the
device, it would say "unknown device" with exclaimation mark.. After
the installation of widcomm driver, and rebooting, this would never
appear anymore, the hour glass would come up whenever I insert or
remove the device. I believe this is because

3. I have not tried to componentize this driver, yet. It's a fairly
big driver. But I'll see if I can copy the files manually

 

[KM]

jj3000,

Yes it is the same problem from last week, but I felt I am missing a
fundamental component therefore I'm asking a seperate question.

1. The setupapi.log I believed I looked at it and searched for the
keyword "error". I only see a couple of places and they had to do
with not recognizing the celeron CPU, not with Bluetooth.

"Error" is not good for searching in setupapi.log.
Try "#E".

As Slobodan mentioned you may want to attach the log here so other may help you with analyzing it.

2. In the device manager, I will not see anything as bluetooth
device. Before installation of Widcomm drivers, if I plug in the
device, it would say "unknown device" with exclaimation mark.. After
the installation of widcomm driver, and rebooting, this would never
appear anymore, the hour glass would come up whenever I insert or
remove the device. I believe this is because

IIRC, bluetooth support is coming in SP2 only.

3. I have not tried to componentize this driver, yet. It's a fairly
big driver. But I'll see if I can copy the files manually

"big driver" - what is it? Many files or etc?
For some (if not most) drivers it is enough to just copy files to appropriate directories at run time and PnP will do the job for
you.
Read this thread for more ideas: http://groups.google.com/groups?hl=en&lr=&c2coff=1&selm=#[email protected]

KM

 

[Sven Meirsman]

IIRC, bluetooth support is coming in SP2 only.
I got it to work on SP1. (Sitecom USB bluetooth dongle with Widcomm drivers)

"big driver" - what is it? Many files or etc?

Yeah... really big... The setup itself is about 20 Mbytes. a lot of files,
exe's, dll's, sys, ini, registry settings and some really hardcore system
integration. (Like the bluetooth neighbourhood that embeds into the explorer
and desktop. These are not just icons.)

Anyway, I didn't yet manage to get a componentized version of these
bluetooth drivers up and running. If you succeed with it, JJ3000, I would be
happy to see some details on this issue.

Sven

 

[Slobodan Brcin \(eMVP\)]

Hi Sven,

Have you seen Detonator Drivers from NVIDIA.
How would you rate them. Small, Medium, Huge size?

Let me answer this question
Full package size is 25188 KB in 46 files.

Actually what is driver that will do all what you need.

nv4_disp.inf - 39K
nv4_mini.sys - 2402K
nv4_disp.dll - 3652K

To make this work you will have to remove 2/3 of entries in inf file.
Unless you actually want that your user can use NVIDIA wizards to set additional proprietary settings. You can go with only 6MB.

Same thing is true for most drivers.
Because drivers do not contain pictures, and other useless UI stuff, just compiled code.
20MB of real compiled code would be extremely hard to make.

Best regards,
Slobodan

PS: I hope that you catched a point from this.

 

[KM]

Sven,

I suspected you have run (integrated) the entire install package and that is why I refered you to SP2.
To get it to work you would unlikely need all the files from the package.

Explore SP2 USB Bluetooth Device stack (e.g., start with "Motion Computing USB Bluetooth Device" component). Check out its
dependencies (like bth.inf, bluetooth file transfer, etc.) and you will see that you can get it to the image with much smaller
footprint.

KM

 

[Sven Meirsman]

To make this work you will have to remove 2/3 of entries in inf file.
Unless you actually want that your user can use NVIDIA wizards to set

additional proprietary settings. You can go with only 6MB.

Same thing is true for most drivers.
Because drivers do not contain pictures, and other useless UI stuff, just compiled code.
20MB of real compiled code would be extremely hard to make.

Best regards,
Slobodan

PS: I hope that you catched a point from this.

I know i know, but this Bluetooth dongle installs a driver for the dongle, a
driver for the serial ports, a driver for the headset profiles, a driver for
network access, a driver for dial-up, etc. And all these parts cannot be
configured without the executables that are supplied with the setup. These
exe's cannot be started by just double clicking them. They embed into the
system. They even imitated the right pane of the windows explorer where you
see the contents of a map. (I played with their components in the "ActiveX
Control test container" application.
And depends.exe doesn't tell you much if you use it on ActiveX exe's.

Another one that I found difficult to resolve... The cab file of the setup
contains serveral versions of some files. These could be like
filename_number.ex_, filename_number2.ex_, filename_number3.ex_, etc. I
can't find anything in the setup that will tell me which file is being
extracted. I used inctrl, filemon, regmon and I even used the orca tool to
dig into the Windows Installer Setup.

And yes, I know what you mean... but I already spent about 3 weeks trying to
get this thing componentized, without success.

Sven

 

[Slobodan Brcin \(eMVP\)]

Hi Sven,

Ok.
You will have to deal with each driver separately and to verify that they are installed successfully.
1. Hardware drivers (the one that drive your USB "dongle" and probably same driver your COM ports.)
They only require that their files are present in Windows\inf Windows\System32 Windows\System32\drivers folders. During the FBA PnP
they will be picked up and installed. (DO NOT USE Import function from Component Designer to make component from INF file for them)

2. Network stack drivers if present, you will have probably to use snetcfg.exe to install them.
For example look at MS component "TCP/IP Networking" in Resources you will find FBA Generic Command "TCP/IP Installation" that is
used to install them. Look at this and use pieces for your case.
For other drivers you will have to figure this our your self.

3. Services. (not drivers) (exe or dll files) They should be detected treated and installed separately with different procedures.

4. COM components. (dll/ocx) files you can distinguish them by looking at them from Dependency Walker, or by executing regsvr32 on
them. If it pass them you will have to register them by "FBA DLL/COM Registration"

5. Setup utilities. You need to resolve all dependencies that they need. (static/dynamic and many other thing) You can configure
your hardware (if fixed) on XPP and then copy registry entries so you won't need config utils in your XPe. image.
Or you can detect all resources they need and preinstall them from TD.

Anyhow look at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpembed/html/customxpecomp.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpesp1/html/xpe3rdparty.asp
Also debuggers are great thing to discover what is missing.

Best regards,
Slobodan