home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.ib.com
/
2003-04-09_ftp.ibm.com-os2.zip
/
os2ddpak_cur
/
pccardbr.exe
/
AUTODRV.DOC
< prev
next >
Wrap
Text File
|
1996-12-09
|
32KB
|
871 lines
DOS Auto Configurator V2.0 (AUTODRV.SYS)/
OS/2 Auto Configurator V2.0 (AUTODRV2.SYS)
The Auto Configurator V2.0 is a common enabler which makes many kinds of
PC cards usable.
Explanations not stated for (DOS) or (OS/2) apply to both DOS and OS/2.
1. Functions
The Auto Configurator V2.0
- Is a device driver which uses interfaces with the Card Services
Release 2.0/2.1.
- Makes a PC card usable automatically when the card is inserted.
- Releases the resources such as I/O port addresses, an interrupt
level, or system memory when the card is removed.
- Supports hot insertion/removal so that the card can be inserted/
removed anytime. (*1)
- Makes the card usable based on a file (script file) in which
resource/sequence information is described.
- Supports up to 8 PC card slots.
- Utilities for the Auto Configurator V2.0 are provided.
*1: As for the function of the Auto Configurator, a PC card can be
inserted/removed anytime. These operations may not be supported
by the driver/application of the card.
Refer to the documents for the card/driver/application.
2. Changes from the Auto Configurator V1.0
The Auto Configurator V2.0 provides the following improvements over V1.0:
1. Reduction of the resident size (DOS)
The resident size is reduced from 13KB to 7KB.
2. Script file to enable many kinds of PC cards
To enable PC cards which are not registerd for the Auto Configurator,
a script file in which assigned resource and sequence are described
is used.
3. Setup of beep sound for 4 states
In addition to the time when a PC card is inserted/removed, the
Auto Configurator beeps when the card is enabled/not enabled.
A user can change the beep sound.
Note: An INI file for V1.0 can't be used with the Auto Configurator
V2.0.
3. Enabled PC Cards
Refer to PCMCIA.CRD for the list of PC cards that can be enabled by
the Auto Configurator V2.0.
4. Installation of the Auto Configurator V2.0
The installer installs the Auto Configurator V2.0 and related modules,
and updates CONFIG.SYS.
This section describes how CONFIG.SYS is updated.
Example of DOS CONFIG.SYS
DEVICEHIGH=C:\EZPLAY\IBMDSS01.SYS
DEVICEHIGH=C:\EZPLAY\IBMDOSCS.SYS
DEVICEHIGH=C:\EZPLAY\DICRMU01.SYS /MA=C000-CFFF
DEVICEHIGH=C:\EZPLAY\AUTODRV.SYS <- Auto Configurator
Example of OS/2 CONFIG.SYS
BASEDEV=PCMCIA.SYS
BASEDEV=IBM2SS01.SYS
BASEDEV=AUTODRV2.SYS <- Auto Configurator
DEVICE=C:\EZPLAY\VPCMCIA.SYS
DEVICE=C:\OS2\BOOT\COM.SYS
DEVICE=C:\OS2\MDOS\VCOM.SYS
5. Script File
Information for recognition of PC card, resources (I/O ports, an
interrupt level, system memory, and so on) to be assigned, and a sequence
to enable/disable the card are described in a script file.
An utility for the Auto Configurator V2.0 analyzes the contents of the
script file, and registers it into the Auto Configurator.
The Auto Configurator enables each PC card according to the registered
information.
As a default, the Auto Configurator enables almost all modem cards
and the IBM SCSI card. As for DOS, it enables the IBM 3270 card too.
If you have other PC cards you want to enable, read "5-1. Create Your
Script File".
5-1. Create Your Script File
There are script files for some kinds of PC cards in the directory
where the Auto Configurator is installed. When you select the script
files for PC cards you want to enable from the utility, the
utility creates a script file AUTODRV.SCR (DOS), AUTODRV2.SCR
(OS/2). If you can't find a script file for a PC card you want to
enable, read "5-2. Add Script File for New PC Card".
As the next step, the utility analyzes the script file, and registers
it into the Auto Configurator.
After the system is rebooted, you can use the PC cards described in
the script file.
5-2. Add Script File for New PC Card
According to "7. How to Write Script File", write the required
information for the new PC card. After that, do the same as in 5-1.
Note: Do NOT forget "End" at the last line in the
script file.
6. Auto Configurator Utility
The Auto Configurator Utility provides the following functions for the
Auto Configurator. (For more details about Windows or OS/2, refer to
the manual for the Auto Configurator Utility.)
The Auto Configurator Utility provides functions to:
- select script files for PC cards, and create a script file from them.
- analyze the script file, and registers it into the Auto Configurator.
- GUI utilities are provided for Windows and OS/2.
- An utility is provided to register contents of the script file into
the Auto Configurator for DOS.
6-1. DOS Auto Configurator Utility
Do the following to register contents of the script file into the
Auto Configurator for DOS.
1. As explained in "5. Script File", create a script file AUTODRV.SCR
by gathering script files for PC cards you want to enable.
2. Type the following from the DOS prompt.
AUTOUTL /D
Hit the Enter key.
Note that the utility (AUTOUTL.EXE), the script file (AUTODRV.SCR),
and the Auto Configurator (AUTODRV.SYS) must be in the same
directory.
3. When the script file has an error, a message is displayed.
Correct it, and try the same operation again.
7. How to Write Script Files
If you can't find a script file for a PC card you want to enable from
the provided script files for some kinds of PC cards, or you want to
change the parameters in the script files, read this section.
Note: Keywords (CardID, FunctionID, and so on) are described from
column 1 to 15, and "=" (equal) is described in column 16.
Commands, parameters, and so on should be described from column
17.
7-1. First Line
; IBM PC Card Script File for IBM Auto-Configurator V2.0
Note: - This line is used to make sure that a script file is for the Auto
Configurator V2.0. This line should NOT be deleted nor changed.
7-2. Comment Line
; Modem Card (Common)
Note: - A line containing ";" (semi-colon) at the first column is a comment
line.
7-3. Beep
Beep =1000,2,2000,2,800,2,20000,10
Note: - The frequency(Hz) and duration for a beep are specified.
- The Auto Configurator beeps in the following state:
Card was removed
Card was inserted
Card was enabled
Card wasn't enabled
- "Card wasn't enabled" means "An error occurred".
When the inserted card isn't supported, the Auto Configurator
doesn't beep.
- Explanation of the Example
1000,2,2000,2,800,2,20000,10
------ ------ ----- --------
| | | |
| | | +- Card wasn't enabled
| | +------- Card was enabled
| +-------------- Card was removed
+--------------------- Card was inserted
- The "Frequency,Duration" for each state should be described.
If you don't want a beep for any state, specify 0 (zero) as the
Frequency.
- The "Beep" statement is necessary, and it should NOT be moved or
removed.
7-4. Card ID
CardID =MODEM,MD24XC,116E2,118C2,FC2400,2460MC,FC24F,MF0B
Note: - The Auto Configurator uses a string in Tuple(*2) 0x15 (Level 1
Version/Product Information Tuple) to identify which card is
inserted. The string(s) is(are) described as card ID (CardID).
- This line is case sensitive. "MODEM" and "Modem" are different.
- "," (comma) is used as a separator when multiple card IDs are
described.
- " " (blank) is treated as a part of a card ID. Unnecessary
blank should NOT be inserted. (Blank at the end of a line isn't
treated as a part of the Card ID.)
- The total length for a CardID is under 64 characters, containing
commas.
- Explanation of the Example
MODEM General modem cards
MD24XC OMRON Fax/Data Modem card
116E2 OKI Modem card 2400
118C2 OKI Modem card Fax/Data
FC2400 Dr.Neuhaus Mikroelektronik GmbH FURY CARD 2400
2460MC ELSA GmbH MicroLink 2460MC
FC24F RATOC REX-5565
MF0B MITSUBISHI Voice/Fax/Data/Modem Card
*2: A PC card has infomation, such as name, type, or functions
in itself. The area of a card information contains links
of data blocks called "Tuple". Each Tuple has different
kinds of information.
7-5. Function ID
FunctionID =0x02
Note: - If there is no string described as the card ID in Tuple 0x15 of the
inserted card, the Auto Configurator uses a value in Tuple
0x21 (Function ID Tuple) to identify which card is inserted. The
value is described as the function ID (FunctionID).
- If you don't want to use a function ID to identify a card,
specify "0xFF" for the FunctionID.
- "0x" represents the value in hexa-decimal. For example, "0x10"
is hexa-decimal 10 (decimal 16), "10" is decimal 10.
- Explanation of the Example:
0x02 Serial Port
7-6. Manufacturer ID
ManufacturerID =0x00A4
Note: - If the Auto Configurator finds a string described as the card ID in
Tuple 0x15 of the inserted card, or a value described as the Function
ID in Tuple 0x21 of the card, it checks a value in Tuple 0x20
(Manufacturer ID Tuple) to identify which card is inserted. The
value is described as the manufacturer ID (ManufacturerID).
- If you don't want to use a manufacturer ID to identify a card,
specify "0xFFFF" for the ManufacturerID.
- Explanation of the Example:
0x00A4 IBM
7-7. Card ID not to enable PC card
IgnoreCardID =SDLC,Serial IR,Sound Card
Note: - When a string specified for IgnoreCardID is in Tuple 0x15, the
Auto Configurator doesn't enable the PC card.
- This line is case sensitive. "SDLC" and "Sdlc" are different.
- "," (comma) is used as a separator when multiple card IDs are
described.
- " " (blank) is treated as a part of a card ID. Unnecessary
blanks should NOT be inserted. ( A blank at the end of a line isn't
treated as a part of the Card ID.)
- When IgnoreCardID isn't needed, write nothing.
- The total length for a CardID is under 64 characters, containing
commas.
- Explanation of the Example:
SDLC IBM PCMCIA SDLC Modem
Serial IR IBM PCMCIA Serial IR Adapter Card
Sound Card Roland PCMCIA Sound Card
7-8. Enable Sequence
EnableSequence =ReqIO(0x2F8,0xFF,0,0,0,0,0xFF)
Note: - A sequence to enable a PC card is described after the parameter
"EnableSequence =".
- Commands for the enable sequence should start from column 17.
7-9. Disable Sequence
DisableSequence=RestoreBDA
Note: - A sequence to disable a PC card when the PC card is removed is
described after the parameter "DisableSequence =".
- Commands for the disable sequence should start from column 17.
- Resources (I/O port, an interrupt level, or system memory) reserved
by the ReqIO, ReqIRQ, ReqConfig, and ReqWindow commands in the
enable sequence are released when the PC card is removed.
(*3) Since the Auto Configurator does this automatically, you don't
need to describe the operation in the disable sequence.
*3: Since the used resources are released when the PC card is removed,
another PC card can use these resources when it is inserted.
7-10. End of Script File
End
Note: - "End" means the end of the script file and is necessary.
- "End" is described as the end of a sequence too (explained later),
but "End" for the end of a script file starts from column 1.
7-11. Commands for Enable/Disable Sequence
The following commands are used for the enable/disable sequence.
7-11-1. Get I/O Port Address
ReqIO(0x2F8,0xFF,0,0,0,0,0xFF)
Note: - The Auto Configurator requests the Card Services to assign an I/O
port address for the PC card.
- Explanation of the Example:
ReqIO(0x2F8,0xFF,0,0,0,0,0xFF)
| | | | | | |
| | | | | | +- Number of I/O Address Lines
| | | | | +--- Attributes 2
| | | | +----- Number of Contiguous Ports 2
| | | +------- Base Port Address for Range 2
| | +--------- Attributes 1
| +-------------- Number of Contiguous Ports 1
+-------------------- Base Port Address for Range 1
Attributes 1/Attributes 2
bit 7 6 5 4 3 2 1 0
0 0 0 0 x x x x
| | | |
| | | +- Shared (1=true)
| | +--- First Shared (1=true)
| +----- Force Alias Accessibility
+------- Data Path Width for I/O Range
(1=16 bit, 0=8 bit)
"0" should be 0 (zero).
"x" is 1 or 0 (zero).
- If "0xFF" is specified for the number of the I/O address lines,
the contiguous ports 1 or the contiguous ports 2, the value
set for the card is assigned from the tuples in the card.
7-11-2. Get Interrupt Level
ReqIRQ(0,3)
Note: - The Auto Configurator requests the Card Services to get an interrupt
level (IRQ) for the PC card.
- Explanation of the Example:
ReqIRQ(0,3)
| |
| +- Interrupt Level
+--- Attributes
Attributes
bit151413121110 9 8 7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0 0 0 0 0 x x x x
| | | |
| | +-+- IRQ Type
| | 0: Exclusive
| | 1: Time-Multiplexed Sharing
| | 2: Dynamic Sharing
| | 3: Reserved
| +----- Force Pulse (1=true)
+------- First Shared (1=true)
- If "0xFF" is specified for the interrupt level, the value set for
the card is assigned from the tuples in the card.
7-11-3. Configure PC Card
ReqConfig(0xFF,0xFF,0xFF,0x48,0,0,0x40)
Note: - The Auto Configurator requests the Card Services to configure the
PC card.
- Explanation of the Example:
ReqConfig(0xFF,0xFF,0xFF,0x48,0,0,0x40)
| | | | | | |
| | | | | | +- CCR: Option Register Setting
| | | | | +--- CCR: Socket/Copy Register Setting
| | | | +----- CCR: Pin Replacement Register Setting
| | | +---------- CCR: Status Register Setting
| | +--------------- Vpp2
| +-------------------- Vpp1
+------------------------- Vcc
- If "0xFF" is specified for Vcc, Vpp1, or Vpp2, the value set for
the card is assigned from the tuples in the card.
- If the value for the lower 6 bits in the Option register is 0 (zero),
the index information in Tuple 0x1B (Configuration Entry Tuple) is
set automatically. If it isn't 0, the value specified is set, and
the index information in the tuple isn't set.
7-11-4. Get System Memory Window
ReqWindow(1,0x000C,0xCA000,0x2000,0xFF)
Note: - The Auto Configurator requests the Card Services to get a system
memory window for the PC card.
- Explanation of the Example:
ReqWindow(1,0x000C,0xCA000,0x2000,0xFF)
| | | | |
| | | | +- Window Speed Field
| | | +-------- Memory Window Size
| | +---------------- System Base Address
| +----------------------- Attributes
+------------------------- Window Number
Attributes
bit151413121110 9 8 7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0 0 x x 0 x x x 0
| | | | |
| | | | +- Memory Type
| | | | (1=attribute)
| | | +--- Enabled (1=true, 0=disabled)
| | +----- Data Path Width
| | (1=16 bit, 0=8 bit)
| +--------- Shared (1=true)
+----------- First Shared (1=true)
- The window Number is used to get system memory windows.
It starts from 1.
- If "0xFF" is specified in the window speed field, the value set
for the card is assigned from the tuples in the card.
7-11-5. Map to Memory on PC Card
MapMemPage(1,0xCC000)
Note: - The Auto Configurator requests the Card Services to map a system
memory window to the memory on the PC card.
- Explanation of the Example:
MapMemPage(1,0xCC000)
| |
| +- Card Offset Address
+--- Window Number
- The value specified by the "ReqWindow" command is used.
7-11-6. Release System Memory Window
RelWindow(1)
Note: - The Auto Configurator requests the Card Services to release
the system memory window assigned by ReqWindow.
- Explanation of the Example:
RelWindow(1)
|
+- Window Number
- The window number used by ReqWindow should be specified.
7-11-7. Access Configuration Register
AccessConfigReg(0,0,#1,0)
Note: - The Auto Configurator requests to read or write a PC Card
Configuration Register.
- The offset is a value from the base of the configuration registers.
- Explanation of the Example:
AccessConfigReg(0,0,#1,0)
| | | |
| | | +- Reserved
| | +---- Data Store Area
| +------ Offset
+-------- Action (0=Read, 1=Write)
Read data from a PC Card configuration register (offset 0),
and write it in #1.
AccessConfigReg(1,0,#1,0)
Read data from #1 and write it in a PC Card configuration
register (offset 0),
7-11-8. Setup COM Number
SetupCOM(0xFF)
Note: - Updates BIOS Data Area for a COM number used by, for example,
modem applications. (DOS)
- Registers a COM number to the COM driver. (OS/2)
- Explanation of the Example:
SetupCOM(0xFF)
|
+- COM Number
- When "1", "2", "3", or "4" is specified, the value is treated as
a COM number, and the BIOS Data Area for it is updated (DOS) , or
it is registered to the COM driver (OS/2). If the COM number has
been used already, this operation isn't executed.
- If "0xFF" is specified, the unused area in BIOS Data Area is updated
(DOS), or the unused COM number is registered to the COM driver
(OS/2). If all COM numbers have been used already, this operation
isn't executed.
- If the COM driver isn't installed, this operation isn't executed.
- Even if this operation isn't executed, the PC card is enabled.
7-11-9. Delete COM Number
DeleteCOM
Note: - Deletes the COM number set by SetupCOM.
- BIOS Data Area is restored (DOS), or the registration to the
COM driver is deleted (OS/2).
- If the COM driver isn't installed, this operation isn't executed.
7-11-10. IBM SCSI Card
IBM_SCSI
Note: - Unique operation for the IBM SCSI card is executed.
- This command can be used for the Future Domain SCSI Card (SCSI2GO).
7-11-11. IBM Token Ring Card
IBM_TokenRing(4)
Note: - Unique operation for the IBM Token Ring card is executed.
- Explanation of the Example:
IBM_TokenRing(4)
|
+- Ring Speed (MBPS)
- "4" or "16" is specified as the ring speed.
7-11-12. IBM Ethernet Card
IBM_Ethernet1
IBM_Ethernet2
Note: - Unique operation for the IBM Ethernet card is executed.
7-11-13. Set Data
Move(#1,0xF8)
Note: - Sets data in a data store area (*4).
- Explanation of the Example:
Move(#1,0xF8)
| |
| +- Data
+---- Data Store Area
Sets 0xF8 in #1.
*4: Data Store Area is an area, where 1 byte of data used by
memory read/write, port in/out, or others is stored.
"#1" to "#9" can be specified for a Data Store Area.
7-11-14. Write Data to System Memory
Write(0xCC000,#1)
Note: - Writes the data, in a data store area, to the system memory.
- Explanation of the Example:
Write(0xCC000,#1)
| |
| +- Data Store Area
+--------- System Memory Address
Writes data in #1 to 0xCC000.
7-11-15. Read Data from System Memory
Read(0xCC000,#1)
Note: - Reads data from the system memory, and writes it in a data store
area.
- Explanation of the Example:
Read(0xCC000,#1)
| |
| +- Data Store Area
+--------- System Memory Address
Reads data from 0xCC000, and writes it in #1.
7-11-16. Output Data to I/O Port
Out(0xA20,#1)
Note: - Outputs the data in a data store area to the I/O port.
- Explanation of the Example:
Out(0xA20,#1)
| |
| +- Data Store Area
+------- I/O Port Address
Outputs data in #1 to 0xA20.
7-11-17. Input Data from I/O Port
In(0xA20,#1)
Note: - Inputs data from the I/O port, and writes it in a data store area.
- Explanation of the Example:
In(0xA20,#1)
| |
| +- Data Store Area
+------- I/O Port Address
Inputs data from 0xA20, and writes it in #1.
7-11-18. Logical And
And(#1,#2)
Note: - Gets the logical "and" from the data in 2 data store areas, and
writes it in the data store area.
- Explanation of the Example:
And(#1,#2)
| |
| +- Data Store Area 2
+---- Data Store Area 1
Gets the logical "and" from the data in #1 and #2, and writes
it in #1. (#1 <- #1 & #2)
7-11-19. Logical Or
Or(#1,#2)
Note: - Gets the logical "or" from the data in 2 data store areas, and
writes it in the data store area.
- Explanation of the Example:
Or(#1,#2)
| |
| +- Data Store Area 2
+---- Data Store Area 1
Gets the logical "or" from the data in #1 and #2, and writes
it in #1. (#1 <- #1 | #2)
7-11-20. Conditional Jump 1
JumpE(#1,#2,$1)
Note: - If data in Data Store Area 1 equals to the data in Data Store Area
2, the sequence goes to specified label (*5).
- Explanation of the Example:
JumpE(#1,#2,$1)
| | |
| | +- Label
| +---- Data Store Area 2
+------- Data Store Area 1
If data in #1 equals to the data in #2, jump to label $1.
*5: In the enable/disable sequence, if you want to jump or go back to
some operations, the sequence can jump to the label you specify.
"$1" to "$9" can be used as the label.
7-11-21. Conditional Jump 2
JumpNE(#1,#2,$1)
Note: - If data in Data Store Area 1 doesn't equal to the data in Data Store
Area 2, the sequence goes to the specified label.
- Explanation of the Example:
JumpNE(#1,#2,$1)
| | |
| | +- Label
| +---- Data Store Area 2
+------- Data Store Area 1
If data in #1 doesn't equal to the data in #2, jump to label $1.
7-11-22. Jump
Jump($1)
Note: - The sequence goes to the specified label.
- Explanation of the Example:
Jump($1)
|
+- Label
Jump to label $1.
7-11-23. Label
Label($1)
Note: - Specifies the labels specified in the JumpE, JumpNE, or Jump command.
- Explanation of the Example:
Label($1)
|
+- Label
Specify label $1.
7-11-24. End of Sequence
End
Note: - "End" means the end of the sequence and is necessary.
8. Sample Script File
---- Start of File ------------------------------------------------------------
; IBM PC Card Script File for IBM Auto-Configurator V2.0
Beep =1000,2,2000,2,800,2,20000,10
; ---- Modem Card (Common) ----------------------------------------------------
CardID =MODEM,MD24XC,116E2,118C2,FC2400,2460MC
FunctionID =0x02
ManufacturerID =0xFFFF
IgnoreCardID =SDLC
EnableSequence =ReqIO(0x3F8,0xFF,0,0,0,0,0xFF)
ReqIRQ(1,4)
ReqConfig(0xFF,0xFF,0xFF,0x08,0,0,0x40)
SetupCOM(0xFF)
End
DisableSequence=DeleteCOM
End
CardID =MODEM,MD24XC,116E2,118C2,FC2400,2460MC
FunctionID =0x02
ManufacturerID =0xFFFF
IgnoreCardID =SDLC
EnableSequence =ReqIO(0x2F8,0xFF,0,0,0,0,0xFF)
ReqIRQ(1,3)
ReqConfig(0xFF,0xFF,0xFF,0x08,0,0,0x40)
SetupCOM(0xFF)
End
DisableSequence=DeleteCOM
End
CardID =MODEM,MD24XC,116E2,118C2,FC2400,2460MC
FunctionID =0x02
ManufacturerID =0xFFFF
IgnoreCardID =SDLC
EnableSequence =ReqIO(0x3E8,0x08,0,0,0,0,0x10)
ReqIRQ(1,4)
ReqConfig(0xFF,0xFF,0xFF,0x08,0,0,0x40)
SetupCOM(0xFF)
End
DisableSequence=DeleteCOM
End
CardID =MODEM,MD24XC,116E2,118C2,FC2400,2460MC
FunctionID =0x02
ManufacturerID =0xFFFF
IgnoreCardID =SDLC
EnableSequence =ReqIO(0x2E8,0x08,0,0,0,0,0x10)
ReqIRQ(1,3)
ReqConfig(0xFF,0xFF,0xFF,0x08,0,0,0x40)
SetupCOM(0xFF)
End
DisableSequence=DeleteCOM
End
; ---- IBM SCSI Card ----------------------------------------------------------
CardID =SCSI
FunctionID =0xFF
ManufacturerID =0x00A4
IgnoreCardID =
EnableSequence =ReqIO(0x140,0xFF,0,0,0,0,0xFF)
ReqIRQ(0,5)
ReqConfig(0xFF,0xFF,0xFF,0x08,0,0,0x40)
IBM_SCSI
End
DisableSequence=End
; ---- Future Domain SCSI Card (SCSI2GO) --------------------------------------
CardID =SCSI
FunctionID =0xFF
ManufacturerID =0x0130
IgnoreCardID =
EnableSequence =ReqIO(0x140,0xFF,0,0,0,0,0xFF)
ReqIRQ(0,5)
ReqConfig(0xFF,0xFF,0xFF,0x08,0,0,0x40)
IBM_SCSI
End
DisableSequence=End
; ---- IBM 3270 Card ----------------------------------------------------------
CardID =3270
FunctionID =0xFF
ManufacturerID =0x00A4
IgnoreCardID =
EnableSequence =ReqIO(0x2D0,0x10,0,0,0,0,0xFF)
ReqIRQ(0,9)
ReqConfig(0xFF,0xFF,0xFF,0,0,0,0x40)
ReqWindow(1,0x000C,0xCE000,0x2000,0xFF)
MapMemPage(1,0)
End
DisableSequence=End
; ---- IBM Token Ring Card ----------------------------------------------------
CardID =TOKEN RING
FunctionID =0xFF
ManufacturerID =0xFFFF
IgnoreCardID =
EnableSequence =ReqIO(0xA20,0xFF,0,0,0,0,0xFF)
ReqIRQ(0,9)
ReqConfig(0xFF,0xFF,0xFF,0x20,0,0,0x40)
ReqWindow(1,0x000C,0xCA000,0x2000,0xFF)
MapMemPage(1,0xCA000)
ReqWindow(2,0x000C,0xCC000,0x4000,0xFF)
MapMemPage(2,0xCC000)
IBM_TokenRing(4)
End
DisableSequence=End
; ---- IBM Ethernet Card ------------------------------------------------------
CardID =Ethernet
FunctionID =0xFF
ManufacturerID =0x00A4
IgnoreCardID =
EnableSequence =ReqIO(0x300,0x20,0,0,0,0,0x10)
ReqIRQ(0,5)
ReqConfig(0xFF,0xFF,0xFF,0x20,0,0,0x40)
ReqWindow(1,0x000E,0xCC000,0x4000,0x04)
MapMemPage(1,0x20000)
Read(0xCC000,#1)
Move(#2,0x80)
Or(#1,#2)
Write(0xCC000,#1)
Move(#1,0x41)
Write(0xCC000,#1)
MapMemPage(1,0)
IBM_Ethernet1
RelWindow(1)
ReqWindow(1,0x000C,0xCC000,0x4000,0x04)
MapMemPage(1,0x4000)
IBM_Ethernet2
End
DisableSequence=End
End
---- End of File --------------------------------------------------------------