Forum Replies Created
-
AuthorPosts
-
TorParticipant
Hi huang.
In order to ease the configuration you’re trying to achieve, we’ve added a new Feature Request:
Offer the possibility to restore the window geometry when starting the client or connecting to a desktop
https://www.nomachine.com/FR02N03008We’ll release it very soon, so I’d suggest to enable the notify option in the feature request page. Once you’ll use this new version you’ll just need to enable the new key you’ll find in the NXS file, and the client window will try to go to the same geometry set in the “Resolution” key.
TorParticipantHi mkrisk,
could you please confirm you see black borders when the client window is at its minimum size, so you cannot make it smaller?
TorParticipantHi.
Today we’ve published the new app version fixing this issue.TorParticipantHi huang.
All the keys you’ve mentioned are still used in NXS files. I can’t think of a reason why you didn’t find them, so I suggest to use the latest NoMachine version, create a new connection and read the corresponding NXS file created by default in ‘Documents/NoMachine’.
You may wish to read also these articles giving more information about how desktop resize works in version 5:
Resize and scaling options for NoMachine client version 4 or later
https://www.nomachine.com/AR02M00835Changing how you view the remote host
https://www.nomachine.com/changing-how-you-view-the-remote-host1. no matter how many sessions u have created and saved (for every single session u got a .nxs file) there is only 1 player.cfg file for all of them, if I want set 1 session as “fullscreen” and other 1 as “normal”, how does it work?
The CFG file affects all client instances. If you want to use different CFG files you may create a shortcut/link to the NoMachine client and use the ‘–config’ command line option, for example (on Mac OS X):
/Applications/NoMachine.app/Contents/MacOS/nxplayer --config /tmp/custom.cfg
You may also create a single CFG file starting the client always in fullscreen mode, and use the ‘–geometry’ command line option for those connections that should not be fullscreen, for example (on Mac OS X):
/Applications/NoMachine.app/Contents/MacOS/nxplayer --session server.nxs --geometry 1024x768
2. where can I set the concrete resolutions except the “normal”, e.g I want to create 2 sessions, 1 of them with 1024×768 and the other one with 800×600?
Use the NXS file as you did in version 3.5. More details here:
The most frequently asked options for pre-configuring the client and the session behavior
https://www.nomachine.com/DT07M00094#19TorParticipantHello.
Our recent release was mainly focused on mobile platforms, so some fixes didn’t go through all required testing and were delayed to the next release.
Nevertheless if you want to test our version including this fix, just contact us on forum[at]nomachine[dot]com.TorParticipantHi CG.
We’ve confirmed there is a problem when the server has four or more monitors, it is documented here:The client on mobile doesn’t show more than four monitors in the remote monitors list
https://www.nomachine.com/TR01N06340In order to work around the issue you may create another connection to the same server, so all monitors will be shown by default.
We’ll release an update within a few days. Thank you for your time.TorParticipantHi aplocher.
Currently the mobile version optimized for small screens is one of our top priorities, we plan to have a final release in a couple of months, but an earlier beta release is not excluded. If you didn’t do it already, you may subscribe this Feature Request to be contacted as soon as we’ll release it:
Offering a NoMachine client for Android smartphones
https://www.nomachine.com/FR09L02828Even if the current GUI is not optimized for screens smaller than 7 inches, you may wish to try the client by downloading the package from our website. The Play Store doesn’t make it available on your device, so you have to manually install the APK.
December 21, 2015 at 12:05 in reply to: Plans to support iPad Pro’s effective resolution of 1366×1024? #9408TorParticipantHi benny.
A few days ago we’ve submitted a new app version which will offer a better support for the iPad retina resolution 2048×1536, which of course will be available also on iPad Pro. We’ve already started to work on optimizations required for the new resolution, so it should be available in one of our next updates.
TorParticipantHi Motto!
Our engineer would like to send you some debugging libraries to retrieve more information. Can you please confirm the NoMachine version you’re using on client and server? We’ll contact you by e-mail. Thanks.
TorParticipantHi markus! The feature FR12K02799 is not yet scheduled for implementation, so I can’t give you a release timeframe, but we’ll do our best to start it as soon as possible.
TorParticipantHi motto.
Our engineer didn’t find relevant information in your logs, he was planning to ask your help to test a new debugging version but you solved the issue and he became sad! Now that you’ve found a new way to reproduce it, I’m sure he’ll return to the fray. 🙂
Can you please do the following when you reproduce the issue, and let me know if it is enough to work around it:
– Open the NoMachine menu and select ‘Show the connection status’
– Click the ‘On’ button to shut down the server
– In the new dialog click ‘YES’ to restart the server at the next reboot
– Authorize the server shutdown
– Open the NoMachine Client
– Click the ‘Settings’ button
– Click the ‘Connection status’ link
– Click the ‘Off’ button to start the server
– Authorize the server startup
– Click the ‘Close’ buttonFor the record, with the next release we’ll offer an easier way to restart the server from the GUI. It is not a common operation for a user, but it may still be useful.
TorParticipantHi skullius.
Currently the quick connection string format “Protocol://Host:Port” can only be used in the search edit, the box you see between the Sort and New buttons, as explained in the tutorial dialog visible when the client starts.
We may extend the support to other configuration fields, but we would need to know how you’ve configured your connection in order to know what to improve.The error you’re reporting occurs for example if you write “nx://aaa.bbb.ccc.ddd” in the Host field of the connection Edit dialog. In that case you can change Protocol and Port fields (on the right side of the dialog), so the quick connection format is ignored.
If this is your case, remove the prefix “nx://” from the address in Host, press OK and connect again.TorParticipantHi.
Currently the mobile version optimized for small screens is one of our top priorities, we’re working hard on it. Even so I cannot say right now when it’ll be available.
If you didn’t do it already, you may subscribe this Feature Request to be contacted as soon as we’ll release it:Offering a NoMachine client for Android smartphones
https://www.nomachine.com/FR09L02828TorParticipantHi.
Can you please give us more information:– What’s your Android version?
– Are you using a custom keyboard?TorParticipantThose environment variables are mainly intended to be used internally, so I discourage you from defining them system-wide (which is common on Windows).
You may however create a batch file for each user which executes the ‘set’ command to change NX_CONFIG (the directory where the client will read/write all user settings), and at last starts the client.
I don’t see a real advantage though. Defining that variable may be useful when administrators don’t want to create the settings directory in the default path (%USERPROFILE%\.nx), while in your case you want to change all default paths, so you should still modify player.cfg. -
AuthorPosts