I noticed there was no -interval argument as well.  Pretty sure it's using a default internal if there's no -interval argument present.  I've got two rigs running NPM 1.3 that use different interval times, although I've never manually the interval manually... intentionally.   I think I might have copied and used a start.bat from an older version of the miner that had an interval argument in it the first time I ran NMP 1.3.  Pretty sure it picked it up and remembered it, so I'd bet you can add it back in if you wanted to.  I was waiting for "trust" to get to 100% to check earnings accuracy so I wasn't willing to add a different -interval argument and restart the miner to test, but if MrPlus doesn't chime in before I get home, I'll probably give it a shot tonight.

As for replacing the miner, have a look at post #57.  Roman's got you covered.

I had the two miners open when I was benchmarking Neoscrypt.  After I removed the NeoScrypt algo, everything else seemed to work as well as NemosMiner typcially has.  Palgin's HSRminer also didn't close when the benchmarking should have been finshed, but I've often found that to be the case with other algos/miners in NemosMiner as well.

When benchmarking, if the miner doesn't close after the second interval it will likely run until you stop it.  When I see that, I shut the script down and restart, that usually resolves the issue.... although it didn't in the case of HSRminer.

So ya, +1 here to remove it until you can figure out what the problem is.  It's too bad, it's the fastest Neoscrypt miner I've tested.

From what I understand, it's the logic in how Nplus decides which is the most profitable algorithm.  Not sure if Nemos is incorporating MrPlus' most recent changes to his miner, because if he is, the net results are going to be very similar.