From: Paarvai Naai on 30 May 2008 12:01 I've constructed an INF file as described in the WinUSB "How to" document and things work nicely on 32-bit versions of XP and on Vista (32-bit and 64-bit). However, while installing the driver on 64-bit machines I noticed that the 64-bit WinUSB co-installer was not updating the 32-bit winusb.dll in SysWow64. To test this, I manually removed winusb.dll from SysWow64 and ran the installer. The 64-bit co-installer did not replace this missing DLL as I would have expected. The 64-bit DLL was correctly installed in System32. My concern is that if there are updates to winusb.dll in the future, the co-installer should replace both the 32-bit and 64-bit versions of winusb.dll. It looks like it's not currently doing that. Is there something that needs to be specified in the INF file to cause the co-installer to install the 32-bit DLL in SysWow64?
From: Paarvai Naai on 23 Jun 2008 20:37 Has anyone else experienced this issue? Here are the steps to reproduce: 1) Use a 64-bit Vista machine that has the default WinUSB installed 2) Delete System32\winusb.dll and SysWow64\winusb.dll 3) Use an INF file that references the WinUSB co-installer 4) Install a device that invokes this INF file System32\winusb.dll is restored, but SysWow64\winusb.dll is not. This suggests that SysWow64\winusb.dll will not be installed or upgraded by the coinstaller. Any help would be most appreciated. Thanks, Paarvai
From: chris.aseltine on 23 Jun 2008 23:04 On Jun 23, 7:37 pm, Paarvai Naai <PaarvaiN...(a)discussions.microsoft.com> wrote: > System32\winusb.dll is restored, but SysWow64\winusb.dll is not. > > This suggests that SysWow64\winusb.dll will not be installed or upgraded by > the coinstaller. Does it work on Linux and Darwin?
From: Doron Holan [MSFT] on 24 Jun 2008 13:12 since vista ships with winusb, the winusb coinstaller does nothing on the OS. you are deleting an OS file and expecting it to magically reappear...that will not happen 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. "Paarvai Naai" <PaarvaiNaai(a)discussions.microsoft.com> wrote in message news:8E9A1B44-4BA2-44DD-9C86-5DF65C55C022(a)microsoft.com... > Has anyone else experienced this issue? > > Here are the steps to reproduce: > > 1) Use a 64-bit Vista machine that has the default WinUSB installed > 2) Delete System32\winusb.dll and SysWow64\winusb.dll > 3) Use an INF file that references the WinUSB co-installer > 4) Install a device that invokes this INF file > > System32\winusb.dll is restored, but SysWow64\winusb.dll is not. > > This suggests that SysWow64\winusb.dll will not be installed or upgraded > by > the coinstaller. > > Any help would be most appreciated. > > Thanks, > Paarvai >
From: manik_66 on 3 Jul 2008 04:27
I am also facing the same problem. When installing the driver into WinXP(x64), the co-installer does not locate the 32bit version of WinUsb.DLL at SysWow64, thereby 32bit processes using WinUsb.DLL do not work at all. However, WinXP(x64) does not come with 32bit WinUsb.DLL at SysWow64 as default, so who can copy the DLL into SysWow64? I upgraded the OS with using "Windows Server 2003 (x64) SP2", but nothing solved. What I tried is co-installer VER1.5. Did anybody try VER1.7 co-installer? |