Explorer window visually moves to different screen

[willichan]

I am running a fully patched XP Pro SP3 system with 3 monitors. I had this problem using dexpot_1514_r1777, and have recently updated to dexpot_ivy_r1805 and still see this behavior.

After the system is locked, or goes into the screensaver, Windows Explorer windows (not Internet Explorer) will visually appear on some random desktop other than where they were, but the taskbar item for that window will still be on the correct desktop. On the desktop where the window visually appears, the window is not clickable: it is only there visually. On the desktop where the taskbar item is, I can only right-click and close the window. Minimizing, restoring and moving have no effect. Less frequently, but at times, the window will visually appear on all desktops but the one where the taskbar item is.

I have no rules that affect explorer windows. My only rules apply to three specific applications.

[Patrick]

Please send me a log file.

[willichan]

Log file sent by PM

Code: Select all

*** BEFORE
         | "WOL" folder window     | "Ladwilli's Documents" folder window
Desktop# | On Desktop | On Taskbar | On Desktop | On Taskbar |
---------+------------+------------+------------+------------+
   1     + No         | No         | Yes        | Yes        +
---------+------------+------------+------------+------------+
   2     + No         | No         | No         | No         +
---------+------------+------------+------------+------------+
   3     + Yes        | Yes        | No         | No         +
---------+------------+------------+------------+------------+
   4     + No         | No         | No         | No         +
---------+------------+------------+------------+------------+
   5     + No         | No         | No         | No         +
---------+------------+------------+------------+------------+
   6     + No         | No         | No         | No         +
---------+------------+------------+------------+------------+
   7     + No         | No         | No         | No         +
---------+------------+------------+------------+------------+


*** AFTER
         | "WOL" folder window     | "Ladwilli's Documents" folder window
Desktop# | On Desktop | On Taskbar | On Desktop | On Taskbar |
---------+------------+------------+------------+------------+
   1     + Yes        | No         | No         | Yes        +
---------+------------+------------+------------+------------+
   2     + No         | No         | Yes        | No         +
---------+------------+------------+------------+------------+
   3     + No         | Yes        | Yes        | No         +
---------+------------+------------+------------+------------+
   4     + No         | No         | Yes        | No         +
---------+------------+------------+------------+------------+
   5     + Yes        | No         | No         | No         +
---------+------------+------------+------------+------------+
   6     + Yes        | No         | No         | No         +
---------+------------+------------+------------+------------+
   7     + Yes        | No         | No         | No         +
---------+------------+------------+------------+------------+


[Patrick]

Thanks!

I don't see anything suspicious in the log. Very strange...

Maybe try this version.

[willichan]

Similar results. New log file PM'ed to you.

[willichan]

Just saw the post about problems between Fences and Dexpot. I am running both Fences and ObjectDock Pro 2. Could this maybe be related?

I do not have differing fences or docks per screen, but it may be a direction to look at.

. . .

Just got an Application Error

___
Dexpot: dexpot.exe - Application Error
The instruction at "0x7e42948d" referenced memory at "0x00850004". The memory could not be "read".

[Patrick]

Just saw the post about problems between Fences and Dexpot. I am running both Fences and ObjectDock Pro 2. Could this maybe be related?

I doubt it, but Fences does some funny stuff, so I wouldn't dismiss it entirely. Considering your problem is easy to reproduce, could you disable Fences and ObjectDock temporarily and see whether it makes a difference?

Dexpot: dexpot.exe - Application Error
The instruction at "0x7e42948d" referenced memory at "0x00850004". The memory could not be "read".

That's an unrelated, known XP-only problem. We're already working on it.

[willichan]

I uninstalled Fences, and shut-down OD2, but it seems to not make a difference.

I'll keep looking for anything else that might be doing it.

Would applications like the LogMeIn client cause problems with Dexpot?
How about devices like the Plugable UGA-2K-A (USB video device I use for my third monitor)?
I'll test these over the next couple of days as I get a little time, but I am reluctant to uninstall the video device unnecessarily.

[Patrick]

Is your screensaver password protected?

[willichan]

Yes. It is.

[Patrick]

Then it looks like the system unlock is what triggers the problem? I'll create a new test version with some additional log output.

[willichan]

Looking forward to testing the new version. In the mean-time, I am reverting back to the previous version.

[Patrick]

dexpot.exe

(1.37 MiB) Downloaded 90 times

Sorry it took so long...
New log file please.

[willichan]

I ended up upgrading to a newer PC and reloading. I will turn on the logging, and watch to see if I get the same behavior.

I started having some problems with the video card. I am wondering if it wasn't related.