Falcon DOS Portable Data Terminals, Руководство для продвинутых пользователей

Страница: 81 / 184

Using XFER
Advanced User’s Guide
3-29
sets the overwrite option to
2
(overwrite if CRCs don’t match) but doesn’t
cause XFER to use COM port 2. The following commands could be used to do
this:
In the last example, the first
2
is treated as the setting for the
O
, and the second
2
is parsed as the COM port to use for the transfer.
The Modem-Initialization File
Format
The modem-initialization file (
modem .ini
) contains keyword-and-value
pairs, with each pair on a separate line. Each keyword is separated from its
value by one or more spaces; tabs and other white-space characters are not
valid. Keywords can be in any order within the file.
Lines beginning with a
#
character or with a space character are treated as
comment lines and are ignored. The
#
character can also be used to embed
comments within a line. Any characters after a
#
character in a line are ignored
for that line.
Keywords
ACCESS_DELAY:
This keyword specifies the number of milliseconds for
XFER to wait for a response from the local modem when sending a command
to the local modem. The default is
2000
ms (2 seconds).
CARRIER_TIMEOUT: This keyword specifies the number of seconds for
XFER to wait for a carrier signal from the remote end before timing out. The
default is
60
seconds.
COMPRESSION_STRINGS:
This keyword specifies a list of response strings
(expected responses from the modem) that indicate that a connection was
made using data compression. Because modems often support various types of
data compression, they may have more than one string indicating that
compression is taking place. Use the
COMPRESSION_STRING
keyword as
many times as necessary to create the desired list. However, the combined
C:\> xfer /z2o foo
C:\> xfer /z2o2 foo
C:\> xfer /zo22 foo
Individual lines cannot exceed 128 characters in length, including comments, or errors
in parsing may occur.
advuser.book Page 29 Friday, September 27, 2002 4:22 PM