OS2READ.TXT Driver File Contents (multi231.zip)

           INSTRUCTIONS TO USE MULTICARD ENABLER AND DRIVERS IN OS/2

We suggest that you print this file out and read through it 
before you try it. This is a simple, but sophisticated procedure. 
We expect the people who try this to be experienced computer and 
network users.  If you are uncomfortable doing these things or 
if these steps don't make sense, perhaps you should find someone 
who is more comfortable following these instructions. 

(1) Do NOT use the DOS install program in A:\  or in C:\APEXEM  !!!!!
    Rename the NET.OS2 file to NET.CFG on the C: drive. Do Not use the
    NET.CFG provided on the floppy disk in A:\ since it is for DOS.

(2) Software required: IBM OS2 version 2.1;
                       Netware client for OS2;
                       IBM Socket Services (provided with your Thinkpad);
                       MultiCard enabler APEXEM.OS2
                       ODI driver EMODI.OS2 for ODI environment, or
                       NDIS2.0 driver EMNDIS20.os2 for NDIS environment

(3) Copy point enabler files APEXEM.OS2 and EMODI.OS2 to \NETWARE directory 
    if you use ODI driver; or copy APEXEM.OS2 and EMNDIS20.OS2 
    to \IBMCOM\MACS if you use NDIS driver.

(4) List a directory of \OS2\COM.SYS
    Check the creation date making sure it is 6/17/93 or later. If the date
    is earlier, then call IBM OS2 support at 1-800-992-4777 and request the
    latest COM.SYS file. Upon receipt of the new file, replace the existing
    COM.SYS.

(5) From the OS2 command prompt folder select OS2 window and go to the OS2
    root directory (C:\ or D:\ ect.). Bring up your CONFIG.SYS file in the
    OS2 editor. Complete the following steps:

        a. If you need card services in your OS2 environment, verify that 
	   PCMCIA.SYS is present and is being loaded.  If card services are 
	   absent, the enabler will interface directly with  the PCMCIA 
	   controller.
        b. Verify that COM.SYS is present and is being loaded. If it is
           not present, add it.
        c. Replace the original driver with MultiCard driver if your
           installation selected other than MultiCard driver:
                For ODI:    DEVICE=C:\NETWARE\EMODI.OS2
                For NDIS:   DEVICE=C:\IBMCOM\MACS\EMNDIS20.OS2
        d. Add the enabler following all netware drivers:
           DEVICE=C:\NETWARE\APEXEM.OS2 /INT=XX /COM=XX /SOC=XX /MEM=XXXXX
           The command parameters has the following meanings:
                /INT=XX -- IRQ used for LAN interrupt. The default
                           setting is 5.
                /COM=XX -- COM port number. Support 0 t0 6
                    /COM=0: no COM port selected
                    /COM=1: port address: 0x3f8 -- 0x3ff; IRQ -- 4
                    /COM=2: port address: 0x2f8 -- 0x2ff; IRQ -- 3
                    /COM=3: port address: 0x3220 -- 0x3227; IRQ -- 4
                    /COM=4: port address: 0x3228 -- 0x322f; IRQ -- 3
                    /COM=5: port address: 0x3e8 -- 0x3ef; IRQ -- 4
                    /COM=6: port address: 0x2e8 -- 0x2ef; IRQ -- 3
                           The default setting is 2.
                /SOC=XX -- Only 1 and 2 are supported. Used only when Card
                           Services is not loaded and ignored by the enabler
                           if Card Services found. It specifies the socket
                           number the MultiCard will be inserted. The default
                           setting is 1.
                /MEM=XX -- Supported values: C0, C4, C8, D0, D4, and D8.
                           Memory address for common and attribute memory
                           of MultiCard card. The default setting is d0.
                /N         No check on the MultiCard IDs in the CIS memory.
                           In case the Card Services is absent, the enabler
                           always assumes that the card inserted in the
                           specified socket is MultiCard.

        e. If you need card services in your OS2 system, install your 
	   IBM Socket Services provided with your IBM Thinkpad.

        f. Verify your current CONFIG.SYS with the following order of the
           previously mentioned device drivers (assume all drivers are
           located on drive C:)
                                        ......
           (provided by OS2) - DEVICE=C:\OS2\COM.SYS
                                        ......
           (provided by OS2) - BASEDEV=C:\OS2\PCMCIA.SYS

           (Socket services  - BASEDEV=C:\OS2\ICRMU01.SYS
            drivers provided - BASEDEV=C:\OS2\IB2SS01.SYS
            by IBM)          - DEVICE=C:\OS2\AUTODRV2.SYS C:\OS2\AUTODRV2.INI
                               DEVICE=C:\MDOS\VPCMCIA.SYS
                                        ......
           (MultiCard driver) - DEVICE=C:\NETWARE\EMODI.OS2 ( for ODI) or
                                DEVICE=C:\IBMCOM\MACS\EMNDIS20.OS2 ( for ndis)
                                        ......
           (MultiCard enabler) -DEVICE=C:\NETWARE\APEXEM.OS2 (for ODI) or
                                DEVICE=C:\IBMCOM\MACS\APEXEM.OS2 (for ndis)
                                        ......

        (g) reboot the system

(7) If you encounter problems please run the EMLOOOK.EXE utility for help in
    determining the problem.

                            TECHNICAL INFORMATION

(1) In CONFIG.SYS, install Card Services followed by driver then enabler, then 
    Socket Services in the specified order.

(2) When no Card Services are present, the enabler interfaces directly to the 
    PCIC from Intel or TCIC from DATABOOK.

(3) Link driver name is MCARD for ODI OS/2 and MCARD$ for NDIS OS/2.

(4) When no Card Services are present, hot-swap will require the card being 
    re-inserted to the same socket where it is removed.

    With Card Services present, the card can be re-inserted to any socket.


(5) There are no hardware diagnostics of during initialization because of the 
    way Card and Socket Services work together with the enabler and driver. 
    Only during the “Device Driver InitializationComplete” backward call-back
    process, is the driver is able to access the hardware. But at that time,
    driver is already loaded there is no known way to un-load. What this means 
    is the driver will be loaded even when there is no hardware present.


Download Driver Pack

How To Update Drivers Manually

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.

server: web5, load: 0.58