Warwick, at 15:30 on Apr 26 1996, you wrote to Bill Grimsley...

WE> You recently helped me with my dialling problem, by pointing out
WE> the Result codes. I misinterpreted  your advice on changing from  X4 to X3,
WE> by inputting  ATX=3. However when you corrected my syntax to ATX3, I find
WE> that it will not work. IE, ATX3 has not changed my problem, but ATX=3 
WE> has??? The only difference I note when dialling with ATX=3 in place, is 
WE> that the engaged signal will not cut off and I have to manually hang up.

I have just noted that the incorrect command syntax of ATX=3 will actually
set X=0, which in turn disables ALL service tone detection.  It might
therefore be better if I guide you through the full initialisation sequence
so that you'll have a rough idea of what you're doing in the future.

Start your terminal app, and configure it so that you have CTS/RTS hardware
flow control enabled, XON/XOFF software flow control disabled, lock your
serial port rate to 38400 bps, and enable your 16550 buffered UART if you
have one.  Next, edit your term's init$ to read ATZ^M (where control-M is
the carriage return character), then enter the following string to your
modem (once only, and exactly as written)...

  AT &F &A3 &K3 X3 &W ^M
   ³  ³  ³   ³   ³  ³  À-Carriage return character (press Enter)
   ³  ³  ³   ³   ³  À-Permanently write command to NVRAM
   ³  ³  ³   ³   À-Disable BUSY service tone detect  
   ³  ³  ³   À-Enable V.42bis but disable MNP-5
   ³  ³  À-Enable full connect string results
   ³  À-Reset factory default profile
   À-Attention command

Set the modem's DIP switches so that 3, 5, and 8 are ON, all others OFF.

An ATI4 issued whilst in terminal mode should return a display similar to
the following.  If not, recheck your steps thoroughly...

----------------------------------------------------------------
ati4
USRobotics Austel external Sportster 14400 Fax Settings...

   B0  E1  F1  M1  Q0  V1  X3
   BAUD=38400  PARITY=N  WORDLEN=8
   DIAL=HUNT  ON HOOK

   &A3  &B1  &C1  &D2  &G0  &H1  &I0  &K3
   &M4  &N0  &P0  &R2  &S0  &T5  &Y1

   S00=000  S01=000  S02=043  S03=013  S04=010  S05=008  S06=002
   S07=060  S08=002  S09=006  S10=007  S11=070  S12=050  S13=000
   S14=000  S15=000  S16=000  S17=000  S18=000  S19=000  S20=000
   S21=010  S22=017  S23=019  S24=000  S25=005  S26=000  S27=000
   S28=008  S29=020  S30=000  S31=000  S32=000  S33=000  S34=006
   S35=000  S36=000  S37=000  S38=000  S39=000  S40=000  S41=000
   S42=000  S43=000  S44=015  S45=000  S46=000  S47=000  S48=000
   S49=000  S50=000  S51=000
----------------------------------------------------------------

WE> When the line is free, the modem works flawlessly. However, I now seem to 
WE> have a problem with Telix interpreting the time for download, whereby the 
WE> original estimated time will be a ridiculuosly low 0.5 minutes (or so), but 
WE> the actual time might be 5 or 8 minutes. Any bright ideas?

Not exactly sure what you mean here, but it could simply be that the
estimated file transfer times will be wildly inaccurate while the modem's
buffers are being filled with data.

Regards, Bill

--- Msgedsq/2 3.20