Hi David,
we improved the startup time in the last year. On a decent system it should start within 7 or 8 seconds (without any documents, of course). Depending on the number of documents you open and the size of them, the startup time may be higher. Right now, we can't really improve startup times without completely re-structuring a major portion of our code and even then, we probably will only be able to shave off a second or two. A big portion of the startup time is the OS loading the .NET framework we are using. So when the app starts the first time on system, the OS needs to load the framework first - which we can't really speed up.
One way to deal with that is to automatically start Royal TS when the system starts. You could set the options to start minimized and minimize to systray. This way Royal TS will be loaded in the "background" and when you need it, you activate it using the systray icon. You can also store all your document passwords in the Windows Credential manager, so that you won't get asked for document passwords.
Regarding the layout: you could also enable Compact mode in appearance (in case it isn't set already).
Regards,
Stefan
David Macdivitt
Currently I am only using for a few Ad-hoc rdp connections. Would like any suggestions to speed up the initial launch of Royal TS and make the most space to view the remote desktops.
Some things I have tried already: