17 Nov
2015
17 Nov
'15
2:55 a.m.
I've encountered a new challenge with the CRC now, it's from the data
blocks written by the Kennedy 6450/6455 Tape Drive.
The below message is to the creator of CRC_RevEng about this topic, but
since several here have been so helpful to me on understanding CRCs (and
Chuck, you referred me to CRC_RevEng), I thought I would put this out to
this group as well.
Again, I really appreciate the feedback!
Thanks,
-AJ
On Tue, Nov 17, 2015 at 1:10 AM, Convergent MightyFrame <
mightyframect at gmail.com> wrote:
Greg,
I am extremely impressed by the CRC_RevEng program you wrote. It is quite
amazing. I have a unique problem using it, and I was hoping you could help.
Instead of trying to articulate all of the complexities in an email, I
recorded a YouTube video explaining my dilemma and demonstrating the
result. Please watch that here:
https://youtu.be/nH-tfbvXYrI
Please forgive me if I ramble on in the video, but I hope it effectively
describes the problem, and how I arrived at it.
The web pages I reference in the video is my own, at:
http://microtechm1.blogspot.com/2015/09/kennedy-6450-tape-drive-data-format…
and
http://mightyframe.blogspot.com/2015/08/qic-24-tape-data-block-format-decod…
The long-data-block files I use as demonstration in the video are attached.
I would be very appreciative if you could point me toward any available
work-arounds to this issue.
--
Thanks!
-AJ Palmgren
515.460.6393
http://MightyFrame.com
http://MicrotechM1.blogspot.com
--
Thanks,
-AJ
http://MicrotechM1.blogspot.com
17 Nov
17 Nov
8:42 a.m.
AJ
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.
--
Andreas
10:45 p.m.
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:
AJ
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.
--
Andreas
--
Thanks,
-AJ
http://MicrotechM1.blogspot.com
3164
days inactive
3165
days old
2 comments
2 participants
participants (2)
-
microtechdart＠gmail.com -
ramdyne＠gmx.net