|
Post Reply
PieterS 2008-02-04 19:20
I had UltraMon 3.0.2 32-bit started on a WinXP dual-monitor machine, with the secondary monitor located on the left of the primary display. When I opened a Remote Desktop session to that machine, its UltraMon instance crashed with the following dialog:
---------------------------
UltraMon
---------------------------
UltraMon encountered a fatal error and will exit.
More information:
Source file: .\MultimonGUI.cpp
Line: 310
Return value: -2147221164
Last error: 3765269347
---------------------------
OK
---------------------------
2 issues might play a role:
- 2nd display on the left --> negative coordinates
- remote desktop supports only one display, so there's always a switch on the remote machine enabling only one display
|
Christian Studer 2008-02-05 09:59
I'm not sure what would cause this, the error message you got means that UltraMon failed to create a COM object because the component is not registered.
You could try if manually registering the component from within the remote session fixes the problem. To do this, connect to the system via Remote Desktop, open a command prompt, then run the following command:
regsvr32 c:\windows\system32\UltraMon.dll
Christian Studer - www.realtimesoft.com
|
XK 2008-02-28 10:33
I am also having a crash when I connect to my PC with a remote desktop. Both host and remote are windows XP Pro. Here is a copy of the error from the event viewer:
Source; Applications Error
Type: Error
Event ID: 1000
Description:
Faulting application ultramontaskbar.exe, version 3.0.2.0, faulting module ultramontaskbar.exe, version 3.0.2.0, fault address 0x00008692.
From UltraMon About Page:
Version 3.0.2 (3.0 Beta 2.1)
System Information:
4 monitors, 2 disabled
Current desktop: 3360x1050 (0,0 - 3360,1050)
Monitor 1 - ViewSonic VX2025w_Series (primary):
Settings: 1680x1050, 32-bit color, 60 Hz refresh rate
Coordinates: 0,0 - 1680,1050. Workspace: 0,0 - 1680,1050
Video card: Radeon X1600/X1650 Series
Device: \\.\DISPLAY1\Monitor0
Thank you,
XK
|
Christian Studer 2008-02-29 11:55
Is the taskbar set to use autohide? If yes, this issue will be fixed in the next release.
Christian Studer - www.realtimesoft.com
|
XK 2008-02-29 15:06
Yes, it is set to autohide, so I'll be patient and see what happens.
Thank you,
X
|
PieterS 2008-04-01 00:44
(sorry for the delay in responding; a newborn baby interfered with my planning ;->. Thanks for your quick reply on my original request!)
Regarding the original issue in this thread: registering the component didn't help... Don't worry too much since I don't connect remotely that often, and restarting Ultramon fixes the problem. But there's definitely something wrong, somewhere in my universe ;-). If it's any help, here's the content from the About dialog box:
2 monitors
Current desktop: 2560x1024 (-1280,0 - 1280,1024)
Monitor 1 - Plug and Play Monitor (primary):
Settings: 1280x1024, 32-bit color, 60 Hz refresh rate
Coordinates: 0,0 - 1280,1024. Workspace: 0,0 - 1280,994
Video card: 256MB ATI Radeon X1300PRO
Device: \\.\DISPLAY1\Monitor0
Monitor 2 - Plug and Play Monitor:
Settings: 1280x1024, 32-bit color, 60 Hz refresh rate
Coordinates: -1280,0 - 0,1024. Workspace: -1280,0 - 0,994
Video card: 256MB ATI Radeon X1300PRO Secondary
Device: \\.\DISPLAY2\Monitor0
|
Christian Studer 2008-04-01 10:29
Unfortunately I don't know what might cause this.
What's weird is that restarting UltraMon fixes the problem, sounds like the component registry entries aren't present when UltraMon first gets started, but then get added later on.
Christian Studer - www.realtimesoft.com
|
rich 2008-10-12 00:03
If you don't install the mirror option in 3.0.3, it causes
.\multimongui.cpp fatal error
|
PieterS 2008-11-12 05:07
Just wanted to let you know that the original issue is solved; probably because I installed the 3.0.3-beta on the remote machine (some other system changes have occurred, but they don't seem that relevant). Thanks for the support!
|
Post Reply
|
