Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!psuvax1!brutus.cs.uiuc.edu!samsung!cs.utexas.edu!natinst!rpp386!aubrey
From: aubrey@rpp386.cactus.org (Aubrey McIntosh)
Newsgroups: comp.os.minix
Subject: Re: listserv file decoding
Summary: modify Unpunch.c
Message-ID: <18080@rpp386.cactus.org>
Date: 2 Mar 90 16:17:17 GMT
References: <27395@cup.portal.com> <27404@cup.portal.com>
Reply-To: aubrey@rpp386.UUCP (Aubrey McIntosh)
Distribution: usa
Organization: vima, Austin TX
Lines: 30

>I am in the process of upgrading to ST 1.50. Unfortunately I didn't
>download the the PC upgrades when they were posted.  I have, however,
>started to pull them off of LISTSERV.  My problem is this:
> After 1 & 2 , I requested and received 2 files in LPUNCH format as
>well as the LPUNCH info packet with the c conversion routine.
>The LPUNCH conversion didn't work at all. It complains on just about 
>every line - either premature EOF or lines over 80 characters.  I'm in the
>process of debugging this - but I would like to be able to use the uuencoded 
>files I already have.
>
>  Does anyone have a way out of this - Just what is it I have?
I pulled most of the 1.3 material from the ListServ at NoDak.  Approximately
10 of the 35or 40 files arrived 'short'.  Those files gave some usable
  
info in the shar'ed portions.

All the mail headers were over the 80 byte line limit, and Unpunch did not
ignore them---the getline routine barfed.

I added an Isheader variable, and skipped the abort code while it is true...
If I had the old version I'd post the diffs...

I suppose I can mail it to anyone who requests it.  


-- 
Aubrey McIntosh        
comp.os.minix, comp.lang.modula2, soc.culture.celtic         
Austin, TX 78723 
1-(512)-452-1540  (v)