NX connects you to your desktop faster than any other remote access solution. XAUTHORITY points to the Xauthority file, which could be %USERPROFILE%\.Xauthority. NX Client lets you access your remote workstation wherever you are. In addition to NX_SYSTEM, it is necessary to set the NX_ROOT and XAUTHORITY environment variables before running nxservice. nxservice -start display -nokeyhook -resolution fullscreen To find out about your font path setting, you could try running NXWin through nxservice.exe which will result in informative log output on the console, e. Path arguments to nxwin.exe should be in POSIX format ("/cygdrive/c/."). instead of "-fullscreen" to get a window. You can supply "-screen 0 1280x1024" etc. A line that works for me is: nxwin -fullscreen -fp -hide -clipboard -noloadxkb -nokeyhook -auth -nowinkill -name NX :1 It can be a bit picky about its invocation. NXWin is included with the client installation. But nxauth should work just fine if you set the NX_SYSTEM environment variable to your NX client's installation directory. If that's not what you want, because you want to use Cygwin's xauth, remove the appropriate part from Auth.cpp. Note: nxcomp includes code that makes it use nxauth instead of xauth when building for Windows.
LIBS="$LIBS -L./nxcomp -lXcomp -lstdc++ -Wl,-e,_mainCRTStartup -ljpeg -lpng12 -lz"Īfterwards put cygXcomp.dll and nxproxy.exe in any directory of your choice, it should run from there. CXXFLAGS="-I/usr/include/libpng12 $CXXFLAGS" Unpack the NX tarballs in one common directory, so that it contains the subdirectories nxcomp/ and nxproxy/ afterwards.
You might need the following Cygwin packages: However, you can compile it with Cygwin tools from nxcomp-3.4. and nxproxy-3.4. Nxproxy doesn't seem to be supplied for the Windows client.
0 kommentar(er)
