Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!chensun1!klf1305
From: klf1305@chensun1.tamu.edu (Kelly L. Fergason)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: VRAM386 in SIMTEL20 corrupted??
Keywords: simtel20 vram386.zip sysutl
Message-ID: <13381@helios.TAMU.EDU>
Date: 17 Mar 91 06:22:43 GMT
References: <wong.669006960@scapa> <5412@vela.acs.oakland.edu> <wong.669112367@scapa> <valley.669143831@gsbsun> <wong.669178528@scapa>
Sender: usenet@helios.TAMU.EDU
Organization: Texas A&M University, Chemical Engineering
Lines: 23

In article <wong.669178528@scapa> wong@cs.UAlberta.CA (Brian Wong) writes:
>
>
>
>Hi,
>
>So far nobody can tell me why my procedure:
>ftp - uuencode - transfer - uudecode - pkunzip
>WORKS for vram386.zip from 128.214.12.37
>but fails for the same(??) file from simtel20 and 128.252.135.4.
>I use the above procedure for many other programs and it has not
>failed.


	Well, I don't know about anyone else on the net, but
	for me, every once in a while, things just don't work.
	By this, I mean that you do everything right, but the
	results just are not correct.  In my experience, it
	seems to be the ftp part of the procedure.  I usually
	just attribute it to gremlins in the lines, and do
	it again, and it usually works.  

Kelly Fergason