Hello Ian!

Wednesday March 01 1995, Ian Timms writes to Jerry McBride:

 IT> OS/2 restriction (I think this still holds in 2.x). Also the open
 IT> needs to be of an appropriate type, ie. OPEN_SHARE_DENYNONE so
 IT> that you are permitted to read and write to it. Unfortunately,
 IT> some things (nameley IBM's SLIP) open in OPEN_SHARE_DENYREADWRITE
 IT> which is down right ornery!

IBM's SLIP is a really PITA for co-existing with other programs. I would
love to use RXASYNC as a front-end to a SLIP server, but IBM don't seem to
have grasped the concept of 'hot handles' yet :-(.

 IT> If opened via RxAsyncOpen you'll get
 IT> OPEN_SHARE_DENYNONE, I don't however know what Maximus uses but I
 IT> think it's the same as RxAsync.

 JM>> The reason I wish to pass comhandles is it would simplify the writing of
 JM>> door programs for Maximus/2 2.02 as this bbs only passes
 JM>> handles.

 IT> The BBS I connect to uses Bink and RxAsync in just this way but to
 IT> control BGFAX,

This seems a little pointless since Binkley has its own built-in fax
receive facility which works pretty well...

 IT> if Max gets the handle from Bink then I can't see
 IT> any problem in doing what you want.

I just tried running the little program from the previous msg from Maximus
using the following line in my menus.ctl:-

        Xtern_DOS j:\rxasync3.CMD_-xabc_-p%P_-t%k       Sysop "RXasync"

...and it worked just fine.

I suppose one problem which people may have, if they want to write doors
using RXASYNC, is that output is not echoed to the local screen. This may
not be the case, as I haven't had a proper look through the docs yet, but
if you had to duplicate each line of code for remote and local output, it
could become a little tedious.

RXASYNC does look like a really useful program, I hope I manage to make
some use of it. I suppose, with a few extra Fidonet-type functions, you
build your own Binkley in REXX :-).

John

--- GoldED/2 2.50.Beta4+