🚀 go-pugleaf

Stan, dylan, Karl & several others,
   I'm really sorry/annoyed about this. It seems MindLink uses the
 backslash character (ascii $5c) as an escape character, ie. it eats
 backslashes & sometimes the next character if it fits one of MindLink's
 commands. This plays all hell with uuencoded files...
 ---Attempt zero---
   Let BS = BackSlash
   There are 15 backslashes in pacd.sh, but only lines 2 & 9 seem to be
 corrupted (as well as the header).
        >sed 's/^XX//' <<   HAR_EOF > pacd4.zuu                    -HDR
                          ^
                         BSSHAR_EOF

XXM_0(!F`,``'$```!D%(MUF,\!```)P,```$```````````!004-$-`"3F@``/   -L2
                         ^^
                        BSBS!``

XXMS,NUQ79$,!8T`V&<:4P"B(3%L@(A`M;IY1(`((W;'^Q,"O.[_^?9GYN5!%G   -L9
         ^
        BSR9$,!

   Now when these lines get to you they will be corrupted by the ML editor
 again. Where you see the ^ char below with BS below, insert one
 backslash. The other characters are the same.
 ---Attempt one---
   My other alternative, is to try to trick the ML editor here by
 substituting BSBS for BS. ;-) How do these lines look?

sed 's/^XX//' << \SHAR_EOF > pacd4.zuu                              -HDR

XXM_0(!F`,``'$```!D%(MUF,\\!```)P,```$```````````!004-$-`"3F@``/   -L2

XXMS,NUQ7\R9$,!8T`V&<:4P"B(3%L@(A`M;IY1(`((W;'^Q,"O.[_^?9GYN5!%G    -L9

 ---
   Hopefully, now one way or the other, you will be able to reconstruct a
 valid .sh file. The ironic side is that PACD is a really simple little
 program. Open expansion.lib & do FindConfigDev until done.
   As for the double XXs, I'm not sure why that happened. I am using a
 Dave Wecker Shar (12388 bytes). It unshared on my system, so I didn't
 worry about it.

  "You can't get blood out of an illusion." -The Lickerish Quartet
    Harvey Taylor               Meta Media Productions
         uunet!van-bc!rsoft!mindlink!Harvey_Taylor
                a186@mindlink.UUCP