Newsgroups Main » Newsgroups Directory » Computers - Non-OS » Architecture

VMEbus ( comp.arch.bus.vmebus )

From dstewart+@cs.cmu.edu Thu Sep 17 09:06:10 1992
Xref: uunet news.announce.newgroups:2727 news.groups:56632 comp.realtime:2726 comp.robotics:3102 comp.lang.c:56110 comp.sys.m68k:3359 comp.os.os9:3416 comp.os.misc:2910 comp.lang.ada:8796 comp.os.vxworks:832 comp.sys.sun.hardware:4438
Newsgroups: news.announce.newgroups,news.groups,comp.realtime,comp.robotics,comp.lang.c,comp.sys.m68k,comp.os.os9,comp.os.misc,comp.lang.ada,comp.os.vxworks,comp.sys.sun.hardware
Path: uunet!bounce-back
From: dstewart+@cs.cmu.edu (David B Stewart)
Subject: RFD: comp.sys.vmebus
Message-ID: <Bup4FB.ExL@uunet.uu.net>
Followup-To: news.groups
Sender: tale@uunet.uu.net (David C Lawrence)
Organization: The Robotics Institute, Carnegie Mellon University
Date: Thu, 17 Sep 1992 00:09:09 GMT
Approved: tale@uunet.uu.net
Lines: 36

This is a Request For Discussion (RFD) regarding creation of an unmoderated
newsgroup for discussing all aspects of computing related to the VMEbus
and VMEbus-based systems:

    comp.sys.vmebus	   Discussions on hardware and software for VMEbus.


The VMEbus is one of the more popular standards for developing
open-architecture applications based on off-the-shelf hardware.  Many hardware
components, operating systems, and applications are based on this standard, yet
there currently is no USENET group where discussions of this standard,
and related items, are appropriate.

The proposal is to create comp.sys.vmebus as a forum for discussing issues
related to developing VMEbus-based systems.  This includes discussion on the
VMEbus Specification; VMEbus-based hardware, such as CPU boards and I/O devices;
secondary buses such as VSB, VXI, and VMX; open-architecture applications based
on the VMEbus; and hardware-dependent software, such as device drivers and bus
communication protocols.  The group is also available for questions and
answers, so that developers of VMEbus-based hardware and software can get
feedback or help with any problems they may encounter.

Discussions should not be about hardware-independent software which use the
VMEbus, such as the operating system or language being used, as there are other
comp.* newsgroups dedicated to those functions.

The discussion on this proposal will take place in news.groups.

Please see the pertinent postings in news.answers and news.announce.newgroups
for the rules that will be followed in creating a newsgroup
(cf. <spaf-howto_715578991@cs.purdue.edu>).
-- 
David B. Stewart  - email: <dstewart@cmu.edu>            The Robotics Institute
snail mail:       - ECE Dept., Carnegie Mellon University, Pittsburgh, PA 15213
Current Projects: - Chimera 3.0 Real-Time Operating System
		  - Reconfigurable Sensor-Based Control Systems

From dstewart+@cs.cmu.edu Fri Sep 25 12:22:25 1992
Xref: uunet news.announce.newgroups:2771 news.groups:56956 comp.realtime:2764 comp.robotics:3164 comp.lang.c:56467 comp.sys.m68k:3384 comp.os.os9:3443 comp.os.misc:2920 comp.lang.ada:8931 comp.os.vxworks:865 comp.sys.sun.hardware:4603
Newsgroups: news.announce.newgroups,news.groups,comp.realtime,comp.robotics,comp.lang.c,comp.sys.m68k,comp.os.os9,comp.os.misc,comp.lang.ada,comp.os.vxworks,comp.sys.sun.hardware
Path: uunet!bounce-back
From: dstewart+@cs.cmu.edu (David B Stewart)
Subject: 2nd RFD: comp.sys.vmebus
Message-ID: <Bv4xux.5vL@uunet.uu.net>
Followup-To: news.groups
Sender: tale@uunet.uu.net (David C Lawrence)
Organization: The Robotics Institute, Carnegie Mellon University
Date: Fri, 25 Sep 1992 13:08:57 GMT
Approved: tale@uunet.uu.net
Lines: 66

This is the 2nd Request for Discussion (RFD) regarding creation of an
unmoderated newsgroup 'comp.sys.vmebus' for discussing all aspects of computing
related to the VMEbus and VMEbus-based systems.

So far the following summarizes what has been discussed on news.groups about
the proposed creation of comp.sys.vmebus:

1- No objections yet.  Some say this newsgroup is long overdue.

2- Naming the newsgroup 'comp.sys.vme' VS. 'comp.sys.vmebus'.
    The shorter name was recommended by one netter, saying that it is a common
    abbreviation.  However, not everyone agrees since VMEbus is the official
    name, and VME is the name of a mainframe operating system.  Based on this,
    I plan on keeping the name 'comp.sys.vmebus' when we have the Call for
    Votes (CFV).

3- One person recommends that the charter of the newgroup be expanded to
    include other buses related to VMEbus, such as Futurebus+.
    Additional discussion on this point is encouraged.  

All discussions should take place in news.groups.

The Call for Votes will occur on Oct. 17 at the earliest, according to the
USENET rules for creating a new newsgroup.  
(cf.  <spaf-howto_715578991@cs.purdue.edu>).

The original Request for Discussion follows:

-------------------------------------------------------------------------

This is a Request for Discussion (RFD) regarding creation of an unmoderated
newsgroup for discussing all aspects of computing related to the VMEbus
and VMEbus-based systems.

comp.sys.vmebus	   Discussions on hardware & software for VMEbus.


The VMEbus is one of the more popular standards for developing
open-architecture applications based on off-the-shelf hardware.  Many hardware
components, operating systems, and applications are based on this standard, yet
there currently is no USENET group where discussions of this standard,
and related items, are appropriate.

The proposal is to create comp.sys.vmebus as a forum for discussing issues
related to developing VMEbus-based systems.  This includes discussion on the
VMEbus Specification; VMEbus-based hardware, such as CPU boards and I/O devices;
secondary buses such as VSB, VXI, and VMX; open-architecture applications based
on the VMEbus; and hardware-dependent software, such as device drivers and bus
communication protocols.  The group is also available for questions and
answers, so that developers of VMEbus-based hardware and software can get
feedback or help with any problems they may encounter.

Discussions should not be about hardware-independent software which use the
VMEbus, such as the operating system or language being used, as there are other
comp.* newsgroups dedicated to those functions.

The discussion on this proposal will take place in news.groups 

Please see the pertinent postings in news.answers and news.announce.newgroups
for the rules that will be followed in creating a newsgroup
(<spaf-howto_715578991@cs.purdue.edu>).
-- 
David B. Stewart  - email: <dstewart@cmu.edu>            The Robotics Institute
snail mail:       - ECE Dept., Carnegie Mellon University, Pittsburgh, PA 15213
Current Projects: - Chimera 3.0 Real-Time Operating System
		  - Reconfigurable Sensor-Based Control Systems

From dstewart+@cs.cmu.edu Thu Oct 15 22:08:57 1992
Xref: uunet news.announce.newgroups:2834 news.groups:57848 comp.robotics:3356 comp.realtime:2848 comp.lang.c:57425 comp.unix.wizards:7675 comp.sys.m68k:3486 comp.sys.misc:4086 comp.os.os9:3499 comp.lang.ada:9125 comp.os.vxworks:930
Newsgroups: news.announce.newgroups,news.groups,comp.robotics,comp.realtime,comp.sys.sun,comp.lang.c,comp.unix.wizards,comp.sys.m68k,comp.sys.misc,comp.os.os9,comp.lang.ada,comp.os.vxworks
Path: uunet!bounce-back
From: dstewart+@cs.cmu.edu (David B Stewart)
Subject: CFV: comp.arch.bus.vmebus
Keywords: VMEbus
Followup-To: poster
Approved: tale@uunet.uu.net
Sender: tale@uunet.uu.net (David C Lawrence)
Organization: The Robotics Institute, Carnegie Mellon University
Date: Thu, 15 Oct 1992 23:52:07 GMT
Message-ID: <Bw6syw.606@uunet.uu.net>
Reply-To: chimera+@cmu.edu
Lines: 72

This is a Call for Votes for the creation of a new newsgroup for discussing
VMEbus systems and related topics. The specifics of the proposed newsgroup are
given below, followed by the voting intructions and rules.


    Name:	comp.arch.bus.vmebus

    Purpose:    Discussions of hardware and software for VMEbus Systems.

    Status:	Unmoderated

    Charter:    The newsgroup 'comp.arch.bus.vmebus' is a forum for discussing
		issues related to developing VMEbus-based systems.  This
		includes discussion of VMEbus-based hardware, such as CPU
		boards and I/O devices; the VMEbus specification; any alternate
		or secondary buses supported by the VMEbus International Trade
		Association (VITA) which includes FutureBus+, VSB, VXI, and
		VMX; open-architecture applications based on the VMEbus; and
		hardware-dependent software, such as device drivers and bus
		communication protocols.  The group is also available for
		questions and answers, so that developers of VMEbus-based
		hardware and software can get feedback or help with any
		problems they may encounter.

		Discussions should not be about hardware-independent software
		which use the VMEbus, such as the operating system or language
		being used, as there are other comp.* newsgroups dedicated to
		those functions.


Voting Instructions:

    All votes should be sent to <chimera@cmu.edu>.
    Be sure to include the word "vote" in the subject line.

    If you want the group 'comp.arch.bus.vmebus' to be created, 
    include the text:

	"I vote YES for the creation of comp.arch.bus.vmebus."

    If you feel the group 'comp.arch.bus.vmebus' should not be created, 
    include the text:

	"I vote NO for the creation of comp.arch.bus.vmebus."


Voting Rules:

    - One vote per person. If you vote more than once, only the *last* of 
	those votes will count.  Therefore if you change your mind about
	the vote, you can send a new vote, which invalidates the old vote,
	as long as it is within the voting period.

    - Ambiguous votes will be invalidated.
	Ambiguous votes contain neither YES nor NO, or contain both,
	or are conditional, such as "I vote ... if ..."

    - Votes posted to any newsgroup will NOT be counted.

    - According to the USENET rules, in order for the new group to be created,
	at least 2/3 of the votes must be "YES", and there must be at least 100
	more "YES" votes than "NO" votes.

    - For more details on the voting rules being followed, refer to article
	<spaf-howto_715578991@cs.purdue.edu> in news.announce.newgroups.

Voting period:

    Votes will be collected for a period beginning when this CFV is approved
    for publication in news.announce.newgroups and ending at midnight on
    Tuesday November 10, 1992.  Votes received after the expiration of the
    voting period will be discarded.

From dstewart+@cs.cmu.edu Wed Nov  4 10:19:50 1992
Xref: uunet news.announce.newgroups:2898 news.groups:58832 comp.robotics:3527 comp.realtime:2952 comp.sys.sun.hardware:5347 comp.lang.c:58349 comp.unix.wizards:7881 comp.sys.m68k:3556 comp.sys.misc:4233 comp.os.os9:3557 comp.lang.ada:9335 comp.os.vxworks:991
Newsgroups: news.announce.newgroups,news.groups,comp.robotics,comp.realtime,comp.sys.sun.hardware,comp.lang.c,comp.unix.wizards,comp.sys.m68k,comp.sys.misc,comp.os.os9,comp.lang.ada,comp.os.vxworks
Path: uunet!bounce-back
From: dstewart+@cs.cmu.edu (David B Stewart)
Subject: 2nd CFV: comp.arch.bus.vmebus
Keywords: VMEbus
Followup-To: poster
Approved: tale@uunet.uu.net
Sender: tale@uunet.uu.net (David C Lawrence)
Organization: The Robotics Institute, Carnegie Mellon University
Date: Wed, 4 Nov 1992 13:49:16 GMT
Message-ID: <Bx72E4.J4E@uunet.uu.net>
Reply-To: chimera+@cmu.edu
Lines: 71

This is the second (and final) Call for Votes for the creation of a new
newsgroup for discussing VMEbus systems and related topics. The specifics of
the proposed newsgroup are given below, followed by the voting intructions and
rules.


    Name:	comp.arch.bus.vmebus

    Purpose:    Discussions of hardware and software for VMEbus Systems.

    Status:	Unmoderated

    Charter:    The newsgroup 'comp.arch.bus.vmebus' is a forum for discussing
		issues related to developing VMEbus-based systems.  This
		includes discussion of VMEbus-based hardware, such as CPU
		boards and I/O devices; the VMEbus specification; any alternate
		or secondary buses supported by the VMEbus International Trade
		Association (VITA) which includes FutureBus+, VSB, VXI, and
		VMX; open-architecture applications based on the VMEbus; and
		hardware-dependent software, such as device drivers and bus
		communication protocols.  The group is also available for
		questions and answers, so that developers of VMEbus-based
		hardware and software can get feedback or help with any
		problems they may encounter.

		Discussions should not be about hardware-independent software
		which use the VMEbus, such as the operating system or language
		being used, as there are other comp.* newsgroups dedicated to
		those functions.


Voting Instructions:

    All votes should be sent to <chimera@cmu.edu>.
    Be sure to include the word "vote" in the subject line.

    If you want the group 'comp.arch.bus.vmebus' to be created, 
    include the text:

	"I vote YES for the creation of comp.arch.bus.vmebus."

    If you feel the group 'comp.arch.bus.vmebus' should not be created, 
    include the text:

	"I vote NO for the creation of comp.arch.bus.vmebus."


Voting Rules:

    - One vote per person. If you vote more than once, only the *last* of 
	those votes will count.  Therefore if you change your mind about
	the vote, you can send a new vote, which invalidates the old vote,
	as long as it is within the voting period.

    - Ambiguous votes will be invalidated.
	Ambiguous votes contain neither YES nor NO, or contain both,
	or are conditional, such as "I vote ... if ..."

    - Votes posted to any newsgroup will NOT be counted.

    - According to the USENET rules, in order for the new group to be created,
	at least 2/3 of the votes must be "YES", and there must be at least 100
	more "YES" votes than "NO" votes.

    - For more details on the voting rules being followed, refer to article
	<spaf-howto_715578991@cs.purdue.edu> in news.announce.newgroups.

Voting period:

    Votes will be collected until Tuesday November 10, 1992.  Votes received
    after the expiration of the voting period will be discarded.

From dstewart+@cs.cmu.edu Fri Nov 13 07:59:10 1992
Newsgroups: news.announce.newgroups,news.groups,comp.robotics,comp.realtime,comp.sys.sun.hardware,comp.unix.wizards,comp.sys.m68k,comp.sys.misc,comp.os.os9,comp.lang.ada,comp.os.vxworks
Path: uunet!uunet!bounce-back
From: dstewart+@cs.cmu.edu (David B Stewart)
Subject: RESULT: comp.arch.bus.vmebus passes 227:19
Keywords: VMEbus
Followup-To: news.groups
Approved: tale@uunet.uu.net
Sender: tale@uunet.uu.net (David C Lawrence)
Organization: The Robotics Institute, Carnegie Mellon University
Date: Fri, 13 Nov 1992 10:16:08 GMT
Message-ID: <BxnGIw.FIF@uunet.uu.net>
Lines: 291
Xref: uunet news.announce.newgroups:2951 news.groups:60361 comp.robotics:3634 comp.realtime:3001 comp.sys.sun.hardware:5631 comp.unix.wizards:8051 comp.sys.m68k:3609 comp.sys.misc:4269 comp.os.os9:3604 comp.lang.ada:9469 comp.os.vxworks:1029

Below is the result of votes received in the comp.arch.bus.vmebus
new group vote as of 00:01 EST  11 November 1992.

Vote Tabulation:

	258 votes received
	 12 simple duplicates reduced to one each

	 19 no
	227 yes
	-------------
	246 total

	227 yes
      -  19 no
	-------------
	208 margin  (more than 100 more yes than no!)

	227 / 246 = 0.920 = 92.0%  (more than 2/3 [67%] in favor!)

Having met the declared criteria, it appears that the vote for
comp.arch.bus.vmebus has passed.

The list of voters, grouped by how they voted, and sorted by the "From:" line
of their email, appears below.  If there are no substantial changes to the
recorded votes within the 5 days from the posting of this article, the group
creation message will be issued by David Lawrence (tale@uunet).

During the vote, 4 ambiguous ballots were received (with no indication of yes
or no in the headers or the message.) Simple email informing the voter that the
votes could not be counted were sent, and in each case a new valid vote
was sent by the voter.

Thanks to everyone who voted, and I look forward to some interesting
discussions in the future.

					David B. Stewart
					<dstewart@cmu.edu>


No votes (19)
=============================================================
AH Al_ashaab <A.H.Al_ashaab@lut.ac.uk>
Charles Shub <cdash@moet.cs.colorado.edu>
Eric J. Olson <ejo@kaja.gi.alaska.edu> [2 votes reduced to 1]
Gerry Roston <gerry@frc2.frc.ri.cmu.edu>
Jon Lin <jwlin@soda.berkeley.edu>
Sven M. Heinicke <sven@cs.widener.edu> [2 votes reduced to 1]
al198723@next00.mty.itesm.mx
austin@franklin.com (Austin G. Hastings)
barrett@cc.gatech.edu (James Barrett)
brandt@jarrett.den.mmc.com (Joe Brandt))
d9bertil@dtek.chalmers.se
devon!paul@hobbes.cert.org
eggert@twinsun.com (Paul Eggert)
emcguire@intellection.com (Ed McGuire)
ggw@wolves.durham.nc.us (Gregory G. Woodbury)
kumr!abekas.UUCP!mikep@kumr.lns.com (Mike Park)
pseudo!mjn@uunet.uu.net (Murray Nesbitt) [2 votes reduced to 1]
rick@crick.ssctr.bcm.tmc.edu (Richard H. Miller)
sp0mikpa@josefin.his.se (Mikael Parknert)

Yes Votes (227)
==============================================================
88opensi!sartin@uunet.uu.net
Anay S. Panvalkar <anay@mcnc.org>
Andre Somberg <inducom!andre@relay.nluug.nl>
Andy Jackson <arj@cam-orl.co.uk>
Bob Foery <bobf@verdix.com>
Bob Herlien <hebo@mbari.org>
Brad_Nelson@IUS5.IUS.CS.CMU.EDU
Brian Carlton <bdc@bdcsys.suvl.ca.us>
Brian Palmer <bpalmer@bbn.com>
Brian e. Batson <brianb@ims.com>
Christoph Eck <cec@dxcern.cern.ch>
D.W.Wright@bnr.co.uk
DONALD MACKELLAR <dvm@swlvx2.msd.ray.com>
David Lee <D.Lee@cs.ucl.ac.uk>
David_B_Stewart@IUS4.IUS.CS.CMU.EDU
Denis Poussart <poussart@gel.ulaval.ca>
Edgar Perez <eperez@hpprdos.prd.hp.com>
Edward McClanahan <edwardm@hpcuhe.cup.hp.com>
Einar Sjaavik <einar@ade.no>
Eoin.Hyden@cl.cam.ac.uk
Florian.Wohlgemuth@rus.uni-stuttgart.de (Florian Wohlgemuth)
Glenn Kasten <glenn@ready.eng.ready.com>
HOGLE RICHARD A <HOGLE@crdgw2.crd.ge.com>
Henning Pangels <hmp@frc2.frc.ri.cmu.edu>
James McIntosh <James_McIntosh@umcp.natinst.com>
James Olsen <jolse@dswe.navy.mil.nz>
Jan Ekkel <inducom!jan@relay.nluug.nl>
Jian Huang <jhuang@sci.ccny.cuny.edu>
Jim Cockrell @ NSI <cockerel@cave.arc.nasa.gov>
Joe Weintraub <jweintr@atlantis.cs.orst.edu>
John Heimbold <heimbold@cerf.net>
John Sauter <john@iti.org>
John M. Jourdain <jmj+@andrew.cmu.edu>
Jon Kieffer <Jon.Kieffer@faceng.anu.edu.au>
Jurriaan Vreeburg <vreeburg@fys.ruu.nl>
Kai Atle Myrvang <kai@ade.no>
Klaus Rennecke <marion@cs.tu-berlin.de>
Larry_Anglin@quickmail.natinst.com (Larry Anglin)
Mark Williams <markw@hpcss01.cup.hp.com>
Mark Wuest <violin!mdw%trumpet.att.com@violin.att.com>
Markus Traber <traber@ppc.lpc.ethz.ch>
Matthieu Herrb <matthieu@idefix.laas.fr>
Meindert Kuipers <inducom!meindert@relay.nluug.nl>
Michael M. O'Dorney <mmo2273@aw2.fsl.ca.boeing.com>
Michael Quinn <MJQUINN%PUCC.BITNET@bitnet.cc.cmu.edu>
Ninane%fynu.ucl.ac.be@bitnet.cc.cmu.edu
Oded Ravid <odedr@ie.technion.ac.il> [2 'yes votes reduced to 1]
Orion@cup.portal.com [2 'yes votes reduced to 1]
Paul Wilkinson <pwilkins@tsotsi.demon.co.uk>
Paul Qualtrough <paulq@spider.co.uk>
Pete Lyall <plyall@lookout.it.uswc.uswest.com>
Phil Kester <philk@verdix.com>
Pirawat Watanapongse <pw@cacs.usl.edu> [2 'yes' votes reduced to 1]
Reidar Strand <reidar@ade.no>
Remko van Driel <inducom!remko@relay.nluug.nl>
Rene Leiva <rene@cs.ualberta.ca>
Richard.Voyles@B.GP.CS.CMU.EDU
Robert J. Docktor <rdocktor@pica.army.mil>
Rolf Dietze <fornax@cs.tu-berlin.de>
Ron Fox <fox@foxsun.nscl.msu.edu>
SYSTEM@cycl.phys.tue.nl
Sean Quinlan <sean@cs.stanford.edu>
Sinan Karasu <sinan@atc.boeing.com>
Steve Blachman <sblachma@aoc.nrao.edu>
Steven King (503) 627-2736 <sjk@stapledon.labs.tek.com>
Stuart Quick <stu1@kaa.ee.umist.ac.uk>
Sundar Kuttalingam <wiltel!sundark@uunet.uu.net>
Timothy J Chappell <ee90tjc@brunel.ac.uk>
Venneman John <Venneman_John@mm.ssd.lmsc.lockheed.com>
Vincent Verleun <verleun@fys.ruu.nl>
Vuorimaa Petri Kalevi <pv@cs.tut.fi>
Walter E Miller @ NSI <wmiller@cave.arc.nasa.gov>
ZAL@sscvx1.ssc.gov
abg@beowulf.epm.ornl.gov (Alex L. Bangs)
adams@pdv2.fmr.maschinenbau.th-darmstadt.de (Adams)
alfredb@deathstar.wv.tek.com
apoyner@as.arizona.edu (Tony Poyner) [2 'yes votes reduced to 1]
barryn@world.std.com (barry n nelson)
bbieszk@nis.naitc.com (Bob Bieszk) [2 'yes votes reduced to 1]
bernie@metapro.dialix.oz.au
biocca@csg.lbl.gov (Alan K Biocca)
bmw@isgtec.com (Bruce M. Walker)
budelsky@ikp.uni-koeln.de (Dietmar Budelsky)
butler@ursula.natinst.com (Paul Butler)
cdl@mpl.ucsd.edu (Carl Lowenstein)
cheilek@famine.ssd.lmsc.lockheed.com (Alan Cheilek)
christ@ostar.pen.tek.com (Chris Tilt)
clh@sparky.mda.ca (Christian Lam)
comore@arcetri.astro.it (Gianni Comoretto)
comtec!tang!robert@ucsd.edu (Robert Redfield)
craigc@eagle.natinst.com (Craig Conway)
crispen <@ada3.ca.boeing.com:crispen@efftoo.boeing.com>
cummings@falcon.natinst.com (Rodney Cummings)
curry@tc.fluke.com (John Curry)
curtiss@burn.colorado.edu (Brian Curtiss)
cvd@aberystwyth.ac.uk
cwk@irrational.ssc.gov (Carl Kalbfleisch)
cyclone@netcom.com (Bill Sheppard)
dank@blacks.jpl.nasa.gov (Daniel R. Kegel)
dap@anubis.network.com (Dave Peterson)
dawn%grumpy@kssib.ksc.nasa.gov (Dawn Stewart)
dbruce@ll.mit.edu (Dave Bruce)
dbsun!harbison@wupost.wustl.edu (harbison)
dc@navstar.lanl.gov (Darrell Call)
djc@phebos.aps.anl.gov (Dan Ciarlette)
dkocinsk@ehsl.mitre.org (David Kocinski)
dnewcomb@whale.st.usm.edu (Donald R. Newcomb)
donaldlf@cs.rose-hulman.edu
dufault@alliant.com (Peter Dufault)
dwells@fits.cv.nrao.edu (Don Wells)
ediger!neufeld@gatech.edu (Keith Neufeld)
erik@pluto.newcastle.edu.au (Erik Plesner)
ernst@ik3vdg.kfk.de (Albrecht Ernst)
erolfe@ll.mit.edu (Ed Rolfe)
eurocor!mike@uunet.uu.net (Mike Geipel)
faught@berserk.ssc.gov (Ed Faught)
floyd@wmi.com (Floyd Miller)
frtjeb@efe.frk.cdc.com (Jens Ebert (69-6305-299))
fstbab@ambrosia.lerc.nasa.gov (Theresa Babrauckas)
galloway@derek.ecs.umass.edu (john galloway) [2 'yes votes reduced to 1]
ganesan@lynx.com (Ganesan)
gca!faill@uunet.uu.net (Peter Faill)
gee@dretor.dciem.dnd.ca
gerd@zaphod.physik.fu-berlin.de (Gerd Buntkowsky)
gilbert@comm.mot.com (Steve Gilbert)
gjn@phebos.aps.anl.gov (Greogry J. Nawrocki)
glens@falcon.natinst.com (Glen Sescila)
gordon@tpocc.gsfc.nasa.gov (Gordon Miller)
grima@iphase.com (Gary Rima)
groves@tcville.hac.com (Gillian Groves)
gt@prosun.first.gmd.de (Gerd Truschinski)
guycole@netcom.com (Guy Cole)
harry@neuronz.jpl.nasa.gov (Harry Langenbacher)
heiby@chg.mcd.mot.com (Ron Heiby)
heidi@falcon.natinst.com (Heidi Frock)
hill@luke.atdiv.lanl.gov (Jeff Hill)
hodapp@nvl.army.mil (John Hodapp)
hwajin@iphasew.com
jablin@eagle.natinst.com (Mike Jablin)
jaime@eagle.natinst.com (Jaime Edwards)
jcp@aplexus.jhuapl.edu (John C. Peden)
jfinn@ll.mit.edu (Joe Finnivan)
jhorstko@rosebud.cv.nrao.edu (Jim Horstkotte)
jkreznar@ininx.com (John E. Kreznar)
jmoudy@jabba.ess.harris.com (James D. Moudy)
jms@tardis.tymnet.com (Joe Smith)
jones@cs.buffalo.edu (Terry A. Jones)
jpmott%sunspot.nosc.mil@nosc.mil (Jon Mott)
jtillema@panda.lpl.arizona.edu (John Tillema)
jtwp%ukfca1@sj.ate.slb.com
kat@genisco.gtc.com (Kathryn Fielding)
kemp@dxcern.cern.ch (Douglas Kemp)
kevin@jd.b17a.ingr.com (Kevin Pammett)
kiki@ferrari.matra-espace.fr (Graulle Christophe)
koss@engin.umich.edu
lewis@csg.lbl.gov (Steve Lewis)
magnaud@irit.fr
markm@ee.ubc.ca (mark milligan)
martinez@mailbox.syr.edu (Kenneth Mtz. (YONIX))
mcrware!johnl@uunet.uu.net (John Lengeling)
mistik@grex.ann-arbor.mi.us (Mustafa Soysal)
mitchell@aaec1.aaec.com
mkumar@cs.utexas.edu (Mohan J. Kumar)
mmt@redbrick.com (Maxime Taksar KC6ZPS)
moliver@shadow.eng.pyramid.com (Mike Oliver)
mrmike@michelotti.ae.ge.com ("Mr. Mike" Passaretti)
msv@isi.com (Manish S. Vaidya)
muir@tfs.com (David Muir Sharnoff)
mwca!bill@uunet.uu.net (Bill Sheppard)
myer@mar.webo.dg.com (Jeff Myer)
nealc@tinton.ccur.com
nicolay@ikp.uni-koeln.de (Norbert Nicolay)
pardo@sun-valley.stanford.edu (G. Pardo-Castellote) [2 'yes votes reduced to 1]
paul@suite.sw.oz.au (Paul Antoine)
pdw@sunbar.mc.duke.edu (Patrick D. Wolf)
psm%helios.nosc.mil@nosc.mil (Scot McIntosh)
pyoo@rtoeu.enet.dec.com
rab@csg.lbl.gov (Robert Belshe)
raj@eagle.natinst.com (Raj Shelke)
rice%kuwait@sun.com (George Rice)
rick@sbcs.sunysb.edu (Rick Spanbauer)
riendeau@ireq-sat.hydro.qc.ca (Sylvain Riendeau 8573)
rjm@apl.washington.edu (Bob McKenzie)
robert@eagle.natinst.com (Robert Canik)
robison@rocke.electro.swri.edu (Bob Robison)
robnett@vtu1.mdc.com (Glenn Robnett)
root@ssw.de (Benno Lange)
ross@alcatel.ch (David Ross) [2 'yes votes reduced to 1]
rtw@mtuxj.att.com
ruman@meroot.eng.uci.edu (ruman)
salerno@ast.dsd.northrop.com (Peter Salerno)
santos@vxcrna.cern.ch
sawey@eagle.natinst.com (David Sawey)
seth@marge.trg.saic.com (Seth A. Phillips)
shen@eagle.natinst.com (Tian Shen)
shuford@cs.utk.edu
slater@tpocc.gsfc.nasa.gov (Don Slater)
smb@genrad.com (Steve M. Blumenau)
srb@ll.mit.edu ( Steve Broadstone)
srm@matrx.matrix.com (Steve Morris)
srogers@tad.eds.com (Steve Rogers)
stassen@id.dth.dk (Flemming Stassen)
stevez@mallet.med.ge.com (Steve Zanoni 5-4325)
str@iitb.fhg.de (Struck)
stu@valinor.mythical.com (Stu Labovitz)
tcarey@p2tacs.lanl.gov (Tom Carey)
ted@sangabriel.desktalk.com (Ted Eggers)
thomson@ursula.natinst.com (Andy Thomson)
thor@surt.atd.ucar.edu (Richard E. Neitzel)
tony@microware.co.uk (Tony Mountifield)
tshann@transquest.oe.fau.edu (Ted Shannon) [2 'yes votes reduced to 1]
tweekco!alizard@pacbell.com (A.Lizard)
vanandel@rsf.atd.ucar.edu (Joe VanAndel)
vestli@ifr.ethz.ch
volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
ward horner <whorner@macward.gsfc.nasa.gov>
wbrown@csg.lbl.gov (Bill Brown) [2 'yes votes reduced to 1]
wdf@ukfca1.sinet.slb.com
welchj@cs.rpi.edu
willey@kroy.com (Don Willey)
winans@phebos.aps.anl.gov (John R. Winans)
wongi@netcom.com (Isaac Wong)
woodbury@dogone.enet.dec.com
wpm@phebos.aps.anl.gov (Bill McDowell)
wybo@adi.com (Dave Wybo)
yoshio@ucrengr.ucr.edu (yoshio nakamura)
yvesb@minas.lockheed.on.ca (Yves Boudreault)