Using the IFADAP.EXE utility
============================
LSS 7.1(0), September 2000
--------------------------
Summary
-------
The IFADAP program detects network adapters attached to a computer and allows
the selective loading of device drivers depending upon whether a particular
adapter is present. Use it to create boot configurations that load drivers
depending on the adapter hardware located in the computer. Run IFADAP as a
device driver from config.sys or from the command line/batch file.
Contents
--------
1) Using IFADAP.EXE for DOS from config.sys
2) Using IFADAP.EXE for DOS from the command line
3) IFADAP Options
3.1) Searching For Specific Adapters
3.2) Bus Searching
3.3) Device Driver Loading
3.4) Display And Reporting
3.5) ErrorLevel Modifiers
3.6) Card Services
4) Errorlevels (COMMAND LINE only)
5) Environment Variables (COMMAND LINE only)
6) Valid parameters
1) Using IFADAP for DOS from config.sys
---------------------------------------
device=IFADAP.EXE CARD=<card> [options] DD=<DDname> [DDoptions]
For valid [options], see the "Options" section below.
This will install the device driver <DDname> if the specified network adapter
is found.
Example :-
device=ifadap.exe CARD=IBM dd=dxmc0mod.sys
This will load dxmc0mod.sys, if an IBM adapter card is present.
If the specified device driver takes parameters then the whole command line
must be enclosed in quotes. For example:
device=ifadap.exe CARD=IBM DD="C:\DOS\EMM386.EXE X=CC00-CDFF"
This example loads EMM386.EXE with a certain range of memory excluded if
IFADAP finds an IBM adapter in the computer.
2) Using IFADAP for DOS from the command line
---------------------------------------------
IFADAP [options]
For valid [options], see the "Options" section below.
If you run IFADAP with no options, it will search for an adapter of any known
type. You can specify a particular type of adapter using the CARD or UCARD
option along with the RAM=, IO= and SLOT= options, in which case IFADAP will
only search for and report this type of adapter. You may only specify the
RAM, IO and SLOT parameters if a CARD or UCARD parameter is present on the
command line also.
When you run IFADAP from the command line, it sets environment variables and
returns an error level to reflect any adapter found. Environment variables
and error levels set by IFADAP may be tested in a batch file. If multiple
adapters are present, IFADAP sets the environment variables and the error
level to reflect the first adapter it locates.
Multiple adapters can be reported to the screen using the MULTI option.
Options may be preceded with a / or -. All options are case insensitive.
3) IFADAP Options
-----------------
The options to IFADAP can be split into six functional groups as follows:-
3.1) SEARCHING FOR SPECIFIC ADAPTERS
------------------------------------
CARD=<card>
-----------
Only search for adapters of type <card>.
Valid values for <card> are:-
IBM - Any IBM (or compatible) Tropic Based Card
SMT16/4 - Madge Smart Token Ring Adapters
SMT100 - Smart 100 FDDI Card
PCMCIA - Any Madge Smart 16/4 PCMCIA adapter
PRESTO - Madge Presto PCI Adapter
FOUR_MEG - Madge Four Megabit Adapter
IBM_PCMCIA - IBM PCMCIA Token Ring Adapter
IBM_AUTO - IBM Auto ISA Token Ring Adapter
IBM_AUTO_PNP - IBM Auto PNP Token Ring Adapter
IBM_STD - True IBM Tropic Adapter
MDG_STRAIGHT_BLUE - Madge Straight Blue Adapter
MDG_BLUE_PLUS - Madge Blue Plus Card
IBM_PCI - IBM Lanstreamer PCI Token Ring Adapter
THREECOM - 3Com IBM Compatible Card
CARD_BUS - Any Madge Cardbus adapter
PCI3 - Madge Smart 16/4 PCI Ringnode Mk3
PRESTO2 - Madge Presto Plus PCI Adapter
PRESTO2000 - Madge Presto 2000 PCI Adapter
PCI-HS - Madge Smart 100/16/4 PCI-HS Ringnode
PCI-HS2 - Madge Smart 100/16/4 PCI Ringnode
OLICOM_TMS - Olicom TI-TMS Adapters (OC-3117/3118/3133/3135/3136/3137)
OLICOM_PCMCIA - Olicom PCMCIA Adapter (GC-3221)
OLICOM_CARDBUS - Olicom CardBus Adapter (GC-3250)
OLICOM_PCI - Olicom RapidFire 16/4 PCI Adapters (RF-3139/3140/3141)
OLICOM_PCI-HS - Olicom RapidFire 100/16/4 Adapter (RF-3540)
If the card is found in the machine the errorlevel is 0. If the specified
card is NOT found in the machine the errorlevel is 1. This may seem
illogical but it is a convention that DOS programs return 0 on success.
UCARD=<card>
------------
Only search for adapters of type <card>. This alternative method of
specifying cards is more flexible because it allows each card to be
specified individually. The valid values for this option are:-
SMT100 - Smart 100 FDDI Card
IBM - True IBM Tropic Based Card
STRAIGHT_BLUE - Madge Straight Blue Adapter
BLUE_MC - Madge MC Blue Adapter
IBMAUTOISA - IBM Auto ISA Token Ring Adapter
IBMAUTOPNP - IBM Auto PNP Token Ring Adapter
THREECOM - 3Com IBM Compatible Card
IBMUNKNOWN - IBM Compatible Card from an unknown vendor
BLUE_PLUS - Madge Blue Plus Card
BLUE_PNP - Madge Blue PNP
CARDBUS2 - Madge Cardbus adapter Mk2
CARDBUS - Madge Cardbus adapter
PCMCIA - Madge Smart 16/4 PCMCIA adapter
PCMCIA2 - Madge Smart 16/4 PCMCIA Mk2
IBMPCMCIA - IBM PCMCIA Token Ring Adapter
XIRCOM - XIRCOM PCMCIA Token Ring Adapter
IBMPCI - IBM Lanstreamer PCI Token Ring Adapter
PCI1B - Madge Smart 16/4 PCI Ringnode
PCIBM1 - Madge Smart 16/4 PCI Ringnode (BM)
PCIBM2 - Madge Smart 16/4 PCI Ringnode (BM) Mk2
AT - Madge Smart 16/4 AT Card
FIBER - Madge Smart 16/4 Fiber AT Ringnode
BRIDGE - Madge Smart 16/4 AT Bridgenode
ISAC - Madge Smart 16/4 ISA Client Ringnode
ATP - Madge Smart 16/4 AT Plus Ringnode
ISACP - Madge Smart 16/4 ISA Client Plus Ringnode
ATPNP - Madge Smart 16/4 AT PnP Ringnode
MAXY - Madge Smart 16/4 MAXY Ring Node
PC - Madge Smart 16/4 PC Ring Node
ISACPNP - Madge Smart 16/4 ISA Client PnP Ringnode
EISA_MK1 - Madge Smart 16/4 EISA Ringnode
EISA_MK2 - Madge Smart 16/4 EISA Ringnode
EISA_MK3 - Madge Smart 16/4 EISA Ringnode
EISA_BRIDGE - Madge Smart 16/4 EISA Bridgenode
SMART16 - Madge Smart 16 Ringnode
MC16 - Madge Smart 16/4 MC Ringnode
MC32 - Madge Smart 16/4 MC32 Ringnode
PCI3 - Madge Smart 16/4 PCI Ringnode Mk3
PCI-HS - Madge Smart 100/16/4 PCI-HS Ringnode
PCI-HS2 - Madge Smart 100/16/4 PCI Ringnode
PRESTO - Madge Presto PCI Adapter
PRESTO2 - Madge Presto Plus PCI Adapter
PRESTO2000 - Madge Presto 2000 PCI Adapter
FOUR_MEG - Madge Four Megabit Adapter
OLICOM_3136 - Olicom Token-Ring PCI 16/4 Adapter (OC-3136)
OLICOM_3137 - Olicom Token-Ring PCI/II 16/4 Adapter (OC-3137)
OLICOM_3133 - Olicom Token-Ring EISA 16/4 Adapter (OC-3133)
OLICOM_3135 - Olicom Token-Ring EISA 16/4 Server Adapter (OC-3135)
OLICOM_3117 - Olicom Token-Ring ISA 16/4 Adapter (OC-3117)
OLICOM_3118 - Olicom Token-Ring ISA 16/4 Adapter (OC-3118)
OLICOM_3221 - Olicom GoCard Token-Ring PC Card (OC-3221)
OLICOM_3250 - Olicom GoCard 3250 Token-Ring 16/4 CardBus PC Card
OLICOM_3139 - Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter
OLICOM_3140 - Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter
OLICOM_3141 - Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter
OLICOM_3540 - Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter
OLICOM_3140V2 - Olicom RapidFire 3140 V2 16/4 TR PCI Adapter
If the card is found in the machine the errorlevel is 0. If the specified
card is NOT found in the machine the errorlevel is 1. This may seem
illogical but it is a convention that DOS programs return 0 on success.
RAM=<ram>
---------
Only report adapters with amount <ram> of RAM
Valid values are 64, 128, 256, 512.
IO=<io>
-------
Only report adapters at IO location <io>
SLOT=<slot>
-----------
Only report adapters at Slot location <slot>
This option is only valid for adapters which can have a slot number
associated with them. Adapters on PCI, EISA, PCMCIA, CARDBUS and MCA buses
have a slot number. ISA cards cannot have a slot number.
3.2) BUS SEARCHING
------------------
BUS=<bus type> BID=<bus identifier> (IFADAP for DOS only)
---------------------------------------------------------
These two arguments must be used together without any other adapter
specifiers, ie. no CARD, UCARD, IO, RAM or SLOT options may be used with
them.
They may be used with the 'DD =' argument to load a device driver.
<bus type> must be one of MCA, EISA, PNP, PCI or PCMCIA. The format of the
<bus identifier> depends on the <bus type>, as shown below:
<bus> <bus identifier>
----- ----------------
MCA AAAA/B AAAA is up to 4 hex digits (MCA POS ID)
B is a single decimal digit (Slot number)
EISA AAAA/BBB/C AAAA is up to 4 hex digits (Manuf'r ID)
BBB is up to 3 hex digits (Product ID)
C is a single hex digit (Slot number)
PCI AAAA/BBBB AAAA is up to 4 digits (Vendor ID)
BBBB is up to 4 digits (Device ID)
PNP AAAA/BBBB AAAA is up to 4 digits (Manufacturer ID)
BBBB is up to 4 digits (Device ID)
PCMCIA AAAA/BBBB/CCCC AAAA is up to 4 digits (Manufacturer ID)
BBBB is up to 4 digits (Device ID)
CCCC is up to 4 digits (Socket number)
Taken together, the two arguments may be used to specify any type of adapter
on a bus. If the card is found the errorlevels are set as for the other
adapter specifiers above, ie. 0 for found, or 1 for not found.
The utility WHATADAP.EXE is used to display a list of BUS and BID values for
all the devices in a computer. These values can then be used as an input to
IFADAP to detect a particular type of adapter. The BUS and BID parameters
are useful because modern buses (MCA, EISA, PCI, PNP, PCMCIA) have defined
methods of detecting specific adapter cards. Using these defined methods is
much safer (i.e will not disturb running cards) than the traditional method
of probing for cards. However, ISA (non PNP) cards cannot be found using
the BUS and BID parameters.
Users are cautioned against trying to generate their own sets of bus
information from any other source than running the WHATADAP.EXE utility. The
use of WHATADAP.EXE and the BUS and BID options to IFADAP.EXE provide a
general method of configuring device drivers for any type of adapter, not
just network adapters. (See the file WHATADAP.TXT for more details on using
WHATADAP.EXE.)
3.3) DEVICE DRIVER LOADING
--------------------------
DD="<DDname> [DDoptions]" (IFADAP for DOS)
------------------------------------------
This is an alternative to specifying the device driver to be loaded and its
options at the end of the device=ifadap.exe ... line in config.sys. This
option may be placed anywhere on the command line. If the DDoptions include
an option enclosed in quotes, \" must be used rather than " so that IFADAP
can differentiate this quote from the one which terminates the /DD="..."
option.
e.g
device = ifadap.exe CARD=ibm DD="testdrv.sys \"test\""
Certain types of device driver may also be loaded from the DOS command line
with IFADAP. For example:-
C:\> IFADAP CARD=SMT16/4 DD=C:\DOS\RAMDRIVE.SYS
~ (IFADAP for DOS, CONFIG.SYS only)
-------------------------------------
This negates the logic of IFADAP, ie if NO adapter of the specified type was
found then the device driver specified on the command line IS loaded.
Conversely, if the adapter specified WAS found then the device driver IS NOT
loaded.
QUESTION[="<question>"] (IFADAP for DOS only)
---------------------------------------------
If QUESTION is given on the command line then a default question is asked of
the user (unless overriden by specifying an alternative <question>) if IFADAP
finds a specified adapter. The user is asked whether he wants to load network
drivers and may reply either yes (F1) or no (F2). If the user replies "no"
then the result is as if IFADAP failed to find an adapter (environment
variables are cleared, or, if run as a device driver, no subsequent driver is
loaded).
3.4) DISPLAY AND REPORTING
--------------------------
RF[=<name>] (IFADAP for DOS only)
---------------------------------
Write adapter information to a file. This information is in the same format
as that displayed on the screen if an adapter is found. If no <name> is
specified then the default ifadap.out is used.
Q or QUIET
----------
Quiet option - don't display adapter information to the screen.
?, H, HELP
----------
Display help text.
MULTI
-----
If MULTI is specified on the command line then IFADAP will report the
presence of ALL recognized adapters in the machine which conform to the
parameters given on the command line. Without the /MULTI parameter only the
first adapter found is reported. The errorlevel and environment variables are
set to reflect the first adapter found. If no other parameters are given
("IFADAP /MULTI") then all adapters in the machine will be reported.
3.5) ERRORLEVEL MODIFIERS
-------------------------
ALTERR
------
If you specify ALTERR, IFADAP returns a different error level for each type
of Madge Smart Ringnode, rather than grouping them according to RAM size. See
the "Error levels" section for more details. Note that /ALTERR does not imply
/XIBM, ie. IBM and Madge Blue adapters will still be reported as error level
1 (Madge Blue / IBM Token Ring Adapter).
UNIFORM
-------
If this option is present then new errorlevels uniquely identify every
adapter recognised by IFADAP are returned. See the section on errorlevels
for the values of these errorlevels for individual cards.
XIBM (IFADAP for DOS only)
--------------------------
If a CARD or UCARD parameter is not specified, then display verbose IBM or
Madge IBM compatible (Straight Blue and Blue Plus) adapter names, as opposed
to the generic "Madge Blue/IBM Token Ring" label. This will also report
detailed error levels for IBM/Madge IBM compatible adapters, see the
"Errorlevels" section.
3.6) CARD SERVICES OPTIONS
--------------------------
ECS (IFADAP for DOS only)
-------------------------
If no PCMCIA Card Services are loaded, emulate Card Services functions.
IFADAP attempts to install an internal Card Services library so that it can
interrogate any PCMCIA adapters found. This allows IFADAP to find Madge
PCMCIA adapters on computers with no Card Services loaded. If no memory
address is specified (see the CSMEM section, below) IFADAP searches memory to
try and find a free block to use.
CSMEM=<address>
---------------
Only relevant if the /ECS option is also specified. The address specified is
the address in the upper memory block ( above 640K and below 1 MB ) which the
IFADAP Card Services emulator will try and use. Valid addresses are any 4K
memory block in the address range A000 to EF00 that is not in use by a memory
device driver (eg. EMM386.SYS) or other installed hardware. IFADAP tries to
verify that nothing else is using the memory before it uses it, but there may
be cases where it does conflict with other devices, possibly causing a system
crash or hang. If IFADAP detects another user of the specified memory it
prints an error message and continues without loading its Card Services.
4) Error levels (COMMAND LINE only)
-----------------------------------
When IFADAP.EXE terminates it returns an error level to the command shell. An
error level is an integer value which can be used to determine the success of
an operation. IFADAP uses error levels to indicate the type of adapter
located in the machine.
If IFADAP is run with card details (CARD= etc.) specified, then an error
level of 0 is returned if the specified adapter is found and an error level
of 1 is returned if it is not.
If IFADAP is run with no card details (CARD= etc.) specified, then an error
level is returned based on the type of the first adapter found:
error level 0 - no adapter found
1 - Madge Blue / IBM Token Ring adapter found
2 - 128K Madge Smart 16/4 Ringnode found
3 - 256K Madge Smart 16/4 Ringnode found
4 - 512K Madge Smart 16/4 Ringnode found
5 - Madge Smart 16/4 Ringnode found (RAM unknown)
6 - Madge Smart 100 Ringnode found
7 - Madge Smart 16/4 Pocket Ringnode found
8 - Xircom Pocket Token-Ring adapter found
9 - Madge Smart 16/4 PCMCIA Ringnode found
10 - Madge Four Megabit Adapter
11 - IBM PCMCIA Token Ring Adapter
12 - IBM PCI LanStreamer Token Ring Adapter
13 - Madge 16/4 CardBus Token-Ring Adapter
14 - Madge Presto PCI Token-Ring Adapter
15 - Madge Smart 16/4 PCI Ringnode Mk3
16 - Madge Presto Plus PCI Token-Ring Adapter
17 - Madge Smart 100/16/4 PCI-HS Ringnode
18 - Madge Smart 100/16/4 PCI Ringnode
19 - Madge Presto 2000 PCI Token-Ring Adapter
60 - Olicom TI-TMS Adapters (OC-3117/3118/3133/3135/3136/3137)
61 - Olicom PCMCIA Adapter (GC-3221)
62 - Olicom CardBus Adapter (GC-3250)
63 - Olicom RapidFire 16/4 PCI Adapters (RF-3139/3140/3140V2/3141)
64 - Olicom RapidFire 100/16/4 Adapter (RF-3540)
If you specify /XIBM, IFADAP returns the following error levels instead of
errorlevel 1:
41 - IBM Token Ring Adapter
42 - IBM Auto ISA Token Ring Adapter
43 - IBM Auto ISA Plug And Play Adapter
44 - Madge Straight Blue Adapter
45 - Madge Blue Plus Adapter
46 - 3Com Token Ring adapter (IBM compatible)
If you specify /ALTERR, IFADAP returns the following error levels instead of
error level 2,3,4 or 5:
20 - Madge Smart 16/4 AT Ringnode
21 - Madge Smart 16/4 PC Ringnode
22 - Madge Smart 16/4 MAXY Ringnode
23 - Madge Smart 16/4 AT Fiber Ringnode
24 - Madge Smart 16/4 AT Bridgenode
25 - Madge Smart 16/4 ISA Client Ringnode
26 - Madge Smart 16/4 AT Plus Ringnode (AT mode)
27 - Madge Smart 16/4 AT Plus Ringnode
28 - Madge Smart 16/4 ISA Client Plus Ringnode
30 - Madge Smart 16/4 MC Ringnode
31 - Madge Smart 16/4 MC16 Ringnode
32 - Madge Smart 16/4 EISA Ringnode Mk1
33 - Madge Smart 16/4 EISA Ringnode Mk2
34 - Madge Smart 16/4 EISA Bridgenode
35 - Madge Smart 16/4 MC32 Ringnode
36 - Madge Smart 16/4 MC32 Bridgenode
37 - Madge Smart 16/4 PCI Ringnode
38 - Madge Smart 16/4 PCI Ringnode (BM) Mk1
39 - Madge Smart 16/4 ISA Client PnP Ringnode
40 - Madge Smart 16 Ringnode
50 - Madge Smart 16/4 PCI Ringnode (BM) Mk2
51 - Madge Smart 16/4 PCMCIA Ringnode Mk2
If you specify /UNIFORM, IFADAP returns the following set of error levels:-
142 - Smart 100 FDDI Card
101 - True IBM Tropic Based Card
102 - Madge Straight Blue Adapter
103 - Madge MC Blue Adapter
104 - Madge Blue Plus Card
105 - Madge Blue PNP
143 - IBM Auto ISA Token Ring Adapter
144 - IBM Auto PNP Token Ring Adapter
145 - 3Com IBM Compatible Card
146 - IBM Compatible Card from an unknown vendor
127 - Madge Cardbus adapter Mk2
129 - Madge Cardbus adapter
118 - Madge Smart 16/4 PCMCIA adapter
119 - Madge Smart 16/4 PCMCIA Mk2
147 - IBM PCMCIA Token Ring Adapter
148 - XIRCOM PCMCIA Token Ring Adapter
133 - IBM Lanstreamer PCI Token Ring Adapter
120 - Madge Smart 16/4 PCI Ringnode
121 - Madge Smart 16/4 PCI Ringnode (BM) Mk1
122 - Madge Smart 16/4 PCI Ringnode (BM) Mk2
106 - Madge Smart 16/4 AT Card
107 - Madge Smart 16/4 Fiber AT Ringnode
108 - Madge Smart 16/4 AT Bridgenode
109 - Madge Smart 16/4 ISA Client Ringnode
110 - Madge Smart 16/4 AT Plus Ringnode
111 - Madge Smart 16/4 ISA Client Plus Ringnode
112 - Madge Smart 16/4 AT PnP Ringnode
140 - Madge Smart 16/4 MAXY Ring Node
141 - Madge Smart 16/4 PC Ring Node
113 - Madge Smart 16/4 ISA Client PnP Ringnode
114 - Madge Smart 16/4 EISA Ringnode
115 - Madge Smart 16/4 EISA Ringnode
116 - Madge Smart 16/4 EISA Ringnode
117 - Madge Smart 16/4 EISA Bridgenode
130 - Madge Smart 16 Ringnode
131 - Madge Smart 16/4 MC Ringnode
132 - Madge Smart 16/4 MC32 Ringnode
124 - Madge Smart 16/4 PCI Ringnode Mk3
128 - Madge Smart 100/16/4 PCI-HS Ringnode
150 - Madge Smart 100/16/4 PCI Ringnode
123 - Madge Presto PCI Adapter
126 - Madge Presto Plus PCI Adapter
149 - Madge Presto 2000 PCI Adapter
139 - Madge Four Megabit Adapter
151 - Olicom Token-Ring 16/4 PCI Adapter (OC-3136)
152 - Olicom Token-Ring 16/4 PCI/II Adapter (OC-3137)
153 - Olicom Token-Ring 16/4 EISA Adapter (OC-3133)
154 - Olicom Token-Ring 16/4 EISA Server Adapter (OC-3135)
155 - Olicom Token-Ring 16/4 ISA Adapter (OC-3117)
156 - Olicom Token-Ring 16/4 ISA Adapter (OC-3118)
157 - Olicom GoCard Token-Ring PC Card (OC-3221)
160 - Olicom GoCard 3250 Token-Ring 16/4 CardBus PC Card
161 - Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter
162 - Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter
163 - Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter
164 - Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter
165 - Olicom RapidFire 3140 V2 16/4 TR PCI Adapter
5) Environment variables (COMMAND LINE only)
--------------------------------------------
The CARD, RAM, SLOT, DMA, IRQ, NODEADDR, BUS and IO environment variables are
set by IFADAP when it is run from the command line, regardless of whether you
specified any parameters. They give the attributes of the first adapter
IFADAP found, or are cleared if IFADAP returns "Adapter not found".
Example :-
C:\>ifadap CARD=SMT16/4
If a Madge Smart 16/4 Ringnode is found, IFADAP sets the following environment
variables if they are known and appropriate:
CARD=SMT16/4 / card type
RAM=<ram> / amount of adapter ram
IO=<io> / IO base address
SLOT=<slot> / slot number (if applicable)
IRQ=<irq> / IRQ number
DMA=<dma> / DMA channel (if applicable)
BUS=<bus> / Bus architecture
NODEADDR=<bia> / Burnt-In Node Address
If IFADAP did not find a Madge adapter, it clears these environment variables.
If IFADAP finds multiple adapters (using the /MULTI command line switch) the
environment variables reflect the first adapter only. However, the IO
addresses of additional adapters will be set in the variables IO2, IO3 etc..
If particular environment variables are not relevant for the adapter found,
eg RAM= and IO= for a Xircom adapter, then IFADAP clears them (see below).
6) Valid parameters
-------------------
The valid <io>, <slot> and <ram> parameters depend upon which <card> you
specify. IFADAP only does limited checking on valid values. If for instance
an invalid <io> address is specified for the particular card being searched
for then IFADAP will never find the card. Ensure that the parameters given
are valid for the card specified.
When you run IFADAP from the command line, the CARD, RAM, IO, IRQ,
SLOT and DMA environment variables are set to the relevant values from those
given below. If there are no valid values for a particular attribute, then
that environment variable is cleared.
Note : You must load Card & Socket Services for IFADAP to be able to detect
PCMCIA adapters.
Madge 4Mbit adapter <card> = FOURMEG <io> = 0A20, 1A20, 2A20, 3A20
Madge Blue / IBM adapter <card> = IBM, IBM_STD, IBM_AUTO_PNP, IBM_AUTO,
MDG_STRAIGHT,BLUE, MDG_BLUE_PLUS <io> = 0A20, 0A24
IBM PCI LanStreamer Token Ring adapter <card> = IBM_PCI <io> = any
IBM PCMCIA Token Ring adapter <card> = IBM_PCMCIA <io> = any
Madge Smart 16/4 PCMCIA Ringnode <card> = PCMCIA <ram> = 512 <io> = any
<slot>= 0 - 15
Madge Smart 16/4 Pocket Ringnode <card> = POCKET
Madge Smart 16/4 Ringnode <card> = SMT16/4 <ram> = 128, 256, 512 <io> =
920, 940, 960, 980 A20, A40, A60, A80, B20, B40, B60, B80, 1A20, 2A20, 3A20,
4A20, E20, 1E20, 2E20, 3E20, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000,
9000, A000, B000, C000, D000, E000, F000, + xx00 for PCI adapters <slot>= 0 -
15
Madge Smart 100 Ringnode <card> = SMT100 <ram> = * no valid values * <io> =
1C80, 2C80, 3C80, 4C80, 5C80, 6C80, 7C80, 8C80, 9C80, AC80, BC80, CC80, DC80,
EC80, FC80 <slot>= 1 - 15
Xircom Pocket Token-Ring adapter <card> = XIRCOM
Madge Presto PCI<card> = PRESTO <io> = any <slot>= 1 - 31
Madge PCI Presto Mk2 <card> = PRESTO2 <io> = any <slot>= 1 - 31
Madge Smart 16/4 PCI Ringnode Mk3 <card> = PCI3 <io> = any <slot>= 1 - 31
See Also
--------
Further details of using WHATADAP.EXE to provide data for IFADAP.EXE can be
found in WHATADAP.TXT
**** End of IFADAP.TXT ****
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.