Universal Media Server | Forum

You have done the correct thing, the crash is before the log file is created so the only way to get the output is to run "java" instead of "javaw" as you did. The developers should have the information they need to find the problem with the stacktrace you posted. An interesting point is what is different with your system.

This is probably related to some problem with the configuration file, it is by default located in "%PROGRAMDATA%\UMS" (not under "\Users"). I guess you could check it out and see if there's an old configuration there with some invalid path specification or permissions problems.

If you know C/C++, you should have no trouble with Java, it's basically simplified C++

That said, this project is pretty large and complex so it takes quite a lot of time to get an overview over things even for people that are familiar with Java. The lack of logic and documentation many places doesn't help.

The reason it says DMS (not UMS) in the JavaDoc is because the UMS devs don't bother to go through the code they copy from Digital Media Server (DMS). DMS is a fork made by me because I disagree with the lack of focus on "code quality" in UMS, which leads to a lot of bugs and much frustration for everybody involved. The primary focus for DMS is to fix what's already there instead of constantly adding new (buggy) stuff making the situation worse. That said, when cleaning up things it will often lead to some new features or at least new possibilities for existing features. Even if the UMS devs doesn't want to do the "hard work" of fixing things themselves, they very much want to copy the fixes already done. But, since the "merging" of the code is done in the same hastily manner as everything else, it doesn't always actually lead to improvements

In any case, looking at this case, it seems to me that the problem is with some of my code that they have copied, so I guess I am somewhat responsible The error is when your PATH environment variable is split and parsed, I suspect that you might have used double quotes within the PATH..? Could you post you complete PATH? It would be nice for me to make the code robust enough to tackle it anyway...

It's good to hear that you got it to work. I still think the parsing should be more robust so that an invalid PATH doesn't prevent it from starting, so I'll have to try to find the time to do that. That said, your PATH really was invalid and wouldn't have been easy to parse "properly".

Generally, I've had nothing but trouble with upgraded Windows installations (that mostly goes for Linux as well), so I never do that. Cleaning up the PATH and other environmental variables manually isn't that hard, but it's also all the stuff in the registry that ends up pointing to the wrong place or being generally invalid. I find that life is too short for that

Just fixed the same issue. Seems like UMS doesn't like double quotes in any part of the path.