HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: USE command and Windows 3.1 with explicit devicename
From: "Roel Alkema Kernfysisch Versneller Instituut, Groningen" <ALKEMA@KVI.NL>
Date: 12 Jan 1993 12:40:12 +0000
Delivery-receipt-to: alkema@KVI.nl
X-PS-Qualifiers: /FORM=A4/LEFT_MARGIN=36/TOP_MARGIN=36
X-VMS-Cc: ALKEMA
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Hello Window experts,
From Dos it is possible to connect to a fileservice on an device other than
then the logindevice by using the syntax:

use ?: \\server\disk$2:[username]%username *

Note: disk$2:[username] is also my own disk. (Only usable in pathworks 4.1-2
when on the serverside PCFS$SETDIR_ENABLE=true is present in the PCFS$startup
file.)

Now, if i want the same functionality from the fileservice menu in windows, it
is not  possible, you get a NETWORK error.

If the connection was made before starting windows, it shows up in the Current
Drive Connections, (without showing the device spec. so you can not see if it
is your disk$1 or disk$2 ... but it is usable)

Does anyone know how to make this connection from windows ?

Thanks, Roel

================================================================================
Roel D. Alkema                          Phone : +31 (50) 633617
Kernfysisch Versneller Instituut        Fax   : +31 (50) 634003
Zernikelaan 25                         E-mail : alkema@kvi.nl
9747 AA Groningen                     Surfnet : kviclu::alkema
NL Nederland                    X.25/PSI-mail : psi%15901047::alkema
================================================================================
Newsgroups: vmsnet.networks.desktop.pathworks
From: osyjm@cs.montana.edu (Jaye Mathisen)
Subject: New users can't use pathworks mail...
Organization: CS
Date: Sun, 10 Jan 1993 20:59:25 GMT



VAXstation 4000/60, VMS 5.5-2, Pathworks 4.1-2 

I haven't added any users with admin/pcsa in a while. So I do:

$ admin/pcsa add user/int xyzzy

go through all the screens just taking the defaults, and
it creates the account.  The account looks fine,
but if the user tries to run pathworks mail, they can't
get logged in, and it leaves a server process hanging around
on the vax.

There are no errors in the netserver.log for the account, no
errors in any file that I can find, they just can't
log in via mail.

If they use SETHOST, they have no problems getting on the vax
and using normal vaxmail, but no pcmail.

Just to test, I copied an old account record from a user who had
not had their account removed yet to the new account, and
changed the username stuff, kept the same UIC, changed the
rights identified, etc., and now the account works fine, but
again, no newer accounts will work.

I think this has become  a problem since the 4.1-2 upgrade, I don't
recall having this problem before then, but like I said, it's been 
a while since I added users.

If you have any suggestions/ideas, please drop me a line.  I will
summarize and post if demand warrants.

I'm thinking perhaps a PCSA database got corrupted, but I don't 
have any idea which one.
-- 
 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
Newsgroups: vmsnet.networks.desktop.pathworks
From: jpeterse@thiele.che.wsu.edu (James N. Petersen)
Subject: NE2000 drivers that work with Pathworks
Organization: Washington State University
Date: Thu, 7 Jan 93 00:42:09 GMT

I have recently obtained a Gateway 2000 laptop computer with an NE2000
compatible ethernet interface.  When I try to connect to the file server, it
fails.  I have had this problem before with systems that do not allow
the ethernet address to be changed, as is required for DECnet systems
under pathworks.  Thus, I am looking for updated drivers for the NE2000
that do work with Pathworks.  I am using version 4.1 of Pathworks for
DOS.

Thanks for any ideas.

Jim Petersen
jpeterse@thiele.che.wsu.edu
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: PW/Mac 1.1 and System 7.1
From: John Chadwick <CHADWICK@UNMB.BITNET>
Date: 12 Jan 1993 13:51:00 -0700 (MST)
Content-transfer-encoding: 7BIT

As I understand the problem with concerning PW 1.1 and Mac System 7.1, the fix
is going to have to come from Digital. I had heard a while back that Digital
was working on a fix, but nothing recently.

--john chadwick
tnchadwick@technet.nm.org
chadwick@bootes.unm.edu
From: richardb@extro.ucc.su.OZ.AU (Richard Banks)
Subject: disk space problems
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Tue, 12 Jan 1993 23:02:28 GMT

I have pathworks running on a 3100. Currently I have a problem where there is
45 Meg of free space on one of the disks that pathworks is using, yet a PC that
does a dir of any service on the disk in question will report no free space.

There is no diskquota on the disk, and pathworks works fine for services on
other disks (ie report free space).

If anyone has any ideas how I can fix this I would greatly appreciate it.

Richard Banks.
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Compatibility of pathworks copy and kermit transfer
From: Gregg Pentecost X6228 IC44 <PENTECOST@BROOK.BITNET>
Date: 12 Jan 1993 10:28:23 -0400
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

> Sometime ago I posted a porblem with regards to binary file transfer.  Well
> I was instructed to look into the c-kermit, which I did...thanks to all
> that responded.
>
> However, I am still facing this problem.  If I do a file copy through
> pathworks to the VAX system, and I download it to a PC through kermit, the
> program does not work.

We implemented a NETCONVERT command to "fix" the files before downloading
them with Kermit.  These commands are in the .COM file:

        IF "''P2'" .EQS. "" THEN P2 = P1
        EXCHANGE COPY 'P1 'P2/TRANSFER=BLOCK/CARRIAGE=NONE

Hope it helps.  Gregg.

PENTECOST@BROOK.BITNET

p.s. - I thought someone mentioned a SET FILE TYPE IMAGE command.  I
assume that didn't help?
From: makinc@hhcs.gov.au (Carl Makin)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Digital answer to VMS pthwks print problem.
Date: 11 Jan 93 14:16:33 +1100
Organization: Aust. Dept. Health, Housing and Community Services

In article <2362@sousa.tay.dec.com>, burrows@brons.enet.dec.com (Jim Burrows) writes:
 
> In article <1993Jan5.121438.569@hhcs.gov.au>, makinc@hhcs.gov.au (Carl Makin)
> writes:
 
> |>Well I finally got an answer back from Digital Service regarding
> |>the problem of not being able to print to LTA or TTA devices from
> |>Pathworks for VMS (Macintosh) created queues if the device is
> |>spooled.
> |>
> |>This is a feature.
 
> 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. The engineer who owns that code and I

I can give you names and log information via EMAIL if you like.

> Anyway, we are actively working on the problem. I can't commit to
> a fix by a certain time or in a certain release yet, but we agree
> with you that there should be a fix for this.

Thanks, that's the response I was looking for in the first place. 
I spent a lot of time on this. It was desperation when I
unspooled the device, just to see what would happen, and suddenly
it worked. :-)
 
> As to the response you got, I'm sorry.

It's ok now.  I've cooled down. :-)

Thanks for your reply, it's appreciated.

........
For others who have the same problem, another member of this
newsgroup suggested a workaround that performs well.  Create a
dummy LTA device (using LATCP), don't assign a node/port to it,
just spool it to the queue. 

mcr latcp create port <dummy lta port>
set dev/spooled=(<queue>,sys$sysdevice) <dummy lta port>

Since the device you're using is not spooled the MSAP$SYMBIONT
print symbiont still sees it and you can copy to the node::device
(where the device is the dummy LTA device) and the output goes into 
the queue.

This has other uses, like being able to print from a Vax that's
not running Pathworks for VMS (Macintosh) to an AppleTalk printer
etc.

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: mitton@dave.lkg.dec.com (Dave Mitton)
Subject: Re: Re(2): Pathworks for PC Proxy Access
Reply-To: mitton@dave.lkg.dec.com (Dave Mitton)
Organization: Digital Equipment Corporation, Littleton MA
Date: Mon, 4 Jan 1993 21:40:34 GMT


In article <921231121641.20200e99@STC10.CTD.ORNL.GOV>, PUNGMS@STC10.CTD.ORNL.GOV writes:
From: PUNGMS@STC10.CTD.ORNL.GOV
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re(2): Pathworks for PC Proxy Access
Date: 31 Dec 92 17:16:41 GMT

<     What I am looking for is the way to configure a true PROXY account so
<     that the USERNAME is sent to the remote VAX host and it verifies access
<     via the VAX/VMS Proxy File/Utility.
<
<                                                                Mike

	What you are looking for is (was?) implemented in DNP by using
a USER name defined for the local node.  eg: If you are running on a
node 4.69 whose EXECUTOR NAME is MSDOS, then do the following command:

	NCP DEFINE NODE 4.69 NAME MSDOS USER <username>

	The standard socket routine for making DECnet connects (dnet_conn)
which is used in all DECnet-DOS utilities will pick this up and stuff it
in the appropriate place for proxy information.  VMS will only use it if
all other info is not present.

	Any user written application must do this themselves (see dnet_conn
sources on how to use bind()) or use dnet_conn().

	This doesn't work with NETBIOS sessions (I don't think?... don't
remember) which will include PCSA file services.

	Dave (former DNP author)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: PW/Mac 1.1 and System 7.1
From: Graham Bisset - Aberdeen Net Support +44 224 771117<bisset@ABJ.SINET.SLB.COM>
Date: 08 Jan 1993 15:03:45 +0000 (GMT)
Content-transfer-encoding: 7BIT
X-Vms-From: PSI%ABJM31::ABJ::BISSET"Graham Bisset - Aberdeen Net Support +44 224 771117"

Hi,

I've heard that System 7.1 and Mail for Mac has a few problems with
crashing etc.  Anybody else heard or can confirm this?  What other problems
are there with 7.1 relating to Pathworks/Mac??

Sorry if this is a FAQ.

Regards

Graham Bisset
e-mail: bisset@abj.sinet.slb.com
From: hogstedt@ae.chalmers.se (Per Hogstedt)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Notification of All-in-1 Mail
Date: 10 Jan 93 23:20:35 GMT
Organization: Dept. of Applied Electronics. Chalmers Univ. of Technology.

In article <LANWORKS%93010812234766@MIAMIU.ACS.MUOHIO.EDU>, ES12453@SWTEXAS.BITNET writes:
> 
> [8<] I would like to have the
>    subscribers who have PCs to be notified when they have All-in-1 mail
>    without having to log onto the VAX to check if they have mail.  Our
>    Pathworks users do already load the RCV, and I have used WINRCV for
>    windows also.  What I need is something, either a detached process or a
>    batch job, that possibly could check the All-in-1 pending file and if a
>    subscriber is a Pathworks user use the PCSA Broadcast Utility to notify
>    them. Or, does anyone else have another idea that works?
> 

I wouldn't call this proposal elegant, but if you're desperate enough:

We run a local hack here to alert a user as he/she logs in on VMS how many
e-mail they have waiting inside All-in-1. You could modify this hack and have
it check the All-in-1 mail count every now and then and send a message
to the PC whenever the count is incremented since last check. As I said, this
is not very elegant. I'm shure something better could be done from inside
All-in-1 in it's mail processing using the forwarding mechanism from VMSmail
(the forward to PCSA%"nodename$userid" stuff).

Keep us posted,
Per 
-- 
   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
Newsgroups: vmsnet.networks.desktop.pathworks
From: houseman@Turing.ORG (Carl Houseman)
Subject: Re: LANSESS & Windows Fixes
Organization: The Turing Project, Public Access Internet Host
Date: Sat, 9 Jan 1993 18:04:54 GMT

In article <01GTA4D1YFR08WXRTW@ctrvax.Vanderbilt.Edu> Alan Cantrell <CANTRELL@VUCTRVAX.BITNET> writes:
>>  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

Start up the Control Panel, and click on Network.

>Alan Cantrell
>Vanderbilt University Computer Center
>
>cantrell@ctrvax.vanderbilt.edu
>CANTRELL@VUCTRVAX

Carl Houseman
GENICOM Engineering
(new e-mail address as of 1/11/93 is still unknown!)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: PW/Mac 1.1 and System 7.1
From: Helen Strother <STROTHHM@SNYONEVA.BITNET>
Date: 12 Jan 1993 13:20:30 -0400
X-VMS-Cc: STROTHHM
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

>>Anything referencing DECNET crashes Systems 7.1<<

I am waiting on a IIvx which comes with 7.1 installed.  Can you give more
details on the problems that you have been having?  Thanks.

                Helen Strother
                Academic Computing
                SUNY College at Oneonta
                STROTTHHM@SNYONEVA.CC.ONEONTA.EDU
From: "Tricia Norris, IS R&D, B8/2.9 x2374" <NORRISP%AM%RWEI00@mr.bas.roche.com>
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: PW (MAC and Dos) and a Tektronix PostScript Printer
Date: 11 Jan 1993 16:49:08 +0000 (GMT)

Well now you've all had some experience with Pathworks for MAC and print 
services I was wondering if anyone has any ideas about how I might solve the 
following problem:

Scenario:

Tektronix Phaser II Colour Postscript Printer connecting via an Appletalk port 
to a standalone MAC and via its serial port to a terminal server. (The Printer 
automatically senses where the data is coming from.)
VMS Pathworks for Dos
VMS Pathworks for Mac
A Standalone MAC user.

The standalone MAC user and networked MAC and DOS users require access to the 
printer.

Problem:

We found that the automatic sensing did not work unless a ^D character was 
sent at the end of the file. Also the FORMFEED sent by the DEC print Symbiont 
had to be stopped. So we created our own Symbiont and Device Control Library 
and set up a queue as shown. This worked perfectly for the DOS users and the 
Standalone MAC user.

Terminal queue PRINT_COLOUR_1, idle, on RWER01::LTA19:, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC
  /LIBRARY=PHASERII Lowercase /OWNER=[SYSTEM] /PROCESSOR=NOFORMFEED
  /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN /SCHEDULE=(NOSIZE)
  /SEPARATE=(RESET=(RESET))


Now we need to set up a print service for the same printer for use by the 
Pathworks for MAC users. I've tried using the same queue and LAT port and I've 
tried setting up another queue to a differnt LAT port pointing to the same 
Terminal Server port. I even failed having deleted all other ports and queues
that I'd previously had configured. I've tried a few other options in between. 
The result is usually "device unavailble..." type errors. Or printouts 
disappear into the ether! Or Incorrect LaserPrep file errors.

Before I pursue this matter further I was hoping that someone out there may 
have had a similar experience and hence may be able to help me.

Any bright ideas, folks?

                                Tricia Norris

Internet address: norrisp%am%rwei00@mr.bas.roche.com
X400 address: S=NORRIS, G=PATRICIA, PRMD=ROCHE, ADMD=ARCOM, C=CH
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Still problems with sethost
From: bachism <BACHISM@JHUDEV.DEV.JHU.EDU>
Date: 05 Jan 1993 07:38:17 -0500
Content-transfer-encoding: 7BIT
X-Vmsmail-To: SMTP%"LANWORKS@MIAMIU.ACS.MUOHIO.EDU"

Have you told Windows that you are running on a Pathworks Network (in Windows
Setup)?????????
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Still problems with sethost
From: Helen Strother <STROTHHM@SNYONEVA.BITNET>
Date: 04 Jan 1993 11:51:05 -0400
X-VMS-Cc: STROTHHM
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi all,
        I have been off for the last week and a half and unfortunately the
computer elves did not solve all my problems while I was away.  Anyway, my
previous post on sethost hanging my machine still is not solved.  To reiterate,
I am running DOS 5.0, Windows 3.1 and unfortunately, Pathworks 4.0 on a 486
with 4 MB of memory.  When I run sethost and DOS under windows, everything
works fine until I go to DOS and issue a USE command.  The machine actually
reboots itself at this point.  Jim Becker replied that I should run LATCP and
DEFINE SCB 4, SET NVTWIN=1 at the DOS PROMPT and include the following in my
system.ini file: DNETHeapSize=128.  I should have included in my first post
that I had done all of this already and the problem has not gone away.
        I did not use the PIF file for sethost that comes with Pathworks so
this morning I replaced the PIF file that I created with the one that came with
Pathworks. A slight improvement, the machine doesn't reboot itself but hangs
and I have to reboot it.  I've also discovered that the same thing happens when
I issue a memman command.  Dir and other standard DOS commands seem to work
fine.  What is going on?  We are planning to upgrade to 4.1 very soon, will the
problem go away with the upgrade?  Is it a memory conflict?  I should also add
that the same thing happens with the vt320 emulator.

Thanks in advance for the help.

                Helen Strother
                Academic Computing
                SUNY College at Oneonta
                STROTHHM@SNYONEVA.CC.ONEONTA.EDU
Newsgroups: vmsnet.networks.desktop.pathworks
From: houseman@Turing.ORG (Carl Houseman)
Subject: Binary attachments in Mail
Organization: The Turing Project, Public Access Internet Host
Distribution: All
Date: Thu, 7 Jan 1993 17:37:14 GMT

Does anyone know of or have a tool that will reconstruct a binary attachment
as encoded by Pathworks 4.x Mail?  I need to be able to decode the mail
messages under DOS, Unix, and VMS (hmmm, sounds like a simple C-program).
(Yes, we'd like to send binary attachments via SMTP to people who aren't using
Pathworks).

I couldn't believe it when I saw that Mail was encoding the information on
its own, rather than using VMS' SEND/FOREIGN mechanism of passing the
binary data.

My e-mail address is going away after Friday 1/8/93, but I expect to have a
new one shortly after, with only a few days missed monitoring this group.
Thanks for any help.

Carl Houseman
GENICOM Engineering
houseman@turing.org
703-949-1323
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Is there a 'Maximum # of files' limitation on a virtual disk??
From: "Gordon Cressman RTI (919) 541-6363" <GMC%SSIDW1@RTI.BITNET>
Date: 05 Jan 1993 09:49:26 -0500
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

"The root directory of each disk, like the other items in the system portion
of a disk, is a fixed size for each disk format.  This size determines how
many entries there are for files in the root directory.  Each directory entry
occupies 32 bytes, so 16 of them fit into a single sector.  The smallest
diskette format, the single-sided 160K format [virtually extinct], has four
sectors set aside for the root directory, so it has room for 64 files in the
directory.  A double-sided diskette has seven directory sectors, making room
for 112 files.  Hard disks have more: for example, the AT's 20-meg [wow] disk
has 32 sectors, making room for 512 file directory entries."

Norton, Peter. Inside the IBM PC. 2nd Ed. Prentice Hall Press. p.141

Since PATHWORKS Disk Services appear as a standard DOS disk device, they
adhere to DOS directory conventions.  Others may have more recent information.

-gmc
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: PW/Mac 1.1 and System 7.1
From: Beth Stranahan <BETH@VSCNET.BITNET>
Date: 08 Jan 1993 11:34:00 -0400 (EDT)
Content-transfer-encoding: 7BIT

>I've heard that System 7.1 and Mail for Mac has a few problems with
>crashing etc.  Anybody else heard or can confirm this?

We have been using Mail for Mac for about 10 months. We have encountered these
problems:

1. When purging many (+- 30) deleted memos, connection to mail server will be
lost. Solution: user needs to re-login to the mail server.

2. When typing text into message body, characters infrequently are entered as
if the caps lock key were down (even though the caps lock key is not
depressed). Solution: delete some portion of the text, usually the previous
word, and reenter.


> What other problems are there with 7.1 relating to Pathworks/Mac??

The biggest hit is memory. Most of our users are using IIsi's with 9MB.

We have a small user population connecting over LocalTalk via LC's (4MB). The
combination of System 7.1 inits, DosMounter (control panel used here),
processor speed, and network bandwidth create problems establishing a network
connection at boot time.

Beth Stranahan
Office of Computer Services
Vermont State Colleges
Waterbury, Vermont 05676
beth@vscnet.bitnet
From: backstrom@ranger.enet.dec.com (ranger::backstrom)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: NE2000 drivers that work with PATHWORKS
Date: 12 Jan 93 05:00:22 GMT
Organization: Digital Equipment Corporation
X-Posted-Via: NEWS-NOTES gateway (a hack!)

>                jpeterse@thiele.che.wsu.edu (James N. Petersen)
>                    NE2000 drivers that work with Pathworks
>
>I have recently obtained a Gateway 2000 laptop computer with an NE2000
>compatible ethernet interface.  When I try to connect to the file server, it
>fails.  I have had this problem before with systems that do not allow
>the ethernet address to be changed, as is required for DECnet systems
>under pathworks.  Thus, I am looking for updated drivers for the NE2000
>that do work with Pathworks.  I am using version 4.1 of Pathworks for
>DOS.

    Microsoft developed the NDIS drivers for the Novel NE1000 and
    NE2000 adapters.
    
    Version 1.20 of the drivers are the first revision known to work.
    
    They're, at least, available on the MSNETWORKS forum on CompuServe.
    Possibly also on one or the other of Microsoft's BBS's. I don't know
    of any Internet locations.
    
    ...petri (petri.backstrom@ljo.mts.dec.com)
       Personal Computing Integration Engineering
       Digital Equipment Corporation
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: <None>
From: HolcomGE <holcomge@CCMAIL.PE-NELSON.COM>
Date: 06 Jan 1993 13:56:30 -0700 (PDT)
Content-transfer-encoding: 7BIT

Please remove both of my accounts from the subscription list.

Gene Holcombe


gene.holcombe@pe-nelson.com
and
gene.holcombe@snard.pe-nelson.com
Newsgroups: vmsnet.networks.desktop.pathworks
From: Chris McNeil <cmcneil@mta.ca>
Subject: REMOTE Boot any other way ?
X-Xxmessage-Id: <A76F260678020108@rush.mta.ca>
X-Xxdate: Tue, 5 Jan 93 16: 48:22 GMT
Organization: Mount Allison University
X-Useragent: Nuntius v1.1.1d11
Date: Tue, 5 Jan 1993 15:44:43 GMT

Is it possible to remote boot pathworks 4.1 for Dos using anything
other than DEC's method. For example could I use bootp and have the boot
image on my bootp server ? Is anyone doing this ?

Chris McNeil
cmcneil@mta.ca
Newsgroups: vmsnet.networks.desktop.pathworks