home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!bailgate!prod_eng1.lincoln.gpsemi.com!colh
- From: colh@lincoln.gpsemi.com (Colin Helliwell)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: DIS_PKT9 with DEC Pathworks
- Message-ID: <colh.1.724958050@lincoln.gpsemi.com>
- Date: 21 Dec 92 17:14:10 GMT
- Sender: usenet@bailgate.gpsemi.com (usnet account)
- Organization: GEC Plessey Semiconductors
- Lines: 54
- Nntp-Posting-Host: prod_eng1.lincoln.gpsemi.com
-
- I'm trying to run the dis_pkt9 (packet driver-over-ndis) shim with my DEC
- Etherworks LC card.
-
- I have successfully used the driver with NCSA Telnet etc, but I cannot get
- the DEC Pathworks (PCSA) software to work alongside it.
-
- If I delete the "[PKTDRV]" entry in the protocol.ini file and reboot, then
- Pathworks works fine i.e. I can have one or the other or both.
-
- I am guessing that the packet driver program is grabbing the ethernet
- packets, and then chucking them away without giving the Pathworks
- application a chance to accept them. This is only a guess though - I don't
- know for certain what's happening.
-
- The ndis driver and protocol manager are both as supplied by DEC.
-
- The protocol.ini file is as below:
-
-
- ; PROTOCOL.INI file.
-
- [PROTOCOL MANAGER]
- DriverName = PROTMAN$ ; protman.sys
- Priority = DATALINK ; doesn't seem to have any effect !
-
-
- [PKTDRV]
- DriverName = PKTDRV$
- Bindings = depca
- Intvec = 0x60
-
-
- [DATALINK]
- Drivername = DLL$MAC ; dllndis.exe
- Bindings = depca
- Lg_Buffers = 64
- Sm_Buffers = 12
- Outstanding = 128
- Heuristics = 0
- Adapter_Type = 5 ; ???
- MOP = 0 ; ???
- ;Specify IRQ level used by workstations network adapter
- ;NI_IRQ = 5
-
- [DEPCA]
- DriverName = DEPCA$ ; depca.dos
- AdapterName = DE100
- RamAddress = 0xD000
- IoAddress = 0x300
- Interrupt = 5
-
-
- Does anyone with NDIS/Pathworks/Dis_Pkt experience know what's going
- wrong ??
-