Newsgroups: bit.listserv.3com-l
Date:         Mon, 31 Aug 1992 12:51:00 PDT
From:         Brian_Whittaker@3MAIL.3COM.COM
Subject:      Re: Help about Etherlink16 and NDIS....
X-To:         3COM-L@nusvm.BITNET, Joe@email.ncsc.navy.mil

FYI.................

==================================================================
FIX #1
Conrad writes:
> We want to install both LAN MANAGER and CU/TCP in the same PC, but we
> can't because of a number of errors and crashes of the DOS.
> -------------------------------------------------------------------------
----
>  Protocol.ini
>
> [PROTOCOL MANAGER]
>   DRIVERNAME = PROTMAN$
>
> [PKTDRV]
>   drivername = PKTDRV$
>   BINDINGS = ETHERLINK16
> ;  intvec = 0x60
*** You should probably uncomment out the above intvec line.  I use a
*** higher interrupt vector number to allow loading winpkt to load at a
*** lower interrupt but winpkt is only necessary for running Windows.
*** I'm not sure what the default interrupt is.
>
>  ; DLC Protocols
> [DLC]
>   DRIVERNAME = MDLC$
>   BINDINGS = ETHERLINK16
>   stations = 64
>   loopback = 4
>
> ; 3Com NETBIOS Protocol
> [NBP]
>   DRIVERNAME = NBP$
>   BINDINGS = ETHERLINK16
>   DEFAULTS = SERVER
***             ????  Huh? Is this the protocol.ini file from your
***                         server or do you just have it set this way
***                         to increase NBP resources available?
>
> ; 3Com 3C507 and 3C507TP
> [ETHERLINK16]
>   DRIVENAME = ELNK16$
>
> =============================
> config.sys
> =============================
>
> device=c:\dos\ansi.sys
> COUNTRY=039,437,C:\DOS\COUNTRY.SYS
> files=30
> STACKS=9,256
>
> device = c:\ndis\protman.exe /i:c:\ndis
> device = c:\ndis\elnk16.dos
> device = c:\ndis\dis_pkt.dos
> ---------------------------------------
> autoexec.bat
>
> c:\ndis\netbind

It may not be related but I saw no mention of your NetBIOS driver.  Does
that mean you are loading NBP in autoexec.bat but didn't show it?  At
any rate, with the EtherLink16 everything is set via setup software and
you didn't include that information.  Critical things to check include
the hardware interrupt number (I use 2 or 5 but be careful nothing else
is already using the one you have chosen), memory mapping (a lot of disk
controllers use C800 so I usually avoid that one), and I/O address
mapping (the default value of 300h has worked well for me).

If you don't already have it, you ought to get the latest version of the
NDIS to packet shim.  I think it is up to version 1.09 and is available
from better anonymous ftp sites everywhere.  A couple that come to mind
are "netlab2.usu.edu" where the "official" copy lives, and
"comlab.gatech.edu" in "/pub/lanman" where I have a copy along with some
other handy LanMan utilities.

After saying all that I hope I didn't miss anything obvious!
Bob

===================================================================
FIX #2
In article <3COM-L%92082515452800@NUSVM.NUS.SG>, conrad@iuavcd.unive.it
says: >Can anybody help us to run correctly  a 3com Etherlink 16  with
LAN MANAGE R >and CU/TCP from the Clarkson University?  > >We want to
install both LAN MANAGER and CU/TCP in the same PC, but we can' t
>because of a number of errors and crashes of the DOS.  I use CUTCP with
PathWorks (which is NDIS based and used the MS Redirector, so is
functionally very similiar to LanMan) regularly in machines with
EtherLinkIIs (3C503s) regularly, without any problems.

When setting up a PathWorks for OS/2 server (ie LanManager over DECnet),
I decided to use a 3C507 (EtherLink 16) but it crashed with NDIS messages
a couple of times, so I used a 3C503 instead. As it became a production
server before I got a chance to look into it, I never did find out what the
problem with the 3C507 is, and it's still running fine with the 3C503.

If anyone has any information about the NDIS driver for the 3C507, I'd
appreciate it for the next time I set up a server.
>
>Thanks if you can help us.
>                                  Corrado Petrucco
>
>P.P.S
>What's dis_pkt.gup??
It's the version of dis_pkt.dos provided with PC/TCP by FTP Software.
dis_pkt.dos is an NDIS application that provides a packet driver front
end for applications that are written to use Packet Drivers. We currently
use dis_pkt9.dos (look on netlab.usu.edu), which is a bit more up to date,
(it works with gopher!)

Aengus
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling????
====================================================================
Fix#3
Thanks to all people who helped me:

 Aengus Lawlor,
 Stephen Stone,
 Bob Hutchinson,
 Bob Baggerman,
 Andy Seal
 and Brian

 (This list is wonderful!),  at this point I know a lot about NDIS, Etherli
nk
 and Lan Manager.

Now my Etherlink 16 runs with NDIS and CU/TCP.
This is the protocol.ini:

====================================================

[PROTOCOL MANAGER]
  DRIVERNAME = PROTMAN$

[PKTDRV]
  drivername = PKTDRV$
  BINDINGS = "exp16_nif"
  intvec = 0x60
  chainvec = 0x66

[EXP16_NIF]
  DRIVERNAME = ELNK16$

=====================================================
and this is the config.sys:

device=c:\dos\ansi.sys
COUNTRY=039,437,C:\DOS\COUNTRY.SYS
files=30
STACKS=9,256

device = c:\ndis\protman.exe /i:c:\ndis
device = c:\ndis\elnk16.dos
device = c:\ndis\dis_pkt.dos
================================================================

and more thanks.

Corrado

---------------------------------------------------------------------------
---
MAIL TO: conrad@iuavcd.unive.it

                           C.I.D.O.C.
 Centro Interdipartimentale di Documentazione Statistica e Calcolo
       Istituto Universitario di Architettura di Venezia
                         VENICE - ITALY

MAIN INTERESTS: Architecture, Computer Graphics, Rendering, Cartography,
                Urban Planning,   Statistics,   Artificial Intelligence.

       tel. +39 (41) 721900     fax. +39 (41) 5208945

       Friendly, from the romantic Venice.
---------------------------------------------------------------------------
-------------------------------------------------------------------------
YOUR MESSAGE




HELP!

Need assistance, I am trying to get a EtherLink16 (3c507) card to work with
our 3+Open Lan Manager v1.1 network.  I'm installing the card in a Gateway2000
486DX2/50 PC.  First of all the installation setup program did not work.  So,
I did a manual installation, by coping all the necessary files.  Anyway,
everthing seems to load O.K. until I get to a point where I'm loading MS-DOS
Lan Man NETBIND v1.1 --> then, it fails gives an error message:
  PRO0033E No Network driver binding was performed.
  Network card not found.

Then, I copied over the latest NETBIND v.20 from the installation disks.  This
time everything seems O.K. until it gets to the NETBIND command line and it
gives and error message stating that PROTMAN.EXE is not found.  My question is
whether this has something to do with NETBIND v2.0 or what?

Everything works fine with a ETHERLINK II (3c503) card using the existing
configuration(w/mods). Here's what my configuration looks like (shorten):
(BTW, I am running MS-Windows 3.1, but I've shorten these files)

*************************CONFIG.SYS****************************************
DEVICE=C:\LAN\LANMAN\DRIVERS\PROTMAN.DOS /I:C:\LAN\LANMAN\DRIVERS
DEVICE=C:\LAN\LANMAN\DRIVERS\elnk16.dos
device=c:\lan\dis_pkt.dos
DEVICE=C:\LAN\LANMAN\DRIVERS\xnstp.dos
rem DEVICE=C:\LAN\LANMAN\DRIVERS\NEMM.DOS
rem DEVICE=C:\LAN\LANMAN\DRIVERS\TCPDRV.DOS /I:C:\LAN\LANMAN\DRIVERS
****************************************************************************
**********************AUTOEXEC.BAT******************************************
pktint
c:\LAN\lanman\drivers\nbp
c:\LAN\lanman\drivers\netbind
c:\LAN\lanman\drivers\minses
*****************************************************************************
**************************PROTOCOL.INI***************************************

[protocol mananger]
  DRIVERNAME=PROTMAN$

  ; 3Com 3C505
[ETHERLINK_PLUS]
  DRIVERNAME = ELNKPL$
  INTERRUPT = 9
  IOADDRESS = 0x300
  DMACHANNEL = 5

; Packet driver to NDIS shim
[PKTDRV]
  DRIVERNAME=PKTDRV$
  BINDINGS=ETHERLINK16
  INTVEC=0x66

; 3Com 3C503
[ETHERLINKII]
  DRIVERNAME = ELNKII$
  Interrupt = 2
  IOAddress = 0x300
  DMAChannel = 1
  xmitbufs = 2
  TRANSCEIVER = EXTERNAL

; 3Com 3C507
[ETHERLINK16]
  DRIVERNAME = ELNK16$

;************************
;**     PROTOCOLS      **
;************************

; 3Com XNS protocol
[XNS_TRANSPORT]
   DRIVERNAME     = XNSTP$
   BINDINGS       = ETHERLINK16
   MAXPROCESSES   = 12
   FGTICKS        = 2
   BGTICKS        = 2
   MAXROUTES      =
   MAXSOCKETS     =
   MAXXMITDESCS   =
   NONGROUPS      =
   SHAREGROUPS    =
   LOGINLIBRARY   = YES
   COURIERLIBRARY = NO
   NETBIOSGROUPS = 0

; NetBEUI ; works with DLC Protocol
[NETBEUI]
  DRIVERNAME = MNETB$
  BINDINGS = DLC

; DLC Protocol
[DLC]
  DRIVERNAME = MDLC$
  BINDINGS =

; 3Com NETBIOS Protocol
[NBP]
  DRIVERNAME = NBP$
  BINDINGS = ETHERLINK16
  DEFAULTS = LIGHT-USER

; 3Com TCP/IP Protocol
[TCPIP]
  DRIVERNAME = PKTDRV$
  BINDINGS = ETHERLINK16
  IPADDRESS0 = 130 109 117 235
  SUBNETMASK0 = 130 109 000 000
  DEFAULTGATEWAY0 = 130 109 002 001
  SNAP = NO
  ARPTBLSIZE = 10
  IPSOCKETSIZE = 0
  TCPCONNECTIONS = 8
  TCPCONNTIMEOUT = 30
  TCPWINDOWSIZE = 4350
  TCPSEGMENTSIZE = 1450
  LOADFACTOR = 105
  LBUFSZ = 1550
  MBUFSZ = 600
  SBUFSZ = 100
  LBP = 50
  MBP = 30
  CLIENTOD = 9
  CLIENTBD = 25
  CLIENTMSG = 16
  CLIENTAMSG = 16

[RFCNETBIOS]
  DRIVERNAME = TCPNB$
  BINDINGS = TCPIP
  NUMNCBS = 16
  NUMNAMES = 6
  NUMSESSIONS = 8
  SCOPE = ""

[TCPGLOBAL]
  HOSTNAME = "123_456"
  NETFILES = "C:\ETC"

[DNR]
  DRIVERNAME = DNR$
  BINDINGS = TCPIP
  NAMESERVER0 = 130 109 001 001
  NAMESERVER1 = 130 109 001 002
  DOMAIN = "NCSC.NAVY"

[NMDRV]
  DRIVERNAME = NMDRV$
  BINDINGS = TCPIP
  SYSTEMID = "1.3.6.1.4.1.43.1.5"
  SYSTEMDESC =" "

[SOCKETS]
  DRIVERNAME = SOCKETS$
  BINDINGS = TCPIP
  MAXSENDSIZE = 1024
  POOLSIZE = 10000
  NUMSOCKETS = 32
  NUMTHREADS = 32

[TELNET]
  DRIVERNAME = TELNET$
  BINDINGS = TCPIP
  NSESSIONS = 4
  MAX_OUT_SENDS = 3
  MAX_SEND_SIZE = 128
  DRIVER_EOL = 1
  APP_EOL = 1
  ECM_CHAR = ""
  BRK_ACTION = 3
  MUI_PROMPT = "LAN> "
  REDIREC_COM = 1

*****************************************************************************

I would really appreciate any and all assistance.

Thanks,
Joe

Joe@email.ncsc.navy.mil
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU