Hello, I have a Wix based application installer that installs an application which is used to control our USB device and installs a WinUSB based driver for communicating with the device using the WinUSB CoInstaller. While performing a software first install the user is notified that they may plug the device in after the installation has finished, this is caused by the WinUSB CoInstaller option DriverPlugAndPlayPrompt. A problem arises on XP when after installation the user runs the installed control software before plugging in the device, because the software requires winusb.dll which is only installed by the WinUSB CoInstaller after the device is plugged in. A workaround to this problem is to include a copy of winusb.dll in the application install directory, however this means the software will never use the winusb.dll installed by the WinUSB CoInstaller when the device is plugged in, I expect this is not an ideal situation, especially if winusb.dll at some stage in the future gets security patches installed via Windows Update. Can anyone see a way around this problem on Windows XP? Assuming that I would have to deploy a 32bit copy of WinUsb.dll at the target machine, which will be the better way? 1) deploy WinUsb.dll to the directory, where the 32bit app EXE is located 2) deploy WinUsb.dll to SysWow64 directory (only if the dll to delploy is newer than existing, or absent) The 1st approach is simply a local installation for my own app only, therefore no impact to entire system or other apps, but the app will not use newer WinUsb.dll even if it would be installed in SysWow64. Free Windows Xp DownloadThe 2nd approach is machine-level install and will have the impact to entire system, but as long as following to general installation rule by version-compare, the app will always use the newest version of the dll. This section describes the generic WinUSB driver (Winusb. sys). SKUs of Windows XP with SP2 service packs support WinUSB. WinUSB is not native to Windows XP. Windows 10/8/7/XP doesn't need WinUsb.sys. Click here to know if WinUsb is safe and how to avoid WinUsb.sys errors. Sep 25, 2012 How to install WinUSB.sys without a. Prior to Windows 8 if you choose Winusb.sys as the function. Windows 8 and earlier versions up to Windows XP SP3. Hi, I have been asked to load the Winusb.sys for our USB device in 'Windows XP sp2'. I copied the sys file from the vista and I changed the inf to install the winusb.sys and as the WDK documentation mentioned I have added a AddReg section to create a GUID registry entry. And when I tried to install the driver, I am getting the error code 37. The Microsoft article points out that this error is due to the failure in DriverEntry routine. But I don't know how to get rid of this problem. I even tried to install the driver with the WdfCoInstaller dll, but I get the same error. I could able to install the driver successfully in Windows Vista with the same Inf. But is it possible to install the driver in Windows XP. I have attached the setupact.log and setupapi.log file logs. Could any one help me on this? Winusb requires KMDF v1.5 (also from the WDK), not KMDF v1.1 d -- Please do not send e-mail directly to this alias. This alias is for newsgroup purposes only. This posting is provided 'AS IS' with no warranties, and confers no rights. Wrote in message news.4cwc.googlegro ups.com. > Hi, > > I have been asked to load the Winusb.sys for our USB device in > 'Windows XP sp2'. I copied the sys file from the vista and I > changed the inf to install the winusb.sys and as the WDK documentation > mentioned I have added a AddReg section to create a GUID registry > entry. > > And when I tried to install the driver, I am getting the error code 37. > The Microsoft article points out that this error is due to the failure > in DriverEntry routine. But I don't know how to get rid of this > problem. I even tried to install the driver with the WdfCoInstaller > dll, but I get the same error. > > I could able to install the driver successfully in Windows Vista with > the same Inf. But is it possible to install the driver in Windows XP. The Wurlitzer electric piano has proved a tough nut to crack in software. Can Arturia rise to the challenge? Wurlitzer-V is Arturia’s amazingly accurate physical model of the classic Wurlitzer 200A electric piano. 'Compared to any other Wurli emulation out there, this is. Arturia wurlitzer v. > > I have attached the setupact.log and setupapi.log file logs. > > Could any one help me on this? Thanks for your response. I have installed WDF 5472 in my machine. So does it includes KMDF v1.5? If not how could I get KMDF v1.5? Thanks Ravi Doron Holan [MS] wrote: > winusb requires KMDF v1.5 (also from the WDK), not KMDF v1.1 > > d > > -- > Please do not send e-mail directly to this alias. This alias is for > newsgroup purposes only. > This posting is provided 'AS IS' with no warranties, and confers no rights. > > > wrote in message > news.4cwc.googlegro ups.com. > > Hi, > > > > I have been asked to load the Winusb.sys for our USB device in > > 'Windows XP sp2'. I copied the sys file from the vista and I > > changed the inf to install the winusb.sys and as the WDK documentation > > mentioned I have added a AddReg section to create a GUID registry > > entry. > > > > And when I tried to install the driver, I am getting the error code 37. > > The Microsoft article points out that this error is due to the failure > > in DriverEntry routine. But I don't know how to get rid of this > > problem. I even tried to install the driver with the WdfCoInstaller > > dll, but I get the same error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |