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 < [email protected]> 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.html#CRC > and > > http://mightyframe.blogspot.com/2015/08/qic-24-tape-data-block-format-decoding.html#CRC > > 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
