Use case: Squish #147
-
Hi everyone! To start off, I don't know if this is even remotely the right use case for this project. If it isn't, I apologize, and you can tell me to sod off :) I'm looking to run an app that requires a display (specifically, Squish, a GUI testing framework) on a Windows VM managed through Hyper-V. Quick background: Connecting to the VM via RDP (Remote Desktop Protocol) works fine; I can see Squish starting the application-under-test with its GUI and everything. Can this driver can be used so that I don't need to connect via RDP at all, but still have a "display"? Driver installation was successful (it's now listed right below the Microsoft Remote Display Adapter when I connect through RDP), but it doesn't seem to have any noticeable effect. Squish still fails to discover the GUI application. Thanks for taking the time! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Basically, once the driver is installed you would want to interact with the "display" like a normal display, and not through the remote desktop display (try anydesk, teamviewer, parsec, etc). When using the virtual display through those types of programs instead, it interacts with it normally rather than what remote desktop does, which is making a new virtual display for your session not the same as a physical (or driver in this case) does for you. |
Beta Was this translation helpful? Give feedback.
Basically, once the driver is installed you would want to interact with the "display" like a normal display, and not through the remote desktop display (try anydesk, teamviewer, parsec, etc). When using the virtual display through those types of programs instead, it interacts with it normally rather than what remote desktop does, which is making a new virtual display for your session not the same as a physical (or driver in this case) does for you.