From: Paarvai Naai on 8 Jul 2008 15:10 Hi Doran, Thanks for your reply. You are correct that deleting system files in Vista is not be advisable. This was just a toy example and we can instead look to Win XP for more evidence regarding this issue. Similar to the experience of manik_66, we too found that using the WinUSB coinstaller on Windows XP 64-bit did not result in the SYSWOW64/winusb.dll (32-bit version) being installed. Only the SYSTEM32/winusb.dll (64-bit version) is installed. After copying the SYSTEM32/winusb.dll (32-bit version) from an XP 32-bit machine to the XP 64-bit machine, my 32-bit application ran without incident on the 64-bit OS. Please note that I had also posted previously regarding whether WinUSB is supported on XP 64-bit at all: http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.development.device.drivers&tid=cf739aa7-7ade-48e4-aa0e-2e7cc99ed4d4 Finally, my understanding was that, while Vista ships with WinUSB pre-installed, the coinstaller mechanism allows a way to update WinUSB if a new version is subsequently released. The information above highly suggests that the coinstaller may not properly update the SYSWOW64/winusb.dll. Can you please shed some light on this? Best regards, Paarvai "Doron Holan [MSFT]" wrote: > 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. >
From: Paarvai Naai on 8 Jul 2008 15:13 Hi manik_66, Yes, this is exactly what I saw. I tried version 1.7 of the *WDF* co-installer. However, this does not make a difference since it is the *WinUSB* co-installer that is responsible for installing the winusb.dll. As far as I know, there is only one version of the WinUSB co-installer currently available. Best regards, Paarvai "manik_66" wrote: > 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? >
From: Paarvai Naai on 16 Jul 2008 15:25
Hi all, Is there anyone who can provide input on this Windows XP 64 coinstaller issue or Windows XP 64 compatibility issue for WinUSB? To summarize my previous email quoted below, the documentation does not list Windows XP 64 as a supported OS for WinUSB. However it seems to work, except for the fact that the coinstaller does not install the SYSWOW64/winusb.dll. It appears manik_66 has seen the same behavior as me. Thanks, Paarvai "Paarvai Naai" wrote: > Hi Doran, > > Thanks for your reply. You are correct that deleting system files in > Vista is not be advisable. This was just a toy example and we can > instead look to Win XP for more evidence regarding this issue. > > Similar to the experience of manik_66, we too found that using the > WinUSB coinstaller on Windows XP 64-bit did not result in the > SYSWOW64/winusb.dll (32-bit version) being installed. Only the > SYSTEM32/winusb.dll (64-bit version) is installed. > > After copying the SYSTEM32/winusb.dll (32-bit version) from an XP > 32-bit machine to the XP 64-bit machine, my 32-bit application ran > without incident on the 64-bit OS. > > Please note that I had also posted previously regarding whether WinUSB > is supported on XP 64-bit at all: > > http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.development.device.drivers&tid=cf739aa7-7ade-48e4-aa0e-2e7cc99ed4d4 > > Finally, my understanding was that, while Vista ships with WinUSB > pre-installed, the coinstaller mechanism allows a way to update WinUSB > if a new version is subsequently released. The information above > highly suggests that the coinstaller may not properly update the > SYSWOW64/winusb.dll. > > Can you please shed some light on this? > > Best regards, > Paarvai |