>Hi, there:
> I just install successfully term 1.08 on my PC 386DX and on remote
>sun workstation. Everything works very well except for one thing:
> It hangs there forever and I have to stop term locally to get every
>opened window killed. (But the connection with remote is still there; I can
>re-run the term without dialing again)
> Here is my modem: Practical Peripherals 14400. I am using kermit on
>my linux home.
> Here is what I saw:
>modem tries to send signal to remote almost every 1 second, but receives
> nothing from the remote. This is observed at the front panel of modem,
> they are tx and rx lights. For normal operation, if I press a keystroke, the
> tx (send) blinks once, then rx blinks once(I guess that means: sends a
> signal to remtoe (tx) and gets an acknowledgement from the remote)
>Can someone help me out ?
>Thanks
>Mike
Hi, I had this problem solved halfly by myself. The following is the detail
of what I really ran through and my (half)solution. Hope somebody else have
the other half:
Detail:
kermit (login to remote sun workstation)
term -s 38400
^\c (return to local kermit)
^z (stop kermit)
(mark a)term -s 38400 > /dev/cua0 < /dev/cua0 & (you may use /dev/modem, also ok.)
trsh
Now I am on sun
txconn (get screen no, say 9)
setenv DISPLAY autarch.acsu:9
xterm -e rlogin ubvmsd & (open my 1st xterm)
xterm -e rlogin lictor & (" 2nd )
... and so on
Now the devil is:
When you open a xterm by receiving it from remote, you are sending a lot
of data via modem. When you move the xterm to another place on your screen,
you are really re-receiving the data of your xterm again. So you can see
your modem's RX (and maybe also) TX light constantly. This is will hang your
modem just open 2 or 3 xterm's. OF COURSE, logically, if your system and
modem configuration is good enough, they should, I think, handle this
"too busy" traffic well enough so the performance is down but not gets
hanged. (There are some hints in the package term108.tar which I saw some
of them but could not work it out yet)
My solution is:
After (mark a), instead, I did the followings:
(Now I am on the local) xterm -e trsh rlogin ubvmsd &
xterm -e trsh rlogin lictor &
... and so on
I.e., from now on, xterm is using the local resources, so your moving
it around will not need data received form remote. This reduces your
modem traffics to nearly the same as just running a one session kermit.
Now I can open as many as 12+ windows logged on different remotes
without any troubles or noticed slow down.
Note BUT: If you are not just using xterm, say, you are using a drawing
program on your remote and exporting the output to your local, you can
not get around with this method.
Hope it helps a bit.
Mike
by