HDTenEightyP/NetNews huggingface dataset:
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Is there a 'Maximum # of files' limitation on a virtual disk
Date: 12 Jan 93 05:01:44 GMT
Organization: Digital Equipment Corporation
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                    WARFORD@UTHSCSA.BITNET (CRAIG WARFORD)
>       RE: Is there a 'Maximum # of files' limitation on a virtual disk
>
>As was mentioned in another message on this list (via a qoute from Peter
>Norton) the number of root directory entries on a DOS-formatted disk is
>based upon the size of the disk.
>
>It's important to remember, however, that with Pathworks services, we are
>not necessarily using DOS-formatted disks, but rather a simulation by
>Pathworks of a DOS-formatted disk.  (Remember, you can't access physical
>sectors on a network drive.  Even "Norton the Great" can't do that.)  For
>example, if you have a service on a VAX, the formatting is not DOS format,
>but is made to appear as such by Pathworks.
>
>Therefore, the limitation may not be that of DOS, but of the simulated
>DOS listing by Pathworks.

    PATHWORKS file services do not have a FAT (File Allocation Table),
    and are, thus, not subject to FAT limitations (in terms of root
    directory size, disk size, etc.). Rather, their limitations come
    from the server's native file system (RMS on VMS, UFS on ULTRIX/SCO,
    FAT or HPFS on OS/2, etc.)
    
    PATHWORKS disk services ("virtual disks", LAD's [Local Area Disks],
    DECnet-DOS virtual disks [NDU, Network Disk Utility]), however, do
    have a FAT and are, in fact, formatted as DOS disks (when a LAD disk
    is created, the PCSA_MANAGER utility automatically formats it, but
    LAD's can also be formatted from DOS over the network with the pure,
    vanilla DOS FORMAT command).
    
    I.e. Disk size with LAD's matters just as much as it matters on local 
    disks (LAD disks can range in size from 360KB to 512MB).
    
    ...petri (petri.backstrom@ljo.mts.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
From: dmmatt@bigez (Mike Mattix)
Subject: Paradox/SQL Link/Rdb Headaches
Organization: Monsanto Agricultural Company
Date: Thu, 7 Jan 1993 17:36:50 GMT

I bring this up here because Q+E to Rdb has been discussed here before.

I am having a dreadful time making Paradox and SQL Link work properly
when accessing DEC's Rdb.  I have tried it with both 3.5 and 4.0.  I 
am attempting to connect to a database via an SQLSELECTCONNECT statement
where I have a Paradox screen prompt for Username and Password and then
supply this information with the VALUES parameter list.  When I do this
the messages at the right bottom of the screen tell me that I have connected
to the database but do not tell me I have opened it.  When I attempt to 
perform a query a remote table from the next script in the application it
tells me there are 'No images present' and bugchecks.  If I attempt the 
query the remote table manually it prompts me for a Username and Password
again and then performs the query.  When I use the Connections screen it 
tells me I have connected to and opened the database and then queries 
can be performed as usual.  I have tried many other combinations and am
getting more confused by the hour.  

Questions:

 1) Are there any problems moving the replica tables from one directory to
    another?  I have done this, is this the problem?

 2) Any special setups in SQL Services on the VAX?  I am running the 'out
    of the box' version with no configuration modifications.

 3) Any other ideas??

Please help my sanity is going....


-- 
Mike Mattix
Agricultural Group of Monsanto
P.O. Box 174
Luling, LA 70070
INTERNET Address: dmmatt@bigez.monsanto.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Pathworks Mail - carbon copy syntax
From: Alan Cantrell <CANTRELL@VUCTRVAX.BITNET>
Date: 08 Jan 1993 15:18:38 -0600
MIME-version: 1.0
Content-transfer-encoding: 7BIT

>From: Carl Houseman <houseman@TURING.ORG>

>properly.  If you want copies to yourself, you'll also note that the VMS
>COPY_SELF settings aren't observed (another reduced functionality compared
>to PW 3.0 PCMAIL), instead you have to use MAILSETU to get yourself a copy,
>or write yourself in on the CC: line.

Or you can enter SET COPY_SELF /ON at the MAIL> prompt.

>Carl Houseman
>GENICOM Engineering
>houseman@turing.org (good only through 1/8/93)

Alan Cantrell
Vanderbilt University Computer Center

cantrell@ctrvax.vanderbilt.edu
CANTRELL@VUCTRVAX
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Pathworks Mail - carbon copy syntax
From: Alan Cantrell <CANTRELL@VUCTRVAX.BITNET>
Date: 08 Jan 1993 08:09:53 -0600
MIME-version: 1.0
Content-transfer-encoding: 7BIT

All that's necessary is to insert a line in the message similar to the
following:

        CC:     user1,user2,...

Try it and see what happens.  There may be another way. Don't know.

--Alan
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: kermit program
From: TKENNETT@BENTLEY.BITNET
Date: 04 Jan 1993 10:15:00 -0400 (EDT)
Content-transfer-encoding: 7BIT
Comments: Warning -- original Sender: tag was TKENNETTE@BENTLEY

>>>Subject: kermit program
>>>
>>>The second problem is trying to upload MS-DOS exe files from VAX to MSDOS
>>>machine using kermit file transfer.  I try to set both kermits to binary
>>>but after the file has been transfered, it does not run.  Any solution to
>>>this?
>>>
>> Please post replies or carbon them to me.  I have the same problem.  I've
>> "solved" it by uu-encoding and decoding, and sending ascii files, but this
>> obviously dramatically increases transmission file sizes, which I want to
>> avoid.  Thanks.
>> David W. Garber (garber@aru.dom.uab.edu)
>
>If the VMS file has file/record org stream_lf, Kermit may not handle binary
>down load correctly.  Try changing the file/record org to fixed length
>record, 512 bytes then Kermit down loading.
>
We have encountered the same problem when using Kermit-32 on VAX VMS.
The solution that I found was to obtain the most recent version of Kermit(5A)
And setting the file type to IMAGE.  This retains all the DOS/Pathworks
attributes of any executable/binary file transferred.

****************************************************************************
* Ted Kennette             Bitnet: tkennett@Bentley.Bitnet                 *
* Systems Manager                                                          *
* Bentley College           "Hey waiter, there's a bug in my soup!"        *
* 175 Forest St.                 "That's not a bug, It's a feature!"       *
* Waltham Ma. 02154                                                        *
****************************************************************************
From: jasper@molbiol.ox.ac.uk
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Digital answer to VMS pthwks print problem.
Date: 8 Jan 93 18:25:02 GMT
Organization: Oxford University Molecular Biology Data Centre
Nntp-Posting-User: jasper

In article <2362@sousa.tay.dec.com>, burrows@brons.enet.dec.com (Jim Burrows) writes:

> 
> Hi. I'm the Macintosh Technical Lead in the PATHWORKS group, and I
> can understand your annoyance. I'm a bit perplexed as to who the
> "Service person" talked to. 

Welcome to the real world of dealing with PW for Mac and CSC.... If they don't
understand it as a bug then its a feature, 'cos that will get you off the
line. Normally it doesn't get the customer on the Net. Actually I don't think
that the CSC people know about the Net and the engineers reading it! 

Personally my experience of the CSC here was that they could do with some 
in depth training, especailly about Macs.... and perhaps a comprehensive set 
of hardware to test problems with!

regards,   jasper

jasper@molbiol.ox.ac.uk
From: yingling@gw.wmich.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Infoserver 100 for Remote Boot
Date: 5 Jan 93 17:02:46 EST
Organization: Western Michigan University

Greetings All!  Hope you all had a good holiday...

I need some help in making an Infoserver 100 service MOP requests to 
PC's using PW4DOS.  Here are a few germane bits of data with 
respect to our setup:

	DOS 5.0
	PW 4.1 (using DECnet)
	120 (hard) diskless PC's
	80 hard drive equipped PC's

	DEPCA_H has been installed on the Infoserver
	MOP services have been enabled
	Partition is named: DEPCA_H
	Infoserver has not been rebooted (at least not since MOP service was 
	  created/enabled)
	
The point is that the Infoserver DOES receive the REQUEST for MOP service, 
but there is no evidence that any further action is done by the Infoserver.

I thought that I read here that several of these PW4DOS sites were 
using the Infoserver for DEPCA_H.TSK files (i.e. the MOP service files for 
DEPCA equipped PCs) on diskless remote boot machines....if any one that 
might be able to help needs more data, let me know!

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
From: ralph@rlg80.enet.dec.com (rlg80::ralph)
Subject: LANSESS & Windows
Organization: Digital Equipment Corporation
Date: Tue, 5 Jan 1993 05:00:26 GMT
X-Posted-Via: NEWS-NOTES gateway (a hack!)

  
  To fix your problems with LANSESS & Windows upgrade the following files to:
             DECNET.386 ->  V4.1.11
             DECNB.386  ->  V4.1.11
             DNNETH.EXE ->  V4.1.127
  They should be available through the DECPCI forum on Compuserve or through
  DEC support channels.

  - Ralph

Newsgroups: vmsnet.networks.desktop.pathworks
From: houseman@Turing.ORG (Carl Houseman)
Subject: Re: Is there a 'Maximum # of files' limitation on a virtual disk??
Organization: The Turing Project, Public Access Internet Host
Date: Mon, 4 Jan 1993 15:44:29 GMT

In article <01GT133IDFQAA4L849@Meena.CC.URegina.CA> "A. Mahendra Rajah, System Manager" <MAHENDRA@MEENA.CC.UREGINA.CA> writes:
>    Does anybody know if there is an upper limit on how many files one can
>    store in any directory on a virtual disk? We are trying to do the
>    following:
>    1.    All Win31 files are on a file service (say) W:
>    2.    Create a 64MB disk service on the server - call it H:
>    3.    Connect to both W: and H: from a PC.
>    4.    XCopy or just plain copy all files from W: to H:
>    Step 4 fails after copying 511 files and cmplains "cannot make a
>    directory entry" for any more files.
>
>    Is this normal? Is there a workaround? Am I missing something very
>    obvious? (It is 4:19 AM right now).

There is a limit to the number of files in the root directory of a DOS disk.
The workaround is to create a subdirectory (i.e. H:\WINDOWS) and copy the files
there.  Subdirectories have no fixed limit on the number of files they may
contain.

>    -- mahendra (A. Mahendra Rajah :: Mahendra @ Meena.CC.URegina.CA)
>       System Manager, Dept of Computing Services, University of Regina,
>       Regina, Sask., Canada.

Carl Houseman
GENICOM Engineering
houseman@turing.org (address may not be good after Jan 8, 1993)
From: hogstedt@ae.chalmers.se (Per Hogstedt)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Need Customer Feedback!
Date: 12 Jan 93 02:19:09 GMT
Organization: Dept. of Applied Electronics. Chalmers Univ. of Technology.

In article <1993Jan7.045820.23005@nntpd.lkg.dec.com>, wasser@ranger.enet.dec.com (ranger::wasser) writes:

Let's take the disagreements first :-)
> 	Unfortunately is is hard to justify adding features
> 	to PC DECwindows Motif when we give it away free
> 	with PATHWORKS for DOS.  With no feedback in the

No, no and no once again; you are _not_ "giving it away for free".
DECwindows was a part of the product (PCSA) we evaluated in competition
with other alternatives many years back. Part of a product we decided to
buy, to pay licence fees for and finally have a service agreement with
DEC on. We keep our part of the agreement, partly to make it possible for
dedicated people at DEC to _develop_ the product (and debug it...).
I'm not very fond of the idea of having that effort on our part being
used to support "smart" marketing gurus that once again, after entering the
DEC marketing think tank, comes up with the brightness we've seen happen
before: "Hey - now we've got a nice base of installations - let's strip the
goodies of the product, make them into separate products and have them (=us)
pay for it once again!"
So, to summarize, I feel we have a mutual agreement that DEC should be
nursing, especially in those cases when the software is an important part
of a computing strategy involving the use of mini-servers (VAXen) and
PC-based workstations. For example, every DECwindows/MOTIF user is an argument
why we should not throw out the VAXen and go for micro based servers.

OK, feeling much better now...

And about PC DECwindows Motif: It's very valuable to us, we use it a lot here
and even if it may have it's flaws, we think it should be supported, developed
and _not_ be put in the fridge by the nice guys in nice suits!
If DEC has other intentions that this, let us know and we'll see how much
pressure the Mill can take :-)

I also hope that you John, Petri and others at DEC keep up the good work
in this forum - it's good to have you around every now and then.

> 			-John A. Wasser
> 			 Project Leader (and only remaining engineer)
                                             ^^^^^^^^^^^^^^^^^^^^^^^
                                             Say it 'aint true???
> 			 PC DECwindows Motif
> 			 PC Integration Group
> 			 Digital Equipment Corporation
-- 
   Per Hogstedt               Internet:  hogstedt@plab.se
   Lindholmen Utveckling            or:  hogstedt@ae.chalmers.se
   P.O. Box 8714              Phone...:  +46 31 50 70 50
   S-402 75 Gothenburg        Fax.....:  +46 31 51 53 13
   Sweden                     MiniCall:  +46 74 35 68 49
From: karcher@jevex.waisman.wisc.edu
Subject: RE: LANSESS, NET USE, MS WINDOWS
Organization: Waisman Center, University of Wisconsin-Madison
Date: 4 JAN 93 21:26:44 CST

In a previous article, houseman@Turing.ORG" wrote:
>No, actually I was speaking of CSCPAT #3037, which you asked about in a
>separate e-mail message.
> 
>BUT, since you mention it, does CSCPAT #3046 contain drivers more recent than
>those which ship with Windows 3.1?
> 
Yes. 3046 includes the latest network drivers (which fix the "USE from a DOS
window with Lansess problem"), Dec printer drivers and the WINRCV program for
windows. So it looks like either CSCPAT #3046 V1.3 or CSCPAT #3037 V1.6
will fix the problem. Note that prior versions of these patches do NOT fix the
problem.


Carl Karcher                          Internet: KARCHER@WAISMAN.WISC.EDU
Waisman Center                        Bitnet:   KARCHER@WISCMACC
University of Wisconsin-Madison       PSTnet:   (608) 263-5896
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: LANSESS & Windows Fixes
From: Alan Cantrell <CANTRELL@VUCTRVAX.BITNET>
Date: 08 Jan 1993 15:26:31 -0600
MIME-version: 1.0
Content-transfer-encoding: 7BIT

>  To fix your problems with LANSESS & Windows upgrade the following files to:
>             DECNET.386 ->  V4.1.11
>             DECNB.386  ->  V4.1.11
>             DNNETH.EXE ->  V4.1.127
>  They should be available through the DECPCI forum on Compuserve or through
>  DEC support channels.

>  - Ralph

Forgive me if this should be obvious, but how can you tell what version of
these files that you have?

--Alan

Alan Cantrell
Vanderbilt University Computer Center

cantrell@ctrvax.vanderbilt.edu
CANTRELL@VUCTRVAX
From: biol_res@gw.wmich.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: HP printers problems...HELP
Date: 6 Jan 93 23:15:04 GMT
Organization: Western Michigan University

X-News: wmichgw vmsnet.networks.desktop.pathworks:4724

>From: "Nalley, Gary K." <nallegk@OKRA.MILLSAPS.EDU>
>Subject:RE: How to use a non-DEC postscript printer???
>Date: 30 Dec 1992 17:57:24 -0600 (CST)
>Message-ID:<00965DF4.52D088C0.9911@okra.millsaps.edu>

>
>It's my understanding that you have to create a generic queue to use with
>non-DEC (or unsupported) printers and not use the CPS software.  This is due to
>all the "communication" that DEC printers have with VMS.  The CPS software will
>only work with DEC, HP, Apple, etc. printers (I can't remember the whole
                     ^^^^???
>supported list off the top of my head).
>
>We are using postscript IBM 4019s and 4029s on generic queues and sending the
>appropiate control codes in FORMS to change the printer's data stream between
>the PPDS, plotter, PCL and Postscript modes.
>
>E-mail me if you need more information on what we are doing>
>
>        +-------------------------------------------------------+
>        |   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         |
>        +-------------------------------------------------------+
Sir,

In your posting I noticed that you have mentioned that you got HP printers
to work with Pathworks...? I've called HP and DEC support several times
on this issue and all they replied was that HP Postscript (or any other
postscript printers except DEC) are not supported ina Pathworks
environment. They we desired was that the HP Postscript IIIP printer would
run off the parallel port of a PC and would be configured as a queued
printer, then on the VMS side a queue was set up for it. The problem is
that it prints sometimes and sometimes it does not print. When a print
job is sent to it from an application (say WP or 123) it kicks the
print queue into a stalled/paused/stopped state. There is no say to which
state it would go to. Then we would have to manually stop and reset the 
queue. There have been instances where the whole queue had to be rebuilt.

We are not using any extra software, cause DEC said that they have
a 3rd party software which would only work with DEC postscript printers 
(how selfish of them). If any netter got either a HP postscript
printer or a NEC silent writer (model 95 or 890) to work, could you 
please share the information with me/us.

I really do not know why DEC has held back on the printing over the
network with other printers...to boost their sales in postscript
printers...? Well if that is the case they should realize that they
are loosing quit a few customers wanting to go for Pathworks but
eventually backing out due to the various printing problems. (my thought)

Once again if anyone has a solution for the printing problem please
share 
Thanks
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Is there a 'Maximum # of files' limitation on a virtual disk??
From: CRAIG WARFORD <WARFORD@UTHSCSA.BITNET>
Date: 08 Jan 1993 12:09:25 -0500
Organization: The University of Texas Health Science Center at San Antonio
X-VMS-Cc: WARFORD
MIME-version: 1.0
Content-transfer-encoding: 7BIT

>>Hello:
>>
>>    Does anybody know if there is an upper limit on how many files one can
>>    store in any directory on a virtual disk? We are trying to do the
>>    following:
>>
>>    1.    All Win31 files are on a file service (say) W:
>>    2.    Create a 64MB disk service on the server - call it H:
>>    3.    Connect to both W: and H: from a PC.
>>    4.    XCopy or just plain copy all files from W: to H:
>>
>>    Step 4 fails after copying 511 files and cmplains "cannot make a
>>    directory entry" for any more files.
>
>Isn't that the limit on the number of directory entries that can be in
>the root (\) of the disk?
>--
> Jaye Mathisen, COE Systems Manager                (406) 994-4780
> 410 Roberts Hall,Dept. of Computer Science
> Montana State University,Bozeman MT 59717      osyjm@cs.montana.edu
>

As was mentioned in another message on this list (via a qoute from Peter
Norton) the number of root directory entries on a DOS-formatted disk is
based upon the size of the disk.

It's important to remember, however, that with Pathworks services, we are
not necessarily using DOS-formatted disks, but rather a simulation by
Pathworks of a DOS-formatted disk.  (Remember, you can't access physical
sectors on a network drive.  Even "Norton the Great" can't do that.)  For
example, if you have a service on a VAX, the formatting is not DOS format,
but is made to appear as such by Pathworks.

Therefore, the limitation may not be that of DOS, but of the simulated
DOS listing by Pathworks.

Try copying the files to a subdirectory, then connecting a drive to that
subdirectory.  I don't know what it will do if the files are already there
when you connect.  It may blow up, but I'd like to see what happens.

                                WAR          warford@uthscsa
From: frzmtdb@aspentec.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Looking for snftobdf program for pathworks.
Date: 12 Jan 93 01:09:15 EST
Distribution: world
Organization: Aspen Technology, Inc. Cambridge, MA.

Hi.

does anyone have a snftobdf program for DEC pathworks???

thanks,
-- 
----
Fred R. Ziegler               Email: <ziegler@aspentec.com>
Aspen Technology, Inc.        tel:   +1-617-577-0100 x262
Ten Canal Park                fax:   +1-617-577-0303
Cambridge, Ma. 02141          telex: +1-948-038(ASPEN TECH)
U.S.A.                        
Internet Society Member (#1315080) since Feb 1992
From: ES12453@SWTEXAS.BITNET
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Notification of All-in-1 Mail
Date: 7 Jan 93 17:30:00 GMT
Content-transfer-encoding: 7BIT
X-Original-To:  pathworksng, ES12453


   Hello all.

   Does anyone know of a way to notify a Pathworks user when they receive
   mail in All-in-1 IOS?  I'm looking for something similar to the message
   that interactive users get when they receive All-in-1 mail.  This way a
   Pathworks users does not have to have a terminal session running in order
   to get new mail notification.

   Thanks for your help.

*****************************************************************************
* 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...       *
*****************************************************************************