HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Problems with PC and MAC sharing a file service
From: BESSETTE@VSDEC.NUSC.NAVY.MIL
Date: 12 Nov 1992 08:28:15 -0500
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"

> I have a fileservice on a VAX that is accessible from both PC, Mac and
> VMS. The problem is that if a PC wants to delete a directory it can not
> do that due to the fact that MSA has created subfolders in the directory
> that the PC can not see and therefore cannot delete. From the Mac there
> is no problem with deleting files. To delete files from VMS one have to
> use the command DELETE/ACL before one is allowed to delete the
> directories.
 
> My question is: Does anybody know of a workaround to let the PC delete a
> directory that is empty, but has subdirectories that the PC can not see
> due to that the file names are to long?
 
> If there is not a workaround is not this a weak point in the integration
> of PCs and Mac that DEC ought to fix, or is it just me that has such
> problems?
 
All the responses have correctly detailed the reason for the problem.  When
I initially set up PATHWORKS over a year ago, I had my VMS directory on the
server as a PC and MAC directory/volume.  After some time I had the same
problems that you are describing.  Being the system manager, I took care
of the problems from the system managers account under VMS.  Not the best
method.  What I have recently done is make a directory called MACSTUFF
in my VMS directory and that directory is what I mount as the Bessette
volume from MSA.  What does this do for me?  I can "see" it from DOS
since the directory name is 8 characters.  (First try I called it
MAC_STUFF and wondered where the stuff went :-)  This allows me to copy
from DOS to MAC.  Also, if I watch the names, as Ta Fuh pointed out,
I can "see" the Mac files.  I can now manage all my DOS files from my
PC.  Now the down side.  The MAC cannot "see" the DOS side without going
to NETCOPY which of course requires you to be a DECnet node.  Keeping my
directory clean and having my MAC on ethernet makes this work for me.
Maybe it would work for you.
 
Bob B.
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Performance of 3COM's 3C509-coax ethernet card.
From: "Roel Alkema Kernfysisch Versneller Instituut, Groningen" <ALKEMA@KVI.NL>
Date: 10 Nov 1992 09:07:13 +0000
X-PS-Qualifiers: /FORM=A4/LEFT_MARGIN=36/TOP_MARGIN=36
X-VMS-Cc: ALKEMA
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Sorry if you receive this message twice, it was not distributed the first time?
 
The new ethernet card of 3COM type 3C509 promises a cheaper but also faster
alternative for the 3C503 etherlinkII-16 cards.  However some tests, measuring
filetransfer-speeds, performed on a fast and  slow MS-DOS machine and on a
normal and slow responding server, does not fully confirm  this.
 
Tested is the use of virtual disk service, and especially reading them, because
applications like WINDOWS, PCAD, WORDPERFECT, DRAWPERFECT are all loaded from
a virtual disk in our institute.
 
My conclusions are :
1 - With a reasonable fast PC (386/25) and a normal reponding server; reading
with the 3C509 is faster then the 3C503, but with a slower PC the differences
become smaller and when also the server becomes slower (heavier loaded), the
3C503 card has even a slightly better performance.
 
2 - For diskservice "writes" the performance seems nearly equal for both cards.
 
3 - For fileservices tested with DECNET and  TCP/IP as transport layer the
differences between the two cards are not significant for both read / write's.
 
 
My conclusion is that you may not always have profit buying this cards, but
perhaps my tuning is not correct, or there are other NDIS drivers then those
delivered by 3COM, or ....
If anybody has different experiences, please let me know.
 
Roel Alkema.
 
 
 
 
 
Conditions:
 
Used with the NDIS driver supplied with the 3C509 card.
The etherlink3 part of the protocol.ini file:
[etherlink3]
DRIVERNAME = ELNK3$
MAXTRANSMITS = 30
(other parameters (XMIT, INTERRUPT .. are not longer accepted.)
 
For the diskservice the LAD qualifiers are tuned to /R:2 /W:15.
Although /R:15 gives sometimes better performance, it will crash the PC
sometimes. (Always hang when starting up windows (from diskservice)).
 
The 3C509 is autoconfigured, and uses the follwing setup
@I/O base address:                 300H
@Interrupt request level:          10
@Boot PROM size:                   disabled
@Transceiver type:                 on-board coax
@Network driver optimization:      DOS client
@Maximum interrupt disable time:   500 microseconds
 
Pathworks V4.1, Server VAX 4000-300, VMS V5.5.
 
 
================================================================================
Roel Alkema                             Phone : +31 (50) 633617
Kernfysisch Versneller Instituut        Fax : +31 (50) 634003
Zernikelaan 25                         E-mail : alkema@kvi.nl or alkema@hgrrug51
9747 AA Groningen                     Surfnet : kviclu::alkema
NL Nederland                    X.25/PSI-mail : psi%15901047::alkema
================================================================================
Newsgroups: vmsnet.networks.desktop.pathworks
From: jmacdonald@mta.ca
Subject: All-In-One MAILWorks vs. POP3 clients
Reply-To: jmacdonald@mta.ca
Organization: Mount Allison U, Sackville, N.B. Canada 
Date: Mon, 9 Nov 1992 17:55:01 GMT

We are considering pruchasing DEC's MAIL Works (all-in-one).  The interface is
nice but the price is a heck of alot more than the POP3 clients out there
(popmail).  Other than price (and support) there are two issues of concern:
functionality and performance.  I would appreciate hearing of any experiences
with these products - IS the price of MAIL Works worth it AND WHY/WHYNOT??????
Thank-you for your help.

Jane MacDonald (jmacdonald)
Computing Services
Mount Allison University
Sackville, New Brunswick
Canada
From: crle@gnv.ifas.ufl.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Help..Upgrade MSCDEX V2.10?
Date: 9 Nov 92 14:47:11 -0500

A Question Asked:
>> DOS 5.0, Windows 3.1, VMS 5.5-1.
>>I don't understand what to do with the LADCDDRV.SYS and MSCDEX.EXE files.
>>When I install LADCDDRV.SYS with DEVICE = in the config.sys and do a
>>USE ?: <service_name> /CDROM, the PC told me that MSCDEX is not installed.
>>When I call MSCDEX, it tells me that I don't choose a valid driver ?!?!?
>>Thanks for an help !

A Reply Given:
>         Make sure you use the latest MSCDEX V2.21, from
>         Microsoft there are problems with the one shipped with
>         Pathworks.

Huh?...
	What is wrong with the MSCDEX that came with PW?
	Is it really broken? If so, what version?
	Look at what I'm running, Should I upgrade?...
        Why should I upgrade?...Would you Upgrade?...
        etc...

PC:	DOS5, Windows 3.1, NCSA Telnet, PW 4.1, MSCDEX V2.10
VAX:	VAX Cluster (6320,4000), VMS 5.5-1, InfoServer 100 v2.0

P.S.
	I don't have a problem...Fix something that is not broken?
	DON'T FLAME ME...DON'T FLAME ME...DON'T FLAME ME...

+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+

                   U n i v e r s i t y   o f   F l o r i d a
       \o\ - - - Institute of Food and Agricultural Sciences  - - - /o/
      	\o\     ________    ________     _________    __    __     /o/
       	 \o\    \___  __\   \  _____|   |  ____  /   /  \  / /    /o/ 
          \o\     __\ \___   \ \____    | |___/ /   / /\ \/ /    /o/
       	   \o\    \_______\   \_____|   |______/   /_/  \__/    /o/
       	    \o\                                                /o/
             \o\ - - - C O m p u t e r -- N e t w o r k - - - /o/

+--------------------------------------+--------------------------------------+
|    Christian R. Leopold              |   Internet: CRLE@GNV.IFAS.UFL.EDU    |
|    University of Florida             |     Bitnet: CRLE@IFASGNV             |
|    IFAS Computer Network             |      Phone: 904/392-5180             |
|    Building 120  Rm 205              |        Fax: 904/392-5857             |
|    Gainesville, FL 32611-0350        |                                      |
+--------------------------------------+--------------------------------------+
Newsgroups: vmsnet.networks.desktop.pathworks
From: mitton@dave.enet.dec.com (Dave Mitton)
Subject: Re: Station Address and the Ethernet Packet
Keywords: station address
Reply-To: mitton@dave.enet.dec.com (Dave Mitton)
Organization: Digital Equipment Corporation, Littleton MA
Date: Thu, 5 Nov 1992 17:36:17 GMT


In article <apple.720974069@drvax3>, apple@drvax3.msfc.nasa.gov (Kathleen Applegate) writes:
>Newsgroups: vmsnet.networks.desktop.pathworks
>From: apple@drvax3.msfc.nasa.gov (Kathleen Applegate)
>Subject: Station Address and the Ethernet Packet
>Date:  5 Nov 92 14:34:29 GMT
>
>Which address is used in the ethernet header for the packet
>going out on the wire:
>
>    - The hardware address hardcoded onto the ethernet
>      card (e.g. 08:00:2B:25:D9:A6)?
>    - Or, the station address whose last three number
>      sets are calculated based on the DECnet address
>      (e.g. AA-00-04-00-B9-23)
>                     ^^^^^^^^ calculated
>
>            ^^^^^^^^based on IEEE vendor IDs in the MAC address.
>
>DEC Tech Support just told me that it is the calculated address
>that goes into the packet, and that the other will not appear in
>any of the packet headers.   
>
>So this is a reality check--can this really be true?
>--
>Kathleen Applegate, Sr. Analyst      apple@drvax3.msfc.nasa.gov           
>Marshall Space Flight Center             Voice:  (205) 544-7656

	Yes, DECnet Phase IV has worked that way since we added support
for Ethernet and began shipping it in 1982.  Gee 10 years now.

	The local station address is calculated and set by the DECnet
node address. (the 16 bit binary ((area*1024)+number) byte swapped)
The upper 4 bytes are a constant.

	Dave Mitton
	Networks and Communications
	Digital Equipment Corp.
From: jrkdmd@dmdscs.com (Joe Krulewicz)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Windows for Workgroups
Date: 9 Nov 92 16:06:06 GMT
Organization: DMDS Consulting Services, Branchburg, NJ

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
From: KRAMER_AG@RSO.DNET.GE.COM (Aaron Kramer GE Hypersonic Systems Dept 215-354-4355)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: unable to connect to disk service (3.1) & file service (4.1)
Date: 12 Nov 92 12:26:12 GMT
Content-transfer-encoding: 7BIT
X-Cc: KRAMER_AG

Greetings. May I take this opportunity to thank the contributors to
the list for their time and expertise; I have been able to solve
many a problem by just lurking and watching. Thanks also to DEC
for watching.
 
From STARTNET.BAT:
Now attempting connection to the system file service \\VXSV04\PCSAV41
Error: Network Name not found
** WARNING ** Unable to connect to \\VXSV04\PCSAV41
              Retrying...
Error: Network Name not found
** ERROR ** Unable to connect to \\VXSV04\PCSAV41
 
Now, these errors happen most of the time, but some of the time it
works. This PC is unable to connect to the system file service under
Version 4.1 of Pathworks, also is unable as unreliably under version 3.1
of Pathworks to connect to the PCSA$DOS.... service, on a completely
different server. The hardware hasn't been ruled out (DEPCA AUI through
a 10baseT converter) but ....
 
Where should I look? Is this a protocol thing, as I think this is the
first USE statement in both cases?
 
Aaron Kramer kramer_ag@rso.dnet.ge.com
From: HOLDREGE+_MP%A1%PacifiCare@MCIMAIL.COM (Matthew Holdrege)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Pathworks vs. Novell (?)
Date: 6 Nov 92 17:24:00 GMT
Content-transfer-encoding: 7BIT

>We are a 12000 employee telecom company with a 1.5 billion revenue spread all
>over Brazil (a large country) with a corporate net based on IBM, VAXes, and
>desktops. We picked Pathworks over Novell to integrate our 3,000 PCs
 nationwide.
>Why? Try to integrate applications with a Novell net...
 
Since I don't have the time to test Novell integration, could you or anyone
else give us some specific problems with Novell integration? Just telling
management that Novell sucks for big corporations is not good enough. I
need to find out what the real technical problems are.
 
Thanx!
 
Matt Holdrege                   5156065@mcimail.com
Pacificare Health Systems       holdrege@eisner.decus.org
From: RWU@MATTEC.INTEL.COM (Ron Wu, SC2-24, 5-2368.)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: problem saving files on a file service using amipro
Date: 6 Nov 92 16:01:30 GMT
Content-transfer-encoding: 7BIT


	I had that same problem saving (not copying) file in Amipro 2.0
to Pathworks file service (version 4.0).
 
	The problem went away when I upgraded to Pathworks 4.1.
 
Ron
rwu@mattec.intel.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Sorry for this FAQ, Infoservers CD's connected to PC
From: "a1::cox"@MRGATE.OFFICE.OFFICE.DECNET.LOCKHEED.COM
Date: 04 Nov 1992 18:28:18 -0800
Content-transfer-encoding: 7BIT

From:	NAME: John Cox
	FUNC: 48-02
	TEL: 756-6979  FAX 742-6428           <COX AT A1 AT OFFICE>
To:	NAME: VMSMail User "LANWORKS <"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"@EAGLE@MRGATE>
 
 
> DOS 5.0, Windows 3.1, VMS 5.5-1.
>I don't understand what to do with the LADCDDRV.SYS and MSCDEX.EXE files.
>When I install LADCDDRV.SYS with DEVICE = in the config.sys and do a
>USE ?: <service_name> /CDROM, the PC told me that MSCDEX is not installed.
>When I call MSCDEX, it tells me that I don't choose a valid driver ?!?!?
>Thanks for an help !
>--
># Lutz Marten,  Postmaster and general dogsbody
># Fraunhofer-Gesellschaft Institut fuer Lasertechnik
># BITNET: KQ040MA@DACTH11 , InterNet: marten@ilt.fhg.de
># HEPNET: 13533::52714::MARTEN, Phone: +49/241/8906-112, -0
 
         Make sure you use the latest MSCDEX V2.21, from
         Microsoft there are problems with the one shipped with
         Pathworks.
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Pathworks vs Novell
From: Ta Fuh Chiam <chiam@VULCAN.CBA.OHIOU.EDU>
Date: 11 Nov 1992 10:25:37 -0500 (EST)
Content-transfer-encoding: 7BIT

>   I agreed with Miguel that Pathworks and Banyan are far more superior
>than Novell in terms of WAN corporate wide networking as they have more
>networking capabilities.
 
If you need the WAN capability, then PATHWORKS is a better product and the
right solution.
 
>   However as a result of more features plus incorporation of decnet
>into their network module , Pathworks is very memory intensive and
>will eat up abt 300 - 400 Kbytes of physical memory which create a lot of
 
Not if you only want File and Print services, which is what basic Novell server
provides you with.
 
>problems for SG when we try to network most of our PCs which comprise
>of 8086/8088 PCs abt two years ago. Morever softwares such as Wordstar
>and Freelance needs certain amount of free base memory before it can work
>efficiently. Novell on the other hand eats up far less physical memory.
>MS-DOS version 5.0 has resolved to a certain extent but still not
>good enough the lack of base memory by allowing certain modules to be
>installed into high mem.
 
Look further down the road. Are you going to keep the 8086/8088 for very long?
 
>    In terms of printing, Pathworks boast of able to print Freelance, Lotus
>and other PC software files in LN03/LN06 DEClaser printer that are
>connected to the terminal server but practically this is a bunch of
>craps as the printing on these printer is extremely slow and we face
>a lot of truncation problems related to it. DEC Singapore was
>not able to help us on this and admit that the printing emulation
>software (which DEC acquire from a third party) was not effective on this.
 
I think "boast" and "crap" is a little too much here. :-)
 
>   Last - the server cost for Novell is much cheaper than a DEC VAXstation.
 
Not necessary true any more. The prices for Vaxstations have dropped.
Furthermore, there is no licensing cost for a PATHWORKS server, only cost for
your PC clients. Cost for Novell, on the other hand, is tied to the server. Once
you total up the total cost, Novell is not cheaper than PATHWORKS.
 
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.
============================================================================
From: nallegk@OKRA.MILLSAPS.EDU (Nalley, Gary K.)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Problems with PC and MAC sharing a file service
Date: 11 Nov 92 21:10:52 GMT
Content-transfer-encoding: 7BIT

> I have a fileservice on a VAX that is accessible from both PC, Mac and
> VMS. The problem is that if a PC wants to delete a directory it can not
> do that due to the fact that MSA has created subfolders in the directory
> that the PC can not see and therefore cannot delete. From the Mac there
> is no problem with deleting files. To delete files from VMS one have to
> use the command DELETE/ACL before one is allowed to delete the
> directories.
>
> My question is: Does anybody know of a workaround to let the PC delete a
> directory that is empty, but has subdirectories that the PC can not see
> due to that the file names are to long?
>
> If there is not a workaround is not this a weak point in the integration
> of PCs and Mac that DEC ought to fix, or is it just me that has such
> problems?
>
>
> Gunder Soensteby
> EDP-dept
> Norwegian School of Economics and Business Administration
> Norway
 
The problem is not DEC's it's MicroSoft's and DOS's.  DOS does not recognize
filenames over 8 char for name and 3 for extention.  DEC can't show these to the
PC because how do you tell DOS the difference between them to diffrentiate?
 
	MOUSE.PRG1
	MOUSE.PRG2
 
	or
 
	PHILPAPERKANT.WP
	PHILPAPERDESCARTES.WP
 
As far as I know, there is no workaround DOS's limited capabilities.  (Besides
switching Operating systems)
 
Gary
 
	+-------------------------------------------------------+
	|   Gary. K Nalley	   Network Specialist           |
	|   Computer Services      nallegk@okra.millsaps.edu    |
	|   Millsaps College       nalley@decus.org             |
	|   1701 N. State St.      Fax:    601.974.1168         |
	|   Jackson, MS 39210      Voice:  601.974.1140		|
	+-------------------------------------------------------+
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Pathworks vs. Novell (?)
From: MIGUEL@NET.EBT.ANRJ.BR
Date: Fri, 6 Nov 1992 09:06:00 BSC
Content-transfer-encoding: 7BIT
Comments: @FPSP.FAPESP.BR - @FPSP.HEPNET - @BRFAPESP.BITNET - .BR gateway

Hi there,
 
We are a 12000 employee telecom company with a 1.5 billion revenue spread all
over Brazil (a large country) with a corporate net based on IBM, VAXes, and
desktops. We picked Pathworks over Novell to integrate our 3,000 PCs nationwide.
Why? Try to integrate applications with a Novell net...
 
We tested Novell, LanManager and Pathworks (Banyan is not around here) and
Pathworks easy of integration in a multi-vendor environment was far (by
light years) superior to the others. Novell performed extremely well, but it
lacked the ability to be as interoperable as my business needed to be.
 
To tell you the truth, Novell is a very nice solution for a small, local, PC
based net. But, when we are talking Corporate, they just dont have it. It does
perform well, tough, specially with 486 machines as servers.
 
Miguel
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Problems writing to file and disk services
From: "(bachism)" <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 10 Nov 1992 09:54:11 -0500
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"

I just had the same problem with the RMS protections.  Changing the VMS
protection does not change the file services RMS protection.  In order to do so
you must delete the fileservice (don't delete the VMS directory and files.) and
the add it again at the pcsa command line specifing the default RMS protection.
For the disk quota you may want to check if they are enabled and who you are
logged on as when trying to add the service.
Newsgroups: vmsnet.networks.desktop.pathworks
From: apple@drvax3.msfc.nasa.gov (Kathleen Applegate)
Subject: Station Address and the Ethernet Packet
Summary: Query:  Ethernet Packet uses the MAC address or the Station Address?
Keywords: station address
Organization: NASA/MSFC
Date:  5 Nov 92 14:34:29 GMT

Which address is used in the ethernet header for the packet
going out on the wire:

    - The hardware address hardcoded onto the ethernet
      card (e.g. 08:00:2B:25:D9:A6)?
    - Or, the station address whose last three number
      sets are calculated based on the DECnet address
      (e.g. AA-00-04-00-B9-23)
                     ^^^^^^^^ calculated

            ^^^^^^^^based on IEEE vendor IDs in the MAC address.

DEC Tech Support just told me that it is the calculated address
that goes into the packet, and that the other will not appear in
any of the packet headers.   

So this is a reality check--can this really be true?
--
Kathleen Applegate, Sr. Analyst      apple@drvax3.msfc.nasa.gov           
Marshall Space Flight Center             Voice:  (205) 544-7656
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: PathWorks DECnet and PathWorks TCP/IP
From: "(bachism)" <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 09 Nov 1992 19:25:24 -0500
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"

You can run dual protocols, but it takes some configuration and the use of the
enhanced redir with Pathworks 4.1.  This is only if you want to access file
services using both tcpip and decnet.  If you only want to access fileservices
via one of the two that's even simpler.