HDTenEightyP/NetNews huggingface dataset:
Date: 10 SEP 92 17:56:06 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From:     adelman (Kenneth Adelman) @ TGV.COM
From: adelman@TGV.COM
Subject:  Re: Ultrix backups.
Organization: The INFO-MULTINET Community

>      >We have ultrix 5000/240 workstations with no tapes, and vms 5.5 vax
>      >4000/500 with 5f85 and Multinet 3.1 .  We have learned to NFS file share
>      >and printer share, and are ready for the lesson on what to do to back up
>      >the Ultrix machines onto vms TF85 tape.  Incidentally it is a FAST tape
>      >drive, a real thrill to use.

>      Although I suspect it's a bit Rube Goldbergish I use dump to backup
> file systems on Ultrix/Bugtrix to NFS mounted disks on my VAXCluster
> running TGV MULTINET.  The dumps then go out to tape with VMS BACKUP.
> COPY has record length problems.  It works.

    The problem with this scheme is that it results in a loss of
certain properties of files.  In particular, if a file is owned by a
group which is not the group that you've got a user mapped to in
MULTINET CONFIGURE/NFS, the information about which group it is owned
by is lost when you copy it to the VMS NFS Server and back.  Also, if
a file has "holes" in it (areas which were never written) these holes
get filled in with zeros and when the file is restored, although it
will appear the same, it will take more disk space.

    The second problem is that most people would rather have UNIX backups
in a UNIX format and VMS backups in a VMS format.  The reason for this
is so that "X" years from now if you don't have one of these machines
you won't be unable to restore files from your backups of the other.

>      I've never heard of tapes being defined as an NFS mounted object.
> MSCP has the same problem in VMS; no tapes.

    The RMT Server does this.

								Ken
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re(2): decwindows, multinet, and ucx
From: "Lawrence P Macintyre" <macintyrelp@ornl.gov>
Date: 10 SEP 92 19:57:38 GMT
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: "Lawrence P Macintyre" <macintyrelp@ornl.gov>

[This message is converted from WPS-PLUS to ASCII]

>> The approach I use is to define the logical DECW$IGNORE_DECWINDOWS in
>> SYSSTARTUP_V5.COM. This then gives me the luxury of starting everything in
>> the order I choose. Since networking stuff is particularly sensitive to
>> ordering I start it up using a single separate command file that does
>> everything in the proper order that's rigidly defined. I find that while
>> you can save a minute or so by getting fancy the long-term price you pay
>> in obscure problems just isn't worth it.
>> 
>> 				Ned
>
>That works for DECNET; I have that defined.  I also have a single .COM file
>that starts all networking software in the proper order.  If you happen to
>run this .COM file in parallel with SYSTARTUP_V5.COM as I do, you can (and
>I do about 50% of the time) have this race condition with DECWindows and
>MultiNet.  In my book, having a hack that works all the time outweighs
>getting phone calls from users and admin asking why they can't display
>a TCPIP window when the person on the next station can.
>++ Dave
        You could always use SYSMAN to start everything...  DECnet is 
        always started before anything you put in BASEENVIRON.  
        DECwindows is started once in CONFIG and again in LPBEGIN, before 
        anything you add.  If you use DIRECT mode, things are started in 
        sequence, not in parallel.  I start LAT, ESS, and Multinet in 
        BASEENVIRON, and let SYSMAN deal with DECnet and DECwindows.  
        This always works.
                                    Lawrence
                                        ~
        


X-Gateway-Source-Info: INTERNET
Date: 14 SEP 92 20:15:49 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: Brian McKeever <MCKEEVER@VAX2.CSTP.UMKC.EDU>
From: Brian McKeever <MCKEEVER@VAX2.CSTP.UMKC.EDU>
Subject: RE:loggin anonymous ftp server
X-Envelope-to: info-multinet@tgv.com
X-VMS-To: IN%"info-multinet@tgv.com"
Organization: The INFO-MULTINET Community

> I'm trying to find a way to log the ftp sessions for my
> anonymous ftp server. Is there any way I can log information
> such as the users entry (ie the password)?
>
> Rodrigo:-)

I wrote a little procedure that scans the FTP_SERVER.LOGs (and
FTP_SERVER.OLDs in ANONYMOUS's login directory) for hostname, password, and
any 550 errors.  550 errors can indicate someone trying to move into a
directory they aren't allowed access to, i.e. a breakin-attempt.  I have
its output mailed to me nightly.  It may be what you're looking for.  You
can get it via anonymous FTP from CSTP.UMKC.EDU.

--Brian

P.S.  Here is my ANONYMOUS FTP LOGIN.COM so you know where the
      FTP_SERVER.OLDs come from.

    $ request/noreply "Anonymous FTP connection established."
    $ rename ftp_server.log;-1 ftp_server.old
    $ purge/before="-30-" ftp_server.old
Newsgroups: vmsnet.networks.tcp-ip.multinet
From: roeber@vxcrna.cern.ch
Subject: Re:  Re: RCP and LOGIN.COM problem
Organization: CERN -- European Organization for Nuclear Research
Date: Mon, 7 Sep 1992 09:49:18 GMT

In article <2460313607SEP92071342@TGV.COM>, adelman@TGV.COM writes:
>     Yes, if the first line of your login com turns off verify:
> $ verify = 'f$verify(0)

Any suggestions on how a poor user can convince the system and group
manager types to similarly clean up the system/group login files?

I know it would be a hack, but it would be awfully nice if in some
future version the daemon recognized the rcp request and just bit-
bucketed any output before the rcp program started..

-- 
Frederick G. M. Roeber | CERN -- European Center for Nuclear Research
e-mail: roeber@cern.ch or roeber@caltech.edu | work: +41 22 767 31 80
Organization: Penn State University
Date: Mon, 14 Sep 1992 08:47:02 EDT
From: <KJB6@psuvm.psu.edu>
Newsgroups: vmsnet.networks.misc
Subject: HELP WITH NETWORKING SYSADMINSTRATION

I am an Administer for unix based machines on a local network. A professor has
put a vax station onto the network. I do not know much about vms administration
Any help would be great.

I am using ucx (sp?) and can do a telnet 146.186.xx.xx, which file(s) allow
me to use the name of the machine instead of the numerical address? Also, if
I try to telnet outside our local net, I get "network unreachable". Which file
do I need to look at to show gateways & routes?

Again, "any" help would be greatly appreciated. If you could mail to me
directly, that would be great because I am very rarely in this group.


Ken Bauer
Systems Analyst      kjb6@psuvm.psu.edu
PENN. STATE - ERIE, The Behrend College
From: makinc@hhcs.gov.au (Carl Makin)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Mail system to use with PathWorks?
Date: 11 Sep 92 15:03:02 +1000
Organization: Aust. Dept. Health, Housing and Community Services

In article <0096066C.E46A3A40.1688@VULCAN.CBA.OHIOU.EDU>, chiam@VULCAN.CBA.OHIOU.EDU (Ta Fuh Chiam) writes:

>>> 3.    DEC's Mailworks.

>>We're in the process of running up Mailworks.  It doesn't talk
>>direct to VMS mail.  It's X.400 based and the user interface is
>>pretty horrible. (Yes that's a personal opinion)  It's reasonably
  
> Can you give a little more details on why it is pretty horrible? Examples will
> be helpful.

There are buttons that don't work, some menu items don't get
updated once an evet has happened (like you've deleted a message
and the wastebasket still shows empty).  These and others are
problems that hopefully Dec will fix soon.  My main complaint is
in the mail creation and reading area.  There is no standard size
of the mail window and you can't specify line widths except by
resizing it.  The mail editor wordwraps at the window size and
inserts carriage returns but as you can't specify line sizes you
get everyone with different size windows and the text is usually
badly formatted.  Even Windows Notepad is a better editor than
the mailworks message entry screen.

>>product in another 12 months time.  To talk to VMS Mail you have
>>to obtain Dec's Message Router software.

>>Mailworks requires Dec's Distributed Directory Services (DDS) as
>>well.
  
> Please note that Message Router *is* required since DDS is part of Message
> Router.

Ah, well, the Digital solution is, of course, to buy more Vaxes
and Vax licences.  You'll have to excuse my ire though, the
Department I work for is now so deeply reliant on Digital
services ($50 Million plus) that Digital can dictate terms to us.

Hmmm..  Maybe it's time I left.

Carl.

-- 
Carl Makin, MVS/ESA Systems Programmer, VAX/VMS Dabbler. 
Dept. Health, Housing and Community Services, Canberra, Australia.
sserve.cc.adfa.oz.au!hhcs!makinc   -   UUCP
makinc@hhcs.gov.au		   -   Internet
vk1kcm@vk1kcm.act.aus.oc	   -   Packet Radio
"I'm from the Government and I'm here to help you."
Newsgroups: vmsnet.networks.desktop.pathworks
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Subject: Re: BROADCAST & DOS 5.0
Organization: Digital Equipment Corporation
Date: Sat, 5 Sep 1992 05:00:39 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                          akk9180@ritvax.isc.rit.edu
>                              BROADCAST & DOS 5.0
>
>Hello - We are running Pathworks on some DS5000 (ULTRIX).  Client rev is Pathworks
>4.1.  Has anyone else experienced a PC system hang when "broadcasting" to a
>client who is in the DOS 5.0 edit program?  Any solutions?  Thanks in advance!

    Everybody must experience it ;-)
    
    It is a problem in the libraries which Microsoft uses to build character
    cell applications like EDIT and DOSSHELL.  They do not consistantly pass
    keyboard input from hardware Int 9h to BIOS Int 16h.

    Microsoft has been made aware of this, but so far I haven't heard of
    any fix made available.
    
    As a workaround you could trun off RCV before running EDIT and reactivate
    it after exiting:
    
        @echo off
        rcv /t:0 >nul
        edit %1
        rcv /t:1 >nul

    ...petri (backstrom@ranger.enet.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Subject: RE: HP-Laserjet(s) Printer Symbiont
Organization: Digital Equipment Corporation
Date: Mon, 7 Sep 1992 05:00:21 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                            TKENNETT@BENTLEY.BITNET
>                        HP-Laserjet(s) Printer Symbiont
>
>Problem:
>        When printing to any HP LaserJet (old style to LJ III si ) we get
>        a blank page at the beginning of the print job, and at the beginning
>        of every print job for that matter.
> 
>Attempts to resolve:
>        Tried:
>                Using the supplied Pathworks printer symbiont
>        Result:
>                Leaves leading and trailing blank pages

    Using the SMBSRVSHR.EXE supplied with PATHWORKS for VMS (or VMS V5.5-1)
    alone isn't enough.
    
    In other words, you need to modify your device control library so that 
    the print symbiont is told not to send these additional form-feeds.
    
    Take a look at the file PCSA$FIX_RESET_MODULES.COM in SYS$STARTUP.
    
    ...petri (backstrom@ranger.enet.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation

    N.B. When upgrading VMS with the PATHWORKS for VMS supplied SMBSRVSHR.EXE
         in use, if it is not VMS V5.5-1 you're upgrading to, save the
         SMBSRVSHR.EXE and use it to replace the one a VMS upgrade puts in
         its place.
         
         If you didn't save it, you can just grab it from the PATHWORKS for
         VMS savesets (separately or by reinstalling).
From: jackson@BDRC.BD.COM
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Windows front end for LOGIN
Date: 10 Sep 92 15:45:00 GMT
Content-transfer-encoding: 7BIT
Encoding: 27 TEXT
X-Mailer: Network Courier V2.1b

REPLY FROM: Jackson, Gene
 
>2) WP Mail for Mac Version 3.03 is causing problems in a Pathworks (4.1)
>environment. Mail sent from Mac to PC, Mac to VAX or Mac to Mac is fine. Mail
>sent from PC or VAX to Mac comes out on the Mac with a scrambled FROM: field
>and extraneous characters (sometimes) in the body of the text. VMS version on
>the VAX with the shared mail directories is 5.5.
 
>Murray Penno
>Computer Consultant
>NZ Pastoral Agriculture Research Institute Ltd.
>Invermay Agricultural Centre             InterNET:  PENNOM@INVERMAY.CRI.NZ
>Private Bag 50034                      CompuServe:  76467,610
>Mosgiel                                       FAX:  (064) (3) 4893 739
>New Zealand                                 Voice:  (064) (3) 4893 809
>
 
===========================================
 
The MSAF$FILE_TYPES.DAT file needs to be modified to translate the mail files
correctly.  The file that comes with Pathworks does a CR translation by
default for all files that are not otherwise defined.  This needs to be
changed to "none" for the mail files.  For a complete description of this
file see pages 5-10 to 5-16 of the Pathworks for VMS (Macintosh) Server
Administrators Guide.
From: BECKERJA%WPO1P%WPO2V@SNYCENVA.BITNET (Jim Becker)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Printing from local applications through
Date: 11 Sep 92 17:12:00 GMT
Content-transfer-encoding: 7BIT

Another list member appropriately suggested using the PSC.COM
program shipped with PW to help signal the end of print jobs.
 
Before doing that though, see if it's possible to set up the
application to print the job to a file.  For instance in WP, if
you selected:
 
          Port, Device or filename,
 
as if to print to a file, you can also enter LPTx as a DEVICE
name.  This makes WP treat the job as if it's a file and sends an
EOF code at the end.  This is a key to the LAN software that the
stream is complete and to close the print channel.
 
This works in other products as well as long as they accept the
device name in place of a file name.
 
Or, as in products like LOTUS 1 2 3, they provide selections for
device names in the Printer Defaults menu.  So, don't choose
Parallel 1 or Serial 2, but choose DOS Device LPT1, etc., and it
should work correctly (it does where we are, anyway.)
 
==================================================================
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:     Printing from local applications through Pathworks
 
I have recently setup users with Pathworks, that are running
DOS applications on their PC's.  When printing from these
applications the file isn't noticable in the VAX queue and
doesn't print until a WordPerfect document is sent.  The
WordPerfect resides on the server.  Has anyone experieced
any print problems like this?
From: chiam@VULCAN.CBA.OHIOU.EDU (Ta Fuh Chiam)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Pathworks unsupported kits via DSNlink - more info
Date: 10 Sep 92 13:37:52 GMT
Content-transfer-encoding: 7BIT

Hi, ALl,
 
I sent out a message about the availability of the Pathworks unsupported kits
via DSNlink.
 
As you can see from the note reposted below from DECUServe, please also note
that the kits is only available via DSNlink and you are NOT to call the DEC CSC
to request the kits on diskettes.
 
Ta Fuh Chiam
 
--------------------------------------------------------------------------------
           <<< EISNER::DUA2:[NOTES$HIVOL]BUSINESS_PRACTICES.NOTE;1 >>>
                            -< Business Practices >-
================================================================================
Note 216.17       Distribution of the Unsupported PATHWORKS kit         17 of 17
EISNER::HYDE "From the laboratory of Dr. Jekyll"     18 lines  10-SEP-1992 09:14
                                 -< more info >-
--------------------------------------------------------------------------------
        This does not change the availability of the disk from
        DECdirect.
 
        I should note that CSCPAT_3056 will *only* be available via
        DSNlink. Do not call the CSC and request this 'patch' kit on
        diskette. Being unsupported stuff and given that there is
        already a way to get the diskettes from DECdirect, the CSC will
        not eat the expense of distributing media.
 
        If Canada uses DSNlink to deliver CSCPAT's then there should be
        no problem. I don't know for sure how they work.
 
        Since I own the CSCPAT business for Atlanta I can make the
        disk available on DSNlink via that mechanism. I do not feel that
        I can give the Digital ok for putting them in other places -
        even though I personally don't think it should be a problem.
 
        mark
From: enisaxg@state.systems.sa.gov.au
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Pathworks/DOS with Wollongong PATHWAY
Date: 13 Sep 92 10:52:06 GMT
Organization: State Systems, South Australia

Quick question, hope it's not an FAQ (I suspect not!).

We're running Wollongong's PathWay products on PCs and Macs AND on VAXes.
We're considering replacing the VAX bits, doing one of:

	. replace all of Wollongong (SMB server, TCP/IP, NFS Server/Client)
	  with TGV's Multinet or similar
	. keep Wollongong's TCP/IP, but get rid of its SMB server

BECAUSE we hear that PathWorks comes with TCP/IP support and an SMB server.
However, it's unlikely that we'll be able to convert the PC and Mac PathWay
licenses to PathWorks licenses this year. So ...

Does PathWorks (for DOS in particular) work over Wollongong TCP/IP, using
DOS  PathWAY clients???

If so, how successfully? (ie Is it production-quality?).

Thanks in advance for any help.

(Alex Gunjko)
Systems Manager
Department of Environment and Planning
South Australia

Phone: 61-8-207-2054
Email: gunjkoa@dep.sa.gov.au
FAX  : 61-8-207-2298
From: Huy_Le@mindlink.bc.ca (Huy Le)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: HP Printer solutions
Date: 12 Sep 92 18:15:10 GMT
Organization: MIND LINK! - British Columbia, Canada
Distribution: world

>We are checking out a solution using HP LJ IIISi printers and ethernet
>communication card from XCd Inc. These cards support LAT today and if we take
>them now, we are prommised free upgrades to the version suporting both LAT and
>TCP/IP. The demo setup we have seen worked very well, so we have more or less
>decided to get them wen we add an LJ IIISi to our net later this year.

Can anyone who is using this product post a review of it. I am sure that
many people will be interested in the results. Thanks.

Huy Le
From: MIS9509@UMBCADMN.BITNET (Glen Whims 301-455-2579)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Printing from local applications through Pathworks
Date: 10 Sep 92 17:34:00 GMT
Content-transfer-encoding: 7BIT

I have recently setup users with Pathworks, that are running
DOS applications on their PC's.  When printing from these
applications the file isn't noticable in the VAX queue and
doesn't print until a WordPerfect document is sent.  The
WordPerfect resides on the server.  Has anyone experieced
any print problems like this?
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Zenith and EtherWORKS Turbo problems.
From: bachism <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 04 Sep 1992 08:05:30 -0400
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS%MIAMIU.BitNet@pucc.PRINCETON.EDU"

Have you tried doing it with no himem.sys and no emm drivers in your
config.sys?  If that works try using one and not the other.  One thing I had a
problem with was a mouse driver.  The best trouble shooting comes when you
clean out you config.sys and autoexec.bat to the bare miminum and then work
your way up.  If it doesn't work with a minimum config.sys its definately
some type of conflict within the hardware
From: coopebl@OKRA.MILLSAPS.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Int14 w/LAT LATCOM etc..
Date: 8 Sep 92 20:42:50 GMT
Content-transfer-encoding: 7BIT


	FYI:
 
	  LATCOM (an unsupported utility from Digital that
	allows PC programs to use modems attached to terminal
	servers via LAT) and several other wonderful PATHWORKS
	related (WINRCV, UPDATE...) utilities can be found on
	COMPUSERV in the DECPCI forum.
 
	  I don't know of an FTP source for LATCOM.  The FTP
	subject has been brought up, but not resolved, at
	DECUS Symposia. (petri do you of a source?)
 
                        Brad Cooper
		        PC-SIG Vice Chair DECUS U.S.
			cooper@decus.org
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Best bet is to upgrade Mac ethernet drivers
Date: 12 Sep 92 10:27:16 GMT
Organization: St. Peter's College, US

In article <1992Sep12.040149.25363@nntpd.lkg.dec.com>, harris@ranger.enet.dec.com (ranger::harris) writes:
>     Re: "weissh@nextadm.cc.vt.edu" 
>         -< Known Problems with Pathworks for Mac and VMS/DECnet 5.5? >-

  [I can't find this article locally. If the References: header is correct,
we've already expired it]

>     The problem most likely is due to a change in the VMS ethernet drivers
>     which reject any packets that are received which do not match the
>     length specified in the packet header.

  Some bugs were introduced into the drivers at the same time (the V5.4-3
release, as I recall). These were the 802.3 system crash, the dropping of
broadcast packets, and not filling in the from address when sending using
the "altstart" interface.

  There are patch kits for all of these. Some that come to mind are #552
and #3024. You might also want #555.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
From: br197@cleveland.Freenet.Edu (Michael T. Gercevich)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: EMM386.EXE undocumented function.
Date: 10 Sep 1992 14:12:31 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: br197@cleveland.Freenet.Edu (Michael T. Gercevich)
NNTP-Posting-Host: slc4.ins.cwru.edu

Hi,

We were having problems with many of our PCs hanging (esspecially in LOTUS).
EMM386 was found to be at fault.  If you have an IDE harddrive and use
expanded memory through EMM386 with the 'ram' qualifier...add the parameter,
NOMOVEXBDA to the device line in config.sys.  This has fixed nearly all of
the problems we've been having since our DOS 5.0 upgrade.

Hope this helps somebody!
Michael Gercevich
PC/Network Analyst -- Squire, Sanders & Dempsey
(216)687-3452  Fax:(216)687-3401
internet: br197@cleveland.freenet.edu
From: edbis%Solomon.Technet.sg (Koh Eng San)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: VT320 emulation on Win3.1
Date: 7 Sep 92 02:25:55 GMT
Organization: National University of Singapore
X-Newsreader: Tin 1.1 PL5

This probably has been asked before..

I noticed that the key mapping for the VT320.EXE program found on PathWorks
for DOS 4.1 is not really the same as the SETHOST.EXE program. For example,
you need to press ALT-RETURN to get the ENTER key and the keypad on a enhanced
keyboard is not mapped at all.

Is there an updated version of this program? Or how do I customise the
keyboard mapping?

Regards,

Koh Eng San
EDB Singapore
Newsgroups: vmsnet.networks.desktop.pathworks