HDTenEightyP/NetNews huggingface dataset:
From: finkel@sdi.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Disk Services not network devices with WIN3.1
Date: 12 Aug 92 16:47:33 CDT
Organization: Systems by Design of Illinois (SDI), Chicago


Folks,
	Anyone know a workaround to this?  Micrsoft says it's DEC's
	problem.

	BACKGROUND: network drive is MSDOSDSK
		    node is ORPHEO
		    execute command : USE ?: \\ORPHEO\MSDOSDSK /V
  		    connected drive is E:

	Within WIN3.1:

		Command: E:
		Results: Default drive is E:; all is OKAY

		Command: FILE MANAGER | DISK | SELECT DRIVE
		Results: Drive E: has no volume label; all is NOT OKAY

		Command: FILE MANAGER | DISK | NETWORK CONNECTIONS
		Results: Drive E: is not listed; all is NOT OKAY

		In general, only File Services are known as network 
		devices; Disk Services are not known as network devices
		and are treated by WIN3.1 as local floppy drives

	Thanks in advance,

/Joel
	
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

		     vote for RON DANIELS for president

  Joel R. Finkel   Systems by Design of Illinois (SDI) 	 finkel@sdi.com

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Newsgroups: vmsnet.networks.desktop.pathworks
From: duffiem@wl.com (Mark Duffield)
Subject: Re: Installing Pathworks for VMS on Mac
Organization: Warner Lambert / Parke-Davis
Date: Fri, 21 Aug 1992 18:05:28 GMT

In article <weissh.25.0@nextadm.cc.vt.edu> weissh@nextadm.cc.vt.edu (Hugh Weiss) writes:
>In article <15058@umd5.umd.edu> bleau@umdsp.umd.edu writes:
>[...]
>
>> I don't know much about Appletalk protocols, but it appears, from reading 
>> the installation instructions, that I have to have the Decnet/Appletalk 
>> gateway running on the VAX in order to do much of anything else.
>
>It depends on your setup.  If you have Macs only on Ethernet, then you will
>probably not need the AppleTalk-DECnet gateway (ADG).  The ADG is *only*
>useful if you have Macs on LocalTalk segments sitting behind AppleTalk
>Internet Routers.  You can ONLY talk AppleTalk across LocalTalk.  So in
>this case you talk AppleTalk across the LocalTalk segment, throught the
>AppleTalk Internet Router, across the Ethernet to the ADG on the VAX 
>where it is pulled off the wire, converted to DECnet and put back on the
>wire for transmission to the ultimate DECnet destination.  The ADG allows
>your LocalTalk connected Macs to talk to DECnet hosts even though they
>themselves cannot talk DECnet.  There is an AppleTalk-LAT gateway that
>functions the same way for communicating with DEC systems talking LAT.
>Again, the AppleTalk-LAT gateway is only useful if you have LocalTalk
>connected Macs that want to talk to DEC systems using LAT.
>
The AppleTalk-DECnet Gateway DEFINITELY IS useful on ethernet.  I am running
A/UX 3.0 and am only able to use Mail for Macintosh if I use the gateway.  This
is because the DECnet implementation shipped with PathWorks DOES NOT WORK under
A/UX.  Even the experimental "unsupported" PathWorks Listener works in this
manner.  For those interested, there doesn't seem to be any performance
advantage or disadvantage to using the "ADG" over DECnet proper.

DEC, if you are listening, PLEASE get DECnet to work under A/UX.  I am
getting by with the ADG, but it would be nice to be a TRUE DECnet node.  In
addition, if would also be nice if the AppleTalk-LAT Gateway were implemented
on the VAX and not through a Macintosh.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Mark J. Duffield          | 
 Parke Davis Biotechnology |   Beer is a beverage, not a projectile.
 (duffiem@wl.com)          | 
Newsgroups: vmsnet.networks.desktop.pathworks
From: uujanze@ccu.umanitoba.ca (Rob Janzen)
Subject: Bookreader
Keywords: Argh!
Organization: University of Manitoba, Winnipeg, Canada
Date: Thu, 13 Aug 1992 01:18:18 GMT

Well, our office is in the middle of a move, and I had a need to look up
a VAX error message today. Seeing as the manuals are currently in a different
building, I thought this would be a good time to see how well eXcursions was
working.

Argh!!!!!

Did the people who wrote the Bookreader program never have to use it?

While the display was great, TRY TO FIND THE INFORMATION YOU NEED!

Ok, the first thing I did was look through System Errors manual, and was 
really annoyed with that you could not advance to a specific letter of the 
alphabet, but had to advance topic at a time until I advanced to the point
I wanted.

Of course the error message wasn't there (it wasn't a system error message).

So then I look for the master index of the volumes... Hmm, doesn't seem to be 
one... Ok, then I started having to look through each book trying to find
the message. Gee, you can't even search for a word or phrase within the book.

So... the point of this message... Is there a Digital or 3rd party product 
which will actaully do a *good* job of making the on line docs readable?

Rob Janzen 		(uujanze@ccu.umanitoba.ca)
Newsgroups: vmsnet.networks.desktop.pathworks,comp.os.ms-windows.misc
From: dbk@pslu1.psl.wisc.edu (Don Katz)
Subject: Running the PATHWORKS USE command in an MS-DOS Windows hangs system
Organization: Physical Sciences Lab, UW-Madison
Date: Fri, 14 Aug 92 17:22:42 GMT

We are running Pathworks 4.1 (server and client) on a heap of PC's. I
find that when I am running Windows 3.1, if I open an MS-DOS window
and then run the Pathworks USE command in the window, the USE command
gives the correct output. If I then type exit, I receive a message
from Windows that 

"The application was communicating on the network when you terminated
it. Windows was unable to restore the state of the network. You need
to restart your computer."

I can then return to the program manager, but on one machine,
attempting to leave Windows hangs the system, and on another machine,
I can leave Windows, but running USE from the DOS prompt then hangs
the system.

What is going on, and how can I avoid this problem?

Don Katz
dbk@psl.wisc.edu

-- 
-----------------------------------------------------------------------------
Don Katz                                .         Physical
                                       .- / \ -.      Sciences
University of Wisconsin - Madison   ./'  /+-+\  `\.       Laboratory   E-MAIL
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Problems with HP IIIsi printing
From: "Gordon Cressman RTI (919) 541-6363" <GMC%SSIDW1@RTI.BITNET>
Date: 17 Aug 1992 13:04:10 -0400
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Thanks to all who responded to my description of problems printing to HP
IIIsi printers over PATHWORKS.  To recap, graphics and complex documents were
consistently printed with missing and misplaced characters and garbled
graphics.  The IIIsi's are connected to the network via DECserver 200,
DECserver 300, and third party terminal servers via serial lines at speeds up
to 19.2K bps.
 
As several people suggested, converting from software XOn handshaking to
DTR/DSR hardware handshaking solved the problem.  The change was made only at
the terminal servers.  No change was necessary in the printer setup.
 
-gmc
From: ronm@slc.slac.stanford.edu (Ron MacKenzie)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: PW for MAC v1.1 upgrade savesets
Date: 12 Aug 92 18:52:59 GMT
Organization: Stanford Linear Accelerator Center



Hello friends in network land.

I'm about to upgrade from v1.0 to v1.1 of pathworks for mac.
I understand that they broke the product into two kits, one for the server
and one for the client.  I received two sets of savesets named 
MSAUS011 and MSA011.  I suspect that MSA011 is the server, the other is the
client.

My question is... Is it necessary to install both to upgrade from 1.0 to 1.1?
The Pathworks for VMS server (macintosh) release notes say on page 1 that
only the server software is updated with this release.  Does that mean that
I only need to vmsinstall the MSA011 savesets and that the MSAUS011 savesets
are only provided for completeness and in case someone is doing an 
initial installation and not an upgrade like I am?

Thanks in advance,
Ron

ronm@slc.slac.stanford.edu
-- 
 
============================================================================
Ron MacKenzie
Stanford Linear Accelerator Center                    Phone: (415)926-2490
P.O. Box 4349                                         Fax:   (415)926-3515
Stanford, Ca. 94309
                                      Internet: ronm@slc.slac.stanford.edu
============================================================================
From: SPITZBARTH@UCS.UWPLATT.EDU (Edward Spitzbarth, Manager of Desktop Computing)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Windows front end for LOGIN
Date: 21 Aug 92 21:16:00 GMT
X-Organization: University of Wisconsin--Platteville
Content-transfer-encoding: 7BIT

Has any seen, written, know of, a method of doing a LOGIN (connecting
a VAX account to a DOS drive) via Windows?  I need something that
faculty could use without too much instruction (which eliminates stuff
like NFT, etc.).  Connecting via LOGIN works fine, but I need someway
that they can do it from windows without going to the DOS prompt, etc.
 
Thanks,
 
Ed Spitzbarth
Manager of Desktop Computing
University of Wisconsin at Platteville
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Problems with WP Office 3.1
From: 002060@vaxd.northwest.missouri.edu (Sean M. Sheil)
Date: 18 Aug 92 09:39:53 CST
Organization: Northwest Missouri State University


I am installing WordPerfect Office for PC Lan's ver 3.1 (1/31/92)
Everything works fine on local boot machines.  However there 
appears to be a problem with remote boot.  I haven't had time to
fully diagnose the problem.  However, if someone has installed
this package, I am open to comments and/or suggestions on how to
proceed.  Please e-mail me at the below address.  If their appears
to be enough interst in this topic I will summarize.

Thanks in advance,

sean

------------------------------------------------------------------------------
   Sean M. Sheil                    Title:     Sr. Programmer
   Computing Services               Internet:  002060@northwest.missouri.edu
   Northwest Missouri State U.      Phone #:   (816) 562-1135
------------------------------------------------------------------------------
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: VT320: random tabs or spaces are inserted in the screen output
From: MARK@OJC.COLORADO.EDU
Date: 16 Aug 1992 17:44:44 -0600
X-VMS-Cc: MARK
MIME-version: 1.0
Content-transfer-encoding: 7BIT

        I've run into the same problem before, and I think it has to do
        with the DECterm fonts that come with Pathworks.  I fixed our
        problem by re-running the DOS win3setu program that comes on the
        pcsav41 system service.  I think that it's located in the \mswinv30
        directory.
 
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        ~       Mark Allen              | Internet: MARK@OJC.COLORADO.EDU ~
        ~       Computer Programmer B   | DECNET:   OJC::MARK             ~
        ~                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        ~       Otero Junior College                                      ~
        ~       La Junta, CO 81050              Curiosity killed the cat, ~
        ~       (719) 384-6830                  but for a while there I   ~
        ~                                       was the suspect.          ~
        ~                                               - Steven Wright   ~
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: Taisa_Monastyrski@mindlink.bc.ca (Taisa Monastyrski)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: PATHWORKS and AS/400?
Date: 21 Aug 92 22:21:53 GMT
Organization: MIND LINK! - British Columbia, Canada
Distribution: world

Help! We've been tearing our hair out trying to get PCs to talk to our VAX
(PATHWORKS 4.1) and our AS/400 (PC Support), and haven't had much luck. Has
anybody out there made this work? Any suggestions?

Thanks!

- Taisa
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: RCV utility for graphic mode?
From: "Federico A. Schlagel" <CCSA_13@RCKHRST1.BITNET>
Date: 21 Aug 1992 20:05:42 -0500
MIME-version: 1.0
Content-transfer-encoding: 7BIT

I just got back from DEC's PCSA system management class in Chicago, and
asked the "experts" the same question.  Currently there is no solution
to break-through graphics mode.  I guess we will have to wait for the
next release.
 
Fred Schlagel
Tech. Consultant
Marion Merrell Dow Inc.
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Windows front end for LOGIN
From: "Federico A. Schlagel" <CCSA_13@RCKHRST1.BITNET>
Date: 21 Aug 1992 20:15:33 -0500
MIME-version: 1.0
Content-transfer-encoding: 7BIT

An easy way to get around this is by:
 
1. Selecting FILE from the Program Manager
2. Clicking on RUN.
    This will bring up a window for end-user dos commands.
3. Type in <login servername username *>
 
This should get you rolling. I use it all of the time.  Since Login is
actually a .bat file which utilizes USE and runs AUTOUSER.BAT you
shouldn't have any problems.
 
Thanks,
 
Federico Schlagel
Tech. Consultant
Marion Merrell Dow
From: chiam@VULCAN.CBA.OHIOU.EDU (Ta Fuh Chiam)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Pathworks for VMS on Mac
Date: 21 Aug 92 14:23:01 GMT
Content-transfer-encoding: 7BIT

>We are having a problem with accessing an AppleTalk MAC server on
>Ethernet and at the same time accesssing a local printer.  They tell me
>that there is some problem with accessing local talk and appletalk at
>the same time.  We have applications on the server but can't print while
>we are accessing the server.
 
This is not a Pathworks problem. It is just a limitation of AppleTalk/Macintoh.
When you use the Ethernet port, your Localtalk port is not accessible at the
same time.
 
>Is this also true for PW for MACs 1.1?
 
If you place the local printer on the Localtalk network (daisy chain it) instead
of directly plugged into your MAC, you can get Pathworks to reroute printing to
the printer.
 
>I don't want to put every apple printer on the network.  Is this a
>problem with the Dot matrix printers as well as the laser printers?
 
Then, you are out of luck.
 
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: coopebl@OKRA.MILLSAPS.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Disk Services no network devices with WIN3.1
Date: 17 Aug 92 00:09:58 GMT
Content-transfer-encoding: 7BIT


     Sounds like your network startup procedure does not
   contain the USE/FIXUP command.  This command is part
   of the standard STARTNET.BAT created by NETSETUP.
 
     USE/FIXUP marks unconnected drive identifiers allocated
   to LADDRV.SYS as invalid.  These identifiers are "hidden"
   from DOS and Windows until a connection is made with a
   USE command or the the File Manger.
 
    Exit Windows and try the following:
 
       - Log to drive E: at a DOS prompt.  You should get a
         "Abort, Retry, Fail" prompt.
 
       - Issue a USE/FIXUP and try drive E:.  You should get
         an "Invalid drive..." message.
 
     If the above corrects the problem, stick USE/FIXUP back
   in the station's STARTNET.BAT.
 
					-brad.
 
Internet: coopebl@okra.millsaps.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Running the PATHWORKS USE command in an MS-DOS Windows hangs system
From: MARK@OJC.COLORADO.EDU
Date: 16 Aug 1992 17:42:47 -0600
X-VMS-Cc: MARK
MIME-version: 1.0
Content-transfer-encoding: 7BIT

        Instead of using the MS-DOS USE command, use the Network Connections
        option from the File Manager.  In the Network Path box, use the
        same syntax that you would use with the DOS command
        (ie \\server\service) and if the server requires a password, then
        enter the password into the password prompt.  You can select which
        drive you wish to connect to by clicking (or typing) the appropriate
        letter.
 
        Hope this helps,
 
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        ~       Mark Allen              | Internet: MARK@OJC.COLORADO.EDU ~
        ~       Computer Programmer B   | DECNET:   OJC::MARK             ~
        ~                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        ~       Otero Junior College                                      ~
        ~       La Junta, CO 81050              Curiosity killed the cat, ~
        ~       (719) 384-6830                  but for a while there I   ~
        ~                                       was the suspect.          ~
        ~                                               - Steven Wright   ~
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: TILLOTSON@ALISUVAX.BITNET
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Network name not found?
Date: 20 Aug 92 15:39:00 GMT
Content-transfer-encoding: 7BIT

>The Symptom: the PC is unable to find and connect to PCSAV41 common
>file service, or any other file service for that matter.  The
>specific message is:
>
>Now attempting connection to the system file service \\TRLN\PCSAV41
>Error: Network name not found
>
 
   What does NCP say when you do a LIST NODE TRLN? Is TRLN defined
   properly?  Is TRLN defined as MS-NET?  Perhaps the NCP database
   has become corrupted.
 
Jenett Tillotson
Ames Laboratory
515-294-7908
TILLOTSON@ALISUVAX.BITNET
Xref: sparky vmsnet.networks.desktop.pathworks:2537 comp.os.msdos.desqview:2743 comp.sys.ibm.pc.misc:11511
From: finkel@sdi.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Disk Services not known as network devices in WIN3.1
Date: 12 Aug 92 16:49:40 CDT
Organization: Systems by Design of Illinois (SDI), Chicago


Folks,
	Anyone know a workaround to this?  Micrsoft says it's DEC's
	problem.

	BACKGROUND: network drive is MSDOSDSK
		    node is ORPHEO
		    execute command : USE ?: \\ORPHEO\MSDOSDSK /V
  		    connected drive is E:

	At DOS 5.0 prompt:

		Command: E:
		Results: Default drive is E:; all is OKAY

	Within WIN3.1:
		Command: FILE MANAGER | DISK | SELECT DRIVE
		Results: Drive E: has no volume label; all is NOT OKAY

		Command: FILE MANAGER | DISK | NETWORK CONNECTIONS
		Results: Drive E: is not listed; all is NOT OKAY

		In general, only File Services are known as network 
		devices; Disk Services are not known as network devices
		and are treated by WIN3.1 as local floppy drives

	Thanks in advance,

/Joel
	
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

		     vote for RON DANIELS for president

  Joel R. Finkel   Systems by Design of Illinois (SDI) 	 finkel@sdi.com

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
From: PENTECOST@BROOK.BITNET (Gregg Pentecost X6228 IC44)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Infoserver as primary PCSA server
Date: 18 Aug 92 14:36:00 GMT
Content-transfer-encoding: 7BIT

> I would like to hear from someone who has gathered experience
> using the Infoserver as the primary PCSA server: Positive or negative
> experience, backups, prices (when compared to a Novell server), etc.
> Going PCSA only, what services will I not get when compared to Novell?
 
 
My only concern about this is that (correct me if I'm wrong,) an
Infoserver doesn't run VMS and can't run PCFS_SERVER, etc.  Perhaps this
is only true with the model we have.  We did use our Infoserver to offer
WordPerfect services for awhile, but we've switched all of our
applications over to a dedicated VAXstation 4000 VLC.  The Infoserver
service was definitely much faster than our primary server (an 8650,)
which ran the file and disk server, and is still used for time-sharing
and file services.
 
Gregg.
From: bleau@umdsp.umd.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Installing Pathworks for VMS on Mac
Date: 19 Aug 92 19:12:19 GMT
Reply-To: bleau@umdsp.umd.edu
Organization: University of Maryland Physics Dept., College Park, MD

I'm in the process of purchasing Pathworks for VMS (Macintosh) V1.1 and
Pathworks for VMS V4.1 and have a few questions.  I hope someone ahs had
experience in doing this and can advise me.

My university is part of DEC's TEI (The Education Initiative) and DEC's ESL
(Educational Software Library).  This allows us to get a wide variety of DEC
software products for free.  All we can do, though, is copy the product
savesets and install them.  We don't get a separate media for each of us (DEC
supplies one media set on CD-ROM) and we don't get any documentation (we can
buy it at 30% off, though).  MSA V1.1 (the Pathworks for the Mac) is available
through the ESL.  Something tells me, though, that you have to do something on
the Mac side to get it to be part of the Pathworks scheme of things.  What is
this?

Question #1: Is a separate media (diskette?) needed for the Mac to get it to
boot or otherwise start communicating with the Pathworks s/w on the VAX?  If
so, does anyone have a diskette I could just copy?  DEC's charging over $300
for media on this product.

Currently the Mac's are running TCP/IP and doing it rather nicely.  I'd like my
users to be able to continue to access other systems using TELNET, FTP, etc.
after Pathworks is installed.  I'm told, however, that Pathworks for the Mac
uses Decnet and/or Appletalk and can't use TCP/IP as a transport(?) layer.

Question #2: Is this statement true?  That I cannot use TCP/IP to communicate
between the Mac and the VAX Pathworks?  Even if it is, is there any way to use
some TCP/IP package in parallel with Pathworks on the Mac to still provide
TELNET and FTP capabilities?

I don't know much about Appletalk protocols, but it appears, from reading the
installation instructions, that I have to have the Decnet/Appletalk gateway
running on the VAX in order to do much of anything else.

Question #3: How does Appletalk fit into the scheme of things here?  Does the
Mac talk Appletalk, Pathworks on the VAX translates that to Decnet,
rebroadcasts it, and is picked up by another VAX with Pathworks, where the
disk/mail/print service is carried out?  Or does the Mac somehow send Decnet
packets directly?  We don't have Appletalk currently running, BTW, so this
seems like a lot of extra setup.

Last and final:

Question #4: Am I using the right product to provide these services for my
users?  What I'd like is file and print service, mail service, an X server for
the Mac, and some TCP/IP capability.  Pathworks is 4 out of 5, but is there
something else that gives all of the above?

Thanks, netters.  Send answers to me directly (bleau@umdsp.umd.edu) and I'll
summarize in a week or so.  Post if you feel it is of general enough interest.

Larry Bleau
University of Maryland
bleau@umdsp.umd.edu
301-405-6223
From: edi@hadassah.bitnet
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Infoserver as primary PCSA server
Date: 16 Aug 92 10:02:47 +0200
Organization: Hadassah Medical Center. Jslm Israel

I would like to hear from someone who has gathered experience
using the Infoserver as the primary PCSA server: Positive or negative
experience, backups, prices (when compared to a Novell server), etc.
Going PCSA only, what services will I not get when compared to Novell?

I'll be glad to get any replies connected to this subject.
Edi.
--
Edi Landau

Hadassah University Hospital, Jerusalem, Israel.
Bitnet: Edi@Hadassah       Phone: 972-2-447312/3
Newsgroups: vmsnet.networks.desktop.pathworks