[trim]

MS>> ...no ~IRQ~... `RLFossil' talks to the Packet-Driver and the later
MS>> has EXCLUSIVE use of your real MoDem.  The packet-Driver itself is
MS>> no piece of HardWare...  ...an image is worth a thousand words...

ML>> But what COM port would one tell {COMMO} or telix or procomm to use
ML>> to talk to RLFOSSIL?

 MS>      `Procomm v2.4.3' doesn't have such a capability, `{Commo}
 MS> v7.7' and `Telix v3.51' do support ~INT-14~/~FOSSIL~ Serial-Ports.

interesting... very interesting... i wasn't aware that {COMMO} or Telix has
INT14 capabilities... especially Telix and i've been using it since it
first appears in the wild...

 MS> Since an image is worth a thousand words, euh...  i'll simply use
 MS> command-line samples:

 MS>           RLFossil.EXE 2 1 "Commo.EXE /:INT-14 /{*1,,3,V,}"
 MS>           C:\PPP\RLFossil.EXE 2 1 "Telix.EXE INT14"

thanks!! what versions of {COMMO}, Telix and RLFossil are those, please?

[trim]

 MS>      Take note that no genuine `{Commo}' release used the
 MS> `INT-14' macro but both packages allow the selection of a
 MS> ~FOSSIL~ Serial-Port from the Command-Line:  in `{Commo}'s
 MS> case, "*1" in "{*1,,3,V,}" means ~BIOS INT-14~/~FOSSIL~
 MS> Serial-Port at 38K4 bps.  I must confess that the matter
 MS> of local connection speed (~DTE~, isn't it?)

hardware to hardware (IE: modem to computer or printer to computer) are DTE
as in Data Terminal Equipment... DCE is modem to modem as in Data
Communication Equipment...

 MS> sure sounds somewhat "elusive" since i get rate peaks around
 MS> 4K cps (both on `{Commo}' and `Telix') but there's no
 MS> significant drop when i set `Telix' for a 9K6 bps connection;

there shouldn't be, either, since the equipment is not hampered by hardware
(aka uart) speed limitations/settings...

 MS> if i use `MS-kermit' with `RLFossil' instead then my connect
 MS> speed shows as "unknown"...

that would seem to indicate that ms-kermit either doesn't have a matching
connect speed or doesn't recognise what it may be being told is the
connection speed...

 MS> In any case, the Serial-Port `{Commo}' or `Telix' would use
 MS> is defined right on `RLFossil's Command-Line!...

ok... my bbs does that with telix all the time anyway... when a user logs
off, my system fires up telix (only one copy installed on the machine) one
which ever com port belongs to that node and runs a script to fetch the
session's stats from the modem (ie: fallbacks, retrains, up/downlink
speeds, db's at specific frequencies) for later analysis (aka beating the
telco with) if needed...

 MS> It's just a matter of making both pieces of SoftWare agree
 MS> (and to pick a Serial-Port which is free, preferably)!  ;-)
 MS> Now, might a HardWare and a ~Fossil~ Serial-Port coexist by
 MS> using the same COM number and yet work correctly?

yes... FOSSIL ports start at 0 (zero) and the physical address of port0 can
be defined differently then the "standard" port addresses... for
that matter, if one is handy with debug or other capable software, one can
redefine the BIOS table of serial and parallel port addresses that reside
at 0040:0000  ;)

ie:
c:\>debug
-d 0040:0000
0040:0000  F8 03 00 00 00 00 00 00-78 03 00 00 02 00 80 9F
0040:0010  27 C2 00 7C 02 28 00 20-00 00 22 00 22 00 30 0B
0040:0020  0D 1C 62 30 75 16 67 22-0D 1C 64 20 20 39 30 0B
0040:0030  30 0B 34 05 30 0B 3A 27-30 0B 30 0B 30 0B 00 80
0040:0040  00 00 FF 01 F7 01 00 E0-C8 03 50 00 40 20 00 00
0040:0050  00 11 00 00 00 00 00 00-00 00 00 00 00 00 00 00
0040:0060  07 06 00 D4 03 29 30 7F-03 00 C0 FF CD 1C 0D 00
0040:0070  00 00 00 00 00 01 00 00-14 14 14 28 01 01 01 01
-

you'll note the first line shows F8 03 (small endian format) which is the
(general) address of COM1... if i alter that to something else, then
programs that look to the BIOS table will go for the new address... each
port address is a 'word' (two bytes) in size... there is only space
allocated in the BIOS table for four words which matches to the four com
ports... in the above, the 5th word, 78 03, is the address of the first
parallel port ;)

 MS> There is such a possibility in a `W32' DOS box when `COM/IP'
 MS> happens to be the Virtual ~TelNet~ MoDem "Shim", i believe,
 MS> but my setup is OK as it is...

;)

 MS> N.B.:  Please, drop me a note when you're ready to try
 MS> `MS-Kermit' as an `OS/2' external file-transfer protocol-driver
 MS> on a `Maximus' BBS!

i'll do that 'cept it'll be on a RemoteAccess BBS since i don't run Maximus
"out front" ;)

)\/(ark