HDTenEightyP/NetNews huggingface dataset:
From: hamilrk1@bisdpo1.bisdnet.jhuapl.edu ()
Subject: Printing from Lotus 1-2-3 (DOS app in WIN31) drops file services
Reply-To: hamilrk1@bisdpo1.bisdnet.jhuapl.edu ()
Organization: Johns Hopkins University Applied Physics Lab
Date: Wed, 11 Nov 1992 22:30:01 GMT

 A co-worker writes:

+ Joe Nobles left me a message which indicated that Dan Dearborn (BPS) was 
+having trouble printing LOTUS 1-2-3 files.  I stopped by and briefly 
+witnessed the problem:

+Dan is using Lotus 1-2-3 release 2.2 (under Windows) and a large macro which 
+formats his output.  When he prints a document, it freezes the machine.  He 
+can then terminate LOTUS 1-2-3 (usually), but receives an error message from 
+Windows indicating that it can no longer access network drives.  Eventually, 
+the entire machine locks up, forcing him to reboot.  I was not able to 
+examine his machine further, as he was busy and was not willing to give it 
+up. He mentioned that he would be able to let someone work on the machine on 
+Tuesday afternoon at 1pm, when he will be in a class.

+Since I won't be in next Tuesday, would you be able to (jointly) work on the 
+problem?  It sounds as if it might require both Lotus expertise and 
+Pathworks expertise.  


I have confirmed that the network drives are PATHWORKS file services.
PATHWORKS for DOS V4.1, PATHWORKS for VMS V4.1, Windows V3.1 and Lotus V2.2 
are the products. The version of Lotus is old and where I suspect the problem 
is. Others think that the problem is PATHWORKS.                  

Ideas?

-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
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
From: chiam@VULCAN.CBA.OHIOU.EDU (Ta Fuh Chiam)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Still problems writing to disk and file services
Date: 11 Nov 92 20:38:30 GMT
Content-transfer-encoding: 7BIT

>        I can create directories when I login to VMS.  I can only do this using
>the system account since that is the only account with privileges to those
>directories.  When I sign on to the file service using my VMS usercode, I can
>create files but again, when I create directories, no error message but the
>directory does not get created.
 
Sounds like you have a file/directory protection set incorrectly. It could very
well be ACL too.
 
Ta Fuh Chiam
============================================================================
Ta Fuh Chiam
Ohio University, College of Business Administration / Phone: (614)593-2088
Management Information Systems                        FAX:   (614)593-0319
Copeland Hall 22                   INTERNET : chiam@vulcan.cba.ohiou.edu
Athens, Ohio 45701, U.S.A.            or    : chiam@ouvaxa.ucls.ohiou.edu
                                   BITNET   : CHIAM@OUACCVMB
                          Use my first Internet address if at all possible.
Disclaimer: What I have said are my opinions, not of anyone else.
============================================================================
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: 10BaseT Cards for MCA (PS/2)
From: "KEN HARRIS (MIS9230) (410) 455-3934" <MIS9230@UMBCADMN.BITNET>
Date: 11 Nov 1992 08:58:00 -0500 (EST)
X-VMS-Cc: MIS9230
Content-transfer-encoding: 7BIT

We are in the process of connecting several IBM PS/2s to our PathWorks
network.  For our PCs, we are using 3COM and DEPCA cards.  We are now
looking for cards for IBM's MCA.  3COM makes an MCA card, but it seems
a bit expensive.  Has anyone had any experience with any other brand
of card?
 
Thanks in advance for any information,
 
Ken Harris
UMBC
From: LAGAN_TJ%VENUS.decnet@APG-EMH7.ARMY.MIL (VENUS::LAGAN_TJ)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: <None>
Date: 9 Nov 92 20:53:00 GMT
Content-transfer-encoding: 7BIT

subscribe pcsa-l lagan_tj
Newsgroups: vmsnet.networks.desktop.pathworks
From: khan@pslu1.psl.wisc.edu (Mumit Khan)
Subject: Re: Windows for Workgroups
Organization: Physical Sciences Lab, University of Wisconsin
Date: Mon, 9 Nov 92 20:06:00 GMT

In article <1992Nov9.120606.57@dmdscs.com> jrkdmd@dmdscs.com (Joe Krulewicz) writes:
>Does anyone know if PATHWORKS is Compatible with Microsofts NEW
>Windows for workgroups?  I sure would like the peer to peer PC networking
>together with PATHWORKS
>
>Thanks!
>jrkdmd@dmdscs.com


This might be of general interest, so please post if you get any info via
email.

mumit -- khan@xraylith.wisc.edu
Newsgroups: vmsnet.networks.desktop.pathworks
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Subject: RE: Still problems writing to disk and file services
Organization: Digital Equipment Corporation
Date: Fri, 13 Nov 1992 05:00:29 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                   Helen Strother <STROTHHM@SNYONEVA.BITNET>
>               Still problems writing to disk and file services
>
>        I am narrowing down the reasons why I can't write to my file or disk
>services but do not know a solution.  Sorry if these are simple problems but I
>have looked through the manuals and can't find any answers.
>        A little bit of history first.  I created some file and disk services
>and everything worked fine for about a week.  At some point, quotas were
>enabled and I was no longer able to write to the services even though I had the
>correct privileges.  We've fixed that problem but since the disk that the
>services are on is the system disk, I've been asked to move them to another
>disk which has caused a new set of problems.
>        I have created a file service on the second disk giving myself and
>group PUBLIC RWC access.  When I sign on to the file service using my VMS
>usercode, I can create files but I can't create directories.  My quota on this

    When you use diskquotas on VMS with PATHWORKS, make sure that both
    
        PCFS$ACCOUNT
        
    and
    
        SYSTEM
        
    have enough diskquota on the devices (SYSTEM is important, since it
    usually becomes the owner of directories - what affects this is who
    owns 000000.DIR in 'disk:[0,0]'.
    
    Besides diskquotas, of course, PCSF$ACCOUNT and/or whatever accounts
    are used to connect to services, of course have the access you wish
    them to have granted through PCSA_MANAGER?
    
    Also note: When moving file services from a disk to another, use
    VMS BACKUP to copy the directory structure. A straight COPY from
    DCL does not copy the necessary ACL's. After copying, remove the
    service, add it back with a new 'root' and, if necessary, make 
    sure the correct access has been granted to whomever should have
    (whatever ;-) access.

    Disk services are not affected by diskquotas, the only thing that
    governs this is whether the service (the LAD container) is mounted
    with read-only or write access (with or without a password).
    
    And if a disk service is mounted read-only, nobody will be able to
    write to it.
    
    If a disk service is mounted for writing, only the first one that
    connects to it for writing will have access to it - no other connections
    are possible at that point.
        
    ...petri (petri.backstrom@ljo.mts.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: unable to connect to disk service (3.1) & file service (4.1)
From: "(bachism)" <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 12 Nov 1992 08:31:14 -0500
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"

Look at Pathworks Manager in VMS to ensure your user has access.  Try granting
that user access and see it that solves your problem.
Newsgroups: vmsnet.networks.desktop.pathworks
From: janderson@vax (Jim Anderson - Systems Manager - x2082)
Subject: Re: Printing to HP LaserJet IIISi with LAT
News-Software: VAX/VMS VNEWS 1.41    
Organization: Williams College Center for Computing
Distribution: usa
Date: Wed, 11 Nov 1992 22:50:00 GMT

In article <9211111909.AA23122@eunice.ssc.wisc.edu>, gasser@SSC.WISC.EDU (Kyle Gasser) writes...
> 
>        Setting it up in PostScript is fine, setting it up to take ASCII is
>great.  Is there anyone out there who can print send either an ASCII or
>PostScript file to a queue with a IIISi waiting on the end, and have the
>printer discern whether the job is ASCII or postscript?  The printer needn't
>be a HP, but anyone had success doing it?  A simple yes or no answer would
>be dandy.
> 
>        Kyle R. Gasser
>        Center for Demography and Ecology
>        University of Wisconsin-Madison
>        Madison, WI

Got is up and running here.  Need a postscript "preprocessor" symbiont on the
vax end.  Usd a 3rd party one here.  Also need to set up a device control 
library to hand the escape sequences to do the autoswitching.  Successfully 
printed ascii from the pc via pathworks, ps out of Interleaf via PW and ascii 
and ps from the vax, all items "queued" in the queue with printer flipping 
between ps and pcl.

Jim
From: CF0@PSUALT.BITNET (Craig Farrell)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Cabletron network cards
Date: 11 Nov 92 21:00:00 GMT
Content-transfer-encoding: 7BIT
Original_To:  PCSA

I have two IBM 55SX systems that are on a Pathworks network.  Both
have the same hardware specs.  One has a Cabletron E3020-X and
the other has a E3112-X card.  I have noticed the E3112-X seems
slower.  It is the newer of the two cards.  I downloaded the
lastest NDIS drivers and this didn't make a difference.
 
When starting SETHOST, which is on a system file service, it
loads alot slower in the machine with the E3112-X card.  I even
placed the machines side by side and used the same network
connection to isolate the problem.  I wondering about setting
in protocol.ini file that might effect performance.  I don't
notice this in a 56SLC but it is much faster than a 55 to
begin with.
 
Any ideas?
 
       Craig Farrell                       Penn State Altoona Campus
       CF0@PSUALT.bitnet                   225 CLRC Building
       (814) 949-5295                      Altoona PA,  16601
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Local hard disk as a service?
From: TILLOTSON@ALISUVAX.BITNET
Date: 04 Nov 1992 11:51:43 -0500
MIME-version: 1.0
Content-transfer-encoding: 7BIT

     HOWDY!
 
     Look under PERMIT.  The syntax is:
 
          PERMIT {alias}={directory} {nodename}
 
     Then from the PC with the decnet address {nodename}:
 
          NET USE ?: \\{nodename of PC offering service}\{alias}
 
     NOTE:  The PERMIT command will tie up the PC until either
     you hit <cntl-break> twice or until a connection is made
     and then dropped.  However, I have heard of people doing
     this inside of a windows in Windows, but I would suggest
     you have a fast machine before attempting this.
 
     We use this command mainly to copy an entire harddrive from
     one computer to another.  It isn't very useful for everyday
     file sharing.
 
     Jenett Tillotson
     Ames Laboratory
     TILLOTSON@ALISUVAX.BITNET
     (515) 294-7908
Newsgroups: vmsnet.networks.desktop.pathworks
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Subject: RE: Remote boot with NDIS and PW DOS (TCP/IP)
Organization: Digital Equipment Corporation
Date: Wed, 11 Nov 1992 05:01:03 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                       les@sscl.uwo.ca (Les Flodrowski)
>                   Remote boot with NDIS and PW DOS (TCP/IP)
>
> I have a couple of question that maybe a Digital listener might answer...

    It is possible. ;-)
    
> 1. Does the Pathworks for DOS (TCP/IP) product require the use of NDIS to
>    work?

    Yes.
    
> 2. Is it true that NDIS is not supported when using Remote Boot?

    Yes.
    
> 3. Therefore, is it true that PW DOS (TCP/IP) cannot be used by clients
>    which remote boot? (If so, then why doesn't the SPD just state that
>    remote boot is not supported when using this product).

    Yes. I don't remember reading the SPD very carefully, but if, indeed,
    it isn't stated, it is an obvious omission. I'll make sure the product
    manager is aware of this.
    
> 3A. Why can't NDIS be used with remote boot?

    Because the current mechanism doesn't allow for this. However, we are
    looking into this flaw in our remote boot strategy... In other words,
    hopefully a future PATHWORKS release no longer has this limitation.
    
> 4. Assuming one has PW DOS and PW DOS (TCP/IP) running, can both TCP/IP
>    and DECnet protocols such as DECnet and LAST be used simultaneously.

    Yes, provided you're not remote booting ;-) However, the crude NETSETUP
    utility that lives with a lot of old baggage cannot be used to configure
    such a setup; i.e. you have to do it by hand.
    
    Additionally: It is not officially supported by Digital, beacuse of
    the above reason + the fact that the TCP/IP EMS usage is not compatible
    with the DECnet EMS usage, and because this type of configurations have
    not been fully tested.
    
    But, in any case, conventional memory permitting, it works just fine. ;-)
    
    We've posted sample configurations on your CompuServe forum DECPCI in the
    file STACKS.ZIP. Your Digital Customer Support Center should also be able 
    to provide them to you if you don't have a CompuServe account (we have no 
    Internet access to the file).
    
    ...petri (petri.backstrom@ljo.mts.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
From: dsrekrg@prism.gatech.EDU (Rob Gibson)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: <None>
Date: 12 Nov 92 23:03:57 GMT
Organization: Georgia Institute of Technology

In article <01GQPL651JDS0000CX@vax1.may.ie> PPENDER@VAX1.MAY.IE writes:
>Hello,
> 
>I'm also looking for information about Tektronics emulation programs available
>for ethernet users with the facility to screen dump to postscript printers.
> 
Zstem 240 from Kea Systems emulates a Tek 4014 and screen dumps to printers
like IBM Graphics printer, HP Laserjet, etc. and dumps to TIFF files,
but the v2.3 release form 1990 that we have does not support Postscript.
Maybe they do now.

Kea Systems
3738 North Fraser Way, Unit 101
Burnaby, British Columbia
CANADA  V5J 5G1

FAX: 604-431-0818
-- 
Rob Gibson, WREK 91.1 MHz, 40000 watts - Georgia Tech, Atlanta Georgia, 30332
Studio: 404/894-2468  FAX: 404/853-3066  ARPA: dsrekrg@prism.gatech.edu
From: RONAU%CUTTER%OPUS@MCOIARC.BITNET
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Gateway 486DX2E on Pathworks
Date: 5 Nov 92 19:18:00 GMT
Content-transfer-encoding: 7BIT

50 MHz
 
Yes we did get one of those EISA beast running.  Not happily though.
The Award bios takes up from E000-ffff.  The video takes a000-c7ff.  The
SCSI takes c800-cbff.  The depca took all of D.  Only 16k of c left.  No
room for expanded memory.  We sent it back.  We were using PCSA 3.0
client.  Not enough memory left to do much.
 
 
 
 Theodore F. Ronau                  ------------------------------------------
 Network & Small System Manger      | DOS 5.0, Windows 3.1, Pathworks for DOS|
 Information Systems                | Pathworks for OS.2, Pathworks for Mac, |
 Medical College of Ohio            | Word for windows 2.0, WordPerfect 5.1, |
 (419)-381-3601                     | Excel 4.0, Lotus 3.1, Lotus 2.4, ....  |
 Bitnet: Ronau@mcoiarc              | Where does it all end?                 |
 Internet: Ronau@OPUS.IARC.MCO.EDU  ------------------------------------------
Newsgroups: vmsnet.networks.desktop.pathworks
From: egntoh@ntuix.ntu.ac.sg (Toh Guan Nge)
Subject: Re: PATHWORKS TCP/IP on Intel EtherExpress Card
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 13 Nov 1992 07:58:47 GMT

bachism (BACHISM@JHUDEV.DEV.JHU.EDU) wrote:
: Maybe it can't find you HOSTS file.  In protocol.ini you have it specified for
: the A drive.  Are you booting from the A drive when you have this problem???
: The other thing is to make sure there is a Blank line after the last host in
: this file otherwise it will only be able to connect to the first one listed.

Yes, I booted the pc from A drive. and hv the right HOSTS file. What puzzle me
is the INtel card can be installed to work with DECNET successfully but not
TCPIP, even using the same NETSETUP program from the same server. I hv also
done that with a WD8003 card, with both DECNET amd TCPIP run concurrently.
The only different between the two cards is the WD8003 has RAM on card while
the Intel EtherExpress has none.

--
Toh Guan Nge, School of EEE,
Nanyang Technological University, Singapore
Internet Email: egntoh@ntuix.ntu.ac.sg
Bitnet   Email: egntoh@ntuvax.bitnet
Newsgroups: vmsnet.networks.desktop.pathworks
From: aswin@nimbus.worldbank.org (Aswin Kokilananda, 885/72)
Subject: Re: Station Address and the Ethernet Packet
Reply-To: aswin@nimbus.worldbank.org
Organization: Sun Microsystems, Inc.
Date: Tue, 10 Nov 1992 19:40:37 GMT

In article K6n@mtholyoke.edu, mcrowley@mtholyoke.edu (Michael A. Crowley) writes:>

>If you are in an NDIS situation and wish to change the
>hardware address to correspond with the station address
>(   c:\> use /status  )
>you could enter something like this for the netaddress line
>in the protocol.ini file.  This is something needed when,
>for example, using both, IBM PC support and Pathworks.
>(Of course this would be a local boot situation.)
>
>------------------
>; PROTOCOL.INI file create by DNETOMO.V41 V4.1.060
>;                         via DNETWIK.V41 V4.1.047
>
>[protocol manager]
>DRIVERNAME = PROTMAN$
>
>[ELNKMC.DOS]
>DRIVERNAME = ELNKMC$
>MAXTRANSMITS = 20
>NETADDRESS = AA000400BBB6
>.....
>------------------

This NETADDRESS works fine on most of 3COM's ethernet cards (had problem with only 3c507). 
Could not get it to work on any of the Digital Etherworks family of ethernet cards. 

Any idea, anyone ? Is something wrong with DEC's NDIS driver ?
 
Few years back I made the mistake of purchasing a bunch of DEC ethernet cards, running Pathworks 
only is OK, now we need to run multiple protocols (TCP/IP with Decnet) on the Desktop so we need to use 
NDIS and the NETADDRESS scheme.

Looks like we'll just have to replace DEC's ethernet cards with 3COM's.

aswin@nimbus.worldbank.org
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: DEPCA.DOS running DUAL Protocols
From: "(bachism)" <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 11 Nov 1992 15:24:32 -0500
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"

A few days ago I saw a message about a problem getting the DEPCA to run dual
protocols using the enhanced redir.  I currently have all 3COM and only 2 DEPCA
at one site which is to run TCP/IP and NETBEUI allowing me to access the file
services using both protocols.  I had not problem configuring the 3COM card but
I too am having trouble configuring the DEPCA.  It does not load NETBEUI.  Has
anyone goto the DEPCA to run dual protocols and if so how can I get a copy of
the software driver (I am assuming that that is where the problem lies.)
 
 
BACHISM@JHUDEV.DEV.JHU.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
From: wasser@ranger.enet.dec.com (ranger::wasser)
Subject: Just different versions of the same thing.
Organization: Digital Equipment Corporation
Date: Wed, 11 Nov 1992 05:00:24 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

> If someone has a little time, could you compare/contrast the three
> terms/systems:  DECwindows, Xwindows and MOTIF.

	The X Window System (currently Version 11, Release 5) was 
	developed at MIT as part of Project Athena.  It defines
	the X Window System Protocol, the X Interface Library
	which gives low-level access to the X Window System Protocol
	and defines a user interface toolkit which defines the
	programming interface to a set of control objects (buttons,
	scroll bars, etc).

	DECwindows defined a toolkit and a user interface specification
	layered on the X Window System Protocol.   It is a product of
	Digital Equipment Corporation.

	Motif defines a different toolkit and user interface specification
	that is also layered on the X Window System Protocol.  It is
	a specification owned by the Open Software? Foundation (OSF).

	Since the X Toolkit, DECwindows Toolkit and Motif Toolkit are
	all layered on the X Window System Protocol, they can all
	co-exist on an X Window System Server.  Each application will
	have the user interface of the toolkit it is written with.
	The window controls will have the user interface of the
	toolkit that the Window Manager is written with.  You can
	have a Motif Window Manager managing DECwindows applications
	and vice-versa.

				-John A. Wasser
				 Project Leader
				 PC DECwindows Motif V4.1
From: fuhrman@litsun.epfl.ch (Cris Fuhrman)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: PATHworks for Macintosh on a Quadra (built-in Ethernet)?
Date: 13 Nov 92 10:55:50 GMT
Followup-To: vmsnet.networks.desktop.pathworks,comp.sys.mac.comm
Organization: Swiss Federal Institute of Technology

In article <1992Nov13.043430.19685@dms.agames.com>, petrick@dms.agames.com
(Jim Petrick) wrote:
> 
> We have been trying to hook up PATHworks on our new Quadra but are having no
> luck.  If DECnet is run with the standard System 7.0.1 (Tuned-up), it freezes
> at boot time.  If I install the new Networks Product upgrade that comes with
> the Quadra (upgrade for Quadra 700 and Appletalk V57.0.3 (I think that's the
> version)), the Mac will crash during boot and just go into an infinite restart
> -crash-restart... loop.  Can anyone help me?  We're using PATHworks 1.1, by
> the way.

Can't help you with the DECnet for Mac problem. However, holding down the
Shift key on the boot in System 7 will cause the Mac to *not* load the
extensions (so you can then remove DECnet from the system folder).

---------------------------------------
 Cris FUHRMAN, fuhrman@litsun.epfl.ch
 Laboratoire d'informatique technique
 EPFL-LIT, IN Ecublens, CH-1015 Lausanne, Switzerland
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Windows for Workgroups
From: GREG BEAN 410-455-2580 <MIS9000@UMBCADMN.BITNET>
Date: 10 Nov 1992 08:44:00 -0500 (EST)
X-VMS-Cc: MIS9000
Content-transfer-encoding: 7BIT

Greetings!
 
There have been a few messages posted that indicated limited success with
the installation of Windows for Workgroups and Pathworks. What specifics
can you offer on your configuration? What version of Pathworks are you using?
Are there limitations with the enhanced redirector? What choices did you make
in the WFW setup? What mods to config.sys, etc.? What services do you add,
what do you lose?
 
Where is DEC with their "coexistence"?
 
Thanks,
Greg
 
-----------------------------------------------------------------------------
Greg Bean                                   E-Mail: Greg_Bean@UMBCADMN.BITNET
Director of Administrative Computing        Tel: (410) 455-2580
University of Maryland Baltimore County     Fax: (410) 455-1069
-----------------------------------------------------------------------------
Newsgroups: vmsnet.networks.desktop.pathworks