Mantar wrote:Hey Dan the Java path for my windows install is:
I also have javaw.exe in c:\windows\system32 which is the same as the java mentioned above. My computer doesn't appear to be suffering the same problem with java paths as yours. I think that is a reason why my JAVA doesn't spike as high as you had mentioned.
Just so we are clear, that is your actual install path on the hard drive, right? If so, that too differs from my hard drive install path, which is:
I believe there is an option to change the install path during installation, so I might have cleaned up the default path since that was the only version installed on this computer. Since Sun Microsystems provided the option to change the install path, there is no reason to believe that it wouldn't work if someone took them up on their offer.
However, what struck me as particularly odd was what happens when you go into the "Java Control Panel" and check what Java itself thinks is it's install path. For that you need to go into:
Start-> Control Panel-> Java Control Panel-> Java Tab-> View Button-> Path
Then, double-click on the Path field under the Path column to allow access to the field. Here that path is completely different than the install path and reads:
As shown below underlined, that does not exist. Here are both the actual install path and what Java believes to be the install path together for an easy comparison:
On my install, it is the Java Runtime Environment Settings path which can not be fixed, either by editing it directly or having Java itself find it using it's own search. This path was wrong with Update 14 and after completely removing Java from the hard drive, including traces from the Registry, it is still wrong with Update 15. Checking there would really blow my mind if yours did have the correct path, but I suspect yours too will have the extra bit added to the end, like this:
And, editing it or using Java's JRE Find feature won't fix the problem.
Mantar wrote:I have had similar experiences with MEncoder/mplayer.. unfortunatly it doesn't appear that you can disable it under linux.. which is a bummer.
I thought the whole idea of Java was to be able to have cross-platform functionality?
Mantar wrote:Here is an update on what I am trying to do to get a workable PS3MS.
Windows - DLNA Error 2006 issues
1.) Will try to downgrade Java tonight to see if it fixes the slow browsing
I suspect downgrading PS3MS would have a bigger impact, but none the less would be interested in your findings.
Mantar wrote:Linux - Mencoder and TsMuxer during transcodes it will play the video at what appears 1.5 speed, which throws the audio way off. Will not play some VOBs that the windows version of PS3MS will play. For MKVs MP4 everything works perfectly.. a bit mind boggling atm.
I quite agree, that is mind boggling.
Mantar wrote:2.) try a few mencoder options in PMS.conf
I started to look at some of the command switches for MEncoder and my first thought was, "Why is this necessary?".
Mantar wrote:At this point I don't really care which OS this runs on.. as long as one set of problems can get fixed. Time to go post over on the Linux thread also...
Now that school is coming back and summer is coming to an end, maybe we'll hear from someone.
Thank you for your continued feedback on these issues.