Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!UCONNVM.BITNET!SEWALL From: SEWALL@UCONNVM.BITNET (Murph Sewall) Newsgroups: comp.sys.apple Subject: Re: Problems Message-ID: <8805031457.aa21203@SMOKE.BRL.ARPA> Date: 3 May 88 19:49:17 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 28 >One of the people here who is on the Amiga list said that Bitnet converts >squigly brackets "{" and "}" to colons. I put in some squiggly brackets >to see if they get converted when this message gets back to me. Would this >affect those packed Apple2L files like GS Bouncing Demo? Nonstandard conversion of characters between EBCDIC (IBM's character set) and ASCII (everyone else's) CAN cause files packed in EXECUTIONER's 6bit format to fail. Anything packed with EXECUTIONER's 4bit option will be okay because that method uses only upper case letters and Arabic numerals. I don't know, off hand, whether the GS Bouncing Demo is packed in 6bit, we keep asking everyone to please use 4 so that particular problem won't occur. Some systems translate the brackets okay but don't translate some other character(s) back to their original ASCII properly. Another common cause of failure of EXECUTIONER files to unpack is a pad character on the line between the end of the encrypted code and the BSAVE. That MUST be a (literally) blank line (stored on you ProDOS disk as two consecutive carriage returns). Kermit should download the files properly if you host's editor doesn't insist on padding blank lines when you use it to strip the headers from the top of the files. --------------------- Disclaimer: The "look and feel" of this message is exclusively MINE! (subject to change without notice; void where prohibited) ARPA: sewall%uconnvm.bitnet@mitvma.mit.edu Murphy A. Sewall BITNET: SEWALL@UCONNVM School of Business Admin. UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL University of Connecticut