Must press Stop and Resume buttons for every trace

I just upgraded from free version 1.10 to 1.20. I have the "# of times to trace" set to 1. When I enter an address and press "Trace", I now have to press "Stop" and then "Resume" to trace again or try another address. In the prior version, the program would present the "Resume" button without the intervening "Stop" button.

If I enter "2" for "# of times to trace", the program works correctly the *first* time... i.e. it traces twice and then presents the "Resume" button. But once you press the "Resume" button it thereafter forces you to press the "Stop" button again before pressing "Resume".

Is there a fix for this?

This looks to be a bug - which no one has reported yet (well, they have now!). We'll have to take a look and see if we can find any workarounds or otherwise.

Thanks for the report.

- Pete

Has there been any progress on this?

We've not found any workarounds for it. We have this logged as a bug to be fixed in the next release.

Thanks for the report and followup.

- Pete

So based on your past release schedule, I can expect something in 2013? <img src="/forums/images/graemlins/tongue.gif" alt="" />

I'm not sure what your intentions are with the freeware version, but if the idea is to tempt people to upgrade to the purchased version then you might want to consider replacing the broken version with the one that worked.

Well ... this bug is pretty "corner case" and hardly affects anyone (you're the only one to report it). We fix major bugs as quickly as possible, but let minor ones "pile up" a bit and release them in batches. We've just not collected enough bugs to release this fix yet.

You're certainly welcome to go back to the previous 1.1 release (http://www.nessoft.com/dlm_start.php?ProgID=3) if the latest version has show-stopper problems for you.

- Pete

I may be the only one to have reported it, but isn't this the way the program now behaves? How can a bug that affects anyone/everyone who uses the product be considered a "corner case"? If you're implying that I'm the only one that's seeing this behavior and the program works correctly for others, please let me know so I can try and find out what's wrong with my setup.

And yes, I immediately went back to the prior version after seeing how the latest version behaves.

This is a bug in the way it works - for everyone. The "corner case" is that most people don't have "# of times to trace" set to 1. Most people use unlimited.

OK, that makes sense. Thanks for the reply.