🚀 go-pugleaf

I am unable to solve a problem with three systems with Telebit
modems and SCO Xenix systems.

My system is a 486/33 with a Telebit TB+ on a specialIX port running
SCO Xenix 386. Its a dog with an average of 32 Users, the response
time is bad. I am not sure how this would affect the modem, the SI
board is an intelligent board with RTS/CTS flow control.

System A is a 386 with a T1000 on COM1: with the interface locked
at xxxx baud

System B is a 286/12 with a T1000 on COM1:, the interface is locked
at xxxx baud

When system A tries to send a 20K file to system B using UUCP, the
line is lost.

When system A tries to get the file from system B using UUCP, the
line is lost.

All systems are set with m2s61=255, micro-packets disabled and tone
before packets, the modems are not retraining at the point where
the error occurs. On my system I have s58=2s68=2, on system B,
s58=3s68=255, on system A, s58=3s68=3.

When I send a 1.2MB file to system A, the file transfers fine, when
uucp changes to to slave mode and tries to retrieve a 170K file,
the line is lost. When System A calls me and attempts to send the
file, the line is lost. When I try to download using Zmodem from
A to me with Xmodem spoofing on (because I was going to try Xmodem
if Zmodem failed), there were errors but the file made it. When I
uploaded the same file to system B using Xmodem with Xmodem spoofing,
the transfer took a long time, had a large number of errors  but
it finally made it. With Xmodem, there were a lot of pauses when
nothing was being sent. With UUCP, the transfer procedes for a
while and all of a sudden I start receiving alarms, eventually it
will abort with line lost.

I had thought that 'spoofing' meant that the modems would take care
of error correction between themselves and return the user an error
free data transmission. Why am I seeing errors with Xmodem? What
is going on here? Can you help me?

Does anyone have list of the undocumented features in the Telebit
modems? I know of some of the information for disabling micro-packets
and adding tone before packets, and I remember some S registers
have undocumented 254 and 255 values.

This is the register setting for my Tbit+

E1 F1 M2 Q4 T V1 X1     Version BA4.00
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006
S10=007 S11=070 S12=050 
S45=255 S47=004 S48=000 S49=000
S50=255 S51=005 S52=001 S53=001 S54=002 S55=000 S56=017 S57=019 S58=002 S59=000
S60=000 S61=100 S62=003 S63=001 S64=000 S65=000 S66=001 S67=000 S68=002 
S90=000 S91=000 S92=001 S95=002 
S100=000 S101=000 S102=000 S104=000 
S110=001 S111=020 S112=001 
S120=012 S121=000 

This is the register setting for system A's T1000

%E0 F1 M0 Q0 P V1 W0 X1 Y0 &P0 &T4     Version FA2.10
%S00=001 S01:001 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
%S10=007 S11=070 S12=050 S18=000 S25=005 S38=000 
%S41=000 S45:255 S47=004 S48=000 S49=000
%S50=000 S51:005 S52:002         S54:003 S55:003 S56=017 S57=019 S58=003 S59=000
%S60=000 S61=150 S62=003 S63=001 S64=000 S65=000 S66:001 S67=000 S68=255 S69=000
%S90=000 S91=000 S92=000 S94=001 S95=000 S96=001 
%S100=000 S101=000 S104=000 
%S111:030 S112=001 
%S121=000 S130=002 S131:001 S255=001 

This is the register setting for system B's T1000

%E0 F1 M0 Q0 P V1 W0 X1 Y0 &P0 &T4     Version FA2.10
%S00=001 S01:001 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
%S10=007 S11=070 S12=050 S18=000 S25=005 S38=000 
%S41=000 S45:255 S47=004 S48=000 S49=000
%S50=000 S51:005 S52:002         S54:003 S55:003 S56=017 S57=019 S58=003 S59=000
%S60=000 S61=150 S62=003 S63=001 S64=000 S65=000 S66:001 S67=000 S68=255 S69=000
%S90=000 S91=000 S92=000 S94=001 S95=000 S96=001 
%S100=000 S101=000 S104=000 
%S111:030 S112=001 
%S121=000 S130=002 S131:001 S255=001 

---
-----------------------------------------------------------------------------
Mark Seiffert                    UUNet: mark@delta1.UUCP
Delta Systems                 InterNet: mark%delta1@rex.cs.tulane.edu
New Orleans, LA 70002            Voice: +1 504 837 9835  Fax: +1 504 837 9838