q_and_a

通讯程序源码

			Questions and Answers
		for the most common Pcomm problems.

1) The "elpase time" doesn't increment during a dialing attempt.

	This is a symptom of a bug in the wgetch() routine in the curses
	library.  The work-around is to set WGETCH_BROKE in the config.h
	file and recompile.

2) I can't get Pcomm to dial, it just sits there.

	This typically is due to the wrong device name for the tty port.
	Some systems have more than one name (different minor device
	numbers) for the same tty port.  UUCP may use the device name
	that has "modem control" enabled; if so, that is the one Pcomm
	needs to use.

3) How do you make Sun's dial in and out on the same port?

	Sun Sparc boxes don't come configured for doing dialin and dialout
	on the same serial port.  However, there is a blurb in the printed
	manual that tells you what to do...

	Make a new device (cua0 for ttya, and/or cua1 for ttyb)
		mknod /dev/cua0 c 12 128
		mknod /dev/cua1 c 12 129

	Edit /etc/ttytab.  Change the ttya (or ttyb) line to look like
	the following.  Look in the /etc/gettytab file for the choices
	for the second field (std.38400, in this example).
		ttya   "/usr/etc/getty std.38400"  dialup    on remote secure
		ttyb   "/usr/etc/getty std.38400"  dialup    on remote secure

	Edit /etc/uucp/Devices.  Add a line for each speed your modem
	supports.  The dialer field (hayes, in this example) must match
	whatever you've got in /etc/uucp/Dialers.
		ACU cua0 cua0 1200 hayes
		ACU cua0 cua0 2400 hayes
		ACU cua0 cua0 9600 hayes
		ACU cua0 cua0 19200 hayes
		ACU cua0 cua0 38400 hayes

4) I get a measage that tells me I can't create the lockfile (or can't
open the tty port).

	Pcomm is typically configured to be set-user-id to uucp.  To do
	this, you type (as root):
		chown uucp pcomm
		chmod 4755 pcomm
		
5) As soon as I am connected, the modem lights go crazy.

	This is probably caused by an improper UUCP lock file.  Pcomm
	understands several variations of UUCP lock files, but must
	match the one used by your UUCP.  Read the Readme file and check
	the LOCK_DIR, ASCII_PID, SVR4_LOCKS, and XENIX_LOCKS in the
	config.h file.

6) I've got a V.32bis modem but without locked DTE speeds, how do I
setup Pcomm for this?

	Change the tty database so that the "locked speed" entry is set
	to zero.  Then change the "auto-baud detect" flag in the modem
	database to 'N'.

	In this configuration, the modem will always use the DTE speed
	as specified in the dialing directory.  The status line will
	show this speed, regardless of the actual connected baud rate.

7) Some of the Pcomm screens appear messed up.

	Yes, that's unfortunately quite common...  It's a bug in either
	the curses library or the termcap/terminfo database.  I've
	included a terminfo entry for AT386 in the Readme file, that
	seemed to fix the problem for my 386 box.

8) Where do I get xmodem/ymodem/zmodem stand-alone programs for Unix?

	I use Xmodem v3.8 by Steve Grandi, and an older version of rzsz
	by Omen Technologies.  Both of these should be available at a
	neighboring archive site.

9) I can't get the external zmodem programs "rz" and "sz" to work from
inside Pcomm.

	The authors of rz and sz have deliberately broken the program so
	that it will not work from inside another program.  See if you
	can find an older version.