| I was told by our DECndu guru that the PC-MCIA card is not yet supported by
DECndu. Apparently there is some problems with doing MOP loads of devices (e.g.
DECbridge 90 and DECagent 90) when using the PC-MCIA card. One person did
successfully load other DEChub 900 modules that use the TFTP mechanism, but it
looks like the PC-MCIA card has problems with MOP loads. I have no further
details on what the problem is or exactly what the fix is.
However, I was also told that a fix is in the works and should be ready soon
(like next week). If you would like to get on the notification list for this
update, please send mail to NETCAD::DJERBAKA (that's Paul Djerbaka).
...Roger...
|
| I thought it would be worthwhile to document the versions of the drivers that I
have successfully gotten to work on various systems with a variety of network
adapters.
The version of DECndu Plus for DOS is the one that is available on the network.
Use PKUNZIP.EXE to decompress the NDUPLUS.ZIP file, both located at:
NETCAD::PROJ$706:[NDU.V3.RELEASE.DOS.SSB]
The file README.NOW contains instructions for building a DOS diskette from which
to boot and run DECndu Plus.
The DECndu Plus executable file has the following attributes:
decndup.exe Size: 49,422 Date: 08-09-93 11:20a Version: V1.0
The following details the specific things that execute at startup for each of
the network adapters on which I have successfully run DECndup Plus. I have a
bootable 3.5" floppy which I transport between systems. This floppy contains
the files detailed below.
CONFIG.SYS
----------
shell=\command.com /P /E:526
device=protman.sys /I:A:\
device=<driver> ! See below
AUTOEXEC.BAT
------------
@echo off
break on
prompt $p$g
a:\dllndis
a:\netbind
The following is the details about the relevant network and driver files. For
all systems, these three files are common to all of them:
File Size Date & Time Version
----------- ------ --------------- ---------
DLLNDIS.EXE 8,915 05-04-92 8:47a v4.00.039
NETBIND.EXE 15,639 05-04-92 8:47a v1.1
PROTMAN.SYS 10,657 05-04-92 8:47a v1.1
For specific systems and network adapters, the following are the details of the
<driver> file name that should be substituted into the CONFIG.SYS file along
with a listing of the PROTOCOL.INI file.
System: DECstation 325 (desktop)
NIC: DEPCA
Driver: DEPCA.DOS Size: 15,577 Date: 05-04-92 8:47a Version: v1.13.005
PROTOCOL.INI
------------
[protocol manager]
DRIVERNAME = PROTMAN$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
MOP = 0
BINDINGS = DEPCA.DOS
[DEPCA.DOS]
DRIVERNAME = DEPCA$
-----------------------
System: DECpc 425SE (laptop)
NIC: DEPEA-B3
Driver: DEPEA.DOS Size: 52,442 Date: 01-25-94 9:45a Version: V1.61.000
PROTOCOL.INI
------------
[protocol manager]
DRIVERNAME = PROTMAN$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
MOP = 0
BINDINGS = DEPEA.DOS
[DEPEA.DOS]
DRIVERNAME = DEPEA$
PMODE = 3
DIAGNOSTIC = 1
-----------------------
System: DECpc 425SE (laptop)
NIC: XIRCOM PE2
Driver: PE2NDIS.EXE Size: 34,822 Date: 10-30-92 9:42a Version: V1.44
PROTOCOL.INI
------------
[protocol manager]
DRIVERNAME = PROTMAN$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
MOP = 0
BINDINGS = PE2NDIS.EXE
NI_IRQ = 7
[PE2NDIS.EXE]
DRIVERNAME = XIRCOM$
-----------------------
System: DECpc LPv 466d2 (desktop)
NIC: Etherworks III
Driver: EWRK3.DOS Size: 39,944 Date: 12-16-93 4:14p Version: V2.77.000
PROTOCOL.INI
------------
[protocol manager]
DRIVERNAME = PROTMAN$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
MOP = 0
BINDINGS = EWRK3.DOS
[EWRK3.DOS]
DRIVERNAME = EWRK3$
IOADDRESS = 0X300
RAMADDRESS = 0XD000
MEMORYMODE = 2
INTERRUPT = 5
-----------------------
And now for the big question:
"What if I have a different network adapter than one of the examples above?"
The best thing to do is to contact the adapter manufacturer to obtain the
latest driver. For DEC adapters, check the Pathworks repositories for drivers
which have shipped with Pathworks. These repositories may also contain
versions of PROTMAN.SYS, DLLNDIS.EXE and NETBIND.EXE which are compatible with
the driver. The following repositories are publicly available via a Pathworks
client on the network (File Manager -> Disk -> Connect Network Drive):
V4.1 \\jsbach\pcsav41
V5.0 \\lanmgr\pwv50
The files can be found under the \lmdos\drivers directory.
Then use the PROTOCOL.INI file for the DEPCA adapter above as a template,
substituting the correct file name in the BINDINGS line and between the square
brackets below it. Also specify a DRIVERNAME under this section. And don't
forget to substitute your driver name in the CONFIG.SYS file.
Now reboot and watch the fireworks.
I hope this helps in some small way.
...Roger...
|