READPKT.TXT Driver File Contents (dsdsk401.exe)

Aironet Wireless LAN Software

Packet Driver Installation Procedures

The packet driver is a TSR program that implements the Packet Driver
Interface Specification as defined by FTP software.
The packet driver is invoked by the following DOS command line:

    awcpkt  [-cnwumi] <int_number>    - ARLAN PC Adapter
    awcp690 [-cnwumi] <int_number>    - ARLAN PCMCIA 690 Adapter
    PKTCFG.EXE    - Utility to parse pkt.ini to pkt.cfg file
    PCMCFG.EXE    - Utility to parse pcmcia.ini to pcmcia.cfg file.
    PKT900.INI    - Sample pkt.ini for 900 Mhz
    PKT24.INI     - Sample pkt.ini for 2.4 Ghz 
	(pkt900.ini & pkt24.ini MUST BE RENAMED TO PKT.INI 
    PKT001.MSG    - Language file for English (default)
    PKT002.MSG    - Language file for French Canadian
    PKT033.MSG    - Language file for France
    PKT034.MSG    - Language file for Spain
    PKT039.MSG    - Language file for Italy
    PKT049.MSG    - Language file for Germany

    **note**        (Language file must be in root directory)

-c    allow IEEEDRV.EXE from FTP software to properly load.
-n    allow usage with BYU Novell-Packet Driver Converter
-w    allow usage with windows
-u    unload Packet Driver TSR
-m    Put driver into monitor mode. For use with the monitor mode ROM.
-i    Specify drive-path-filename of default configuration file pkt.cfg.
<int_number>    software interrupt for the packet driver to use. (i.e. 0x65)

2.1 Startup failure codes

    The driver startup failure codes are grouped in two catagories.
The first code is a startup reason code and the second code is an ARLAN
diagnostic reason code.

Startup reason codes        Description

    0x80        Reset timeout.  This error is generally hardware related the
		coprocessor could not be reset.

    0x81        Reset error.  This error is generally hardware related the
		coprocessor could not be properly reset.

    0x82        Nop command failed.  Sending nop command to coprocessor
		failed.  Generally caused by faulty hardware or coprocessor

    0x83        Config failed.  Sending the config command to the
		coprocessor failed.  Generally caused by faulty hardware or
		coprocessor firmware.

    0x84        Config timeout.  The config command timedout waiting to
		complete.  This is generally caused by faulty hardware or
		coprocessor firmware.

    0x85        Config error.  The data in the configuration file was
		invalid for this coprocessor type.  Verify correct default
		information exists in the config file for the coprocessor in

    0x86        Address timeout.  The coprocessor was unable to formulate
		a valid MAC address for itself.  Usually indicates faulty
		coprocessor hardware or firmware.

    0x87        COP timeout.  The coprocessor timed out waiting for a
		command to complete.  Usually indicates faulty coprocessor
		hardware or firmware.

    0x88        Nop did not complete.  The nop command failed to complete.
		This is generally caused by faulty coprocessor firmware or

    0x89        Nop command interrupt failure.  The nop command failed to
		generate the appropriate hardware interrupt.  This usually
		indicates faulty coprocessor hardware.

Diagnostic reason codes    Description

    0xEC            EEPROM error on radio module.
    0xED            Too many Txenable commands.
    0xEE            T410 chip failure.
    0xEF            On chip failure.
    0xF0            Invalid parameter found in command.
    0xF1            Invalid command received by coprocessor.
    0xF2            Reserved.
    0xF3            Load code error.
    0xF4            Invalid spreading code/channel.
    0xF5            Reserved.
    0xF6            Invalid config format.
    0xF7            Missing SS code.
    0xF8            Checksum error.
    0xF9            No more address space.
    0xFA            Transceiver not found.
    0xFB            Backbone failure.
    0xFC            SCC failure.
    0xFD            Local ram test failed.
    0xFE            EPROM checksum failed.
    0xFF            OK.

Diagnostic offset description has been added to the driver to assist in
determining which byte in the configuration structure the Dataspan card had
trouble with.  The offset will point to a byte field in the configuration
structure if a configuration error occurs.  This byte is only valid for
startup code 0x85.

Packet Driver Configuration

The configuration of the packet driver layer is done through a file called
"PKT.CFG".  PKT.CFG is created from an "INI" file using PKTCFG.EXE

PKT.INI definition:

Note: Two standalone programs, PKTCFG.EXE and PCMCFG.EXE, are included with
the driver.  These programs will convert the INI file to the required PKT.CFG
and PCMCIA.CFG files. The PKTCFG.EXE program can also be used to generate an
INI file from the CFG file.  The following are usage examples for PKTCFG.EXE

    Generate binary config file from ascii file.           PKTCFG BIN.INI
    Generate binary PCMCIA config file from ascii file.    PCMCFG BIN.INI
    Generate ascii file from binary config file.           PKTCFG PKT.CFG -I

The INI file used to configure the packet driver has the following format:

    BitRate = 0
    Channel =  0x3
    SystemId = 0x110
    RootRepeater =  0
    RegistrationMode =  1


[SpreadPacket]         The category identifier for the packet driver

BitRate                A number corresponding to the Spread Spectrum Code ID.
		       Byte must be zero if Channel is used.

Channel                A number corresponding to a preconfigured Radio Channel
		       which can be set between 0 and 14.(See product manual
		       to determine which channel to use.)

SystemID               System Identifier to uniquely define different networks.                       This must be a even value and same on all nodes of the
		       network.  The upper byte must be a 0x00 for Dataspan
		       networks and 0x02 for ARLAN networks.

RootRepeater           Used in the 411/671 card to indicate if the 411/671
		       card is a root or a repeater.
		       00    Root
		       01    Repeater

RegistrationMode       Indicates what mode the Spread Card will operate.
		       0    Peer to Peer Mode
		       1    Normal TMA Mode
		       2    Power-Saving TMA Mode

[Pcmcia]               The category identifier for the PCMCIA Configuration.

Socket                 The PCMCIA Socket being used.  Default is 1.

Irq                    The IRQ the PCMCIA Controller will use.
		       Default is 3.

BaseAddr               Shared RAM Base Address.  Default is 0xD000.

For assistance, 
Please see you User Guide or Technical Reference Manual.
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: web3, load: 1.75