unknown@ucscb.ucsc.edu (The Unknown User) (03/12/91)
The title basically says it all.. The ShrinkIt 3.2.1 posted to comp.binaries.apple2 is corrupted. Both the DOX file and the main program had bad CRCs.. Trying to unpack the dox file crashed my copy of ShrinkIt 3.2 twice... So after booting into GS/OS (which I had to do anyway), ShrinkIT GS told me tha the CRC was corrupted. Now all I have is a bad copy of ShrinkIT 3.2.1! (Yeah yeah yeah, maybe it wasn't the greatest idea of unpacking it ONTO my only other copy of 8 bit ShrinkIt but I don't wanna waste disk space) -- <unknown@ucscb.ucsc.edu Apple IIGS Forever! CHEAP CD INFO-mail me BETTER .sig?>
gt0t+@andrew.cmu.edu (Gregory Ross Thompson) (03/13/91)
unknown@ucscb.ucsc.edu (The Unknown User) writes: > The title basically says it all.. The ShrinkIt 3.2.1 posted to > comp.binaries.apple2 is corrupted. Both the DOX file and the main program > had bad CRCs.. Wrong. The archive is fine. I just un-shrunk it with no problems at all. The only problem with what was posted to comp.binaries is that the poster cut out the "FiLeStArTfIlEsTaRt" from parts 2, 3, and 5 of the binscii files. I suppose if you were decoding with something that doesn't do any error checking, you might have gotten a corrupted ShrinkIt archive of the files, but I assure you that what was posted is not damaged. > -- > <unknown@ucscb.ucsc.edu Apple IIGS Forever! CHEAP CD INFO-mail me BETTER .sig?> -Greg T. ------------------------------------------------------------------------ ^ Any resemblance between the above | ARPANet : gt0t+@andrew.cmu.edu ^ ^ views and those of my employer, my | ^ ^ terminal, or the view out my window | ^ ^ are purely coincidental. | Bitnet : R746GT0T@VB ^
scotth@ux1.cso.uiuc.edu (Scott Henderson) (03/13/91)
In article <QbrG=K200WB9Q9AqNU@andrew.cmu.edu> gt0t+@andrew.cmu.edu (Gregory Ross Thompson) writes: > > Wrong. The archive is fine. I just un-shrunk it with no problems >at all. The only problem with what was posted to comp.binaries is >that the poster cut out the "FiLeStArTfIlEsTaRt" from parts 2, 3, and >5 of the binscii files. I suppose if you were decoding with something >that doesn't do any error checking, you might have gotten a corrupted >ShrinkIt archive of the files, but I assure you that what was posted >is not damaged. > Hmm... interesting. I posted it. Let me tell youwhat I did so someone might tell me what I did wrong. I binsciied the archive and then uploaded all 5 parts. I then used the cat command in Unix to concatenate the files into two groups. When I look at the concatenated files, they all contain the FiLeStArTfIlEsTaRts from all 5 parts. (Part 1 had the first 3, Part 2 had the last 2). However, when I looked at the posted message, the filestarts were gone. I remedied the problem by just posting each part separately, but I'd like to figure out what I messed up so that it won't happen again. -Scott > > -Greg T. > >------------------------------------------------------------------------ >^ Any resemblance between the above | ARPANet : gt0t+@andrew.cmu.edu ^ -- = R. Scott Henderson = "Some people claim that there's a = = University of Illinois = woman to blame, but I know it's = = scotth@ux1.cso.uiuc.edu = my own damned fault. = = Apple II Forever! = -Jimmy Buffet =
v060q267@ubvmsb.cc.buffalo.edu (David B Bandish) (03/13/91)
According to Andy Nicholas on GEnie, there is another problem with Shrinkit 3.2.1. In setting it up to fix a bug, he deleted the code neccessary to UnSqueeze files (such as .BSQ and .QQ files.) He intends to upload 3.2.2 to GEnie in the next few days. I posted a comment to this effect to comp.binaries.apple2 as well.
w165011@yogi.ucdavis.edu (Telon Mistar) (03/13/91)
For those of you who are having trouble with all this downloading, only to find Shrinkit (or any other program off the net) is corrupted, and you just spent X minutes (or heaven forbid, hours!) wasted in downloading...I'd suggest you try and get sciibin/nulib. Note, both are in Public Domain or Share/Free-ware. The source for both ar readily available in C. You can compile them (hopefully) on just about any machine with a 'good' C compiler. I've found that it helps ALOT to run sciibin on all the things I get off comp.binaries.apple2 (as well as various anonymous ftp sites). For one, it makes the thing smaller (the un-Binscii'd version is usually much smaller than a Binscii'd version of the same). I also don't have to worry about all the stupid Linefeed vs Carrieage Return problems as wel (although Binscii v1.03 apparently does't really care either way). It also allows me a chance to use Nulib, to check the integrity of the ShrinkIt archives...so I don't have to download the whole mss, only to find out it's no good. It's also nice that, if the stuff was compressed in the 'old' format (ie: pre-LZW2) you can unshrinkit with Nulib, so I can read docuentation/readme on my Unix rather than finally at home. hence, I can judge if the thing is worth dl'ing to begin with. I realize some of you are not on systems that can do sciibin/nulib, and I wish there were some way to fix that. But for thsoe of you who can, you really ought to think about getting the two. Hopefully this will lessen the amount of "File XX is no Good, can somone do another" post. Maybe Nulib/Sciibin ought to be placed in teh FAQ as well. Paul Hirose ccrovac@yogi.ucdavis.edu
ART100@psuvm.psu.edu (Andy Tefft) (03/14/91)
In article <QbrG=K200WB9Q9AqNU@andrew.cmu.edu>, gt0t+@andrew.cmu.edu (Gregory Ross Thompson) says: > >unknown@ucscb.ucsc.edu (The Unknown User) writes: >> The title basically says it all.. The ShrinkIt 3.2.1 posted to >> comp.binaries.apple2 is corrupted. Both the DOX file and the main program >> had bad CRCs.. > > Wrong. The archive is fine. I just un-shrunk it with no problems >at all. The only problem with what was posted to comp.binaries is >that the poster cut out the "FiLeStArTfIlEsTaRt" from parts 2, 3, and Sounds to me like unknown just concatenated all the files and used binscii on them. Binscii would have just skipped past the parts without headers, resulting in a shrinkit archive with some great big holes. Unfortunately binscii does not tell you "you still need to decode parts ...".
shrinkit@Apple.COM (Andrew Nicholas) (03/14/91)
In article <13322@darkstar.ucsc.edu> unknown@ucscb.ucsc.edu (The Unknown User) writes: > The title basically says it all.. The ShrinkIt 3.2.1 posted to >comp.binaries.apple2 is corrupted. Both the DOX file and the main program >had bad CRCs.. Don't feel so bad -- ShrinkIt 3.2.1 couldn't unpack BQY, SQ, or ACU files. ShrinkIt v3.2.2 is up on all the major online services. :-) andy -- Andy Nicholas GEnie & America-Online: shrinkit Apple Computer, Inc. CompuServe: 70771,2615 Green System Software InterNET: shrinkit@apple.com I'm doing this on my own time, so I don't speak for Apple.