HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Downloading soft fonts to HPs
From: ES12453@SWTEXAS.BITNET
Date: 14 Dec 1992 09:52:00 -0600 (CST)
Content-transfer-encoding: 7BIT
X-Original-To:  Pathworksng, ES12453

   We are running Pathworks 4.1 and VMS 5.5-1. We are having difficulty
   using Glyphix to print to our networked HP printers. When users attempt
   to download fonts and print, the fonts aren't being interpreted correctly
   by the printer. The font escape sequences are being printed as text. This
   problem only occurs when printing to a networked printer. The LAT
   terminal port for the queue is configured as follows.
 
   Terminal: _LTA19:     Device_Type: LN03          Owner: SYMBIONT_4
                                                 Username: SYSTEM
 
      Input:   9600      LFfill:  0      Width: 511      Parity: None
      Output:  9600      CRfill:  0      Page:   66
 
   Terminal Characteristics:
      Interactive        Echo               No Typeahead       No Escape
      No Hostsync        TTsync             Lowercase          No Tab
      No Wrap            Hardcopy           No Remote          Eightbit
      No Broadcast       No Readsync        Form               Fulldup
      No Modem           No Local_echo      No Autobaud        Hangup
      No Brdcstmbx       No DMA             No Altypeahd       Set_speed
      No Commsync        No Line Editing    Overstrike editing No Fallback
      No Dialup          No Secure server   No Disconnect      No Pasthru
      No Syspassword     SIXEL Graphics     No Soft Characters No Printer
   Port
      Numeric Keypad     No ANSI_CRT        No Regis           No Block_mode
      No Advanced_video  No Edit_mode       No DEC_CRT         No DEC_CRT2
      No DEC_CRT3        No DEC_CRT4        VMS Style Input
 
   Device spooled to _SYSDSK$DIA0:
 
   In addition, the form assigned to this queue is set up with a width of
   511 and is /notruncate.
 
   Does anybody have any ideas or thoughts?
 
*****************************************************************************
* Ed Stuart                                      *  Haven't thought of      *
* Systems Analyst                                *  anything to put here    *
* City of Austin Electric Utility                *  yet.                    *
*****************************************************************************
* Using the Southwest Texas State University VAX Cluster                    *
* Internet - ES12453%SWT.DECNET@RELAY.THE.NET                               *
* Bitnet   -ES12453%SWTEXAS.BITNET                                          *
*****************************************************************************
* Please apply a generous amount of all the usual disclaimers here...       *
*****************************************************************************
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Zenith Z-Notes on PATHWORKS
From: "Gordon Cressman RTI (919) 541-6363" <GMC%SSIDW1@RTI.BITNET>
Date: 16 Dec 1992 14:44:36 -0500
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

> Subj: Zenith Z-Notes on PATHWORKS
>
> I'm considering purchase of Zenith Z-Note laptops.  Has anyone tried to use
> the Z-Note Ethernet interface on a PATHWORKS network?  Does it work?  Any
> special adjustments?
 
Following on the response to my own query, I've had one response that
Zenith's desktop ZSTATION's Ethernet port works fine on PATHWORKS using the
LANmanager NDIS driver.
 
Has anyone tried AST's PowerExec notebook with PCMCIA Ethernet adapter?
 
-gmc
Newsgroups: vmsnet.networks.desktop.pathworks
From: poncelet@smr.slb.com (Paul Poncelet - SFM - (33)-1-4746-7117)
Subject: Pathworks TCP/IP on VAX with CMU/TEK
Reply-To: poncelet@smr.slb.com
Organization: SMR Montrouge, France.
Date: Fri, 18 Dec 92 11:38:01 GMT

We have the CMU/TEK TCP/IP package running on our VAX cluster. We are  running
Pathworks for VMS with DECnet, without problem. We wished to try out the TCP/IP
option of Pathworks and installed the files on the server without problem. 

The problem is that the NBNS TCP Netbios process crashes upon startup claiming
it can't find the hostname. DEC's answer is to use their UCX product as the
TCP/IP layer. Does anyone else have experience of getting Pathworks TCP/IP to
work with products other than UCX?


Thanks for any help you can provide


Paul Poncelet
Systems Manager
Sedco Forex Schlumberger
Montrouge
France

e-mail: poncelet@sfm.sinet.slb.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: remove from list
From: Brenda Frick - SRC <bmf@SRC.ORG>
Date: 15 Dec 1992 20:24:09 -0500
Content-transfer-encoding: 7BIT

Please un-subscribe me.
From: yingling@gw.wmich.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Laserwriter IINT printing problems
Date: 16 Dec 92 08:59:47 EST
Organization: Western Michigan University

In article <LANWORKS%92121117003035@MIAMIU.ACS.MUOHIO.EDU>, JIMS@SERVAX.BITNET
(Jim Schenk) writes:
> Hello,
>  
> We recently moved an Apple Laserwriter IINT from Localtalk to Pathworks.
> It is attached to a terminal server (serial) from our VAX server.
> We are running Pathworks 1.1 for the Mac and Pathworks 4.1 for DOS.
>  
> Ever since we connected the printer, certain characters do not print
> correctly from our Macs.  For example, the degree symbol prints out
> as a right curly bracket }, bullets print out as percent signs %, and
> apostrophies and double quotes print as capital T, S, and U.  This
> happens from several Macs, with System 7.0.1 and 6.0.7, using both
> truetype and bitmapped fonts.  I get the same results using Courier,
> Geveva, Helvetica, New York, and Palatino; and with printing from
> WordPerfect, Microsoft Word, and Teachtext.  All Macs are using the
> LaserWriter 7.1.1 driver.  When printing from a DOS machine, the
> characters print out correctly.  The printer is set to No parity,
> XON/XOFF handshake, 8 data bits, and 1 stop bit.
>  
> Has anyone out there come across this problem?  Any suggestions would
> be appreciated.
>  
> Jim Schenk
> University Computer Services
> Florida International University
>  
> Bitnet:         jims@servax
> Internet:       jims@servax.fiu.edu
Yes this is the continual problem that all new connections of Apple 
LaserWriter printers experience when connection is made via serial port.

SInce you've successfully printed from the PCs, try sending this to your 
printer with a type or copy command...

serverdict begin 0 exitserver
statusdict begin
25 9600 67 setsccbatch
end

This should fix (part of) your problem.
-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Ralph N. Yingling, Director	  yingling@hcob.wmich.edu  (Internet)
College Computing Services
Haworth College of Business   --  Western Michigan University
Kalamazoo, MI 49008		  (616) 387-5356
                                  YES, There really IS a Kalamazoo!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Remote boot not booting.
From: hand@marshall.wvnet.edu
Date: 14 Dec 92 15:22:11 -0500
Organization: Marshall University


	Hi, Pathworks people.

	I am having a great deal of difficulty setting up a pc to "remote boot"
from our Pathworks 4.1 server.  I have run the DOSLOAD utility to copy DOS to
the server but if I do a directory of the created dos directory all the files
show up as 0 bytes.  I have tried looking it up in the manual but it keeps
refering to the manual "Client Installation and Configuration Guide for the 
VMS Server".  This manual is not listed in my Pathworks for DOS kit packing
list, so I would assume it comes in another kit.

	If there is anyone out there in net-land that has some expeience with
remote boot, I could use some pointers.  Specificaly, how do I get that manual,
and any "tricks" necessary to get the pc to remote boot.

	BTW the pc in question has a DE202-aa installed and works well from the 
hard drive.  The final application is for an academic lab full of diskless
workstations.

	Thanks in advance.

	Art Hand
	Marshall University Computer Center
	HAND@MARSHALL.WVNET.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Subject: RE: Windows mail interface for UNIX mail
Organization: Digital Equipment Corporation
Date: Sat, 12 Dec 1992 05:00:15 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                      laverty@genitd.UUCP (Mark Laverty)
>                     Windows mail interface for unix mail
>
>I am using the mail application that came with pathworks for our PC's.
>It works well, but we would like a Microsoft Windows version of this.
>
>Is ALL-IN-ONE mail equivalent to the DOS version of pathworks mail? 
>That is, is it a windows interface to the Rand Mail Handler that uses DECNET as
>a transport?   

    ALL-IN-1 MAIL, now named DEC MAILworks, is an X.400 mail product
    that consists of several user interfaces (for different platforms;
    DOS, Windows, Macintosh, Motif, VT-terminals, whatever) and a server
    part that interfaces to the MAILbus products (Message Router et al).

    And, fwiw, with MAILworks a VMS server is a requirement for now.
    
    Today we are not shipping a Windows interface that'd correspond to
    the current PATHWORKS Mail program. It is being planned for a future
    release (of PATHWORKS).
    
    One alternate approach could be the DECwindows/Motif mail utility,
    which also interfaces to MH on ULTRIX. You could use it with an X
    Server for Windows (like, e.g., Digital's eXcursion for Windows).
    
    ...petri (petri.backstrom@ljo.mts.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Running Sethost Reboots the machine -Repl
From: Jim Becker <BECKERJA%WPO1P%WPO2V@SNYCENVA.BITNET>
Date: 17 Dec 1992 08:43:00 -0500 (EST)
Content-transfer-encoding: 7BIT

Hey!  No bashing on the net!  :)
 
I presume you've done the following, but just in case:
 
Before Windows:
    Run LATCP
       DEFINE SCB 4
    Rerun LAT  (or %BOOT%\DECNET\EMSLOAD %_SYSD%\DECNET\LAT)
    SET NVTWIN=1    at a DOS prompt.
    Edit  SYSTEM.INI  and have the following parameter somewhere
    in the [386Enh] section:
       DNetHeapSize=30       (helps sometimes.)
 
Run Windows...
 
I used the standard shipped PIF found in %_SYSD%\MSWINV30
 
Good luck and happy holidays yourself.
 
==================================================================
Jim Becker          |  __   LAN 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@SNYCENVA |  ~~~   \_/~~\_/  \     JNET  \      PMDF
==================================================================
 
================== Original message text ===================
 
Subj:     Running Sethost Reboots the machine
 
Hi all,
        For the first time, I am fooling around with Windows.  I
am trying to run sethost from Windows and it reboots the machine.
I am using Windows 3.1, DOS 5.0 and Pathworks 4.0.  I am using
the DOS 5.0 memory managers, EMM 386 and Himem.sys.  Two times I
have received the following error message:  EMM 386 exception
error #06  and once EMM386 exception error #01.  I have tried all
sorts of things in the sethost pif file but have not had any
success.  Any ideas?
 
(Jim Becker, you better not be chuckling at my misery!!!)
 
        Happy Holidays to all!
 
                 Helen Strother
                 Academic Computing
                 SUNY College at Oneonta
                 STROTTHM@SNYONEVA.CC.ONEONTA.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
From: wasser@ranger.enet.dec.com (ranger::wasser)
Subject: Re: Running Sethost Reboots the machine
Organization: Digital Equipment Corporation
Date: Fri, 18 Dec 1992 05:00:32 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

> I am trying to run sethost from Windows and it reboots the machine.  I am 
> using Windows 3.1, DOS 5.0 and Pathworks 4.0.  I am using the DOS 5.0 
> memory managers, EMM 386 and Himem.sys.

	One thing to try is "SET NVTWIN=1".  This will tell SETHOST that 
	it is running under MS Windows and therefore it should not try
	to dynamically load CTERM, LAT, or TELNET.

	Another frequent cause of crashes is a memory manager that thinks
	the network buffer memory on a DEPCA or Etherworks card is available.
	Telling the memory manager to ignore D000-D800 might help.

	You might also want to use the MS Windows 3.1 versions of the
	memory managers...  I believe the MS-Windows manual says that
	they superceede the DOS 5.0 versions (although DOS 5.0 says
	its memory managers superceede MS Windows 3.0).

				-John A. Wasser
				 Principal Software Engineer
				 PC Integration Engineering
				 Digital Equipment Corp.
From: SYSTEM%APACHE@EPAVAX.RTPNC.EPA.GOV (Greg Siegert, System Administrator, ORD LAN)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Remote boot not booting.
Date: 16 Dec 92 18:40:22 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT

>From: hand@MARSHALL.WVNET.EDU
>Subject: Remote boot not booting.
>Sender: A discussion of Digital's PCSA product <LANWORKS@MIAMIU.ACS.MUOHIO.EDU>
>To: Multiple recipients of list LANWORKS <LANWORKS@MIAMIU.ACS.MUOHIO.EDU>
>Reply-to: A discussion of Digital's PCSA product
> <LANWORKS@MIAMIU.ACS.MUOHIO.EDU>
>Message-id: <01GSDQD8HUPU91WF04@epavax.rtpnc.epa.gov>
>X-Envelope-to: AJOHNSON%MOHAWK, SYSTEM%APACHE
>Content-transfer-encoding: 7BIT>
 
>        Hi, Pathworks people.
>
>        I am having a great deal of difficulty setting up a pc to "remote boot"
>from our Pathworks 4.1 server.  I have run the DOSLOAD utility to copy DOS to
>the server but if I do a directory of the created dos directory all the files
>show up as 0 bytes.  I have tried looking it up in the manual but it keeps
>refering to the manual "Client Installation and Configuration Guide for the
>VMS Server".  This manual is not listed in my Pathworks for DOS kit packing
>list, so I would assume it comes in another kit.
 
  Our workstations typically boot locally on my network, but the symptom
     that you described looks to me like you loaded the DOS SW while
     attached to the file service as System.  You need to
     check the privileges assigned to these DOS files to see if access has
     been granted to everyone.  Files that are inaccessible usually show up
     with a "0" size when you do a dir on that virtual disk. You might
     consider making the owner of those DOS files PCFS$ACCOUNT.  That way
     everyone automatically gets read and execute privilege to those files
     as well as WRITE.
 
 
     Greg Siegert
     VAX SA
     Martin Marietta at EPA/WIC, Washington, DC
 
     Internet Address:  siegert.gregory@epamail.epa.gov
Newsgroups: vmsnet.networks.desktop.pathworks
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Subject: RE: Want to get 437usa directory out of the path
Organization: Digital Equipment Corporation
Date: Sat, 19 Dec 1992 05:00:17 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                       dbk@pslu1.psl.wisc.edu (Don Katz)
>                 Want to get 437usa directory out of the path
>
>When our PC's boot, STARTNET.BAT adds three directories to the path
>for Pathworks - %_SYSD%\decnet, %_SYSD%\pcapp, and %_SYSD%\437usa. We
>don't have a sufficiently long path to accomodate everything, and I
>so I would like to eliminate at least the \437usa directory from the
>path.
>
>Does anyone know what file(s) from \437usa are being used so I can
>move them to another directory in the path?

    The files in that (or any "code page directory" are character
    conversion tables between the code page the directory is for
    and a corresponding server side character set.
    
    Most likely in the dominant 8-bit world of today, the character
    set used on your (or anyone elses) (VMS) server is the DEC
    Multinational Character Set (DEC MCS), which'd mean you need
    DECM.CHR. It could also be ISO Latin-1, which'd be ISO.CHR.
    
    If you're content with servers using 7-bit character sets,
    then the U.S. ASCII version is ASCII.CHR, and what remains 
    are for different countries/languages with their 7-bit
    variations (like, e.g., FINNISH.CHR).
    
    The applications that use these files are SETHOST/VT320,
    PATHWORKS Mail and the NFT utility.
    
    The T.E.'s character set of choice is configured in their Set-Up 
    screens, PW Mail is configured wit MAILSETU, and NFT picks the
    conversion table depending on the parameters to the command
    COPY/ASCII:source-char-set:destination-char-set.
    
    In most situations you'll only need one of these files (since
    PC's on any given site tend to use the same code page, and all
    servers tend to use one character set as well).
    
    And since the 8-bit ones (DECM.CHR, ISO.CHR) are fully compatible
    with the 7-bit U.S. ASCII world, you'd probably be content with
    either one (they only differ by three characters, and what those
    are usually makes no difference for most nationalities that use
    either DEC MCS or ISO Latin-1).
    
    As to your PATH problems, the inherent DOS limit is 127 characters.
    Workarounds are use SUBST to replace a longer device/directory spec
    with just the device (however it will not work with network drives).
    I.e. SUBST Z: C:\APPS\TOOLS and use Z: in the PATH.
    
    And there are also public domain and sharware utilities that allow
    you to use a longer (than 127 characters) path. E.g., 4DOS, being
    a full command shell than a mere "PATH enhancer", can do it. I've
    also heard of others, but none comes to my mind right now.
    
    ...petri (petri.backstrom@ljo.mts.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: What's going on
From: b8tereggie@UMS01.MINC.UMD.EDU
Date: 16 Dec 1992 09:47:58 -0500 (EST)
Content-transfer-encoding: 7BIT

        Are we having trouble with the Lanworks mailing list? I haven't seen any
thing
 in a couple of days. I have checked all my internet gateways, and find no
 pronlems at all. Could someone please advise on what's going on.
 
                                        Thanks
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Remote boot not booting.
From: "Mark Montaqez, System Manager AHEC, (303)556-2409"<MONTANEZM@AHECAS.COLORADO.EDU>
Date: 16 Dec 1992 18:06:55 -0700
X-VMS-Cc: MONTANEZM
MIME-version: 1.0
Content-transfer-encoding: 8BIT

RE: Remote boot not booting.
 
> I am having a great deal of difficulty setting up a pc to "remote boot"
> from our Pathworks 4.1 server.  I have run the DOSLOAD utility to copy DOS to
> the server but if I do a directory of the created dos directory all the files
> show up as 0 bytes.  I have tried looking it up in the manual but it keeps
> refering to the manual "Client Installation and Configuration Guide for the
> VMS Server".  This manual is not listed in my Pathworks for DOS kit packing
> list, so I would assume it comes in another kit.
>
 
The book is in your Pathworks for VMS distribution......
 
Sounds like the user that you gave as an priv'd user for dosload to work wasn't
System.... After several failed attempts I've decided that they meant SYSTEM
not just a priv'ed account....
 
You can tell if things are amiss by doing a
$dir/sec 'your pcas disk':[pcsa.pcsav41.'your dos service']*.*
 
and looking for the files that are owned by someone other than SYSTEM, or that
are missing the ACL's (what I found).
 
I've tried to fix the acls from the VMS side and found it easier to just remove
the old dos service and re-add it using SYSTEM as the priv user..
 
Good luck... and let us know how it turns out....
 
MM
 
 
                              ______..---------====*====---------.._______
..=======---------------.   .='======________ ============= _________======`=
`_________________.----'  /  - _-=_/        `-----=*=-----'
    /_____/__.-----======'-------_'
     `-----===._  -  _  =  __.--'     Mark Montaqez, System Programmer/Manager
                `---------'                The Auraria Higher Education Center
                                                 Montanezm@ahecas.Colorado.EDU
 
 
O'TOLLE'S COMMENTARY ON MURPHY'S LAW
   Murphy was an optimist.
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Want to get 437usa directory out of the p
From: Jim Becker <BECKERJA%WPO1P%WPO2V@SNYCENVA.BITNET>
Date: 17 Dec 1992 09:22:00 -0500 (EST)
Content-transfer-encoding: 7BIT

I'm not entirely sure if the \437USA is needed in the US and I
agree with the other message about PATHMAN, but in the meantime,
let's analyze this:
 
Since NETENVI did not fail, there must be enough space to hold
the Path (<127 characters) once Set so it's the COMMAND setting
the Path that's too long.
 
Therefore you could set an intermediate one in Startnet, let's
say _PWPath, containing only the system service paths.  That way,
the %_sysd%s are reduced from 7 letters to only 2 (eg. - j:)
saving 15 characters in all.  Then, add this intermediate path to
the real path.
 
In essence:
  PATH=lots o' stuff
 
  SET _PWPath=%_sysd%\decnet;%_sysd%\pcapp;%_sysd%\437usa
  SET PATH=%path%;%_PWPath%
  SET _PWPath=
 
You could change your DECNET.WIK (or DNETWIK.V41) file in the
appropriate place if it's important enough and rerun NETSETUP.
 
Or...  do you really need all those Paths in there initially.
Could you add them later one at a time, when you need them for
your applications?
 
==================================================================
Jim Becker          |  __   LAN 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@SNYCENVA |  ~~~   \_/~~\_/  \     JNET  \      PMDF
==================================================================
 
================== Original message text ===================
 
Subj:     Want to get 437usa directory out of the path
 
When our PC's boot, STARTNET.BAT adds three directories to the
path for Pathworks - %_SYSD%\decnet, %_SYSD%\pcapp, and
%_SYSD%\437usa. We don't have a sufficiently long path to
accomodate everything, and I so I would like to eliminate at
least the \437usa directory from the path.
 
Does anyone know what file(s) from \437usa are being used so I
can move them to another directory in the path?
 
Does anyone want to share any bright ideas about how to deal with
path length problems?
 
Don
 
--
-----------------------------------------------------------------------------
Don Katz                                .         Physical
                                       .- / \ -.      Sciences
University of Wisconsin - Madison   ./'  /+-+\  `\.
Laboratory   E-MAIL
From: lane@duphy4.physics.drexel.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: help with LK250 on PC
Date: 17 Dec 92 12:56:16 GMT
Distribution: all
Organization: Drexel University Physics

This might not be the right group, but at least *this* group has
people using both PCs and VAXes!

I use DEC LK250 keyboards on PCs.  I'd like programs running on the PCs
to be able to read keypresses from the entire keyboard (i.e. use the
keyboard as a VT300 keyboard rather than a PC keyboard) including numlock
as PF2, F17-F20, etc.

The terminal emulator I use (Zstem) is able to do this, but in looking over
many sources of PC hw and sw information I have yet to find a way to use the
keyboard in "VT300" mode in my own programs.

Any clues?
--

 Drexel University       \V                     --Chuck Lane
----------------->--------*------------<--------lane@duphy4.hepnet
     (215) 895-1545      / \  Particle Physics  lane@duphy1.bitnet
FAX: (215) 895-5934        /~~~~~~~~~~~         lane@duphy4.physics.drexel.edu