June 14, 1995
This README file describes the use of the New Media LAN Socket Services
configuration utility, NMSOCKET.EXE.
Contents:
1) Overview
2) Using NMSOCKET.EXE
3) Command Line Options
4) Changes to Network Configuration Files
5) Error Messages
----------------------------------------------------------------------------
Overview:
NMSOCKET can be used to configure the New Media Ethernet LAN card for
operation. In general, it is highly preferred that user's of the Ethernet
LAN card use the client driver, NMCENET.EXE, in conjunction with Card and
Socket Services, to configure the card. NMCENET.EXE allows full "hot
swappability" of the LAN card. In addition, the use of Card and Socket
Services helps to reduce hardware resource conflicts since Card and Socket
Services maintains control over the resources being used.
If you choose to use NMSOCKET.EXE to configure the LAN card,
the LAN card WILL NOT BE HOT SWAPPABLE. That is, the LAN card must be
inserted in the machine when NMSOCKET.EXE is run, and the card CANNOT
be extracted after running NMSOCKET.EXE. In additon, hardware resource
conflicts are far more likely when using an enabler program such as NMSOCKET.
Also, when using NMCENET.EXE, all Advanced Power Management (APM) will be
disabled for the Live Wire card. Any APM settings in your network
configuration file (NET.CFG or PROTOCOL.INI) will be ignored. In addition,
Live Wire message boxes will be disabled.
NMSOCKET.EXE requires that you load Socket Services software prior to
running the program. Note that NMSOCKET.EXE will NOT work if Card Services
is loaded. Only Socket Services should be loaded. For example, if using
SystemSoft CardSoft Card and Socket Services on your computer, you should
comment out the Card Services drivers, leaving only the Socket Services
driver, as shown below:
DEVICE=C:\CARDSOFT\SSxxxx.EXE
rem DEVICE=C:\CARDSOFT\CS.EXE
rem DEVICE=C:\CARDSOFT\CSALLOC.EXE C:\CARDSOFT\CSALLOC.INI
rem DEVICE=C:\CARDSOFT\ATADRV.EXE
rem DEVICE=C:\CARDSOFT\RAMDRV.EXE
rem DEVICE=C:\CARDSOFT\CARDID.EXE
where SSxxx.EXE is the Socket Services driver (SS365SL.EXE, SSDBOOK.EXE,
SSVADEM.EXE, or SSCIRRUS.EXE).
In addition, Socket Services can often be loaded as a TSR AFTER the system
has been started.
----------------------------------------------------------------------------
Using NMSOCKET.EXE:
NMSOCKET is an executable program which must be run prior to network binding.
That is, NMSOCKET.EXE must be run prior to the ODI LAN driver NMCETHR3.COM if
this is the driver in use. Alternatively, if using the NDIS driver,
NMETH3.DOS, NMSOCKET.EXE must be run prior to network startup commands such
as 'NET START', 'STARTNET.BAT', etc. These commands are typically placed in
the AUTOEXEC.BAT file by network software installation programs, so be sure
to run NMSOCKET.EXE prior to running them (for example, by adding NMSOCKET
to your AUTOEXEC.BAT file before the net startup commands). For example, if
using Novell NetWare, you should execute your network startup commands as
follows:
cd <NetWare Directory>
LSL
NMSOCKET [Options]
NMCETHR1
IPXODI
NETX
If using Windows for Workgroups, your AUTOEXEC.BAT may look like the
following:
cd <NMSOCKET Directory>
NMSOCKET [Options]
cd \
C:\WINDOWS\NET START
.
.
etc.
---------------------------------------------------------------------------
Command Line Options:
It is important to use the proper command line options when using
NMSOCKET.EXE. Often, NMSOCKET will not work correctly without the proper
command line switches.
Option Default Effect
__________________________________________________________________
/0, /1 0 PCMCIA slot number
/irq=x 5 IRQ level for the card.
Must be a HEX value 1-F
/port=xxx 300 Base port address for the
card
/mem=xx D0 Base memory window address
to be used by NMSOCKET.
The memory window is not
used by the LAN card after
being enabled by NMSOCKET.
/c=databook1 or OFF MUST be used if using
/c=databook2 SSDBOOK.EXE Socket Serv.
Often needed with DataBook
PCMCIA controller chips.
/v OFF Verbose mode. Use for
debug messages.
Note: there can be no spaces in the options statements. For example,
/irq=5 is correct,
/irq = 5 is NOT correct.
Examples:
1) NMSOCKET
- configures slot 0 for IRQ 5 and Port 300, using memory window at
base D000:0000.
2) NMSOCKET /1 /port=320 /irq=A
- configures slot 1 for IRQ A and port 320, using memory window at
base D000:0000.
3) NMSOCKET /c=databook1 /irq=9 /v /mem=d8
- configures Databook PCMCIA controller slot 0 for IRQ 9 and port 300,
using memory window at base D800:0000. Debug statements enabled
with /v switch.
----------------------------------------------------------------------------
Changes to Network Configuration files:
In order to use NMSOCKET as an enabler, the following lines MUST be in your
network configuration files. The following lines are in addition to the
standard lines in the configuration files. See the Live Wire Ethernet LAN
User's Manual for further description of the syntax of these parameters.
1) Config Address (NET.CFG) / CONFIG_ADDRESS (PROTOCOL.INI)
This line represents the LAN card's unique IEEE address programmed onto the
card. This line is added when you run the LAN card installation program
on the Ethernet LAN card distribution disk. In order to run the installation
program, BOTH Card and Socket Services must be loaded on the computer.
After running the installation program, "Remark" out the Card Services drivers
from CONFIG.SYS, leaving only the Socket Services driver. See above for
instructions on which drivers to leave in CONFIG.SYS.
2) Int (NET.CFG) / INTERRUPT (PROTOCOL.INI)
This line represents the IRQ level to be used by the card. This value MUST
match the value established by the NMSOCKET enabler. Note that this value
should be a DECIMAL value (e.g., 11, rather than a hex value, like B), whereas
the value used for NMSOCKET should be hex value, and NOT a decimal value.
3) Port (NET.CFG) / IOBASE (PROTOCOL.INI)
This line represents the base IO port to be usd by the LAN card. This value
MUST match the value established by the NMSOCKET enabler.
4) EXT ENABLE (NET.CFG) / EXT_ENABLE (PROTOCOL.INI)
This line MUST be in both NET.CFG and PROTOCOL.INI.
Example NMCETHR3.COM section in NET.CFG:
Link driver nmcethr3
Frame Ethernet_802.3
Port 300
Int 5
Config Address 00c0150002d0
EXT ENABLE
Example NMETH3.DOS section in PROTOCOL.INI:
[NMETH3]
DriverName=NMETH3$
IOBASE=0x300
INTERRUPT=5
CONFIG_ADDRESS=0x00,0xc0,0x15,0x00,0x02,0xd0
EXT_ENABLE=Yes
----------------------------------------------------------------------------
Error Messages:
If you receive the following error
ERROR: LAN socket configuration failed!
re-run NMSOCKET using the /v option. Using the /v option will generate
one of the follwoing error messages.
1) resetSocket: Socket Services Error: NO_CARD
This error indicates that you are trying to enable the wrong socket. Use the
/0 or /1 switch to enable the opposite socket.
2) setSocket: Socket Services Error: BAD_IRQ
This error indicates that the IRQ level being configured is invalid. This is
either due to an unavailable IRQ, or the use of a non-Hex value (e.g., 11,
rather the Hex value, B).
3) setWindow IO Base: Socket Services Error: BAD_BASE
This error indicates an invalid IO base address. Use the /port=xxx option to
try another value.
4) setWindow enable: Socket Services Error: BAD_BASE
This error indicates a base memory window base address. This can be caused
by Socket Services not allowing the use of a window, or the window being used
by another program. Try another window using the /mem=xx option, or make
sure the requested window is available by excluding the requested window
from use by memory manager programs, e.g.,
DEVICE=C:\DOS\EMM386.EXE NOEMS X=D000-DFFF
in CONFIG.SYS should allow the use of /mem=D0 by NMSOCKET.
5) ConfigOpt write failed!
This indicates that the memory window being used is invalid, probably because
another program occupies the memory range. Try another window using the
/mem=xx option, or make sure the requested window is available by excluding
the requested window from use by memory manager programs, e.g.,
DEVICE=C:\DOS\EMM386.EXE NOEMS X=D000-DFFF
in CONFIG.SYS should allow the use of /mem=D0 by NMSOCKET.
6) Socket Services not found, either load Socket Services or unload
Card Services
This error indicates that either Socket Services has not been loaded, or both
Card and Socket Services have been loaded. ONLY Socket Services should be
loaded if using NMSOCKET.
7) SSDBOOK.EXE / DataBook PCMCIA Controller
Also, remember, you MUST use the /c=databook1 or /c=databook2 switch if using
SSDBOOK.EXE Socket Services (SytemSoft). In addition, one of these switches
may be necessary if using another vendor's Socket Services on a computer
with a DataBook PCMCIA controller. If you do not use these switches,
NMSOCKET may complete successfully, but the LAN card may not function
properly.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.