- This topic has 3 replies, 3 voices, and was last updated 4 years, 8 months ago by
.
- Posts
I apologize if this topic has been discussed before. I am trying to use a BB60C remotely to monitor FM band signals. When I use Microsoft RDC to remote in I get the ambiguous “spectrum analyzer software stopped working” error. This probably has to do with RDC falling back to OpenGL1.1, which the BB60C wants 2.0 or better. Is there anyway to work around this other than trying to install a VNC client? Installing a VNC client would be problematic because different users would be logging in, and most VNC client’s I have used do not do Windows login very well. Thanks in advance!
Mike
Hey Mike,
Below is what another customer on this forum is doing to use the Spike software on remote desktop.
I created a batch file in the spike program folder and named it RunFromRDP.bat.
Inside that batch file I placed the following commands:
tscon 1 /dest:console
spike.exeThe first command disconnects the remote desktop session and forces Windows to run in the local console. Then the Spike starts and OpenGL initializes correctly. After a few seconds I reconnect and everything works fine.
Essentially, as long as Spike is started not through remote desktop, you can log into the machine while it is running with no issues. To date, this is the primary workaround. If you search for remote desktop and OpenGL you will find several discussions online that might have other suggestions.
We have used TightVNC in the past with success, maybe TeamViewer is a possible solution here? If your CPU has vPro capabilities, there are tools available for connecting to the PC through this as well, which we have tested at one point with success.
Let me know if you have additional questions.
Regards,
AndrewThanks to stackoverflow.com I found a great article and now I can now reliably remote desktop from a Windows 10 client via RDP to a host system with Spike and Windows 10. This is also a cure for remote operation of various other software using OpenGL that used to crash for me.
This was done by changing the group policy for the local machine to enable the graphics card for remote desktop. To change the setting run “gpedit.msc” then navigate to “Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment” and then enable “Use hardware graphics adapters for all Remote Desktop Services sessions”. Alternatively modify “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services” and set the DWORD “bEnumerateHWBeforeSW” to 1. Note that I had to download the latest graphics card driver and restart for all to work as the stock Windows driver wasn’t good enough.
For full information see the various contributions at https://stackoverflow.com/questions/51705471/current-state-and-
solutions-for-opengl-over-windows-remote
You must be logged in to reply to this topic.