petera@utcsri.UUCP (Peter Ashwood-Smith) (08/02/86)
[line eater]
Hello Usenet MS-DOS users,
The following 5 articles are a uuencoded archive of the latest PC-LISP
distribution V2.12. You need the utilities uudecode either on your host or PC
and you need a recent copy of ARC on your PC. Both of these have been floating
around on the net for the last while so if you do not have them you should be
able to drum one up from a friend or neighbouring site.
You can get PC-LISP off the net by following these instructions EXACTLY.
Sorry to hand hold but it usually saves the net from reading a few million
'It don't work!' flames. I have downloaded these files and reconstructed
PC-LISP without problem so it should work for you too.
1) Write article 1 of 5 to a file called 'lisp.1'
" " 2 of 5 " " 'lisp.2'
. . . . . .
Write article 5 of 5 to a file called 'lisp.5'
2) Edit each of the files lisp.1..lisp.5 and remove all the lines
at the top of the file up to and including the 'CUT HERE' line.
Also delete any blank lines from the bottom of the files. They
should either end with a line "M........" or "end ...". This
is important because some versions of uuencode are confused by
blank lines.
3) Concatenate the files into one large file as follows:
cat lisp.1 lisp.2 lisp.3 lisp.4 lisp.5 > lisp.uuu
Then check that the file lisp.uuu has the 'begin' at the front
and the 'end' at the end. You may also want to make sure there
are no blank lines in the file between the 'begin' and 'end'
lines. Note lisp.uuu should be about 252918 bytes.
4) Uudecode the file as follows:
uudecode lisp.uuu
There should now be a file called exe.arc. This file is an
archive of the entire PC-LISP distribution. The file should be
about 183551 bytes. If it is much bigger look for blank lines
in lisp.uuu and repeat step 4. If it is much smaller check
the files lisp.1...lisp.5 to see if any were truncated by
the mailer. A message will be at the end of the file if this
is the case. This should not happen because each file is less
than 64K.
5) Ready you KERMIT or XMODEM file transfer program and download
the file exe.arc to your PC using a BINARY TRANSFER PROTOCOL.
If you use a text protocol it won't work! This will take a
while. When you get the file on your PC you should run the
arc program to test the integrity of the archive before trying
to do anything with it. You can do this as follows:
arc t exe.arc
Which should hopefully report no errors. Then try the command
arc v exe.arc
You should see something like the following:
Name Length Stowage SF Size now Date Time CRC
============ ======== ======== ==== ======== ========= ====== ====
DRAGON.L 1139 Crunched 39% 697 14 Apr 86 10:44a F435
HANOI.L 775 Crunched 36% 502 15 May 86 3:10p 4C8E
MATCH.L 8549 Crunched 55% 3860 8 May 86 12:30a 0033
PC-LISP.DOC 149543 Crunched 58% 63454 1 Aug 86 10:21a E7A4
PC-LISP.EXE 124324 Crunched 25% 94303 31 Jul 86 11:01a B45B
PC-LISP.L 9710 Crunched 51% 4784 23 Jul 86 3:38p D960
QUEENS.L 2877 Crunched 49% 1474 15 May 86 3:05p 03BD
SUZY.ARC 12373 -- 0% 12373 23 Jul 86 4:14p C01E
TURTLE.L 3476 Crunched 48% 1841 14 Apr 86 10:47a 1CC9
==== ======== ==== ========
Total 9 312766 42% 183288
6) If you reach this point and all is ok you can unpack the archive
and play with PC-LISP. To unpack the archive you can type the
command:
arc x exe.arc *.*
The file SUZY.ARC is an archive of a program called SUZY.L which
was posted to net.lang.lisp a few months back. It is a Latin to
English translator. You should make an appropriate directory
and unpack it.
7) Your done, read the manual and away you go.
PROBLEMS?
If the above process does not work for you there are a number of
places you could have messed up. First make sure the files are in the
right order, ie article x of 5 is called lisp.x. Make sure you cut out
the blank lines from the bottom and the header at the top. Make sure you
cat'ed them together in the correct order ie lisp.1 lisp.2 lisp.3 lisp.4
and lisp.5. Make sure you downloaded the exe.arc file using a BINARY
transfer protocol option. If you downloaded the lisp.uuu file to do the
uudecoding on your MS-DOS machine make sure that you used a TEXT transfer
protocol option. The most common mistake is to use the wrong HOST to MICRO
transfer protocol option.
Finally look for corrupt files. This will show up when you get it to
your PC. If most of the files in the archive are ok but one or two are
corrupt as reported by 'arc t exe.arc' then something is wrong with the
files that you got off the net. If this is the case then email me and I
if enough people have trouble I will redistribute. Otherwise you can mail
me 2 blank good quality diskettes + $1.50 and I will mail the program back
to you. Unix compilable C source code is also available. This requires 3
diskettes. Good luck and have fun.
Peter Ashwood-Smith,
#811, 120 St Patrick St.
Toronto, Ontario,
M5T 2X7
Phone# (416) 593-7574. wlb@rruxp.UUCP (B Boutin) (08/14/86)
> The following 5 articles are a uuencoded archive of the latest PC-LISP > distribution V2.12. You need the utilities uudecode either on your host or PC > and you need a recent copy of ARC on your PC. Both of these have been floating Please do not post UUENCODED data to this newsgroup! There is net.source.(whatever) news groups for this purpose! I, for one, print out news groups before reading them. Postings like this costs big bucks! UUENCODE costs big for nothing! So, please consider before posting code. Thanks ------ Bill Boutin /-----\ Bell Communications Research, Inc. < 0 0 > \ < / "The dice are rolling!" \0/ Oh, nooooooooooooo!!! - -- Bill Boutin /-----\ Bell Communications Research, Inc. < 0 0 > \ < / "The dice are rolling!" \0/ Oh, nooooooooooooo!!! -
petera@utcsri.UUCP (Peter Ashwood-Smith) (08/14/86)
> > > The following 5 articles are a uuencoded archive of the latest PC-LISP > > distribution V2.12. You need the utilities uudecode either on your host or PC > > and you need a recent copy of ARC on your PC. Both of these have been floating > > Please do not post UUENCODED data to this newsgroup! > There is net.source.(whatever) news groups for this purpose! > I, for one, print out news groups before reading them. > Postings like this costs big bucks! UUENCODE costs > big for nothing! So, please consider before posting First of all net.sources is not appropriate for uuencoded executables as I have been told the first time I distributed PC-LISP. This is because the distribution is not source code, it is executable, raw, binary, 1's and 0's. It must be uuencoded otherwise the news software will not handle it so UUENCODE is a must. Were I to post the source code to net.sources it would be much bigger than the UUENCODED executable and would therefore cost even more to distribute. I do not distribute the source code over the net for this reason. As far as automatically printing the news group may I suggest a short shell script to check the sizes of the articles before printing them, this is not too hard to do. If the readers of net.micro.pc feel that the distribution of executables in uuencoded + arc format is inappropriate then speek up now or forever hold your peace. I guess if enough people do not like it we could start up a news group net.binaries.uuu or some such thing. Peter Ashwood-Smith, Happy user of ARC, PC-SHELL, CONCH, COMPRESS,...etc. University of Toronto The Great White North.