JC> the system that I initate the shell type exit and press return to exit
JC> and on the other screen it says c:\telix>echo off.
ya... hmmm. ah... let me see
onthe host system you will get that "echo off" but you should get
a shell on the client (call-ing) system. I have 2 machines here...
just let me shell out of my OLR and try it.
2 hours later: Well I couldn't get it to work. (It was working just
the other week... I'm confused)
I got Telix talking to Telix OK,
trying to shell to dos from hostplus just hung the system.
but I couldn't a BASIC comms prog to talk to a basic comms prog...
It just wouldn't run on one of the computers (device timeout)
From this I'm guessing that Telix is less critical about comm ports
(flow control line levels etc.) than DOS (BIOS) is. you may have to play with
your modem init strings... or you could try running a FOSSIL on the
host system.
1 hour later.
By making repairs to my "null modem" cable I got shell-to-dos
working. :-)
JC> or would that rec. a second modem and some special software??
No, as you've got the computers "talking" via
telix/hostplus the battle is almost won...
Actually you don't need any modems, all you need is a "null modem"
cable (a cable with rs232 plugs on each end wired to connect two
computers together) (this is what i used when testing)
Maybe the problem you have is that your modem isn't telling BIOS th
at it's ready to send/recieve data, what you need to do in this
case is to configure your "host" modem to assert "DCD" "DSR" and
"CTS".
Another possible problem is that Bios may see your modem on a
different port to Telix... (this is more probable than the above
problem) Bios numbers comm ports 1,2,3,4 in the order it detects
them, for example: if your modem is an internal on the COM4 address
bios will call it COM3 if you have COM1 and COM2 but don't have a
COM3 device installed.
  The work-around is to re-define the comm-port in telix so that
COM3 (or whatever) points to the address/irq of your modem
(ALT-O,C) and then get telix to use the port that corresponds to
what BIOS thinks the port is... (don't forget to change your
default port settings (alt-O,T,A) to point to this new port too,
and "Write setup to disk")
I hope you find the solution here somewhere. (I hope this message
gets through, my Sysop tells me that Echomail accross USA is down
due to electrical storms.)
Long live Fidonet.
--- EzyQwk V1.20
---------------