Script problems with Pcomm

Script problems with Pcomm

Post by D Parso » Fri, 25 Nov 1994 01:23:36



I am using Pcomm v.2.0.1 with Slackware 1.2. It works well when dialing
from the dialing directory. The only problem I had with installation
relates to getting a reversed contrast status bar on one machine and
normal status bar on the other (both have setenv term vt100).
   The shell scripts are a problem for me since they easily lock up
the screen and I have to go to another console, ps, and kill the
pcomm jobs. This happens most often when run the script from the
command files window instead of from the command line (pcomm -a
script_file). It would be a help if I could see other shell scripts
(for login to a main frame and also to a BBS). Can someone send
me examples? Many thanks, Don

--
Donald F. Parsons MD, Wadsworth Ctr. Rm C273, NY State Dept of Health, ESP,
PO Box 509, Albany, NY 12201-0509. (518)474-7047 Fax: (518)474-7992


 
 
 

1. IPC error with Pcomm shell scripts

On running shell (csh) scripts for Pcomm after dialing and connecting
I get the message "cant read from IPC" followed by syntax errors. What is
wrong? Don

--
Donald F. Parsons MD, Wadsworth Ctr. Rm C273, NY State Dept of Health, ESP,
PO Box 509, Albany, NY 12201-0509. (518)474-7047 Fax: (518)474-7992


2. Netatalk printing problems on Red Hat 7.1

3. PCOMM Downloading in a script file.

4. Boot problems (2.5 OpenBSD i386)

5. Pcomm installation problems.

6. Geforce3 Ti 200 & RH 7.2

7. PCOMM Make problem

8. Connection LAN users via a Red Had 7.1 Linux Server to the Internet

9. Pcomm problems (Can't find /lib/libc_v2_11c)

10. header <linux/types.h> problem in compiling pcomm

11. Pcomm problems - "Windows not supported (terminal too dumb)"

12. Problem using tn3270 from pcomm

13. script alias problem - Re: apache alias and script alias problem