The Serial Driver, "ibmser.device"
This driver is compatible with both the 1.3 and 2.0 operating system
versions, and is entitled "ibmser.device".
No "mountlist" entry is required to use the driver with a terminal
program. Simply put the driver into your "devs: directory", and change
the serial device in your terminal program to "ibmser.device". You do
not need to use "binddrivers", or any other mounting program. The
AmigaDOS operating system will automatically mount the driver when it
is first used.
The driver supports up to four units, numbered 0 through 3. These
corresspond to the IBM serial devices COM1 through COM4. You must set
up the DIP switches/jumpers on your modem or multi I/O card to make the
serial port COM number you want to use match the unit you specify with
"ibmser.device". The driver will automatically select first-in, first
out (FIFO) buffering if it senses a newer series 16550-compatible UART
chip in the IBM card. Otherwise, it will stay with normal 16450/8250
compatibility.
In addition, the driver will automatically turn on the master interrupt
enable when it is initialized. If you wish to access the new serial
ports from the CLI, use the IOwedge program to redirect SER: data to
this driver (see the description of IOWedge elsewhere in this
documentation).
This driver has been tested with a v.32bis IBM-type internal modem in
an Amiga 3000 at 57600 bps DTE baud rate without any problems. However,
multitasking with certain programs at this speed can cause your terminal
program to lose characters. Any program which turns off interrupts for
an extended period of time will affect your serial port throughput. If
your hard drive interface is on a DMA Zorro II card, you may also
experience character loss at high speeds. This occurs when the DMA
interface occupies the bus an overly long time, and refuses to allow
the serial driver access. If you have such a problem, contact your
hard drive manufacturer to obtain an updated hard disk driver.
HTML Conversion by AG2HTML.pl V2.950424, perl 5.000 & witbrock@cs.cmu.edu