Path: utzoo!utgpu!news-server.csri.toronto.edu!csri.toronto.edu!byu
Newsgroups: comp.sys.handhelds
From: byu@csri.toronto.edu (Benjamin Yu)
Subject: Re: W A R N I N G  compress & ftp can corrupt hp48 bin files
Message-ID: <1990Oct15.172722.25374@jarvis.csri.toronto.edu>
Keywords: Ouch!
Organization: CSRI, University of Toronto
References: <9006@jarthur.Claremont.EDU> <40717@eerie.acsu.Buffalo.EDU> <1990Oct15.170509.9366@nntp-server.caltech.edu> <40831@eerie.acsu.Buffalo.EDU>
Date: 15 Oct 90 21:27:22 GMT
Lines: 45

In article <40831@eerie.acsu.Buffalo.EDU> cloos@acsu.buffalo.edu (James H. Cloos) writes:
# In article <1990Oct15.170509.9366@nntp-server.caltech.edu> madler@piglet.caltech.edu (Mark Adler) writes:
# >
# >                   This fellow has a very common syndrome among computer
# >users, which is to assume anything possible before assuming that oneself is
# >doing something wrong. Of course, that is the FIRST thing that should be
# >assumed---I know I do.
# 
# Given that this was posted, so is this:
# 
# I must object to Mark's characterization of me wrt asuuming something else
# is at fault before assumeing I am.  In general AND IN THIS SPECIFIC CASE,
# I did quite the opposite.  In fact, I first started noticing these problems 
# a few weeks back, but waited so long to post because I was trying various
# things to prevent/correct the symptoms.  None of these succeeded.
# 
# *SOMETHING* is going wrong, that is certain.  Multiple tests usw have led
# me to the opinions expressed in my first posting.
# 
# I also seriously feel that the above quoted comment was not called for, I 
# so mauch as told him that in a mail file earlier today (in response to a
# reply by Mark to my 1st post).
# 
# {If nothing else, leaving that comment out would have reduced badwidth
# usage, but as much as I hate to see flames in c.s.h, I do not enjoy
# public attacks either.  Comments like that belong only in the mail.}
# 
# -JimC
# --
# James H. Cloos, Jr.		Phone:  +1 716 673-1250
# cloos@acsu.buffalo.edu		Snail:  PersonalZipCode:  14048-0772, USA
# rutgers!ub!cloos

Well, call me whatever you like, but I experienced different output from
different FTP and UUDECODE programs (ALL FLAGS SET THE SAME!!).  I have
tried ftp once to get an uuencoded file from a site, downloaded to my PC for
uudecode and then to my 48, and nothing worked.  But if I uudecoded the file
on my Unix box and then uuencoded it again and then download it to my PC,
uudecoded it and then to my 48, it works.  So, unless everyone has the same
ftp, uudecode, uuencode, compress, etc. functioning the same in all platform,
I would hesitate to say outright that the problem is simply setting BINARY
in the file transfer!!!

Benjamin Yu
byu@csri.toronto.edu