There is a section on "Changing the Configuration Block" in the
RS232 section of the Device Drivers Manual. I found it a little
confusing. In most cases the communication program you use will
override those settings it cares about so you can ignore this data.
However, I had to play with them once in order to get a Pascal
program to communicate at 9600 baud. The Configuration Block values
are initially set as follows:
0123456789ABCDEF
-- -- -- -- -- -- -- ---- -- -- -- --
-- -- --
06 22 00 00 00 00 13 11DF 84 50 00 |||||||||||+-->
Hdwr handshake =OFF ||||||||||+----->
Data block len =80 char |||||||||+-------->
Min buffer lev = 132 char ||||||||+----------->
Max buffer lev = 223 char |||||||| |||||||+---->
Control character 2 = XON ||||||+------->
Control character 1 = XOF |||||+---------->
Control protocol= None ||||| ||||+-->
Form feed delay = None |||+----->
Line feed delay = None ||+-------->
RETURN delay= None || |+-->
Data format = 7 bits, odd parity +-----> Baud
rate= 300 baud
The "factory" settings are pretty
much useless these days. More common is 2400 baud speed, 8-bit
no-parity data format, XON/XOF control.
Configuration block settings for that setup looks like this:
Remember, with almost all Apple ///
data communications programs, it does not matter what the .RS232
driver's Configuration Block looks like. Your data comm program will
do the settings for you -- the OPENAPPLE-S menus in Access /// and
The Communications Manager and XModem ///, the SETRS232 command in
Kermit ///, etc.
Also, though it may seem obvious,
the .RS232 driver could be on one bootable disk and not on another.
You need it on the disk you boot the system with to use the
communication program. If you are booting with a single "hard disk
program selector" like BOS ///, Catalyst or Selector ///, there is
one exception. Version 2 of Catalyst has a separate SOS.DRIVER in the
hard disk's CATALYST directory that may be added (the EXTRA DRIVERS
part of a Catalyst item's menu entry. If you need .RS232 only for one
program, you can get .RS232 from the "extra" file when that program
is invoked.
1 2
3 4
5 6 7
8 9
10 11
12 13
14 