From: bielski@skyler.mavd.honeywell.com (Walt Bielski)
Subject: Re: HELP! Need to get DEC Pathworks 4.1 on NDIS to work with WinQVT/NET
Organization: Honeywell Systems & Research Center
Date: Thu, 8 Oct 1992 16:15:08 GMT

In article <1992Oct8.130138.15357@msuinfo.cl.msu.edu>, carter@cemvax.cem.msu.edu (Tom Carter) writes:
> The subject outlines my problem. I have DEC PathWorks 4.1 running on my 
> Gateway 486/33C with a DEC EtherWorks Turbo (DE200) ethernet card on a coax 
> thinnet network here on campus. The transport I'm currently using is via the 
> NDIS drivers provided by PathWorks (BTW, PathWorks is MS Lanman ported to VMS; 
> I think the client side is nearly identical to a straight MS Lanman 
> installation). What I THINK I need to do is install an NDIS-to-packet converter 
> like dis_pkt.dos, and then a packet multiplexer like pktmux. Trouble 
> is, I'm fairly new to this networking stuff, and so far the problem hasn't 
> succumbed to my feeble attempts to get it to work.
> 
> Can anyone help me out <~whine~>? I really want to get this going so I don't 
> have to exit windows and stop PathWorks when I want to run WinQVT/NET, or exit 
> windows and reboot when I am running WinQVT/NET and need to do PathWorks.
> 
> Any and all help or advice or guidance will be GREATLY appreciated. TIA
> 
> ===========================================================================
> |        Tom Carter                    |     carter@cemvax.cem.msu.edu    |
> |  Michigan State University           |     carter@msucem.bitnet         |
> |    Chemistry Department              |                                  |
> ==========================================================================

Since this question has come up a number of times, I am posting the reply.

Pathworks 4.1 will coexist just fine with WinQVTNet (I am using both right
now). I am using a NE-2000 compatible NIC with the MS NDIS drivers for same.
I think MS wrote these drivers for LanMan. Anyway, I assume that the
DEC-supplied drivers are also "real" NDIS drivers. If so, here are the steps
that I followed to get this working (it took _me_ a while to figure this out,
so I hope I am saving folks some time):

1. Get DIS_PKT9.ZIP from a friendly FTP site near you (I don't remember
   where I got mine from).

2. UnZIP same into its own directory (hey, keep that drive organized :)).

3. Copy DIS_PKT9.DOS into your decnet directory.

4. Modify your protocol.ini file in your decnet directory to look like the
   following (keeping in mind that if you are using a different network card
   you will see references to its driver rather than NE2000.DOS): 


; PROTOCOL.INI file create by DNETOMO.V41 V4.1.060
;                         via DNETWIK.V41 V4.1.047

[protocol manager]
DRIVERNAME = PROTMAN$


[IPX4MAC]                     \
DRIVER = IPX$MAC               > ...but this might be new too.
BINDINGS     = NE2000.DOS     /

[pktdrv]                        \
  drivername = pktdrv$           \
  bindings = NE2000.DOS           > I'm pretty sure that this is all I added...
  intvec = 0x60                  /
  chainvec = 0x66               /

[DATALINK]
DRIVERNAME   = DLL$MAC
LG_BUFFERS   = 16
SM_BUFFERS   = 6
OUTSTANDING  = 32
HEURISTICS   = 0
BINDINGS     = NE2000.DOS
;Specify IRQ level used by workstations network adapter
;NI_IRQ       = 5


[NE2000.DOS]

; protocol.ini section for the Novell NE2000 Card

    IOBASE = 0x300
    INTERRUPT = 3
    DRIVERNAME = MS2000$


5. Load the dis_pkt shim in your config.sys after you load the other Pathworks
   and NDIS drivers. Below is a fragment from my config.sys:

REM Install the Pathworks software
device=\DECNET\PROTMAN.SYS /I:C:\DECNET
devicehigh=\DECNET\NE2000.DOS               <- again, my NDIS driver
REM Install the NDIS/packet driver shim
devicehigh=c:\decnet\dis_pkt9.dos


6. Load the WinQVTNet driver after Pathworks is started (but the order may not
   matter). Below is a fragment from my autoexec.bat:

REM Executing network startup procedure
if not exist \DECNET\STARTNET.BAT goto nostartup
call \DECNET\STARTNET
goto end
:nostartup
echo ** WARNING ** STARTNET.BAT file not found.  Network functions not
performed
:end
loadhigh c:\network\qvtnet\pktint.com

Note that you do not need pktmux.


Unless I forgot something, you should now be able to reboot your system and
all of the drivers will be installed. You can check this by Norton or other
utilities (or a mem/c in DOS 5.0). If there is a problem, make sure that the
dis_pkt shim is in the same directory as the protocol.ini file (decnet). Note
that if you were loading packet drivers for WinQVTNet, you should not any more. 

This worked for me. I hope it helps you.

Walt

My opinions, not Honeywell's.