INTERACT FORUM
More => Old Versions => JRiver Media Center 23 for Windows => Topic started by: DocLotus on September 12, 2017, 06:41:01 am
-
I get this error message sometimes after a Win 10 boot up.
I don't understand the meaning of the message...
* There is only one instance of MC loading (SEE: JPEG)
* Where would I locate the possible dual User Account problem?
A Windows reboot or using Task Manager to kill MC usually allows MC to load normally.
-
bump.
Anyone have any ideas on this?
-
This normally happens if you have a copy of MC running and try to start another. (There is a setting that allows multiple instances if you wish btw. - I don't personally)
This should not happen if you are starting from a reboot. MC starts the Media Server too if you are using that so if you look in Task Manager you will see 2 entries
Media Centre 23 (32 Bit) -- In Apps
Media Centre Service (32 Bit) -- In Background Processes
to close down fully with this error , you need to stop both in Task Manager
Also have a look in the Options>Startup section , you can set this to start up NC, the Media Server etc on reboot. If one of these is set and you try to start MC AGAIN you may see the error.
I have mine set to Start MC and the Server on Windows startup
Hope this helps
Mike
Reboot is a clean option but that error shouldn't show.
-
Thanks for the info, Mike.
I just switched to the new 64 bit version, will run it for a few days & see what happens. Maybe it will resolve some of the weird problems I've had.
-
WOW :o The 64 bit version resolved all my problems ;D ;D ;D
Simply amazing....
1: No more hard lockups.
2: No more dumb error messages.
3: Only ONE instance of MC running in Task Manager (as it should be).
4: MC Media Server icon is now showing up in the Task Tray (it never did before).
5: When MC loads upon Windows 10 boot up, it starts playing with only the Media Server loaded.
6: MC itself does not load until I actually load it from a shortcut.
This is all VERY clean & orderly... not like the 32 bit version was.
Don't know what has changed (other then going to 64 bit) but something is much better then before.
This all resolves THREE YEARS of total aggravation & irritation that despite several long threads on the subject it never really got any real resolve. Now it does :P
It is sooooo nice to no longer have the endless problems with the software I love so much.
The 64 bit version is looking really good to me.
So far, I'm one very happy camper.
-
64-bit version? I wasn't aware there was one. Is it an option available upon installation or a separate installation package altogether?
-
Google was my friend.
-
The 64 bit version is brand new as of yesterday. It is in the same thread as the 32 bit version; you download the one you want.
https://yabb.jriver.com/interact/index.php/topic,112286.0.html
-
This all resolves THREE YEARS of total aggravation & irritation that despite several long threads on the subject it never really got any real resolve. Now it does :P
This most likely points to some 32bit software on your PC which was in conflict with MC. 64bit handles those things better, and it is less likely that a 32bit application will interfere with a 64bit application. For a start, 64bit applications can just load into higher memory out of the way of the 32bit stuff.
But it doesn't matter now, because...
So far, I'm one very happy camper.
-
This most likely points to some 32bit software on your PC which was in conflict with MC. 64bit handles those things better, and it is less likely that a 32bit application will interfere with a 64bit application. For a start, 64bit applications can just load into higher memory out of the way of the 32bit stuff.
Interesting point.
As soon as I installed the 64 bit version I had a feeling that something was different / better as things just seemed to run smoother. Now some 30 hours later there have been NO darn hard lockups that I used to see several times a day. I'm now feeling much more confident about MC.
-
Antivirus.
-
Speaking of AV, I just did a JRiver MC exclusion for Windows Defender using the WiKi for reference...
https://wiki.jriver.com/index.php/Taming_Windows_Defender
I'm not really sure I got everything right or not as Win 10 has changed so much since the WiKi came out. There is little in common between the WiKi & the current Win 10 / Defender screens.
Does anyone have a complete setup for the current Win 10 / Defender AV exclusion settings?
Also, could JRiver automate the AV exclusion process as I have to re-do it all over again each year when a new major version of MC comes out such as going from v22 to v23 (the version number is included in the exclusion folder)?
Would be much appreciated.