DSEAH@WPI.BITNET (05/01/88)
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?
Dave Seah --- Worcester Polytechnic Institute
+-----------------------------------------------+---------------------------+
| Bitnet: DSeah@WPI.Bitnet | We can't receive files! |
| Internet: DSeah%WPI.Bitnet@CUNYVM.CUNY.EDU | EMAIL only! Apples Rock! |
+-----------------------------------------------+---------------------------+JDA@NIHCU.BITNET (Doug Ashbrook) (05/04/88)
> 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? Yes. You are likely to have problems with any files that are in 6-bit packing mode instead of the 4-bit packing mode. This is why several of us have been requesting that contributors only use the 4-bit mode. ------------------------------------------------------------------- J. Douglas Ashbrook (301) 496-5181 BITNET: JDA@NIHCU ARPA: jda%nihcu.bitnet@cunyvm.cuny.edu National Institutes of Health, Computer Center, Bethesda, MD 20892
SEWALL@UCONNVM.BITNET (Murph Sewall) (05/04/88)
>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
SEWALL@UCONNVM.BITNET (Murph Sewall) (09/02/88)
>The problems you are describing on Info-Apple seem to be problems elsewhere. >The virus list coming out of LEHIIBM1 is coming through up to 3 times for >some people (though not for me). Part of the problem may be attributed >to people contributing to both the arpa and the bitnet list, thus getting >to the bitnet side twice. I also believe Info-Apple is merged with some >other lists too, perhaps people duplicate their posts... People shouldn't send to both info-apple@brl.mil and info-app@ndsuvm1 (it's possible with the "reply all" option, but in my experience that's rarely the problem). info-apple@brl.mil, comp.sys.apple, and INFO-APP@NDSUVM1 all carry the same mail, but the merger system is automated and doesn't (all by itself) cause duplication. Much of that CyberAIDS mail only SEEMED like the same thing over and over :-) Murph Sewall Sewall@UCONNVM.BITNET Business School sewall%uconnvm.bitnet@mitvma.mit.edu [INTERNET] U of Connecticut {rutgers psuvax1 ucbvax & in Europe - mcvax} !UCONNVM.BITNET!SEWALL [UUCP] -+- My employer isn't responsible for my mistakes AND vice-versa! (subject to change without notice; void where prohibited)
labc-3dc@e260-3b.berkeley.edu (Andy McFadden) (02/07/89)
Problems with a couple of things... ZLink returns a strange ProDOS return code when I try to save the config file (this is the version that was passed around the net; dated around the first week in January, I believe). DigiPack and DigiCopy both think that my 3.5 drive is a 5.25 drive. The problem started when I moved the UDC card to slot 6 to make room for the hard drive. It could be just an old version, but it looks like somebody took some shortcuts when coding the program (yo, dkletter?) Interestingly enough, the Optimized pack works correctly; only the standard DDD mode fails. -- labc-3dc@widow.berkeley.edu (Andy McFadden)
johnn@pro-sol.cts.com (John Nishinaga) (02/11/90)
I would like to add that many problems such as crashes, system errors, etc., are caused by bad memory chips. If you are experiencing problems with your computer, try running a RAM testing program (such as the one included if you buy a GS Ram card from AE).