I'm really trying to be patient. I left my request for feedback alone for several days while you guys were playing early April fools' jokes.
Tonight I did a clean install of Win2k pro on a different machine from the three that were experiencing this problem. Same thing: if I connect to a library on a network share -> no screensaver.
The process I followed was:
a) format C drive
b) install Win2k pro
c) install sp4
d) install dx9.0b
e) install ATI driver 4.2 w/control panel
f) install 10.0.104
g) test
If I load a network share that is actually local (i.e. if the MC machine is named mozart and I load \\mozart\testlibrary) then I don't have a problem. The screensaver kicks in fine.
If I load a network share on a different machine, I get no screensaver.
One other thing I've noticed is that while MC is in the foreground, the mouse cursor repeatedly switches to the arrow+hourglass. There is some sort of pattern to it that relates to 10 second intervals. For instance, I may see it at 10:30:20, 10:30:30 and 10:30:40, then not see it for 30 or 40 seconds, then I'll see it again twice in a row 10:31:10, 10:31:20. This little quirk is exhibited on at least two of the 4 machines that I have. I haven't checked the other two for the mouse cursor issue. The mouse cursor doesn't exhibit this behavior when a local library is loaded.
Guys, I'm really wondering what to do at this point.
a) I have been developing an application that makes use of MC, but I'm a bit discouraged at the official support I am receiving. It's difficult to press on when I feel like I'm being ignored.
b)I repeat: I don't know how NOT to reproduce this problem. I would like to know what you have tried in your attempts to reproduce it.
c)I'd like some feedback on the log info that is above.
d)I'd like suggestions as to what I can do to help you find the bug.
e)I'd like a statement as to whether or not network libraries are supported.
Ultimately, I just want some technical support. Thusfar, I think I've gotten shrugs instead. At least a little feedback, please. There is not a single machine on which I've tested on which this problem hasn't occurred (unless you count pre-v10 – this problem appeared the moment I upgraded).