home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Simtel MSDOS - Coast to Coast
/
simteldosarchivecoasttocoast2.iso
/
windows3
/
pcucp15.zip
/
config.doc
next >
Wrap
Text File
|
1993-11-10
|
9KB
|
271 lines
Configuration files
---------------------------------------------------------------------
The configuration files are located in the Pcucp directory
specified by the environment variable PCUCPDIR. The filename
suffix for the configuration files is ".cfg".
Pcucp always attempts to read the default configuration file
"pcucp.cfg". In addition to this, a configuration file can
be specified in the command line, in which case the settings
in the default configuration file are overridden by the
settings in the explicitly specified configuration file.
If the default configuration file does not exist, a
configuration file must be explicitly defined on the command
line.
If there is no need for multiple setups, the default
configuration file may be the only configuration file. With
multiple setups, the default settings can be placed in the
default configuration file.
The configuration files are plain ascii-text files, which
can be created and modified with any text editor such as
the MS-DOS editor (edit) or Windows Notepad.
The settings in a configuration file consist of lines
containing a keyword and arguments. The following sections
"Settings common to unix and dos" and "Settings unique to dos"
list the keywords and the related arguments.
Comments are prefixed by the character '#'. This character
and any remaining characters on the same line are ignored.
The keywords are not case sensitive.
The following escape sequences can be used in string arguments
of the keywords PADSTR, SALVSTR, XLAT and KEY :
\r : cr
\n : nl
\t : tab
\\ : \
\^ : ^
\xNN : hexadecimal escape for the number NN
^X : control code corresponding to character X
Settings common to unix and dos
---------------------------------------------------------------------
PACKETSIZE <n>
Sets the packet size to n bytes. There is no default for
this setting. Packet size must be equal in the remote
and the local end for Pcucp to function at all.
The 'optimum' value for this setting is about 20 - 25 % of
the line transmit capacity in bytes/s. In general, a bigger
value increases transmit efficiency, but decreases interactivity.
If bitcoding is used, the program adjusts the actual packet
size to be evenly divisible by 8 (if either of BIT5 or BIT7
is used) or 4 (if both BIT5 and BIT7 are used).
As an example, lets assume that the line parameters are
2400,N,8,1. Now one byte takes 1 start bit, no parity bit,
8 data bits and 1 stop bit, a total of 10 bits. Hence, the
line can transmit 2400 / 10 = 240 bytes / s. This suggests
a packet size of 48 - 60 bytes. In the typical case, in which
bitcoding for bit 5 is used a packet size of 56, being evenly
divisible by 8 would seem appropriate.
BITCODE <NONE> | <BIT5> | <BIT7> | <BIT5 BIT7>
Sets the bit coding scheme used. This setting must equal in
the remote and the local end for Pcucp to function at all.
NONE : no coding (default)
BIT5 : bit #5 not used, always 1 (no ctrl-codes)
BIT7 : bit #7 not used, always 0
BIT5 BIT7 : only printable characters used (0x20 - 0x5f)
Since all bits in a byte cannot be used, the effective line
speed is decremented by 12.5 % if one of BIT5 or BIT7 is used
and by 25 % if both BIT5 and BIT7 are used, assuming that
8 data bits are available. With 7 data bits, the loss is
14.2 % or 28.6 % respectively.
If Pcucp does not work, try setting both BIT5 and BIT7. This
makes Pcucp use only printable characters and should work
where kermit does. In most cases only BIT5 is sufficient
though, since the problem (if any) usually lies in
'disappearing' control codes (ascii 0 - 31).
PADSTR <string>
Sets the pad string sent after each packet to <string>
(max. 8 bytes).
A pad string is not usually required.
SALVSTR <string>
Sets the 'salvage string' to <string> (max. 64 bytes).
This string is sent over the communication line when no
incoming packets have been received in five seconds. It can
be useful when e.g. a ^S generated by line noise has stopped
input from the line. In this specific case a ^Q as SALVSTR
would salvage the connection.
INDIR <path>
Sets the incoming files directory to <path>. The default is
directory "in" in the directory specified by the environment
variable PCUCPDIR. Do not set INDIR equal to OUTDIR (!).
OUTDIR <path>
Sets the outgoing files directory to <path> The default is
directory "out" in the directory specified by the
environment variable PCUCPDIR. Do not set OUTDIR equal to
INDIR (!).
Settings unique to DOS
---------------------------------------------------------------------
LINEPARAMS COM<n>:<bps>,<parity>,<databits>,<stopbits>
Sets the com-port and line parameters used. There is no
default for this setting.
<n> : com-port number (1 - 4)
<bps> : communication speed (e.g. 1200,2400,9600,19200,38400,57600)
<parity> : parity (N/E/O)
<databits> : databits (7/8)
<stopbits> : stopbits (1/2)
The argument has the same format as the DOS's mode command
argument for com-ports.
If you have a data compressing modem it is usually a good
idea to set the line speed higher than the nominal line
(modem) speed. Note, however, that the higher speeds (>9600)
may not be useful without an UART like the 16550 with
extented line buffers.
XLAT <in> <out>
Sets a translate table entry for the emulated terminal.
If the a character to be displayed on the terminal is
<in> it is displayed as <out>. If a character typed is
<out> it is sent as <in>.
Note : the special international character codes in a Windows
font probably differ from IBM native ones. Using Windows
Notepad to edit the configuration file might help, since it
uses the Windows codes.
KEY <string> <key> [SHIFT] [CTRL]
Sets a special key mapping, that is, sets the key specified
by <key> to emit <string>. The strings set here bypass the
translations specified with XLAT-keywords.
<key> can be any of the following :
BS : backspace
HOME : Home
UP : up arrow
PGUP : PgUp
LEFT : left arrow
MID : middle (5)
RIGHT : right arrow
END : End
DOWN : down arrow
PGDN : PgDn
F1 - F12 : function keys
SHIFT and CTRL can be used to specify a key combination
involving these keys.
FONT <name> [y] [x] [BOLD] [ITALIC]
Sets the font used in Pcucp windows (Windows version only).
<name> : font name
[y] : y-size (pixels)
[x] : x-size (pixels)
[BOLD] : use bold-attribute
[ITALIC] : use italic-attribute
Use this setting if you are not satisfied with the default
font used.
The font must be of a fixed type to work correctly with Pcucp.
Most of Windows fonts are not fixed, and hence the set of
fonts that can be used with this setting is usually very
limited. Also note that the parameters of this keyword are
fed 'as is' to the Windows font selection function which
ultimately selects the font used, hence the actual font can
differ from the one requested.
'Fixedsys' and 'Terminal' are generally available fixed fonts
under Windows 3.1.
AUTOWRAP <ON | OFF>
Controls whether lines longer than the current terminal width
are continued on the next line (ON) or truncated (OFF). The
default value for this setting is ON.
SCRBUFSIZE <kbytes>
Sets the display buffer size in kbytes (characters).
<kbytes> : size in kbytes (1 - 32, default 8)
Space not needed to store actual screen contents is used for
the scrollback buffer. Note that the amount of memory
actually allocated is twice as much as set with SCRBUFSIZE,
since every character takes two bytes to store, one for the
character itself and one for the related attribute (such as
standout, underline..). Also note that a larger buffer also
means greater cpu overhead when scrolling the buffer contents.
BGCOLOR <r> <g> <b>
FGCOLOR <r> <g> <b>
STCOLOR <r> <g> <b>
BGCOLOR sets the background color used in Pcucp windows.
FGCOLOR sets the foregroung (text) color used in Pcucp windows.
STCOLOR sets the standout (highlight) color used in Pcucp windows.
The colors are specified using the RGB-color scheme, where :
<r> : red component (0-255)
<g> : green component (0-255)
<b> : blue component (0-255)
The default colors are :
BGCOLOR : 255 255 255 : white
FGCOLOR : 0 0 0 : black
STCOLOR : 128 128 128 : gray
Note that your display adapter might not be capable of displaying
all possible RGB-combinations and so Windows might try to mimic a
color by dithering (creating a bit pattern instead of a solid
color). While this may be useful in other contexts it tends to
make text on Pcucp windows unreadable.
---------------------------------------------------------------------
This file is part of Pcucp, Copyright (C) 1992, 1993 Jouni Leppäjärvi
---------------------------------------------------------------------