USB Device Installation

[Cliff Nichols]

ahhhh I get it Bernhard

M$ documents stuff that to me sounds like "Lawyer-eeeezzzzze" or whatever spills out of a lawyers mouth. Sure it may be documented, but by the time I get what its saying my response is "Why didn't they just say This This This" instead of the 12 page answer of party of 1st part party of 4th inlaws cousins sister friend down the street part"

Thats the great thing about PB, somewhere it is documented, but in plain english so I get the idea, and why it works, rather than go :huh:

[Bernhard Fomm]

Why is Windows always so complicated? :bawling:

[Cliff Nichols]

Thanks, put ohhh nooo...

Then, I advise better to switch to VISTA.

Huh????

[Bernhard Fomm]

Thanks, put ohhh nooo...

Then, I advise better to switch to VISTA.

[Cliff Nichols]

Bernhard, maybe these will be of some help.
Available Serial Ports (includes USB to RS232 adapters)
List USB Information
USB "In-Complete"

There may be some useful functions there (most can be improved upon, I just haven't gotten back to them to do it myself )

[Bernhard Fomm]

Thank you for the right direction!

Is there a way to determine whether a anything driver installation is active?
My program could during install a driver sleep.

[Cliff Nichols]

I get what you mean Bernhard, (I have to go back and Read USB Complete again, but) basically the reason you get 3 times (and maybe more, maybe less) is because the number of interfaces that the device supports.

Its been a while for me working on the same concepts, and ideas, but still on my hit-list of "TBD" because soon I have several projects involving just that....but current projects take precedence so kinda back-burner at the moment.

Only help I can offer is given all the other default procedure of steps, I am sure there must be a function to tell you how many interfaces there are, Even if its hard to find (like the well guarded secret USB is )

Sorry not much help, but maybe a pointer in the right direction

[Bernhard Fomm]

I mean:

If a "new" drive into the computer, then will installed / configured
Windows the driver. This is an automatic process of Windows.

The following code in my programme notes that a "new" drive inserted:
http://www.powerbasic.com/support/pb...ad.php?t=35756

Test report:


How can I know that the driver installation is completed?
Is there a safe way?

[Michael Mattias]

Then I gave you the answer already: Launch the setup program and wait for it to complete before doing anything else

PB SHELL or Win 32: Monitor Process with ShellExecuteEx June 22, 2001 ought to handle it.

[Bernhard Fomm]

Yes, this is my question.

[Michael Mattias]

WM_DEVICECHANGE only deals with hardware.

How are you installing the driver? Launching a 'setup' program? If so you can monitor that process for completion (and probably the return code for success/fail).

[Bernhard Fomm]

I put a new drive on the computer.

%WM_DEVICECHANGE registers during
the installation three times the drive letter
up (%DBT_DEVICEARRIVAL) and
down (%DBT_DEVICEREMOVECOMPLETE).

How can I do with PB determine whether
the driver installation is finished?