I've only just looked at this thread. Ref the media player problem, maybe it's a bug in W7, or maybe it's just a case of MS enforcing some stricter rules, causing some s/w that used to work to now have problems. I certainly don't know the answer, but I suggest that MS should investigate, even if the outcome is to simply say 'If this (xyz) isn't done correctly, the app may fail in the manner described...' or some such.
The reason for my interest can be seen by looking at a thread I started elsewhere
*** LINK REMOVED ***
http://windows7forums.com/windows-7-support/17012-powerdesk-process-remains-after-exiting-gui.html
After invoking, using, and exiting PowerDesk, a subsequent attempt to invoke it again results in a running process that can be seen in TaskManager, but no GUI. Another attempt to invoke it results in another process, but again no GUI. This will go on, presumably until you run out of memory. However, killing those processes until there is just one left magically causes the GUI to pop up, and everything is back to normal.
This doesn't happen **every** time that PD is invoked again after a previous use, but it's often enough to be a problem. I had suspected that it might have been because I was running W7 x64. However, one of the responders to my thread was running 32-bit W7, and I note that the OP of this thread is also running 32-bit.
I have also heard (once, no documentation, etc) from someone, to the effect of 'yeah, I've seen something like that...'. So maybe there are a number of apps that could exhibit similar problems.
My W7 x64 (i7, 6GB, ATI HD4870, 2TB disk) is rock solid, all networking (wired and wireless) sorted completely, sharing going just right, Virtualbox running like a dream, etc. So I don't put any of this down to a flaky installation (RC1 7100).
It would be interesting to hear about any other apps that fail to bring up their GUI sometimes.
Roger
