🚀 go-pugleaf

(dinner time)


I too have had problems with the PCLISP version recently posted, however
the problem does not seem limited to PCLISP itself. I stripped and
catenated the files exactly as described, then I used two different
methods to get the ARC file onto my PC-AT :
  1/  uudecode on our VAX running 4.2 BSD then TFTP to the AT
  2/  TFTP to the AT and then uudecode using the Turbo Pascal program
      which was posted to the net a few months ago

Both methods produce a .ARC file of the correct length as specified
in the posting, but a COMP reveals that two half-bytes are zero in the
file which was decoded on the PC which are non-zero in the file
decoded on the VAX.

First conclusion - ONE OF THE UUDECODES (probably the PC version) 
                   DOES NOT WORK

I then ran both ARC5.10 and ARC5.12 on BOTH of the uudecode output
files. In all four cases :
  1/  the v (verbose listing) is correct
  2/  either t (test) or x (extract) CRASHES whilst in PCLISP.EXE,
      either causing garbage on-screen and premature return to DOS
      or else hanging the PC and requiring a power-off reboot.

Second conclusion - ARC is not a robust program, because it crashes
                    spectaculary instead of giving an error message.

Third conclusion - the PCLISP file is corrupted.

At the end of the exercise I have lost all faith in uudecode and ARC,
and of course do not have a working PCLISP. Since the problem occurs
in PCLISP.EXE, it can be isolated to either parts 3, 4 or 5 of the
posting, but this does not help much !
-----------------------------------------------------------------------------
Andrew Wylie   (the Zermatt Kid)

BITNET:        WYLIE@CGEUGE51 
ARPA:          WYLIE%CGEUGE51.BITNET@WISCVM 
uucp:          mcvax!cernvax!cui!wylie   
X.400/ean:     wylie@cui.unige.chunet
Hendrix lives !

-----------------------------------------------------------------------------