OK, that was my stupid mistake - I shouldn't have changed the default scanning delay. I meant that to be a temporary change for use while debugging. . . People are used to the current defaults. I will fix it in a "debug" release, along with other fixes as people report in. When Juk gets back, we'll get it posted.
I would like to know if it's because of optimizing based on profiling on MY machine, or what. . .
Can you try this?
Make a file called run.bat with the following in it:
<font class="small">Code:</font><hr /><pre>@echo off
FreePHG.exe -prof</pre><hr />
The "-prof" turns on profiling mode, which will report how many "scans per minute" your machine produces. The "scans per minute" line appears once in a while, and it starts with a lot of spaces, so you'll see it off on the right side of the DOS box in which it's running.
If you could fire this batch against .06 and against .07, I'd be curious to see what kind of numbers you turn up.
If you want to try running .07 with a 1,000 ms delay, use this:
<font class="small">Code:</font><hr /><pre>@echo off
FreePHG.exe -d 1000</pre><hr />
The "-d 1000" changes the delay to 1000. Don't use "prof" mode at the same time when running, because the profiling work slows things down a tiny bit.
Thanks!