USB devices and fbreseal ??

[Thomas Johansen]

Hi

I'm about to make a image ready for a customer. Now the problem is, that
it's using a USB WLAN adpater and a USB RS232 converter. So before fbreseal,
I configure the WLAN with the right settings and add a modem to a COM port
located on the USB RS232 converter with a GPRS connection using that modem.
Then after ended configiration of the image, I run fbreseal.exe and shutdown
my computer. So I'm ready to clone my disk.
But when this image is booting up again on a new platform (new USB WLAN
adapter and USB RS232 convert), a new WLAN adapter is installed as <My WLAN
adapter name #2>. Allso the USB RS232 COM ports, are enumrated from scratch
and got the number 7 to 10, so I now have a gab, COM 1, 2, 7, 8, 9, 10
instead of COM 1, 2, 3, 4, 5, 6. So now my modem and GPRS connection has no
usable COM port.

This behavior actully is OK, if you look at how USB devices work. Allthough
the devices are the same brand and manufacture, they are installed as "new".

This make the cost in our production bigger, because we now has to manully
reconfigure the assigned COM port numbers and WLAN adapter settings!!!. It
could be nice that those things didn't get changed in fbreseal and/or USB
enumerations after first boot

Does any one have a idea, hack or procedure on how to overcome this issue ??
(Could ommit the USB RS232 converter at FBA and wait for USB enumeratrion
when it's installed? )

Thomas

PS: There is no use of EWF.. !!!!! It's a mean and lean WindowsXP PRO SP1
look alike image with the latest QFE ( give and take a few)

 

[Slobodan Brcin \(eMVP\)]

Hi Thomas,

If you want to prevent PNP from detecting new devices each time you use "new device" (different serial numbers) then you can tell
USB HUB to enumerate devices to physical connection point rather then by its SN.

Read about registry switch IgnoreHWSerNum here:
http://groups.google.com/groups?hl=en&lr=&c2coff=1&[email protected]

Anyhow read trough whole thread and you can mix suggestions made by me and Doron to make autoconfig application if worst case.

Regards,
Slobodan

 

[Thomas Johansen]

Hi Slobodan.

Enumeration based on port number instead of HW serial is just what I needed
So the people, that performe the installation, just has to be careful
about where they plug in the USB devices. But they have to be that with COM
device too, so that really doesn't matter.

The keys seems to be undocumented ? Why is that with all the usable things
from MS

Is there any other useful switch under the "UsbFlags" key, that could be
nice to know. ??

But thanks for the help...

Thomas

Hi Thomas,

If you want to prevent PNP from detecting new devices each time you use

"new device" (different serial numbers) then you can tell

USB HUB to enumerate devices to physical connection point rather then by its SN.

Read about registry switch IgnoreHWSerNum here:
http://groups.google.com/groups?hl=en&lr=&c2coff=1&[email protected]

Anyhow read trough whole thread and you can mix suggestions made by me and

Doron to make autoconfig application if worst case.

 

[Slobodan Brcin \(eMVP\)]

Hi Thomas,

Is there any other useful switch under the "UsbFlags" key, that could be
nice to know. ??

I don't know if there was any at that position. But there was one or two additional related to some USB devices. (I can't remember
from head)

Regards,
Slobodan

 

[KM]

Is there any other useful switch under the "UsbFlags" key, that could be

I don't know if there was any at that position. But there was one or two additional related to some USB devices. (I can't remember
from head)

A while ago I ran accross these somewhat useful links:
http://www.sourcequest.com/modsContent.htm
http://msdn.microsoft.com/library/d..._38a60310-b278-439a-9c50-37e228e4a266.xml.asp

I liked this statement: "Microsoft OS Descriptors will be fully documented in future releases of the Windows codename "Longhorn"
Driver Kit (LDK)."

Regards,
KM