Not getting much help from the msi logs. I'll keep at it. I'll post if I make progress. Best I've managed is to install the driver files and use a wrapper script to install the drivers. Not ideal, but it's working...
I've made some progress. I have the vhhcd driver installing via an MSI. However, I get a VirtualHere dialog ("Please attach your device to this"...) message after it installs. Where does this message come from and is there an easy way to suppress it?
I still need to add the vhbus and then create a 64-bit MSI. Once I have them complete, I will e-mail them to you for review and to publish if desired.
Oops. I forgot about the need to call vhenum after the drivers. Maybe the easiest thing to do is call the exe with the -d flag during the MSI installation. I will try that.
Is there a flag to disable the output from the -d command or is there only the -r to go to a file?
Also, what are the -m, -3 and -n flags? They're not mentioned in the client faq or in the help.
You need to call the -d argument. It is too complicated to install the drivers otherwise.
You can pipe the output to NUL in windows (just like /dev/null in linux) so use that as the filename e.g. -r NUL
The -3 argument is useful. It tells virtualhere to use the new version of the virtualhere driver for windows 10 (or later version of windows). This driver is simpler and more compatible than the current virtualhere drivers. Its still in beta mode that's why you need to start the client with that flag but soon ill release it so its the default for windows 10 clients as I now have quite a few customers using that new driver and it works well.
The other flags m,n are just for internal use to switch certain flags in the client
If you can send the msi script that would be great then i can add it to my website for others.
Regarding the -3 , you need to use that (as well as any other arguments )with all calls to vhui64.exe if you want to use/install/uninstall the new driver
So, if you're saying that in order to install the drivers I need to start the gui with "-3", then yes the drivers install fine for me fine.
However, if I attempt to install them via the command line using "vhui64 -3 -d", then I encounter a possible bug. I get a "Virtual HCD Enumerator" dialog "Error, a root-enumerated HCD device has been created, but there are no drivers to bind!".
Also, it appears that "-y" is removing them correctly during this test. I may have had them in a bad state with several failed attempts to install the USB2 and USB3 drivers.
Just to be clear. Is the "-3" required for EVERY call to vhui? I understand it would be required when starting vhui if the USB3 drivers weren't installed, but how about after they are installed?
It appears that "-y" will remove either driver that is installed without the "-3", so is it safe to omit for that? And finally, is it required for the service calls (install/uninstall/communication calls).
Just making sure shortcuts in the MSI have the correct calling convention. And thanks for the speedy fix for the USB3 install!
Yes the -3 is required. Im just testing installing as a service with the -3 and it doesnt work as i need to pass an extra argument to the service. I will fix this now.
There is only one bug left in the win10 driver that is when the device is used via virtualhere the windows bing new hardware plugged in sound doesnt occur and the autoplay for usb sticks doesnt occur for some reason. Otherwise all functionality works fine with the new driver. once that last bug is fixed i will move the driver to the default for windows 10 and there will be no need for the -3 flag. I will work on this over the next few days to get this bug fixed and let you know when its ready.
No, sorry not at the moment
No, sorry not at the moment
I'm not having much luck
I'm not having much luck building one using the difxapp.msm merge modules...
Not getting much help from
Not getting much help from the msi logs. I'll keep at it. I'll post if I make progress. Best I've managed is to install the driver files and use a wrapper script to install the drivers. Not ideal, but it's working...
OK I will have a go at
OK I will have a go at building an MSI early next week, and let you know when it's ready
I've made some progress. I
I've made some progress. I have the vhhcd driver installing via an MSI. However, I get a VirtualHere dialog ("Please attach your device to this"...) message after it installs. Where does this message come from and is there an easy way to suppress it?
I still need to add the vhbus and then create a 64-bit MSI. Once I have them complete, I will e-mail them to you for review and to publish if desired.
Oops. I forgot about the
Oops. I forgot about the need to call vhenum after the drivers. Maybe the easiest thing to do is call the exe with the -d flag during the MSI installation. I will try that.
Is there a flag to disable the output from the -d command or is there only the -r to go to a file?
Also, what are the -m, -3 and -n flags? They're not mentioned in the client faq or in the help.
.
You need to call the -d argument. It is too complicated to install the drivers otherwise.
You can pipe the output to NUL in windows (just like /dev/null in linux) so use that as the filename e.g.
-r NULThe
-3argument is useful. It tells virtualhere to use the new version of the virtualhere driver for windows 10 (or later version of windows). This driver is simpler and more compatible than the current virtualhere drivers. Its still in beta mode that's why you need to start the client with that flag but soon ill release it so its the default for windows 10 clients as I now have quite a few customers using that new driver and it works well.The other flags m,n are just for internal use to switch certain flags in the client
If you can send the msi script that would be great then i can add it to my website for others.
Do I need the -3 with -d to
Do I need the -3 with -d to install the drivers. Or is it just when starting the client?
I am installing to Windows 10. I'll send the MSI's as soon as I test them in the GPO deployment.
Through trial and error, it
Through trial and error, it looks like the usb 3 driver only installs from the gui and does not uninstall with -y.
Regarding the -3 , you need
Regarding the -3 , you need to use that (as well as any other arguments )with all calls to vhui64.exe if you want to use/install/uninstall the new driver
So, if you're saying that in
So, if you're saying that in order to install the drivers I need to start the gui with "-3", then yes the drivers install fine for me fine.
However, if I attempt to install them via the command line using "vhui64 -3 -d", then I encounter a possible bug. I get a "Virtual HCD Enumerator" dialog "Error, a root-enumerated HCD device has been created, but there are no drivers to bind!".
Also, it appears that "-y" is removing them correctly during this test. I may have had them in a bad state with several failed attempts to install the USB2 and USB3 drivers.
OK yes i tested the -3 -d
OK yes i tested the -3 -d again and it did fail i will fix this asap...
Edit: OK fixed in 3.4.8 of the client
Just to be clear. Is the "-3
Just to be clear. Is the "-3" required for EVERY call to vhui? I understand it would be required when starting vhui if the USB3 drivers weren't installed, but how about after they are installed?
It appears that "-y" will remove either driver that is installed without the "-3", so is it safe to omit for that? And finally, is it required for the service calls (install/uninstall/communication calls).
Just making sure shortcuts in the MSI have the correct calling convention. And thanks for the speedy fix for the USB3 install!
Yes the -3 is required. I
Yes the -3 is required. Im just testing installing as a service with the -3 and it doesnt work as i need to pass an extra argument to the service. I will fix this now.
There is only one bug left in the win10 driver that is when the device is used via virtualhere the windows bing new hardware plugged in sound doesnt occur and the autoplay for usb sticks doesnt occur for some reason. Otherwise all functionality works fine with the new driver. once that last bug is fixed i will move the driver to the default for windows 10 and there will be no need for the -3 flag. I will work on this over the next few days to get this bug fixed and let you know when its ready.
V3.4.8 now reports the
V3.4.8 now reports the "Virtual HCD Enumerator" error when NOT using the -3 option.
To clarify, when using the "
To clarify, when using the "-d" rather than "-3 -d".
OK will fix this...
OK will fix this...
OK fixed in 3.4.9 of the
OK fixed in 3.4.9 of the client