Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!mips!bridge2!jarthur!spectre.ccsf.caltech.edu!tybalt.caltech.edu!madler
From: madler@tybalt.caltech.edu (Mark Adler)
Newsgroups: comp.sys.handhelds
Subject: Re: Downloads of HP-48SX binary files.
Message-ID: <1990Mar22.050520.29942@spectre.ccsf.caltech.edu>
Date: 22 Mar 90 05:05:20 GMT
References: <1990Mar21.142101.28032@cec1.wustl.edu> <3590@sunspot.UUCP> <1461@uc.msc.umn.edu> <1990Mar21.225133.2561@santra.uucp>
Sender: news@spectre.ccsf.caltech.edu
Organization: California Institute of Technology, Pasadena
Lines: 39


Oops.  My fault---it seems I didn't achieve binary mode in the kermit
transfer from my PC to my NeXT.  I redid it all, re-ftp'ed it to
gmuvax2.gmu.edu (in "new"), and then reversed the process all the way
to my calculator to make sure it all worked.  It does.  Here is the
list of files and their proper lengths, as they are on gmuvax2:

-rw-r--r--  1 ftp         13713 Mar 21 23:40 apdir
-rw-r--r--  1 ftp           124 Mar 21 23:40 appt
-rw-r--r--  1 ftp          4924 Mar 21 23:40 appt.txt
-rw-r--r--  1 ftp          6877 Mar 21 23:40 clk
-rw-r--r--  1 ftp          9402 Mar 21 23:40 clk.txt
-rw-r--r--  1 ftp          1229 Mar 21 23:40 epsprint.lib
-rw-r--r--  1 ftp          4770 Mar 21 23:41 epsprint.txt
-rw-r--r--  1 ftp          5472 Mar 21 23:41 grob2tif.exe
-rw-r--r--  1 ftp          1363 Mar 21 23:41 grob2tif.txt
-rw-r--r--  1 ftp           865 Mar 21 23:41 inprt
-rw-r--r--  1 ftp          2660 Mar 21 23:41 inprt.txt
-rw-r--r--  1 ftp         47117 Mar 21 23:42 pclink48.tar.Z
-rw-r--r--  1 ftp          1136 Mar 21 23:42 pclprint.lib
-rw-r--r--  1 ftp          4781 Mar 21 23:42 pclprint.txt
-rw-r--r--  1 ftp          2831 Mar 21 23:42 stpwatch.lib
-rw-r--r--  1 ftp          3936 Mar 21 23:42 stpwatch.txt
-rw-r--r--  1 ftp          1401 Mar 21 23:42 usag
-rw-r--r--  1 ftp          3822 Mar 21 23:42 usag.txt

Just by the way, I have had no problems with the HP-48SX kermit,
except for the Lost Memory problem (there are other situations
besides bringing in a zero-length file that causes it).  I always use
three character "checksums" however.  I've not tried the one or two
character checksums.

(For the edification of kermit users, the reason I blew the transfer
the first time is that I didn't realize that the kermit being served
is the one that controls the file type (text or binary), so setting
binary before "serv" on the mainframe kermit had no effect.)

Mark Adler
madler@hamlet.caltech.edu