2-28 Radio PC Card Configuration
MX2 Reference Guide Revision A MX2A137REFGD
The PROTOCOL.2 file will be renamed PROTOCOL.INI
when it is saved on the MX2 drive.
4. Select the File Configuration button in the Custom Configuration
menu.
5. Select the Add button, and use the File Selection dialog box (see
screen displays in Chapter 4) to include the main application and
additional files in your custom installation. This should include the
TCP/IP package you want to load, as well as a protocol manager
(e.g., PROTMAN.SYS). Be sure to turn on the Main Application
switch for the application you want the MX2 to use.
6. Select the Next button at the bottom of the File Configuration
window.
7. In the second File Configuration window, make sure the Vendor
Specific option is selected. This option identifies which Phoenix
drivers to download.
Note: The I/O-card drivers are not compatible with
Proxim’s client driver. Do not select the I/O Cards
options when using RF.
8. Select the More button to verify that the DOS files you need are
included in the download. After viewing the file list and making any
necessary changes, return to the File Configuration window.
9. Select the NEXT button to move to the third File Configuration
window.
10. If you want to include commands to be executed in the
AUTOEXEC.BAT
file, select the AUTOEXEC.BAT button. Enter
the commands, and save the revised file before exiting from the text
editor.
Note: Verify that the drive and directories of any drivers
loaded in the AUTOEXEC.BAT file are correct. The
default PX_PKDRV.CFG file assumes these drivers
will go to a specific location on the MX2. If you
change the destination directory on the MX2 for these
files, be sure to change them here, too. The file that
you selected as the main application will
automatically be appended to the AUTOEXEC.BAT
file before it is downloaded to the MX2.
11. Select the CONFIG.SYS button, and verify that the drives and
directories specified for any device drivers in the CONFIG.SYS file
are correct. Be sure to include a line to load the protocol manager
(e.g., device=c:\net\protmen.sys /i:c:\net). By
default, NDIS TCP/IP drivers and programs are assumed to be in
