RevEng CRC model on really really long messages of 4096 bytes
microtechdart at gmail.com
Tue Nov 17 21:45:21 CST 2015
Thanks for the feedback here, Andreas, very good question.
Actually, I was suspecting that I was running into the maximum length of
the command line at least with Windows, and possibly with Linux, even
though it displayed the full message in the terminal window.
This is why I wanted to do the youtube video to actually show a result and
how I arrived at it, and direct it to the software designer, rather than
just try to describe it...yet, make it fully public so anyone could weigh
in on it if they wanted to.
There are a number of variables, and at this point, I'm just guessing at
the solution, without enough knowledge yet to look "under the hood" of
CRC_RevEng, or even CRCs themselves, and get a fuller understanding of
what's happening behind the scenes.
I'm hoping that he can run some kind of test that shows that his program
is, indeed, processing the entire 8196+ character message/CRC parameter.
Next best, would be someone with great experience using CRC_RevEng to show
me how to run those diagnostics myself, and I've just missed them because
I'm a newbie at this.
On Tue, Nov 17, 2015 at 7:42 AM, Andreas Sikkema <ramdyne at gmx.net> wrote:
> Are you sure you're not running into the maximum length of a command line?
> I haven't used Windows in a very long time, so I am not sure what the
> current maximum is, but with > 16k characters I would assume it is at
> least an option.
More information about the cctech