petera@utcsri.UUCP (Peter Ashwood-Smith) (08/16/86)
[ line eater ]
Ok, The following articles 1,2 and 3 contain a split uuencoded
archive of the PC-LISP.EXE. The "ARC V" output should be like this:
Name Length Stowage SF Size now Date Time CRC
============ ======== ======== ==== ======== ========= ====== ====
PC-LISP.EXE 124324 Crunched 25% 94303 31 Jul 86 11:01a B45B
==== ======== ==== ========
Total 1 124324 25% 94303
Again, sorry to handhold those who know what they are doing but for
the sake of less experienced folks, follow these instructions EXACTLY:
#1 - Save article 1 as lisp.1, 2 as lisp.2 and 3 as lisp.3
#2 - If (you have uudecode on your MS-DOS machine) then
download now lisp.1,lisp.2,lisp.3 using a TEXT mode protocol.
Continue from #3 on your MS-DOS machine.
else
Continue from #3 on the UNIX host.
end if
#3 - Edit each of lisp.1,lisp.2,lisp.3 and remove the stuff
at the top of the file up to and including the ==== CUT ===
line. Also make sure there are NO blank lines at the end
of file.1 and file.2. file.3 may have blank lines at the
end without any problems.
#4 - if (you are now on your MS-DOS machine) then
do command "copy lisp.1+lisp.2+lisp.3 lisp.uuu"
else
do command "cat lisp.1 lisp.2 lisp.3 > lisp.uuu"
#5 - do command "uudecode lisp.uuu"
#6 - If (you are on NOT yet on your MS-DOS machine) then
You should have a file called exe.arc on UNIX. You
should download this file to your MS-DOS machine
using a BINARY protocol.
else
Do nothing.
end if.
#7 - (Now on MS-DOS machine)
Check that you have a file called exe.arc
do command "arc t exe.arc".
If (you do not get a "pc-lisp.exe ... okay" message)
Read the list of problems.
Go back to step 1 and try again.
Do not run pc-lisp if it fails the "ARC T" test, it
will almost certainly crash your machine.
Instead, go back to step 1 and try again.
end if.
#8 - do command "arc x exe.arc pc-lisp.exe".
Since pc-lisp.exe passed the checksum test in step #7
you should now have a working version of PC-LISP.
End ... whew!
LIST OF PROBLEMS (arc indicates bad checksum on PC-LISP.EXE)
~~~~~~~~~~~~~~~~
1 - You got the article numbers out of sequence with the file numbers.
eg article 1 of 3 is file.1, 2 is file.2 and 3 is file.3.
2 - You got the files out of sequence in step 4. Should be 1,2 and 3.
3 - You deleted DATA from the file(s) when editing them. You should
only remove data from the front of the file and blank LINES from
the end of the file. Don't remove blanks from the end of a data
line(s) at the end of the file. Eg.
MabAFKLJDFL DFKJSFLKSDFJKSDFSDLFKSDFLSDFLKSDFKLSDFLKSDkkkj;
M123489715(*&(*&238172348712348712938471298347123489
^^^^^^^
||
Don't remove these
4 - You edited before downloading the file.1..file.3 to your PC and
blank lines at the end of the file were introduced this way. You
should edit them immediately before the uudecode step on the same
machine.
5 - You did not download the file(s) with the correct protocol. Use
BINARY for the exe.arc or TEXT for file.1, file.2 and file.3.
If you downloaded using a simple TEXT save program then you
may get undetected errors. You should try a few times before
giving up. If you downloaded using KERMIT or XMODEM there should
be no errors introducable in this step (IF YOU GET THE PROTOCOL
RIGHT).
6 - The file(s) were clobbered during transmission from one UNIX host
to another. I don't know how this happens but it does. Your only
course of action is to send me 2 good quality blank diskettes
and I will put the entire executable on disk for you and send them
back. (Include about $1.50 for postage). The address is:
Peter Ashwood-Smith
#811, 120 St Patrick St.
Toronto, Ontario,
M5T - 2X7
CANADA.
Phone: 416-593-7574