New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow any remote desktop client OSX #2231
Comments
From an email I sent in January 2012:
I ended up choosing CoRD because it is free open source software, licensed under the GPLv2 license. It is based off the Unix program rdesktop, which is also licensed under the GPL. |
I think this is important because CoRD is no longer maintained, and even suggests using Microsoft's RDP client instead (cf. https://github.com/dorianj/CoRD/blob/master/README.md):
|
Cf. https://apple.stackexchange.com/a/199208 → https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-uri: Microsoft's Remote Desktop Client for Mac (both versions 8.0.43 and 10.0.1) register their ability to open I haven't contributed code to BOINC before, but I might be able to fiddle with the relevant code of MainDocument.cpp and have a patch within the next week or so. |
Thank you fro the links. I will look into this.
|
Also, CoRD does support |
I ran some tests with LHC@home and can successfully show the VM Console using Microsoft Remote Desktop. But there are a couple of issues which I feel make MRD unacceptable for this purpose:
If you select Connect Always the message is not repeated for future connections to that port, but appears again if a different port is referenced. These issues occurred even when I tried all the seemingly relevant options in the open command:
Please let me know if you find a solution to these issues. |
I have now tested with Microsoft Remote Desktop 10.0.823 on OS 10.13.2, in addition to the problems with MRD 8.0, MRD 10.0 also displays an alert asking for a user name and password. This can be eliminated by adding a dummy username and password to the RDP "query-string" like this:
|
I have not looked into this issue much more, but I would say that 1024x665 resolution used by CoRD is a red herring. Although I saw CoRD similarly use 1024x640 when I tried it, the VM was actually using 720x400. The resolution issue is not specific to the MS RDP client on Mac. I wonder if RDP clients are even capable of knowing what resolution the VM is set to. Unlike connecting to a session on a physical screen over e.g. VNC, and therefore the server dictating the resolution used by the client, I would think the intended use case of RDP (controlling a session not tied to a physical screen) is for the client to dictate the resolution. VirtualBox supports the RDP client resizing the VM's resolution, but only when guest additions are active. So BOINC Manager might have to use something like |
Found it:
|
This issue is raised again in https://boinc.berkeley.edu/forum_thread.php?id=14173 Given the recent changes in OSX to accommodate Apple silicon, should we promote this up the priority order? |
On my Mac, when I click "Show VM Console" then it asks me to download CoRD, however in my case I have the the microsoft remote desktop application. Could it be genericized so that any RDP capable program can be used?
The text was updated successfully, but these errors were encountered: