klefstad@ux1.cso.uiuc.edu (Sue Klefstad) (03/09/91)
Is it possible to get FTP's dis_pkt (NDIS<-->packet driver converter) to work with 3Com's 3+Share? On bootup I get the following message: MS DOS LAN Manager Netbind v1.1 PRO0025E Failed to bind Since I see all sorts of references to 3+Open and none to 3+Share, I wonder if I am... spitting in the wind. Relevent files (3C523 adapter): PROTOCOL.INI: [MAC3C523] drivername = ETH523.SYS iobase = 0x300 membase = 0xC0000 [PKTDRV] drivername = PKTDRV bindings = ETH523.SYS intvec = 0x65 chainvec = 0x66 CONFIG.SYS: device=protman.sys device=eth523.sys device=dis_pkt.dos device=pro.sys 12 2 2 device=buf.sys device=idp.sys device=spp.sys device=lgl.sys AUTOEXEC.BAT: runminds mindspro mindsbuf minseth minsidp mindsspp mindslgl nb 2 4 4 minses msredir /s:2 /l:8 /z:4096 3c523 0x60 netbind (I've played around with the order of the 3Com, Clarkson, and FTP calls in autoexec.bat.) Thanks! -- -- Sue -- ========================================================================= Sue Klefstad Ill. Natural History Survey klefstad@uiuc.edu
jbvb@FTP.COM ("James B. Van Bokkelen") (03/12/91)
Is it possible to get FTP's dis_pkt (NDIS<-->packet driver converter)
to work with 3Com's 3+Share?
As far as I knew, 3+/Share didn't used to be available in a version that
used NDIS (even 3+/Open didn't really work with NDIS in the first betas).
I don't know off-hand what the "failed to bind" message is, I've never seen
it before.
First, I'd make sure that 3+/Share is supposed to use NDIS in the first
place. Second, you can't use the Clarkson 3C523 driver at the same time
as you use the 3Com NDIS driver for the same card. If the DIS_PKT file
is in the system, it provides the Packet Driver functionality and you
don't need the Clarkson driver. Third, "netbind" has to run before
you run our kernel. I don't know whether it needs to be done before
you run the 3+/Share redirector.
James B. VanBokkelen 26 Princess St., Wakefield, MA 01880
FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901