![]() ![]() There are cases where it is normal that the process runs in background, but what you’re describing is something different. So in my case it’s expected that the process never goes away? We’ll release it with the next update, if you keep enabled the automatic software updates check NoMachine will alert you when a new version will be available. I’m sending a zip of my recent sessions from tonight (which demonstrate the two issues above) to the email you mention above.Thanks! Then if I launch NoMachine again, connect to remote machine, perform a few tasks and then quit there will be two instances of nxplayer.bin*32 that never go away!Īnother issue I noticed is that if I launch NoMachine, connect to remote machine and then try to close the NoMachine window before I’ve done anything on the remote machine then NoMachine will freeze and I’ll be forced to manually kill the process. ![]() In other words if I launch NoMachine, connect to remote machine, preform a few tasks (*you’ll see why this part is important in the next section) and then quit there will be one instance of nxplayer.bin*32 that never goes away. So in my case it’s expected that the process never goes away? That definitely seems wrong because it leaves an instance of the process running for every single run. When can I get this version? I assume I just need to update NoMachine on my client and can leave the server running the same version as before?įor my second question I don’t believe I’m running the Enterprise Client as I’m just using whatever free/default version for both the client and server. Yes, using Ctrl+Alt+N to switch windows would be fantastic. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |