Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!cmcl2!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn ) Newsgroups: comp.sys.apple Subject: Re: binscii file format Message-ID: <9722@smoke.BRL.MIL> Date: 26 Feb 89 03:05:32 GMT References: <464@duteca2.UUCP> <9455@bloom-beacon.MIT.EDU> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 51 In article <9455@bloom-beacon.MIT.EDU> dcw@athena.mit.edu (David C. Whitney) writes: >Any questions? YES! >immediately following is the translation alphabet What is this alphabet, normally? (I could look in some posted file but then I'd have to wonder whether some mailer has already messed it up.) > FSAMPLE followed by blanks to fill out 15 chars Why isn't this 6SAMPLE (with no padding) instead? It seems that you're requiring the filename to contain spaces, which ProDOS does not allow (but DOS 3.3 did, and perhaps some GS/OS file systems might). > then CRC checked: Why isn't the filename included in the CRC? > File info (date, #blocks, type, etc) What format? Also, are the sizes etc. in ASCII decimal or are they binary (little-endian? how many bytes?) > CRC How is this CRC computed? >Each line is 64 chars long followed by What if the file size is not an integral multipel of 64 bytes? >the last line is the CRC check of the file. How is this CRC computed? >Bytes are coded 3 at a time into 4 characters (6-bit encoding). What is the specific encoding scheme? Also, how do you handle the resource fork, different file system types, etc.? I'd appreciate enough information so that I can write a program to turn these files back into reasonable ones on my UNIX system before transfer to my Apple. I don't want to have to do this on my Apple, and I don't want the added file transfer time that the encoding forces.