HDTenEightyP/NetNews huggingface dataset:
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: WordPerfect 5.1 and PW
Date: 9 Apr 92 04:00:22 GMT
Organization: Digital Equipment Corporation
X-Posted-via: NEWS-NOTES gateway (a hack!)

>       f71839389@milori.ccit.arizona.edu (D R Friedman Release 1 Versio
>                            Wordperfect 5.1 and PW
>
>I would like some experiences on how I get Worpderfect to recognize the
>queues on the VAX to Wordperfect.
>
>The USE lptx:\\node\queuename
>seems to be not working with wordperfect.

    The queue is there? You can print to it from DOS and/or other applications
    and/or the server? Or is it just WP that fails?
    
    Is it a network or a standalone version of WP? If it is a network 
    version, what network did you choose when you installed it (hopefully 
    PCSA/PATHWORKS ;-)?

    WP is set up to print to the correct LPTx: port? With a printer driver
    that corresponds to the actual printer behind the queue?
    
    What exactly does "seems to be not working" mean? What happens? Any
    error messages? Anything in the file server's spool directory? Anything
    in the file server's log file?

    I.e. more details is needed to really know what's going on and what is
    failing.
    
    To my experience WP works just fine in a PATHWORKS environment.
    
    The only "special" things with WP to remember is that you shouldn't
    load the Redirector to HMA (or "XMS" as NETSETUP calls it); load it 
    high if you want (and have a free 35KB UMB). Also increasing the
    Redirector print buffer size(s) helps in speeding up printing from
    WP (other applications I haven't seen suffering from the defaults
    of 128 bytes). Change with the /P1:, /P2: and /P3: qualifiers to
    the Redirector (in STARTNET.BAT) or with NETSETUP (which'll change
    the qualifiers for you ;-).

    Oh, and older, non-network versions of WP tended not to start the
    print job until one exited the applications. Workarouds: pressing
    <Ctrl/Alt/PrtScreen> or <Ctrl/Alt/*> depending on your keyboard,
    or specifying in WP that you want to print to a file and say the
    filename is LPT1 or LPT2 or LPT3 (without colons). And in PATHWORKS
    for DOS V4.0 and onwards the PSC/PRTSC utilities could be used.
        
    ...petri (backstrom@ranger.enet.dec.com)
       Personal Computing Systems Group
       Digital Equipment Corporation
From: dorenbos@research.ptt.nl (Marcel Dorenbos, C3, tfn 070-435127)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: What does JOB_CONTROL do on a VMS machine?
Date: 10 Apr 92 14:58:28 GMT

Hi NETworkers,

On two different PATHWORKS servers we see a different load of job control. We 
donot know the reason for this and if any of you can give us a glue, please 
help us. I am also interested in the tasks of job control.

On our site we are running PATHWORKS on two 4000-300 machines. These machines
are part of a fairly large LAVC (6620, 8810, 8700, about 25-30 3100 and a 
few uVAX). The 4000 machines have their own system disks shared on the DSSI 
bus (the system disks are shadowed). Both machines have approximately the same
load (about 100 PC's each machine). Machine 1 needed about 4 minutes CPU time
for job control versus 8 hours for machine 2!!!
I can give you more information if you need more information about our 
configuration.

Many thanks,

Marcel Dorenbos
PTT Research - the Netherlands
M.C.M.Dorenbos@research.ptt.nl
phone (0)70-3325127
-----------------------------------------------------------------------------
Machine 1: (output of show sys command)
VAX/VMS V5.4-2  on node DNLSR1  10-APR-1992 15:39:58.43   Uptime  6 16:02:14
  Pid    Process Name    State  Pri      I/O       CPU       Page flts Ph.Mem
29E0008C JOB_CONTROL     HIB     10    34915   0 00:04:22.66      8377    437   
                                               ^ ^^ ^^ ^^ ^^
29E0008D SHADOW_SERVER   HIB      5        6   0 00:00:00.03        73    136   
29E0008F NETACP          HIB     10    14434   0 00:07:32.51      1190   1186   
29E00092 LAD$KERNEL      HIB      9      407   0 00:00:01.15       187    298   
29E00093 NETBIOS         HIB      9    15859   0 00:00:05.95       147    254   
29E00096 PCFS_SERVER     HIB     10  1704052   0 04:03:35.81    126006  44119   

=======================================

Machine 2: (output of show sys command)
VAX/VMS V5.4-2  on node DNLSR2  10-APR-1992 15:40:08.34   Uptime  6 16:06:17
  Pid    Process Name    State  Pri      I/O       CPU       Page flts Ph.Mem
29C0008C JOB_CONTROL     HIB      8  4681166   0 08:07:31.83     15964    446   
                                               ^ ^^ ^^ ^^ ^^
29C0008D SHADOW_SERVER   HIB      4    18619   0 00:00:18.31        89    257   
29C0008F NETACP          HIB     10     5280   0 00:00:20.78      1015   1154   
29C00092 LAD$KERNEL      HIB      9      898   0 00:00:02.93       128    239   
29C00093 NETBIOS         HIB      9    15888   0 00:00:05.80       147    254   
29C00096 PCFS_SERVER     HIB      9  4897514   0 07:25:31.44    199507  44505
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Post Script Printing
From: DUG@CZHETH5A.BITNET
Date: Fri, 10 Apr 1992 14:30:00 N
X-Original-To:  LANWORKS@MIAMIU, DUG

Comment: Mail not returnable through this path, use the list address
 
Author: AEOLUS::NOTES3B "Dillier Norbert"
Topic 1000.1
Time: 10-APR-1992 09:12 ZRH
 
    -< problems with postscript cartridges >-
 
    We have encountered similar problems some time ago with a HPLJ IIp and
    a pacipic page postscript cartridge. A temporary solution was to print
    the long documents in shorter pieces. In the meantime we have switched
    to HP-postscript cartridges and did not encounter any problems so far
    even with "very long" documents including lots of graphics.
    Make sure you have enough memory in your printer (at least 2.5 megs)
    N.Dillier, ORL-USZ, Switzerland
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Shared local printers via LAT
From: "Jon Sonntag (LutherNet)" <SONNTAJM@CRF.CUIS.EDU>
Date: Mon, 13 Apr 1992 17:56:00 CDT
X-Organization: Concordia University Information Systems, River Forest, Il.
X-VMS-Cc: SONNTAJM

>>Problems with shared local printers as LAT-Services:
>>
>>We have been able to set up local printers (connected to DOS-PC's via a
>>parallel port, e.g. LPT1) as Pathwork-Printer-Services via LAT (see below
>>for a step-by-step description).
>>The printers are HPLJIIp with postscript emulation. We can print text and
>>graphics from any PC in the net as well as from the host to these local
>>printers without problem once the system has been set up correctly.
>>However, after powering down the local PC or the printer the VMS-printer-
>>queue stops and will not restart once the PC is back on the net.
>>We have checked that the local LAT is working correctly and that
>>      USE LPT1: /CHECK
>>indicates "printer OK". The only way to restart the queue seems to be the
>>DCL-command "start/que locprt".
>>
>>We have - as a temporary solution - put a
>>     "NFT SUBMIT "system password" node::[sysmgr]restart_queue.com"
>>command in the local AUTOUSER.BAT network-startup-command which is
>>undesirable because it requires operator privilege and a system password.
>>
>>Does anybody have a better solution for this problem?
>>.......
>>Status report:
>>
>> Printer        PC on LAN       Queue           Jobs in Queue
>> -------        ---------       ------------    -------------
>>    On              Yes         Running         Normally proceed
>>    Off             Yes         Stalled         "Printing"
>>    Off             No          Stopped         Retained on Error
>>
>>The 3rd case is probably the most common problem: powering the printer on
>>and reconnecting the PC to the LAN has no effect on the queue: it will
>>remain "stopped" forever unless the DCL Command:
>>        $ start/queue Queue-Name
>>is entered. The jobs in the queue are "retained on error".
>>
>>Norbert Dillier, ENT-Department, University Hospital, Zuerich, Switzerland
>>E-Mail: K365710@CZHRZU1A.BITNET
>How about an ACL on the queue and grant the identifier to the user.  He or
>she can then control the queue and the submit command would have their pass-
>word and not the system password.
 
We do just that.  The person who usually logs into the PC is responsible for
the queue. I have mine set up to use NFT and submit a com to start the queue.
 
You might also note that if the queue is not stopped and the PC is turned off,
the print job will be retained on error.   The moral is - Stop the queue before
turning off your PC.  We often leave ours on and just turn off the monitor at
night.   It certainly doesn't hurt the PC any (some say it is actually better
for it) and we don't have to bother with starting and stopping the queue all
the time.
 
Jon Sonntag
LutherNet Technical Support
Concordia University Information Systems     (708) 209-3210
7400 Augusta St                              (708) 209-3177 FAX
River forest, IL 60305-1499                  sonntajm@crf.cuis.edu (Internet)
From: andreas@didymus.rmi.de (Andreas Fassl)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: 3C503 errors from Netsetup 4.1
Date: 8 Apr 92 10:09:34 GMT
Organization: Klaus Kaempf Softwareentwicklung

Hi,

at this topic, is there a 3c501-driver available for pathworks and
where can I get it?

Thanks

Andreas
-- 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ proGIS Softwareentwicklung, Simulationssysteme, Beratung   + 
+            D- 51oo Aachen, Jakobstrasse 181                + 
+ E-Mail: andreas@didymus.rmi.de VOICE: (49) 241 403 446     +
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Need help with Appletalk-connected printer and Control D's
From: Shawn Allin - Alcan KRDC Computer Services <ACCESS@KRDC.INT.ALCAN.CA>
Date: Thu, 9 Apr 1992 06:43:00 EST

Date sent:  9-APR-1992 06:36:13
 
     Hi,
 
We have a QMS ColorScript 100 Model 10 hooked up to our Ethernet through a
Dayna EtherPrint box to it's Localtalk port.
We have a queue defined via ADMIN/MSA using the printername@appletalk zone
name method...works great from both Vax and Mac...Works SORT OF from the
Pathworks DOS side.
The problem comes from printing to it from something like Harvard Graphics.
The resulting file has one Control D at the very end of it which hangs the
job in the Vax print queue after it completes, never letting another one
through.  We have to STOP/RESET the queue, delete the job, and restart it.
Dec provided a fix for a similar, but less annoying, problem with the
PrintServer 20 where we would get an error page after a similar job to the
effect:
"Illegal character <04> - flushing to end of job"
 
Their fix there was for me to put the following line in one of the config
PostScript files for the LPS20 (It took me a couple of shots to find the
correct one :-))
 
<04> cvn { } def
 
Would the same thing work here?  If so, where can I put this line? One of
the MSAP$* modules?
 
     Thanks,
 
     Shawn Allin
     Alcan International Ltd.,
     P.O. Box 8400,
     Kingston, Ont.,
     Canada  K7L 5L9
     (613) 541-2178
 
     ACCESS@KRDC.INT.Alcan.CA
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Windows 3.1 -Reply
From: Jim Becker <BECKERJA%WPO1P%WPO2V%WPGATE@SNYCENVA.BITNET>
Date: Thu, 16 Apr 1992 08:31:00 EST

==================== Original message text =====================
 
Subj:     RE: Windows 3.1
 
 
First upgrade the QEMM to 6.0.  After that you must exclude some
segment of the B000 B7FF for 386 enhanced operation.  From my
experience, how much you have to exclude will depend on which
Video driver you are using.  I use the TIGA and only have to
exclude B000 B0FF.  You also have to exclude CC00 CCFF for 386
operation.  WIN 3.1 automatically knows you are running V4.1 of
Pathworks and DOS 5.0.  We have two people up on DEC 433pc and
except for the QEMM stuff it has been no problem.
 
================================================================
 
 
Mr. Mattix,
 
Could you please expound on the reason for the exclusion in the C
segment (CC00 CCFF)?  I'm a little worried about this since our
configurations often place adapters in the area.
 
==================================================================
Jim Becker         |  __   PC WP _____\ VMS WP _____\ WP/VMS Mail
State Univ. of NY  | |ME|  Office     / Office      /   Gateway
Central Admin.     |  ~~                                    |
TEL: (518) 443-5548|                                        |
FAX: (518) 443-5799|  ___   /~\__/~\                        V
E-MAIL:            | |YOU| |Internet| /____ Joiner /____ Innosoft
  BECKERJA%WPO1P   |  ~~~   \_/~~\_/  \      JNET  \       PMDF
  @SNYCENVA.BITNET |
==================================================================
 
==================== Original message text =====================
 
Subj:     RE: Windows 3.1
 
 
First upgrade the QEMM to 6.0.  After that you must exclude some
segment of the B000-B7FF for 386 enhanced operation.  From my
experience, how much you have to exclude will depend on which
Video driver you are using.  I use the TIGA and only have to
exclude B000-B0FF.  You also have to exclude CC00-CCFF for 386
operation.  WIN 3.1 automatically knows you are running V4.1 of
Pathworks and DOS 5.0.  We have two people up on DEC 433pc and
except for the QEMM stuff it has been no problem.
 
--
Mike Mattix
Agricultural Group of Monsanto
P.O. Box 174
Luling, LA 70070
INTERNET Address: dmmatt@bigez.monsanto.com
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: PATHWORKS directory depth
Date: 8 Apr 92 04:00:36 GMT
Organization: Digital Equipment Corporation
X-Posted-via: NEWS-NOTES gateway (a hack!)

>                  mcrowley@mtholyoke.edu (Michael A. Crowley)
>                           Pathworks directory depth
>
>We have both VMS and Ultrix (Risc and VAX) running as pathworks DOS
>servers (versions 4.0, 1.1, 1.0 respectively).  There appears
>to be a problem with making directories too deep when connecting
>to any of these servers.  

    DOS has an internal limit of 63 characters for the full spec.

    In a LAN Man (PATHWORKS) environment this includes the "\\server\service"
    (and "%username") portion. I.e. you have to subtract this from the 63
    characters available to you.
    
    I.e. keep your user, service and directory names as short as possible ;-)
    
    Also on VMS the file system RMS (Record Management System) presents you
    with some limits. Notably a directory depth of eight (8) levels max.
    You can define a so called rooted logical name on VMS to work around
    this (i.e. you define a logical name that points to e.g. eight levels
    deep and then use that logical name as a devicename and add more to
    that).
    
    This is not a limitation for file service users, however, since the
    PW4VMS file server (PCFS_SERVER) mostly bypasses RMS.
    
    The drawback with this is that the OOTB (out of the box) VMS BACKUP
    utility can't back up files in directories past the 8th level.
    
    Only doing a full backup of the disk with BACKUP/IMAGE can you save
    directory trees this deep to tape.
    
    I.e. don't create directory trees deeper than 8 levels on a VMS
    system.
    
    ULTRIX and OS/2 server does not have this limitation (but for DOS
    clients the 63 character limit, of course, still applies).
    
    ...petri (backstrom@ranger.enet.dec.com)
       Personal Computing Systems Group
       Digital Equipment Corporation
From: sh1u+@andrew.cmu.edu (Stuart Mark Hiser)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Ethercard drivers found
Date: 13 Apr 92 18:10:03 GMT
Organization: School of Urban & Public Affairs, Carnegie Mellon, Pittsburgh, PA

I have found the NDIS drivers for the Ethercard+, and am now up and
running.  Thanks to all who replied.

For the curious, they can be found (along with lots of other stuff) on
ftp.uu.net in the /vendor/microsoft/network-drivers directory.


Stu Hiser, System Manager, Carnegie Mellon
Hiser@Astra.Supa.cmu.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: WordPerfect 5.1 and PW
From: "Peter Ruwhof - Leiden Univ." <RUWHOF@RULBR2.LEIDENUNIV.NL>
Date: Wed, 15 Apr 1992 09:55:00 MET

Petri Backstrom writes:
 
>     The only "special" things with WP to remember is that you shouldn't
>     load the Redirector to HMA (or "XMS" as NETSETUP calls it); load it
>     high if you want (and have a free 35KB UMB).
 
Why shouldn't you load REDIR to HMA? I didn't experience any problems so far!
 
Peter Ruwhof
system/network manager
University Bureau of the Leiden University
Netherlands
internet:     ruwhof@rulbr2.leidenuniv.nl
bitnet/earn:  ruwhof@hlerul5b.bitnet
telephone:    +31 71 273122
telefax:      +31 71 273118
mail:         PO Box 9500, 2300 RA Leiden, Netherlands
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: local printer queue
From: Dan Wing <DWING@UH01.COLORADO.EDU>
Date: Wed, 8 Apr 1992 13:03:02 -0700
Content-transfer-encoding: 7BIT
MIME-version: 1.0

Nigel Arnot, NRA%ipg.ph.kcl.ac.uk@nsfnet-relay.ac.uk, wrote:
 
>> Problems with shared local printers as LAT-Services:
>...
>> However, after powering down the local PC or the printer the VMS-printer-
>> queue stops and will not restart once the PC is back on the net.
>...
>> We have - as a temporary solution - put a
>>      "NFT SUBMIT "system password" node::[sysmgr]restart_queue.com"
>> command in the local AUTOUSER.BAT network-startup-command which is
>> undesirable because it requires operator privilege and a system password.
 
By "system password", you aren't implying the SYSTEM username, are you??
 
>Well, you can reduce the security loophole by attaching an ACL to the queue
>at the VAX end, so any specified unprivileged user can restart the queue.
>This is of course a work-around, not a cure.
>
>$ SET ACL /ACL=(ID=xxx, ACC=R+W+E+D ) /OBJECT=QUEUE queuename
>
>If I remember right, the RWED flags represent R: can look at queue, W: can
>submit to queue, E: can perform operator functions on the queue and D: can
>delete the queue (not sure: may be delete jobs from the queue).
 
D allows you to delete or otherwide individual jobs in the queue (basically
all of the SET ENTRY commands), and E allows you to modify or delete the queue
itself (basically all the SET QUEUE commands), and perform all the functions
allowed by "D" access.
 
>xxx would be either the user-id whose user-id/password are stored on the
>PC, or an identifier granted to that user and other persons who should be
>allowed to do things to that particular queue. It's best if the user-id stored
>on the PC is dedicated to this one purpose and as restricted as possible (no
>interactive access, for example) so that it is of as little use as possible
>to a hacker.
 
Be careful - giving "Execute" access to a queue allows someone to do anything
to that queue, including changing block restrictions, default form and
/feed settings, owner, etc.  Also, some version of VMS would cause the queue
manager to crash if a person with E access to a queue (and no OPER priv) did
a DELETE/QUEUE command.
 
I'd recommend a CAPTIVE user that has OPER privilege and can only do the
subset of functions you need from a .COM file, and use the NFT SUBMIT with
that user, and only allow BATCH access for that username.
 
Another kludge is a batch job sitting (/HOLD) in a special batch queue on
the VAX.  This batch queue has the appropriate identifier allowing "D" access
to all users you want to be able to release this batch job (you only need
"D" access to modify or delete a job in a queue).  The batch job would do
the desired function.  This would make it completely unnecesary to have a
privileged, captive user do the desired functions.
 
-Dan Wing, DWING@UH01.Colorado.EDU  (or WING_D@UCOLMCC.BITNET)
 Systems Programmer, University Hospital, Denver
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Modem as Service ?
From: Ricardo Pinto <RICARDOPINTO@FIOCRUZ.BITNET>
Date: Wed, 8 Apr 1992 17:05:00 C
Original_To:  JNET%"lanworks@miamiu"
Original_cc:  RICARDOPINTO

        Is it possible to offer a modem connected to a PC in the
LAN as a service ? With printers the LAT protocol works fine but
I can't imagine how to do that with a modem.
        Any ideas ???
============================================================================
=    BITNET: RICARDOPINTO@FIOCRUZ       X25: 12160038::RICARDOPINTO        =
=    VOICE: (021)3891550     (HOME)          1215032820::RICARDOPINTO      =
=           (021)5510021-343 (OFFICE)                                      =
=    ADDRESS:                                                              =
=                Av. Sernambetiba 2916/1028                                =
=                22620 - Rio de Janeiro - Brasil                           =
============================================================================
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: PW & Cluster Alias
From: Maria Rosa Drake <MARIA@SERVAX.FIU.EDU>
Date: Thu, 16 Apr 1992 13:17:34 -0400
X-Vmsmail-To: SMTP%"lanworks@miamiu.bitnet"

We are setting up two 4300s (clustered) and we are debating whether to
use DECnet Cluster Aliasing for connecting to the servers via
Pathworks 4.1.  We like the transparency with which we could setup the
user environment, but we are concerned with performance.
 
I'd greatly appreciate any comments and suggestions from others who
are running Pathworks server software in a clustered environment.
 
Thanks for your help,
 
Maria Rosa Drake
Florida International University
Bitnet:		Maria@Servax.bitnet
Internet:	Maria@servax.fiu.edu
Newsgroups: vmsnet.networks.management.decmcc
From: NETMGR@talos.cc.uch.gr
Subject: decmcc and decnet phase V
Originator: server@ralph.rtpnc.epa.gov
Reply-To: <decmcc@ralph.rtpnc.epa.gov>
Organization: Environmental Protection Agency 
Date: Mon, 6 Apr 1992 12:40:03 GMT

Hello from Crete
 We have installed decmcc MSU ver 1.0 and i want to ask
 if someone else has faced any problem with Decnet V.

thanks in advance
Kaloxylos Alekos
computer center of crete
Greece.
Newsgroups: vmsnet.networks.management.decmcc
From: Bill at MKO <"skibum::gassman"@enuf.enet.dec.com>
Subject: RE: decmcc and decnet phase V
Originator: server@ralph.rtpnc.epa.gov
Reply-To: <decmcc@ralph.rtpnc.epa.gov>
Organization: Environmental Protection Agency 
Date: Mon, 6 Apr 1992 14:15:34 GMT


	To Kaloxylos Alekos of Crete - The DECmcc MSU product is now
	shipping V1.1, and has been since last November.  You should
	upgrade to that, as it's quite a bit improved over V1.0 (and
	wait till you see V1.2!).  The MSU product however is a SNMP
	manager, which added functionality for some of Digital's older
	management protocols (12 years of legacy product).  It does not
	support DECnet Phase V (aka ADVANTAGE-NETWORKS, aka DECnet/OSI).
	The protocol that Phase V uses (DEC-CMIP) is supported by the
	DECmcc Director products (EMA based).  The DECmcc Director family
	supports DEC-CMIP, SNMP, and others, all with an integrated
	interface.  MSU, while supporting several protocols, presents
	some differences in interface depending on the protocol.  The
	right product to buy really comes down to what you are looking for.
	If Phase V is a requirement, or fully integrated UI is what you want,
	then DECmcc Director is for you.  MSU is less integrated, but for
	SNMP management, is a more popular product because it's more like
	the 'other 50' on the market, but has some support for Digital's
	older management protocols, and has the distributed polling and
	map daemon feature.  

	bill