Devcon -r install%WINDIR% Inf Netloop.inf *MSLOOP. List all devices that are present for each class named (in this case, USB and 1394). Devcon listclass usb.

That's why it is better to use a windowing protocol such as Zmodem. -- 'If you want to post a followup via groups.google.com, don't use the broken 'Reply' link at the bottom of the article. Cisco xmodem transfer 3750.

So you're sitting comfortably at your observatory, or even at your home (maybe far far away from the telescope) and you need to unplug and replug some device. The only way seems to be resetting the computer and that takes quite a long time. We'll that was my case when I was testing some new firmware for the Seletek, and after quite a few google-research, I found the following solution: First of all, download and install the (in case there's a problem with the link, or if help for installing is needed, here's the). Once installed, you'll have to find your offending device hardware I.D.

Just launch the device manager (should be available from the control panel, system, hardware), and look for your device: You may ask now: but if it's an USB device, why it is under 'Ports' and not under 'Universal serial bus'? The truth is you can find USB devices under Ports (if they are mimicking a serial or parallel port), or under 'Astroimaging equipment' (that's the case for some QHY cameras), and many other places, that's up to the developer of the driver. Back to our subject, please double-click now your device and select the 'Details' tab, then scroll to 'Hardware ID': In our case, you can see 'USB VID_16C0&PID_09B0' at the second line. Now it's time to use the DEVCON utility; in my case, I wrote a small batch program (those old '.bat' files), with these lines inside: c: tmp devcon i386 devcon disable USB VID_16C0*PID_09B0* c: tmp devcon i386 devcon enable USB VID_16C0*PID_09B0* (of course the 'c: tmp devcon i386' should be replaced with the actual folder of your devcon installation). And saved the '.bat' file to the desktop. Important: no program should be using the device for this to work. In Seletek's case, that means closing all Seletek programs before launching this devcon.

Now that I'm writing this, I very much bet this is the same as manually disabling / enabling the device from the device manager, will have to try. Oliver kasper softbox. This method is at least far more comfortable.

Hi all, I am packaging software at present for the Olympus Digital Voice REcorder VN-240PC and I can't seem to get the device drivers to install for the device. There are 2 inf files, DW90USB.INF and VNUSB.INF that come with the software and which do not get installed by the setup.exe. When the device is plugged in, it's only then that the option to install the device drivers appears. When I use the Windows device driver utility to install the drivers, manually, it works ok. I need to get these drivers installing silently. I have used devcon.exe and Dpinst.exe in the past but neither of these seem to be working. The thing is the drivers aren't signed.

The command line I am using with devcon.exe is devcon.exe install And for Dpinst.exe I am using Dpinst.exe /LM and this reports that it's installed the driver successfully but when I plug in the device the Add new hardware wizard still appears. Has anyone got any clue how i can install these drivers so that the add new hardware wizard doesn't pop up. But I keep getting devcon.exe failed.

Thanks, Mark. There are serveral ways but for me the most succesvol is the following.

This is a litte help to get in de right direction. The only condition is that you're drivers are signed. Checked that with sigverif.exe. Put the drivers like sys inf etc in the INSTALLDIR. In wise: 1) Make a custom action Execute Program from installation of the driver 2) include the following Executable File DPINST.exe Commandline arguments /S /LM /PATH '[INSTALLDIR] Put it in the sequence that suites you well. Condition like NOT REMOVE.