thanks for your input.
>
>We are using a shareware product called "ComT" for this application.
>
>Works great for WinCIM, works terrible for Navigator (but after much
>testing, we believe it's Navigator's fault).
>
>Email me if you want more info on it (I don't have it handy at the moment).
>
I have heard of it, know where to get it, but hadn't understood how it could
help me. Telnet for me was always a login to a remote host. Until yesterday
when the solution to modem configuration was presented as telnetting to a
serial interface. Suddenly my horizons widened! Thanks for your experiences
with the CS access products.
>
>We have Century TERM on our SCO UNIX boxes which allows you to specify a
>telnet port as a device (as opposed to a dial script).
>
>Unfortunately, that means when you telnet to the portmaster, TERM assumes
>you're connected to the final destination (which would be the case if you
>were TERM'g to a local host). Therefore, you need to manually type the
>modem dial command (I can live with this). Some sharp TERM scripting
>people could probably find a way around this, though.
>
>The command line option would be:
>
>term -ltelnet:portsvr
>
>Or if you have the dialout (or twoway) modems configured on a different
>telnet port than the default (23):
>
>term -ltelnet:portsvr#6000
>
>(Usually, term takes an argument of the form -l/dev/tty2a)
>
My SCO UNIX requirement is for an application to talk to a /dev/somedevice
as if this device were a (fast) serial port. I define the type of communication
to be async serial and I must give the device name in the configuration.
I guess Digiboard or similar is the solution, but the revelation of entering
AT&F in a telnet session and getting a reply of OK really got me wondering.
>
>Hope this helps...
>
Everything is a tremendous help to a Newbie. Thanks a lot.
Phil
PLUS COMMUNICATIONS, Vienna, Austria
http://www.plus.at