[Info-vax] wrong file format

Bill Gunshannon bill.gunshannon at gmail.com
Thu Dec 31 12:50:56 EST 2020


On 12/31/20 12:36 PM, Phillip Helbig (undress to reply) wrote:
> In article <rsk1o2$nqo$5 at gioia.aioe.org>,
> helbig at asclothestro.multivax.de (Phillip Helbig (undress to reply))
> writes:
> 
>> In article <rsi2lj$du4$6 at dont-email.me>, Simon Clubley
>> <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>
>>> On 2020-12-28, Phillip Helbig (undress to reply) <helbig at asclothestro.multivax.de> wrote:
>>>>
>>>> In the end, I managed to transfer it again (don't ask!) and somehow,
>>>> magically, it was OK.
>>>>
>>>
>>> If you still have the original version around, what does TECO do
>>> to it if you read it in and write it out again ?
>>
>> In order to avoid confusion, I deleted the bad version.  However, it
>> didn't look like the files which I've just opened and closed in TECO in
>> order to fix them.
> 
> Same problem today, but with a much smaller file (30 instead of 200,000
> blocks).  I loaded it into TECO then exited, then deleted the extra
> blank lines with a TECO learn sequence.  Still some problem.  I then
> went to the post-TECO file and noticed that a few lines had been broken
> at the wrong place (they are supposed to be all the same length).  I
> fixed those by hand with EDT (not possible with 100 MB), then TPU again.
> In the end there was still something not 110% correct, but I could still
> use the file so all is well now.  :-)
> 

Can you tell us where these files come from and how they get on the
VMS System?

bill




More information about the Info-vax mailing list