Post by drandel » 22.03.2012 22:20:23
1. Dexpot version in "About Dexpot" shows 1.5.99, Build 1805, license agreement shows 1.6
& Windows 7 SP 1
2. No error messages, but in desktops 2 through n (no matter how many desktops I set), I see a (phantom?) Windows Explorer window of a network share on our Microsoft Server 2003 server and all of the folders in it. (I've probably had that window open sometime during the day.) You cannot click and drag the window, close it, select files, or do ANYTHING with the window. It is as if it is part of the desktop wallpaper (but, of course, it's not). By the way, desktop 1 does not display the window.
3. At this point, I don't know how to reproduce the error.
4. Other running applications: Chrome, Firefox, Skype, & Sticky Notes.
5. It doesn't seem to be connected with any other software.
If I exit Dexpot and restart it, the phantom window still appears.
If I reboot, it does not reappear.
If I can gather more information about this "unusual" behavior, I'll update this thread.
- Attachments
-
- screenshot of phantom window
- Dexpot Phantom Window.png (421.77 KiB) Viewed 2088 times
1. Dexpot version in "About Dexpot" shows 1.5.99, Build 1805, license agreement shows 1.6
& Windows 7 SP 1
2. No error messages, but in desktops 2 through n (no matter how many desktops I set), I see a (phantom?) Windows Explorer window of a network share on our Microsoft Server 2003 server and all of the folders in it. (I've probably had that window open sometime during the day.) You cannot click and drag the window, close it, select files, or do ANYTHING with the window. It is as if it is part of the desktop wallpaper (but, of course, it's not). By the way, desktop 1 does not display the window.
3. At this point, I don't know how to reproduce the error.
4. Other running applications: Chrome, Firefox, Skype, & Sticky Notes.
5. It doesn't seem to be connected with any other software.
If I exit Dexpot and restart it, the phantom window still appears.
If I reboot, it does not reappear.
If I can gather more information about this "unusual" behavior, I'll update this thread.