HDTenEightyP/NetNews huggingface dataset:
From: nradov@jarthur.claremont.edu (Slippery Jim)
Subject: combining Pathworks and AT&T Star Lan
Keywords: Pathworks, Star Lan
Organization: Harvey Mudd College, Claremont, CA 91711
Date: Thu, 28 Jan 1993 00:58:04 GMT

We have a number of pc workstations networked together using AT&T Star Lan (a
version of Microsoft Lan Manager just like DEC Pathworks).  I would like to
know what the easiest way will be to allow these pc's to access our VMS
servers; it seems as though the two networks should be able to be in use
simultaneously and share most of the software drivers, but then again there
seem to be subtle differences in just about everything.  I would appreciate
any advice before I start trying different configurations.

-Nick Radov (nradov@jarthur.claremont.edu)
Newsgroups: vmsnet.networks.desktop.pathworks
From: houseman@hopper.ACS.Virginia.EDU (Carl Houseman)
Subject: Re: ULTRIX, X-Windows and PATHWORKS for DOS (TCP/IP)
Organization: UVA. FREE Public Access UNIX! 
Date: Wed, 27 Jan 1993 01:19:16 GMT

In article <16B61ADBC.UNF315@rhrz.uni-bonn.de> UNF315@rhrz.uni-bonn.de writes:
>  - Is X-Windows support only available via DECNET, or missed I some=
>    thing to install (may be on the ULTRIX side) ?

Under VMS, TCP/IP support for X-windows isn't turned on by default.
Perhaps something similar applies to Ultrix.

>  - What's wrong with the DECNET transport and a NE2000 card ?
>    (NDIS driver works with TCP/IP, but not with DECNET ?!?)

Network adapters need to change their ethernet address to work with DECnet.
Seems to me that someone else said that NE2000 cards couldn't do that.

>                                                             Uwe Nass
> 
>INTERNET: UNF315@ibm.rhrz.uni-bonn.de (131.220.221.1)

Carl Houseman
houseman@hopper.acs.virginia.edu
GENICOM Engineering
703-949-1323
From: david@lrc.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Help needed with TCP/IP and pathworks.
Date: 27 Jan 93 15:30:19 EST
Organization: Lenoir-Rhyne College, Hickory, NC

We have some software that uses TCP/IP to connect to a computer 
over the internet.  I know that PathWorks can use TCP/IP, but I need 
to know how.

VAX-info:
VMS 5.5-1
Pathworks 4.1
We don't have the TCP/IP software for Pathworks.  We are using DECNET.

My question is where can I get a packet driver for our DEPCA (The old
ethernet cards) and the DE-100 (Newer ones)?  I have heard of some sites on
the internet that have them, but I can't seem to find them.  Can anyone
help or is this a lost cause?  Thanks for your help. 
---------------------------------------------------------------------------
David J. Link                 david@alice.lrc.edu
Lenoir-Rhyne College          
Hickory, NC  28603 (USA)      I make no claims, but God does.
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Problem with Mac LC and DECnet for Macintosh
From: "Sherrie M. Kroll" <KROLL@VICVX1.VIC.UH.EDU>
Date: 21 Jan 1993 15:52:29 -0600
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Hi Everybody,
 
I'm having trouble with a Mac LC after loading DECnet for Macintosh and hope
some of you may be able to help!  First let me say that I am a VAX system
manager and have very little Mac experience, and we have no resident Mac
expert, so please bear with me if my terminology, etc. is not quite right.
 
The server, a VAX 8350, is running Pathworks for Mac V1.1.
The Mac LC originally was running System 6.0.7 with a Farallon EtherMac Card.
 
I installed the network software on the users Mac using the Easy Install.
Everything worked fine.  I was able to use Macterminal and connect to our local
VAX.  A few days later, I installed DECnet for Macintosh.  (The user needed
CTERM to access the cluster on main campus.)  The install was successful.  I
then ran NCP, defined the node, set the DECnet state to be ON at startup, and
defined the node that I wanted to connect to.  When I rebooted, the system
hung during the DECnet initialization.  Subsequent reboots had the same
results. I then booted from a floppy and tried removing DECnet from the system
folder. The system would boot, but I would get system bomb messages at
different times when I would either try to load the Ethernet Phase 2 software
or when I would run the Chooser.
 
We called a tech out from a local company.  He rebuilt the system folder and
the problem still persisted.  He then upgraded to System V6.0.8. to no avail.
 
I had installed DECnet for Macintosh on our test Mac LC a few days earlier and
everything worked fine.  The differences are that the test Mac is running
System 7 and I set the DECnet state off at startup.
 
We will upgrade the user to System 7 if we have to, but if anybody has
any other suggestions, I would greatly welcome them.
 
Thanks!
 
Sherrie Kroll
University of Houston-Victoria
kroll@VicVX1.Vic.UH.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Problems with NET ATTRIB
From: "Gvran Lvwkrantz IM Program AB +46 8-6507525 (0)" <glz@KALLE.IMPAB.SE>
Date: 25 Jan 1993 17:57:46 +0100
Content-transfer-encoding: 7BIT

Hello there!
 
We have a problem with allowing access to a selected file on an application
file service setup as a read-only service to registered users. I want to give
write access to ONE file for ONE user.
 
Setup:
        VMS 5.5-2
        PW/VMS 4.1
        PW/DOS 4.1
        DOS 5.0
        Win 3.1
 
Service is conected '\\kalle\develop%user passwd' on J:. The specific file was
setup using 'NET ATTRIB J:\OSD\X.TST USER /ACCESS=WRITE' and when looking at
the file from either VMS or DOS side the protection is OK, e.i. the user has an
ACE before the PCFS$* ACE's and this ACE should give write access to the file.
The user has write access to the file from his VMS account.
 
It don't work fro DOS! I can't write to the file with any DOS application, not
even edit!
 
As a test I did an 'EDIT/ACL' on the VMS side and added 'EXECUTE+DELETE' to the
ACL and rebooted the PC, but no change. I have also tested changing the
protections for the directory tree, but still no change.
 
Has anyone got this to work?
What's wrong? From the 'Client Command Reference' this should work!
 
Cheers,
        /Goran
 
  Goran Lowkrantz           Email    : glz@impab.se Tel: Nat    08-6507525
  IM Program AB             CompuServ: 100030,347        Int +46 8 6507525
  Fleminggatan 56                                   Fax: Nat    08-6502870
S-112 45 Stockholm,  Sweden                              Int +46 8 6502870
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: conferencing software
From: MARK@AHECAS.COLORADO.EDU
Date: 21 Jan 1993 11:09:56 -0700
X-VMS-Cc: MARK
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Subj:   conferencing software
 
>Does anyone know of any good conferencing software that works with
>Pathworks?  We want to be able to set up discussion topics and allow
>everyone to post public messages to stimulate discussion.  I've
>looked at Vaxnotes, but we really want something PC-based (ideally
>Windows based).  Using mail is not an option, as that would mean
>keeping copies for every user of every mail message, and they would
>also not be organized into topics.  Something more like a BBS would
>be better, but I don't know of any that work with Pathworks.
 
I just recieved a packet of glossies from the request pack out of Pathworks
Network News.  Check with your DECie for info on Pathworks Conferencing.  It is
a Windows based solution that looks like just the ticket for what you are
after.
 
Disclaimer: I don't work for DEC and I haven't seen anything but glossies that
            describe the product, but I looks really nice to me.
 
Mark
 
+-----------------------------------------------------------------------------+
| Mark Montanez                         |        *** Internet ***             |
| Systems Manager, System Programmer    |                                     |
| Information Services, Campus Box B    | ListServ: Mark@ahecas.Colorado.EDU  |
| The Auraria Higher Education Center   | Work: Montanezm@ahecas.Colorado.EDU |
| P.O. Box 173361                       |                                     |
| Denver, Colorado 80217-3361           |                                     |
+-----------------------------------------------------------------------------+
 
GILB'S 4th LAW OF UNRELIABILITY
   Investment in reliability will increase until it exceeds the probable cost
   of errors, or until someone insists on getting some useful work done.
From: nowicki@poplar.egr.msu.edu (Dean Nowicki)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Pathworks and packet drivers
Date: 26 Jan 1993 15:51:29 GMT
Organization: College of Engineering, Michigan State University
Distribution: world
NNTP-Posting-Host: 35.8.14.28
Keywords: PC/FTP, SMC

Hello:
  I haven't had too much experience with this and I'm seeking some advice.
Here at MSU we have a Pathworks network using DEPCA boards. I'm attempting
to find a configuration  that will work for faculty and staff who have
Wester Digital (SMC) boards and use PC/FTP v.2.5 with software such
as POPmail and PCgopher. I haven't been able to successfully load the
SMC packet driver without losing my connection to the system file service.
I've started using dllndis and have successfully used both MACWD.DOS
and SMCMAC.DOS when booting. Are there any suggestions on how to
run both pathworks and PC/FTP (or just load the required packet driver)
with this board?
					Thanks in advance,
					Dean Nowicki
					nowicki@egr.msu.edu
Organization: Rohm and Haas Company
Date: Wed, 27 Jan 1993 18:17:56 EST
From: Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com>
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: File attributes with PCSA USE library

In article <lloyd.728149614@femto.engr.mun.ca>, lloyd@jeeves.engr.mun.ca (Lloyd
Little) says:
>
>Does anyone know if it is possible to change the ULTRIX file attributes
>via some PCSA USE library function call? I need to change the permissions
>of a file created by my program to group:rw. I can do this by logging in
>and doing a chmod, but I would like my program to do this automatically.
>I do not want to change the default permissions of pcsamgr to group:rw
>for obvious reasons.
I'm not sure if this applies to ULTRIX file atributes, but to change the
file attributes on a VMS server you use the NET ATTRIB command. So it is
possible to change VMS file attributes from a DOS machine. I haven't done
any programming with the PCSA libraries, but I would imagine that there
is a call to support this. If all else fails, you could Exec the NET
command, maybe?

>Perhaps I'm using an older version of the USE library? It's version 1.6.27?
>Thanks,
>Lloyd
>--
>Lloyd Little      lloyd@femto.engr.mun.ca

Aengus
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling?"
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: conferencing software
From: Sam Houston <E7OPSAM@TOWSONVX.BITNET>
Date: 24 Jan 1993 11:37:46 -0500
MIME-version: 1.0
Content-transfer-encoding: 7BIT

> Does anyone know of any good conferencing software that works with
> Pathworks?  We want to be able to set up discussion topics and allow
> everyone to post public messages to stimulate discussion.  I've
> looked at Vaxnotes, but we really want something PC-based (ideally
> Windows based).
 
We have looked at some PC based conferencing software from "Group Systems
Software" that works on a Pathworks network.  I think that VAXnotes is
more straightforward for our users.  We have a Notes server on the
VAX and together with sethost or Kermit have setup the numeric keypad
to do all of the functions necessary to read and contribute messages.
We also chose keys that were familiar to our PC users, i.e., all of the
arrow keys function to move about topics and replies as they are labeled,
PgUp and PgDn work, etc.
 
VAXnotes for DOS on the unsupported software disks unfortunately is very
inconsistent with the product on the VAX, especially with respect to the
user interface.  I have only seen a demo of VAXnotes for Windows but I would
guess since its a commercial product it would offer sufficient functionality
and would be a good choice for you PC users using Windows.
 
Sam Houston
Internet:  sam@toe.towson.edu
BITNET:    sam@towsonvx
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: DWDOS386 & DECW$SESSION.EXE
From: "Prof. David Miller" <DMILLER%BSU.DECNET@MSUS1.BITNET>
Date: 22 Jan 1993 15:30:00 -0600 (CST)
Content-transfer-encoding: 7BIT

From: Jeff Silverman <silverm@BCSTEC.CA.BOEING.COM>
 
>My users don't like the session manager that comes with DWDOS386, they wanted
>me to get them something like the session manager that comes with DECwindows
>MOTIF, namely, SYS$SYSTEM:DECW$SESSION.EXE.  Well, okay, a session manager is
>just another X-client, so why not simply set SESSION_MANAGER=NO and specify
>DECW$SESSION.EXE in the DWDOS.INI file (ed note- doen't modify the DWDOS.INI
>file, instead, use a different .INI file and invoke DWDOS386 with the command
>
>DWDOS386 filename.INI
> .... etc
>
>Now for the question: is this feature of the session manager actually a bug?
>It takes a while to reboot the VXT as well, so it would be nice if the session
>manager didn't do that.
 
It makes good sense to me! One benefit is that SYS$SYSTEM:DECW$SESSION.EXE is
documented! :) as opposed to DWDOS386.
 
I'll try it ASAP. Thanks, Jeff.
                                   /-------------------\
Dave.                             ||      /\   *       ||
                                  ||    /    \  /\     ||
DMILLER@VAX1.Bemidji.MSUS.EDU     ||  /_      _\   \   ||
           or                     ||   /      \     _\ ||
DMILLER%BSU.DECNET@MSUS1.BITNET   || /__________\___\  ||
                                  ||      ||    ||     ||
Bemidji (Minn.) State University   \------||    -------/
Newsgroups: vmsnet.networks.desktop.pathworks
From: silverm@bcstec.ca.boeing.com (Jeff Silverman)
Subject: DWDOS386 & DECW$SESSION.EXE
Summary: Discussion of running the VMS session manager instead of the PC version
Keywords: session manager pathworks pc dwdos dwdos386
Organization: Boeing Computer Services
Date: Fri, 22 Jan 1993 06:45:41 GMT

My users don't like the session manager that comes with DWDOS386, they wanted
me to get them something like the session manager that comes with DECwindows
MOTIF, namely, SYS$SYSTEM:DECW$SESSION.EXE.  Well, okay, a session manager is
just another X-client, so why not simply set SESSION_MANAGER=NO and specify
DECW$SESSION.EXE in the DWDOS.INI file (ed note- doen't modify the DWDOS.INI
file, instead, use a different .INI file and invoke DWDOS386 with the command

DWDOS386 filename.INI

that way if you screw up or don't like the results, you can recover easily).
So I did it, and it worked more or less as expected.  I haven't gotten it to
work using the IP transport yet, but then, I am not confident of the IP
transport at all.
The only problem is, well, when you tell the session manager to end the session
it causes the PC to reboot.  This is consistent with the session manager and
a VXT 2000 terminal, also.
So I shot off a note to DSN, and without infringing on their copyrights, they
said that DWDOS is in maintenance so they aren't going to fix it.

If rebooting is acceptable to you, then you can use this trick.  Otherwise,
don't.

Now for the question: is this feature of the session manager actually a bug?
It takes a while to reboot the VXT as well, so it would be nice if the session
manager didn't do that.

Jeff Silverman, Boeing Commercial Airplane
From: wasser@ranger.enet.dec.com (ranger::wasser)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: DWDOS386 & DECW$SESSION.EXE
Date: 26 Jan 93 05:00:18 GMT
Organization: Digital Equipment Corporation
X-Posted-Via: NEWS-NOTES gateway (a hack!)

> set SESSION_MANAGER=NO and specify DECW$SESSION.EXE in the DWDOS.INI 
> The only problem is, well, when you tell the session manager to end the 
> session it causes the PC to reboot.

	The PC should never reboot unless you press Ctrl/Alt/Del.  What
	the VMS Session Manager tries to do is send a "KillClient" request
	for each of the first 32 clients...  This usualy kills every 
	application in use.  It then puts up the VAXstation login screen
	(big DIGITAL logo and username/password edit fields).

 	The reboot sounds like a bug in PC DECwindows Motif or something 
	bad in the memory manager configuration on the PC.  Call Digital 
	customer support and ask if PC DECwindows Motif V4.1-2  (that's 
	"dash two") is available yet.  That might fix the reboot problem.
	The bug fix release includes DWDOS286.EXE, DWDOS386.EXE and
	PCX_VAX.VMS (the last being for TCP/IP REXEC to VAX/VMS/UCX V2.0).

	The only way to shut down PC DECwindows Motif with the internal
	session manager disabled is to press Ctrl/Alt/F10...  Anything
	else (except a warm boot: Ctrl/Alt/Del) leaves (or SHOULD leave)
	the server running.

	I presonally never shut down my DWDOS386 running DECW$SESSION.  
	When I go home at night I use the PAUSE feature of DECW$SESSION to
	hide the screen and turn of power to the monitor to save energy.
	If I want to shut down (like over a long weekend or vacation) I
	would use Ctrl/Alt/F10 or use the EXIT button on the PC Session
	Manager which I do not disable.

> Now for the question: is this feature of the session manager actually a bug?

	Sounds like a bug somewhere.  With luck the 4.1-2 release will
	fix it.

	Note that early versions of the VMS Session Manager did not work
	at all well for remote nodes but I have had no problem with
	VMS 5.5-2.

					-John A. Wasser
					 The Last Programmer
					 PC DECwindows Motif
					 Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
From: toa@regent.e-technik.tu-muenchen.dbp.de (Tobias Abthoff)
Subject: Re: Connection to Pathworks file service without using windows file mg
Organization: Technical University of Munich, Germany
Date: Tue, 26 Jan 1993 09:06:08 GMT

>Sorry for including the whole article just to pick up on this point, but
>you shouldn't have any problems running USE in a DOS window (at least I
>don't!) The lack of a simple WINUSE app is a bit of a pain, but that's
>a seperate issue entirely. Your current DOS batch jobs, USE commands and
>all, should work.

>(I've no idea if DEC say they should or shouldn't work, but from a purely
>empirical point of view, USE 4.1.23 works in a Windows 3.1 DOS window.
>Maybe I'm just lucky, but I get to sit at a lot of different desks, and I
>don't think I've ever had problems using USE from a DOS prompt. I prefer
>to use USE because if I'm working on someone elses machine, and I use
>File Manager to connect to another drive, then the automatic reconnect feature
>will cause unecessary prompts if I forget to disconnect).

You are just lucky. The Problem is not the USE Command. This works
very well in a DOS-Box. The Problem is Windows which is not 
aware of new connection you have made.
This might get you in *sometimes* in some trouble. You will get
a message like "Your applikation was communicating on the network
when it was terminated - please restart windows"

tobias


---------------------------------------------------
abthoff@regent.e-technik.tu-muenchen.de

A
A
a message like
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Problems with NET ATTRIB
From: "Carlos Sainz <*> (305) 284-3565" <CSAINZ@UMIAMI.BITNET>
Date: 25 Jan 1993 14:22:52 -0500
X-VMS-Cc: CSAINZ
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Hello there!
 
> We have a problem with allowing access to a selected file on an application
> file service setup as a read-only service to registered users. I want to give
> write access to ONE file for ONE user.
  ..
  ..
  ..
 
> As a test I did an 'EDIT/ACL' on the VMS side and added 'EXECUTE+DELETE' to th
   e
> ACL and rebooted the PC, but no change. I have also tested changing the
> protections for the directory tree, but still no change.
 
Do you have a APPLICATION file service or a COMMON file service?
 
According to the Server Administration Guide in the chapter for "Managing
File Services" (ver. 4.1) it says that in COMMON file services you control
access to individuals files as well as to the file service, but in APPLICATION
file services you only control the access to the file service.  Individual
files within the APPLICATION file services are the same as the service.
 
Carlos.
 
Carlos J. Sainz
Academic Services Manager
----------------------
BITNET   : CSAINZ@UMIAMI                PHONE  : (305) 284-3565
INTERNET : csainz@umiami.ir.miami.edu
Newsgroups: vmsnet.networks.desktop.pathworks
From: houseman@hopper.ACS.Virginia.EDU (Carl Houseman)
Subject: Re: Prowrite V2.2 on Pathworks 4.1a
Organization: UVA. FREE Public Access UNIX! 
Date: Wed, 27 Jan 1993 01:45:49 GMT

In article <E8692F8720007467@ewuvms.bitnet> LRICHARDS@EWUVMS.BITNET writes:
>We have Prowrite ver 2.2 on local harddisks on 486s running under Pathworks
>4.1a served by a VAX 4000.  We are printing to a DEC LPS20 turbo.  Everything
>works fine except after a job is sent to the printer thru Prowrite you have to
>exit the program and reenter it in order to print again.  Is anyone out there
>using prowrite v2.2 on your systems and gotten it to work properly?  We did
>have it on the server in a Common file service where we have all our DOS
>applications but couldn't come close to getting it to run there, so we moved it
>to the local hard drives.  Thanx in advance.

This is a common problem for those unaccustomed to using network printers.
Your software believes it is sending to a REAL PARALLEL PORT.  Tell your
software it is using a "DOS device" or something similar that you can select
when configuring the printer device.  If it doesn't allow you to print to
a "DOS device LPT1:" for example, or to print to a file called LPT1, then
your only resort is the PSC utility that comes with Pathworks.  See page
2-39 in Client Commands Reference (Pathworks 4.1 doc set).

>Larry Richards, Manager, University Computing Labs
>Eastern Washington University
>Bitnet:lrichards@ewuvms
>Phone: (509)-359-7985

Carl Houseman
houseman@hopper.acs.virginia.edu
GENICOM Engineering, Waynesboro, VA
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Problem with Mac LC and DECnet for Macintosh
From: "Sherrie M. Kroll" <KROLL@VICVX1.VIC.UH.EDU>
Date: 25 Jan 1993 15:00:04 -0600
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Thanks to all those that responded to my problem of DECnet hanging a Mac LC.
Today we backed up the disk, trashed the system folder and started from
scratch.  After rebuilding the system, I re-installed the network software
with the Easy Install, re-installed DECnet for Macintosh, and ran NCP to
define my node, etc.  All this is exactly as I had done before EXCEPT the
DECnet startup state was OFF.  Everything works wonderfully.  I haven't been
brave enough to try starting the Mac with the DECnet startup state on...
I think I'll leave well enough alone for awhile!  Thanks again to those that
responded.
 
-- Sherrie Kroll
   University of Houston-Victoria
   kroll@VicVX1.UH.EDU
From: bats@utrtsc.enet.dec.com (utrtsc::bats)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Get yourself the White Paper form DEC
Date: 26 Jan 93 05:00:39 GMT
Organization: Digital Equipment Corporation
X-Posted-Via: NEWS-NOTES gateway (a hack!)




	Get in contact with either your CSC or look on Compuserve
	(GO DECPCI) and get the White Paper on running Windows for 
	Workgroups on top of DECnet (PATHWORKS).
	Note that it's a Postscript document.

	If you follow this, it will work without a problem.
	(Typing this from a WfW DECnet/NetBEUI/IPX/IP based station)

	Pjotrr Batzz
	DeskTop Expertise Centre
	Digital Netherlands
Newsgroups: vmsnet.networks.desktop.pathworks