INTERACT FORUM

I'll be terse this time.

Process Explorer with network library:

Process: Media Jukebox.e Pid: 2116

Type   Name
Desktop   \Default
Directory   \KnownDlls
Directory   \Windows
Directory   \BaseNamedObjects
Event   \BaseNamedObjects\userenv:  User Profile setup event
Event   \BaseNamedObjects\GuardEventmmGlobalPnpInfoGuard
Event   \BaseNamedObjects\mixercallback
Event   \BaseNamedObjects\hardwaremixercallback
Event   \BaseNamedObjects\crypt32LogoffEvent
Event   \BaseNamedObjects\MSFT.VSA.IEC.STATUS.6c736db0
File   \Device\LanmanRedirector\salsburs-2k\salsbst\testmcnetwork\
File   \Device\LanmanRedirector\salsburs-2k\salsbst\testmcnetwork\
File   \Device\NamedPipe\ntsvcs
File   \Device\KSENUM#00000001\{9B365890-165F-11D0-A195-0020AFD156E4}
File   C:\Program Files\J River\Media Center\PlaybackEng.dll
File   C:\WINNT\system32\STDOLE2.TLB
File   \Device\KsecDD
Key   HKCR
Key   HKLM\SOFTWARE\MICROSOFT\COM3
Key   HKU
Key   HKLM\SOFTWARE\MICROSOFT\COM3
Key   HKCR\CLSID
Key   HKCR
Key   HKLM\SOFTWARE\MICROSOFT\COM3
Key   HKU
Key   HKLM\SOFTWARE\MICROSOFT\COM3
Key   HKLM\SOFTWARE\MICROSOFT\COM3
Key   HKCR\CLSID
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes
Key   HKCU\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\Windows
Key   HKCU\Software\Classes
Key   HKLM
Key   HKCU\Software\Classes
Key   HKCU
Key   HKCU\Software\Classes
Key   HKCU\Software\Classes\CLSID
Key   HKLM\SOFTWARE\MICROSOFT\Windows\CURRENTVERSION\Explorer
Key   HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\DRIVERS32
Key   HKCU\SOFTWARE\MICROSOFT\Windows\CURRENTVERSION\Internet Settings
Key   HKLM\SYSTEM\ControlSet001\Control\NetworkProvider\HwOrder
Key   HKCU\SOFTWARE\JRiver\Media Jukebox
Key   HKLM\SYSTEM\ControlSet001\Control\Nls\Locale
Key   HKLM\SYSTEM\ControlSet001\Control\Nls\Locale\Alternate Sorts
Key   HKLM\SYSTEM\ControlSet001\Control\Nls\Language Groups
Key   HKCU\SOFTWARE\JRiver\Media Jukebox
Key   HKCU\Software\Classes
Key   HKCR
Key   HKLM\SOFTWARE\MICROSOFT\COM3
Key   HKU
Mutant   \BaseNamedObjects\MICROSOFT_WMDM_MUTEX
Mutant   \BaseNamedObjects\AMResourceMutex2
Mutant   \BaseNamedObjects\GuardMutexmmGlobalPnpInfoGuard
Mutant   \BaseNamedObjects\mxrapi
Mutant   \BaseNamedObjects\mxrapi
Mutant   \BaseNamedObjects\Media Jukebox Application
Port   \RPC Control\OLE2b
Section   \BaseNamedObjects\__R_0000000000e4_SMem__
Section   \BaseNamedObjects\MJCurPlayingInfo
Section   \BaseNamedObjects\VIDEOMEMORY
Section   \BaseNamedObjects\MJCurPlayingInfo
Section   \BaseNamedObjects\mmGlobalPnpInfo
Section   \BaseNamedObjects\JRiver Hook Map
Section   \BaseNamedObjects\WDMAUD_Callbacks
Section   \BaseNamedObjects\MJCurPlayingInfo
Section   \BaseNamedObjects\MJCurPlayingInfo
Semaphore   \BaseNamedObjects\GuardSemmmGlobalPnpInfoGuard
Semaphore   \BaseNamedObjects\shell.{A48F1A32-A340-11D1-BC6B-00A0C90312E1}
Thread   Media Jukebox.e(2116): 1304
Thread   Media Jukebox.e(2116): 1328
Thread   Media Jukebox.e(2116): 1328
Thread   Media Jukebox.e(2116): 2160
Thread   Media Jukebox.e(2116): 1268
Thread   Media Jukebox.e(2116): 2136
Token   NASD\SalsburS
WindowStation   \Windows\WindowStations\WinSta0
WindowStation   \Windows\WindowStations\WinSta0


The only difference I see is that with a network library there are 4 sections named MJCurPlayingInfo, whereas with local library there are 3 .  The significance of this, or lack thereof, is beyond me.

I would appreciate it if someone from J River would comment.

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).

Thanks for your response.

The mouse cursor thing sounds like interference from something like network activity.

Agreed. MC is doing something that is preventing the screensaver, but only when it has a network library loaded.

Try disabling your network interfaces, including bluetooth, 1394, etc.  Just to see what happens.

Don't have any of that.

Edit: I deleted your post from the build thread because you've got something going here.

I was informing you that there is a bug in the build.  I don't think it's right to try to hide that.

Official support doesn't know.  Honest.

I have stated that I would like to know what "Official support" is doing about the bug.  If you guys don't tell me what you are testing, then I may be running around in circles.

With this comment, I think you've proven it is not MC related:

Quote

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.

I have no idea what you're talking about.  It only occurs when MC is running with a network shared library that is not on the local machine.  This latest machine on which I tested has no other software installed, much less running software.  Please explain what about my statement makes you think it is not MC-related.

I feel your pain, I wish I could help.

I just uninstalled v10 and installed 9.1.  Loaded a network library and sat for a minute.  Screen saver kicked in right on time.

This is a bug that was introduced in v10.  From my records, it looks like this bug cropped up on or before 10.0.80, since I didn't try any v10 builds prior to that one.

Yes, things (~variables) change when a new program is installed.  If the new program has a bug, then one may fall victim to it.

Have you tested in a LAN where there is an NT4 domain controller?  I don't understand why you seem to be so unwilling to accept the fact that v10 has a bug.

FYI: rolled a second machine back to 9_1 and it too no longer exhibits the problem.

I understand that you don't believe this is a bug.  Could you help me to understand what tests you've performed and the logic you have used to come to this conclusion?

Thanks, I'll test.  Since this is happening in normal view and 100% dependent on loading a network library rather than local, my guess is that any screensaver specific stuff you do isn't related, but I'll give it a shot anyway.

Matt, is there any chance you could give me access to a few of the early v10 builds so I could see where the problem first cropped up?

Stuart,
Though I understand you think this is a bug, I do not.  I could be wrong, but I don't see how.  The OS handles the network.  

I would appreciate it if you would keep a more open mind about the problem.

The fact that 9.1 worked and 10.0 doesn't only means that something is different.  MC depends on the OS and it works with it differently from one version to the next.

At this time, we're not going to chase this problem.

Can you find a work-around?

Jim

Jim,


The only workaround is to not use MC10 in my HTPC.  I cannot go without a screen saver on a display that cost more than I could afford when I bought it.

My mind is open, but you aren't feeding it with anything that I can digest.  SInce only one of us wants to figure out what is going wrong, I would say that I am not the one who needs to keep an open mind.

When you say that the OS handles the network, I think I understand what you mean, but I don't think I agree with your conclusion.  It seems obvious that something that MC10 (post-build 80) does (and that MC9.1 and prior do not do) when there is a network library is preventing the screen saver.  If you were to say that there is something different between my network environments and the ones on which you test, I would buy that in a heartbeat.  In fact, I think that is the reason you haven't seen the bug.  The fact that I can repro it on a totally clean machine seems like pretty compelling evidence that it is MC and not some other application.  There are three things installed on the machine: MC10, ATI's driver and Windows 2000.  The screensaver is only disabled when MC10 is loaded and with a network library.  I think 99 out of 100 people would conclude that MC has the bug.

How hard would it be to let me download a few older builds?  How hard would it be to tell me whether or not you've tested with an NT4 domain.  Why not at least respond to my questions and requests.  I find the lack of response to my innocent and well-meaning questions and requests for support to be unfair and inexplicable.  I'm not throwing a tantrum or anything, just stating my case.

Oh, well.

There's progress: I can reproduce it.

Let us scratch our heads for a while.  Hopefully we can figure it out.

It should be fixed next build.  Creating and destroying a progress window that was never even shown when saving the library caused this.

Thanks for all your help.  

( I still say it's a windows bug )

Confirmed as fixed..thanks again.