🚀 go-pugleaf

I would like to apologize for not including tipsz and tiprz executables
together with tipx.  I just forgot and I am afraid that currently there
in no way I could rectify that error.  My numerous attempt to upload
to cs.orst and sonata(nova) the latest version of Kermit for Next all
failed.  Any other generally accessible archives where I should try?
 
Here is a guide to possible troubles with tipx hacky software.
A) I cannot compile missing tipsz and tiprz programs from included
   sources.
  
   They compile correctly under 2.0, 2.1 and 3.0 (just checked).
   The only catch with 3.0 is that Makefile in dependencies
   contains references to '/usr/include/...'.  As we all know
   NeXT "improved" a layout of headers in 3.0 and this is causing
   trouble.  Throw away these lines and everything will be OK.
   They do not really serve any useful purpose.
 
B) Everything installed fine but I am getting a floating point
   exception when I try transfers.
 
   As I wrote this stuff is known to work with MY modem.  The trouble
   is that tipx is trying to find out a connection speed (better not
   look how this is done) and is using it to compute expected transfer
   times.  If this speed happens to be zero (or some strange garbage)
   then you will get a floating point exception.
   Cures:
     a) change your modem for something else;
     b) at the top of a function filexfer (file cmds.c) set
        Cbaudrate to some reasonable constant, like 2400 or 9600;
        your expected transfer times will be possibly off by a
        constant factor but no exceptions;  Cbaudrate is not
        used for anything else;
     c) if b) works re-hack hayes.c to set Cbaudrate rigth with
        your modem;
     d) do it properly, i.e. adjust expected transfer times once
        you know how many characters in what time are you really
        sending/receiving (both informations are continously available);
     e) if you are still getting floating point exceptions I have not
        a slightest clue.
 
C) When I start 'rz' I am getting nonsensical error messages.
 
   Send a break (with ~#) befor hitting ~X.  Or better - fix that bug
   but I do not know where it is.
 
An attribute 'cm' from /ect/remote for sending initialization strings
to your modem works correctly with tipx but only for entries which
have 'du' flag - either explicitely or in some continuation stuff.
Do not forget to include all these '\r's in a cm-string so it will be
really accepted.  Something like this ':du:cm=at&k0&n3&m0\r:pn=...'
 
  Michal Jaegermann
  ntomczak@vega.math.ualberta.ca