Ok, so we stated burstpowernetwork.ml, have a testing pool and wallet there. Tweaking the settings for NXT means restarting the wallet sometimes. That is not an easy task sometimes. A simple CTRL+C is good most of the time, but often that sticks. Using either task manager or closing the console window is not the way to go, but sometimes that is the only choice. About half the time if we do this, the wallet will never start again until the DB has been replaced. NXT starts in its own window and if working stays open. Any error and it shuts down.
The code line going in is
start "BURST" "%%~$path:f" -cp burst.jar;lib\*;conf nxt.Nxt
On our server the PATH is set so the line is actually...
start "BURST" java.exe -cp burst.jar;lib\*;conf nxt.Nxt
I gather that is saying to use java.exe with burst.jar as a library and nxt.Nxt(within the lib) as a loading point for the config. I have extracted the jar and don't really have the time to pick through and find that point where the console is opened. If so, I would simply put a java pause in and that way I could see an error and go from there. The nxt logs are not great at all. Set all the settings to FINE and still just get the basics. I either need a better shut down method or a better start up method.