This project has moved. For the latest updates, please go here.

Terminals1.6e/1.6i conflicts with Ultramon 2.7.1 in mutiple monitors?

Topics: Developer Forum, User Forum
Apr 22, 2008 at 2:18 AM
I have 2 monitors, primary and secondary. And the display card is X1600, OS Windows XP SP2 Pro English with Asia Launguage Package.

If I launch Terminals in either monitor without fast switching by Ultramon 2.7.1, everything's fine.

If I launch Terminals, then restore the window, use "Move window button" of ultramon to move it to secondary monitor, everything's fine.

However, if I launch Terminals with MAXIMUM window in primary monitor (It's a pity that Terminals cannot remember its posistion launching last time, always in primary monitor), and use "Move window button" of ultramon to move it to the secondary monitor, then the error appears.

Exception of type 'System.Windows.Forms.AxHost+InvalidActiveXStateException' was thrown.

The error message is below:
----------------------------------------------------------------------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

                            • Exception Text **************
Property get of 'FullScreen' cannot be invoked at this time.


                            • Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Terminals
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///D:/share/Terminals1.6e/Terminals.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GACMSIL/System.Windows.Forms/2.0.0.0_b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GACMSIL/System/2.0.0.0_b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GACMSIL/System.Drawing/2.0.0.0_b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
log4net
Assembly Version: 1.2.10.0
Win32 Version: 1.2.10.0
CodeBase: file:///D:/share/Terminals1.6e/log4net.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GACMSIL/System.Configuration/2.0.0.0_b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GACMSIL/System.Xml/2.0.0.0_b77a5c561934e089/System.Xml.dll
----------------------------------------
TabControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/share/Terminals1.6e/TabControl.DLL
----------------------------------------
VncSharp
Assembly Version: 0.9.0.0
Win32 Version: 0.9.0.0
CodeBase: file:///D:/share/Terminals1.6e/VncSharp.DLL
----------------------------------------
AxInterop.MSTSCLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/share/Terminals1.6e/AxInterop.MSTSCLib.DLL
----------------------------------------
arlpypii
Assembly Version: 1.6.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GACMSIL/System/2.0.0.0_b77a5c561934e089/System.dll
----------------------------------------
Interop.MSTSCLib6
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/share/Terminals1.6e/Interop.MSTSCLib6.DLL
----------------------------------------
Interop.MSTSCLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/share/Terminals1.6e/Interop.MSTSCLib.DLL
----------------------------------------

                            • JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Coordinator
Apr 23, 2008 at 10:02 PM

Can you try to reproduce the above with just using the default terminal services client? mstsc.exe ?

Do you see the same issue?

Thanks.
Apr 24, 2008 at 1:44 AM
I'd been used mstsc.exe before I found some tools to instead of it.
mstsc.exe is fine all the time.
But there's one thing to notice that only launch mstsc.exe with normal windows, the "Move window button" appears.
If launch mstsc.exe with maximum window, just the head title, you know.
Coordinator
Apr 30, 2008 at 3:38 AM

liubo,

I'm leaning towards of just simply stating that (currently) we do terminals will not support using it with Ultramon. I know that doesnt give you a solution but quite honestly I dont have the time to dig into the details. If you have some spare cycles feel free to dig into the details.

At best (for now) I could always copy this into a feature request (to enable support for terminals with ultramon....
May 4, 2008 at 8:15 AM
Thanks.