|
Post Reply
David 2006-03-16 10:20
I am running UltraMon on a Windows XP x64 with two monitors connected to a ASUS Xtreme N6600GT card.
When I first remote desktop to it after a reboot it does not 'colapse' the windows in the secondary monitor onto the primary until I use Alt+Tab to move the focus to the secondary-monitor windows (UltraMon dies too). Subsequent remote logins then show all the windows on the primary monitor as expected. When I later return to the console, all the windows are now on the primary monitor and I have to manually move them to the secondary. I remember that this did not happen when I was running Windows XP 32-bit on the same machine.
Also, the first time I remote login after a reboot the remote desktop shows the wallpaper even though I have disabled it through the client and the local group policies. Subsequent remote logins blue-out the wallpaper as the policies tell it. This did not happen on the Win XP 32-bit either.
Are these differences due to the different version of UltraMon or because Win XP x64 is based on Win 2003 and uses completely different code from Win XP 32-bit? Is there a solution? It is not that bad, just a nuisance.
|
David 2006-03-16 21:20
It's me back again with more info on the problem:
The problem does not really happen between reboots, but between console accesses, that is, the first time I remote-desktop login after having used the computer from the console it shows the wallpaper and does not move the secondary-monitor applications on to the primary. Also, UltraMon dies with the error message "Failed to set systray icon."
If I OK the error message, restart UltraMon manually, disconnect and then reconnect remotely again, everything is fine (except for some window resizing) until I go back to the console again.
|
Christian Studer 2006-03-17 03:23
Unfortunately I don't know what might cause this, but it's unlikely that this is related to UltraMon.
Regarding the 'failed to set systray icon' error: this happens if the shell hasn't finished initialization when UltraMon is started, and can be fixed by delaying UltraMon startup. See this thread for more on this.
I haven't been able to reproduce the issues you mentioned, here's what I tested:
Windows XP x64 with UltraMon 2.6 installed, UltraMon wallpaper selected. After restarting the system, I logged on locally and started Notepad on the secondary monitor. I then connected remotely to the system, with the desktop background disabled under the experience options for the remote connection.
The desktop background was blank (default blue), and Notepad had been moved to the primary monitor.
What I noticed as well is that on Windows x64, Notepad didn't get moved back to the secondary monitor after disconnecting the remote session, whereas on 32-bit Windows it was back on the secondary monitor when I logged in locally again.
Christian Studer - www.realtimesoft.com
|
Post Reply
|
