HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Can MS-LAN Manager and Pathworks/DOS Live Together?
From: Stephen Stone <CCSWS@LEVELS.UNISA.EDU.AU>
Date: 05 Oct 1992 08:29:30 +0930
MIME-version: 1.0
Content-transfer-encoding: 7BIT

>Here at the National Institutes of Health we support several hundred LANs tied
>to a cisco router "backbone" routing DECnet, TCP/IP, AppleTalk Phase II, and
>3Com XNS. For a number of years we "supported" 3Com servers as a way to network
>PCs, and have recently added AppleTalk to keep the Mac users happy. We now have
>an increasing number of Pathworks users as VAX owners realize that they can
>support both PCs and Macs. We are in the process of phasing out the 3Com-based
>LANs in favor of Microsoft LAN Manager, and need to know how to advise our
>customers on the interoperability of Pathworks and LAN Manager. I would deeply
>appreciate any comments about your experiences using these products on the same
>LAN. Please mail your replies and I'll summarize to the group. And if such a
>summary already exists, please let me know, although it may need an update if
>it isn't recent.
 
 
The University of South Australia was formed by the merger of groups
with a mixture of Pathworks and 3Com (now LAN Manager) networks.  We have
tested the interoperability of both DOS abd OS/2 LAN Manager clients
running Microsoft's (= HP and 3Com) TCP/IP stack, connecting to file
services on an Ultrix Pathworks server (running TCP/IP).
 
For the simple commands like NET USE, there appears to be good interoperability.
 
There are some restrictions.  A DOS or OS/2 LAN Manager client cannot
remotely administer a Pathworks server (using NET ADMIN \\serevr) in the
same way they can remotely administer a LAN Manager server.
 
Also, you need to set up an LMHOSTS.INI file for each client which has entries
for each server which is not on the client's IP subnet.  I hope someone
is working on an RFC which allows the Domain Name Resolver to be used
in some way.
 
We have not tried the reverse yet (DOS Pathworks client running TCP/IP
connecting to LAN Manager server running TCP/IP stack).  We have tried
multiple protocol stacks on OS/2 LAN Manager servers (such as all of
NETBeui, DECnet, TCP/IP and XNS at the same time).
 
Stephen (Rocky) Stone,  Levels Team Leader
 
Postal mail:                          |  Tel:  +61 8 302 3242
    Information Technology            |  Fax:  +61 8 302 3385
    University of South Australia     |  Email: Rocky.Stone@UniSA.Edu.au
    The Levels, S.A.  5095            |
From: PMGRIEGG@IUP.BITNET (Paul Grieggs)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Setting personal file service protection.
Date: 1 Oct 92 12:02:00 GMT
X-Organization: Indiana University of Pennsylvania
X-VMS-Cc: IN%"gareth@lucifer.latrobe.edu.au",PMGRIEGG
Content-transfer-encoding: 7BIT
X-cc:         gareth@lucifer.latrobe.edu.au

>
> I was wondering if it is possible to change the default RMS protection of
> personal file services (i.e. the M:\ directory ).
>
> I am fully aware of how to set application file service RMS protections
> ( $ PCSA SET FILE SERV /PERM /RMS=G:RWED ) but personal file services
> leave me with G:R protection by default.
>
> Thanks,
>
> Gareth.
>
> --
> gareth@lucifer.latrobe.edu.au
 
The latest patch for Pathworks for VMS 4.1 allows one to modify the server
default RMS protection.  This patch is CSCPAT_3043011.
 
To make the change, edit your PCFS$LOG_FILES:PCFS$STARTUP_PARAMS.DAT
file to add the line:
 
   PCFS$DEF_UIC_PROTECTION=(rms protection mask)
 
For example:
 
   PCFS$DEF_UIC_PROTECTION=(S:RWED,O:RWED,G,W)
 
After adding this line, restart the file server.
 
For more info on this, see the release notes for CSCPAT_3043011.
 
==========
Paul Grieggs                                     PMGRIEGG@IUP.BITNET
Data Communications Manager                      PMGRIEGG@GROVE.IUP.EDU
Indiana University of PA
From: karcher@jevex.waisman.wisc.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Novell drivers for Depca's?
Date: 2 Oct 92 23:26:14 GMT
Organization: Waisman Center, University of Wisconsin-Madison

In a previous article, I asked:
>Is anyone aware of Depca/Etherworks drivers for use with Novell Dos clients?
>I know about the Novell Coexistence product which supplies the files to
>build an NDIS compliant IPX but it looks like that requires a pathworks
>license to use (and I don't want to run pathworks AND novell). Is there
>any way to make DEC's cards work with Novell 3.11 dos clients without
>pathworks? 
> 
Many thanks to the people that replied to my query.  I ended up finding exactly
what I needed on Compuserve in a saveset called ethwks.zip.  It contains .LAN
and .OBJ files to link an IPX via WSGEN for Netware 3.11.  I also understand
that Dec may be working on an ODI driver for their cards.  Thanks again.


Carl Karcher                          Internet: KARCHER@WAISMAN.WISC.EDU
Waisman Center                        Bitnet:   KARCHER@WISCMACC
University of Wisconsin-Madison       PSTnet:   (608) 263-5896
Newsgroups: vmsnet.networks.desktop.pathworks
From: eirikur@ranger.enet.dec.com (Eirikur Hallgrimsson)
Subject: Re: Pathworks for Mac, folder/sub-directory limit?
Organization: Digital Equipment Corporation
Date: Wed, 30 Sep 1992 22:01:26 GMT


In article <1992Sep15.210038.826@miavx3.mid.muohio.edu>, jfeldhouse@miavx3.mid.muohio.edu (Jim Feldhouse) writes...
>I seem to remember someone encountering a problem using
>Pathworks for Mac due to there being a limit on the number
>of subdirectory levels or folder levels on either the VMS
>or Macinotosh sides?  Does anyone remember some more details
>of this or specifically what the limit might be and on which
>side?

It's a VMS restriction.  PATHWORKS for VMS (Macintosh) uses the standard VMS
filesystem, representing folders as directories, allowing nifty
interoperability with VMS users and applications.  Problem is, Mac users can
create infinitely deep directory trees.  Certain key VMS utilities will not
operate on data that is more than 8 deep.  VMS Backup, and Disk Verify come to
mind.  This problem has been reported to VMS Engineering.

You probably noticed the setting in the server manager for restricting the
depth that folders can be created at.  It was put in to help avoid data loss
due to files not being backed-up because Backup couldn't see them.  You can
adjust this, but it comes set for Backups's limits, which seems to be the most
useful thing.  If you use some other backup mechanism, you can disable this.

WARNING: The folder-depth-checking is not a perfect solution.  It is possible
to circumvent it.  


Eirikur Hallgrimsson   |    "Rhodes?  Where we're going, we don't need Rhodes!"
eh@ranger.enet.dec.com |
PATHWORKS for Macintosh|

Newsgroups: vmsnet.networks.desktop.pathworks
From: karcher@jevex.waisman.wisc.edu
Subject: RE: Win 3.0 Setup / PW 4.1
Organization: Waisman Center, University of Wisconsin-Madison
Date: 6 OCT 92 17:37:44 CDT

In a previous article, KRAMER_AG@RSO.DNET.GE.COM (Aaron Kramer GE Hypersonic Systems Dept 215-354-4355) wrote:
>1. I remember reading that some have moved the PCSV41 file service
>   to a disk service. Have those people experienced any problems
>   with doing this? Is it as straightforward as it seems? It appears
>   to me that I can up the logon speed if we move from file -> disk.

We've converted the V4.0 system file service to a disk service. Putting it in a
container file is the easy part. You then have to modify the "WIK" file
(\PCAPP\DNETWIK.V41 for V4.1) to load LAD before connecting to the system
service and add /V to the USE command. The WIK file is used to generate
STARTNET.BAT. It's not too bad of a job (although entirely "unsupported"). The
language of the WIK file is partially documented in an appendix of the client
commands manual.

However, before you go through that, make sure LANSESS is loaded on the clients
and open file caching is turned on for your server. This can make a big
difference in the performance of file services. I've found that with open file
caching turned on and a large enough data cache, a system file service is quite
adequate for a VS4000/60 server. For a slower server it may not be and using a
system disk service could help. A system file service has the advantage that it
is much easier to update than a disk service (since all PC's don't need to
disconnect before you can write to it). 

>2. I am trying to follow the PW4.1 docs fir uSoft Windows Support,

For windows 3.1, WIN3SETU is not required or desirable. You can select a network
type of "DEC PATHWORKS (version 4.1 or higher)" from the windows Setup Options
menu. It may ask you to insert a disk from the windows 3.1 distribution to get
the driver.


Carl Karcher                          Internet: KARCHER@WAISMAN.WISC.EDU
Waisman Center                        Bitnet:   KARCHER@WISCMACC
University of Wisconsin-Madison       PSTnet:   (608) 263-5896
From: RONAU%CUTTER%OPUS@MCOIARC.BITNET
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Performance Problems with File Services
Date: 5 Oct 92 17:17:00 GMT
Content-transfer-encoding: 7BIT

Mike,
 
Go to an OS/2 server with Pathworks for OS/2.  Use it for your file
services.  We have been putting our applications that use a file service
on the OS/2 and we have has good performance.
 
Pros-     Cost- Gateway 486/66 under $3000
          Setup- OS/2 was OK, PW for OS/2 was easy (use share mode)
Cons-     Limited number of partition
 
 Theodore F. Ronau               ------------------------------------------
 Network & Small Systems Manger  | First try Esc, then Ctrl/Break, Ctrl/C |
 Information Systems             | or Ctrl/Z, Ctrl/Alt/Del, the On/Off    |
 Medical College of Ohio         | Switch, and if all else fails, PRAY!!  |
 (419)-381-3601                  ------------------------------------------
 Bitnet: Ronau@mcoiarc          Or for the Vax (per another list subscriber)
                                 Ctrl/Q,Ctrl/T,Ctrl/W,Ctrl/U,Ctrl/Z,Esc,
                                 Ctrl/C,Ctrl/Y/Y/Y,break,power off
From: gareth@lucifer.latrobe.edu.au (Chief Smeghead)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Setting personal file service protection.
Date: 1 Oct 92 01:06:15 GMT
Organization: La Trobe University

I was wondering if it is possible to change the default RMS protection of
personal file services (i.e. the M:\ directory ).

I am fully aware of how to set application file service RMS protections
( $ PCSA SET FILE SERV /PERM /RMS=G:RWED ) but personal file services
leave me with G:R protection by default. 

Thanks,

Gareth.

-- 
gareth@lucifer.latrobe.edu.au
Newsgroups: vmsnet.networks.desktop.pathworks
From: klovatt@klnet.UUCP (Keith Lovatt)
Subject: Re: Printing from Applications 
Organization: Lugroid Enterprises
Date: Sat, 3 Oct 1992 20:00:14 GMT
X-Newsreader: Tin 1.1 PL4

hamilrk1@bisdpo1.bisdnet.jhuapl.edu () writes:
[...]
: Use the PSC.COM TSR that comes with Pathworks for DOS. The file is located in
: the \PCSAV41\LMDOS directory. Copy the file over to the DOS Client and then
: add the following line to the STARTNET.BAT 
: 
: 	C:\DECNET\PSC.COM
: 

Just make sure, when you edit STARTNET.BAT that PSC is loaded before REDIR.

Keith.
-- 
Keith Lovatt                 	|	Scarborough, Ontario, Canada
r-node.gts.org!klovatt@klnet	|	Phone: +1 416 293 0292
doe.utoronto.ca!klovatt@klnet	|    "You can never find a Lugroid
klovatt@terranet.cts.com	|	when you really need one"
From: dbk@pslu1.psl.wisc.edu (Don Katz)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Pathworks performance vs Novell
Date: 6 Oct 92 13:45:19 GMT
Organization: Physical Sciences Lab, University of Wisconsin

In article <1992Oct5.120157.884@mala.bc.ca> dunnett@mala.bc.ca (Malcolm Dunnett) writes:
>In article <Bvnu8r.1Hs@netnews.jhuapl.edu>,
>     hamilrk1@bisdpo1.bisdnet.jhuapl.edu () writes:
>> You have received some good information regarding the comparison of the 
>> machines to be used for file servers. I recommend that you make sure to use 
>> the LANSESS transport on your DOS clients instead of DECNET. The LANSESS 
>> transport was written specifically for use in a Local Area Network 
>> environment and will provide you with the best transport performance.
>> 
>> We have used both DECNET and LANSESS on our LAN and have noticed a 
>> considerable difference accessing file services ......
>> 
>
>  We used to use LANSESS, but I've had a couple of problems with file
>services which seem to be related to using LANSESS instead of DECNET.
>In one case an application was complaining intermittently about "Network
>not available", even though everything indicated the network connection
>was there ( eg DIR of the service worked fine, etc ). In the other case
>accessing a file service from a DOS Shell session within Windows 3.1
>seemed to hang the connection using LANSESS. In both cases switching
>back to DECNET solved the problem.
>
>  This doesn't mean you shouldn't try LANSESS, but I'd suggest if you
>get strange problems you switch back to DECNET and see if they go
>away.

I am unable to load LANSESS on the PC's here because of problems with
Microsoft Windows 3.1. If LANSESS is loaded, 1) typing USE in an
MS-DOS Window causes Windows to crash, and 2) running the Print
Manager also causes Windows to become flaky. If anyone knows of a
solution, I would love to hear it.


-- 
-----------------------------------------------------------------------------
Don Katz                                .         Physical
                                       .- / \ -.      Sciences
University of Wisconsin - Madison   ./'  /+-+\  `\.       Laboratory   E-MAIL
From: GOODWIN@SMCVAX.BITNET (Dave Goodwin)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Performance Problems with File Services
Date: 2 Oct 92 12:49:00 GMT
Content-transfer-encoding: 7BIT

>We are currently having major performance problems with one of our labs.
>Here's a rough idea of our configuration.
>
>Server:
>Microvax 3100-80
>V6 Mb RAM
>Pathworks Disk RZ25 426 MB
>System Disk RZ24 209 MB
>VMS 5.5-1 (with various patches)
>Pathworks 4.1
>
>Clients:
>60 386sx PCs (4Mb RAM)
>7 IBM PS/2 Model 70s
>10 486sx PCs (4Mb RAM)
>all remote boot
>
>THE PROBLEM!!!!!!
>
>3. Mounting a file service takes quite a long time (between 5 and 10 minutes)
>when performance gets bad (somewhere after 15 to 20 active users).
>4. The same performance is observed as in point 3 whenever there is any
>sort of file activity on a file service (dir list, save, retrieve).
>
>--
>Mike Babin
 
Well, Mike, our configuration is not exactly like yours, but we DON'T need
or have a Cray!  We run PW 4.1 on a MicroVAX 3400, 28MB of RAM, better than
2GB of disk.  We support some 250 client nodes, of which 90 is about the
maximum we ever see connected at one time.  File service access is quite
quick, averaging perhaps 10 seconds to make the connection, worst case.
Loading the application averages about 25-30 seconds for something like
Lotus, all times being somewhat dependent on the type of PC.  Disk service
access is only moderately faster, so we are slowly moving most of our
applications to file services since we can then maintain them without having
to dismount them.
 
We have a rough schedule for 2-3 more campus buildings to come online, at
which time I've warned my Director to expect having to upgrade the server
or partition the network into two servers.  But at that point, I'll be
expecting to see around 150 simultaneous users.  I won't fault the 3400 if
it can't handle that load; we projected it for only around 100 clients.
 
I tend to agree with your system people that disk I/O is probably the
trouble.  I think we use more cache than you have in total RAM!  That
extra memory should help some, but may not solve the problem completely.
 
===========================================================================
Dave Goodwin                                   |
Assistant Director, Academic Computing         | We're all kinds of animals
-----------------------------------------------| coming here.
BitNet   : Goodwin@SMCVAX                      |
Ma Bell  : (802)654-2220                       | Occasional Demons, too.
US Mail  : Saint Michael's College             |
           Winooski Park, Colchester, VT 05439 |           -Jethro Tull
Ham Radio: N1HRO @ W1KOO.#NWVT.VT.USA.NA       |
===========================================================================
From: huffer@phoenix.ocf.llnl.gov (Clayton K Huffer)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: pkzip and pathworks problem
Date: 5 Oct 92 23:08:29 GMT
Distribution: vmsnet.networks.desktop.pathworks
Organization: Lawrence Livermore National Laboratory


	we're having problems with the well-known ms-dos pkzip
	file compression utility crashing the host portion of pathworks. 

	has anyone seen the following problem or have an
	idea about what is going on ?  the pathworks vms log files
	don't provide any clues. 

	we currently use pathworks v4 for ms-dos.  our application is
	software development.  we use gateway 2000 25mhz 486 pc's.
	all the source files and other files (object, list) are on
	the vax disk.
	after doing a few hundred compilations we like to use pkzip
	to recursively compress .obj and .lst files.  if we do this
	at 25mhz, then the host portion invariably crashes.  
	however, if we switch from 25mhz to slow-mode, then we don't
	have the problem.  unfortunately, you have to change the
	cmos setup and reboot the machine to do the switching. 

	a "small" number of files at 25mhz causes no problem.

	thanks in advance,

	keith huffer
	huffer@llnl.gov


--
-----------------------------------------------------------------
keith huffer, computer scientist, lawrence livermore national lab
huffer@llnl.gov, huffer@phoenix.ocf.llnl.gov
From: hamilrk1@bisdpo1.bisdnet.jhuapl.edu ()
Subject: Re: DWDOS386 and screen size...?
Reply-To: hamilrk1@bisdpo1.bisdnet.jhuapl.edu ()
Organization: Johns Hopkins University Applied Physics Lab
Date: Mon, 5 Oct 1992 17:55:06 GMT

Michael,

  Have you tried turning on Panning under the DWCONFIG program? If not, run 
DWCONFIG again and enable horizontal and vertical panning. This will not 
reduce the size of your screen, but will enable you to pan the screen easily 
with the use of your mouse ....

-BobH



=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Robert K. Hamilton            hamilrk1@bisdpo1.bisdnet.jhuapl.edu         
Johns Hopkins University  Phone: (301) 953-6068
Applied Physics Lab          FAX  : (301) 953-1093
Bldg. 9-163
Laurel, Md.  20723-6099
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Newsgroups: vmsnet.networks.desktop.pathworks
From: ccksb@trentu.ca (Ken Brown)
Subject: Re: Novell drivers for Depca's?
Reply-To: ccksb@trentu.ca (Ken Brown)
Organization: Trent University
Date: Thu, 1 Oct 1992 13:00:37 GMT


In article <28SEP92.14245804@jevex.waisman.wisc.edu>,
karcher@jevex.waisman.wisc.edu writes:

>Is anyone aware of Depca/Etherworks drivers for use with Novell Dos clients?
>I know about the Novell Coexistence product which supplies the files to
>build an NDIS compliant IPX but it looks like that requires a pathworks
>license to use (and I don't want to run pathworks AND novell). Is there
>any way to make DEC's cards work with Novell 3.11 dos clients without
>pathworks? 

DEC's Etherworks cards can be used for Novell clients.  What you need is
a packet driver and BYU's IPX configured for a packet driver.  (This solution
does NOT work for the original DEPCA).

Obtain the packet driver DEPCA.COM from sun.soe.clarkson.edu (128.153.12.3)
/pub/ka9q/pktd9_0s.zip and BYU's stuff /pub/novell/novell.exe.  Alternatively
try csd1.trentu.ca (192.75.12.139) and grap /archives/novell.exe,
/archives/pktdrv10.zip (if you just want the packet driver you'll find
/clarkson/depca.com).  Read the docs and you're off to the races.

The only licence to worry about is Novell's user limit on your server(s).

--
====================================================================
Ken Brown                                       voice: (705)748-1540
Trent University Computing & Telecommunications   fax: (705)748-1246
Peterborough, Ontario, Canada K9J 7B      internet: kbrown@trentu.ca
From: dolan@ACUVAX.ACU.EDU ((Tom Dolan))
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: WinQVT
Date: 2 Oct 92 18:42:23 GMT
Content-transfer-encoding: 7BIT
X-POPmail-Charset: English

Does anyone have Pathworks 4.1 and WinQVT TCP/IP client working together?
I want to have access to Pathworks files services and the SMTP server at
the same time.
 
WinQVT starts to run and then causes Windows to exit to the C:\ prompt.
 
I need help with WinQVT.
 
Thanks!,
 
Tom Dolan           Dolan@Acuvax.acu.edu
Systems Manager
College of Biblical Studies
Abilene Christian University
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: PCSA MAIL looping?
From: "(bachism)" <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 29 Sep 1992 07:50:39 -0400
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS%MIAMIU.BitNet@pucc.PRINCETON.EDU"

Look at his MAIL.INI file or try setting him up with MAILSETU
From: CF0@PSUALT.BITNET (Craig Farrell)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: PW4.1, UCX2.0
Date: 6 Oct 92 14:52:00 GMT
Content-transfer-encoding: 7BIT
Original_To:  PCSA

We just recently installed UCX2.0 on our VAX.  This isn't directly
related to Pathworks. We can't get outgoing internet mail
working.  We can receive incoming mail but can only send to one
or two internet mail sites.  Other mail sits in que and doesn't
go anywhere.  Another site here at PSU has the same problem
and we have been talking to DEC but no solution has been found
yet.  I thought maybe someone using UCX with Pathworks might
have run into the same problem.  We think we have UCX set right
for mail.  We don't have any MX records set up.  We thought the
nameserver should be able to resolve the receiving location.
 
       Craig Farrell                       Penn State Altoona Campus
       CF0@PSUALT.bitnet                   225 CLRC Building
       (814) 949-5295                      Altoona PA,  16601
Newsgroups: vmsnet.networks.desktop.pathworks
From: aus@winx03.informatik.uni-wuerzburg.dbp.de (Hans Aus)
Subject: Re: HOW TO READ MS-CDROM VIA PATHWORKS?
Organization: University of Wuerzburg, Germany
Date: Thu, 1 Oct 1992 14:50:38 GMT

From article <2ac96be8.8ccb5d.2@BEIZ.mediatex.ch>, by Programmierer@BEIZ.mediatex.ch (055485666: MEDIAtex AG):
> You need a software called F11CD.
> 
> What I heard (but I'm not shure) F11CD should be on the Septmeber CONDIST-CD.
> If not, call your DEC-REP he can organize it for you. F11CD need's no license
> and is free.

I just received my copy of the September CONDIST-CDs. I do not see it
on the distribution. Am I missing something ?

> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> |B                                    B|
> |E           CH: VTX *3600#           E|
> |I           D:  BTX *28881#          I|
> |Z                                    Z|
-- 
Hans M Aus, Institute of Virology, University of Wuerzburg, Germany
e-mail: hans.aus@vax.rz.uni-wuerzburg.dbp.de (prefferred)
Versbacherstr 7, 8700 Wuerzburg. Fax: Germany +931 201 3934; tel:3954
Newsgroups: vmsnet.networks.desktop.pathworks