|
Post Reply
Kurt Tomicich 2003-02-10 17:10
...but if I disable the smart taskbar and re-enable it, it will work. This happens every time I boot up the computer but disable/enable of smart taskbar fixes it.
I'm using UltraMon 2.1 and I'm currently running 3 displays off of a Parhelia/MX420 combination (I can't work with it stretched across all monitors, but surround gaming rocks - manual cable swap when necessary:))
Anything that can be suggested would be greatly appreciated.
thanks,
KT
Stuff from the About window:
----------
3 monitors
Current desktop: 3456x864 (-1152,0 - 2304,864)
Monitor 1 - ViewSonic PS790 (primary):
Settings: 1152x864, 32-bit color, 85 Hz refresh rate
Coordinates: 0,0 - 1152,864. Workspace: 0,0 - 1152,834
Video card: Matrox Parhelia 128MB - English
Device: \\.\DISPLAY1\Monitor1
Monitor 2 - Plug and Play Monitor:
Settings: 1152x864, 32-bit color, 85 Hz refresh rate
Coordinates: 1152,0 - 2304,864. Workspace: 1152,0 - 2304,834
Video card: Matrox Parhelia 128MB - English
Device: \\.\DISPLAY3\Monitor0
Monitor 3 - Plug and Play Monitor:
Settings: 1152x864, 32-bit color, 85 Hz refresh rate
Coordinates: -1152,0 - 0,864. Workspace: -1152,0 - 0,834
Video card: NVIDIA GeForce4 MX 420
Device: \\.\DISPLAY4\Monitor1
|
Christian Studer 2003-02-11 02:12
During testing with the Parhelia I had noticed the same problem when Matrox PowerDesk (PDeskNet.exe) was started after UltraMon.
If you have PowerDesk set up to start automatically during system startup, it should start before UltraMon by default. If you only start it manually, you would need to restart UltraMon to fix the problem.
BTW, with PowerDesk running, movement of maximized windows will be slowed down. For this reason I would recommend disabling PowerDesk.
Christian Studer - www.realtimesoft.com
|
Kurt Tomicich 2003-02-13 16:31
Both are set to launch on startup. I'm not sure how I can force one to launch before the other.
|
Christian Studer 2003-02-13 23:43
There's no real way of doing this as far as I know. The applications which get started from the registry (such as PowerDesk) should run before those started from the Startup folder (UltraMon), but there's no guarantee that PowerDesk has finished startup when UltraMon gets started.
As a workaround, you could create a script which waits for a couple of seconds, then launches UltraMon. You can then point the UltraMon shortcut in Start menu > Programs > Startup to this script.
To create the script, paste the following lines into a .vbs file:WScript.Sleep 2000
Set shell = CreateObject("WScript.Shell")
shell.Run """C:\Program Files\UltraMon\UltraMon.exe""" The first line is the delay in milliseconds, if you want to wait 5 seconds replace 2000 with 5000. Replace the path on the third line with the complete path to UltraMon.exe on your system.
To edit the shortcut in the Startup folder, right-click the shortcut, select Properties and replace the Target field with the path and file name of the script.
Christian Studer - www.realtimesoft.com
|
Kurt Tomicich 2003-02-16 18:53
I've never worked with vbs scripting before but, based on experience creating batch file, I just pasted your code into a text file and changed the extension to .vbs - is that not how to go about it?
Copying your code and pasting it into the text file created a single line. I tried running it that way and I tried running it after manually inserting carriage returns and both ways return an error message:
Script: C:\Program Files\UltraMon\Ultramon Delay.vbs
Line: 1
Char: 19
Error: Expected End of statement
Code: 800A0401
Source: Microsoft VBScript compilation error
Thanks for your help, any further suggestions would be appreciated.
KT
|
Christian Studer 2003-02-16 23:54
I'm not sure what would cause this, try if this script works: UltraMonDelay.vbs.
Christian Studer - www.realtimesoft.com
|
Kurt Tomicich 2003-02-19 17:03
That one worked just fine. About 45 minutes after sucessfully testing your 2nd script, "Align to Grid" stopped working and I couldn't even get it to Auto Arrange. Played around trying to load a couple restore points and finally pulled all video drivers and reinstalled them - I had only tried overlaying the drivers or pulling them one at a time previously and apparently this is what was needed.
All problems are gone now, including the need for the script that you so graciously provided (I'll be hanging on to it though!)
Thanks for your help.
KT
|
Post Reply
|
