macausla@newton.ccs.tuns.ca (Robert MacAusland) (08/11/90)
Has anyone successfully downloaded and decoded files from 131.215.139.100? I received 21 parts to the Ssmithbootdisk file, stripped off the mail headers, concatenated them all together using the Unix Cat command, and then tried running the file through both uudecode and Tar - uudecode wouldn't touch the file and Tar said their was a directory checksum error. I tried this with the 3200color demo as well and received the same results. Can anyone offer any advice? -- /* Robert MacAusland -> macausla@newton.ccs.tuns.ca */
toddpw@tybalt.caltech.edu (Todd P. Whitesel) (08/14/90)
macausla@newton.ccs.tuns.ca (Robert MacAusland) writes: >Has anyone successfully downloaded and decoded files from >131.215.139.100? I received 21 parts to the Ssmithbootdisk file, >stripped off the mail headers, concatenated them all together using >the Unix Cat command, and then tried running the file through >both uudecode and Tar - uudecode wouldn't touch the file and >Tar said their was a directory checksum error. I tried this >with the 3200color demo as well and received the same results. >Can anyone offer any advice? 1. README files are there for a REASON!! get and more them, and be enlightened. 2. uudecode was not used to prepare ANY of the files in the apple2 directory. If text encoding was used (most of the time), it was BinSCII 1.0.3. 3. tar is no longer being used on the files. If you FTP to 131.215.139.100 now, you will find that all the .tar files have been replaced by directories filled with cryptically named binscii pieces. All I did was tar -xvf the tar files and delete the tar files. I will be implementing a better solution soon. Todd Whitesel toddpw @ tybalt.caltech.edu