Newsgroups Main » Newsgroups Directory » Computers - OS and Platforms » IBM OS2
General ( comp.os.os2 )
From mlevis@ringer.cs.utsa.edu Fri Feb 4 16:09:07 1994
Path: uunet!bounce-back
From: mlevis@ringer.cs.utsa.edu (Mike Levis)
Newsgroups: news.announce.newgroups,news.groups,comp.os.os2.announce,comp.sys.ibm.pc.games.announce
Subject: RFD: comp.os.os2.* new groups
Followup-To: news.groups
Date: 1 Feb 1994 15:36:36 -0500
Organization: University of Texas at San Antonio
Lines: 134
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net, jsciv@polaris.async.vt.edu,
tholen@newton.ifa.hawaii.edu
Message-ID: <comp.os.os2-newgr-RFD1@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4535 news.groups:93781 comp.os.os2.announce:396 comp.sys.ibm.pc.games.announce:335
Request For Discussion
This is the formal Request For Discussion for the creation of four
newsgroups, the renaming of one newsgroup, and the removal of one
newsgroup. Please do not vote now. As soon at this RFD is posted,
I will post an RFD pointer to:
comp.os.os2.apps
comp.os.os2.programmer.misc
comp.os.os2.networking
comp.os.os2.ver1x
Summary of proposals (all unmoderated):
a) Create comp.os.os2.games
b) Create comp.os.os2.programmer.tools
c) Create comp.os.os2.programmer.oop
d) Create comp.os.os2.networking.tcp-ip
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
f) Remove comp.os.os2.ver1x
Background:
The popularity of 32-bit OS/2 2.1 is growing, thanks to a combination
of lower hardware prices, low-cost availability of OS/2 2.1, and an
attractive feature set of OS/2 2.1. One of the great strengths of OS/2
2.1 is to run DOS and Windows programs, such as games.
Games are among the most picky programs to configure, many requiring
DOS users to have different CONFIG.SYS and AUTOEXEC.BAT files to play.
OS/2 2.1 makes it easier because it allows many DOS games to run without
having to reboot the computer. Under OS/2 2.1, each DOS or Windows game
(or non- game program, for that matter) can have its very own environment,
such as its own AUTOEXEC.BAT file, its own CONFIG.SYS lines, memory setup,
and so forth. OS/2 2.1 also makes an excellent platform for its own games
as well. With features such as multi- threading and multi-media, there
are freeware, shareware, and commercial OS/2 games that are already here
or are being developed. But OS/2 is not just for playing around.
There is a slew of OS/2 2.1 programming tools -- each having advantages
and disadvantages over another. Since OS/2 2.1 can be likened to a bridge
between UNIX, OS/2 1.3, DOS, and Windows, there have been many OS/2 2.1
compilers and assemblers ported or derived from these platforms (e.g.
emx/gcc, gcc/2, Borland C++/2, et.al). There are also visual programming
tools such as VisPro/Rexx and VX-Rexx that offer the programmer more
choice in development environments.
Programmers can write programs that interface with OS/2 2.1's object-
oriented subsystem called System Object Model (SOM). SOM is a language-
independent specification for object-oriented programming. Programmers
can enhance system-provided objects by overriding the desired methods, for
instance, or change the behaviour of the Workplace Shell (WPS) -- OS/2
2.1's object- oriented shell based on SOM -- such as changing the
behaviour of a "folder" (an object) by modifying a method or two without
having to rewrite a "folder" from scratch. IBM is working on enhancing
SOM's object-oriented specification by means of Distributed SOM (DSOM)
to allow such actions across a network, OpenDoc, and Taligent Frameworks
as part of IBM's cross-platform strategy with its future Workplace OS and
Pink operating systems.
OS/2 can be connected to other platforms, or to other OS/2 machines,
through networking. TCP/IP is a popular networking package for OS/2
machines. This will be more so since a free TCP/IP package is being
worked on right now.
OS/2 1.3 has long been popular in networking environments, although there
is less need for regular people to run OS/2 1.3 due to the popularity of
OS/2 2.1 (lower hardware prices, low-cost availability, and attractive
feature set).
Proposed charters or reasons:
a) Create comp.os.os2.games
Charter: Unmoderated discussion of OS/2-specific games (e.g.
pricing, availability, features, reviews, previews, surveys,
etc.), and discussion of running DOS and Windows games under
OS/2 (e.g. compatibility, settings, etc.).
Note that discussion of DOS and Windows games not related
to OS/2 belongs in the proper games newsgroup.
b) Create comp.os.os2.programmer.tools
Charter: Unmoderated discussion of programming tools (compilers,
interpreters, assemblers) that generates or executes OS/2
code, and discussion of running DOS and Windows programming
tools under OS/2.
Note that discussion of DOS and Windows programming tools
not related to OS/2 (e.g. how much does `<xyz> for DOS'
cost) belongs in the proper programming newsgroup.
c) Create comp.os.os2.programmer.oop
Charter: Unmoderated discussion of programming for OS/2's object-
oriented subsystem, including SOM, DSOM, OpenDoc, and
Taligent Frameworks.
Note that discussion of object-oriented languages (e.g.
C++, Smalltalk) belongs in the proper language newsgroup.
d) Create comp.os.os2.networking.tcp-ip
Charter: Unmoderated discussion of TCP/IP (e.g. hardware, drivers,
setup, problems, bugs, etc.) under all versions of OS/2.
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
Reason: The standard practice of Usenet is usually to rename a
split newsgroup as .misc.
Charter: comp.os.os2.networking.misc will continue to be the
newsgroup to discuss miscellaneous OS/2-related networking
issues in an unmoderated setting.
f) Remove comp.os.os2.ver1x
Reason: OS/2 1.3 is now used mostly by companies (such as in
networking environments or ATMs) managed by long-time
experts rather than by regular people (i.e. Usenet
readers).
Schedule:
These proposals have been informally discussed in several comp.os.os2.*
newsgroups throughout January. Some other proposals that were discussed
informally did not make it in this RFD, but may be included in a future
RFD. Minor changes were made to the names of some of these proposals
to match existing newsgroup names (i.e. comp.os.os2.programmer.oop rather
than *.oo -- cf. comp.sys.mac.oop; comp.os.os2.networking.tcp-ip rather
than *.tcpip -- cf. comp.protocols.tcp-ip).
The posting of this RFD begins the formal discussion period, and will
last for 21 days. Discussion is to take place in news.groups. Please
do not vote now.
If there are no unresolvable objections, a formal Call For Votes (CFV)
will be posted when the formal discussion period is over.
--
Mike Levis
mlevis@ringer.cs.utsa.edu
From jmaynard@oac.hsc.uth.tmc.edu Thu Feb 24 17:55:07 1994
Path: uunet!bounce-back
From: jmaynard@oac.hsc.uth.tmc.edu (Jay Maynard)
Newsgroups: news.announce.newgroups,news.groups,comp.os.os2.announce,comp.sys.ibm.pc.games.announce
Subject: CFV: comp.os.os2 reorganization
Followup-To: poster
Date: 24 Feb 1994 16:00:50 -0500
Organization: Usenet Volunteer Votetakers...the knights who say ACK!
Lines: 190
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Expires: 18 Mar 1994 00:00:00 GMT
Message-ID: <comp.os.os2-reorg-CFV1@uunet.uu.net>
References: <comp.os.os2-newgr-RFD1@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4679 news.groups:96500 comp.os.os2.announce:430 comp.sys.ibm.pc.games.announce:376
FIRST CALL FOR VOTES (of 2)
Reorganization of comp.os.os2
Summary of proposals (all unmoderated):
a) Create comp.os.os2.games
b) Create comp.os.os2.programmer.tools
c) Create comp.os.os2.programmer.oop
d) Create comp.os.os2.networking.tcp-ip
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
f) Remove comp.os.os2.ver1x
Newsgroups lines:
comp.os.os2.games Running games under OS/2
comp.os.os2.programmer.tools Compilers, assemblers, interpreters under OS/2
comp.os.os2.programmer.oop Programming system objects (SOM, WPS, etc)
comp.os.os2.networking.tcp-ip TCP/IP under OS/2
comp.os.os2.networking.misc Miscellaneous networking issues of OS/2
Votes must be recieved by 23:59:59 GMT, 17 March 1994.
This vote is being conducted by a neutral third party. For voting questions
only, contact Jay Maynard (jmaynard@oac.hsc.uth.tmc.edu). For questions about
the proposed groups, contact the proposer, Mike Levis, at
mlevis@ringer.cs.utsa.edu.
A pointer to this Call for Votes is being posted to the following groups:
comp.os.os2.apps, comp.os.os2.programmer.misc, comp.os.os2.networking, and
comp.os.os2.ver1x.
CHARTER
a) Create comp.os.os2.games
Charter: Unmoderated discussion of OS/2-specific games (e.g.
pricing, availability, features, reviews, previews, surveys,
etc.), and discussion of running DOS and Windows games under
OS/2 (e.g. compatibility, settings, etc.).
Note that discussion of DOS and Windows games not related
to OS/2 belongs in the proper games newsgroup.
b) Create comp.os.os2.programmer.tools
Charter: Unmoderated discussion of programming tools (compilers,
interpreters, assemblers) that generates or executes OS/2
code, and discussion of running DOS and Windows programming
tools under OS/2.
Note that discussion of DOS and Windows programming tools
not related to OS/2 (e.g. how much does `<xyz> for DOS'
cost) belongs in the proper programming newsgroup.
c) Create comp.os.os2.programmer.oop
Charter: Unmoderated discussion of programming for OS/2's object-
oriented subsystem, including SOM, DSOM, OpenDoc, and
Taligent Frameworks.
Note that discussion of object-oriented languages (e.g.
C++, Smalltalk) belongs in the proper language newsgroup.
d) Create comp.os.os2.networking.tcp-ip
Charter: Unmoderated discussion of TCP/IP (e.g. hardware, drivers,
setup, problems, bugs, etc.) under all versions of OS/2.
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
Reason: The standard practice of Usenet is usually to rename a
split newsgroup as .misc.
Charter: comp.os.os2.networking.misc will continue to be the
newsgroup to discuss miscellaneous OS/2-related networking
issues in an unmoderated setting.
f) Remove comp.os.os2.ver1x
Reason: OS/2 1.3 is now used mostly by companies (such as in
networking environments or ATMs) managed by long-time
experts rather than by regular people (i.e. Usenet
readers).
RATIONALE
The popularity of 32-bit OS/2 2.1 is growing, thanks to a combination
of lower hardware prices, low-cost availability of OS/2 2.1, and an
attractive feature set of OS/2 2.1. One of the great strengths of OS/2
2.1 is to run DOS and Windows programs, such as games.
Games are among the most picky programs to configure, many requiring
DOS users to have different CONFIG.SYS and AUTOEXEC.BAT files to play.
OS/2 2.1 makes it easier because it allows many DOS games to run without
having to reboot the computer. Under OS/2 2.1, each DOS or Windows game
(or non- game program, for that matter) can have its very own environment,
such as its own AUTOEXEC.BAT file, its own CONFIG.SYS lines, memory setup,
and so forth. OS/2 2.1 also makes an excellent platform for its own games
as well. With features such as multi- threading and multi-media, there
are freeware, shareware, and commercial OS/2 games that are already here
or are being developed. But OS/2 is not just for playing around.
There is a slew of OS/2 2.1 programming tools -- each having advantages
and disadvantages over another. Since OS/2 2.1 can be likened to a bridge
between UNIX, OS/2 1.3, DOS, and Windows, there have been many OS/2 2.1
compilers and assemblers ported or derived from these platforms (e.g.
emx/gcc, gcc/2, Borland C++/2, et.al). There are also visual programming
tools such as VisPro/Rexx and VX-Rexx that offer the programmer more
choice in development environments.
Programmers can write programs that interface with OS/2 2.1's object-
oriented subsystem called System Object Model (SOM). SOM is a language-
independent specification for object-oriented programming. Programmers
can enhance system-provided objects by overriding the desired methods, for
instance, or change the behaviour of the Workplace Shell (WPS) -- OS/2
2.1's object-oriented shell based on SOM -- such as changing the
behaviour of a "folder" (an object) by modifying a method or two without
having to rewrite a "folder" from scratch. IBM is working on enhancing
SOM's object-oriented specification by means of Distributed SOM (DSOM)
to allow such actions across a network, OpenDoc, and Taligent Frameworks
as part of IBM's cross-platform strategy with its future Workplace OS and
Pink operating systems.
OS/2 can be connected to other platforms, or to other OS/2 machines,
through networking. TCP/IP is a popular networking package for OS/2
machines. This will be more so since a free TCP/IP package is being
worked on right now.
OS/2 1.3 has long been popular in networking environments, although there
is less need for regular people to run OS/2 1.3 due to the popularity of
OS/2 2.1 (lower hardware prices, low-cost availability, and attractive
feature set).
HOW TO VOTE
You should send MAIL (posts to a group are invalid) to
jmaynard@oac.hsc.uth.tmc.edu
(just replying by MAIL to this message should work, if you're not reading this
as part of a mailing list). I will send mail acknowledgements for votes that
I receive. If you receive a correct ack, your vote has been received. If you
do not receive an ack after several days, you need to vote again. It is your
responsibility to see that your vote is recorded correctly.
USE THE FORM AS IT IS. Otherwise your vote may be rejected. Do not delete
anything between the "-=-=-=-=-" lines - and most certainly do not monkey with
the group names. Please delete everything but the ballot itself, though; I
don't need another copy of the full CFV. You may _NOT_ do a combined vote -
i.e., "I vote for all of them" or "I vote against all of them."
For each group, simply add your vote between the brackets on the same line.
Recognized votes are Yes and No. Capitalization is not important. If you
don't want to vote on a particular group, just leave the space blank. Don't
worry about spacing of the columns or any quote characters ">" that your reply
inserts.
Anything else may be rejected by the automatic vote counting program. ABSTAINs
do not affect the vote outcome. You may change your vote later by voting
again. The votetaker will respond to received ballots with mail acks.
Addresses and votes of all voters will be published in the vote results. If
you wish to remove your vote and all indication that you have voted from the
final list, send a vote with CANCEL in each voting position.
Standard Guidelines for voting apply. Only one vote per person, and only one
vote per account, will be counted. For each proposal to pass, 100 more YES
votes than NO votes and twice as many YES votes as NO votes must be received.
Simple instructions: Delete everything above the top "-=-=-=-" line, delete
everything below the bottom "-=-=-=-" line. Give your real name on the line
that asks for it. For each group, place a YES or NO in the brackets next to
it to vote for or against it.
[[ news.announce.newgroups moderator's note: IMPORTANT! A vote of "YES" for
comp.os.os2.ver1x means you agree it should be deleted; one of "NO" means it
should be retained. This is exactly opposite the meanings of YES/NO votes
for the other groups in the proposal. -- tale ]]
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
comp.os.os2 reorganization Ballot <COOR-0001> (Don't remove this marker)
Give your real name here:
[Your Vote] Group
-----------------------------------------------------------------------
[ ] comp.os.os2.games
[ ] comp.os.os2.programmer.tools
[ ] comp.os.os2.programmer.oop
[ ] comp.os.os2.networking.tcp-ip
[ ] comp.os.os2.networking.misc
[ ] comp.os.os2.ver1x
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu | adequately be explained by stupidity.
"The difference between baseball and politics is that, in baseball, if you
get caught stealing, you're out!" -- Ed Shanks
From jmaynard@oac.hsc.uth.tmc.edu Thu Mar 10 15:13:20 1994
Sender: tale@uunet.uu.net
Date: 9 Mar 1994 18:06:30 -0500
Lines: 222
Path: uunet!bounce-back
From: jmaynard@oac.hsc.uth.tmc.edu (Jay Maynard)
Reply-To: jmaynard@oac.hsc.uth.tmc.edu
Followup-To: poster
Newsgroups: news.announce.newgroups,news.groups,comp.os.os2.announce,comp.sys.ibm.pc.games.announce
Subject: 2nd CFV: comp.os.os2 reorganization
Message-ID: <comp.os.os2-reorg-CFV2@uunet.uu.net>
References: <comp.os.os2-newgr-RFD1@uunet.uu.net> <comp.os.os2-reorg-CFV1@uunet.uu.net>
Supersedes: <comp.os.os2-reorg-CFV1@uunet.uu.net>
Organization: Usenet Volunteer Votetakers...the knights who say ACK!
Approved: tale@uunet.uu.net
Expires: 18 Mar 1994 00:00:00 GMT
Xref: uunet news.announce.newgroups:4755 news.groups:97755 comp.os.os2.announce:464 comp.sys.ibm.pc.games.announce:398
LAST CALL FOR VOTES (of 2)
Reorganization of comp.os.os2
Summary of proposals (all unmoderated):
a) Create comp.os.os2.games
b) Create comp.os.os2.programmer.tools
c) Create comp.os.os2.programmer.oop
d) Create comp.os.os2.networking.tcp-ip
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
f) Remove comp.os.os2.ver1x
Newsgroups lines:
comp.os.os2.games Running games under OS/2
comp.os.os2.programmer.tools Compilers, assemblers, interpreters under OS/2
comp.os.os2.programmer.oop Programming system objects (SOM, WPS, etc)
comp.os.os2.networking.tcp-ip TCP/IP under OS/2
comp.os.os2.networking.misc Miscellaneous networking issues of OS/2
Votes must be recieved by 23:59:59 GMT, 17 March 1994.
This vote is being conducted by a neutral third party. For voting questions
only, contact Jay Maynard (jmaynard@oac.hsc.uth.tmc.edu). For questions about
the proposed groups, contact the proposer, Mike Levis, at
mlevis@ringer.cs.utsa.edu.
A pointer to this Call for Votes is being posted to the following groups:
comp.os.os2.apps, comp.os.os2.programmer.misc, comp.os.os2.networking, and
comp.os.os2.ver1x.
CHARTER
a) Create comp.os.os2.games
Charter: Unmoderated discussion of OS/2-specific games (e.g.
pricing, availability, features, reviews, previews, surveys,
etc.), and discussion of running DOS and Windows games under
OS/2 (e.g. compatibility, settings, etc.).
Note that discussion of DOS and Windows games not related
to OS/2 belongs in the proper games newsgroup.
b) Create comp.os.os2.programmer.tools
Charter: Unmoderated discussion of programming tools (compilers,
interpreters, assemblers) that generates or executes OS/2
code, and discussion of running DOS and Windows programming
tools under OS/2.
Note that discussion of DOS and Windows programming tools
not related to OS/2 (e.g. how much does `<xyz> for DOS'
cost) belongs in the proper programming newsgroup.
c) Create comp.os.os2.programmer.oop
Charter: Unmoderated discussion of programming for OS/2's object-
oriented subsystem, including SOM, DSOM, OpenDoc, and
Taligent Frameworks.
Note that discussion of object-oriented languages (e.g.
C++, Smalltalk) belongs in the proper language newsgroup.
d) Create comp.os.os2.networking.tcp-ip
Charter: Unmoderated discussion of TCP/IP (e.g. hardware, drivers,
setup, problems, bugs, etc.) under all versions of OS/2.
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
Reason: The standard practice of Usenet is usually to rename a
split newsgroup as .misc.
Charter: comp.os.os2.networking.misc will continue to be the
newsgroup to discuss miscellaneous OS/2-related networking
issues in an unmoderated setting.
f) Remove comp.os.os2.ver1x
Reason: OS/2 1.3 is now used mostly by companies (such as in
networking environments or ATMs) managed by long-time
experts rather than by regular people (i.e. Usenet
readers).
RATIONALE
The popularity of 32-bit OS/2 2.1 is growing, thanks to a combination
of lower hardware prices, low-cost availability of OS/2 2.1, and an
attractive feature set of OS/2 2.1. One of the great strengths of OS/2
2.1 is to run DOS and Windows programs, such as games.
Games are among the most picky programs to configure, many requiring
DOS users to have different CONFIG.SYS and AUTOEXEC.BAT files to play.
OS/2 2.1 makes it easier because it allows many DOS games to run without
having to reboot the computer. Under OS/2 2.1, each DOS or Windows game
(or non- game program, for that matter) can have its very own environment,
such as its own AUTOEXEC.BAT file, its own CONFIG.SYS lines, memory setup,
and so forth. OS/2 2.1 also makes an excellent platform for its own games
as well. With features such as multi- threading and multi-media, there
are freeware, shareware, and commercial OS/2 games that are already here
or are being developed. But OS/2 is not just for playing around.
There is a slew of OS/2 2.1 programming tools -- each having advantages
and disadvantages over another. Since OS/2 2.1 can be likened to a bridge
between UNIX, OS/2 1.3, DOS, and Windows, there have been many OS/2 2.1
compilers and assemblers ported or derived from these platforms (e.g.
emx/gcc, gcc/2, Borland C++/2, et.al). There are also visual programming
tools such as VisPro/Rexx and VX-Rexx that offer the programmer more
choice in development environments.
Programmers can write programs that interface with OS/2 2.1's object-
oriented subsystem called System Object Model (SOM). SOM is a language-
independent specification for object-oriented programming. Programmers
can enhance system-provided objects by overriding the desired methods, for
instance, or change the behaviour of the Workplace Shell (WPS) -- OS/2
2.1's object-oriented shell based on SOM -- such as changing the
behaviour of a "folder" (an object) by modifying a method or two without
having to rewrite a "folder" from scratch. IBM is working on enhancing
SOM's object-oriented specification by means of Distributed SOM (DSOM)
to allow such actions across a network, OpenDoc, and Taligent Frameworks
as part of IBM's cross-platform strategy with its future Workplace OS and
Pink operating systems.
OS/2 can be connected to other platforms, or to other OS/2 machines,
through networking. TCP/IP is a popular networking package for OS/2
machines. This will be more so since a free TCP/IP package is being
worked on right now.
OS/2 1.3 has long been popular in networking environments, although there
is less need for regular people to run OS/2 1.3 due to the popularity of
OS/2 2.1 (lower hardware prices, low-cost availability, and attractive
feature set).
NOTE...
Due to a clerical error, my account on this machine was deleted on 1 March.
Some ballots in the ongoing vote have been lost, as the files in my account
were restored from a backup taken the evening of 28 February. It was restored
the afternoon of 1 March.
If you have not received an acknowledgement for your vote, or if your
acknowledgement was sent between noon US Central Time (1800 GMT) on 28
February and 2 PM US Central Time (2000 GMT) on 1 March, and you have not
received another acknowledgement from me since then, you need to vote again,
as your vote has been lost. If your acknowledgement was sent outside that
time, you should be OK. If you're not sure, please feel free to vote again;
duplicate votes will be weeded out during the counting process.
This note was posted to the same groups as the original Call for Votes; it is
being repeated here to ensure that interested people see it.
HOW TO VOTE
You should send MAIL (posts to a group are invalid) to
jmaynard@oac.hsc.uth.tmc.edu
(just replying by MAIL to this message should work, if you're not reading this
as part of a mailing list). I will send mail acknowledgements for votes that
I receive. If you receive a correct ack, your vote has been received. If you
do not receive an ack after several days, you need to vote again. It is your
responsibility to see that your vote is recorded correctly.
USE THE FORM AS IT IS. Otherwise your vote may be rejected. Do not delete
anything between the "-=-=-=-=-" lines - and most certainly do not monkey with
the group names. Please delete everything but the ballot itself, though; I
don't need another copy of the full CFV. You may _NOT_ do a combined vote -
i.e., "I vote for all of them" or "I vote against all of them."
For each group, simply add your vote between the brackets on the same line.
Recognized votes are Yes and No. Capitalization is not important. If you
don't want to vote on a particular group, just leave the space blank. Don't
worry about spacing of the columns or any quote characters ">" that your reply
inserts.
Anything else may be rejected by the automatic vote counting program. ABSTAINs
do not affect the vote outcome. You may change your vote later by voting
again. The votetaker will respond to received ballots with mail acks.
Addresses and votes of all voters will be published in the vote results. If
you wish to remove your vote and all indication that you have voted from the
final list, send a vote with CANCEL in each voting position.
Standard Guidelines for voting apply. Only one vote per person, and only one
vote per account, will be counted. For each proposal to pass, 100 more YES
votes than NO votes and twice as many YES votes as NO votes must be received.
Simple instructions: Delete everything above the top "-=-=-=-" line, delete
everything below the bottom "-=-=-=-" line. Give your real name on the line
that asks for it. For each group, place a YES or NO in the brackets next to
it to vote for or against it.
[[ news.announce.newgroups moderator's note: IMPORTANT! A vote of "YES" for
comp.os.os2.ver1x means you agree it should be deleted; one of "NO" means it
should be retained. This is exactly opposite the meanings of YES/NO votes
for the other groups in the proposal. -- tale ]]
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
comp.os.os2 reorganization Ballot <COOR-0002> (Don't remove this marker)
Give your real name here:
[Your Vote] Group
-----------------------------------------------------------------------
[ ] comp.os.os2.games
[ ] comp.os.os2.programmer.tools
[ ] comp.os.os2.programmer.oop
[ ] comp.os.os2.networking.tcp-ip
[ ] comp.os.os2.networking.misc
[ ] comp.os.os2.ver1x
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
BOUNCE ACKNOWLEDGEMENTS
The voters in the following list may not have received mail acknowledgements
due to one problem or another. If you appear in this list, your vote has been
received and recorded; you don't need to do anything else (except, possibly,
check out any problems you may be having receiving mail.)
comp.os.os2 reorganization Bounce Ack List
------------------------------------------------------------------------------
bradw@rams
chorn%ew@spcvxa.spc.edu
fred@lucy.async.vt.edu
jima@ims.com
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu | adequately be explained by stupidity.
"The difference between baseball and politics is that, in baseball, if you
get caught stealing, you're out!" -- Ed Shanks
From jmaynard@oac.hsc.uth.tmc.edu Thu Mar 24 18:07:22 1994
Path: uunet!bounce-back
From: jmaynard@oac.hsc.uth.tmc.edu (Jay Maynard)
Newsgroups: news.announce.newgroups,news.groups,comp.os.os2.announce,comp.sys.ibm.pc.games.announce
Subject: RESULT: comp.os.os2 reorganization: all proposals pass
Supersedes: <comp.os.os2-reorg-CFV2@uunet.uu.net>
Followup-To: news.groups
Date: 22 Mar 1994 20:15:18 -0500
Organization: Usenet Volunteer Votetakers...the knights who say ACK!
Lines: 678
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <comp.os.os2-reorg-RESULT@uunet.uu.net>
References: <comp.os.os2-newgr-RFD1@uunet.uu.net> <comp.os.os2-reorg-CFV1@uunet.uu.net> <comp.os.os2-reorg-CFV2@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4815 news.groups:98770 comp.os.os2.announce:477 comp.sys.ibm.pc.games.announce:411
RESULTS
Reorganization of comp.os.os2
Summary of proposals (all unmoderated):
a) Create comp.os.os2.games
b) Create comp.os.os2.programmer.tools
c) Create comp.os.os2.programmer.oop
d) Create comp.os.os2.networking.tcp-ip
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
f) Remove comp.os.os2.ver1x
comp.os.os2 reorganization results - 486 valid votes
Yes No : 2/3? >100? : Pass? : Group
---- ---- : ---- ----- : ----- : -------------------------------------------
440 32 : Yes Yes : Yes : comp.os.os2.games
432 31 : Yes Yes : Yes : comp.os.os2.programmer.tools
412 47 : Yes Yes : Yes : comp.os.os2.programmer.oop
428 37 : Yes Yes : Yes : comp.os.os2.networking.tcp-ip
421 38 : Yes Yes : Yes : comp.os.os2.networking.misc
322 106 : Yes Yes : Yes : comp.os.os2.ver1x
12 invalid votes
Newsgroups lines:
comp.os.os2.games Running games under OS/2
comp.os.os2.programmer.tools Compilers, assemblers, interpreters under OS/2
comp.os.os2.programmer.oop Programming system objects (SOM, WPS, etc)
comp.os.os2.networking.tcp-ip TCP/IP under OS/2
comp.os.os2.networking.misc Miscellaneous networking issues of OS/2
Voting ended at 00:00:00 GMT, 18 March 1994.
This vote was conducted by a neutral third party. For voting questions only,
contact Jay Maynard (jmaynard@oac.hsc.uth.tmc.edu). For questions about the
proposed groups, contact the proposer, Mike Levis, at
mlevis@ringer.cs.utsa.edu.
CHARTERS
a) Create comp.os.os2.games
Charter: Unmoderated discussion of OS/2-specific games (e.g.
pricing, availability, features, reviews, previews, surveys,
etc.), and discussion of running DOS and Windows games under
OS/2 (e.g. compatibility, settings, etc.).
Note that discussion of DOS and Windows games not related
to OS/2 belongs in the proper games newsgroup.
b) Create comp.os.os2.programmer.tools
Charter: Unmoderated discussion of programming tools (compilers,
interpreters, assemblers) that generates or executes OS/2
code, and discussion of running DOS and Windows programming
tools under OS/2.
Note that discussion of DOS and Windows programming tools
not related to OS/2 (e.g. how much does `<xyz> for DOS'
cost) belongs in the proper programming newsgroup.
c) Create comp.os.os2.programmer.oop
Charter: Unmoderated discussion of programming for OS/2's object-
oriented subsystem, including SOM, DSOM, OpenDoc, and
Taligent Frameworks.
Note that discussion of object-oriented languages (e.g.
C++, Smalltalk) belongs in the proper language newsgroup.
d) Create comp.os.os2.networking.tcp-ip
Charter: Unmoderated discussion of TCP/IP (e.g. hardware, drivers,
setup, problems, bugs, etc.) under all versions of OS/2.
e) Rename comp.os.os2.networking to comp.os.os2.networking.misc
Reason: The standard practice of Usenet is usually to rename a
split newsgroup as .misc.
Charter: comp.os.os2.networking.misc will continue to be the
newsgroup to discuss miscellaneous OS/2-related networking
issues in an unmoderated setting.
f) Remove comp.os.os2.ver1x
Reason: OS/2 1.3 is now used mostly by companies (such as in
networking environments or ATMs) managed by long-time
experts rather than by regular people (i.e. Usenet
readers).
RATIONALE
The popularity of 32-bit OS/2 2.1 is growing, thanks to a combination
of lower hardware prices, low-cost availability of OS/2 2.1, and an
attractive feature set of OS/2 2.1. One of the great strengths of OS/2
2.1 is to run DOS and Windows programs, such as games.
Games are among the most picky programs to configure, many requiring
DOS users to have different CONFIG.SYS and AUTOEXEC.BAT files to play.
OS/2 2.1 makes it easier because it allows many DOS games to run without
having to reboot the computer. Under OS/2 2.1, each DOS or Windows game
(or non- game program, for that matter) can have its very own environment,
such as its own AUTOEXEC.BAT file, its own CONFIG.SYS lines, memory setup,
and so forth. OS/2 2.1 also makes an excellent platform for its own games
as well. With features such as multi- threading and multi-media, there
are freeware, shareware, and commercial OS/2 games that are already here
or are being developed. But OS/2 is not just for playing around.
There is a slew of OS/2 2.1 programming tools -- each having advantages
and disadvantages over another. Since OS/2 2.1 can be likened to a bridge
between UNIX, OS/2 1.3, DOS, and Windows, there have been many OS/2 2.1
compilers and assemblers ported or derived from these platforms (e.g.
emx/gcc, gcc/2, Borland C++/2, et.al). There are also visual programming
tools such as VisPro/Rexx and VX-Rexx that offer the programmer more
choice in development environments.
Programmers can write programs that interface with OS/2 2.1's object-
oriented subsystem called System Object Model (SOM). SOM is a language-
independent specification for object-oriented programming. Programmers
can enhance system-provided objects by overriding the desired methods, for
instance, or change the behaviour of the Workplace Shell (WPS) -- OS/2
2.1's object-oriented shell based on SOM -- such as changing the
behaviour of a "folder" (an object) by modifying a method or two without
having to rewrite a "folder" from scratch. IBM is working on enhancing
SOM's object-oriented specification by means of Distributed SOM (DSOM)
to allow such actions across a network, OpenDoc, and Taligent Frameworks
as part of IBM's cross-platform strategy with its future Workplace OS and
Pink operating systems.
OS/2 can be connected to other platforms, or to other OS/2 machines,
through networking. TCP/IP is a popular networking package for OS/2
machines. This will be more so since a free TCP/IP package is being
worked on right now.
OS/2 1.3 has long been popular in networking environments, although there
is less need for regular people to run OS/2 1.3 due to the popularity of
OS/2 2.1 (lower hardware prices, low-cost availability, and attractive
feature set).
NOTE...
Due to a clerical error, my account on this machine was deleted on 1 March.
Some ballots in the ongoing vote have been lost, as the files in my account
were restored from a backup taken the evening of 28 February. It was restored
the afternoon of 1 March.
All votes outside of that time frame have been counted and acknowledged. A
note about the problem was posted separately to the same groups as this
posting, as well as being included in the second Call for Votes.
VOTES
Votes from the following people have been received:
comp.os.os2 reorganization Final Vote Ack
comp.os.os2.ver1x --------+
comp.os.os2.networking.misc -------+|
comp.os.os2.networking.tcp-ip ------+||
comp.os.os2.programmer.oop -----+|||
comp.os.os2.programmer.tools ----+||||
comp.os.os2.games ---+|||||
||||||
A.H.Henry@midge.bath.ac.uk Andrew Henry YY----
a01dgu1@mvs.niu.edu Dave Ulrick YYYYYY
a5g192@rick.cs.ubc.ca YYYYYN
aaa@atl.hp.com Simon Fowler -----N
achatche@midway.uchicago.edu Andrew Hatchell YYYYYY
acollins@EECS.Berkeley.EDU Andy Collins YYYYYY
aden_steinke.admin_po@central-gw.uow.edu.au Aden Steinke Y----Y
aev@dcs.kcl.ac.uk Alexis E Vassilakas YYYYYY
ag916@freenet.carleton.ca Nicholas Mayo ag916@Freenet.Carleton.CA YYYYYY
aguy@sheartl.hna.com.au Andrew Guy YYYYYY
ahabig@bigbang.astro.indiana.edu Alec Habig YYYYYY
ahostma@cscns.com Art Hostmark YYYYYY
ahuttune@delta.hut.fi Ari Huttunen YYYYYY
aicrelay!news!annv@xorbithost.austin.aicnet.com Ann Vanderlaan YYYYYY
al198723@academ01.mty.itesm.mx Eugenio Sanchez NYYYYY
alec+@CMU.EDU Alec Flett YYYYYY
amberle@maroon.tc.umn.edu Amberle S Ferrian YYYYYY
anderson@allvax.enet.dec.com Dave Anderson YYYYY-
anderss@forwiss.uni-passau.de Sven Anders YYYYYN
andreas@traci.almroth.pp.se Andreas Almroth YYYNNN
andy@arizona.edu Andy Hartman YYYYYY
andyl@harlequin.com Andy Latto YYYYYY
asselin@vnet.IBM.COM Andre Asselin Y--YYN
atkin901@cs.uidaho.edu Mark S. Atkinson YYYYYY
bachww@ferret.cig.mot.com Bud Bach YNNYYY
bbroad@netcom.com Bill Broadhurst YYYYYY
bburch@ux4.cso.uiuc.edu Bruce Burch YYYYYY
bc@unixg.ubc.ca Alan Ballard YYYYYY
bcrwhims@undergrad.math.uwaterloo.ca Carsten Whimster YYY---
bdpeterson@aol.com BRIAN PETERSON YYYYYY
benc@netcom.com Ben Coleman YYYYYN
benningf@aurfs1.aur.alcatel.com Robert F. Benningfield Jr. NNNNNN
bernd@batman.RoBIN.de Bernd Driegert YYYYYY
bernie@bjt105.rh.psu.edu Bernie Thompson YYYYYY
bferrell@uceng.uc.EDU Brett D. Sherron-Ferrell YYYYYY
BJohnson@WorldBank.Org YYYYYY
bobdehn@mprcamnl.wr.usgs.gov Bob Dehnhardt YYYYYY
boyj@troi.cc.rochester.edu John H. Boyd III YYYYYY
brad@mesnet.mesonet.uoknor.edu Thomas B. Stanley YYYYYY
bradw@rams Brad Wright YYYYYY
Brian.Davis@dwe.csiro.au Brian Davis YYYYY-
budworth@netcom.com David Budworth YYYYYY
burleigh@bronze.ucs.indiana.edu Frank Burleigh YNNNYY
burt+@CMU.EDU Burt Holzman YYYYYY
bylee@phoenix.Princeton.EDU Benjamin Y. Lee YYYYYY
caliaro@avalon.unizh.ch Aurelio Caliaro YYYYY-
cambria@world.std.com Michael C. Cambria YYYYYN
campbell@brahms.udel.edu L L Campbell YYYYYY
caveman@wam.umd.edu Caveman YYYYYY
cchan1@ux4.cso.uiuc.edu Christopher Chan YYYYYY
cgtaylor@engprn.mobil.com Clement G. Taylor YYYYYY
ch71@columbia.edu Christopher Horymski YYYYYY
chad@WINDSURF.unmc.edu YYYYYY
chandoni@husc.harvard.edu John-Marc Chandonia YYYYYY
Charles_Wong@mindlink.bc.ca Charles K.F. Wong YYYYYY
chip%fin.uucp@dg-rtp.dg.com Chip Salzenberg YYYYYN
chip@clark.net Chip Davis YYYYYY
chorn%ew@spcvxa.spc.edu Christopher Horn YYYYYN
chris@suite.sw.oz.au Chris Maltby YYYYYN
chuahl@soda.berkeley.edu Chua Hak Lien YYYYYY
cjensen@netcom.com Colin Jensen YYY--Y
cjl@ukelele.GCR.COM Chris Linstruth Y--YYN
Clark.Gaylord@vt.edu Clark Gaylord YYYYN-
clemenmf@sluaxa.slu.edu Marc F. Clemente YNY--Y
clement!dhosek@netcom.com Don Hosek YYYYYN
cliff@shell.portal.com Clifford L. Pelletier -YYYY-
cmiller@netcom.com Chris Miller Y-----
coates@physics.uq.oz.au Anthony Coates YYYYYY
comital@ecf.toronto.edu Leo Comitale YYYYYY
corrigan@aplcomm.jhuapl.edu YYYYYN
coulman@skaries.USask.ca Randy Coulman YYYYYY
cpage@eniac.seas.upenn.edu Carter Page ---YY-
cro@socrates.ed.asu.edu C. R. Oldham YYYYYY
crouchkp@flidh102.delcoelect.com Kenneth P. Crouch, Jr. NNNNNN
crp5754@erfsys01.boeing.com Chris Payne NNNNNN
cs334001@Armstrong.EDU James Peterson YYYNYY
cses66@maccvm.corp.mot.com Guy Roshto YYYYYY
cstreete@nyx10.cs.du.edu Carl Streeter YYYYYN
cs_a264@kingston.ac.uk Frederico Terenas YYYYYY
CVABA428@CSUPomona.Edu NAME "Boulton A. Fernando" YYYYYY
cvale@netcom.com Chris Vale YYYYYY
cwiseley@cc1.cccco.edu W. Charles Wiseley YYYYYY
d.greenberger@cornell.edu David Greenberger YYYYYN
daled@cadence.com Dale DePriest YYYYYY
DALONGMU@ELECTRICAL.watstar.uwaterloo.ca Derek A. Longmuir YYYYYY
dan@cs.mun.ca Dan Best YYY--Y
danap@crl.com Dana P'Simer YYYYYN
davem@ee.ubc.ca Dave Michelson YYYYYN
david@porsche.visix.COM David Charlap YYYYYY
davidp@aadt.com David E. Pedigo YYYYYY
dbr@garnet.msen.com David B. Rein YYYYYY
dbrajort@sss.montrouge.rps.slb.com David BRAJORT YYNYYY
dbullock@vnet.IBM.COM Dan Bullock YYYYYY
decastro@netcom.com Richard A. De Castro YYYYYY
DFROST@wvuvphs1.hsc.wvu.edu Dennis Frost YYYY-N
dgal@cad.gatech.edu Damon Gallaty YYYYYY
dhd@umich.edu David H Detlefs YYYYYN
DHS10@phx.cam.ac.uk David Scott YYYYYY
dick@dw.itg.ti.com Dick Whitehurst YYYYYY
DITTMAN@skitzo.dseg.ti.com Eric Dittman YYYYYY
dodger@sztma.tu-graz.ac.at Starlinger YYYYYY
Doug_Crozier.LOTUS@CRD.lotus.com Doug Crozier YYYYYY
downes@mkcase1.dseg.ti.com Stephen Downes YYYYYY
DPETERSON@astro.sunysb.edu Deane Peterson (DPeterson@sbast1.ess.suny YYYYYY
drayer@minerva.cis.yale.edu Rebecca Drayer YYYYYY
dries@elvis.rowan.edu PowerSlave YYYYYN
duffy@theory.chem.ubc.ca Patrick Duffy YYYYYY
dweller@sugar.NeoSoft.COM DAvid Weller YYYYYN
dwl@watson.ibm.com David W. Levine YYYYYN
dz@phantom.msk.su Dmitry Zavalishin YYYYNY
eaiu184@orion.oac.uci.edu Jimmy Shaw YYYYYY
EBB7683@VENUS.TAMU.EDU Ed Blackman YYYYYN
eck@s704.dseg.ti.com Terry Eck (@s704) YYYYYY
eckstein@susy.isd.uni-stuttgart.de Knut Eckstein YYYYYN
edp480b@apple.fcit.monash.edu.au Kon Katsaros YYYYYY
efeustel@ida.org Edward Feustel YYYYYN
eigler@vnet.IBM.COM Frank Ch. Eigler YYNYYN
emd@ham.almanac.bc.ca Robert Smits YYYYYY
empire@nwu.edu David A. Guidry YYYYYY
enos@erc.cat.syr.edu Ronald Enos YYYYYY
erbo@coyote.rain.org Eric J. Bowersox YYYYYN
eric@logsdon.atl.ga.us Eric Logsdon YYYYYY
eric@ramsey.cs.laurentian.ca Eric Vanden Heuvel YYYYYY
erikmo@oslonett.no Erik Mogensen YYYYYY
es070@eng.warwick.ac.uk David Barnsdale YYYYY-
essig@snowhite.eeap.cwru.edu Robert A. Essig YYYYYY
essmjf@netcom.com Michael Faklis YYYYYY
etellefs@lehman.com Eric Tellefsen YYYYYY
etxjafa@eua.ericsson.se Jan Fagerstrom YYYYYY
eurjof@mvs.sas.com Jochen Friedrich YYYYYY
evanc@spatial.synapse.org Evan Champion YYYYYY
fernand@morgan.com Chris Fernandes YYYYYY
fkk@stasys.sta.sub.org Frank Kaefer NNNNNN
flash@aragorn.csee.lehigh.edu Stephen Corbesero YYYYYY
floppy@paola.dei.unipd.it Toniolo Emanuele YYYYYY
fn@mathappl.polymtl.ca Francois Normant/16384 YYYYYN
francis@vnet.IBM.COM Tim Francis YYYYYY
frank@sax.sax.de Frank Behrens YYYYY-
frankdn@mv.MV.COM Douglas Frank YYYYYN
fred@vt.edu Fredrick R Homan YYYYYY
freddy!jerome.yuzyk@tibalt.supernet.ab.ca Jerome Yuzyk YYYYYN
fredrik@idt.unit.no Fredrik Kvamme YYYYYY
fsspr@camelot.acf-lab.alaska.edu Sean P. Ryan NYNYYY
fvck2412%aimws6@aimws6.rus.uni-stuttgart.de Martin Thierer YYYYYY
fw@world.std.com Forrest D. Whitcher YYYYYY
G.Siegert@kri.uni-koeln.de Gabriele Siegert YYYYYY
gaetano@dmi.stevens-tech.edu Gaetano Liberatore YYYYYN
gareth@qdeck.com Gareth Boulton YYYYYY
Georg.Brandal@mrih.no Georg Brandal YYYYYY
gerhard@horse.sax.de Gerhard Kociok YYYYYY
GHDAI@VAX1.UMKC.EDU YYYYYY
gisle@elkraft.unit.no Gisle J Torvetjoenn YYYYYY
gkoehler@arlut.utexas.edu George Koehler
YYYYY-
glen@cs.utexas.edu Glen Graham YYYYYY
glga@MR.Net Gary Greenberg YYYYYY
GLITTLE@bcsc02.gov.bc.ca Glen Little YYYYYN
glj@iai.MV.COM Glenn A. Larson, Jr. YYYYY-
godau@dec2.wi-inf.uni-essen.de Hans-Juergen Godau YYYYYY
GOLDMAN@ala.btk.utu.fi YYYYYY
gordon@ll.mit.edu Gordon Matheson YYYYYY
gordy@panix.com Gordy Thompson YYYYYY
goyal@utdallas.edu Mohit Goyal YYYYYY
graeme.lindsell@anu.edu.au Graeme Lindsell YYYYYY
gregory@bcstec.ca.boeing.com Greg Wright YYNYYY
greve@rs1.thch.uni-bonn.de Thomas Greve YYNYYN
griffin@admaix.sunydutchess.edu Patrick J. P. Griffin YYYYYN
grimes@netcom.com grimes@netcom.com YYYYYY
gspear+@CMU.EDU Geoffrey Spear NYYYNY
gt7027c@acme.gatech.edu Carlos YYYYYY
gt8006b@acme.gatech.edu Bradley D. Porter YYYYYN
gumo@df.lth.se Gustav Morin YYYYYY
gwk@world.std.com Greg Kushmerek YYYYYY
h.p.kiehl@kfa-juelich.de Horst Kiehl YYYYY-
haan@fgbbs.iaf.nl Henk de Haan YYYNNY
hajo@quijote.in-berlin.de Hans-Joachim Zierke -YYYYY
harlie@brian.org Brian S. Hall YYYYY-
hassag@rpi.edu George C. Hassa, Jr. YYYYYY
hayden@krypton.mankato.msus.edu Robert A. Hayden YYYYYY
HD0022%ALBNYVMS.bitnet@UACSC2.ALBANY.EDU Chip Dunham NNNNNY
heath@austin.ibm.com YYYYYY
hermus@nlr.nl Bart Hermus ---YY-
hethmon@cs.utk.edu Paul Hethmon YYYYYY
hildajk1@aplcomm.jhuapl.edu Ken Hildabolt YNYNNY
hmkirchh@cip.informatik.uni-erlangen.de Hans-Jochen Kirchhoff YYYYYY
hucke@sumter.cso.uiuc.edu Matt Hucke YYYYYN
hyongel@cco.caltech.edu Hyong Lee Y--YY-
ian@uhunix.uhcc.Hawaii.Edu Ian Gibbons YYYYYY
ian@vnet.IBM.COM Ian Stirling YYYYYY
ianst@qdpii.ind.dpi.qld.gov.au Ian Staples YYYYY-
im790921@im.mgt.ncu.edu.tw Xu Chang Qing YYYYYY
J.C.vanderWal@research.ptt.nl Kees van der Wal YYYYY-
J.Hoppenbrouwers@kub.nl Jeroen Hoppenbrouwers YYYYY-
J0S@PSUVM.PSU.EDU Jack W. Sharer YYYYYY
jacob@rygel.anorad.com Jacob George YYYYYY
jadoerin@MIT.EDU Joseph A. Doeringer YYYYYY
jalcorn@marvin.wariat.org Justin B. Alcorn YYYYYY
jamesp@cory.EECS.Berkeley.EDU James Peroulas YYYYYY
janrune@ccwf.cc.utexas.edu Jan Rune Andreassen YYYYYY
jarlehto@utu.fi Jari Lehtonen YYY---
jcarmack@phoenix.aps.muohio.edu John D. Carmack YYNYYY
jcollier@alexandra.mtl.com John Collier YYYYYY
jderrico@umich.edu John A. D'Errico YYYYYY
jdp9w@watt.seas.virginia.edu John D. Palmer Y--YY-
Jean-Philippe.Fassino@babbage.imag.fr Fassino@ufrima.imag.fr YYYYYY
jeff@neon.rain.com J. Beadles NNNNNY
jelle@farallon.sac.unify.com Jelle Jorritsma YYYYYY
jgarzik@pantera.atl.ga.us Jeff Garzik YYNYYY
jgd@dixie.com John De Armond NYYYYY
jhm@netcom.com Jonathan Hulley-Miller YYYYYN
jim@draco.bison.mb.ca Jim Jaworski YYNYYY
jima@ims.com James L. Agin YYYYYY
jjl@civen.civil.wits.ac.za Dr J J Lambourne YYYY--
jk@zarniwoop.pc-labor.uni-bremen.de Jens Kuespert -YYYY-
jkfurr@eecs.umich.edu Hardchargin Sanhedrin NNNNNY
jks@giskard.utmem.edu John K. Spitznagel, Jr. YYYYYY
jliukkon@cc.helsinki.fi Juha Liukkonen YYYYY-
jmartz@gibbs.oit.unc.edu John M. Martz YYYYYY
jmcging@access.digex.com John McGing YYYYYY
jmehl@strauss.udel.edu James B. Mehl YYYYYY
joachim@urz.unibas.ch Peter Joachim YYYYYY
joe@decoy.uoregon.edu Joe St Sauver YYYYYY
johansso@elixir.e.kth.se Anders Johansson YYY--Y
john.heater@father.com JOHN HEATER YYYYYN
john@uhs1.uhs.uga.edu YY-NNN
johnh@meaddata.com John Holt johnh@meaddata.com YYYYYY
johnwu@netcom.com John Wu Y--YYY
John_Bodnar-R16292@email.sps.mot.com John Bodnar YYYYYY
jost@dkb.dk John Staahle YYYYY-
jpc@avdms8.msfc.nasa.gov J. Porter Clark YYYYYN
jrlink@netcom.com John R. Link YYYNN-
jsruebel@iastate.edu James S. Ruebel YYYYYY
JSTMN@aurora.alaska.edu Todd Nagengast YYYYY-
jstuart@nptn.org Jeffrey A. Stuart YYYYYY
jtiller@kelvin.jpl.nasa.gov Jason B. Tiller YYYYYY
judd@austin.ibm.com Judd Rogers YYYYYY
julian@bongo.tele.com Julian Macassey NNNNNN
jzawodn@andy.bgsu.edu YYYYYY
kadorken@Thinkage.On.CA Keith Dorken YYYYNY
kassarji@spot.Colorado.EDU Steven J Kassarjian YYYYYY
katzer@estd.nrl.navy.mil D. Scott Katzer YYYYYY
kbass@hns.com Ken Bass YYYYYY
keith@its.bldrdoc.gov Keith Junker YYYYYY
kenton+@CMU.EDU Kenton W Shaver YNY---
kirk@enterp.raider.net Jason Neal YYYYYY
kjb@CVSD.CV.COM Ken Brucker YYYYYN
kkudielk@email.tuwien.ac.at Klaus Kudielka ---YYY
klaus@gnugate.rhein.de Klaus Guhr <klaus@gnugate.rhein.de> YYYYYN
klevin@isumataq.eskimo.com Noah Romer YYYYY-
klund@MIT.EDU Kent Lundberg YYNYYN
kmb@cameron.delme.north.de Kai M. Becker YYYYYY
kohlhaas@faw.uni-ulm.de Bernhard Kohlhaas YYYYY-
kris@binkley.cs.mcgill.ca Christian Zabbal YYYYYY
krlynch@MIT.EDU Kevin Lynch YYYYYY
landy@altair.krl.caltech.edu Brian R. Landy Y--YY-
larsen@cs.uregina.ca Bryan Larsen YYYYYY
las@cbnmva.att.com Larry A. Shurr YYYYYY
lday@vnet.IBM.COM Leland L. Day YYYYYN
LED873B@vma.smsu.edu Lynn Dickison YYYYYY
lej2@po.cwru.edu Lewis Jones YYYYYN
leo@unlinfo.unl.edu Leo G. Chouinard II YYYYYY
leung@unixg.ubc.ca Johnnie Leung YYYYYY
linfield@bach.utias.utoronto.ca Kevin W Linfield YYYYYY
lode2@basil.eng.monash.edu.au Lachlan O'Dea YYYYYY
lou@hobbes.xilinx.com Lou Sanchez-Chopitea YYYYYY
LPARSONS@EAGLE.WESLEYAN.EDU Lance Parsons YYYYYY
lrj@helios.tn.cornell.edu Lew Jansen YYYYYY
lsr@taligent.com Larry Rosenstein --Y---
ltubbs@netcom.com Larry Tubbs YYYYYY
lucasj@mentor.cc.purdue.edu Joseph Lucas YYYYYN
lwalton@zombie.demon.co.uk Lee Walton YYNYYN
M.H.W.Bonse@wbmt.tudelft.nl Marcus Bonse YYYYYN
m.ruppel@imperial.ac.uk Markus Ruppel YYYYYY
Mahoney@emdisle.fidonet.org Mike Mahoney YYYYYN
marabldl@aplcore.jhuapl.edu David L. Marable Y--YYY
Marc_Van-Woerkom@ac3.maus.de Marc E.E. van Woerkom YYYYYY
margoli@watson.ibm.com Larry Margolis YYYYYN
markr@cs.kun.nl Mark Ruys YYYYYY
Martin.Lafaix@sophia.inria.fr Martin Lafaix YYYYYN
marvinl@netcom.com Marvin Lichtenthal YYYYYN
matagep@csv.warwick.ac.uk Faheem YYNNNN
mats@binkley.cs.mcgill.ca Mathieu Dupont YYYYYY
mau@beatles.cselt.stet.it Maurizio Codogno YNNNNY
maxk@dork.sps.mot.com Max Kull YYYYYN
mbhpfpj@meehpe.ee.man.ac.uk Paul John Floyd YYYYYN
mcarthur@oksw56.okanagan.bc.ca Rob McArthur YYYYYY
mdorman@world.std.com Michael A Dorman YYYYYY
mds@access.digex.net Michael D. Sullivan YYY---
mernst@interaccess.com Michael Ernst YYYYY-
messina@umich.edu Matt Messina YY-YY-
mgphl@crl.com Michael G. Phillips YYYYYY
mhagger@altair.krl.caltech.edu Michael Haggerty YYYYYY
mhuth@u.washington.edu Mark Huth YYYYYY
michaelh@amgen.com Michael Harris YYYYYY
Michael_Silverton@f1802.n202.z1.fidonet.org Michael Silverton YYYYYY
mikel@networx.com Mike Lempriere YYYYYN
miker@orion.med.bcm.tmc.edu Hung Michael Nguyen YYYYYY
mlevis@ringer.cs.utsa.edu Mike Levis - OS/2 2.1 GA YYYYYY
mmt@RedBrick.COM Maxime Taksar KC6ZPS NNNNNY
moloney@lds.loral.com Timothy M. Moloney YYYYYY
Mor@mavor.demon.co.uk Mike O'Reilly YYYYYY
msaletni@Jade.Tufts.EDU Michael J. Saletnik YYNYYN
msc%ssihub@uunet.uu.net Michael S. Cross YYYYYY
msilva@infi.net Mark Silva YYYYYY
mstaedt@va-klaus.va.fh-ulm.de Olaf Mittelstaedt YYYYYY
murali@magnet.fsu.edu Murali Chaparala NYYNNN
nareid@nvg.unit.no Helge Nareid YYYYYN
nathan@crl.com Nathan Hamblen Y-----
ncmoore2@aplcomm.jhuapl.edu Nathan C. Moore YY-YY-
nefud-the-delirious@tamu.edu Allan Bailey YYYYYY
nent10@isumataq.eskimo.com Dick Tennent YYYYYY
nholford@ccu1.auckland.ac.nz Nick Holford YYYYYY
nils@wildcat.dartmouth.edu Nils Nieuwejaar NNNNYY
njchalko@crash.cts.com Nick J Chalko -YYYYY
no6b@merlin.jpl.nasa.gov Robert Dengler YYYYYN
nobi@hobbes.nbg.sub.org Norbert Duell YYYYYY
norman@oncology.wisc.edu Norman R. Drinkwater YYYYYY
novik@physics.ubc.ca Keir Novik YYYYY-
npatrick@acs.bu.edu Neal Patrick YYYYYY
npross@undergrad.math.uwaterloo.ca Norm Ross YYYYYY
nwaltham@cix.compulink.co.uk Nicholas Waltham YYYYYY
oberhaus@dfki.uni-sb.de Fred Oberhauser YYYNYN
oeggerli@ezmlib.vmsmail.ethz.ch Andreas Oeggerli, Chem. Eng. Dep., E YYYYYY
offordj@wl.com Jim Offord YYYYYN
os2man@panix.com Larry Salomon, Jr. YYYYYY
oursler@kenyon.edu Miles Oursler NNNNNN
owen@wcs.uq.oz.au Owen Byrnes YYYYYN
P.Raffin@frcl.bull.fr Patrick Raffin YYYYYN
p00500@psilink.com John Ebert YYYYYY
paulf%cerebus.is@brooktree.com Paul Francis YYYYYN
paulg@alpha2.csd.uwm.edu Paul Gunderson YYYYYY
pcbsd@netcom.com Gregory Altman YYYYYN
PCOEN@DRUNIVAC.DREW.EDU Paul Coen YYYYYN
pe@pst.sh.sub.de Peter Steenken YYYYYY
pebly@vnet.IBM.COM Bob Pebly YYYYYN
peter@hprcl191.mayfield.hp.com peter huang YYYYYY
peter@pgeck.sub.org Peter Gahbler YYNYYY
peterb@telerama.lm.com Peter Berger NYNNNY
pfeifeg@spot.Colorado.EDU Gary Pfeifer Y--NN-
pfilsing@uoguelph.ca Paul Filsinger YYYYYY
ph@anweald.exnet.co.uk Patrick Herring YYYYYY
pjg30@eng.amdahl.com Paul John Gibbons YYYYYY
PMARKS@VAX1.UMKC.EDU Bud Marks pmarks@vax1.umkc.edu YYYY--
powelcr@anubis.network.com Chris R. Powell YYYYYN
PPARKER@TWSUVM.UC.TWSU.EDU Phil Parker YYYYYY
premont@iro.umontreal.ca Patrick Premont YYYYY-
pshuang@MIT.EDU Ping Huang YNNYYN
psyhtjs@unicorn.ccc.nottingham.ac.uk Tim Sneath YYYYYY
qraerus@kiba2.ericsson.se Hans Beckirus YYYNNY
quinn@phoenix.Princeton.EDU Michael J. Quinn YYYYYY
RAINER@sasowa.han.de Rainer Wantosch YYYYYN
raju@mcs.anl.gov Murali Raju YYYYYY
rbarnett@blkbox.COM Rick Barnett YYYYYN
rbf5812@belaero1.ca.boeing.com Ray French YYYYYY
rcw@rcw.sr.hp.com Richard Williams YYYYYN
rdippold@qualcomm.com Ron Dippold YY-YY-
reaume@server.uwindsor.ca Dan Reaume YYYYYY
reinhard@ifki50.informatik.fh-muenchen.de Reinhard Schuerer NYYYYY
rene@math.fu-berlin.de Rene Mueller YYYYYY
revu@midway.uchicago.edu Sendhil Revuluri NNNNNY
rhd@home.interaccess.com Rich Derr YYYYNN
rhynes@fox.nstn.ns.ca Ross D. Hynes YYYYYY
richard@corixia.demon.co.uk Richard Ashton YYYYYY
rick@bcm.tmc.edu Richard Miller NYNYNN
rickert@cs.niu.edu Neil Rickert NNNNNY
rlr@hal.com Randall Raemon YYYYYY
RMG8909@UTARLG.UTA.EDU Bob Geisel YYYYYY
robert.howard@matd.gatech.edu Robert L. Howard Y--YYY
robert@ireq-ht.hydro.qc.ca Robert Meunier YYYYYY
ROBERTSON@PHYSC3.BYU.EDU James F Robertson YYYYYY
roe2@midway.uchicago.edu Greg Roelofs YYYYYN
roelle@uars_mag.jhuapl.edu Curtis Roelle YYYYYY
rofische@iiic.ethz.ch Roman Fischer YYYYYY
rogerd@crl.com Roger D. Niclas YYYYYN
rolfe@ldp.com Rolfe Tessem YYYYYY
rommel@ars.muc.de Kai Uwe Rommel NYYYYN
rpr@oce.nl Rob Prikanowski YYYYY-
rswai1@monu6.cc.monash.edu.au Ron Wail YYYYYY
rturner@Newbridge.COM Robert Turner YYYYYN
s106275@ee.tut.fi Anssi Saari YYYYYY
sam.white@metrokc.gov Saluel H. White YYYYYY
sanjay@cs.columbia.edu Sanjay Aiyagari YYYYYY
sasmob@sas.com Mark C. Burhans YYYYYY
sbutler@hpbs548.boi.hp.com Sylvan Butler YYNYYN
schaefer@calle2.e.open.de Christian Schaefer YNNYYY
schoepf@isis.wu-wien.ac.at Oskar Schoepf YYYYYY
Scott.Marks@lambada.oit.unc.edu YYNYYY
sdarsey@metronet.com Steve Darsey YYYYYY
sf@arinc.com Steve Friedman NNNNNY
sferris@math.macalstr.edu Scott M. Ferris YYYYYY
shaneh@netcom.com Shane Hartman NNNNNY
sheilah@wam.umd.edu Sheila Herndon Y-----
shivaji@Virginia.edu NNNNNY
sholford@sirius.uvic.ca Stephen F. Holford YYY--Y
sidbury@cs.uofs.edu Dick Sidbury YYYYYY
sim@necsy.it Marco Silvestri YYYYYY
Singlis@bcde.demon.co.uk Steven Inglis YYYYYY
sip1@midway.uchicago.edu Timothy F. Sipples YYYYY-
sk001sp@unidui.uni-duisburg.de Martin Spott ---Y--
SL859@cc.usu.edu Raymond Bingham Y-----
slumos@nevada.edu STEVE LUMOS YNYYYN
smarry@turing.toronto.edu Marc Moorcroft NNNNNY
smtplink%Katz.E_at_Bull-MA30-TDS@ma02q.bull.com Edouard Katz YYYYYY
snmiller@mmm.com Shawn N. Miller YYYYYY
somervi@cs.pdx.edu Jeffrey Somerville YYYYYY
spves@post.nlh.no YYYYYN
srogers@tad.eds.com Steve Rogers NNNNNN
ssislett@csn.org Scott Lett YYYYYN
stainles@bga.com Dwight Brown NNNNNY
stephen@digitech.co.nz Stephen Worthington YYYYYN
stephens@vnet.IBM.COM Alan Stephens YYYYYY
Steve.King@comlab.oxford.ac.uk Steve King YYYYYY
Steve@cader.demon.co.uk Stephen Marsh YYYYYY
steve@molly.dny.rockwell.com Steven A. Robenalt YYYYYY
sthiagar@nickel.ucs.indiana.edu Raja Thiagarajan YYYYYY
strike@steam.rome.NY.US Timothy B. Bowser YYYYYY
Stu@nemesis.wimsey.com Stuart Smith YYYYYY
STURM@uni-muenster.de Eberhard Sturm YYY--Y
svs6@columbia.edu Stephen Stibler YYYYYN
sward+@CMU.EDU David Sward NNNNNY
swkgohcp@leonis.nus.sg Alvin Tan YYYYYN
swt@garble.affinity.mn.org Stephen W. Thomas YYYYYY
szherod@othello.ucdavis.edu Jim Herod YYYYYY
s_deisenh@main01.rz.uni-ulm.de Johannes Deisenhofer YYYYYN
tajones@cs.utexas.edu Timothy Allen Jones YYYYYN
tas@dadstoy.jpunix.com Terry Stockdale YYYYYY
TAT@yvax.byu.edu Todd Turnblom YYYYYY
tbgamb@iglou.com Tom Gambill YYYYYN
tedc@cs.ubc.ca Ted Chen YYYYYY
tennesen@mars.dgrc.doc.ca Andy Tenne-Sens YYYYYY
tennis@warp66.nde.swri.edu Richard Tennis YYYYYY
tep@nwg.nectec.or.th Pornthep Narula YYYYYY
TERKUILE@eig.unige.ch Ernest J.W. ter Kuile YYYY--
terry@TYRELL.NET Terry McDill YYYNYY
tfriis@imada.ou.dk Torben Friis YYYYYY
thewoz!rswill@netcom.com R Scott Williams YYYYY-
Thomas.Berge@studorg.uio.no Thomas Berge (Thomas.Berge@studorg.uio.n YYNYYY
thomas@geac.co.nz Thomas Beagle YYYYYN
thomasez@dhhalden.no Thomas Lundquist YYYYYY
thompson@atlas.socsci.umn.edu T. Scott Thompson YYYYYY
tim@derwent.co.uk Tim Morley YYYYYY
tim@nanometrics.on.ca Tim Hayman YYYYY-
timur@seas.gwu.edu Timur Tabi YYYYYN
ting@ATB.Teradyne.COM Peter Ting YYY--Y
tmeadow@bearriver.com Anthony Meadow -YYY--
tmg@wg.saar.de Tilman Mueller-Gerbes YYYYYN
tom@longs.lance.colostate.edu Tom Aurand YYYYYN
tombros@ifi.unizh.ch Dimitrios Tombros YYYYYY
tomc@kendeco.com Tom Cross YYYYY-
tomdunn@vnet.IBM.COM Tom Dunn YYYYYY
Tom_Rubinstein-CEGR01@email.mot.com Tom Rubinstein ---YYY
trall@almaden.ibm.com Tony Rall YYYYYY
tsbogend@bigbug.franken.de Thomas Bogendoerfer YYYYYY
tyers@acs.ucalgary.ca Bruce R. Tyers YYYYYY
vaps2km@acme.gatech.edu Kenneth D. Merry YYYYYY
venky@rice.edu Venky Veeraraghavan NYYYYY
vhuy-p@babel.ee.up.ac.za Pierre van Huyssteen YYYYYY
vkjoshi@cs.vu.nl Vivek Joshi YYYYYY
w-chase@tamu.edu William L. Chase YYYYYY
wallace@glen-ellyn.iit.edu Ralph W. Wallace YYYYYY
walraven@eo.com Ewout Walraven NNNYYY
wang@cedar.nrl.navy.mil Dennis Wang YYYYYY
WARD@ernie.van.forintek.ca Ward F. Bush YYYYYY
wardb@scico1.chchp.ac.nz Bruce Ward -YYYY-
ware@clipper.ens.fr Cedric Ware -YY---
we39110@is1.bfu.vub.ac.be DE SCHEEMAECKER MARC YYNYYN
we44478@is1.bfu.vub.ac.be Ringo De Smet YYYYYN
we45194@is1.bfu.vub.ac.be Herbert Baerten Y-----
weber@rhrk.uni-kl.de Christoph Weber-Fahr YYYYYY
weberdd@macc.wisc.edu David Devereaux-Weber YYYYYY
wesb@dermit.uuisis.org Wesley Boisvert YYYYYY
west@esd.dl.nec.com Mike West YY-YY-
wherrera@lookout.com William Herrera YYYYYN
whitmire@netcom.com Scott A. Whitmire (whitmire@netcom.com) YYYYYY
whkc100@cus.cam.ac.uk Kenneth Chan YYNNNY
whostler@procy.gi.com Wade Hostler NNNNNN
widow@camelot.bradley.edu Shaun Burnett YYYYYY
will@austin.ibm.com Will Fiveash YYYYYY
WINDISCH%DHDIBM1.BITNET@vm.gmd.de Eric R. Windisch YYYYYY
wjgjr@MIT.EDU William J. Gehrke, Jr. YYYYYY
wjh@cis.ufl.edu Wayne J. Hyde YYYYYY
wjw@eb.ele.tue.nl Willem Jan Withagen YYYYY-
wmaton@calvin.chin.doc.ca William Maton YYYYYN
woc8r@virginia.edu YYYYYY
worsley@server.uwindsor.ca Brian Worsley Y-YYYN
Yadallee@gallif.ersys.edmonton.ab.ca Dave Shariff Yadallee YYYYYY
zbecka@Newbridge.COM Zdenek Becka YYYYYY
Votes in error
------------------------------------------------------------------------------
adept@cs.wisc.edu Mark McCullough
! No vote statement in message
admin!admin@relay.NL.net Wanne de Kler
! Invalid address
button@se01.wg2.waii.com Brian Button
! No vote statement in message
choia@athena.ecs.csus.edu Alex Choi
! No ballot
Chris_Marble@hmc.edu Chris Marble
! No vote statement in message
DEEL@CPVA.SAIC.COM
! No vote statement in message
josco@gaia.arc.nasa.gov Joseph Coughlan
! No ballot
lmah@ee.ualberta.ca Lester Stephen Mah
! No ballot
markj@saintjoe.edu
! No ballot
mdk@sni.co.uk Michael King
! No ballot
smithgr@nag.cs.Colorado.EDU Gregory P. Smith (smithgr@cs.colorado.edu)
! No vote statement in message
U23783%UICVM@UIC.EDU Daniel Sachs 708-833-3763
! No ballot
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu | adequately be explained by stupidity.
"The difference between baseball and politics is that, in baseball, if you
get caught stealing, you're out!" -- Ed Shanks
USENET FACT: Kill File
A set of filters setup to determine which user's posts will be read/downloaded or ignored.
NewsDemon® is a trademark of K&L Technologies, Inc.
2001 - 2012 © Copyright NewsDemon.com