I just finished making the changes I mentioned in another thread to my InpReader class. Although I had not encountered any .inps that it would misdetect, theoretically it was possible, so that's why I improved it. The new version does everything correctly for the testbed of .inps I use for this class, but of course, that is only a tiny fraction of the .inps on MARP, so if ever there are problems, please let me know which .inp causes problems.

For those interested in the latest versions (using this new InpReader) of my chkDIPs/chkDIPsGUI, InpHisto, and InpSpeed programs, please let me know.

I am going to send the source code for the new InpReader class to Chad shortly, and I am also going to send him the source code for InpSpeed so that he can combine it with analinp. Of course, InpSpeed is only meant for m35tg3/win35tg3 recordings.

InpSpeed is basically the same as Mark Longridge's Checker program, but, unlike Mark's program, the filename is specified on the command line. Furthermore, it does not have the bug in Mark's program where it sometimes does not display the correct number of frames (usually off by one), nor the bug that it does not detect frames where the speed was 256% or more.

Cheers, Ben Jos.

-- Anonymous, June 15, 2000

Answers

can you send me inpspeed.cpp again, i didn't realize you wanted ME to combine it. i was hoping to just send you analinp.cpp so you could combine it :)

-- Anonymous, June 16, 2000

Oh, sure. I can combine them too. Just send me the source code for analinp then.

Cheers, Ben Jos.

-- Anonymous, June 16, 2000