Forum Replies Created
-
Posts
-
The link is definitely the best way to track the resolution, when the fix has been officially released to the public. Its status will change to ‘closed’.
We might be able to send out a patched version to users before it gets released to the public. If we have any news, we will update this topic 🙂
It shows that kexts were loaded, but there is no indication that the crash was nx-related. If it happens again, the NoMachine logs and stacktrace would be useful. Check our article for steps on how to gather those: https://knowledgebase.nomachine.com/DT11R00181
Windows’ native RDP can run with virtual display drivers, so it can create virtual displays mirroring the client displays and switch the user’s remote desktop session onto those virtual displays. NoMachine cannot create virtual Windows (or Mac) displays. Linux is the exception. The free version can connect you to a remote physical Linux display or a virtual one. Additionally, it’s possible to run multiple virtual displays on Linux. This is achievable when using NoMachine’s Terminal Server for Linux products.
Similar topics:
https://forums.nomachine.com/topic/are-multiple-monitors-supported-when-remote-server-has-no-monitors
https://forums.nomachine.com/topic/multiple-monitor-support-for-vms
https://forums.nomachine.com/topic/windows-multiple-displaysFurther references:
https://knowledgebase.nomachine.com/AR06S01131aaron, we won’t need the logs now, we’ve reproduced the black screen and updated an initial Trouble Report we inserted regarding Big Sur on M1
@Brisn, thanks for this additional information about how to reproduce the problem. Every extra bit of information can be useful, especially in this particular because there are three possible ways for a computer to become idle: 1) the monitor enters sleep mode to save energy 2) you close the lid on your macbook/laptop 3) there is a full system sleep where we can only try to wake it with WoL (wake on lan).
this should (to me) be a somewhat simple fix to make but it seems to have been lying out there unaddressed for years……it’s almost as if the developers don’t fully use their own software enough in the real world to experience these annoying deficiencies for themselves…
Have you had this problem on Intel as well? M1 only came out last November. Successfully diagnosing a problem and then finding an effective solution can sometimes be a long process, however, I don’t recall *unresolved* problems with NoMachine waking up Intel Macs/Macbooks/Mac (i.e if there have been problems in previous versions, they’ve been resolved). “Deficiencies” can be interpreted as missing features and in that case, we certainly welcome feedback on how to improve and add value to the product.
On the connecting device try disabling MDNS. You can do this by going to Settings / Player / Security and unchecking the box “Don’t show other computers on the local network”.
“Is there any software that will create a dummy display?”
Not that we are aware of. I would go for the dummy adapter.
We’ve tried installing NoMachine on a variety of Windows XP hosts and can’t reproduce the issue you are encountering.
I would download again from our website and reinstall from scratch (you must remove all traces of the earlier installation from your computer) and make note of the MD5 signature of the package. Then, using an external tool such as http://www.fourmilab.ch/md5/, you could check whether the MD5 signature is being corrupted in someway.
Unfortunately you won’t be able to use NVENC because you have a GTX 460 which is based on Fermi architecture.
NVENC was introduced by Nvidia on Kepler architecture. It was introduced with the GeForce 600 series.More info about Nvenc: https://en.wikipedia.org/wiki/Nvidia_NVENC
There is now a Trouble Report documenting this issue.
NoMachine does not work correctly after installing on Windows XP 64 bit
https://knowledgebase.nomachine.com/TR07S10323It will be released in the next software update.
Removing panels is easy. Just click on any panel, go to settings and there you should have a dropdown list.
However, your problem seems to be unrelated to NoMachine software. If those boxes are visible even when you are not using a NoMachine remote desktop session, you should really ask in the Xfce forums.
Or do those boxes visible only appear when you are in a NoMachine session?
Thanks for letting us know. If you have any other questions or issues, feel free to submit a new topic.
“I changed it on one server and it apparently changed it on all my servers. It has not made any difference.”
This is not clear. You shouldn’t be changing anything in Server Settings. Disabling HW decoding is generally done from within the NoMachine session.
If you start a connection in the regular way, you then open the connection menu (Ctrl-Alt-0) from within the session and select ‘Display’ and then ‘Change settings’.
Click modify and check the box “disable hardware decoding” (check this guide for an example https://knowledgebase.nomachine.com/DT10R00167#5.8).
Please provide clear steps of the problem related to NoMachine software (assuming this is a web-based session).
Hi, at first I thought it might be nested sessions which was causing the problem, but it works for us with VirtualBox 🙂 From Mac to Win VM, start a new session and connect to Mac, (we had to enable grab keyboard in the NoMachine player before starting the session from the Win VM).
With VMware it doesn’t work because basically VMware changes cmd to Ctrl , so it appears to be more of a problem with VMware? We tried with Fusion as well, cmd+N works, but cmd+C, cmd+V are transferred as ctrl+(C/V).