Well, it worked, but with no keyboard shortcuts to switch between desktops! Some colleagues got past this by changing keys of Virtuawin. I tried it and it unfortunately failed because Virtuawin didn’t work at all on the remote desktop. This is an attracting solution used by many colleagues.
#Nomachine nx 3.x Pc
I tried upgrading from NX Client 3 (recommended by my company since NX Server 3 is in use) to NX Client 4 with absolutely no change. I tried applying the compatibility setting on each and every executable found in the installation directory, including NXWin.exe which is responsible for showing the desktop, NXSSH.exe which establishes the SSH connection, NXClient.exe which is the frontend offering the configuration panel, etc. However, this is miserably failing for NX Client. I have a post in French about this, called Le problème des caractères trop petits sous Windows. But this is doable, because this is how I worked out Ableton’s Live. For 64-bits applications, this is trickier and would deserve its own post since it involves registry hacking. This is easy for 32 bits applications: just right click on it, access the properties, then the compatibility tab, and there is a check box for this. In both cases, I was able to turn off DPI scaling locally for the offending application. Second one has been Corel’s VideoStudio, a video editor. First one has been Ableton’s Live virtual studio. This is the third application misbehaving with DPI scaling for me.
#Nomachine nx 3.x windows
Under Windows 8, it seems to get some form of virtual resolution sensitive to the scaling! Let’s do the math real quick. It gets the display resolution and can make use of all pixels. Under Windows 7, this functionality doesn’t affect NX client at all. Magnification is done without lowering screen resolution, by just applying a scaling before rendering the graphical elements, as opposed to scale bitmaps after the fact as the Windows built-in and third-party zooming applications do. This doesn’t completely remove the need for application-specific tweaking, but this at least helps greatly. I use to bump up the scaling to 150% which makes fonts large enough for most cases and also enlarges mouse pointer. It can be adjusted by right-clicking on the Desktop, accessing Personnalize and clicking on Display. There is a very neat way to get this under Windows since 7: the DPI scaling. Nobody seems to be having this issue, and there is a very good reason why.īecause I am visually impaired, I need larger fonts and mouse pointer. However, running NX client on this machine causes a major issue: display resolution goes down to 1114×634! I tried searching for a solution or at least a workaround to no avail. Because it is lightweight, I like to use it when working from home. However, I got a secondary ultrabook running Windows 8.1.
#Nomachine nx 3.x full
I can bump up the resolution closer to native by switching my NX client to full screen. The desktop showed up in a nice 1674×954 resolution, which is near the native 1680×1050 I have with the 22″ LCD out there. When I was connecting to NX server using NX Client 3 or 4 using my main corporate laptop running Windows 7, I got no display problem. I got issues with the screen resolution on Windows 8, erratic keyboard responses and ended up switching to VNC after I couldn’t find any solution under Windows 8. However, I can control on which NX client I run. The virtual machine at my work place is running NX Server 3.4.0-12, probably the free edition.
At the end, I gave up on NX and fell back to VNC, but this exploration is nevertheless interesting. I recently tried using NoMachine‘s NX Client to connect to a virtual machine at work running NX Server, and got an incredible number of problems.
0 kommentar(er)
