home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR10
/
1_COMM.ZIP
/
JOEMODEM.TXT
< prev
next >
Wrap
Text File
|
1993-11-12
|
13KB
|
255 lines
OK, This file is for the "Advanced Communications Dude!"
Please Note: Should you continue to read on and then
attempt to create the "ADVPARAM.DAT" file,
and "stuff messes up," or it just doesn't
work right..... Then just delete the file
and all will return to normal. If the file
doesn't exist the program defaults are
used.
The following mess was added to 1$COMM in order to give the end user more
control over the program, and to adapt to modems that do not re-
spond to the default AT Modem Codes. Although every effort was
made to insure these functions work properly, you should still
be aware that it was impossible for us to test them on every type
of system. Therefore, all we can be certain of is that it works
on our equipment. We use all US Robotics. So, in summary... USE
AT YOUR OWN RISK!
1. Create a text file called: "ADVPARAM.DAT" , and copy it to the
\FMN directory.
2. Note that it is not necessary to fill in every parameter as below
stated. 1$COMM reads this file into an array, checks for the
upper bound, then checks to see if the line contains something,
and if it does, it checks to see if it falls into the correct
parameters, and if it does, then it uses the variable.
3. Again, if the file exists, 1$COMM attempts to use the data, if
the file does not exist 1$COMM uses its default parameters.
4. In the examples... example: "something"; the quotation marks are
not part of the example. Do not include quotation marks.
"ADVPARAM.DAT"
PARAMETER WHERE IT GOES POSSIBLE CHOICES
============================================================================
Override Baud Rate Line 1, Column 1 50, 75, 110, 134,
150, 300, 600, 1200,
1800, 2000, 2400,
4800, 9600, 19200
-384 for 38400
-576 for 57600
-1152 for 115200
Receive Buffer Line 2, Column 1 4 to 24 inclusive
Total Buffer is 32K
what doesn't go in
receive, goes in the
transmit buffer.
AT Reset String Line 3, Column 1 Default = "ATZ"
AT Initialization Line 4, Column 1 Default = "ATE1Q0V1X4S0=0"
For Host Mode, We suggest: "ATE1Q0V1X4F0S0=1"
Optional additional
AT string for use in
Host Mode Line 5, Column 1 Default is nothing.
Note: Do not modify Line 5 unless you plan to use Host Mode,
otherwise 1$COMM will never dial. In Host Mode, since
you don't need to dial, line 5 becomes an extra place
to add additional AT Codes. In Terminal Mode, this is
the AT string that dials the phone.
Modify Port Info
Port Line 6, Column 1 1 to 8 inclusive
Address Line 6, Column 2 Hex, example: "&H3F8"
IRQ Line 6, Column 7 #
Host Mode Line 7, Column 1 ON
must also modify line(s)
4, 5.
RTS ON Line 8, Column 1 ON
Xon Line 9, Column 1 ON
Xon wait ticks Line 9, Column 3 Default = 182
You must use some value
even if you want the
default. Unless the length
of this line > 2, the
entire parameter is dis-
regarded.
# of video lines Line 10 Choose: 25, 43, or 50
Default is 25 or blank
line.
ZMODEM SEND/RECEIVE OPTIONS:
Receive options Line 11, Column 1 0 or 3 Default = 3
0 = no option
3 = crash recovery
Send options
Conversion Line 12, Column 1 0 to 3 inclusive
Default = 3
0 = no option
1 = Binary file
2 = ASCII file
3 = crash recovery
Management Line 13, Column 1 0 to 7 inclusive
Default = 0 unless a #
is found on this line
that is out of the range
specified, then the
default = 4.
0 = crash recovery
1 = send if sender's file is newer or longer than receiver's file
2 = send if sender's file has a different CRC than receiver's file
3 = append file to receiver's existing file, if existing
4 = replace receiver's existing file, if exists
5 = send if sender's file is newer than receiver's file
6 = send if sender's file date or size <> receiver's file date or size
7 = protect destination file, if exists
Skip If Missing Line 14, Column 1 0 or 1 Default = 0
0 = no option
1 = Receiver should not
accept file unless it
already has a file with
the same name. This option
overrides all other
Management options.
ZMODEM BATCH SEND
If you want to send more than 1 file during a ZMODEM transfer, then:
Create a file anywhere, but name it with a "LST" extension,
for example: c:\mydir\files2go.lst
Then simply copy all the file names you want to upload in a single
ZMODEM session, into this file, use full path names, if they don't
reside in the \FMN directory.
At the Upload file name prompt, within 1$COMM, use your list file
full path and name, again if not in the current directory, and
press Enter.
1$COMM will read the file names from your list file into ZMODEM's
file array, and start the upload.
You may also specify filenames using wildcard characters.
Example: "Myfile??.*"
Your list file may contain up to 150 entries, but with the power
of using wildcard characters, you'll have limitless capabilities!
Accepted Bit stings, Line 15, Column 1 Default = [700,701,702,
703,704,710,711,712,713,
714,810]
Again for compatability purposes, we include this line. If it exists will
override our internal tests for a valid [Databit,Stopbit,Parity] String.
Please keep in mind that if an invalid set of these parameters are passed
through intialization, your machine will lock and sometimes require you to
power down ALL your equipment for several minutes, before re-trying. Thus
we created a default test, based on our equipment. Should you find that you
can use settings beyond ours, then create your own override string. You may
use any form of spacing or tokenization between the sets, however the sets
themselves must remain in the: DatabitStopbitParity order, with no commas or
spaces between them. You must also use the integer equivalent. See the Default
above as an example.
On Prompt Do: Auto-Detect Option
If this is received: Line 16, Column 1-39
Then send this: Line 16, Column 40+
This feature can be used to tell the Host Computer that you have a
particular option, or to confirm a security pass, ect. This feature
does not replace the existing Ansi auto-detect send utility, it merely
adds an additional option. For example, suppose you wanted to call
a BBS, and copy all their RIP screens, then on Line 15, starting at
Column 1, you would put "!". On Line 15, Column 40, you would put,
"RIP". When the Host Computer sent you the RIP verification, 1$COMM
would answer it correctly. Although you'll see, "pretty much garbage,"
the internal capture utility will be gathering all the RIP codes, sent.
Take the capture file, cut it up into screen files, load the screens
into your favorite RIP editor, and modify! Be sure to call in ANSI
Mode, since in text mode the escape character is filtered out.
Note: if you do plan to capture RIP screens, you may have to add an
additional receive filter of: "!" changed to "CHR$(13) + !" The in-
ternal capture routine, appends a line to the capture file every time
it encounters a carriage return. Should the line grow to beyond 1024
bytes, before receiving a carriage return, the line is dumped!
Also if the BBS that you call, uses some other way of verifying RIP
presence, you'll have to make that adjustment accordingly. Some BBS's
ask for the RIP version ##|##|## instead of just plain RIP.
Additional Receive Filter
If this is received: Line 17, Column 1-39 Literal 1 character
Then interpret as: Line 17, Column 40+ Literal 1 or 2 characters
Additional Send Filter
If this is to be sent: Line 18, Column 1-39 Literal 1 character
Then send this instead: Line 18, Column 40+ Literal 1 or 2 characters
The optional additional filters can be used to stop or screen
out certain characters from being viewed or captured. For instance
with regards to the Receive Filter, if you "hated" the character
"W" for some wierd reason, you could set Column 1-39 to be
"CHR$(87)" and Column 40+ to be "CHR$(119)". Then every time a
"W" was sent, you would receive a "w" instead.
Suppose in the Send Filter, you decided that every time you pressed
the key "*" the modem should send out "Hi", then you would
set Column 1-39 to "*", and Column 40+ to "Hi".
Please note as in the above examples, do not include the quotation
marks as part of your entry, "", they are only here to identify
the example items. You may use the syntax: CHR$(77) + CHR$(69) or
"M" + "E" or "ME" and so on, as long as the result remains a
string. Also Ansi auto-detect is already built in to 1$COMM, see
the file "1.HLP" for further explanations on how to override the
auto ANSI.
........and that's it!
Should you encounter any problems, please let us know, so that we may
correct any possible errors in this program, for future version releases.
Thank you for using 1$COMM
and remember your registration makes it possible
for us to write and release better versions of our software.
11.05.93 ¥ Wizard.....