Xref: utzoo bit.listserv.novell:11878 comp.sys.novell:1949
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!nntpd.lkg.dec.com!ranger.enet.dec.com!j_pan
From: j_pan@ranger.enet.dec.com (Joanna Pan)
Newsgroups: bit.listserv.novell,comp.sys.novell
Subject: Re: PathWorks for DOS NetWare Coexistence Product from DEC
Message-ID: <23759@shlump.lkg.dec.com>
Date: 21 Jun 91 20:34:11 GMT
Sender: newsdaemon@shlump.lkg.dec.com
Followup-To: bit.listserv.novell
Organization: Digital Equipment Corporation
Lines: 37


In article <91170.134031RBYAML@ROHVM1.BITNET>, RBYAML@ROHVM1.BITNET (Aengus Lawlor) writes...
> 
>But before I spend a lot of time trying to get it to work, I was wondering
>whether I can just run IPX-NDIS along side Pathworks, and if so, what
>problems am I likely to encounter.
>

Yes, you can. You would run the DLLNDIS first, then the IPXNDIS, and then bind
them together. I am running Pathworks with NetWare Co-Existence, and I am happy
with it so far.

>
>Pathworks in an MS-Net compatible OS, and uses MSs REDIR. Netware uses
>some different tricks to achieve the same effect. Will these conflict.
>

I have not seen any problem yet.

>  
>Pathworks will only use drive letters below LASTDRIVE, Netware uses drive
>letters after LASTDRIVE.
>

So, make sure your lastdrive is not z. Otherwise, you won't see NetWare.

> 
>If you run windows, over such a combination (if it works) do you set windows
>up for Netware (better interface) or Microsoft Network?
>

It does work. I set it up for Microsoft Network to access some printers which
cannot be accessed via NetWare. I don't know the effect of setting up for
NetWare.


	Joanna Pan