HDTenEightyP/NetNews huggingface dataset:
From: goathunter@wkuvx1.bitnet
Newsgroups: vmsnet.tpu
Subject: FLIST ported to Alpha
Date: 22 Nov 92 12:22:27 CDT
Organization: Western Kentucky University, Bowling Green, KY

In case you didn't see this is vmsnet.sources.d and comp.os.vms:

FLIST, my file and directory manager, runs under Alpha now.  FLIST is
written mostly in TPU, with a C driver.  For a variety of reasons, I
rewrote the MACRO program in C and have successfully run it under both
OpenVMS VAX and OpenVMS AXP (Alpha).

FLIST lets you view, delete, rename, copy, edit, purge, etc., files.
You can also tag groups of files and delete them all at once, etc.
It's (IMO) an invaluable utility when cleaning directories.  It
provides much of the functionality that C-SWING provides, but it's a
lot faster.  If you haven't tried it, go for it; I think you'll like
it.

To get the new FLIST, with .OBJs and .EXEs for both VAX *and* AXP,
send the following commands in the body of a mail message to
FILESERV@WKUVX1.BITNET:

SEND FLIST
SEND FILESERV_TOOLS

You can also get it via anonymous ftp from ftp.spc.edu; you'll need:

        [.MACRO32]UNZIP.EXE
        [.MACRO32.SAVESETS]FLIST.ZIP

FLIST is also available from SHSU (thanks, George).

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251
Newsgroups: vmsnet.tpu
From: ratel@ireq.hydro.qc.ca (Gilles Ratel 8720)
Subject: EVE with option /DISPLAY + /SECTION
Organization: Institut de recherche d'Hydro-Quebec, Varennes, Canada
Date: Wed, 18 Nov 1992 14:04:55 GMT

SUBJECT: EVE WITH OPTION /DISPLAY + /SECTION
         VAX/VMS V5.5-1
         DW-MOTIF  (Producer:DEC) (Availability: F (Layered Products))

Hello,

I have a new section file
  create by: DECTPU V3.1  1992-08-17 8:37  (i.e. look SHOW SUMMARY)

If I writes command:
  $ EDIT/TPU/SECTION=MV4$0:[RATEL]VT200_EVE

  O.K.

or command:
  $ EDIT/TPU/DISPLAY=DECWINDOWS

  O.K. (without section file)

But with:
  $ EDIT/TPU/SECTION=MV4$0:[RATEL]VT200_EVE/DISPLAY=DECWINDOWS
or
  $ DEFINE TPU$SECTION=MV4$0:[RATEL]VT200_EVE
  $ EDIT/TPU/DISPLAY=DECWINDOWS

  I have warning:
----
X Toolkit Warning: I18NOpenFile: Couldn't open file EVE$WIDGETS - MrmNOT_FOUND
Could not open the specified UID file(s)
----
     ?????
     and section file is not effective !



Do you have idea!

Thanks

Gilles Ratel
Institut de recherche d'Hydro-Quebec
Varennes, CANADA

EMAIL: ratel@ireq-ccfm.hydro.qc.ca  <= please send by Email

Newsgroups: vmsnet.tpu
From: bg@dymaxion.ns.ca
Newsgroups: vmsnet.tpu
Subject: EVE global settings (was: Annoying informational EVE messages)
Date: 18 Nov 92 15:46:03 AST
Organization: Dymaxion Research Limited, NS, Canada

As it appears that many people didn't quite understand my original
post, here is some clarification:

In article <1992Nov16.221022.67@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
> Would someone please post a patch to the EVE routines which will
> prevent informational messages from being displayed in the messages
> window for settings saved via the "SAVE EXTENDED EVE" command.  They
> really bug me.

I'm talking about the following messages:


Default select behavior is now active.
Box operations will now overstrike your buffer.
The cursor is now bound to the flow of your text.
Default command file is undefined.
Default section file is undefined.
Editor will not check for modified attributes on exit.
Pending delete disabled.
Prompting for section file enabled.
Tab mode set to insert a TAB character.
Tabs will no longer be visible.

All of these messages flash by rapidly (or not so rapidly at 2400
baud) at the beginning of an editing session which uses my saved
section file.  The messages are annoying and furthermore obilterate
any useful messages which may have been displayed at the start of
the session, like:

Editing new file.  Could not find: BG.TMP

The procedure which creates my new section file looks like this:

	SET KEYPAD EDT
	SET CURSOR BOUND
	SET NOEXIT ATTRIBUTE CHECK
	INCLUDE DYULIB:DSPELL.TPU
	INCLUDE DYULIB:GETFRO.TPU
	INCLUDE DYULIB:FILBAR.TPU
	INCLUDE DYULIB:OUTSEL.TPU
	INCLUDE DYULIB:MARGIN.TPU

	TPU COMPILE(current_buffer)
	TPU DEFINE_KEY("dy_getfile_ronly",CTRL_G_KEY)
	TPU DEFINE_KEY("dy_getfile_ronly",KEY_NAME("G",SHIFT_KEY))
	TPU DEFINE_KEY("eve_spell",KEY_NAME("S",SHIFT_KEY))
	TPU DEFINE_KEY("vertical_bar",FS_KEY)
	TPU DEFINE_KEY("output_select",KEY_NAME("O",SHIFT_KEY))
	TPU DEFINE_KEY("tilde_bar",RS_KEY)
	TPU DEFINE_KEY("right_70",KEY_NAME("7",SHIFT_KEY))
	TPU DEFINE_KEY("right_80",KEY_NAME("8",SHIFT_KEY))

	SAVE EXTENDED EVE DYM$DISK:[DYMAX.205000]TPUEDT.NEW

I never had a problem with the extra messages appearing until
I added the lines:

	SET CURSOR BOUND
	SET NOEXIT ATTRIBUTE CHECK

Ben.
---
Ben Armstrong, Software Development                  bus: (902)422-1973
Dymaxion Research Ltd.,                              fax: (902)421-1267
Halifax, Nova Scotia, Canada B3J 1R2            Internet: bg@dymaxion.ns.ca
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: vmsnet.tpu
Subject: Re: How to EDIT files via a COMMAND FIle
Date: 21 Nov 1992 00:14:34 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <01GRDAR6Q8RM001XBD@utrcgw.utc.com>, "frank (Chip) Dyer x9568 ..Electrical Design" writes:
> EVE/TPU experts:
>
> I have about 50 files with the number "100C000" (hexadecimal) in them.  I
> need to edit all these files and replace "100C000" with "1010000."  Is it
> possible to do this through a non-interactive (automatic) process?
>
> Ideally I want to have a COMMAND procedure do a GLOBLAL REPLACE on
> "100C000" - something like
>
>    $ EDIT/TPU/NOINIT/NODISplay/COMmand=SYS$INPUT in.src/OUTput=OUT.SRC
>    EVE_REPLACE("100A","*!!*!!**")
>    $ EXIT
>
> Is this possible?  I have never written or used any TPU procedures, so
> any help you can provide will greatly be appreciated.  I use EVE quite a
> bit, but as far as writing or using TPU procedures, I have never done
> that.

$	EDIT/TPU/NODISPLAY/NOSECTION/COMMAND=SYS$INPUT: in.src/OUTPUT=out.src
POSITION(CREATE_BUFFER('',GET_INFO(COMMAND_LINE,'FILE_NAME')));
LOOP	R := SEARCH("100C000", FORWARD);
	EXITIF R=0;
	POSITION(R);
	ERASE(R);
	COPY_TEXT("1010000");
ENDLOOP;
WRITE_FILE(CURRENT_BUFFER, GET_INFO(COMMAND_LINE,'OUTPUT_FILE'));
EXIT;
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
From: bg@dymaxion.ns.ca
Newsgroups: vmsnet.tpu
Subject: Annoying informational EVE messages
Date: 17 Nov 92 02:10:22 GMT
Organization: Dymaxion Research Limited, NS, Canada

Would someone please post a patch to the EVE routines which will
prevent informational messages from being displayed in the messages
window for settings saved via the "SAVE EXTENDED EVE" command.  They
really bug me.

Ben.

P.S. Or maybe it's some hidden parameter I have to tweak.  I'm just
     tired of all of this useless stuff flashing by every time I
     start an editor session.
---
Ben Armstrong, Software Development                  bus: (902)422-1973
Dymaxion Research Ltd.,                              fax: (902)421-1267
Halifax, Nova Scotia, Canada B3J 1R2            Internet: bg@dymaxion.ns.ca
From: ratel@ireq.hydro.qc.ca (Gilles Ratel 8720)
Subject: RE: EVE with option /DISPLAY + /SECTION
Organization: Institut de recherche d'Hydro-Quebec, Varennes, Canada
Date: Wed, 18 Nov 1992 20:01:22 GMT

Hello,

  Finally, I have deleted my section file and create a new
  section file with:

    $ EDIT/TPU/DISPLAY=DECWINDOWS/INITIALIZATION=my_init_file

    and save with
    command: SAVE VT200_DW_EVE

  AND SUCCESS! (??)  

Gilles Ratel
Institut de recherche d'Hydro-Quebec
Varennes, CANADA

Email: ratel@ireq-ccfm.hydro.qc.ca
Newsgroups: vmsnet.tpu
Subject: re: help files under ultrix (.hlbu)
From: dectpu/eve Engineering - the last of a dying race 18-Nov-1992 0646
Date: Wed, 18 Nov 92 03:54:46 PST
Reply-To: DECTPU/EVE Engineering - the last of a dying race 18-Nov-1992
Organization: The Internet
Return-Path: <TPU-Mgr@SHSU.edu>
Errors-To: TPU-Mgr@SHSU.edu
X-Listname: Text Processing Utility (TPU) Language Discussion List
Apparently-To: info-tpu@shsu.edu

>John Gee                        erin@otago.ac.nz (Internet)

writes:

>I have converted a layered version of EVE to run under Ultrix
>with very few problems, but would also like to install the help
>for my editor. How does one create the .hlbu files used for help
>under Ultrix? (They look internally as though they have been
>created from normal VMS .hlp files, with readable text indexing
>added at the end of the file.)
>
>I haven't found any clues in the EVE sample code, and "man -k"
>didn't show up anything, although it is always a question of
>knowing what to ask for :-)
>--

Sorry John, User created help files are not supported because the utility we
use to create them is not available outside of Digital.  The program executes
on a RISC/ULTRIX and takes as input the .hlb.  It is part of the package for
help library support on RISC/ULTRIX.

I think the LSE product on RISC/ULTRIX did something different and they do
support user-created help libraries.

--------------------------------------------------------------------------------
Brian J. McCarthy - DECTPU/EVE Engineering Project Leader

Digital Equimpment Corp.
Nashua, NH
--------------------------------------------------------------------------------
Newsgroups: vmsnet.tpu
Subject: Re: Annoying informational EVE messages
From: trounson@wronz.org.nz
Date: 19 Nov 92 09:32:25 +1300

In article <1992Nov16.221022.67@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
> Would someone please post a patch to the EVE routines which will
> prevent informational messages from being displayed in the messages
> window for settings saved via the "SAVE EXTENDED EVE" command.  They
> really bug me.
> 
> Ben.
> 
> P.S. Or maybe it's some hidden parameter I have to tweak.  I'm just
>      tired of all of this useless stuff flashing by every time I
>      start an editor session.
> ---
> Ben Armstrong, Software Development                  bus: (902)422-1973
> Dymaxion Research Ltd.,                              fax: (902)421-1267
> Halifax, Nova Scotia, Canada B3J 1R2            Internet: bg@dymaxion.ns.ca


I agree they are irritating. I suggest you use the eve$build tpu procedure found
in sys$examples and described in the TPU programming manuals - it requires a
little more work initially, but makes for a clean startup of eve.

Mary Trounson                    Internet:  TROUNSON@WRONZ.ORG.NZ
Computer Systems Officer         PSI:  (05301)30000047::TROUNSON
Wool Research Organisation
Christchurch                    Telephone:  (+64) (+3) 325 2421
New Zealand                           Fax:  (+64) (+3) 325 2717
Newsgroups: vmsnet.tpu
Subject: RE: Annoying informational EVE messages
From: "(Michael
Date: Tue, 17 Nov 1992 17:21:33 -0600 (CST)
Reply-To: "(Michael Lemke, Astronomy UT Austin, Phone: +1-(512)-471-1483)"
Organization: The Internet
Return-Path: <TPU-Mgr@SHSU.edu>
Errors-To: TPU-Mgr@SHSU.edu
X-Listname: Text Processing Utility (TPU) Language Discussion List
X-Vmsmail-To: SMTP%"bg@dymaxion.ns.ca"

In a message of 17 Nov 92 02:10:22 GMT, received on 17 Nov 1992, 15:15 GMT
bg@dymaxion.ns.ca wrote
to: Text Processing Utility (TPU) Language Discussion List <INFO-TPU@SHSU.edu>

>Would someone please post a patch to the EVE routines which will
>prevent informational messages from being displayed in the messages
>window for settings saved via the "SAVE EXTENDED EVE" command.  They
>really bug me.
>

Although I am definitely not an expert on this but I think if you put
the following line in some init procedure the questions will go away:

 eve$$x_attr_exit_check  := false;

I have it in my ...module_init procedure for the eve$build stuff and it
never asks me for saving attributes.

--
Michael Lemke
Astronomy, UT Austin, Texas
(michael@io.as.utexas.edu or UTSPAN::UTADNX::IO::MICHAEL [SPAN])
Newsgroups: vmsnet.tpu
Subject: How to EDIT files via a COMMAND FIle
From: "frank (Chip) Dyer x9568 ..Electrical Design"
Date: 20 Nov 1992 09:13:20 -0400 (EDT)
Reply-To: "Frank (Chip) Dyer x9568 ..Electrical Design"
Organization: The Internet
Return-Path: <TPU-Mgr@SHSU.edu>
Errors-To: TPU-Mgr@SHSU.edu
X-Listname: Text Processing Utility (TPU) Language Discussion List
X-Envelope-To: info-tpu@shsu.EDU
X-Vms-To: INFO-TPU
X-Vms-Cc: DYERFDF
Mime-Version: 1.0
Content-Transfer-Encoding: 7BIT

 EVE/TPU experts:

 I have about 50 files with the number "100C000" (hexadecimal) in them.  I
 need to edit all these files and replace "100C000" with "1010000."  Is it
 possible to do this through a non-interactive (automatic) process?

 Ideally I want to have a COMMAND procedure do a GLOBLAL REPLACE on
 "100C000" - something like

    $ EDIT/TPU/NOINIT/NODISplay/COMmand=SYS$INPUT in.src/OUTput=OUT.SRC
    EVE_REPLACE("100A","*!!*!!**")
    $ EXIT

 Is this possible?  I have never written or used any TPU procedures, so
 any help you can provide will greatly be appreciated.  I use EVE quite a
 bit, but as far as writing or using TPU procedures, I have never done
 that.


 Thanx,  Frank

  *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
  * Frank Dyer                        INTERNET:  DYERFDF@HSDWL.UTC.COM  *
  * Hamilton Standard (UTC Division)  (203) 683-9568  FAX: 683-9500     *
  * Senior Design Engineer                                              *
  * Windsor Locks, CT  USA             Nuthin' Witty to write here Yet! *
  *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
From: erin@otago.ac.nz
Newsgroups: vmsnet.tpu
Subject: help files under ultrix (.hlbu)
Date: 17 Nov 92 22:02:52 +1300
Organization: University of Otago, Dunedin, New Zealand

I have converted a layered version of EVE to run under Ultrix
with very few problems, but would also like to install the help
for my editor. How does one create the .hlbu files used for help
under Ultrix? (They look internally as though they have been
created from normal VMS .hlp files, with readable text indexing
added at the end of the file.)

I haven't found any clues in the EVE sample code, and "man -k"
didn't show up anything, although it is always a question of
knowing what to ask for :-)
-- 
John Gee                        erin@otago.ac.nz (Internet)
Dunedin, New Zealand            "Program until you drop!"
Newsgroups: vmsnet.admin
From: rbn@sunvis.rtpnc.epa.gov (Bob Boyd)
Subject: Re: CFD: VMSNET Alpha newsgroup
Organization: UNISYS/Environmental Protection Agency
Date: Fri, 20 Nov 1992 17:26:28 GMT

dsroberts@beckman.com writes:
> In article <1992Nov18.164347.1@ptavv.llnl.gov>, oberman@ptavv.llnl.gov writes:
> > Is it about time for a VMSNET group for Alpha AXPs? The little devils are sure
> 
> vmsnet.alphaAXP.whatever
> 
> would be my vote (what the hey, AXP is part of the name, after all).  I think
> the Alpha AXP issues are distinct enough to justify starting with the third
> level even if we only have a .misc to start. 
> 
> vmsnet.alphaAXP.misc
> vmsnet.alphaAXP.sysmgt
> vmsnet.alphaAXP.OSF1
> vmsnet.alphaAXP.OpenVMS (this ought to get a reaction from Jamie!)
> vmsnet.alphaAXP.windowsNT

I'm wondering about the alternative structure of 

vmsnet.sysmgt.* (* from set of VAX, AlphaAXP, DECSYSTEM, etc...)
vmsnet.os.* (e.g. * from the set of OSF1, OpenVMS, WindowsNT)

From a conceptual standpoint I see these groupings as a little more
natural than having a group for every member of the cross between
architecture and area of interest.

Comments?
--
----

Bob Boyd
In The Here & Now
Newsgroups: vmsnet.admin
Subject: Re: CFD: VMSNET Alpha newsgroup
From: tp@mccall.com (Terry Poot)
Date: Mon, 23 Nov 1992 09:14:31 CST
Reply-To: tp@mccall.com (Terry Poot)
Distribution: world
Organization: The McCall Pattern Co., Manhattan, KS, USA
Nntp-Posting-User: tp


In article <20NOV199219380835@eql.caltech.edu>, rankin@eql.caltech.edu (Pat
Rankin) writes:
>     The login banner on an Alpha running VMS says "OpenVMS AXP (tm)"
>(where VAX/VMS still says "VAX/VMS", without the extra marketeers' nonsense)

I'll bet that changes. :-)

>and there's no mention of "Alpha" to be seen.  Personally I prefer "Alpha/VMS"
>>and "VAX/VMS" and hope to relegate "OpenVMS" to the circular file where
>it belongs.
>
>     An Alpha porting group would be useful, but VMS is still VMS and
>there's no need for separate groups for regular software.  I can't imagine
>why someone would propose an OSF/1 or WindowsNT group in the vmsnet
>hierarchy though.  Haven't we been through this several times before?

I agree we need something, but I'm not sure exactly how to position it. Due to
the transitional nature if things, perhaps we need just a single group to
discuss any and all topics specific to the Alpha. This could cover everything
from porting issues to chip architecture to the software rollout schedule. 

However, I disagree with the idea that the group(s) will grow. In fact, after an
initial spurt of activity, I suspect it/they will shrink. Note that there are no
groups about the VAX architecture, nor any about porting from RSX to VMS.
Several years after the fact, there will no longer be a need for any alpha
specific groups. If anything, we'll need to create VAX groups for the small
group of people that still want to talk about them. The Alpha will take over all
the groups related to VMS as it becomes the de facto platform for VMS.

I'm not sure more than one group will be justified by the traffic, and in a year
or 3, even this one will die out as the Alpha takes over. Such a catchall group
should probably be called vmsnet.alpha. I suppose v.alpha-axp would be a
possibility. I don't think enough people have heard of the AXP designation to
call it vmsnet.axp. (Hmm... sounds like Kevin's original proposal, doesn't it?)
:-)

Ideas? Opinions on the name(s)?
--
Terry Poot <tp@mccall.com>                   The McCall Pattern Company
(uucp: ...!rutgers!depot!mccall!tp)          615 McCall Road
(800)255-2762, in KS (913)776-4041           Manhattan, KS 66502, USA
Newsgroups: vmsnet.admin
Subject: Re: CFD: VMSNET Alpha newsgroup
From: dsroberts@beckman.com
Date: 20 Nov 92 07:50:31 PDT
Organization: Beckman Instruments

In article <1992Nov18.164347.1@ptavv.llnl.gov>, oberman@ptavv.llnl.gov writes:
> Is it about time for a VMSNET group for Alpha AXPs? The little devils are sure
> cute, but they have some interesting characteristics that lend themselves to
> broad discussion. It should help software porting problems with some advanced
> discussion.

I agree.  I think this would be a useful group.  I just wonder how much overlap
with vmsnet.internals there would be.
> 
> I propose a VMSNET Alpha group which would parallel the existing PDP-11 group.
> I don't read the PDP-11 group, so I don't happen to know just where it is in
> the heirarchy.
> 
Makes sense to me.

vmsnet.alphaAXP.whatever

would be my vote (what the hey, AXP is part of the name, after all).  I think
the Alpha AXP issues are distinct enough to justify starting with the third
level even if we only have a .misc to start. 

vmsnet.alphaAXP.misc
vmsnet.alphaAXP.sysmgt
vmsnet.alphaAXP.OSF1
vmsnet.alphaAXP.OpenVMS (this ought to get a reaction from Jamie!)
vmsnet.alphaAXP.windowsNT
etc.
-- 
   Don Roberts                   Internet:  dsroberts@beckman.com
   Beckman Instruments, Inc.     Phone:     714/961-3029
   2500 Harbor Bl. Mailstop X-12 FAX:       714/961-3351
   Fullerton, CA  92634          Disclaimer:  Blame me, not Beckman.
   This was probably the most disastrous election result for the American
   people since James Buchanon became president.  Heaven help us.
From: nreadwin@micrognosis.co.uk (Neil Readwin)
Newsgroups: vmsnet.admin
Subject: Re: CFD: VMSNET Alpha newsgroup
Date: 21 Nov 92 13:50:23 GMT
Organization: Micrognosis, a division of CSK(UK) Ltd

In article <1992Nov20.075031.1048@beckman.com>, dsroberts@beckman.com writes:
|> vmsnet.alphaAXP.whatever

Gak! Since it will really have to be entirely lower case I think that alpha
would be better then alphaaxp or alpha-axp.

I am not sure that we really need multiple groups under a new 2nd level
hierachy for this. All the OpenVMS stuff should go into the corresponding
VMS groups (after all, they are the same thing :-) I can see a medium term
need for a group to discuss porting issues, but stuff like system
management should stay in the existing groups and OSF/1 questions should be
in the Usenet comp.unix.osf.osf1 group. If WNT ever gets released then no
doubt a home will be found for it under the comp.os.ms-windows hierachy.

Neil.
-- 
 Phone: +44 71 815 5283  E-mail: nreadwin@micrognosis.co.uk
 Anything is a cause for sorrow that my mind or body has made
From: oberman@ptavv.llnl.gov
Newsgroups: vmsnet.admin
Subject: CFD: VMSNET Alpha newsgroup
Date: 19 Nov 92 00:43:47 GMT

Is it about time for a VMSNET group for Alpha AXPs? The little devils are sure
cute, but they have some interesting characteristics that lend themselves to
broad discussion. It should help software porting problems with some advanced
discussion.

I can already say that pages of 8KB make for fun when mapping sections and
MACRO is a pain to port!

I propose a VMSNET Alpha group which would parallel the existing PDP-11 group.
I don't read the PDP-11 group, so I don't happen to know just where it is in
the heirarchy.

R. Kevin Oberman			Lawrence Livermore National Laboratory
Internet: koberman@llnl.gov		(510) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.
Newsgroups: vmsnet.admin
Subject: Re: CFD: VMSNET Alpha newsgroup
From: alistair@myrddn.mits.com.au
Date: 20 Nov 92 11:40:12 +1000
Nntp-Posting-User: alistair

In article <1992Nov18.164347.1@ptavv.llnl.gov>, 
oberman@ptavv.llnl.gov writes:
>Is it about time for a VMSNET group for Alpha AXPs? The little devils are sure
>cute, but they have some interesting characteristics that lend themselves to
>broad discussion. It should help software porting problems with some advanced
>discussion.

I would like to see this group formed. Given that it may want to grow
in the future, I feel that the group should be near the top of the
vmsnet hierarchy, e.g. something like:

	vmsnet.alpha	(perhaps initially)

with more groups added later. As a few examples:

	vmsnet.alpha.porting
	vmsnet.alpha.porting.macro32
	vmsnet.alpha.programming

and perhaps some hardware related groups.

>I propose a VMSNET Alpha group which would parallel the existing PDP-11 group.
>I don't read the PDP-11 group, so I don't happen to know just where it is in
>the heirarchy.

vmsnet.pdp-11


Thanks,

Alistair Grant

Internet:     alistair@mits.com.au
Alternate:    alistair%mits.com.au@ucsvc.ucs.unimelb.edu.au