Page 1
MX2 Reference Guide
IMPORTANT NOTICE
LXE’s MX2 is obsolete.
This electronic manual has been made available as a courtesy to LXE's MX2
customers. Please contact your LXE customer support representative for
assistance and mobile device replacement.
Copyright © June 2006 by LXE Inc.
All Rights Reserved
E-EQ-MX2RG-L-ARC
Page 2
Notices
Notice:
LXE Inc. reserves the right to make improvements or changes in the products described in this manual at any time
without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy,
LXE assumes no liability resulting from any errors or omissions in this document, or from the use of the
information contained herein. Further, LXE Incorporated, reserves the right to revise this publication and to make
changes to it from time to time without any obligation to notify any person or organization of such revision or
changes.
Copyright Notice:
This manual is copyrighted. All rights are reserved. This document may not, in whole or in part, be copied,
photocopied, reproduced, translated or reduced to any electronic medium or machine-readable form without prior
consent, in writing, from LXE Inc.
Copyright © 2006 by LXE Inc., An EMS Technologies Company, 125 Technology Parkway, Norcross, GA 30092
U.S.A. (770) 447-4224
Trademarks:
LXE® is a registered trademark of LXE Inc. Datalight® is a registered trademark of Datalight, Inc. Sockets® and
ROM-DOS
TM
are registered trademarks of Datalight, Inc. The original Datalight ROM-DOS User’s Guide and
Datalight Sockets Developer’s Guide are copyrighted by Datalight, Inc. Text explaining Sockets and ROM-DOS
commands in this manual has been amended by LXE Inc., for reprint purposes with Datalight Inc.’s express
permission. Wavelink® and Wavelink Avalanche® are registered trademarks of Wavelink Corporation, Kirkland,
WA. All other brand or product names are trademarks or registered trademarks of their respective companies or
organizations. When manual is in PDF format: “Acrobat ® Reader Copyright © 2006 Adobe Systems Incorporated.
All rights reserved. Adobe, the Adobe logo, Acrobat, and the Acrobat logo are trademarks of Adobe Systems
Incorporated.” Applies.
Note: The original equipment’s Reference Manual is copyrighted by PSC® Inc. This manual has been amended by
LXE® Inc., for the MX2 and Docking Stations with PSC’s express permission.
Revision Notice
(June 2006) Obsolete/Archived. Available on LXE ServicePass website only. Product’s
replacement device is the LXE MX7.
Updated document presentation to reflect LXE’s 2006 documentation standards. Updated
“Accessories”.
Entire Manual
Added section titled “Revision History”.
Changed all instances of “Integrated Scanner Programming Guide” to “Integrated Scanner
Programming Guide for DOS Devices”.
Changed all instances of “LXE Computers and Wavelink Avalanche User’s Guide” to
“Wavelink Avalanche for DOS Reference Guide”.
Page 3
Table of Contents
HAPTER 1 INTRODUCTION AND SPECIFICATIONS 1
C
Introduction ............................................................................................................... 1
Document Conventions............................................................................................
Technical Specifications .......................................................................................... 3
General......................................................................................................................................3
Physical.....................................................................................................................................4
Keypad....................................................................................................................... 5
38-key Keypad..........................................................................................................................
48-key Keypad..........................................................................................................................
Display ....................................................................................................................... 7
Cleaning the Display / Scan Aperture ..................................................................... 7
Memory ...................................................................................................................... 7
Battery........................................................................................................................ 8
Battery Maintenance Publication............................................................................. 8
Power Management .................................................................................................. 8
Standard Range Laser Scanner............................................................................... 9
Depth Of Field – All Scanners.................................................................................. 9
PC Card.................................................................................................................... 10
IR Communications Port ........................................................................................ 10
Docking Pads .......................................................................................................... 11
Radio PC Card......................................................................................................... 11
PCMCIA LXE 6400 2.4GHz Type II (Obsolete)...................................................................11
PCMCIA LXE 6500 2.4GHz Type II (Obsolete)...................................................................12
PCMCIA Cisco 2.4GHz Type II (Obsolete)...........................................................................12
PCMCIA Symbol 2Mb 2.4GHz Type II (Obsolete)...............................................................12
PCMCIA Symbol 11Mb 2.4 GHz Type II (Obsolete)............................................................13
Getting Help.............................................................................................................
Manuals and Accessories ......................................................................................
Manuals...................................................................................................................................14
Accessories .............................................................................................................................
Revision History.....................................................................................................................15
3
5
6
14
14
15
CHAPTER 2 USING ADVANCED FEATURES 17
Introduction ............................................................................................................. 17
Programming the Enter Keys (38-key Keypad) ....................................................
Key Combinations for International Characters (38-key Keypad) ......................
International Characters and LXE Terminal Emulations .......................................................
17
18
18
Resetting the MX2................................................................................................... 19
Warm Boot..............................................................................................................................
19
Cold Boot................................................................................................................................19
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 4
ii Table of Contents
Safe Boot ................................................................................................................................20
Hardware Reset.......................................................................................................................20
Using PC Cards....................................................................................................... 21
The IR Serial Port .................................................................................................... 21
Laser Scanner .........................................................................................................
Handle Installation (Optional) ................................................................................
22
23
Hand-Strap Installation........................................................................................... 24
The Disk Drives ....................................................................................................... 25
Additional Drives ...................................................................................................................25
Configuring the MX2............................................................................................... 26
Troubleshooting - Enable I 2 of 5...........................................................................................26
Transferring Files.................................................................................................... 26
Advanced Power Management .............................................................................. 27
Batteries..................................................................................................................................27
Doze Mode..............................................................................................................................27
Auto-Off Timer.......................................................................................................................27
Backlight.................................................................................................................................27
Power Management at the Radio Card...................................................................................28
Radio PC Card Configuration ................................................................................ 29
Introduction ............................................................................................................................29
NET.CFG Parameters.............................................................................................................30
Lucent Parameters................................................................................................................30
Link Support .................................................................................................................................. 30
Protocol.......................................................................................................................................... 30
WaveLAN_Network_Name........................................................................................................... 30
Station_Name................................................................................................................................. 30
AP_Distance ..................................................................................................................................30
Microwave_Robustness ................................................................................................................. 31
Transmit_Rate................................................................................................................................ 31
Medium_Reservation..................................................................................................................... 31
Card_Power_Management............................................................................................................. 31
Maximum_Sleep_Duration............................................................................................................ 32
Receive_All_Multicasts................................................................................................................. 32
Enable_Encryption......................................................................................................................... 32
Transmit_Key_ID .......................................................................................................................... 32
Proxim Parameters ...............................................................................................................33
Link Support .................................................................................................................................. 33
Protocol.......................................................................................................................................... 33
Int................................................................................................................................................... 33
Port................................................................................................................................................. 33
Mem#1 (ODI) ................................................................................................................................ 33
Domain........................................................................................................................................... 33
Station_type ................................................................................................................................... 33
Socket............................................................................................................................................. 33
Initialize_365 ................................................................................................................................. 34
Inactivity_min................................................................................................................................ 34
Inactivity_sec................................................................................................................................. 34
Channel .......................................................................................................................................... 34
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 5
Table of Contents iii
Subchannel..................................................................................................................................... 34
Mac_optimize ................................................................................................................................34
Roam_config.................................................................................................................................. 34
Peer_to_peer ..................................................................................................................................34
Cisco Parameters..................................................................................................................35
Link Support .................................................................................................................................. 35
Protocol.......................................................................................................................................... 35
SSID............................................................................................................................................... 35
FragThreshold................................................................................................................................ 35
RTSThreshold................................................................................................................................ 35
DataRateX...................................................................................................................................... 35
RefreshInterval............................................................................................................................... 35
PowerSaveMode ............................................................................................................................ 36
MaxPowerSave .............................................................................................................................. 36
NodeName ..................................................................................................................................... 36
WEP enable.................................................................................................................................... 36
Diversity......................................................................................................................................... 36
PortBase – IRQ – Memory - Socket .............................................................................................. 36
BusType......................................................................................................................................... 36
Frame ............................................................................................................................................. 36
Cisco 350 Radio Only.................................................................................................................... 37
LEAP..........................................................................................................................................................37
WorldMode ................................................................................................................................................37
ShortPreamble ............................................................................................................................................37
AWCLEAP .................................................................................................................................... 37
WEPDOS....................................................................................................................................... 38
Symbol Parameters...............................................................................................................39
Link Support .................................................................................................................................. 39
Protocol.......................................................................................................................................... 39
ESS_ID ..........................................................................................................................................39
mode............................................................................................................................................... 39
ioaddress ........................................................................................................................................39
memory .......................................................................................................................................... 39
interrupt.......................................................................................................................................... 39
performance_index ........................................................................................................................39
Auth_type....................................................................................................................................... 39
Encrypt_Key# ................................................................................................................................ 40
encrypt_enable............................................................................................................................... 40
Encrypt_Key_ID............................................................................................................................ 40
Encrypt_Enable_Index................................................................................................................... 40
diversity .........................................................................................................................................40
Tx_rate........................................................................................................................................... 40
SOCKETS TCP/IP Stack........................................................................................................41
Introduction ..........................................................................................................................41
Bootp.............................................................................................................................................. 41
DHCP............................................................................................................................................. 41
Setting SOCKETS.CFG Parameters ....................................................................................
Set IP Address................................................................................................................................ 42
Set ARP INIT................................................................................................................................. 42
Set Interface ................................................................................................................................... 42
42
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 6
iv Table of Contents
Set Router IP (Gateway only)........................................................................................................ 43
Set Domain Name Server............................................................................................................... 43
Display IP Address ........................................................................................................................43
Options........................................................................................................................................... 43
SOCKET.CFG Parameters...................................................................................................44
domain ...........................................................................................................................................44
iface................................................................................................................................................ 44
interface ......................................................................................................................................... 44
ip .................................................................................................................................................... 47
param .............................................................................................................................................48
route ............................................................................................................................................... 49
tcp................................................................................................................................................... 51
RF Throughput, Performance and Troubleshooting............................................
55
Power Management at the Proxim RangeLAN2 Access Point ..............................................55
MU Access Control..............................................................................................................
Message Filtering .................................................................................................................
55
55
Site Survey..............................................................................................................................56
Throughput and Performance .................................................................................................56
Operational Problems .............................................................................................................57
Problems with DOS Drivers ...................................................................................................58
CHAPTER 3 SOFTWARE CONFIGURATION 59
Introduction ............................................................................................................. 59
BIOS and DOS .......................................................................................................................59
DOS Key Functions Not Supported on the MX2.................................................................59
PC Card and RF Networking Software ..................................................................................59
Disk Drives and Files.............................................................................................. 60
Drive A ...................................................................................................................................60
Drive B....................................................................................................................................62
Drive C....................................................................................................................................64
Root Directory Files.............................................................................................................
64
DOS Directory Files.............................................................................................................64
PCM Directory Files ............................................................................................................65
Agent Directory Files...........................................................................................................65
Terminal Emulation Files.....................................................................................................
TE Selection Menu...............................................................................................................
Menu Customization...................................................................................................................... 66
Drive D ...................................................................................................................................
Drive E....................................................................................................................................
65
66
66
66
System Configurations........................................................................................... 67
Default Configuration.............................................................................................................67
I/O PC Card Support Configuration .......................................................................................68
Data Entry................................................................................................................ 69
Keyboard Data Entry ..............................................................................................................
69
Barcode Data Entry.................................................................................................................69
Infrared Port Data Entry .........................................................................................................
69
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 7
Table of Contents v
Terminal Emulation................................................................................................................69
ANSI Plus.............................................................................................................................70
TN3270 TE and TN5250 TE................................................................................................70
DOS TE User Defined Stored Forms...................................................................................70
DOS TE Font Sizes ..............................................................................................................70
Sample NET.CFG and SOCKET.CFG Files............................................................ 71
Sample NET.CFG Files..........................................................................................................71
Lucent Radio NET.CFG File ...............................................................................................71
Proxim Radio NET.CFG File...............................................................................................71
Cisco Radio NET.CFG File .................................................................................................72
Symbol 2Mb Radio NET.CFG File......................................................................................73
Symbol 11Mb Radio NET.CFG File....................................................................................74
Sample SOCKET.CFG File....................................................................................................76
SNMP DOS Agent....................................................................................................
Avalanche ................................................................................................................
77
78
Minimum Software Baseline..................................................................................................78
Upgrading the MX2................................................................................................................78
Directory Structure .................................................................................................................78
\AGENT ...............................................................................................................................79
\AVA ....................................................................................................................................79
\APPS ...................................................................................................................................79
CHAPTER 4 COMMANDS 81
Introduction ............................................................................................................. 81
ROM-DOS Commands ............................................................................................ 81
ANSI.SYS...............................................................................................................................81
ATTRIB.EXE .........................................................................................................................82
CHKDSK.EXE .......................................................................................................................83
COMMAND.COM.................................................................................................................84
DELTREE.EXE......................................................................................................................85
FORMAT.COM......................................................................................................................
86
HIMEM.SYS ..........................................................................................................................87
MEM.EXE..............................................................................................................................
MODE.COM ..........................................................................................................................
89
90
MORE.COM...........................................................................................................................91
NED.EXE and NED.CFG.......................................................................................................
NED Default Hot Keys ........................................................................................................
92
93
PRINT.COM...........................................................................................................................94
REMDISK.EXE......................................................................................................................
95
REMSERV.EXE.....................................................................................................................96
SYS.COM...............................................................................................................................98
VER ........................................................................................................................................
XCOPY.COM.........................................................................................................................
99
99
ROM-DOS 6.22 Command Summary................................................................... 101
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 8
vi Table of Contents
CHAPTER 5 THE DOCKING STATION 105
Introduction ........................................................................................................... 105
The Single Dock .................................................................................................... 105
Attaching the Single Dock to a Computer............................................................................
The Power Adapter...............................................................................................................
106
106
Using a Single Dock .............................................................................................................107
Charging Batteries..............................................................................................................107
Transferring Files ...............................................................................................................107
Technical Specifications.......................................................................................................
Single Dock........................................................................................................................
108
108
Power Supply .....................................................................................................................108
APPENDIX A CONNECTOR CONFIGURATIONS 109
Introduction ........................................................................................................... 109
The MX2 Computer ............................................................................................... 109
Serial IR Port ........................................................................................................................109
Single Dock ........................................................................................................... 110
25-Pin Connector..................................................................................................................110
APPENDIX B KEY MAPS 111
Keypads................................................................................................................. 111
38-key Keypad......................................................................................................................111
Key Map 101-Key Equivalencies for Batch Units.............................................................111
48-key Keypad......................................................................................................................117
Key Map 101-Key Equivalencies for Batch Units.............................................................117
IBM TN5250 Terminal Emulator Keypad.........................................................................123
NDEX 125
I
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 9
Table of Contents vii
Illustrations
Figure 1-1 The MX2 Hand Held Computer, Rear Views....................................................................................1
Figure 1-2 The MX2 Hand Held Computer, Front Views...................................................................................2
Figure 1-3 The MX2 Hand Held Computer.........................................................................................................4
Figure 1-4 MX2 38-key Keypad..........................................................................................................................5
Figure 1-5 MX2 48-key Keypad..........................................................................................................................6
Figure 1-6 MX2 Display......................................................................................................................................7
Figure 1-7 Battery Pack .......................................................................................................................................8
Figure 1-8 Laser Scanner Location at Top of Unit ..............................................................................................9
Figure 1-9 PCMCIA Card..................................................................................................................................10
Figure 1-10 IR Port Location on Bottom of Unit...............................................................................................10
Figure 1-11 Docking Pad Location on Bottom of Unit .....................................................................................11
Figure 2-1 Location of the Enter Keys...............................................................................................................17
Figure 2-2 Program Trigger Icons .....................................................................................................................17
Figure 2-3 Location of the Hardware Reset Mechanism ...................................................................................20
Figure 2-4 The IR Port on Bottom of Unit.........................................................................................................21
Figure 2-5 Scanner Aperture Location ..............................................................................................................22
Figure 2-6 Scan Button and Scan Trigger.........................................................................................................22
Figure 2-7 Insert Pistol Grip ..............................................................................................................................23
Figure 2-8 Hand Strap Assembly.......................................................................................................................24
Figure 3-1 CONFIG.SYS File on Drive A ........................................................................................................60
Figure 3-2 AUTOEXEC.BAT File on Drive A .................................................................................................61
Figure 3-3 CONFIG.SAF File on Drive A ........................................................................................................61
Figure 3-4 CONFIG.SYS File on Drive B.........................................................................................................63
Figure 3-5 AUTOEXEC.BAT File on Drive B .................................................................................................63
Figure 3-6 CONFIG.SAF File on Drive B.........................................................................................................63
Figure 3-7 CONFIG.SYS File on Drive C for Default Configuration...............................................................67
Figure 3-8 AUTOEXEC.BAT File on Drive C for Default Configuration .......................................................67
Figure 3-9 CONFIG.SYS File on Drive C for I/O PC Card Support ................................................................68
Figure 3-10 AUTOEXEC.BAT File on Drive C for I/O Card Support.............................................................68
Figure 5-1 Charging/Communication Dock for One MX2..............................................................................105
Figure 5-2 Back Panel of the Single Dock.......................................................................................................106
Figure 5-3 US Dock Power Adapter................................................................................................................106
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 10
viii Table of Contents
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 11
Introduction
Chapter 1 Introduction and Specifications
This reference guide is a technical supplement to the “MX2 User’s Guide”. It contains technical
information about the MX2’s system configuration, disk drives, utilities, and DOS commands.
Included in the appendices are connector configurations for the MX2 and the Single Dock and key
maps for the MX2 keypads.
For configuration parameters and barcodes for setting those parameters, please refer to the
“Integrated Scanner Programming Guide for DOS Devices”, available on the LXE Manuals CDROM and the LXE ServicePass website. This manual is provided as a reference guide for system
administrators, developers, and programmers who want to create end-user solutions for MX2
DOS portable computers. It is not intended for use by first-time MX2 users.
There are two types of MX2 devices available. Both use hand-straps.
No Pistol Grip Accessory (38-key keypad)
Figure 1-1 The MX2 Hand Held Computer, Rear Views
Note: Either the Pistol Grip or the Hand-strap are factory installed. Both cannot be connected
to the same unit at the same time. The Pistol Grip handle is standard with the 48-key
keypad.
Note: Always store unused devices with a fully charged main battery pack installed. LXE
recommends an in-use mobile device be frequently connected to an external power
source to retain optimum power levels in the main battery pack and the backup battery.
When the backup battery and main battery pack are dead, the mobile device reverts to
it’s default values when a fully charged main battery pack is installed and the device is
powered On again.
Pistol Grip Accessory (Standard with 48-
key keypad, Optional with 38-key keypad)
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 12
2 Introduction
In addition, the MX2 with Pistol Grip Accessory is available with either a 38-key or 48-key
keypad. The MX2 without the Pistol Grip Accessory only uses the 38-key keypad. The 48-key
keypad version is also available with a TN5250 overlay.
38-key keypad 48-key keypad
Figure 1-2 The MX2 Hand Held Computer, Front Views
Note: All keypads are installed and configured by LXE.
LXE offers two basic configurations:
• RF Configuration – a MX2 with a PCMCIA radio and antenna. The unit may be
configured with or without an integrated laser scanner.
• Batch Configuration – a MX2 without a PCMCIA radio and antenna. The unit may
be configured with or without an integrated laser scanner.
Both configurations can use the Single Dock without requiring adjustment.
MX2’s running LXE’s Terminal Emulation programs require a PCMCIA radio, antenna and RF
configuration files.
Note: Both configurations are available with either type of MX2.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 13
Document Conventions 3
Document Conventions
This reference guide uses the following document conventions:
ALL CAPS All caps are used to represent disk directories, file names, and application
names.
Menu|Choice Rather than use the phrase “choose the Save command from the File menu”,
this manual uses the convention “choose File|Save”.
“Quotes” Indicates the title of a book, chapter or a section within a chapter (for
example, “Document Conventions”).
< > Indicates a key on the keyboard (for example, <Enter> ).
Indicates a reference to other documentation.
ATTENTION
Differences in operation or commands due to radio type.
Keyword that indicates vital or pivotal information to follow.
!
Note:
CAUTION
WARNING
!
DANGER
!
Technical Specifications
General
CPU AMD Am486 33Mhz
Operating Temperature -10C° to 50C° (14°F to 122°F)
Storage Temperature -20°C to 70°C (-4°F to 158°F)
Sealing IP54 (dust and splashing water)
Humidity 0 to 95% non-condensing
Drop 4 foot multiples
Usage Indoors, Limited outdoors
Attention symbol that indicates vital or pivotal information to follow. Also,
when marked on product, means to refer to the manual or operator’s guide.
International fuse replacement symbol. When marked on the product, the
label includes fuse ratings in volts (v) and amperes (a) for the product.
Keyword that indicates immediately relevant information.
Keyword that indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury.
Keyword that indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
Keyword that indicates an imminent hazardous situation which, if not
avoided, will result in death or serious injury.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 14
4 Technical Specifications
Physical
Front Rear
38 key-keypad 48-key keypad 38-key keypad
Figure 1-3 The MX2 Hand Held Computer
Height 7.98 in (198 mm)
Width 3.4 in (86 mm)
Depth 1.4in (36 mm)
Weight (with battery) No radio, no laser 11.5 oz. (325 grams)
without handle
No radio, with laser 11.7 oz (330 grams)
Radio, no laser 12.7 oz (360 grams)
Radio, laser 12.9 oz (365 grams)
48-key keypad and 38-
key keypad with handle
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 15
Keypad 5
Keypad
38-key Keypad
Figure 1-4 MX2 38-key Keypad
Type Rubber Membrane
Keys 38-key (alphanumeric)
Function Keys 5 dedicated - FN, CTL, ALT, 2 special
Shift Keys 5 Shifted Function Keys
Shared Numeric No
Arrow Keys 4, implemented on numeric keys
Key colors 5
Character Western-European character support
Emulation LXE ANSI Plus, TN3270, TN5250
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 16
6 Keypad
48-key Keypad
Figure 1-5 MX2 48-key Keypad
Type Rubber Membrane
Keys 48-key (alphanumeric)
Function Keys 10 Function keys (Fn plus numeric key)
Shared Numeric No
Arrow Keys 4, implemented on alpha keys
Key colors 3
Character Western-European character support
Emulation LXE ANSI Plus, TN3270, TN5250
Note: The 48-key keypad is also available with a TN5250 overlay.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 17
Display 7
Display
Figure 1-6 MX2 Display
Type Supertwist graphics LCD
Writable Area Approximately 2.2” x 1.75” (5.6 cm x 4.4 cm) plus icon area
Char 16 line by 20 character
8 line by 20 character
System Status Dedicated icons (8)
Graphics 128 x 160
Prog. Interface BIOS/Memory Map
Lighting Backlight with programmable timeout
Contrast Adjustment Keyboard adjustable
Cleaning the Display / Scan Aperture
Keep fingers and rough or sharp objects away from the scan aperture and display. If the glass
becomes soiled or smudged, clean only with a standard household cleaner such as Windex(R)
without vinegar or use Isopropyl Alcohol. Do not use paper towels or harsh-chemical-based
cleaning fluids since they may result in damage to the glass surface. Use a clean, damp, lint-free
cloth. Do not scrub optical surfaces. If possible, clean only those areas which are soiled.
Lint/particulates can be removed with clean, filtered canned air.
Memory
RAM
Mapping Contiguous from 0000
Upgradeability Factory upgrade
8 Mbytes
Flash
Mapping Combined DOS and BIOS
2 Mbytes, 3.3V (default: 2M)
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 18
8 Battery
Battery
Figure 1-7 Battery Pack
Main - Rechargeable
Technology Nickel Metal Hydride (NiMH) Battery Pack
Configuration 3 x AA
Capacity 1250 mAh
Protection Polyswitch PTC and Klixon circuit breaker
Life, Operating > 8 hrs. batch;
> 6 hrs with RF link
Life, Storage > 14 days data retention, with fully charged pack
Charging In 1 Slot dock: =< 3 hrs.
Backup - Rechargeable
Type Rechargeable Lithium (Li)
Data Retention Period > 1 hour
Recovery from Cutoff 1M min, 5M typical after 5M operation
Battery Maintenance Publication
The LXE publication “Getting the Most from Your Batteries” is available on the LXE Manuals
CD-ROM and is a single-source guide to battery management. The document contains
information about battery recharging, conditioning, and other pertinent issues.
Power Management
Automatic Shutdown Unit turns off when battery door is removed.
Shutdown Timer Yes
Low Battery Indication Yes
APM Compatible Yes
Turn on to Previous State Yes
Batteries required for Operation Yes
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 19
Standard Range Laser Scanner 9
Standard Range Laser Scanner
Figure 1-8 Laser Scanner Location at Top of Unit
Location At top of unit, built into unit
Aperture Height 0.65” (1.65 cm)
Aperture Width 1.06” (2.69 cm)
Depth Of Field – All Scanners
Note: The following values are dependent upon barcode printing resolution, contrast and
ambient light.
Label Density Standard Range Long Range Advanced Long Range
5 mil
7.5 mil
10 mil
13 mil -- --
15 mil
20 mil
30 mil -- --
40 mil
55 mil
70 mil Reflective
100 mil Reflective
3.0” – 5.0”
8.0 – 13.0 cm
2.5” – 9.0”
6.0 – 23.0 cm
2.5” – 13.0”
6.0 – 33.0 cm
2.5” – 19.0”
6.0 – 48.0 cm
1
2.5” – 21.0”
6.0 – 53.0 cm
1
2.5” – 30.0”
6.0 – 76.0 cm
1
2.5” – 36.0”
6.0 – 91.0 cm
-- --
-- --
9.0” – 22.0”
23.0 – 56.0 cm
7.0” – 38.0”
18.0 – 96.0 cm
7.0” – 45.0”
18.0 – 114.0 cm
10.0” – 90.0”
25.0 – 229.0 cm
10.0” – 100.0”
25.0 – 250.0 cm
60.0” – 180.0”
152.0 – 457.0 cm
62.0” – 240.0”
157.0 – 610.0 cm
--
19.9” – 29.0”
48.0 – 74.0 cm
20.0” – 50.0”
51.0 – 127.0 cm
--
33.0” – 98.0”
84.0 – 249.0 cm
--
27.0” – 115.0”
69.0 – 292.0 cm
114.0” – 250.0”
290.0 – 635.0 cm
125.0” – 360.0”
318.0 – 914.0 cm
1
Minimum distance determined by symbol length and scan angle.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 20
10 PC Card
PC Card
Figure 1-9 PCMCIA Card
Note: The PCMCIA card must be installed by authorized personnel.
Physical One only Type 2 with custom ejector. Sealed inside unit.
Location Bottom of unit
Connections Per PCMCIA specifications
RF Usage Internally mounted antenna
Memory usage ATA Flash
Modem usage Not supported. (Cable exits card end)
Power Management Not supported
Vpp 5V only
IR Communications Port
Physical .65” wide x .25” high (1.65 cm x .63 cm)
Location Bottom of unit
Interface Modified RS-232
Figure 1-10 IR Port Location on Bottom of Unit
Dock Usage Pad on bottom of unit for RS-232 input (RXD) while in dock.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 21
Docking Pads 11
Docking Pads
Left Middle Right
RXD Neg Pos
Figure 1-11 Docking Pad Location on Bottom of Unit
Physical Total width of three pads 1” (2.54 cm)
Width of individual pad .06” (.15 cm)
Location Bottom of unit
Dock Usage With MX2 in the dock, keypad facing front of dock:
Right-most pad: positive lead used for recharging batteries.
Middle pad: negative lead used for recharging batteries.
Left-most pad: RS-232 input (RXD) into MX2 while in dock.
Radio PC Card
Note: Radio PCMCIA cards must be installed / removed by authorized personnel.
PCMCIA LXE 6400 2.4GHz Type II (Obsolete)
Bus Interface PCMCIA 2.0, Type II
Radio Frequencies 2.4 - 2.4835 GHz FHSS
RF Data Rates 1.6 Mbps
RF Power Level 100 mW
Channels 15
Connectivity Novell, TCP/IP, Ethernet, NDIS, ODI
Operating Temperature 60° C (140° F)
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 22
12 Radio PC Card
PCMCIA LXE 6500 2.4GHz Type II (Obsolete)
Bus Interface PCMCIA 2.0, Type II
Radio Frequencies 2.4 - 2.4835 GHz IEEE
MAP 802.11 DS SS
Range 1400 ft dependant on speed and environment
RF Data Rates 11 Mbps
RF Power Level 35 mW nominal
Channels 11 US, 13 Europe, 4 France, 1 Japan
Connectivity Novell, TCP/IP, Ethernet, ODI
Supply Current w/o Encryption Doze Max 9mA, Receive Max 240mA, Transmit
Max 300mA (with encryption, add 10mA)
Output Power 15 dBm (nominal)
Operating Temperature 0°C to 55°C (32°F to 131°F)
Security RC4 IEEE 802.11 compliant encryption
PCMCIA Cisco 2.4GHz Type II (Obsolete)
Bus Interface PCMCIA 2.0, Type II
Radio Frequencies 2.4 - 2.4835 GHz FHSS
RF Data Rates 11 Mbps maximum
RF Power Level 35 mW nominal
Channels 11 US, 13 Europe, 4 France, 1 Japan
Connectivity Novell, TCP/IP, Ethernet, NDIS, ODI
Operating Temperature 0°C to 55°C (32°F to 131°F)
PCMCIA Symbol 2Mb 2.4GHz Type II (Obsolete)
Bus Interface PCMCIA 2.0, Type II slot
Radio Frequencies 2.4 - 2.5 GHz FHSS
RF Data Rates 2 Mbps maximum
RF Power Level 100 mW
Channels 15
Operating Temperature see MX2 Environmental Specifications
Storage Temperature see MX2 Environmental Specifications
Connectivity Novell, TCP/IP, Ethernet, NDIS, ODI
Antenna Internal
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 23
Radio PC Card 13
PCMCIA Symbol 11Mb 2.4 GHz Type II (Obsolete)
Bus Interface PCMCIA 2.0, Type II slot
Radio Frequencies 2.4 - 2.5 GHz IEEE 802.11b DS SS
RF Data Rates 11 Mbps maximum
RF Power Level 100 mW
Channels 11 US, 13 Europe, 4 France, 1 Japan
Operating Temperature see MX2 Environmental Specifications
Storage Temperature see MX2 Environmental Specifications
Connectivity: Novell, TCP/IP, Ethernet, ODI
Antenna Internal
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 24
14 Getting Help
Getting Help
LXE user guides are now available on CD and they can also be viewed/downloaded from the LXE
ServicePass website. Contact your LXE representative to obtain the LXE Manuals CD or access
to the LXE ServicePass website. You can also check the LXE ServicePass website for the latest
manual releases.
Note: Obsolete/archived manuals are not available on the LXE Manuals CD. They are
available for download from the ServicePass website only.
You can get help from LXE by calling the telephone numbers listed on the LXE Manuals CD, in
the file titled “Contacting LXE.” This information is also available on the LXE website.
Explanations of terms and acronyms used in this manual are located in the file titled “LXE
Technical Glossary” on the LXE Manuals CD and on the LXE website.
Manuals and Accessories
Manuals
The following manuals are available on the LXE Manuals CD and the LXE ServicePass website:
User Guides (for the daily user)
• MX2 User’s Guide – English (Obsolete)
• MX2 User’s Guide – German (Obsolete)
Reference Guides (for the SysAdmin)
• ANSI Plus Reference Guide
• DOS API Programming Guide
• Integrated Scanner Programming Guide for DOS Devices
• MX2 Reference Guide (Obsolete)
• TN3270 Terminal Emulation Reference Guide
• TN5250 Terminal Emulation Reference Guide
Networking
• WaveLink Avalanche for DOS Reference Guide
• SNMP Agent Reference Guide
• Telnet Manager Reference Guide
Peripherals
• Getting the Most out of Your Batteries
• MX2 Docking Station User’s Guide
• PCMCIA Card Management and LXE DOS Computers
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 25
Manuals and Accessories 15
Accessories
Battery, 1650 mAh, NiMH, MX2 2325A376BATTNMH850
Battery Charger, 120V Single-slot 2325A377CHGR1US
Battery Charger, 230V Single w/Euro connector 2325A378CHGR1EU
Battery Charger, 230V Single w/IEC 320 connector 2325A379CHGR1IEC
Battery Charger, 120V Four-slot w/pwr supply US MX2A380CHGR4US
Battery Charger, 230V Four-slot w/pwr supply Euro MX2A381CHGR4EU
MX2 Softcase, Clear Protective Cover (keyboard and display) MX2A401CASE
MX2 Soft Case, Open Front (does not include clear plastic cover) MX2A403CASE
MX2 Holster MX2A402HOLSTER
Softcase, MX2 With Handle, Clear protective cover MX2WHA401CASE
Holster, MX2 With Handle MX2WHA402HOLSTER
MX2 Nylon Hand Strap Kit (cannot be used with MX2 w/handle) 990010-0004
Dock, Single Slot * MX2A001DOCKSINGLE
Dock, Single, Power Supply (120V), External AC, US * 2325A301PSDOCK120
Dock, Single, Power Supply (230V), External AC, Int’l * 2325A302PSDOCK230
Dock Serial Cable (9 Pin and 25 Pin) [dock to PC or dock to printer] 2325A052CBLDOCK925
* Requires Dock Power Supply for each dock.
Revision History
Revision K – September 2005
Entire Manual : Updated document presentation to reflect LXE’s 2005 documentation standards. Added new LXE logo. Noted
obsolescense of Symbol FHSS radios where applicable. Added updated “Getting Help” and “Manuals.” Updated “Accessories”
to 2005 availability.
Revision J – August 2004
Entire Manual : Updated document naming conventions.
Chapter 1 Introduction and Specifications : Updated “Accessories” to July 2004 availability.
Chapter 3 Software Configuration : Added section titled “Avalanche”.
Revision H – May 2004
Chapter 1 – Introduction and Specifications : Added technical specifications for Symbol 2MB FHSS radio. Updated the
Accessories section.
Chapter 3 – Software Configuration : Added Symbol 2MB FHSS Radio NET.CFG. Removed “WEP – Prior to November 2003”
section from “Symbol 11 Mb Radio NET.CFG File” sample.
Revision G – December 2003
Chapter 2 – Using Advanced Features : Revised Symbol Radio Encryption information. Revised pertinent sections relating to the
updated DOS Stack Release in November 2003.
Chapter 3 – Software Configuration : Updated screen/font support in “DOS TE Font Sizes” section.
Chapter 4 – Commands : Updated international keyboards and code pages footnote.
Revision F – May 2003
Entire Manual : Replaced references to the XFER file transfer utility with REMDISK/REMSERV utilities. Replaced references
to configuration barcodes with a reference to “Integrated Scanner Programming Guide”, E-SW-SCANNERPG.
Chapter 1 – Introduction : Updated “Introduction”, “48-key Keypad” and “Manuals” sections. Added “Battery Maintenance” and
“PCMCIA Symbol 11Mb 2.4 GHz Type II” Sections.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 26
16 Manuals and Accessories
Chapter 2 – Using Advanced Features : Revised “Set Interface” and “Options” sections. Added “Symbol Parameters” and “Set
ARP INIT” sections.
Chapter 3 – Software Configuration : Added sample Symbol 11Mb NET.CFG file. Revised sample SOCKET.CFG file.
Chapter 4 – Using XFER : Deleted chapter. File transfer is handled by REMDISK and REMSERV, covered in the “Commands”
chapter.
Chapter 5 – Commands : Renamed as Chapter 4 – Commands.
Chapter 6 – The Docking Station : Renamed as Chapter 5 – The Docking Station.
Appendix B – Programming Parameters : Deleted Appendix. This information is included in “Integrated Scanner Programming
Guide”, E-SW-SCANNERPG.
Appendix C – Barcodes for Configuring MX2 : Deleted Appendix. This information is included in “Integrated Scanner
Programming Guide”, E-SW-SCANNERPG.
Appendix D – Key Maps : Renamed as Appendix B – Key Maps. Revised “38-key Keypad”, “Key Map 101-Key Equivalencies
for Batch Units” section for Shift, Left Shift and Right Shift keypresses. Added “IBM TN5250 Terminal Emulator Keypad”
section. Added footnotes to 48-key keypress table for left/right shift and CapsLock.
Revision E – December 2002
Chapter 1 – Introduction : Add 38-key and 48-key keypad information to Introduction. Update figure accordingly. Split Keypad
section into 38-key Keypad and 48-key Keypad sections. Add “Cleaning the Display” section. Add Cisco to “Radio PC Card”
section.
Chapter 2 – Using Advanced Features : Rename section Programming the Enter Keys to Programming the Enter Keys (38-key
Keypad). Update Scan Button Location figure to include 38-key and 48-key keypads.
Update radio parameters:
Lucent: Rename Microwave_Oven_Robustness as Microwave_Robustness.
Delete PortType. Revise Card_Power_Management, AP_Distance, Receive_All_Multicasts.
Proxim: Delete Master_Name
Cisco: Revise Diversity, PowerSaveMode, MaxPowerSave, PortBase-IRQ-Memory-Socket.
Chapter 3 – Software Configuration : Update Sample NET.CFG and SOCKET.CFG Files section to include radio parameter
changes incorporated in Chapter 2. Add “Agent Directory Files”, “Terminal Emulation Files” and “SNMP DOS Agent” sections.
Chapter 4 – The Configuration Utility : Delete chapter.
Chapter 5 – Using XFER : Rename as Chapter 4 – Using XFER.
Chapter 6 – Commands : Rename as Chapter 5 – Commands. Update ROM-DOS Command Summary for different DOS load on
certain MX’2s.
Chapter 7 – The Docking Station : Rename as Chapter 6 – The Docking Station.
Appendix D – Key Maps : Existing keymap is moved into 38-key Keypad section. Add 48-key Keypad section.
Revision C – June 2001
Chapter 1 – Introduction : Technical Specifications. Change title "Standard Range Laser Scanner" to "Laser Scanner". Add
Depth of Field Chart for Scanner Ranges (Standard, Long and Advanced Long Range Scanners). Manuals and Accessories
Section -- Remove "TN6600 System Administrator’s Guide" and "User’s Guide : OnNet Kernel for Windows 2.0 and PC/TCP
Network Software Kernel for DOS 4.0" from Manual listing. Add protective case for MX2 with pistol grip to list of Accessories.
Chapter 2 – Using Advanced Features : Add graphic showing difference between pistol grip back view and non-pistol grip back
view. Add Section for installing optional handle. Add Section for replacing pistol grip with a handstrap.
Revision B – May 2001
Regulatory Notices : Add Datalight, Inc. and Adobe Acrobat copyright information. Revise structure of Regulatory Notices
section: place legal/safety regulatory information in Operator's Guides only.
Chapter 1 – Introduction : Remove TN6600 System Administrator’s Guide and User’s Guide : OnNet Kernel for Windows 2.0
and PC/TCP Network Software Kernel for DOS 4.0 from manual listing.
Chapter 2 – Using Advanced Features : Replace “Radio PC Card Configuration” with updated version containing Sockets
TCP/IP stack information, NET.CFG and SOCKETS.CFG data. Delete “NDIS driver does not install or does not work” from
“Problems with DOS Drivers”.
Chapter 3 – Software Configuration : Add section for “DOS Key Functions Not Supported on the MX2”. Add sections for
“Terminal Emulation Screen Sizes” and “DOS Terminal Emulation User Defined Stored Forms”. Add section for “Sample
NET.CFG and SOCKET.CFG Files”.
Chapter 6 – Commands : Replace chapter contents.
Appendix D – Key Maps : Remove PrintScrn and SysReq from “Key Map 101-Key Equivalencies for Batch Units”.
Revision A – October 2000 : Initial Release
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 27
Chapter 2 Using Advanced Features
Introduction
This chapter provides information about advanced features of the MX2 computers. It does not
cover basics, such as use of the keypad and display. For basic information about the MX2, see the
“MX2 User’s Guide”.
Programming the Enter Keys (38-key Keypad)
Figure 2-1 Location of the Enter Keys
The MX2 with a 38-key Keypad allows reprogramming of one of the Enter keys. One Enter key
may be reprogrammed from a list of available keys. There is no option for swapping the function
of the Enter keys. However, if one key is reprogrammed, the other key automatically becomes the
Enter key. This feature is not available with the 48-key Keypad.
To program an Enter key
First, hold down the [ALT] key then the [FN] key and press the desired [Enter] key to reprogram.
The program-trigger icon should appear on the right in the display, indicating which Enter key is
to be reprogrammed.
Left Enter Key Right Enter Key
Figure 2-2 Program Trigger Icons
Select the key sequence to reprogram the Enter key. The following keys are valid selections:
• Caps
• Intl
• Backspace
• Tab
• Enter
Note: All of these functions, with the exception of the Enter key, are the Fn shifted state of
another key. When selecting the key, you do not need to enter Fn mode first.
For example, to assign the left Enter key to Caps, press [ALT] then [Fn], then left [Enter], then
[Ctrl]. The MX2 automatically translates the Ctrl keypress into the Caps key.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 28
18 Key Combinations for International Characters (38-key Keypad)
Key Combinations for International Characters (38-key Keypad)
International
Characters
á, é, í, ó, ú, É ‘(apostrophe) a, e, i, o, u, E
ç or Ç ‘(apostrophe) c or C
à, è, ì, ò, ù ` a, e, i, o, u
â, ê, î, ô, û ^ a, e, i, o, u
ä, ë, ï, ö, ü, ÿ, Ä, Ö, Ü : a, e, I, o, u, y, A, O, U
å, Å @ None
ñ or Ñ ~ m, n, M, or N
ß s s
æ, Æ ! e or E
¿ ? None
¡ ! !
¢, £, ¥ $ c, k, l, y
Enter international characters by using the following key sequence:
Fn-Alt
where
Fn-Alt is the key sequence to initiate the Intl key function,
accent letter
Accent or
Letter
Letter
accent is a character from the “Accent or Letter” column, and
letter is a character from the “Letter” column in the same row.
After the international icon appears on the screen, the next key pressed displays an international
character and the keypad reverts to normal mode.
International Characters and LXE Terminal Emulations
The international characters shown above are supported in DOS mode only.
LXE’s terminal emulation applications (ANSI Plus, TN3270/-E and TN5250) do not support
these particular international characters. Use the terminal emulation application configuration
utilities to create international characters for use when running terminal emulation applications on
the MX2.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 29
Resetting the MX2 19
Resetting the MX2
One of the critical features of any portable data-collection device is its ability to protect against
accidental data loss. In the event a MX2 becomes “locked up” or otherwise in a state in which
data can no longer be processed, you can use any of four methods to reset the unit. This chapter
describes these methods.
Warm Boot
The warm boot is one of two software methods for resetting a MX2. It is analogous to the CTLALT-DEL key sequence for rebooting IBM-compatible PCs, and the same key sequence is used
to force a warm boot on a MX2. This method of resetting a unit should be used first to attempt to
bring it back to a usable state.
Note: You do not need to press the FN key to activate the DEL function of the BkSp key.
Since a warm boot can be attempted only from a unit that has been turned on, certain assumptions
are made. For example, the rigorous hardware tests that are performed as part of the cold boot
sequence are not all necessary. This means the unit restarts faster with a warm boot than with a
cold boot.
During a warm boot, data written to the RAM drive (D), the flash drive (C), or an ATA flash card
will remain intact. However, if an application is running on a unit before a warm boot, its state
cannot be restored.
Cold Boot
Note: If you do not want end users to be able to reset the unit, scan the “Enable CTL-ALT-DEL
Reboot Off” barcode in the “Integrated Scanner Programming Guide for DOS Devices”,
available on the LXE Manuals CD-ROM.
The second software method for resetting a MX2 is the cold boot. A cold boot should be used
only if a warm boot is unsuccessful. Performing a cold boot is analogous to pressing the reset
button on a PC or to turning the PC’s power off and then back on.
To perform a cold boot on a MX2, first turn it off. Then press [ALT] + [FN] + [Power], holding
the first two keys down while pressing the third.
Release all three keys simultaneously, and the unit will reset.
Simply removing and inserting the battery pack will not force a cold boot, because the backup
battery can provide minimal power to sustain the MX2’s operating state. The exception to this is
when the backup battery is drained of all power, a condition that you should not let happen.
When a cold boot is performed, all transient data is lost, along with the state of any application
that was running on the unit. Data written to the RAM drive (D), the flash drive (C), or an ATA
flash card will remain intact. If a cold boot happens because of a dead backup battery, data written
to a RAM drive may not be maintained.
A cold boot begins with a retesting of the hardware and then follows with the DOS boot sequence.
The unit reboots DOS under the same conditions you would expect from a desktop PC: Device
drivers included in the CONFIG.SYS file and applications included in the AUTOEXEC.BAT file
are automatically loaded as part of the boot process; any other programs that were loaded before
the cold boot will not be reloaded automatically.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 30
20 Resetting the MX2
Safe Boot
During the DOS boot sequence, control is passed sequentially to the CONFIG.SYS files on drives
A, B, and C. A similar process is followed for the AUTOEXEC.BAT files on each drive.
It is possible for a driver or application loading from the CONFIG.SYS or AUTOEXEC.BAT file
on drive C to hang the system. A cold or warm boot of the unit will not directly correct the
problem, because the troublesome program will be started again as part of the boot sequence.
What is required is a method by which the CONFIG.SYS or AUTOEXEC.BAT file on drive C
and the loading of the CFGDEV.SYS and DECODE.SYS drivers can be taken out of the normal
boot sequence. DOS can help some, with the CTL-C and the F8 escape sequences.
The MX2 provides an alternative method that is less accessible to the end user. To bypass the
CONFIG.SYS and AUTOEXEC.BAT files on drive C, reboot the unit (with either a cold or warm
boot), and when the message “Wait…” appears on the display, immediately press the [ESC] and
[Space] keys at the same time. This causes alternative CONFIG.SYS and AUTOEXEC.BAT
processing to take place on drives A and B without chaining into the files on drive C.
The unit indicates safe-boot mode by emitting a low tone followed by a higher-pitched tone. The
flash drive (C) and the RAM drive (D) will be preserved, and the boot sequence will place the unit
at the C:\> prompt.
Note: If you do not hear the two tones indicating the safe-boot sequence, you probably did not
press the ESC and Space keys quickly enough. Reboot the MX2 and press the two keys
simultaneously as soon as you see the “Wait…” message on the display.
Hardware Reset
In the extremely rare situation where none of the rebooting methods is successful, you can use a
reset mechanism that is located below the keypad matrix directly below the Lamp key.
By inserting a paper clip or other narrow device and pressing gently, the unit will perform a
hardware activated cold boot. Only use the same amount of pressure used to press a normal key.
Do not use a sharp instrument. If the keypad rubber matrix is punctured, the industrial
specifications of the MX2 could be compromised.
Note: Attempt at least two cold boots before going into Hardware reset.
Upon reset, you will need to set the date and time in the MX2. These DOS programs may run
automatically after a Hardware Reset.
Figure 2-3 Location of the Hardware Reset Mechanism
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 31
Using PC Cards 21
Using PC Cards
Note: The PC card slot of the MX2 is not user accessible, but functions in the same manner as
the LXE 2325 for software installation, use and general features. Please refer to the
"LXE 2325 Reference Guide” for PC card information.
The MX2 has a slot for plugging in PC cards, and each unit is factory-equipped with Phoenix
CARD Manager Plus PC card drivers. PC cards provide such features as network connectivity,
modem connectivity, and wireless capability. Their primary purpose in the MX2 is to provide
additional memory storage by functioning as a disk drive.
The MX2 holds one PC card at a time. If the MX2 has a radio card installed, the radio card will
need to be removed before a different PC card can be inserted.
The IR Serial Port
Figure 2-4 The IR Port on Bottom of Unit
The serial port is a half duplex IR (Infrared) port. Through software commands, the port may be
set up for IR or a modified RS-232 serial communication.
In general, the IR mode is used when communicating to other IR devices (printers, computers,
etc.) and the modified RS-232 mode is used to communicate with the dock for host
communications.
In IR mode, all physical communications meet the IrDA physical layer specification. In the
modified RS-232 serial mode, the IR port is used to transmit RS-232 level data out the IR port.
With the MX2 in the dock, the keypad facing the front of dock, the left-most pad is the RS-232
input (RXD) into the MX2 while it is in the dock.
Note: The MX2 does not propagate the RS-232 hardware signals such as RTS, CTS, DTR,
DSR, RI and DCD.
When transferring files using the IR port, flow control must be the same on both sides of the
transmission (specifically, with Zmodem: both sender and receiver must use Xon/Xoff).
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 32
22 Laser Scanner
Laser Scanner
Figure 2-5 Scanner Aperture Location
The Standard Range Scanner aperture is located at the back at the top of the MX2. Barcode
scanning is initiated when:
• The user presses the Scan button on an MX2 with 38-key keypad. This version of
the MX2 has one scan button – a large key in the middle of the keyboard labeled
Scan. This key cannot be reprogrammed.
• The user presses the Scan trigger on the handle. The handle is standard with the 48key keypad MX2. Since this model has no Scan button, this is the only way to
initiate a scan on the MX2 with 48-key keypad. MX2’s with the 38-key keypad may
have an optional handle. In this case, either the Scan button or trigger can be used.
Scan Button Location (38-Key Keypad) Scan Trigger on Handle (Standard with 48-
Key Keypad, Optional with 38-Key Keypad)
Figure 2-6 Scan Button and Scan Trigger
The only option for scanning with the MX2 is with the internal laser. Due to sealing and
environmental issues, no external port is available for external tethered scanners. When the MX2
does not have an installed scanner, although the scanner aperture is present, pressing the Scan
button or trigger has no effect.
To use the laser, aim the top of the unit at a barcode and press the Scan button.
A red LED directly below the LCD display indicates when the scanner is active. The LED
switches to green when a scan is successful.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 33
Handle Installation (Optional) 23
Handle Installation (Optional)
Note: The handle is standard with 48-key keypad units and optional with 38-key keypad units.
1. Battery Cover
2. Protective Diaphragm
3. Laser
4. Battery Cover Dials
5. Trigger
6. Washers
7. Screws
8. Pistol Grip
Figure 2-7 Insert Pistol Grip
To Install the Handle
1. Remove the screws located just above the battery cover’s latch dials. Remove the Pistol Grip
Cover.
2. Remove the Protective Diaphragm.
3. Insert the top tab of the Pistol-Grip Assembly into the slot at the top of the pistol grip recess.
Ensure the Pistol Grip assembly is firmly seated in the pistol grip recess.
4. Replace the screws located just above the battery cover’s latch dials.
5. Periodically check the fastenings and retighten if necessary.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 34
24 Hand-Strap Installation
Hand-Strap Installation
Note: The hand strap is not available with 48-key keypad units. These units include the handle
as standard equipment.
1. Hand Strap Clip
2. Hand Strap
3. Battery Cover
4. Laser
5. Battery Cover Dials
6. Pistol Grip Cover
7. Washers
8. Screws
Figure 2-8 Hand Strap Assembly
To Install the Hand Strap
1. Remove the screws located just above the battery cover’s latch dials. Remove the Pistol Grip
Cover.
2. Insert the top tab of the hand-strap cover into the slot at the top of the pistol grip recess.
Ensure the hand-strap cover is firmly seated in the recess.
3. Replace the screws located just above the battery cover’s latch dials.
4. Connect the hand-strap hook onto its connector at the base of the unit.
5. Periodically check the fastenings and retighten if necessary.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 35
The Disk Drives 25
The Disk Drives
The MX2 contains four logical disk drives that provide storage for system files, applications, and
data.
Drive A is a read-only drive. Its contents cannot be changed. Drive B is a read-only drive used to
store system utilities and to initialize the boot process. Its contents cannot be changed.
Drive C is a flash disk drive that allows full read and write access. This drive contains DOS
command files, PC card drivers, utilities, and executable files and associated files for applications.
It may also contain additional CONFIG.SYS and AUTOEXEC.BAT files to configure your MX2
to run applications.
Drive D is a RAM disk drive. The RAM disk is used primarily for data storage. Programs that
need to be loaded into memory and then quickly removed from memory can also be placed here.
Drive D can also be used for scratch disk space or temporary files.
Note: As with any RAM drive, data on drive D can be lost if the MX2 has a power failure
caused by low batteries or a system reset. For truly secure data collection, store your
data on drive C or on an ATA flash card.
Additional Drives
Drive E exists only if your unit has been configured to use PC ATA flash cards. The PC card
looks like a hard disk drive to the operating system. You can use drive E for safe and permanent
storage of data.
Alternately, drive E could be a peer-to-peer or client-server network drive that is accessed
through a wireless access point or Ethernet network card link.
Your unit may have other additional logical drives. These might be RAM drives, ATA flash cards,
or network drives accessed via wireless access points.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 36
26 Configuring the MX2
Configuring the MX2
If your unit is not already configured for use when you get it, please refer to “Radio PC Card
Configuration”, later in this chapter and also to Chapter 3, “Software Configuration”.
You can also scan barcodes with the MX2 to change MX2 configuration settings. For more
information, please refer to the “Integrated Scanner Programming Guide for DOS Devices”,
available on the LXE Manuals CD-ROM.
Troubleshooting - Enable I 2 of 5
Problem
The MX2 configuration does not retain “Enable I 2 of 5” after power down. Note that this is an
isolated incident and that the default MX2 with scanner configuration automatically enables Code
39, I 2 of 5, Codabar/Ames, Code 128, UPC-A and EAN/JAN.
Solution
Create a file containing the actual character string of the barcode used to set that particular
parameter. The character strings are printed under the barcode in the “Integrated Scanner
Programming Guide for DOS Devices”, available on the LXE Manuals CD-ROM – do not add the
asterisks to the character string. Any number of setup strings can be used, one per line in the file
used. After the file is created, copy the contents to the device PARAMS when the
AUTOEXEC.BAT file is loaded.
For example, the setup string to enable I 2 of 5 is $+$-151EE.
1. Create an ASCII file – CUSTPARM.TXT – that contains the following line:
2. Place the following line in the AUTOEXEC.BAT file and the command will be run each time
the AUTOEXEC.BAT file is run:
Transferring Files
To transfer data or program files, connect your MX2 to the host computer with any of the
following accessories:
Your software application may have simple file-transfer options, or you can use the REMDISK
and REMSERV utilities.
For more information on REMSERV and REMDISK, please refer to Chapter 4, “Commands”.
$+$-151EE
COPY CUSTPARM.TXT PARAMS
• Serial cable
• Single Dock
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 37
Advanced Power Management 27
Advanced Power Management
The MX2 uses advanced power management (APM) to provide the longest battery life. Control of
the APM features is provided in the PM.COM
This section provides additional information for getting the most power life out of an MX2 RF
unit using the RangeLAN2 wireless LAN PC card.
utility on drive B of each MX2.
Batteries
For RF units, LXE recommends the use of fully charged batteries. In general, an MX2 with an RF
card should be able to get through a normal 8-hour shift before the batteries need to be replaced or
recharged.
Doze Mode
After 8 seconds without a keypress, scanner input, or other system activity, the MX2 goes into a
power-saving state known as doze mode. To maximize battery life, especially in an RF
environment, try to avoid accidental or unnecessary pressing of the keypad keys.
Auto-Off Timer
After a predetermined time without any system activity, the unit automatically shuts off. The
default auto-off timeout is 5 minutes. To maximize battery life, you can set the timeout to a much
shorter period.
The “Integrated Scanner Programming Guide for DOS Devices”, available on the LXE Manuals
CD-ROM, includes bar codes that provide auto-off settings as low as 20 seconds. You can also
use the PM.COM utility to set the auto-off timer.
Backlight
Use of the display backlight severely affects battery life in the MX2. For RF applications, do not
use the backlight unless it is absolutely necessary. If you do need to use it, you can change the
display’s auto-off timer to a setting lower than the default (15 seconds).
The “Integrated Scanner Programming Guide for DOS Devices”, available on the LXE Manuals
CD-ROM, includes bar codes that provide settings as low as 2 seconds for the backlight auto-off
timer. You can also use the PM.COM utility to set the timeout.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 38
28 Advanced Power Management
Power Management at the Radio Card
To conserve battery life, the radio card has an inactivity sleep mode. The sleep mode is
automatically engaged when a certain period of time has elapsed since the computer has sent or
received data over the network. Once the card is asleep, it can be awoken by an access point
attempting to send data to it. The time before sleeping is calculated by adding the
Inactivity_min and Inactivity_sec parameter settings.
Note: Do not set an inactivity timeout on an RF MX2 being used as a master station. If the unit
goes to sleep, you will lose all communication with your network.
The access point buffers packets that are to be sent to the MX2s. A dozing radio card will receive
a sync message and wake-up list from the Access Point every 400 ms. The AP adds a media
access control (MAC) address to the wake-up list each time a send attempt fails. (The access point
buffers the packet and adds the MAC address of the MX2 to its wake-up list.)
If an MX2 detects that it is on the wake-up list, the radio card exits doze mode and enters receive
mode. Once the radio card wakes up to receive the packet, it stays awake for all future sends until
the inactivity timeout expires. This is why it is important to have the inactivity timeout as low as
possible. The advantages of a higher timeout value is that the radio card will remain in Receive
mode for longer periods of time; network throughput may be better because the unit will not have
the delay of coming in and out of doze mode or of waiting for the wake-up list to see if there are
any packets.
Generally, in the types of environments that the radio card will be used in, the user should strive
for maximum power management. Most MX2 RF applications will not be expecting asynchronous
network traffic, and it is doubtful that throughput differences due to power management will be
noticeable with these types of applications. Always set the Inactivity_min parameter to 0,
and set the Inactivity_sec parameter as low as possible (preferably to 1). Never set
Inactivity_sec to 0, as that turns off the power management completely, and the card will
always stay in receive mode.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 39
Radio PC Card Configuration 29
Radio PC Card Configuration
Note: LXE will pre-install radio cards and drivers on MX2 RF units before delivery. These
instructions are included for those users who may need to reinstall radio drivers and
reconfigure radio parameters.
After installing the radio card, you must configure the MX2 to use the card. Please refer to the
appropriate section for your radio card in the remainder of this section.
Note: Symbol FHSS radios are obsolete (6/2005).
Introduction
Note: The information and programs in this section only pertain to LXE’s 2.4GHz system
radios. They do not work with LXE’s 900MHz system radios.
Change the radio parameters by editing the NET.CFG file in the PCTCP directory. This can be
done with any ASCII text editor or NED. The NET.CFG file is the configuration file used by the
radio card’s ODI driver. The NET.CFG file determines the wireless network name, the
workstation name and other information regarding the wireless system.
2.4GHz radio parameters cannot be changed using LXE’s terminal emulation (TE) configuration
utilities.
The Sockets software package provides an interface to all of the TCP/IP parameters. Parameter
configuration is performed by editing the file SOCKET.CFG.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 40
30 Radio PC Card Configuration
NET.CFG Parameters
Lucent Parameters
The following is a list of parameters that can be modified in the NET.CFG file for computers with
Lucent 2.4GHz radios. For additional information about the parameters in this file see the
WVLAN43.CFG file located in the PCTCP directory. To set the TCP/IP parameters see the
SOCKET.CFG file documentation.
Link Support
Parameter used to define resources for the LSL.COM file. Any modifications may cause resource
conflicts.
Protocol
Instructs TCP/IP stack to bind to radio driver.
WaveLAN_Network_Name
Identifies the WaveLAN network the station will connect to.
Valid: 0 to 32 string of printable uppercase
characters.
Default: ANY
Station_Name
AP_Distance
Note: Setting this value to ANY will enable the station to connect to any IEEE 802.11 network.
Note: The string for WaveLAN_Network_Name is case-sensitive. The WaveLAN DOS ODI
driver requires the use of only UPPERCASE characters. If you have configured the
Access Points with lower-case names you will need to change your Access Point
WaveLAN_Network_Name parameter to UPPERCASE characters for proper operation.
Or, place double quotes around the WaveLAN_Network_Name to allow proper operation
with upper and lower case letters e.g. "NameofUnit".
Identifies the stations on the network. This parameter is used when performing diagnostic tests.
Valid: 0 to 32 string of printable characters.
Default: station_name
Controls the roaming sensitivity of your computer. This parameter must be set according to the
settings of the WavePOINT-II access points.
Valid: 1=Low
2=Medium
3=High
Default: 1
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 41
Radio PC Card Configuration 31
Microwave_Robustness
This option should only be used when troubleshooting slow performance of the network that
could be related to in-band interference from microwave ovens.
Use this option when experiencing recurrent “bursts” of in-band interference exhibited by specific
units where the unit (or the access point) is close to a microwave oven or a microwave oven is
located in the signal path between the unit and the access point. The radio will try to retransmit the
“lost messages”. When retransmission fails again, the radio in Auto Transmit Rate Select
Mechanism mode will attempt to retransmit the message again at a lower data speed. (See
Transmit_Rate)
Selecting “Y” will enable fragmentation of data frames when the automatic transmit rate selection
switches to a lower transmit rate. Fragmentation will avoid increased vulnerability due to longer
frame lengths of transmissions at lower data speeds.
Valid: Y=Yes, N=No
Default: N
Transmit_Rate
Controls the data rate the WaveLAN card will use. Supported rates depend on the card. If the card
does not support the selected rate, the default value of 3 is selected automatically.
Valid: 1=Fixed Low
2=Fixed Standard
3=Auto Rate Select (High)
4=Fixed Medium
5=Fixed High
6=Auto Rate Select (Standard)
7=Auto Rate Select (Medium)
Default: 3
Medium_Reservation
Enables RTS/CTS communications. Sets the frame length threshold that determines when the
station should start using RTS/CTS.
Valid: 0-2347
Default: 2347
Note: The use of Medium Reservation is recommended in network environments where the
density of the WaveLAN stations and WavePOINT-II access points is very low, and
where there is poor network performance due to excessive frame collisions at the
WavePOINT-II access points.
Card_Power_Management
Configures the power management used by the station in an ESS. The recommended mode is
Enhanced Power Management (EPM) for hand held computers. In this mode, the station switches
between Power Save Mode (PSM) and Continuous Active Mode (CAM), based on activity. Any
frame transfer switches the station to CAM. Inactivity for 100ms switches the station to PSM.
For hand held computers, the default is EPM.
Valid: 0=CAM (No power savings)
1=EPM
2=PSM (Maximum power savings)
Default: 1
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 42
32 Radio PC Card Configuration
Maximum_Sleep_Duration
Configures the maximum amount of time the radio will stay in Sleep mode.
Valid: 1-65535
Default: 100 (10 seconds)
Receive_All_Multicasts
Configures whether this station will receive Multicast packets.
Valid: Y=Yes or N=No
Default: N
Enable_Encryption
Configures whether this station will receive/send encrypted data traffic. When “Y” is chosen, the
unit will be able to receive both non-encrypted data and messages encrypted with one of the listed
WEP encryption key values (see Transmit_Key_ID).
If encryption is enabled (Y) while the card does not support WEP, an error is reported.
Valid: Y=Yes or N=No
Default: N
Transmit_Key_ID
If you enable WEP encryption, you can select one key for wireless data transmissions from the list
of WEP Encryption Key Values.
Key1 abcde
Key2 0x123456789a
Key3 abcdefghijkl2
Key4 0x112233445566778899AABBCCDD
Valid: 1-4
Default: 1
Format: Transmit_Key_ID 1
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 43
Radio PC Card Configuration 33
Proxim Parameters
The following is a list of parameters that can be modified in the NET.CFG file. To set the TCP/IP
parameters see the SOCKET.CFG file documentation.
Link Support
Parameter used to define resources for the LSL.COM file. Any modifications may cause resource
conflicts.
Protocol
Instructs TCP/IP stack to bind to radio driver.
Int
Sets the interrupt (IRQ) line to be used. MX2 specific setting is int 3.
Default: 3
Port
Sets the I/O port address. Use 300 for the MX2.
Default: 0x300
Mem#1 (ODI)
Domain
Station_type
Socket
Memory_address sets the resource memory location (0xC000 to 0xE800). Upper memory blocks
from 0xA000 to 0xCFFF are used by MX2 system software.
Default: c100
Sets the network domain. It can be any number from 0 through 15 and must match the domain of
the server or access point to which you want to connect.
Valid: 0 through 15
Default: 0
Sets the status of the PC card as a master (2), alternate master (1), or nonmaster (0) station.
Valid: 0, 1, 2
Default: 0
Sets the PCMCIA socket (A, B, C, or D) that has the PC card installed. The MX2 always uses
socket A for PC cards.
Valid: A, B, C D
Default: A
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 44
34 Radio PC Card Configuration
Initialize_365
Determines whether to initialize the Intel 82365SL PCMCIA controller chip. The MX2 does not
contain this chip, so this parameter must be set to N.
Valid: Y, N
Default: N
Inactivity_min
Sets the number of minutes of inactivity before the PC card goes to sleep. To minimize draw on
the vehicle battery, set this to 0.
Valid: 0 through 20 minutes
Default: 0
Inactivity_sec
Sets the number of seconds of inactivity before the PC card goes to sleep. Valid settings are 0
through 55 (values above 5 are rounded to the nearest multiple of 5). To maximize battery life, set
this as low as possible, preferably to 1.
Valid: 0 through 55 seconds
Default: 1
Channel
Subchannel
Mac_optimize
Roam_config
Peer_to_peer
Sets the channel to be used when the PC card is acting as the master.
Valid: 1 through 15
Default: 1
Sets the subchannel to be used when the PC card is acting as the master.
Valid: 1 through 15
Default: 1
Optimizes the PC card for the number of concurrent modes.
Valid: 0 (light) or 1 (normal)
Default: 1
Sets the roaming speed.
Valid: 0 (slow), 1 (normal) or 2 (fast)
Default: 1
Sets the ability of the PC card to talk to other peers.
Valid: N (off) or Y (on)
Default: N
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 45
Radio PC Card Configuration 35
Cisco Parameters
The following is a list of parameters that can be modified in the NET.CFG file. To set the TCP/IP
parameters see the SOCKET.CFG file documentation.
Link Support
Parameter used to define resources for the LSL.COM file. Any modifications may cause resource
conflicts.
Protocol
Instructs TCP/IP stack to bind to radio driver.
SSID
Identifies the 802.11B wireless network the station will connect to.
Default: “”
Note: Setting this value to “” will enable the station to connect to any IEEE 802.11b network.
FragThreshold
RTSThreshold
DataRateX
Packet size to start fragmenting.
Default: FragThreshold 2312
Packet size to start sending RTS/CTS.
Default: RTSThreshold 2312
To set a data rate other than 11 MB default uncomment rate desired and all data rates less than
that rate. Example to set for 5.5MB data rate uncomment the DataRate1, DataRate2 and
DataRate3.
1 Mbps supported data bit rate
DataRate1 0x02
2 Mbps supported data bit rate
DataRate2 0x04
5.5 Mbps supported data bit rate
DataRate3 0x0B
11 Mbps supported data bit rate
DataRate4 0x16
RefreshInterval
Inactivity time to check association with AP
RefreshInterval 10000
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 46
36 Radio PC Card Configuration
PowerSaveMode
PowerSaveMode "FASTPSP"
Fast Power Save Mode
MaxPowerSave
Maximum power save mode
MaxPowerSave "ON"
NodeName
Descriptive station name
NodeName " "
WEP enable
To enable WEP uncomment the following line and set the key with the wepdos.exe utility (Cisco
340 radios only)
authtype "wepopen"
Set WEP key in radio before wepopen using the WEPDOS program in the PCTCP directory.
Diversity
The diversity parameter must be set according to the number of antennas for each computer.
MX2 computers = 1 antenna, right port.
Diversity ”on” for 2 antennas
Diversity “left” for 1 antenna left port
Diversity “right” for 1 antenna right port
PortBase – IRQ – Memory Socket
The adapter needs 32 16-bit I/O ports, and 1 non-sharable IRQ. Any commented lines are
managed PCMCIA card & socket services and should not be changed or uncommented.
PortBase 100
;IRQ 5
Memory C0000
;Socket 0
BusType
PCMCIA interface is used on all LXE DOS computers.
BusType "PCMCIA"
Frame
Frame type of wired and wireless network.
(Default) Frame ETHERNET_II
Frame ETHERNET_802.3
Frame ETHERNET_802.2
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 47
Radio PC Card Configuration 37
Cisco 350 Radio Only
The following lines appear in the NET.CFG file for the Cisco 350 radio.
LEAP “OFF” ;LEAP authentication (OFF -or- ON)
WorldMode “OFF” ;World mode (OFF -or- ON)
ShortPreamble 0 ;PLCP short preamble (0=auto, 1=long, 2=short)
LEAP
Used to set LEAP (Light Extensible Authentication Protocol) authentication on LXE computers
equipped with Cisco 350 series radios.
Valid: OFF or ON
Default: OFF
Note: This parameter is valid for Cisco 350 series radios only.
WorldMode
ShortPreamble
AWCLEAP
Allows the radio to adopt the maximum transmit power level and frequency range of the access
point to which it is associated (available only in infrastructure mode).
Valid: OFF or ON
Default OFF
Note: This parameter is valid for Cisco 350 series radios only.
This parameter allows the radio to use short radio headers (or preambles). Short radio headers
improve throughput performance. Long radio headers ensure compatibility if a client or access
point does not support short radio headers.
Valid: 0=auto
1=long
2=short
Default: 0
Note: This parameter is valid for Cisco 350 series radios only.
AWCLEAP is a DOS utility used to set the LEAP (Light Extensible Authentication Protocol)
authentication. The SETLEAP.BAT file runs the AWCLEAP utility. To set LEAP, type
setleap <username> <password> at the c:\pctcp prompt.
The CLEAR.BAT utility is used to clear the LEAP username and password. To clear LEAP, type
clear at the c:\pctcp prompt.
The SETLEAP.BAT batch file is used to run the AWCLEAP utility.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 48
38 Radio PC Card Configuration
WEPDOS
WEPDOS utility is used to program the WEP key into the Cisco radios. Once the key value and
key number to be used is set the authtype parameter in NET.CFG file must be modified. To set
the key type wepdos at the c:\pctcp prompt.
Syntax
WEPDOS [-ascii|-hex] [-key#|-home] key ;set a key
WEPDOS [-key#|-home] –clear ;clear a key
WEPDOS [-tx#] ;select transmit key index
WEPDOS [-d] ;display settings
Where
key is a 5 character ASCII string
key is a 10 character hex-digit number
WEP128 allows 5 or 13 character ASCII, and 10 or 26 hex-digit keys
-key# is default key index 1, 2, 3 or 4
-home selects the home key for use with home access points
-tx# selects the transmit key index 1, 2, 3 or 4 (enterprise networking)
Standard Options
-p[iobase] io base address (hex) [380]
-b[membase memory base address (hex) [D000]
-i[irq] interrupt request (decimal) [10]
-s[slot] slot number (decimal) [0]
-365 82365 startup of card
Default: no startup, IO:380, MEM:D000:0, IRQ:10, SLOT:0
Examples
To check WEP key on a LXE computer the correct syntax to type at c:\ prompt
wepdos -365 -p100 -bc000 -d
To set key for use type
wepdos -365 -hex -key# <10 or 26 byte key> -tx# -d
WEPDOS supports up to 4 keys. As an example of setting key number 1 to abcdefghijklm for use
in transmitting type:
wepdos -365 -p100 -bc000 -key1 -tx1 -ascii abcdefghijklm –d
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 49
Radio PC Card Configuration 39
Symbol Parameters
The following is a list of parameters that can be modified in the NET.CFG file. To set the TCP/IP
parameters see the SOCKET.CFG file documentation.
Link Support
Parameter used to define resources for the LSL.COM file. Any modifications may cause resource
conflicts.
Protocol
Instructs TCP/IP stack to bind to radio driver.
ESS_ID
Identifies the 802.11B wireless network the station will connect to. The ESS_ID is a string of 1 to
31 case sensitive characters. Spaces may be included by using quotes.
Default: “LXE”
mode
IO mode required if using card and socket services.
Default: IO
ioaddress
Sets the I/O address location.
memory
Sets the resource memory location.
interrupt
Sets the interrupt (IRQ) line to be used.
performance_index
Configures whether the Symbol 4121 series radio will perform power management.
Auth_type
This parameter is used to enable and manage the 802.11 WEP encryption. The radio card will
only associate with APs that support the same Auth_type.
Default: 340
Default: C000 (2MB radio) C900 (11MB radio)
Default: 3 (2MB radio) 5 (11MB radio)
Valid: 0=CAM Constant Awake Mode
1=Power Management On
Default: 1
Valid: “Open_System” or “Shared_Key”
Default: “Open_System”
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 50
40 Radio PC Card Configuration
Encrypt_Key#
Updates the first, second, third or fourth encryption key, according to the value of #.
For Symbol FHSS radio cards, the key consists of 5 pairs of hex digits (0-9, a-f, A-F) in a string.
For Symbol 4121 series radio cards, use 5 pairs of hex digits for 40 bit encryption. Use 13 pairs
of hex digits for 128 bit encryption.
encrypt_enable
Enables encryption on Symbol 4121 series radios.
Valid: yes or no
Default: yes
Note: This parameter was removed from the Symbol NET.CFG file by LXE effective November
2003.
Encrypt_Key_ID
The key ID indicates which key the adapter is to use for encrypting packets.
Valid: 1 to 4
Default: 1
Note: This parameter is valid for Symbol FHSS radios only.
Encrypt_Enable_Index
Previously named encrypt_key_index. This parameter indicates which key the adapter is to use for
encrypting packets for transmission. Zero means No Encryption (i.e. turn encryption off), and
numbers 1 through 4 mean turn encryption on and use the specified key (i.e. key #1, key #2, key
#3 or key #4). The key to be used to decrypt packets being received is contained in the received
packet.
Valid: 0,1,2,3,4
Default: 0 (No Encryption)
Note: This parameter is valid for Symbol 4121 series radios only.
diversity
Set diversity to “both” for two antennas and “A” for one antenna. MX2=A
Default: both
Tx_rate
Use this parameter to specify that rates at which the radio is allowed to operate. If no rates are
specified, the radio will use all available rates.
Valid: 1 1 Mbps
2 2 Mbps
5 5.5 Mbps
11 11 Mbps
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 51
Radio PC Card Configuration 41
SOCKETS TCP/IP Stack
Introduction
SOCKET.CFG sets the options for SOCKETP.EXE. The section XXX.XXX.XXX.XXX is for
this machines IP. The net mask is specified as part of the IP address. In the IP address command
an optional /net_bits can be used to indicate the number of bits in the network ID.
Net Bits Net Mask Class IP address range
8 255.0.0.0 A 0.x.x.x to 127.x.x.x
16 255.255.0.0 B 128.x.x.x to 191.x.x.x
24 255.255.255.0 C 192.x.x.x or higher
The network can be subdivided by two for every net bit added.
Bootp
DHCP
Net
Bits
1 128 5 248
2 192 6 252
3 224 7 254
4 240 8 255
BOOTP is a UDP/IP based protocol that provides a means to assign an IP address to a booting
host dynamically and without user supervision. BOOTP can also supply the net mask, host name,
and address of a domain name server. One obvious advantage of this procedure is the centralized
management of network addresses, which eliminates the need for per-host unique configuration
files. Sockets implements the BOOTP client whenever it is started with no (or the 0.0.0.0) IP
address supplied.
DHCP is a UDP/IP based protocol that provides a means to assign the IP address dynamically to a
booting host and without user supervision. It can also supply the net mask, host name, address of a
domain name server, and other parameters. An advantage of this procedure is the centralized
management of network addresses, which eliminates the need for per-host unique configuration
files. Sockets implements the DHCP client whenever it is started with the 0.0.0.1 IP address
supplied. All LAN interfaces specified when this IP address is in use will attempt to use DHCP to
resolve the IP address, the subnet mask, hostname, default router and DNS server(s).
Net
Mask
Net
Bits
Net
Mask
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 52
42 Radio PC Card Configuration
Setting SOCKETS.CFG Parameters
Set IP Address
To enable DHCP set the IP address to 0.0.0.1
IP address XXX.XXX.XXX.XXX/16
where
XXX.XXX.XXX.XXX is the IP address
16 indicates the number of bits in the network ID
Set ARP INIT
Controls whether a DHCP ARP is sent when booting up.
ARP INIT GRAT
Using this option makes the stack behave the same as before. The stack does not send a DHCP
ARP when booting up (In this mode, the ARP contains the MAC and IP addresses in the sender’s
field). This option is the default.
ARP INIT DHCP
Set Interface
Using this option sends a DHCP ARP on boot up (the sender’s IP address field is zero filled).
For all radios except Symbol DS 11MB
Interface sets the physical interfaces
Interface pdr if0 dix 1500 10 0x69
where
pdr = packet driver
if0 = interface_card
dix = frame type
1500 = MTU
10 = Buffers
0x69 = ioaddr
For Symbol DS 11MB radios
Interface sets the physical interfaces
Interface pdr if0 dix 1400 10 0x69
where
pdr = packet driver
if0 = interface_card
dix = frame type
1400 = MTU
10 = Buffers
0x69 = ioaddr
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 53
Radio PC Card Configuration 43
Set Router IP (Gateway only)
When using a gateway (IP router) to the rest of the world, replace “XXX.XXX.XXX.XXX” with
your gateway ip and remove the # at the beginning of the line.
# route add default if0 XXX.XXX.XXX.XXX
Set Domain Name Server
When using a domain name server (DNS), replace XXX.XXX.XXX.XXX with the IP address of
the DNS, and remove the # at the beginning of the line.
# domain server XXX.XXX.XXX.XXX
Display IP Address
Redisplay IP information when SOCKET.CFG runs.
IP address
Options
For all radios except Symbol DS 11MB
Refer to documentation to change.
ip ttl 15
tcp mss 1460
tcp window 2920
tcp retry 8
tcp irtt 500ms
For Symbol DS 11MB radios
Refer to documentation to change.
ip ttl 64
tcp mss 1360
tcp window 2920
tcp retry 8
tcp irtt 500ms
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 54
44 Radio PC Card Configuration
SOCKET.CFG Parameters
domain
If a host name is not a decimal (dotted) address and it is not found in the HOSTS file and at least
one Domain Name Server has been defined, an attempt is made to obtain the address from the
defined DNS server(s). The number of times any server is polled (retries), in addition to the time
to wait for a response, can also be specified. A suffix may be specified and is attached to all
names not containing any dots.
All of the following sub-commands can be issued without the optional parameters to obtain
information on the current status.
Syntax
domain server [host_name]
domain retry [retry_count]
domain time [wait_time]
domain suffix [domain]
domain server adds a DNS address or lists the current servers if host_name not specified.
domain retry specifies the retry count for polling each server. domain retry lists the retry count if
retry_count not specified.
iface
interface
domain time specifies or lists the time (milliseconds) to wait for a response before attempting
retry.
domain time lists the time (milliseconds) to wait if wait_time not specified.
domain suffix specifies the domain suffix to add to all simple names; names that contains no dots.
domain suffix lists the domain suffix if domain is not specified.
Example
domain retry 3
domain server 196.2.1.1
domain suffix myorg.co.za
domain time 2000
iface is a synonym for the interface command.
interface informs Sockets of the hardware or software communications interface(s) to be used at
the network interface level. At least one network interface is required, and two or more are used in
gateway (router) applications.
The class or mode of each interface defines the encapsulation used for packaging the data frame
into the transport frame. Some types of interface support only one class.
When using more than one interface, Sockets assigns the previous given IP address in the .CFG
file to this interface and uses its net mask to add a route to that net through this interface. Using
the same IP address would result in multiple routes to the same network. The default route is set
on the first interface with an IP address with a zero net mask (for example, IP address
100.100.100.100/0).
Each interface statement uses the IP address from the last supplied IP address statement.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 55
Radio PC Card Configuration 45
Syntax (general)
interface type name class other parameters
Syntax (specific)
interface pdr name dix mtu numbuf intvec [irq]
interface asy name [slip | cslip | ppp] mtu buflim ioaddr
iovec speed [modemfile]
Parameters
Type
Type defines the type of hardware or software interface.
interface supports the following software interfaces.
Interface Description
Asy Standard PC asynchronous interface (RS232 port)
Pdr packet driver interface
name
name defines the name by which the interface is known on the local host. name is a symbolic
name known only to the local host on which it is used.
name may be arbitrarily assigned. Each interface command on the same host must have a unique
name assigned. This name is used by commands such as route, trace, param, and so on.
class
class specifies how IP datagrams are to be encapsulated in the link level protocol of the interface.
Some interfaces offer a choice between classes while others use a fixed class. The following
classes are available and are listed with their associated types.
Type Class (defined in the following list)
Pdr dix, ieee, token, driver, slip
Asy raw, slip, cslip, ppp
Class Description
Dix The DEC/Intel/Xerox Ethernet interface also known as Blue Book Ethernet
or Ethernet II.
Token IBM Token Ring. Source routing is supported for multiple rings.
Ieee IEEE: 802.3 Ethernet with SNAP headers.
Driver Use the default class for the packet driver.
Slip Serial Link Internet Protocol (SLIP) for point-to-point asynchronous links.
This mode is compatible with UNIX SLIP.
Cslip Compressed Serial Link Internet Protocol (SLIP) for faster reaction over
point-to-point synchronous links.
Ppp Point-to-point protocol over asynchronous links.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 56
46 Radio PC Card Configuration
mtu
mtu specifies the Maximum Transmission Unit size, in bytes. Datagrams larger than this limit are
fragmented into smaller pieces at the IP layer. The maximum value of mtu for the various
interfaces is:
Ethernet - 1500
For serial links a standard value for mtu is 576. (576 is the maximum according to specifications,
but may be increased on reliable connections as long as both sides use the same value.)
numbuf
numbuf specifies how many incoming datagrams may be queued on the receive queue at one time.
If this limit is exceeded, further received datagrams are discarded. This mechanism is used to
prevent fast interfaces from filling up memory when data cannot be handled fast enough.
buflim
buflim specifies the maximum number of outgoing datagrams or packets to queue before starting
to discard datagrams. This mechanism is used to prevent the memory from filling up when a serial
link goes down.
bufsize
bufsize specifies the size of the ring buffer in bytes to be allocated to the receiver in raw mode.
intvec
intvec specifies the software interrupt number (vector) in hexadecimal to use for resident packet
drivers.
ioaddr
ioaddr is the I/O base address in hexadecimal of a serial port or the hardware controller and must
correspond with the jumper or switch settings used during the setup of the controller board. The
standard values for serial ports are:
COM1 03F8h
COM2 02F8h
COM3 03E8h
COM4 02E8h
iovec
iovec is the hardware interrupt vector used by the serial port or controller and must correspond
with the jumper or switch settings used during setup of the controller. The standard values for
serial ports are:
COM1 4
COM2 3
COM3 4
COM4 3
irq
irq is the hardware interrupt vector used by the network interface controller. This is only used for
faster response in Sockets.
modemfile
A file containing the modem commands and scripts.
speed
speed specifies the transmission speed for serial interface devices (baud rate). Before using a
serial connection you have to set flow control with the param command.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 57
Radio PC Card Configuration 47
Examples
interface pdr if0 dix 1500 5 0x60
interface asy ser0 cslip 576 15 0x3f8 4 9600
interface asy p0 ppp 1500 30 0x3f8 4 9600 pppmod.mod
ip
ip displays or sets the values of the options selected when defining the IP (internet protocol) host
address of the next interface to be defined.
Syntax
ip address [hostid [/net_bits] ]
ip status
ip ttl [number]
ip address sets the IP host address of the next interface to be defined. A route is automatically
added to each interface for the default or specified net mask for its address. To make an automatic
route the default, specify the net bits as zero. When specified without the optional parameters, ip
address displays the current value(s) of the local host IP address(es). To assign different IP
addresses to different interfaces on the same host, an ip address statement must precede each
interface definition. The last IP address given is used in case of missing ip address statements.
ip status displays Internet Protocol (IP) statistics, such as total packet counts and error counters of
various types. It also displays statistics on the Internet Control Message Protocol (ICMP). This
includes the number of ICMP messages of each type sent or received.
ip ttl sets the default time-to-live value which is placed in each outgoing IP datagram. The ttl
value limits the number of gateway hops the datagram is allowed to take in order to kill datagrams
that got stuck in loops.
Parameters
hostid
hostid specifies the IP host address to assign to the next interface to be defined. This may be a
symbolic name from the HOSTS file, or a dotted decimal address.
/net_bits
A net mask can be specified for the host. In the ip address command an optional /net_bits can be
used to indicate the number of bits in the network ID. The net mask is used to determine whether
an incoming datagram is a broadcast and also for sending UDP broadcasts.
Net masks are more easily represented in binary or hexadecimal format. For example, the IP
address 128.1.1.5/24
corresponds to a net mask of 255.255.255.0 (FFFFFF00h),
25 bits to 255.255.255.128 (FFFFFF80h)
and 26 bits to 255.255.255.192 (FFF FFC0h).
The default net mask used corresponds to the class of address used if not explicitly specified.
Net Bits Net Mask Class IP address range
8 255.0.0.0 A 0.x.x.x to 127.x.x.x
16 255.255.0.0 B 128.x.x.x to 191.x.x.x
24 255.255.255.0 C and higher 192.x.x.x or higher
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 58
48 Radio PC Card Configuration
If you want to subdivide your network, you can divide it by two for every net bit added. The
following table provides information on converting between net bits and net mask. The number of
net bits to add when changing a 0 in the net mask to:
Net Bits Net Mask Net Bits Net Mask
1 128 5 248
2 192 6 252
3 224 7 254
4 240 8 255
number
When number is omitted, ip ttl displays the current value of the time to live parameter.
param
param invokes a device-specific control routine. When executed without parameters, param
displays defined interface names and device-specific flags. param operates differently for each
interface type and even interface mode. In many cases it is used to interrogate the status of an
interface. The ifstat and param commands perform similar and, in some cases, exactly the same
function.
Syntax
param ifname [arg1...argn]
Parameters
ifname
ifname defines the name used in the interface command for the device to be controlled.
arg1...argn
These parameters depend on the type of interface in use.
Example
To display current serial link settings and restart the statistics on it, use:
param sl0 clear
param, Alternative Routing Control Sub-commands
The Alternative Routing Control Sub-commands set up and check the Sockets alternative route
mechanism. More than one route can be specified to a target host or network. The first route
which has an associated interface in the up state is used.
An interface is in the up state when it is defined by the interface command. It enters the query
state when it does not receive valid input within a specified up-time period after sending data
expecting a response. At this stage three (catering for links with a high data loss) ICMP echo
requests (ping) are sent to a query IP address. It enters the down state by a Sockets command or
when it does not receive valid input within the specified up-time period after entering the query
state. If an up-time has never been specified or a value of 0 is specified, the interface will stay in
the up state whether valid input is received or not.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 59
Radio PC Card Configuration 49
An interface enters the up state by a Sockets command or when valid input is received on that
interface when in the down or query states. An ICMP echo request is sent on an interface in the
down state every down-time period. If a down-time has never been specified or a value of 0 is
specified, the ICMP echo request will not be sent. Up-time and down-time is specified in seconds.
Syntax
param ifname [ uptime | downtime ] time
param ifname query hostname
Example Alternative Routing
Two X.25 interfaces are used to get to the target network 192.6.1.0. The first interface, named if0
should preferably be used, but if it stops receiving for a period of 20 seconds, it should try to ping
192.6.1.2 and if no response is received within another 20 seconds, if1 should take over, but if0
should be tried every five seconds. Interface if1 should disconnect after 80 seconds of no traffic.
The SOCKET.CFG file should contain the following:
interface x25 if0 ... ... ...
param if0 uptime 20
param if0 downtime 5
param if0 query 192.6.1.2
interface x25 if1 ... ... ...
param if1 uptime 80
param if1 downtime 5
param if1 query 192.6.1.2
route add 192.6.1.0 if0
route add 192.6.1.0 if1
route
In the case of both if0 and if1 failing, both are tried every five seconds until one comes up. The
return paths should also be maintained in a similar way with Sockets or by using RIP.
param, RIP Advertising Sub-command for Interfaces
When the rip advertise command has been used, this param sub-command makes allowance to
disable and re-enable RIP advertising on a specific interface.
Syntax
param ifname [ ripadv | noripadv ]
Examples
param if0 noripadv
param if1 ripadv
route creates an entry in the IP routing table for Sockets to determine where to send data. The
Alternative Routing mechanism allows more than one route to be specified to a particular host or
network. Failure of one route causes an automatic switch to the next route.
Refer also to the ip address command for specifying the net mask, because a route is automatically
added to each interface for the default or specified net mask for that address. When multiple
routes are defined to the same address, Sockets uses the route with the network size (largest
number of bits in the net mask).
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 60
50 Radio PC Card Configuration
Syntax (general)
route [ add | drop destination ifname [gateid |none [ metric [proxy]
[private] [static] ] ] ]
Syntax (specific)
route add [ hostid | netid ] ifname [gateid]
route add [ hostid | netid[/mask] ] ifname [gateid]
route add default ifname
route drop [ hostid | netid ]
route drop [ hostid | netid[/mask] ]
route drop default
Parameters
add or drop
Sub-command to add or drop (remove) a route from the routing table.
default
All transmissions to IP addresses not otherwise defined in routing commands are sent via the
network interface specified by ifname.
hostid
hostid is the IP address of a destination remote host to which data must be sent, or a remote host
which must be removed from the routing table (dropped).
netid
netid is the IP address of a destination network to which data must be sent. Any host with this IP
network address is able to receive the data. Whether a particular host will use the data depends on
the host portion of the specific IP address in the IP header.
mask
mask specifies the number of bits in the network portion of the address if sub-netting is used. If
not used, the network portion of the address is determined according to the class (A, B or C) of
the address.
ifname
ifname defines the name used in the interface command for the immediate network on which the
data for the designated host must be sent. This is the network level interface to be used by the
local host to reach the remote host.
gateid
gateid parameter specifies the IP address of a host, on the same physical network as the local host,
which is used as a gateway or router to a different network. The gateway or router host specified
in gateid must be directly reachable on the same physical network as the local host defining this
gateway. In other words, this must be the nearest gateway to this local host.
metric
When using RIP or Proxy ARP a value from 0 to 16 for metric must be specified indicating the
distance or cost of that route. A metric of 16 indicates that the route is down.
proxy, private and static
To support the Routing Information Protocol (RIP) the route command utilizes the proxy, private
and static key words. These words can be used in any order following metric.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 61
Radio PC Card Configuration 51
Proxy ARP should be used with care and not in conjunction with RIP. When more than one host
responds to an ARP request, it can cause confusion and even lead to system crashes. This is
possible in situations where more than one gateway implements Proxy ARP to a common
destination.
When “RIP advertising” is selected, all interfaces advertise all routes except those routes making
use of that specific interface (split horizon) and routes marked private. A route which is dropped
as a result of a RIP update or which becomes unavailable as a result if its associated interface
going into the down state, is immediately advertised as being infinite (metric = 16) and is not
advertised until it becomes available again. In order for an interface to be used for advertising, a
route without a gateway using that interface must be available. The advertisement is sent as a subnet broadcast using the net mask of the host and the IP address of the interface.
When “RIP using” is selected, routes are updated according to received RIP advertisements.
Routes added or amended as a result of RIP, have a timeout associated with them. If another RIP
advertisement is not received during that time, the route is dropped. A route is also dropped if an
advertisement of infinity (metric = 16) is received. To prevent dropping a route, it must be marked
as static. The metric of a route marked static is never updated by a RIP advertisement. Instead a
duplicate route is added before the static route. If the duplicate route is dropped as a result of a
timeout or RIP, the static route is used again.
Examples
route add default ipx0
route add unix_net eth0
route add unix_host ipx1 unx_gate
route add unix_net2 eth0 /eth 1
route add unix_ net ipx0 unx_ gate
route add subnet/26 eth0 sub_gw
route drop unix_net
tcp
route can specify a Proxy ARP on a route, as follows:
route add net interface gateway metric [proxy]
When using Proxy ARP, gateway and metric must be specified. If no gateway is used, none can
be specified. For example:
route add 192.6.1.0 ifx25 none 5 proxy
tcp commands display or set various TCP operating parameters. The TCP configuration
commands are put into SOCKETS.CFG.
Syntax
tcp irtt [time]
tcp lport [port_number]
tcp mss [size]
tcp retry [number]
tcp rtt [time]
tcp smss [size]
tcp timemax [time]
tcp window [size]
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 62
52 Radio PC Card Configuration
Parameters
time
time is the new time value in seconds, or milliseconds if “ms” is appended to the number, as in
2000ms.
port_number
port_number is the local port starting number.
size
For tcp mss, size is the maximum segment size in bytes sent on all outgoing TCP connect requests
(SYN segments). size tells the remote host the size of the largest segment that may be received by
this host. When changing the MSS value, any existing connections remain unchanged.
For tcp smss, size is the send maximum segment size in bytes sent on all outgoing TCP connect
requests. This limits the size of the largest segment that may be sent by this host. When changing
the SMSS value, any existing connections remain unchanged.
For tcp window, size is the size of the receive window in bytes for any new TCP connections.
Existing connections are unaffected.
number
number is the number of retries attempted without receiving an acknowledge from the remote host
before the connection is broken. If the value exceeds 255, it implies an infinite number of retries;
such a connection does not time-out. The default value for number is 6.
tcp irtt Sub-command
tcp irtt displays or sets the initial round-trip-time estimate. When specified without an argument,
the command displays the current values of TCP parameters including the initial round-trip-time
in milliseconds.
time is the initial round-trip-time (IRTT) estimate and is used for new TCP connections until the
actual value can be measured and adapted to. By increasing this value when operating over slow
communication links, unnecessary retransmissions that otherwise occur before the smoothed
estimate value approaches the correct value are minimized. The system default is 5000
milliseconds.
To affect incoming connections, tcp irtt should be executed before the servers are started.
Example
tcp irtt 120
Sample Output
TCP: IRTT 5 ms Retry 6 MSS 1460 SMSS 1460 Window 2920
tcp lport Sub-command
tcp lport specifies the local port starting number. When specified without a number the current
value of the next free local port number is displayed.
Example
tcp lport 2004
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 63
Radio PC Card Configuration 53
Sample output
Lport = 2004
tcp mss Sub-command
tcp mss displays or sets the TCP maximum segment size in bytes. When size is not specified, the
current values of the TCP parameters, including the maximum segment size, are displayed. It is
recommended to reduce the MSS and SMSS on bad network connections.
Example
tcp mss 1460
tcp retry Sub-command
tcp retry displays or sets the retry count before a connection is broken. When specified without the
number parameter, tcp retry displays the current values of TCP parameters, including the retry
count.
tcp rtt sub-command
tcp rtt replaces the automatically computed round-trip time (RTT) for the specified connection with the
time in milliseconds. Sockets calculates the RTT as a smooth average of past measured RTTs,
starting with the IRTT on a new connection.
To get the current RTT in use for a connection n, use the tcp status n command that will give the
smoothed average RTT indicated by SRTT.
Because tcp rtt provides a manual override of the normal back-off retransmission
mechanisms, it may be used to speed up recovery from a series of lost packets.
timing
Example
tcp rtt 4 100
tcp smss sub-command
tcp mss displays or sets the TCP send maximum segment size in bytes. When size is not specified, the
current values of the TCP parameters, including the SMSS, are displayed.
A small SMSS causes the remote to reduce its segment size. tcp mss can reduce the MSS and
S on bad network connections with high loss rates or where large packets get lost.
SMS
Example
tcp smss 512
tcp window sub-command
tcp window displays or sets the default and maximum receive window size.
When specified without the size parameter the current TCP parameters, including the current
window size, are displayed.
Example
tcp window 2920
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 64
54 Radio PC Card Configuration
tcp timemax sub-command
tcp timemax sets the maximum duration of a tcp retry. If a value greater than 255 seconds is
specified, connections will never timeout.
This is very useful in wireless applications where nodes roam in and out of service.
Example
tcp timemax 2000ms
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 65
RF Throughput, Performance and Troubleshooting 55
RF Throughput, Performance and Troubleshooting
Because of the complicated nature of wireless LAN technology, problems occasionally arise. This
section provides general information about performance and addresses some problems that might
arise during setup or use of a wireless network with RF units. This should be your first resource in
case of trouble.
Power Management at the Proxim RangeLAN2 Access Point
Proper setup of the access point (AP) is essential to RF power management. Even with the MX2
set up for maximum power savings, the batteries can become drained quickly if the AP is not
configured properly.
MU Access Control
For environments in which multiple RF networks overlap, you can use an authorization table to
prevent RangeLAN2 APs from accessing RF cards on other networks. This list contains media
access control (MAC) addresses of mobile units that are allowed to associate with the AP.
See the AP user’s guide for more information about MAC addresses and for information about the
authorization table.
Message Filtering
Network packets include a protocol type (IPX, IP, ARP broadcast, NetBIOS, etc.) in the header
field. By filtering out unwanted protocol messages, you can prevent the AP from sending these
packets to the MX2. This will reduce the amount of times the radio cards have to wake up out of
doze mode to service incoming packets.
It can be especially important to filter out broadcast messages. These types of packets, which are
generically addressed to all computers on a system, may force the MX2 to operate continuously in
full receive mode, even when the data is not relevant to the MX2. If the MX2 does not turn off
automatically after the preset timeout, it is an indication that the radio card is receiving broadcast
messages and is unable to go to sleep.
The Proxim AP user interface for filtering packets allows you to select the type of packets that
will be filtered by selecting from a list of possible types. The best method with the Proxim
RangeLAN2 access point is to turn on filtering for every packet type that you know you won’t
use. For example, if the access point is hooked up to a TCP/IP network, you would set TCP/IP to
Not Filtering and all other protocols to Filtering. In a NetBEUI environment, turn off the Filter
NetBEUI option, and turn filtering on for all the rest of the protocols. ARP Broadcast packets
should always be turned off, unless your application requires them, to prevent broadcast messages
from waking up the MX2.
Note: For more information on packet filtering, see the RangeLAN2 access point manual or
your network administrator.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 66
56 RF Throughput, Performance and Troubleshooting
Site Survey
Many companies have an existing Ethernet or wired LAN infrastructure and want to be able to
extend that capability to wireless nodes. This is accomplished by attaching an access point to the
wired LAN, allowing the wireless clients to access the network resources.
MX2s, like other 386-compatible DOS computers, can be connected to networks. With RF
models, radio signals between the MX2s and the AP replace the wires connecting the nodes to the
network.
A site survey is an important part of setting up a wireless network. Contact your LXE
representative.
For most office environments, a site survey is not necessary. For large, industrial environments
requiring multiple APs, however, you should perform a site survey before installing a
RangeLAN2 network system. Run Proxim’s RL2SETUP.EXE
RangeLAN2 card.
The purpose of a site survey is to calculate the most effective number of access points at a site and
the best placement and positioning of antennas for optimal reception of radio signals. This is done
by identifying areas where transmission failures occur. As each site is unique, the surveyor needs
to consider the exact conditions, as they will appear in the final installation. In addition to such
climate factors as moisture, excessive heat, and dust, a site survey can also be affected by physical
obstructions and electromagnetic interference. Also important is the identification of potential
cabling, connector, or power problems.
program on a laptop using a
Throughput and Performance
The bandwidth on a radio network is constant for a given network. Therefore, the more active RF
units using the same frequency- hopping pattern, the slower the throughput of any one unit. If this
is a problem, you should install additional access points.
Radio signals may reflect off some obstacles and be absorbed by others. An RF unit with an
unobstructed line of sight to the access point antenna can successfully transmit and receive signals
at distances up to 1000 feet. In an environment that includes such obstructions as cubicle walls
typically used in modern offices, the range is reduced significantly, with a maximum distance of
500 feet. Where signals must penetrate office walls, the maximum distance may be only 300 feet.
Many other factors also affect performance of wireless LANs, including the following:
• Transmitter power
• Receiver sensitivity
• Interference caused by noise, receiver desensitization, spurious responses, and
intermodulation
• Shadowing
• Multipath fading
• Consumer products in use in the coverage area
Some of these factors can be sensed during a site survey and be avoided.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 67
RF Throughput, Performance and Troubleshooting 57
Operational Problems
This section lists solutions to problems that can occur with an RF unit.
The drivers won’t load, or the unit locks up when the drivers load.
Be sure the RangeLAN2 PC card is correctly installed in the radio card slot before turning the unit
on. Do not remove or insert any PC card while the MX2 is on.
The MX2 seems to lock up for four or five seconds after it is turned on.
Every time a MX2 is turned on, it must initialize the PC card. Wireless LAN PC cards commonly
take four or five seconds to initialize. After the card is initialized, the unit should function
normally.
The MX2 cannot communicate with a NetWare server.
The MX2 and the server may be using different frame types. Make sure that the frame type in
your NET.CFG file matches the server’s frame type.
The MX2 cannot communicate with another machine on the network.
The MX2 may not have the same domain and security ID as the other machine.
The MX2 does not shut down properly when I remove the PC card or take out the
batteries.
Do not remove a PC card or the batteries while the MX2 is on or immediately after turning it off.
When you turn the unit off, it suspends the RF driver, a process that can take one or two seconds.
If you remove the PC card or the batteries before the driver is suspended, the unit may be left in
an unstable state and may need to be reset.
The MX2 never turns itself off automatically, even when the time-out value is
correctly set.
The radio may be receiving broadcast messages from the access point. See “Power Management at
the RangeLAN2 Access Point”, for information on filtering messages.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 68
58 RF Throughput, Performance and Troubleshooting
Problems with DOS Drivers
Some problems may occur in the DOS environment. Many problems can be caused by
inappropriate memory, I/O, or IRQ settings for the MX2. If changing those settings in the
NET.CFG file doesn’t solve the problem, consult the following list of symptoms to identify other
possible causes. Contact your systems administrator if you need additional help.
ODI driver does not install or does not work
• Memory range not reserved
• Incompatible protocol manager and stack
• Improper linking in NET.CFG file
• Memory, I/O, or IRQ setup conflicts with other installed software and hardware
TCP/IP fails
• Incorrect IP/subnet address
• Incorrect domain; check for MU association
Nothing happens after installation of the network software (no login, cannot find
server, no TCP connection)
• Incompatible firmware and driver versions
• Memory, I/O, or IRQ setup conflicts with other installed software or hardware
• MU is out of range
• All cards must have matching security IDs to communicate
Slow or erratic performance
• Out of communication range
• Faulty antenna, antenna connector, or cable
Driver does not install, or driver hangs during installation
• Incompatible firmware and driver versions
• Memory range not reserved
• Memory range does not match setting in NET.CFG file
• Memory range is too small (use I/O mode if memory is restricted)
• Memory, I/O, or IRQ setup conflicts with other installed software or hardware
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 69
Introduction
This chapter details the default contents of the disk drives and the organization of system software
on the MX2. It also includes descriptions of two standard software configurations.
BIOS and DOS
The MX2 uses a modified version of General Software’s BIOS with Datalight’s ROM-DOS. Both
products are burned into system flash in a single 256K image. The A drive is included in the
image, physically addressed just below the BIOS image.
ROM-DOS uses the Datalight command.com processor. This processor is fully Microsoft 6.2
compatible, except that it occupies about half the space in memory. In addition, drive C contains
Datalight DOS files in a DOS subdirectory.
Chapter 3 Software Configuration
DOS Key Functions Not Supported on the MX2
Prnt Scrn A function that is available at the DOS prompt on a desktop PC. The Prnt Scrn as a
system function requires a parallel port and the MX2 has only serial ports.
Sys Req A function that is available at the DOS prompt on a desktop PC. Sys Req is for use in
a multi-tasking environment to switch between various running applications. The
MX2 is not a multi-tasking computer, nor is DOS in general considered a multitasking environment.
PC Card and RF Networking Software
PC card device drivers and utilities as well as RF networking solutions are installed on drive C
(the flash drive).
• Default IRQ for PC card is 7.
• Default PC card COM port is COM 2.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 70
60 Disk Drives and Files
Disk Drives and Files
The MX2 has the following drive structure:
Drive A is a read-only flash drive. The contents of this drive cannot be changed.
Drive B is a read-only flash drive. (Normal operation will not require updating of this drive.)
Drive C is a resident flash disk drive that is accessed with the FLASHDSK.SYS device driver.
You can use this drive to store applications and data.
Drive D is a RAM disk accessed with the VDISK.SYS device driver. This drive can be used to
store applications as well as data. However, you should take great care in selecting files for this
drive. As with any RAM drive, its contents will be lost if power is removed.
Additional drives are mapped to ATA flash PC cards or to network drives via radio frequency
(RF).
This organization provides an easy-to-use, extensible system that allows a high degree of
performance, usability, and customization. The following sections more fully describe the
contents and intended uses of each of the MX2’s drives.
Drive A
Drive A is a disk image that is located in flash along with the BIOS and ROM-DOS. A read-only
drive, it is intended to remain secure throughout the life of the unit. Drive A contains the
following files:
AUTOEXEC.BAT the first file in the startup sequence
CONFIG.SAF the first file in the safe-boot sequence
CONFIG.SYS the first file in the boot sequence
REV.COM the utility that reports the firmware revision
The CONFIG.SYS and AUTOEXEC.BAT files contain only basic commands that the unit needs
to run correctly. Both files chain to their respective counterparts on the B drive, as described in the
next section.
The CONFIG.SAF file is used in the safe-boot sequence.
REM **************************************
REM Initial CONFIG.SYS file for
REM starting the system.
REM **************************************
NEWFILE = B:\CONFIG.SYS
Figure 3-1 CONFIG.SYS File on Drive A
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 71
Disk Drives and Files 61
@echo off
REM ****************************************
REM Initial AUTOEXEC.BAT file for
REM starting the system.
REM ****************************************
VER
PATH=A:\
B:\AUTOEXEC.BAT
Figure 3-2 AUTOEXEC.BAT File on Drive A
REM *********************************
REM Initial CONFIG.SYS for safe boot.
REM *********************************
NEWFILE = B:\CONFIG.SAF
Figure 3-3 CONFIG.SAF File on Drive A
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 72
62 Disk Drives and Files
Drive B
Drive B is a disk image that is located in flash. A read-only drive, it is intended to be used to store
mandatory utilities and initialize the boot process. During normal use this drive will not be
updated. Drive B has no subdirectories.
See Chapter 4, “Commands”, for ROM-DOS command syntax.
AUTOEXEC.BAT the second file in the startup sequence.
CFGDEV.SYS the system-parameter-configuration device driver.
CFGIO.EXE the utility for loading fonts and keypad layouts.
COMIO.COM the utility for redirecting input and output to the serial port.
COMMAND.COM the DOS shell.
CONFIG.SAF the second file in the safe-boot sequence.
CONFIG.SYS the second file in the boot sequence.
COREUPD.COM the utility that updates the firmware image.
DECODE.SYS the bar-code-decoding device driver.
FLASHDSK.SYS the resident flash disk device driver.
FORMAT.COM the disk-reformatting utility.
FUNCTEST.COM the functional test for system components.
HIMEM.SYS the device driver for accessing extended memory.
LD.BAT the batch file for RESPONSE.BAT processing.
LOCK.COM the utility for locking or unlocking the resident flash disk and RAM
disk.
ORGANIZE.COM the utility for reorganizing flash disk data.
PM.COM the power-management utility.
REV.COM the utility that reports the firmware version.
UMBLINK.EXE the device driver for accessing upper memory blocks.
VDISK.SYS the RAM-disk device driver.
The CONFIG.SYS file will load the FLASHDSK.SYS driver to create the C drive and the
VDISK.SYS driver to create the D drive. It will then load DECODE.SYS and CFGDEV.SYS
before chaining to its counterpart on drive C. The AUTOEXEC.BAT file will chain to its
counterpart on drive C, except during a safe boot.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 73
Disk Drives and Files 63
The purpose of the CONFIG.SAF file is to provide a minimal boot configuration that preserves
the flash and RAM drives. When the safe-boot sequence is initiated, the CONFIG.SAF file is
processed instead of the CONFIG.SYS file. This prevents chaining into the drive-C initialization
files by omitting the NEWFILE = C:\CONFIG.SYS command. It also eliminates the loading of
the DECODE.SYS and CFGDEV.SYS drivers.
REM ****************************************
REM Standard CONFIG.SYS for building system.
REM ****************************************
REM ***************************
REM Create flash and RAM drives
REM ***************************
DEVICE = B:\FLASHDSK.SYS 4096
DEVICE = B:=VDISK.SYS 4096 /e
REM *********************************
REM Load decode/configuration drivers
REM *********************************
DEVICE = B:\DECODE.SYS
DEVICE = B:\CFGDEV.SYS
NEWFILE = C:\CONFIG.SYS
Figure 3-4 CONFIG.SYS File on Drive B
@echo off
REM ***********************************
REM Standard AUTOEXEC.BAT for
REM starting system.
REM ***********************************
PATH=%PATH%;B:\
C:
IF EXIST A:\CONFIG.SAF
IF EXIST C:\AUTOEXEC.BAT C:\AUTOEXEC.BAT
Figure 3-5 AUTOEXEC.BAT File on Drive B
REM **********************************
REM Standard CONFIG.SYS for safe boot.
REM **********************************
REM ****************************
REM Recover flash and RAM drives
REM ****************************
DEVICE = B:\FLASHDSK.SYS 4096
DEVICE = B:\VDISK.SYS 4096 /e
Figure 3-6 CONFIG.SAF File on Drive B
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 74
64 Disk Drives and Files
Drive C
Drive C is a resident flash disk drive that is accessed via the FLASHDSK.SYS device driver. By
default, this drive is configured to have full read and write access. The default CONFIG.SYS and
AUTOEXEC.BAT files reside here. You can modify these files to customize the system for an
application. They will be called after the CONFIG.SYS and AUTOEXEC.BAT files on drives A
and B are processed.
By default, this software is installed on the C drive. If the unit is intended to be used with PC
cards, then the Phoenix PC card drivers are installed in the PCM subdirectory on the C drive, and
the proper entries will be transferred into the CONFIG.SYS and AUTOEXEC.BAT files. The
exact configuration of files and the contents of the CONFIG.SYS and AUTOEXEC.BAT files
will change according to the configuration of the unit.
For RF capability, additional files for network connectivity would be required. These might
include a TELNET program or peer-to-peer networking tools, depending on what you choose to
install.
If something happens to a unit and data integrity becomes questionable, use the CHKDSK utility
to detect and correct errors on drive C. You can also use ORGANIZE.COM (on Drive C in the
MX2) to recover unused sectors.
See Chapter 4, “Commands”, for ROM-DOS command syntax.
Root Directory Files
AUTOEXEC.BAT Called after the AUTOEXEC.BAT files on drives A and B are
CONFIG.SYS Called after the CONFIG.SYS files on drives A and B are processed.
DOS Directory Files
See Chapter 4 “Commands” for function descriptions of the following files:
ANSI.SYS MODE.COM
CHKDSK.COM NED.CFG
CHOICE.COM NED.EXE
COMMAND.COM REMDISK.EXE
FORMAT.COM REMSERV.EX
MEM.EXE REV.BAT
processed.
E
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 75
Disk Drives and Files 65
PCM Directory Files
CNFIGNAM.EXE Specifies which PCM Plus configuration parameters are to be used,
based on the selected boot configuration.
PCM.INI Defines system resource requirements for all boot configurations which
contain PCM Plus. When a boot configuration is specified,
CNFIGNAM identifies the selection as CONFIG.SYS is loaded and
requests the relevant configuration information from the PCM.INI file.
PCMATA.SYS Device driver enables the system to access ATA-configured PC cards
as IDE hard drive devices using an IDE partition table.
PCMCS.EXE Must be loaded directly after Socket Services. Coordinates access to the
PC cards and allocates PC system resources among client drivers.
PCMSS400.EXE PCM socket services are located in this driver. The purpose of socket
services is to provide a layer of software support to the actual PC
hardware that controls PC-compatible sockets for PC cards.
Agent Directory Files
The SNMP agent files are loaded on MX2’s with a 2.4GHz radio.
AGENT.EXE Diagnostic agent. Provides limited access to the LXE Private MIB.
CFGAGENT.EXE Configuration agent. Provides full access to the LXE Private MIB.
REV.BAT Displays current revision level.
RFPARSE.EXE Used by PCRFLIB to obtain configuration settings. May or may not be
Terminal Emulation Files
Some MX2’s do not have terminal emulation (TE) files and may or may not have a radio card.
When a need exists to convert the unit to a TE unit or a different radio card, contact LXE
Customer Services for assistance.
Following are the directory names containing the TE program files:
Please refer to the “SNMP Agent Reference Guide” and “Client Configuration
Manager Reference Guide” for more details on the SNMP agent. Please refer to the
following section titled “Avalanche” when Avalanche is installed.
present.
Please refer to the specific Terminal Emulation’s reference guide for complete
instructions.
\APLUS ANSI Plus with 2.4 GHz radio
\IBM24 TN3270 with 2.4 GHz radio
\IBM24 TN5250 with 2.4 GHz radio
Note: Dual Terminal Emulation (Dual TE) is not supported on this device.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 76
66 Disk Drives and Files
TE Selection Menu
The TE Selection menu is generally not displayed on an MX2 computer since dual TE’s are not
supported. However, the TE Selection Menu may also be used to display multiple Autologin
hosts for some TE’s. Please refer to the appropriate terminal emulation reference guide and the
“DOS Autoconfigurator Instructions” for more details.
Menu Customization
The system administrator may change almost every facet of the menu display by modifying the
variables found at the top of TESELECT.BAT. Details on modifying the TESLECT.BAT file are
included in the “DOS Autoconfigurator Instructions”.
Drive D
Drive D is a RAM disk drive. By default, this drive resides in extended memory and is sized 1MB
less than the total RAM in the unit.
Drive D can be used for short-term data storage. Programs that need to be loaded into memory
and then removed from memory quickly can also be located there. The drive can also be used for
scratch disk space or temporary files.
The MX2 preserves the data on drive D between warm or cold boots by checking for an existing
RAM disk. However, only minimal checking is performed on any disk that is found. If something
happens to a unit and data integrity becomes questionable, you should use the CHKDSK utility to
detect and correct errors on drive D.
Drive E
Drive E is the ATA flash card. The PC card looks like a hard disk drive to the operating system
and the user. More flexible than flash disk drive C, it can be used for safer and more permanent
bulk storage of batch data than the RAM disk (drive D). This drive exists only on systems
configured to use ATA flash cards.
Drive E could also be a peer-to-peer or client-server network drive that is accessed through an RF
or Ethernet network card link. This option allows the developer to make many network drives
(drives E, F, etc.) available to applications.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 77
System Configurations 67
System Configurations
Several configurations are possible for the system software on the unit, depending upon the type
of hardware that is to be supported. Two standard configurations are described below, along with
directory structures and default CONFIG.SYS and AUTOEXEC.BAT file descriptions.
Default Configuration
The data files will be stored on drive D. PC card drivers able to support ATA cards will be loaded.
FILES = 30
REM -------------------------------REM Phoenix Card and Socket
REM services for accessing PC Cards
REM -------------------------------device = c:\pcm\cnfignam.exe /NORMAL
device = c:\pcm\pcmssit.exe
device = c:\pcm\pcmcs.exe
device = c:\pcm\pcmata.sys
Figure 3-7 CONFIG.SYS File on Drive C for Default Configuration
REM -------------------------------------REM The following lines set up
REM default parameters for some
REM environment variables. These lines
REM may be modified or overridden in
REM the USER section below.
REM -------------------------------------set prompt=$p$g
set dircmd=/ogn /p
REM -------------------------------------REM The following section is for
REM customized user entries.
REM Insert user-specific options and
REM commands here.
REM --------------------------------------
REM -------------------------------------REM The following lines add system
REM components to the PATH
REM and run the main application
REM executable, if one was specified.
REM --------------------------------------
IF EXIST c:\bparams.ini copy c:\bparams.ini PARAMS
set path=c:\;c:\dos;%path%
Figure 3-8 AUTOEXEC.BAT File on Drive C for Default Configuration
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 78
68 System Configurations
I/O PC Card Support Configuration
The CONFIG.SYS and AUTOEXEC.BAT files below were created by eliminating ATA card
support and adding I/O card support to DEFAULT.CFG.
FILES = 30
REM -----------------------------------REM Phoenix Card and Socket services
REM for accessing PC Cards
REM -----------------------------------device = c:\pcm\cnfignam.exe /NORMAL
device = c:\pcm\pcmssit.exe
device = c:\pcm\pcmcs.exe
device = c:\pcm\pcmscd.exe
Figure 3-9 CONFIG.SYS File on Drive C for I/O PC Card Support
REM ------------------------------------REM The following lines set up default
REM parameters for some environment
REM variables. These lines may be
REM modified or overridden in the USER
REM section below.
REM ------------------------------------set prompt=$p$g
set dircmd=/ogn /p
REM ------------------------------------REM The following section is for
REM customized user entries.
REM Insert user-specific options and
REM commands here.
REM ------------------------------------REM The following lines add system
REM components to the PATH and runs the
REM main application executable, if one
REM was specified.
REM -------------------------------------
IF EXIST c:\bparams.ini copy c:\bparams.ini PARAMS
set path=c:\;c:\dos;%path%
Figure 3-10 AUTOEXEC.BAT File on Drive C for I/O Card Support
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 79
Data Entry 69
Data Entry
Note: The MX2 will not run Microsoft® Windows® products i.e. Windows 3.1, Windows For
Workgroups, Windows 95, Windows NT, etcetera.
The LXE MX2 computer accepts data entry from the keyboard, barcode scanner and the Infrared
input port when an LXE Terminal Emulation (TE) program is running and on batch (non-TE)
units.
Keyboard Data Entry
Once the terminal emulation program is started, data can be entered with the MX2 keypad. Keyed
data can be entered into a data field and transmitted to the host. You might respond to a prompt
sent by the host application with a keypad entry, such as a menu listing choices for your next
action.
Barcode Data Entry
The MX2 supports data entry using the barcode scanner at the top of the unit. Keyboard data
entries can be mixed with barcode data entries.
Infrared Port Data Entry
The MX2 accepts input from the IR port. The MX2 processes data from the IR port the same way
it processes keyed data. The data is entered at the cursor position, and the data is subject to all of
the barcode/RS-232 input menu parameters, such as truncate.
Terminal Emulation
Note: Narrowband and spread spectrum 900MHz radios are not supported at this time. For
details concerning future capabilities, contact the LXE Product Marketing department.
All terminal emulation radio controlled data flows and exchanges are over the radio to the 64XX
or 65XX units, then to the computer network and then to a host computer. The LXE Network
Management System, as part of the wired network, can remotely configure the MX2’s terminal
emulation parameters.
Note: MX2’s with 64XX series 2.4GHz spread spectrum radios communicate only with 64XX
Access Points with installed 64XX 2.4GHz radios.
Note: MX2’s with 65XX series 2.4GHz spread spectrum radios communicate only with 65XX
Access Points with installed 65XX 2.4GHz radios.
Please refer to the system specific terminal emulation reference guide for instruction when using a
MX2 in a specific TE environment. A list of LXE reference guides is located at the end of Chapter
1 “Introduction and Specifications” in the section titled “Manuals”.
LXE’s terminal emulation programs that are compatible with the MX2 computer are:
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 80
70 Data Entry
ANSI Plus
Running on a MX2 with a 2.4GHz radio. ANSI Plus uses a Telnet connection to communicate
with the host computer. A MX2 with a 2.4GHz radio is interfaced to a computer network
(Ethernet or Token-Ring) via 2.4GHz radio equipped Access Points. ANSI Plus does not support
Narrowband RF.
TN3270 TE and TN5250 TE
Runs on a MX2 with a 2.4GHz radio. The TE provides IBM host application support over the RF
backbone and TCP/IP network. This product does not provide interconnectivity for LXE’s
narrowband and 900MHz RF backbones.
DOS TE User Defined Stored Forms
DOS terminal emulations have the following space requirements for user defined stored forms:
ANSI Plus 2K required for each form
TN3270 1K required for each form
TN5250 1K required for each form
DOS TE Font Sizes
MX2 screen sizes available at the DOS prompt are:
Please refer to the appropriate terminal emulation reference guides for technical information about
the terminal emulations and supported screen sizes.
• 8 rows by 16 columns
• 8 rows by 20 columns
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 81
Sample NET.CFG and SOCKET.CFG Files 71
Sample NET.CFG and SOCKET.CFG Files
Note: The examples provided throughout this section are for illustration purposes only.
Note: If the device is configured to use Avalanche for network settings, manual changes made
to NET.CFG and SOCKET.CFG may be overwritten.
Note: The Symbol FHSS radios are obsolete (6/2005).
Sample NET.CFG Files
Note: Hex values are indicated with a leading 0x. NET.CFG values do not use the 0x.
See Chapter 2 “Using Advanced Features” for explanations of NET.CFG parameters.
Lucent Radio NET.CFG File
Link Support
buffers 4 1550
Protocol ODIPKT
Bind WVLAN43
Link Driver WVLAN43
FRAME ETHERNET_II
WaveLAN_Network_Name ANY
Station_Name "station_name"
AP_Distance 1
Microwave_Robustness = N
Transmit_Rate 3
Medium_Reservation 2347
Card_Power_Management 1
Maximum_Sleep_Duration 100
Receive_All_Multicasts N
Enable_Encryption N
Proxim Radio NET.CFG File
Link Support
BUFFERS 2 1550
Protocol ODIPKT
BIND RL2PCM
;IP address is maintained in the socket.cfg file
Link Driver RL2PCM
Socket A
Initialize_365 N
Int 3
Mem #1 C100
Port 300
Inactivity_Min 0
Inactivity_Sec 1
Sniff_Time 0
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 82
72 Sample NET.CFG and SOCKET.CFG Files
Domain 0 ; set per customer settings
Station_Type 0
Peer_To_Peer N
Roam_Config 1
Mac_Optimize 1
Channel 1
SubChannel 1
Frame Ethernet_II
; Frame Ethernet_802.2
; Frame Ethernet_802.3
Cisco Radio NET.CFG File
Link Support
BUFFERS 4 1550
Protocol ODIPKT
Bind CSCODI (Use AWCO48C with Cisco 340 radios only)
file handles=60
LINK DRIVER CSCODI (Use AWCO48C with Cisco 340 radios only)
;Initialization file for Infrastructure
;operating mode
SSID "" ;must match Access Point setting
;FragThreshold 2312 ;packet size to start fragmenting
;RTSThreshold 2312 ;packet size to start sending RTS/CTS
;DataRate1 0x02 ;(1) Mbps supported data bit rate
;DataRate2 0x04 ;(2) Mbps supported data bit rate
;DataRate3 0x0B ;(5.5) Mbps supported data bit rate
;DataRate4 0x16 ;(11) Mbps supported data bit rate
;RefreshInterval 10000 ;inactivity time to check association
;PowerSaveMode "FastPSP" ;Fast Power Save Mode
;MaxPowerSave "ON" ;Maximum power save mode
;NodeName " " ;descriptive station name
;authtype "wepopen" ;Set WEP key in radio before wepopen
;setting for MX2 = right
;diversity "on" ; units with 2 antennas
;diversity "left" ; units with 1 antenna
;diversity "right" ; units with 1 antenna
PortBase 100
; IRQ 5
Memory C0000
;Socket 0
BusType "PCMCIA"
Frame ETHERNET_II
; Frame ETHERNET_802.3
; Frame ETHERNET_802.2
protocol IPX 0 ETHERNET_II
show dots=on
; following lines are for Cisco 350 radios only with LEAP
LEAP "OFF" ;LEAP authentication (OFF or ON)
WorldMode "OFF" ;World mode (OFF or ON)
ShortPreamble 0 ;PLCP short preamble (0=auto, 1=long, 2=short)
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 83
Sample NET.CFG and SOCKET.CFG Files 73
Symbol 2Mb Radio NET.CFG File
See Chapter 2 “Using Advanced Features “ for explanations of NET.CFG parameters.
; IMPORTANT NOTE: commented lines must have a ; in column 1.
; Lines that are not commented out must have a space in column
; 1 and the parameter starts on column 2.
;
link support
buffers 4 1550
protocol odipkt
bind slaodi
link driver slaodi
frame ethernet_ii
ess_id “LXE”
pnp no
cardservices yes ; must load slainit before
socketservices yes ; slaodi to use CS&SS
mode io
ioaddress 340
memory C000
interrupt 3
; tx_rate 1
; tx_rate 2
; socket 2
powermgmt yes
beacon_alg 11 ; beacon is pertinent when using radios
without an access point.
beacon_minimum 1
beacon_maximum 10
;-----------------; The following keywords are used to enable and manage the
; 802.11 WEP Encryption
;
; Auth_Type can be either Open_System or Shared_Key for the MU,
; the MAP will support both Auth_Type settings at the same time.
; The MU will only associate with APs or MAPs that support it’s
; Auth_Type. The MAP will only allow MUs to associate if the MAP
; supports the Auth_Type of the MU.
; The default Auth_Type is Open_System.
;
; Encrypt_Key# (where # is 1, 2, 3, or 4) will update the 1st, 2nd,
; 3rd, or 4th key encryption key in the adapter, according to the
; value of #. The parameter to these Keywords is 5 pairs of hex
; digits([0-9,a-f,A-F]) in a string.
; DO NOT prefix each pair with 0x.
; The default keys for the MU match the default keys of the UAP
; and MAP.
;
; Encrypt_Key_ID indicates which key the adapter is to use for
; encrypting packets for transmission. The parameter is a decimal
; digit from 1 to 4.
; The default Encrypt_Key_ID is 1.
; Note: The key to be used to decrypt packets being received is
; contained in the received packet.
;-----------------; Auth_Type Open_System
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 84
74 Sample NET.CFG and SOCKET.CFG Files
; Auth_Type Shared_Key
; Encrypt_Key1 “xx xx xx xx xx”
; Encrypt_Key2 “xx xx xx xx xx”
; Encrypt_Key3 “xx xx xx xx xx”
; Encrypt_Key4 “xx xx xx xx xx”
; Encrypt_Key_ID n
link driver slainit
verbose yes
DynWindowRsrcs yes
Symbol 11Mb Radio NET.CFG File
See Chapter 2 “Using Advanced Features “ for explanations of NET.CFG parameters.
; 1. A semicolon as the first non blank character denotes a
; comment line.
; 2. Commented out parameter lines create the default setting.
; 3. Rate control only works with 2 Mbps (or greater) radios
; 4. Encryption controls only work with 2Mbps (or greater)
; radios
; 5. ESSID must be changed to reflect the local network.
link support
Buffers 4 1550
Protocol ODIPKT
Bind s11odi
link driver s11odi
frame ethernet_II
; frame ethernet_802.2
; The ESS_ID can be a string of 1 to 32 case sensitive characters.
ess_id 101
station_name
; Use the following keyword to specify rates at which the Adapter
; is allowed to operate. If no rates are specified, the Adapter
; will use all rates available on the radio. Regardless of what is
; specified, the radio will allow
; rates, i.e., 1, 2, 5.5, and 11 Mbps.
; Tx_Rate 1 (1 Mbps)
; Tx_Rate 2 (2 Mbps)
; Tx_Rate 5 (5.5 Mbps)
; Tx_Rate 11 (11 Mbps)
;
; Tx_Rate 1
; Tx_Rate 2
; Tx_Rate 5
; Tx_Rate 11
; Note: IO Mode is required if using Card/Socket Services
Mode IO
IOAddress 340
Memory C9000
Interrupt 5
either 1 and 2 Mbps or all four
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 85
Sample NET.CFG and SOCKET.CFG Files 75
; Set performance index to "1" for MX2. 0=CAM , 1=Power Management On
performance_index 1
; Set diversity to "Both" for two antennas and "A" for one antenna.
diversity A
; To enable WEP you must set Encrypt_Enable_Index to the number of the
; Encrypt_Key# to use and then set the encryption key to the same
; value as the AP is set for. Zero means No Encryption and is the
; default.
; For 128 bit encryption keys you must have 13 pairs of hex digits and
; 5 pairs of hex digits for 40 bit encryption.
; Encrypt_Enable_Index 0
; Encrypt_Key1 12 34 56 78 90 12 34 56 78 90 12 34 56
; Encrypt_Key2 12 34 12 34 12 34 12 34 12 34 12 34 12
; Encrypt_Key3 AB CD EF 12 34 56 78 90 AB CD EF 12 34
; Encrypt_Key4 12 34 56 78 12 34 56 78 12 34 56 78 12
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 86
76 Sample NET.CFG and SOCKET.CFG Files
Sample SOCKET.CFG File
See Chapter 2 “Using Advanced Features “ for explanations of SOCKET.CFG
parameters.
Note: The values for some parameters are dependent on the type of radio card installed.
Please refer to Chapter 2, “Using Advanced Features” for appropriate values for a
specific radio card.
Note: If the device is configured to use Avalanche for network settings, manual changes made
to NET.CFG and SOCKET.CFG may be overwritten.
# Socket.cfg sets the options for Data Light socketp.exe
# The section xxx.xxx.xxx.xxx is for this machines IP
# The net mask is specified as part of the ip address.
# In the ip address command an optional /net_bits can be
# used to indicate the number of bits in the network ID.
# Net Bits Net Mask Class IP address range
# 8 255.0.0.0 A 0.x.x.x to 127.x.x.x
# 16 255.255.0.0 B 128.x.x.x to 191.x.x.x
# 24 255.255.255.0 C 192.x.x.x or higher
# The network can be subdivided by two for every net bit added.
# Net Bits Net Mask Net Bits Net Mask
# 1 128 5 248
# 2 192 6 252
# 3 224 7 254
# 4 240 8 255
# To enable DHCP set the IP address to 0.0.0.1
IP address 0.0.0.1/16
# The ARP INIT parameter makes this stack the same as
# before. The stack will not send a DHCP ARP (DEFAULT) when
# booting up. For added IP address checking you may comment
# this line out if you are NOT using proxy ARP.
ARP INIT GRAT
# Interface sets the physical interfaces
# pdr=packet driver
# if0=interface_card
# dix=frame type
# 1500=MTU
# 10=Buffers
# 0x69=ioaddr
Interface pdr if0 dix 1500 10 0x69
# When using a gateway (IP router) to the rest of the world,
# replace "XXX.XXX.XXX.XXX" with your gateway ip and
# remove the # at the beginning of the line.
# route add default if0 XXX.XXX.XXX.XXX
# When using a domain name server (DNS),
# replace XXX.XXX.XXX.XXX with the IP address of the DNS,
# and remove the # at the beginning
# of the line
# domain server XXX.XXX.XXX.XXX
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 87
SNMP DOS Agent 77
# domain suffix # example lxe.com
# Redisplay IP information
IP address
# options, refer to documentation to change
ip ttl 15
tcp mss 1360
tcp window 2920
tcp retry 8
tcp irtt 500ms
Note: The 2.4GHz radio drivers require a file called odipkt.com which utilizes software
interrupt 69. The corresponding line in the AUTOEXEC.BAT file will be:
c:\pctcp\odipkt.com 0 0x69
SNMP DOS Agent
The SNMP DOS agent resides in the C:\AGENT directory of mobile computers. By default, the
agent is placed into memory as a TSR and uses approximately <50k of memory. When the agent
is not being polled, it is invisible to the user. When it is being polled, there is a slight delay,
depending on how much data is being retrieved by the agent.
For information on disabling the SNMP DOS agent, please refer to the “DOS
Autoconfigurator Instructions”.
For more information on agent operation, please refer to the “SNMP Agent
Reference Guide” and “Client Configuration Manager Reference Guide”.
These manuals are available on the LXE Manuals CD.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 88
78 Avalanche
Avalanche
Note: Wavelink Avalanche is not designed to run on a device with a 900MHz or Narrowband
radio.
Note: If the device is configured to use Avalanche for network settings, manual changes made
to NET.CFG and SOCKET.CFG may be overwritten.
Avalanche may or may not be installed on your mobile device. Refer to this section for important
information relating to Avalanche running on an MX2 with a 2.4GHz radio. Contact your LXE
representative if Avalanche is needed and your mobile system has not been upgraded to the
required minimum software baseline revision levels. For complete instruction when using
Avalanche please refer to the “Wavelink Avalanche for DOS Reference Guide” on the LXE
Manuals CD.
Minimum Software Baseline
The minimum software revision level (baseline) must be loaded on the mobile device in order to
use Avalanche:
Operating System............................232XGSYS.02A
LXE Agent......................................AGNTGD00.01C
Core.................................................232XGCOR.01C
Avalanche Number .........................AVA2GD01.01A
Cisco 350 Radio Driver ..................C802GD35.01H
Lucent Radio Driver .......................L802GD01.01P
Symbol 4121 Radio Driver .............S802GD21.01E
Upgrading the MX2
If an LXE computer does not meet the minimum baselines specified above, it must be manually
upgraded to the baseline before it can be used with Avalanche. The older G-Number software
should be manually deleted from the LXE computer before the new G-Number is installed.
!
Directory Structure
The information in this section supplements the file information presented earlier in this chapter.
Software loaded on drive C:
Copying the new G-Number software to the LXE computer without first deleting the
old G-Number software may lead to insufficient disk space on the LXE computer.
This is especially important for LXE Agent, Radio and MX2 Core G-Numbers.
\AGENT Location of SNMP agent *
\APPS Location of files to track software revision levels
\AVA Location of files to support Avalanche
\DOS Location of ROM DOS *
\PCMCIA Location of PCMCIA files *
\PCTCP Location of radio configuration files *
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 89
Avalanche 79
\APLUS Location of optional TE files *
\IBM24 Location of optional TE files *
\LDS24 Location of optional TE files *
* Although Avalanche can be used to update the files contained in these directories,
the file structure is not changed by the addition of the Avalanche enablers.
\AGENT
When Avalanche enablers are installed, only the SNMP Diagnostic agent, AGENT.EXE is
installed. The configuration agent, CFGAGENT.EXE is not installed.
\AVA
This directory contains the Avalanche enablers and supporting files. Users must not make changes
to the contents of this directory.
When an updated enabler is loaded, it will change the contents of the \AVA directory. The boot
process checks for a newer version of the enabler before loading the enabler in the \AVA
directory. Since the MX2 has limited disk space, updates to the enabler on the MX2 replace the
original enabler files.
\APPS
This directory is used by Avalanche to track the revisions of software on the LXE DOS computer.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 90
80 Avalanche
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 91
Introduction
This chapter describes the Datalight ROM-DOS commands that are loaded in the MX2 by LXE.
The information in this chapter is taken from Datalight’s “ROM-DOS 6.22 User’s Guide” and is
used by permission.
ROM-DOS Commands
Each entry includes an explanation of the command’s purpose, the command entry syntax,
remarks, and examples. Where applicable, command syntax and parameters are given. Parameters
may be supplied using either uppercase or lowercase letters, and the hyphen (-) may be substituted
for the forward slash (/).
Each command also has a label to designate whether it is an internal or external command.
Internal commands are part of the command processor program, COMMAND.COM. These
functions are available only while COMMAND.COM is running. External commands are actually
stand-alone utility programs. They are independent from COMMAND.COM.
Chapter 4 Commands
ANSI.SYS
Type
Installable Device Driver
Purpose
ANSI.SYS is a console device driver that allows you to support ANSI codes on the local display.
Syntax
Device=ANSI.SYS [options]
Remarks
ANSI.SYS supports standard ANSI escape sequences.
ANSI.SYS writes directly the screen when using text video mode.
Options
The /K option forces use of the extended keyboard BIOS calls which sense F11 and F12.
The /X option lets you redefine the extended keys independently.
The /S option disables the keyboard redefinition feature.
The /Tnn option indicates that the video mode nn is a text mode. By default, modes 0, 1, 2, 3 and
7 are text modes.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 92
82 ROM-DOS Commands
Examples
DEVICE=ANSI.SYS
This example loads ANSI.SYS with default settings.
DEVICE=ANSI.SYS /T54 /S
Load ANSI.SYS with mode 54h as a video text mode and disable keyboard redefinition.
ATTRIB.EXE
Type
External
Purpose
The ATTRIB command either displays or modifies the attribute of a file.
Syntax
ATTRIB [+ ¦ -][option][filespec]
Remarks
The file attributes define the characteristics of a file. They determine if a file may be deleted or
modified, or if it is archived. The ATTRIB command is used to manage these file attributes.
Wildcard characters may be used in the ATTRIB filespec.
The ATTRIB command will modify file attributes if modify commands are given to ATTRIB.
The modify commands are:
Command Description
+/- Add(+) or remove(-) attribute
A Archive attribute
C Clear all attributes
H Hidden file attribute
R Read only attribute
S System file attribute
If no modify commands are found by ATTRIB, then the files are displayed along with the file
names and their current attributes.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 93
ROM-DOS Commands 83
Examples
ATTRIB will add the read-only attribute to the file myfile.dat.
ATTRIB +r myfile.dat
ATTRIB will remove the read-only attribute and the archive attribute for all files with the DAT
extension.
ATTRIB -a -r *.dat
ATTRIB will display the attributes of all files with the DAT extension.
ATTRIB *.dat
CHKDSK.EXE
Type
External
Purpose
The CHKDSK command checks the disk directories and File Allocation Table (FAT) and displays
a disk and memory report.
Syntax
CHKDSK [d:][path][filespec][/C] [/F] [/V]
Remarks
CHKDSK examines a disk and determines if the disk has any errors in the File Allocation Table
(FAT) and will optionally fix errors.
Options
The /F option causes CHKDSK to fix errors on the disk if any were found. The errors that can be
found are directory or FAT errors. If the /F is not specified then CHKDSK acts as if it will fix the
disk, but the corrections will not be written out to the disk.
If errors are detected, you will be prompted with a message similar to the following:
15 lost allocation units found in 5 chains.
Convert lost chains to files?
If you answer Y for Yes, each lost chain will be written to a file in the root directory of the current
default drive. Each file will have the name filennnn.chk. nnnn will be a sequential number. The
first chain will be in FILE000.CHK. These files can be verified to see if they contain valuable
information, and then deleted if desired. Answering N for No to the above prompt, CHKDSK will
still make the corrections however the lost chains will not be saved to the disk.
The /C option allows CHKDSK to correct errors without user confirmation. This option must be
used along with the /F option for corrections to be made.
The /V option causes CHKDSK to display each path and file as it is processed.
If a file specification is specified, then CHKDSK displays all files matching the specification that
have noncontiguous data areas on the disk. Files that are stored in noncontiguous areas, especially
.exe files, have slower disk access times. If CHKDSK reports a large number of files with this
problem, a utility program that optimizes the files and free space on your disk should be used.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 94
84 ROM-DOS Commands
After checking the disk, CHKDSK displays any error messages followed by a report on the state
of the disk that was checked. An example of the report is shown below.
Volume ROM-DOS created June 1,1990 1:00a
Volume Serial Number is 190E-4AA2
362496 bytes total disk space
0 bytes in 1 hidden files
6144 bytes in 2 user files
356352 bytes available on disk
655360 bytes total memory
595360 bytes free
CHKDSK does not wait for a disk to be inserted before the checking is initiated nor does it repair
any errors.
Examples
CHKDSK will check the integrity of drive A. The report will be printed to the console.
CHKDSK a:
CHKDSK will check the integrity of RAM disk D. The report will be saved in a file called
DRIVE_D.RPT.
CHKDSK d: >drive_d.rpt
COMMAND.COM
Type
External
Purpose
Start a new command processor.
Syntax
Remarks
This command starts a new copy of the ROM-DOS command processor. The command processor
is the program that has all the internal DOS commands in it.
Starting a new command processor will also produce a new environment. The size of the
environment is 128 bytes by default, but it can be changed using the /E switch.
Command and its arguments can also be used in a SHELL= statement in your config.sys file. See
the full description of SHELL for more details.
Options
The device option specifies that COMMAND.COM should use a different device, such as AUX,
for input and output.
COMMAND[device][/E:number][/K:filename][/P][/C string][/MSG]
The /E:number switch sets the environment size. Number represents the size of the environment
in bytes. Number must be in the range from 160 to 32768. All other values will be ignored and the
default value of 256 will be used. ROM-DOS will round the value entered up to the nearest
multiple of 16.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 95
ROM-DOS Commands 85
The /K:filename option tells the command processor to run the specified filename and then display
the ROM-DOS command prompt. It is not recommended that this option be used in a
CONFIG.SYS SHELL= statement.
The /P switch causes COMMAND not to exit, or in other words, to remain permanent. The /P
switch should be used only when command is used in a CONFIG.SYS SHELL statement.
The /c string switch causes COMMAND to execute the command in string and then terminate.
The string command can be any internal or external command.
The /MSG option indicates that all error messages should be stored in memory. This option is
recommended only for diskette based systems. ROM-DOS keeps many of its error messages in the
resident part of COMMAND.COM rather than using valuable memory to store them. If an error
message is needed and you have loaded ROM-DOS from a diskette, the message will only be
available if the boot disk is still in the drive. By using the /MSG option, the messages will be
available in memory at all times. The /P option must be used along with the /MSG option.
Examples
The following command will cause a new copy of COMMAND to be executed. It will perform a
DIR command on the C drive and then exit back to the previous Command Processor.
COMMAND /C DIR C:
The following example shows loading of a permanent copy of command with an environment size
of 256 bytes.
SHELL=C:\COMMAND.COM /P /E:256
DELTREE.EXE
External Command
The DELTREE command deletes one or more directory trees or individual files.
Syntax
Remarks
/Y prevents DELTREE from prompting before deleting.
[drive:]path indicates the name(s) of the file(s) or directory tree(s) to delete. Wildcards are
allowed.
Examples
Datalight DELTREE deletes one or more directory trees. For example, to delete all files and
directories in the tree C:\TEMP, enter
You can also use DELTREE to delete individual files, one at a time, using wildcards. For
example, to delete selected files in the current directory, enter
DELTREE then prompts you for each file it finds, allowing you to choose whether to delete them.
DELTREE [/Y] [drive:]path [[drive:]path[...]]
DELTREE C:\TEMP.
DELTREE *.*
Caution: Take care when using wildcards with DELTREE. DELTREE deletes all specified
files and subdirectories regardless of their attributes. Multiple files and/or
subdirectories may be specified.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 96
86 ROM-DOS Commands
FORMAT.COM
External Command
The FORMAT command initializes a disk so ROM-DOS can access files on that disk. A disk
must be formatted before ROM-DOS can use it.
Syntax
FORMAT [drive:] [/options]
Remarks
FORMAT initializes the disk and directory of the specified drive. The size of the formatted disk is
the largest possible size that the specified drive supports, unless a different size is specified via a
command line option.
Options
The /4 switch causes the floppy disk to be formatted as a 360KB disk even if the drive is a
1.44MB, 2.88MB, or 1.2MB drive.
The /7 switch causes the floppy disk to be formatted as a 720KB disk even if the drive is a
1.44MB or 2.88MB drive.
The /B option causes FORMAT to used BIOS Int 13h calls. By default, FORMAT checks the
DOS version, and if it is DOS 5.0 or higher, it uses the floppy device driver to do the format.
Using the /B option forces FORMAT to bypass the floppy or hard disk controller and use BIOS
calls. /B makes FORMAT device independent.
The /C switch causes FORMAT to format one disk without user input. The disk is assumed to be
in the specified drive, and FORMAT exits immediately when the format is complete. This switch
is useful in batch files or programs that require a formatted disk without user input.
The /F:size option specifies the size of the floppy disk to be formatted. Available size values are
360, 720, 1.2, 1.44, and 2.88, and are entered as /F:size. For example, /F:1.2.
The /H switch causes the system files not to be hidden or write-protected. This can be used along
with the /S option.
The /I option forces FORMAT to use IOCTL calls and never use BIOS calls. Normally,
FORMAT first tries to access the device driver IOCTL calls to format the disk. If this fails, BIOS
calls are used (unless the /B option is specified). BIOS calls are always used for DOS 3.3 and
earlier.
The /Q option causes FORMAT to do a quick format. A quick format reinitializes the disk,
deleting each file and subdirectory from the disk. A quick format can only be performed on a
previously fully formatted disk.
The /S switch causes FORMAT to copy the ROM-DOS system files, ROM-DOS.SYS and
COMMAND.COM, onto the disk. The file ROM-DOS.SYS is renamed and stored on the disk as
files IBMBIO.COM and IBMDOS.COM, which are stored as hidden files, unless the /H option is
used.
The /V:LABEL switch causes FORMAT to place a volume label on the disk. If the volume label is
not provided on the command line, you are prompted for the volume label once the format is
complete.
The /[ switch causes FORMAT to run without display of the sign-on message.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 97
ROM-DOS Commands 87
If FORMAT encounters an error, the exit code returned to DOS indicates the type of error. The
error codes are listed in the following table.
Error Level Type of Error
0 No error encountered
1 Invalid drive
2 Unsupported drive format
3 Attempted hard drive format (unsupported)
HIMEM.SYS
4 Write-protect error
Installable Device Driver
The HIMEM.SYS device driver manages extended memory and the High Memory Area (HMA)
in a 286, 386 or greater, or PS/2 systems. HIMEM prevents programs from simultaneously using
the same area of memory for two different purposes. HIMEM supports the Extended Memory
Specification (XMS) 2.0. HIMEM is installed as a device driver in CONFIG.SYS.
Syntax
DEVICE = [d:] [path] HIMEM.SYS [/machine:n] [/A20[+]] [/PS2]
[/CONTROLA20:OFF]
Remarks
The HIMEM driver can be used to allow ROM-DOS to run in High Memory.
HIMEM supports a default of 32 handles.
HIMEM should not be used with older versions of Datalight’s VDISK. Current versions of
VDISK use XMS memory if it is available.
HIMEM recognizes PS/2-style A20 line control and determines whether to use the PS/2 A20
control or the AT A20 control method automatically by calling Int 15h, function C0h (get system
configuration). This automatic detection can be overridden with the /Machine:n, /A20, A20+, or
/PS2 command line switches in the event that the auto detection on a given system fails.
/Machine:1 and /A20 both designate the PC AT A20 control method. These switches instruct
HIMEM not to wait for the A20 line to settle.
/Machine:2 and /PS2 both designate the PS/2 control method.
/A20+ is similar to /A20 but instructs HIMEM to wait for the A20 line to settle.
/Machine:3 designates support for the Phoenix Cascade BIOS A20 control methods.
Alternately, /CONTROLA20:OFF instructs HIMEM to not detect the control method for the A20
line and assumes the A20 line is always on.
The /BIOS switch forces the use of BIOS Int15h, Function 87h, for data transfers to and from
XMS memory.
The /QUIET switch forces HIMEM to remove the sign-on message when loading.
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 98
88 ROM-DOS Commands
Error Conditions
No Extended Memory—An extended memory error condition can occur if the BIOS (via Int
15H, function 88H) notifies HIMEM that there is no extended memory. In this situation, HIMEM
displays an appropriate error message and does not install.
Failure to Control the A20 Line—When HIMEM installs, it attempts to control the A20 line,
which controls access to the HMA. HIMEM first attempts control via the AT method (using the
8259 keyboard control). If that fails, HIMEM then attempts control via the PS/2 method (using
I/O port 60H). If both methods fail, HIMEM assumes it can’t control the A20 line and displays the
message
A20 Control (OFF)
If either of these errors occur, try using the /A20, /A20+, or /PS2 in the HIMEM command line.
Note also that some older programs assume that the machine is a 1MB 8086 and so require that
the A20 line to be disabled (OFF) while they run. Current programs typically do not require that
the A20 line be disabled.
Examples
Device = HIMEM.SYS
Installs the XMS device driver. Once this driver is installed, accessing the HMA and Extended
Memory (XMS) memory areas are legal. The Extended Memory area can contain up to 2GB of
memory. Typical systems have 4
Device = HIMEM.SYS /machine:1
, 8, or 16MB of XMS memory installed.
Forces the use of the AT-style A20 line control.
The HIMEM driver fails to load when either the machine does not have memory above the 1MB
boundary or the BIOS does not provide support for it. It also fails to load when another XMS
manager has been previously installed.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Page 99
ROM-DOS Commands 89
MEM.EXE
External Command
The MEM command displays the used and free memory in your system.
Syntax
MEM [/BiosExtensions] [/Classify] [/Raw]
Remarks
/B Displays each BIOS extension and its size.
/C Classifies the memory usage.
/R Does raw dump of the MCB chain.
MEM displays a list of the DOS memory contents, what free space is available, and how much
memory is in conventional memory, upper memory, the HMA and extended memory. This
program is useful to fine tune the system to have as much free memory as possible for
applications.
Options
The /B option displays BIOS extensions in the range from C000:0 to F800:0.
The /C option shows program, TSR, and device driver sizes.
The /R option shows a low-level DOS listing of MCBs (Memory Control Blocks).
E-EQ-MX2RG-L-ARC MX2 Reference Guide
Page 100
90 ROM-DOS Commands
MODE.COM
External Command
The MODE command modifies the operation of the printer, serial port, and active video display.
Syntax
MODE LPT#[:]=COM#[:]
MODE COM#:baud[,parity[,databits[,stopbits[,P]]]]
MODE <video mode>
MODE <display lines>
Remarks
The first syntax above redirects line printer output to the serial port.
The second syntax above changes the operation of the specified communications port. The options
that can be modified are listed below. InValid for any of the options are flagged with an error
message.
baud 110, 150, 300, 600, 1200, 2400, 4800, 9600
parity N - None, O - Odd, E - Even
databits Either 7 or 8
stopbits Either 1 or 2 stop bits
P Printer Port
Using the P option as the last argument causes output to be sent repeatedly to the printer port until
successfully received. Without the P, output is sent only once, causing a critical error if
unsuccessful.
The third syntax changes the active video mode for the display terminal. The valid choices for this
version of the MODE command are as follows:
40—Indicates 40 characters per line.
80—Indicates 80 characters per line.
bw40—For a color graphics adapter with color disabled and 40 characters per line.
bw80—For a color graphics adapter with color disabled and 80 characters per line.
co40—Indicates a color monitor with color enabled and 40 characters per line.
co80—Indicates a color monitor with color enabled and 80 characters per line.
mono—For a monochrome display. Assumes 80 characters per line.
The final syntax sets the number of display lines. Valid included L25, L43, and L50.
Note: A serial port should be initialized before an LPT device is redirected to it.
Examples
MODE COM1:9600,n,8,1
Modifies the settings for the COM1 device to a baud rate of 9600, no parity, eight data bits, and
one stop bit.
MODE LPT2:=COM2
Redirects the output from LPT2 to the COM2 serial port. All following output to LPT2 actually
goes to the COM2 device.
MODE mono
Indicates a monochrome display adapter.
MX2 Reference Guide E-EQ-MX2RG-L-ARC
Loading...