• Your Trusted Usenet Provider
  • Secure, Private, Unlimited

Newsgroups Main » Newsgroups Directory » Computers - OS and Platforms » IBM PC and Clones » Soundcard

General ( comp.sys.ibm.pc.soundcard )
 
From mfarah@ing.puc.cl Fri Nov  5 22:08:30 1993
Path: uunet!bounce-back
From: mfarah@ing.puc.cl (Miguel Farah F.)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.soundcard,comp.sys.ibm.pc.misc,comp.sys.ibm.pc.hardware,comp.sys.ibm.pc.hardware.misc,comp.os.msdos.programmer
Subject: RFD: comp.sys.ibm.pc.soundcard reorganization
Followup-To: news.groups
Date: 5 Nov 1993 20:15:38 -0500
Organization: ing.puc.cl
Lines: 105
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Expires: 6 Dec 1993 00:00:00 GMT
Message-ID: <comp.sys.ibm.pc.soundcard-reorg-RFD1@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4232 news.groups:86864 comp.sys.ibm.pc.soundcard:25238 comp.sys.ibm.pc.misc:43707 comp.sys.ibm.pc.hardware:88270 comp.sys.ibm.pc.hardware.misc:63 comp.os.msdos.programmer:31441

This is a Request For Discusion regarding the reorganization of the
comp.sys.ibm.pc.soundcard newsgroup.

It is a well known fact that the current soundcard newsgroup has a very
high traffic level, and is becoming chaotic. This is why I suggest the
following reorganization of comp.sys.ibm.pc.soundcard:

#1: creation of the newsgroup "comp.sys.ibm.pc.hardware.soundcard.advocacy"
#2: creation of the newsgroup "comp.sys.ibm.pc.hardware.soundcard.announce"
#3: creation of the newsgroup "comp.sys.ibm.pc.hardware.soundcard.help"
#4: creation of the newsgroup "comp.sys.ibm.pc.hardware.soundcard.misc"
#5: creation of the newsgroup "comp.sys.ibm.pc.hardware.soundcard.programming"

The newsgroup comp.sys.ibm.pc.soundcard was created in order to reduce
the traffic level in comp.sys.ibm.pc.hardware - now that it's been
split, the most logical step is moving comp.sys.ibm.pc.soundcard back
to the hardware hierarchy.

There has been a lot of dispute as to whether the soundcard group should
be split according to company or topic. While the current traffic levels
may indicate the need for a group based on an individual product (and we
ALL know which one...), it is essential that the naming convention be
chosen in a way that is relatively unaffectable by market trends. For
example, a company might be bought out, and new standards might arise,
but the topics concerning soundcards in general will not change.


Note: in the following descriptions, "*" is understood to mean
      "comp.sys.ibm.pc.hardware.soundcard".

      NEWSGROUP      DESCRIPTION
      ~~~~~~~~~      ~~~~~~~~~~~

   1) *.advocacy     discussing the advantages and disadvantages of the
                     different PC soundcard models

      The very high level of discussion about which card is the best
      makes strongly advisable to create this newsgroup; it will be for
      comparisons between different soundcard models and not for flames.

   2) *.announce     important announcements about PC soundcards
      (moderated)

      This newsgroup -which will be moderated- will be for important
      announcements concerning PC soundcards (new drivers for some card,
      new model released, etc.). The generic FAQL and the brand-specific
      ones should be published here periodically. Followups should be
      directed to *.misc.

      ****** THERE ISN'T A MODERATOR YET - CANDIDATES WANTED ******

   3) *.help         help requests related to PC soundcards

      This newsgroup will be for help requests and their answers
      concerning problems installing/using PC soundcards (how to physically
      put them on the computer, solving DMA/IRQ conflicts, asking for newer
      drivers, how to set-up them, how to make them work under some
      application, etc.).
      Discussions about problems programming a soundcard should be kept
      in the .programming group and not cross-posted here.

   4) *.misc         miscellaneous topics about PC soundcards

      This newsgroup will supersede comp.sys.ibm.pc.soundcard.
      It will cover every PC soundcard topic that is not covered by the
      other newsgroups.
      Once this newsgroup is created, comp.sys.ibm.pc.soundcard shall be
      rmgrouped after three (3) months.

   5) *.programming  programming PC souncards

      This newsgroup will cover topics related to how to program the
      different PC soundcards.

 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Newsgroup creation votes should be separated and voted in parallel:

BALLOT ENTRY #1: addition of the subgroup ".advocacy"    to the soundcard
                 hierarchy.
BALLOT ENTRY #2: addition of the subgroup ".announce"    to the soundcard
                 hierarchy.
BALLOT ENTRY #3: addition of the subgroup ".help"        to the soundcard
                 hierarchy.
BALLOT ENTRY #4: addition of the subgroup ".misc"        to the soundcard 
                 hierarchy.
BALLOT ENTRY #5: addition of the subgroup ".programming" to the soundcard
                 hierarchy.

[[ news.announce.newgroups moderator's note: 
   THIS IS NOT A VOTE.  THE ACTUAL VOTE WILL NOT BE FOR SEVERAL WEEKS.
                        -- tale ]]

Notes:
 - remember that you can vote YES to some groups and NO to other ones
   *independently* from each other. For example, if you were interested
   only in a split by company, you could vote YES to the ".advocacy",
   ".announce" and ".misc" groups and vote NO to the ".help" and
   ".programming" groups.
 - *during* the RFD we should discuss if the soundcard hierarchy should
   return or not to the hardware hierarchy.
-- 
MIGUEL FARAH F.           // "Trust me - I know what I'm doing."
mfarah@malloco.ing.puc.cl //  - Sledge Hammer
#include <disclaimer.h>   //

From mfarah@ing.puc.cl Tue Nov 30 18:54:42 1993
Path: uunet!bounce-back
From: mfarah@ing.puc.cl (Miguel Farah F.)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.misc,comp.sys.ibm.pc.hardware.misc,comp.sys.ibm.pc.soundcard,comp.os.msdos.programmer,comp.os.ms-windows.setup
Subject: 2nd RFD: comp.sys.ibm.pc.soundcard reorganization
Followup-To: news.groups
Date: 30 Nov 1993 12:55:30 -0500
Organization: ing.puc.cl
Lines: 103
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <2dg1eiINN6br@rodan.UU.NET>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4330 news.groups:88930 comp.sys.ibm.pc.misc:44525 comp.sys.ibm.pc.hardware.misc:598 comp.sys.ibm.pc.soundcard:27885 comp.os.msdos.programmer:32448 comp.os.ms-windows.setup:8125

This is the second Request For Discusion regarding the reorganization
of the comp.sys.ibm.pc.soundcard newsgroup.

It is a well known fact that the current soundcard newsgroup has a very
high traffic level, and is becoming chaotic. This is why I suggest the
following reorganization of comp.sys.ibm.pc.soundcard:

#1: creation of the newsgroup "comp.sys.ibm.pc.soundcard.advocacy"
#2: creation of the newsgroup "comp.sys.ibm.pc.soundcard.announce"
#3: creation of the newsgroup "comp.sys.ibm.pc.soundcard.help"
#4: creation of the newsgroup "comp.sys.ibm.pc.soundcard.misc" 
#5: creation of the newsgroup "comp.sys.ibm.pc.soundcard.programmer"

If comp.sys.ibm.pc.soundcard.misc is created, comp.sys.ibm.pc.soundcard
will be removed in three months from its creation.

There has been a lot of dispute as to whether the soundcard group should
be split according to company or topic. While the current traffic levels
may indicate the need for a group based on an individual product (and we
ALL know which one...), it is essential that the naming convention be
chosen in a way that is relatively unaffectable by market trends. For
example, a company might be bought out, and new standards might arise,
but the topics concerning soundcards in general will not change.


Note: in the following descriptions, "*" is understood to mean
      "comp.sys.ibm.pc.soundcard".

      NEWSGROUP      DESCRIPTION
      ~~~~~~~~~      ~~~~~~~~~~~

   1) *.advocacy     discussing the advantages and disadvantages of the
                     different PC soundcard models

      The very high level of discussion about which card is the best
      makes strongly advisable to create this newsgroup; it will be for
      comparisons between different soundcard models and not for flames.

   2) *.announce     important announcements about PC soundcards
      (moderated)

      This newsgroup -which will be moderated- will be for important
      announcements concerning PC soundcards (new drivers for some card,
      new model released, etc.). The generic FAQL and the brand-specific
      ones should be published here periodically. Followups should be
      directed to *.misc.

      ****** THERE ISN'T A MODERATOR YET - CANDIDATES WANTED ******

   3) *.help         help requests related to PC soundcards

      This newsgroup will be for help requests and their answers
      concerning problems installing/using PC soundcards (how to physically
      put them on the computer, solving DMA/IRQ conflicts, asking for newer
      drivers, how to set-up them, how to make them work under some
      application, etc.).
      Discussions about problems programming a soundcard should be kept
      in the .programmer group and not cross-posted here.

   4) *.misc         miscellaneous topics about PC soundcards

      This newsgroup will supersede comp.sys.ibm.pc.soundcard.
      It will cover every PC soundcard topic that is not covered by the
      other newsgroups.
      Once this newsgroup is created, comp.sys.ibm.pc.soundcard shall be
      rmgrouped after three (3) months.

   5) *.programmer  programming PC souncards

      This newsgroup will cover topics related to how to program the
      different PC soundcards.
      (The name in the first RFD was .programming, but it was suggested
      to have it changed).


 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Newsgroup creation votes should be separated and voted in parallel:

BALLOT ENTRY #1: addition of the subgroup ".advocacy"   to the soundcard
                 hierarchy.
BALLOT ENTRY #2: addition of the subgroup ".announce"   to the soundcard
                 hierarchy.
BALLOT ENTRY #3: addition of the subgroup ".help"       to the soundcard
                 hierarchy.
BALLOT ENTRY #4: addition of the subgroup ".misc"       to the soundcard 
                 hierarchy.
BALLOT ENTRY #5: addition of the subgroup ".programmer" to the soundcard
                 hierarchy.

Notes:
 - remember that you can vote YES to some groups and NO to other ones
   *independently* from each other. For example, if you were interested
   only in a split by company, you could vote YES to the ".advocacy",
   ".announce" and ".misc" groups and vote NO to the ".help" and
   ".programmer" groups.
      
It is not time to vote yet.  Full voting instructions will come in a
future Call for Votes (CFV) article.
-- 
MIGUEL FARAH F.           // "Trust me - I know what I'm doing."
mfarah@malloco.ing.puc.cl //  - Sledge Hammer
#include <disclaimer.h>   //

From vincie@blaze.cs.jhu.edu Tue Mar 29 20:09:10 1994
Path: uunet!bounce-back
From: vincie@blaze.cs.jhu.edu (Michael Young Ko)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.soundcard,comp.sys.ibm.pc.hardware.misc
Subject: RFD: comp.sys.ibm.pc.soundcard reorganization
Followup-To: news.groups
Date: 29 Mar 1994 15:47:49 -0500
Organization: Computer Science Department, The Johns Hopkins University
Lines: 151
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <comp.sys.ibm.pc.soundcard-reorg-RFD1@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4843 news.groups:99431 comp.sys.ibm.pc.soundcard:41833 comp.sys.ibm.pc.hardware.misc:4423

The following RFD has been cross posted to news.annouce.newgroups, news.groups,
and comp.sys.ibm.pc.soundcard. Also, the follow up group will be the
news.groups.

Request For Discussion:

This is a formal Request For Discussion concerning the groups
comp.sys.ibm.pc.soundcard and the illegal group comp.sys.ibm.pc.soundcard.GUS.
This RFD is to remove the groups comp.sys.ibm.pc.soundcard.GUS and replace
comp.sys.ibm.pc.soundcard with the four following groups:
    comp.sys.ibm.pc.(hardware).soundcard.games
    comp.sys.ibm.pc.(hardware).soundcard.music
    comp.sys.ibm.pc.(hardware).soundcard.tech
    comp.sys.ibm.pc.(hardware).soundcard.advocacy

All of these groups will be unmoderated.

The purpose of having hardware in parentheses is the possible of placing
the soundcard group under the hardware hierarchy. This is mainly for
conforming to the other ibm pc hardware groups.

Charters for proposed groups:
   a) comp.sys.ibm.pc.(hardware).soundcard.games - Unmoderated discussion of
        using IBM-PC compatible games with a specific soundcard, resolving
        compatibility problems of a certain soundcard with a particular game,
        discussing campaigns at software groups to have more native
        soundcard support, questions if a particular game supports a certain
        soundcard, and questions on which soundcard is best for a particular
        game or all games in general.

   b) comp.sys.ibm.pc.(hardware).soundcard.music - Unmoderated discussion of
        software that plays back and record sound and music files, music
        formats such as WAV, VOC, MIDI, MOD, STM, 669, ULT, ROL, etc.,
        resolving problems with musical software, discussing which software
        or hardware is best for a particular musical or sound project, and 
	questions concerning sampling or sound patch making.

   c) comp.sys.ibm.pc.(hardware).soundcard.tech - Unmoderated discussion of
        questions concerning programming a particular soundcard, discussing
        hardware problems such as loss of sound from a particular channel,
        discussing the pros and cons of a particular sound generation scheme,
        questions on the compatibility of the soundcard to a particular
        computer type, operating system, and peripheral such as a CD-ROM
        drive, questions about the functionality of a particular soundcard,
        and resolving hardware problems.

   d) comp.sys.ibm.pc.(hardware).soundcard.advocacy - Unmoderated discussion
	of the pros and cons of soundcards in general. This discussion will
	possibly overlap some discussions on the other soundcard groups. Also
	reviews of soundcards and future opinions and tests of soundcards
	will be placed in this group to be discussed by the users. 

Justification:

        The sudden increase in the volume of messages posted to the group
        comp.sys.ibm.pc.soundcard has caused the suggestion of splitting the
        group to appear. Many users on the group have expressed interest
        in dividing the group because the topics listed on the group are
        varied tremendously. Having approximately 200+ new messages a day
	on this group is expensive to some users who must pay for the 
	receiving the usenet group based upon amount of information as well
	as paying for the amount of time needed to sort through all of the
	messages. Currently, a heated debate is present on the c.s.i.p.s
	group which is disrupting those users more interested in new software
	and problems. They have expressed concern that some are not able to 
        keep up with all of the traffic and decided that
        by splitting the group, this would allow them to read the messages
        relevant to their interests pertaining to their soundcard.

	The comp.sys.ibm.pc.soundcard.GUS is unrecognized usenet group
	throughout many news servers. Therefore, to avoid confusion and to
	reorganize the entire soundcard group, this illegal group must be
	eliminated. Many GUS users are satisfied with removing this group
	and using the four above mentioned subgroups.
	
	There was also concern about where this group should be located, under
        the comp.syd.ibm.pc hierarchy or comp.sys.ibm.pc.hardware hierarchy. 
	Most are flexible with the location of these groups. It is a matter 
	which is better in terms of an organizational point of view. By
        placing these groups under the hardware hierarchy, these groups will 
	be seven levels deep. Also, by leaving the split groups under the
	comp.sys.ibm.pc hierarchy, the transition would be less disrupting. 

Rationale:

        The idea of spliting the group was tossed around the c.s.i.p.s
	group many times. However, no action was ever taken. It is hoped
	that finally with the dramatic increase in messages, that this
	reorganization would make the group more efficient and easier to
	use. Questions had to be raised about add another group, a
	c.s.i.p.soundcard.GUS group which would handle all topics 
	specific to the Gravis Ultrasound card. Presently, a majority of
	messages on the group is concerned with this card. Now with the
	a 100 message increase because of a heated debate (flame war?)
	the rational users want the group to be split. This eventually let to
        a group discussion about splitting up the soundcard group based upon
        the particular cards discussed, such as the Ultrasound, Soundblaster,
        Pro Audio Spectrum, etc. However, further discussion revealed that a
        majority thought that such a split would be short term due to the
        possibility of an unexpected loss of interest in a particular product.
        Therefore, because of the prospect of new soundcards being released
        that would increase the number of messages to the group, the prospect
        of more pc users of becoming involved in the multimedia revolution,
        and the steadily increase in messages in this group, it was decided
        that the group should be split based upon the topics mentioned above.

        The games group was chosen because a great number of posts on the
        soundcard group are concerned with how to use a particular soundcard
        with a particular game and what soundcard is best to use with game.
        Many users were concerned that the group was overrun with posts
        concerning how to get a particular game to work with a particular
        soundcard. They had to try to sift through the 200+ message a day
        to look for non-game compatibility messages. Therefore,
        the music group was also chosen because the other large part of
        message is related to the production of music. These include what
        programs can use a particular music format, and what programs exist
        to create programs. Also, in this group is the topic of sounds
        such as digitizing sound bytes and songs. A separate group was not
        created because many of the problems and solutions concerning
        recording or playing back sounds is related to the music production
        scene. The tech section was chosen because many users occasionally
        have questions about the technical aspect of soundcard, such as
        the pros and cons on how a soundcard generates sounds. Also,
        any hardware problems and compatibility would be discussed. But
        most importantly, the advocacy group would handle the bulk of the
	soundcard debate and keep it away from those more concerned
	with games or music. Such a split would try to evenly distribute the
	messages throughout the sub groups. Most agree that sorting through
	50+ is cheaper and less time-consuming.

Schedule:

        These proposals have been discussed informally in the comp.sys.ibm.
        pc.soundcard group for the past five  weeks. I have decided to write
        the RFD to have the group split. I have been keeping count of
        the number of users in favor and against the proposal. Because of
        the vast majority of those in favor of splitting the group, I  have
        made the RFD request. The posting of this RFD will begin the
        discussion period lasting 21 days. The discussion will take
        place in news.groups. Do not vote on this RFD now.

        After the 21 days and/or there are no unresolvable points, a
        formal Call For Votes will be announced.


Michael Ko
-- 
 / ...the chances of getting picked up by another/     The Invincible      \
/ ship within those thirty seconds are 2 to the   /    vincie@cs.jhu.edu     \
\ power of 276709 to one against." - From The    \ Computer Science Depart. /
 \ Hitchhiker's Guide to the Galaxy - D. Adams   \ Johns Hopkins University/

From vincie@blaze.cs.jhu.edu Thu Apr  7 13:55:48 1994
Path: uunet!bounce-back
From: vincie@blaze.cs.jhu.edu (Michael Young Ko)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.soundcard,comp.sys.ibm.pc.hardware.misc
Subject: 2nd RFD: comp.sys.ibm.pc.soundcard reorganization
Followup-To: news.groups
Date: 6 Apr 1994 17:29:54 -0400
Organization: Computer Science Department, The Johns Hopkins University
Lines: 162
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <comp.sys.ibm.pc.soundcard-reorg-RFD2@uunet.uu.net>
References: <comp.sys.ibm.pc.soundcard-reorg-RFD1@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:4905 news.groups:100032 comp.sys.ibm.pc.soundcard:42942 comp.sys.ibm.pc.hardware.misc:4687

The following RFD has been cross posted to news.annouce.newgroups, news.groups,
and comp.sys.ibm.pc.soundcard. Also, the follow up group will be the
news.groups.

This is a revision of the RFD for this reorganzation posted about a week ago.

April 5, 1994

Request For Discussion:

This is a formal Request For Discussion concerning the groups
comp.sys.ibm.pc.soundcard and the illegal group comp.sys.ibm.pc.soundcard.GUS.
This RFD is to remove the groups comp.sys.ibm.pc.soundcard.GUS and replace
comp.sys.ibm.pc.soundcard with the four following groups:
    comp.sys.ibm.pc.soundcard.games
    comp.sys.ibm.pc.soundcard.music
    comp.sys.ibm.pc.soundcard.tech
    comp.sys.ibm.pc.soundcard.advocacy
    comp.sys.ibm.pc.soundcard.misc

All of these groups will be unmoderated.

Charters for proposed groups:
   a) comp.sys.ibm.pc.soundcard.games - Unmoderated discussion of
        using IBM-PC compatible games with a specific soundcard, resolving
        compatibility problems of a certain soundcard with a particular game,
        discussing campaigns at software groups to have more native
        soundcard support, questions if a particular game supports a certain
        soundcard, and questions on which soundcard is best for a particular
        game or all games in general.

   b) comp.sys.ibm.pc.soundcard.music - Unmoderated discussion of
        software that plays back and record sound and music files, music
        formats such as WAV, VOC, MIDI, MOD, STM, 669, ULT, ROL, etc.,
        resolving problems with musical software, discussing which software
        or hardware is best for a particular musical or sound project, and 
	questions concerning sampling or sound patch making.

   c) comp.sys.ibm.pc.soundcard.tech - Unmoderated discussion of
        questions concerning programming a particular soundcard, discussing
        hardware problems such as loss of sound from a particular channel,
        discussing the pros and cons of a particular sound generation scheme,
        questions on the compatibility of the soundcard to a particular
        computer type, operating system, and peripheral such as a CD-ROM
        drive, questions about the functionality of a particular soundcard,
        and resolving hardware problems.

   d) comp.sys.ibm.pc.soundcard.advocacy - Unmoderated discussion
	of the pros and cons of soundcards in general. This discussion will
	possibly overlap some discussions on the other soundcard groups. Also
	reviews of soundcards and future opinions and tests of soundcards
	will be placed in this group to be discussed by the users. 

   e) comp.sys.ibm.pc.soundcard.misc - Unmoderated discussion of topics
	concerning soundcard hardware and software that is outside of the
	above mentioned topics. These could include upcoming product release or
	updates for soundcard software. 

Justification:

        The sudden increase in the volume of messages posted to the group
        comp.sys.ibm.pc.soundcard has caused the suggestion of splitting the
        group to appear. Many users on the group have expressed interest
        in dividing the group because the topics listed on the group are
        varied tremendously. Having approximately 200+ new messages a day
	on this group is expensive to some users who must pay for the 
	receiving the usenet group based upon amount of information as well
	as paying for the amount of time needed to sort through all of the
	messages. Currently, a heated debate is present on the c.s.i.p.s
	group which is disrupting those users more interested in new software
	and problems. They have expressed concern that some are not able to 
        keep up with all of the traffic and decided that
        by splitting the group, this would allow them to read the messages
        relevant to their interests pertaining to their soundcard.

	The comp.sys.ibm.pc.soundcard.GUS is unrecognized usenet group
	throughout many news servers. Therefore, to avoid confusion and to
	reorganize the entire soundcard group, this illegal group must be
	eliminated. Many GUS users are satisfied with removing this group
	and using the four above mentioned subgroups.
	
	There was also concern about where this group should be located, under
        the comp.syd.ibm.pc hierarchy or comp.sys.ibm.pc.hardware hierarchy. 
	It has been decided to leave the soundcard subgroups under the
	former mentioned hierarchy to prevent any problems with news servers
	and provides with usenet groups with seven level names. Also, the
	transition would be less disturbing.

Rationale:

        The idea of spliting the group was tossed around the c.s.i.p.s
	group many times. However, no action was ever taken. It is hoped
	that finally with the dramatic increase in messages, that this
	reorganization would make the group more efficient and easier to
	use. Questions had to be raised about add another group, a
	c.s.i.p.soundcard.GUS group which would handle all topics 
	specific to the Gravis Ultrasound card. Presently, a majority of
	messages on the group is concerned with this card. Now with the
	a 100 message increase because of a heated debate (flame war?)
	the rational users want the group to be split. This eventually let to
        a group discussion about splitting up the soundcard group based upon
        the particular cards discussed, such as the Ultrasound, Soundblaster,
        Pro Audio Spectrum, etc. However, further discussion revealed that a
        majority thought that such a split would be short term due to the
        possibility of an unexpected loss of interest in a particular product.
        Therefore, because of the prospect of new soundcards being released
        that would increase the number of messages to the group, the prospect
        of more pc users of becoming involved in the multimedia revolution,
        and the steadily increase in messages in this group, it was decided
        that the group should be split based upon the topics mentioned above.

        The games group was chosen because a great number of posts on the
        soundcard group are concerned with how to use a particular soundcard
        with a particular game and what soundcard is best to use with game.
        Many users were concerned that the group was overrun with posts
        concerning how to get a particular game to work with a particular
        soundcard. They had to try to sift through the 200+ message a day
        to look for non-game compatibility messages. Therefore,
        the music group was also chosen because the other large part of
        message is related to the production of music. These include what
        programs can use a particular music format, and what programs exist
        to create programs. Also, in this group is the topic of sounds
        such as digitizing sound bytes and songs. A separate group was not
        created because many of the problems and solutions concerning
        recording or playing back sounds is related to the music production
        scene. The tech section was chosen because many users occasionally
        have questions about the technical aspect of soundcard, such as
        the pros and cons on how a soundcard generates sounds. Also,
        any hardware problems and compatibility would be discussed. But
        most importantly, the advocacy group would handle the bulk of the
	soundcard debate and keep it away from those more concerned
	with games or music. Finally, the misc group would be concerned with
	any topic or discussion outside of the above mentioned groups. This
	group is need to provide some kind of order in the other groups.
	Posting messages not really relevant to a particular group would cause
	an increase in traffic where it is not needed. As evident from other
	groups that have split, the misc section is used often. Possibly, by
	posting to the misc group, the message could be sent to the proper
	subgroup.Such a split would try to evenly distribute the
	messages throughout the sub groups. Most agree that sorting through
	50+ is cheaper and less time-consuming.

Schedule:

        These proposals have been discussed informally in the comp.sys.ibm.
        pc.soundcard group for the past six weeks. I have decided to write
        the 1st RFD, as well as this revision, to have the group split. I have
	been keeping count of the number of users in favor and against the 
	proposal. Because of the vast majority of those in favor of splitting
	the group, I have made this RFD request and revision. The posting of
	this 2nd RFD will begin a new discussion period lasting 21 days. The 
	discussion will take place in news.groups. Do not vote on this RFD now.

        After the 21 days and/or there are no unresolvable points, a
        formal Call For Votes will be announced.

Michael Ko
-- 
 / ...the chances of getting picked up by another/     The Invincible      \
/ ship within those thirty seconds are 2 to the   /    vincie@cs.jhu.edu     \
\ power of 276709 to one against." - From The    \ Computer Science Depart. /
 \ Hitchhiker's Guide to the Galaxy - D. Adams   \ Johns Hopkins University/

From asolovay@geoworks.com Wed May 11 14:52:46 1994
Path: uunet!bounce-back
From: asolovay@geoworks.com (Andrew Solovay)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.soundcard
Subject: CFV: comp.sys.ibm.pc.soundcard reorganization
Followup-To: poster
Date: 9 May 1994 19:10:13 -0400
Organization: Usenet Volunteer Votetakers (UVV)
Lines: 213
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Expires: 31 May 1994 00:00:00 GMT
Message-ID: <comp.sys.ibm.pc.soundcard-reorg-CFV1@uunet.uu.net>
Reply-To: votes@geoworks.com (Andrew Solovay's vote-taking alias)
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:5038 news.groups:103106 comp.sys.ibm.pc.soundcard:47682

                     FIRST CALL FOR VOTES (of 2)
           unmoderated group comp.sys.ibm.pc.soundcard.tech
          unmoderated group comp.sys.ibm.pc.soundcard.music
          unmoderated group comp.sys.ibm.pc.soundcard.games
         unmoderated group comp.sys.ibm.pc.soundcard.advocacy
unmoderated group comp.sys.icm.pc.soundcard.misc (replaces comp.sys.ibm.pc.soundcard)



Newsgroups line:
comp.sys.ibm.pc.soundcard.tech	Technical questions about pc soundcards.
comp.sys.ibm.pc.soundcard.music	Music and sound questions using soundcards.
comp.sys.ibm.pc.soundcard.games	Questions about using soundcards with games.
comp.sys.ibm.pc.soundcard.advocacy	Advocacy for a particular soundcard.
comp.sys.icm.pc.soundcard.misc	Soundcards in general.

Votes must be received by 29:59:59 GMT, 30 May 1994.

This vote is being conducted by a neutral third party.  For voting
questions only contact Andrew Solovay <asolovay@geoworks.com>.  For
questions about the proposed group contact Michael Young Ko
<vincie@cs.jhu.edu>.

The vote-taker will post each CFV to the GUS Daily Digest at
<gus-general@mail.orst.edu> shortly after it is posted to
news.announce.newsgroups. He will send an abridged RESULT posting
(without the full list of voters) to the mailing list after voting
ends; the full RESULTs will be posted to all the newsgroups where the
CFV was posted.

CHARTERS

comp.sys.ibm.pc.soundcard.games 

    Unmoderated discussion of using IBM-PC compatible games with a
    specific soundcard, resolving compatibility problems of a certain
    soundcard with a particular game, discussing campaigns at software
    groups to have more native soundcard support, questions if a
    particular game supports a certain soundcard, and questions on
    which soundcard is best for a particular game or all games in
    general.

comp.sys.ibm.pc.soundcard.music 

    Unmoderated discussion of software that plays back and record
    sound and music files, music formats such as WAV, VOC, MIDI, MOD,
    STM, 669, ULT, ROL, etc., resolving problems with musical
    software, discussing which software or hardware is best for a
    particular musical or sound project, and questions concerning
    sampling or sound patch making.

comp.sys.ibm.pc.soundcard.tech 

    Unmoderated discussion of questions concerning programming a
    particular soundcard, discussing hardware problems such as loss of
    sound from a particular channel, discussing the pros and cons of a
    particular sound generation scheme, questions on the compatibility
    of the soundcard to a particular computer type, operating system,
    and peripheral such as a CD-ROM drive, questions about the
    functionality of a particular soundcard, and resolving hardware
    problems.

comp.sys.ibm.pc.soundcard.advocacy

    Unmoderated discussion of the pros and cons of soundcards in
    general. This discussion will possibly overlap some discussions on
    the other soundcard groups. Also reviews of soundcards and future
    opinions and tests of soundcards will be placed in this group to
    be discussed by the users.

comp.sys.ibm.pc.soundcard.misc

    Unmoderated discussion of topics concerning soundcard hardware and
    software that is outside of the above mentioned topics. These
    could include upcoming product release or updates for soundcard
    software. (This group would supersede the existing group
    comp.sys.ibm.pc.soundcard.)

JUSTIFICATION:

        The sudden increase in the volume of messages posted to the group
        comp.sys.ibm.pc.soundcard has caused the suggestion of splitting the
        group to appear. Many users on the group have expressed interest
        in dividing the group because the topics listed on the group are
        varied tremendously. Having approximately 200+ new messages a day
        on this group is expensive to some users who must pay for the 
        receiving the usenet group based upon amount of information as well
        as paying for the amount of time needed to sort through all of the
        messages. Currently, a heated debate is present on the c.s.i.p.s
        group which is disrupting those users more interested in new software
        and problems. They have expressed concern that some are not able to 
        keep up with all of the traffic and decided that
        by splitting the group, this would allow them to read the messages
        relevant to their interests pertaining to their soundcard.

        The comp.sys.ibm.pc.soundcard.GUS is unrecognized usenet group
        throughout many news servers. Therefore, to avoid confusion and to
        reorganize the entire soundcard group, this illegal group must be
        eliminated. Many GUS users are satisfied with removing this group
        and using the four above mentioned subgroups.
        
        There was also concern about where this group should be located, under
        the comp.syd.ibm.pc hierarchy or comp.sys.ibm.pc.hardware hierarchy. 
        It has been decided to leave the soundcard subgroups under the
        former mentioned hierarchy to prevent any problems with news servers
        and provides with usenet groups with seven level names. Also, the
        transition would be less disturbing.

RATIONALE:

        The idea of spliting the group was tossed around the c.s.i.p.s
        group many times. However, no action was ever taken. It is hoped
        that finally with the dramatic increase in messages, that this
        reorganization would make the group more efficient and easier to
        use. Questions had to be raised about add another group, a
        c.s.i.p.soundcard.GUS group which would handle all topics 
        specific to the Gravis Ultrasound card. Presently, a majority of
        messages on the group is concerned with this card. Now with the
        a 100 message increase because of a heated debate (flame war?)
        the rational users want the group to be split. This eventually let to
        a group discussion about splitting up the soundcard group based upon
        the particular cards discussed, such as the Ultrasound, Soundblaster,
        Pro Audio Spectrum, etc. However, further discussion revealed that a
        majority thought that such a split would be short term due to the
        possibility of an unexpected loss of interest in a particular product.
        Therefore, because of the prospect of new soundcards being released
        that would increase the number of messages to the group, the prospect
        of more pc users of becoming involved in the multimedia revolution,
        and the steadily increase in messages in this group, it was decided
        that the group should be split based upon the topics mentioned above.

        The games group was chosen because a great number of posts on the
        soundcard group are concerned with how to use a particular soundcard
        with a particular game and what soundcard is best to use with game.
        Many users were concerned that the group was overrun with posts
        concerning how to get a particular game to work with a particular
        soundcard. They had to try to sift through the 200+ message a day
        to look for non-game compatibility messages. Therefore,
        the music group was also chosen because the other large part of
        message is related to the production of music. These include what
        programs can use a particular music format, and what programs exist
        to create programs. Also, in this group is the topic of sounds
        such as digitizing sound bytes and songs. A separate group was not
        created because many of the problems and solutions concerning
        recording or playing back sounds is related to the music production
        scene. The tech section was chosen because many users occasionally
        have questions about the technical aspect of soundcard, such as
        the pros and cons on how a soundcard generates sounds. Also,
        any hardware problems and compatibility would be discussed. But
        most importantly, the advocacy group would handle the bulk of the
        soundcard debate and keep it away from those more concerned
        with games or music. Finally, the misc group would be concerned with
        any topic or discussion outside of the above mentioned groups. This
        group is need to provide some kind of order in the other groups.
        Posting messages not really relevant to a particular group would cause
        an increase in traffic where it is not needed. As evident from other
        groups that have split, the misc section is used often. Possibly, by
        posting to the misc group, the message could be sent to the proper
        subgroup.Such a split would try to evenly distribute the
        messages throughout the sub groups. Most agree that sorting through
        50+ is cheaper and less time-consuming.


HOW TO VOTE

Erase everything above the top "-=-=-=-" line and erase everything
below the bottom "-=-=-=-" line.  Do not erase anything between these
lines and do not change the group names.

Give your 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.  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.

Then mail the ballot to:    votes@geoworks.com
Just Replying to this message should work, but check the "To:" line.



-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
comp.sys.ibm.pc.soundcard reorganization Ballot    <SOUND-0001> (Don't remove this marker)

Give your real name here:

[Your Vote]  Group
-----------------------------------------------------------------------
[         ]  comp.sys.ibm.pc.soundcard.tech
[         ]  comp.sys.ibm.pc.soundcard.music
[         ]  comp.sys.ibm.pc.soundcard.games
[         ]  comp.sys.ibm.pc.soundcard.advocacy
[         ]  comp.sys.icm.pc.soundcard.misc (replaces comp.sys.ibm.pc.soundcard)
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-



Anything else may be rejected by the automatic vote counting program.  The
votetaker will respond to your received ballots with a personal acknowledge-
ment by mail - if you do not receive one within several days, try again.
It's your responsibility to make sure your vote is registered correctly.

Each person may vote only once, no matter how many accounts he or she
may have. Also, only one ballot will be accepted from any account, no
matter how many people may share it. If more than one vote is received
>from any person or any account, only the last vote received will be
counted.

Addresses and votes of all voters will be published in the final
voting results list. All ballots received are kept in the UVV archives
(including "cancelled" and invalid ballots). The vote files are made
available to the moderator of news.announce.newgroups on request. They
may also, at the discretion of the UVV, be made more widely available
if there is a controversy concerning the vote.

From asolovay@geoworks.com Mon May 23 15:56:55 1994
Path: uunet!bounce-back
From: asolovay@geoworks.com (Andrew Solovay)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.soundcard
Subject: 2nd CFV: comp.sys.ibm.pc.soundcard reorganization
Supersedes: <comp.sys.ibm.pc.soundcard-reorg-CFV1@uunet.uu.net>
Followup-To: poster
Date: 20 May 1994 14:48:16 -0400
Organization: Usenet Volunteer Votetakers (UVV)
Lines: 234
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Expires: 31 May 1994 00:00:00 GMT
Message-ID: <comp.sys.ibm.pc.soundcard-reorg-CFV2@uunet.uu.net>
References: <comp.sys.ibm.pc.soundcard-reorg-RFD1@uunet.uu.net> <comp.sys.ibm.pc.soundcard-reorg-CFV1@uunet.uu.net>
Reply-To: votes@geoworks.com (Andrew Solovay's vote-taking alias)
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:5121 news.groups:104419 comp.sys.ibm.pc.soundcard:49124

                     LAST CALL FOR VOTES (of 2)
           unmoderated group comp.sys.ibm.pc.soundcard.tech
          unmoderated group comp.sys.ibm.pc.soundcard.music
          unmoderated group comp.sys.ibm.pc.soundcard.games
         unmoderated group comp.sys.ibm.pc.soundcard.advocacy
unmoderated group comp.sys.icm.pc.soundcard.misc (replaces comp.sys.ibm.pc.soundcard)



Newsgroups line:
comp.sys.ibm.pc.soundcard.tech  Technical questions about pc soundcards.
comp.sys.ibm.pc.soundcard.music Music and sound questions using soundcards.
comp.sys.ibm.pc.soundcard.games Questions about using soundcards with games.
comp.sys.ibm.pc.soundcard.advocacy      Advocacy for a particular soundcard.
comp.sys.icm.pc.soundcard.misc  Soundcards in general.

Votes must be received by 29:59:59 GMT, 30 May 1994.

This vote is being conducted by a neutral third party.  For voting
questions only contact Andrew Solovay <asolovay@geoworks.com>.  For
questions about the proposed group contact Michael Young Ko
<vincie@cs.jhu.edu>.

The vote-taker will post each CFV to the GUS Daily Digest at
<gus-general@mail.orst.edu> shortly after it is posted to
news.announce.newsgroups. He will send an abridged RESULT posting
(without the full list of voters) to the mailing list after voting
ends; the full RESULTs will be posted to all the newsgroups where the
CFV was posted.

CHARTERS

comp.sys.ibm.pc.soundcard.games 

    Unmoderated discussion of using IBM-PC compatible games with a
    specific soundcard, resolving compatibility problems of a certain
    soundcard with a particular game, discussing campaigns at software
    groups to have more native soundcard support, questions if a
    particular game supports a certain soundcard, and questions on
    which soundcard is best for a particular game or all games in
    general.

comp.sys.ibm.pc.soundcard.music 

    Unmoderated discussion of software that plays back and record
    sound and music files, music formats such as WAV, VOC, MIDI, MOD,
    STM, 669, ULT, ROL, etc., resolving problems with musical
    software, discussing which software or hardware is best for a
    particular musical or sound project, and questions concerning
    sampling or sound patch making.

comp.sys.ibm.pc.soundcard.tech 

    Unmoderated discussion of questions concerning programming a
    particular soundcard, discussing hardware problems such as loss of
    sound from a particular channel, discussing the pros and cons of a
    particular sound generation scheme, questions on the compatibility
    of the soundcard to a particular computer type, operating system,
    and peripheral such as a CD-ROM drive, questions about the
    functionality of a particular soundcard, and resolving hardware
    problems.

comp.sys.ibm.pc.soundcard.advocacy

    Unmoderated discussion of the pros and cons of soundcards in
    general. This discussion will possibly overlap some discussions on
    the other soundcard groups. Also reviews of soundcards and future
    opinions and tests of soundcards will be placed in this group to
    be discussed by the users.

comp.sys.ibm.pc.soundcard.misc

    Unmoderated discussion of topics concerning soundcard hardware and
    software that is outside of the above mentioned topics. These
    could include upcoming product release or updates for soundcard
    software. (This group would supersede the existing group
    comp.sys.ibm.pc.soundcard.)

JUSTIFICATION:

        The sudden increase in the volume of messages posted to the group
        comp.sys.ibm.pc.soundcard has caused the suggestion of splitting the
        group to appear. Many users on the group have expressed interest
        in dividing the group because the topics listed on the group are
        varied tremendously. Having approximately 200+ new messages a day
        on this group is expensive to some users who must pay for the 
        receiving the usenet group based upon amount of information as well
        as paying for the amount of time needed to sort through all of the
        messages. Currently, a heated debate is present on the c.s.i.p.s
        group which is disrupting those users more interested in new software
        and problems. They have expressed concern that some are not able to 
        keep up with all of the traffic and decided that
        by splitting the group, this would allow them to read the messages
        relevant to their interests pertaining to their soundcard.

        The comp.sys.ibm.pc.soundcard.GUS is unrecognized usenet group
        throughout many news servers. Therefore, to avoid confusion and to
        reorganize the entire soundcard group, this illegal group must be
        eliminated. Many GUS users are satisfied with removing this group
        and using the four above mentioned subgroups.
        
        There was also concern about where this group should be located, under
        the comp.syd.ibm.pc hierarchy or comp.sys.ibm.pc.hardware hierarchy. 
        It has been decided to leave the soundcard subgroups under the
        former mentioned hierarchy to prevent any problems with news servers
        and provides with usenet groups with seven level names. Also, the
        transition would be less disturbing.

RATIONALE:

        The idea of spliting the group was tossed around the c.s.i.p.s
        group many times. However, no action was ever taken. It is hoped
        that finally with the dramatic increase in messages, that this
        reorganization would make the group more efficient and easier to
        use. Questions had to be raised about add another group, a
        c.s.i.p.soundcard.GUS group which would handle all topics 
        specific to the Gravis Ultrasound card. Presently, a majority of
        messages on the group is concerned with this card. Now with the
        a 100 message increase because of a heated debate (flame war?)
        the rational users want the group to be split. This eventually let to
        a group discussion about splitting up the soundcard group based upon
        the particular cards discussed, such as the Ultrasound, Soundblaster,
        Pro Audio Spectrum, etc. However, further discussion revealed that a
        majority thought that such a split would be short term due to the
        possibility of an unexpected loss of interest in a particular product.
        Therefore, because of the prospect of new soundcards being released
        that would increase the number of messages to the group, the prospect
        of more pc users of becoming involved in the multimedia revolution,
        and the steadily increase in messages in this group, it was decided
        that the group should be split based upon the topics mentioned above.

        The games group was chosen because a great number of posts on the
        soundcard group are concerned with how to use a particular soundcard
        with a particular game and what soundcard is best to use with game.
        Many users were concerned that the group was overrun with posts
        concerning how to get a particular game to work with a particular
        soundcard. They had to try to sift through the 200+ message a day
        to look for non-game compatibility messages. Therefore,
        the music group was also chosen because the other large part of
        message is related to the production of music. These include what
        programs can use a particular music format, and what programs exist
        to create programs. Also, in this group is the topic of sounds
        such as digitizing sound bytes and songs. A separate group was not
        created because many of the problems and solutions concerning
        recording or playing back sounds is related to the music production
        scene. The tech section was chosen because many users occasionally
        have questions about the technical aspect of soundcard, such as
        the pros and cons on how a soundcard generates sounds. Also,
        any hardware problems and compatibility would be discussed. But
        most importantly, the advocacy group would handle the bulk of the
        soundcard debate and keep it away from those more concerned
        with games or music. Finally, the misc group would be concerned with
        any topic or discussion outside of the above mentioned groups. This
        group is need to provide some kind of order in the other groups.
        Posting messages not really relevant to a particular group would cause
        an increase in traffic where it is not needed. As evident from other
        groups that have split, the misc section is used often. Possibly, by
        posting to the misc group, the message could be sent to the proper
        subgroup.Such a split would try to evenly distribute the
        messages throughout the sub groups. Most agree that sorting through
        50+ is cheaper and less time-consuming.


HOW TO VOTE

Erase everything above the top "-=-=-=-" line and erase everything
below the bottom "-=-=-=-" line.  Do not erase anything between these
lines and do not change the group names.

Give your 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.  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.

Then mail the ballot to:    votes@geoworks.com
Just Replying to this message should work, but check the "To:" line.



-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
comp.sys.ibm.pc.soundcard reorganization Ballot    <SOUND-0002> (Don't remove this marker)

Give your real name here:

[Your Vote]  Group
-----------------------------------------------------------------------
[         ]  comp.sys.ibm.pc.soundcard.tech
[         ]  comp.sys.ibm.pc.soundcard.music
[         ]  comp.sys.ibm.pc.soundcard.games
[         ]  comp.sys.ibm.pc.soundcard.advocacy
[         ]  comp.sys.icm.pc.soundcard.misc (replaces comp.sys.ibm.pc.soundcard)
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-



Anything else may be rejected by the automatic vote counting program.  The
votetaker will respond to your received ballots with a personal acknowledge-
ment by mail - if you do not receive one within several days, try again.
It's your responsibility to make sure your vote is registered correctly.

Each person may vote only once, no matter how many accounts he or she
may have. Also, only one ballot will be accepted from any account, no
matter how many people may share it. If more than one vote is received
>from any person or any account, only the last vote received will be
counted.

Addresses and votes of all voters will be published in the final
voting results list. All ballots received are kept in the UVV archives
(including "cancelled" and invalid ballots). The vote files are made
available to the moderator of news.announce.newgroups on request. They
may also, at the discretion of the UVV, be made more widely available
if there is a controversy concerning the vote.


BOUNCES

The following people have submitted valid ballots, but my EMail
acknowledgement bounced. They do not need to revote.

comp.sys.ibm.pc.soundcard reorganization Bounce List - No need to revote
------------------------------------------------------------------------------
catseye@minerva.cis.yale.edu.                                   Mark Kupferman
JGR@1211.ericsson.se                                      Jesus A. de Gregorio

INVALID VOTES

The following people have submitted invalid ballots and have not
superseded them with valid ones. 

Votes in error
------------------------------------------------------------------------------
scottshk@alpha2.csd.uwm.edu                                     Scott Petersen
   ! No vote statement in message

From asolovay@geoworks.com Tue May 31 20:53:14 1994
Path: uunet!bounce-back
From: asolovay@geoworks.com (Andrew Solovay)
Newsgroups: news.announce.newgroups,news.groups,comp.sys.ibm.pc.soundcard
Subject: RESULT: comp.sys.ibm.pc.soundcard reorganization all groups pass
Supersedes: <comp.sys.ibm.pc.soundcard-reorg-CFV2@uunet.uu.net>
Followup-To: news.groups
Date: 31 May 1994 20:51:14 -0400
Organization: Usenet Volunteer Votetakers (UVV)
Lines: 362
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <comp.sys.ibm.pc.soundcard-reorg-RESULT@uunet.uu.net>
References: <comp.sys.ibm.pc.soundcard-reorg-RFD1@uunet.uu.net> <comp.sys.ibm.pc.soundcard-reorg-CFV1@uunet.uu.net> <comp.sys.ibm.pc.soundcard-reorg-CFV2@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: uunet news.announce.newgroups:5165 news.groups:105345 comp.sys.ibm.pc.soundcard:50177

                               RESULT
    unmoderated group comp.sys.ibm.pc.soundcard.tech passes 223:30
   unmoderated group comp.sys.ibm.pc.soundcard.music passes 220:32
   unmoderated group comp.sys.ibm.pc.soundcard.games passes 215:34
  unmoderated group comp.sys.ibm.pc.soundcard.advocacy passes 213:34
           unmoderated group comp.sys.ibm.pc.soundcard.misc
          (replaces comp.sys.ibm.pc.soundcard) passes 218:32


comp.sys.ibm.pc.soundcard reorganization results - 253 valid votes

 Yes   No : 2/3? >100? : Pass? : Group
---- ---- : ---- ----- : ----- : -------------------------------------------
 223   30 :  Yes   Yes :   Yes : comp.sys.ibm.pc.soundcard.tech
 220   32 :  Yes   Yes :   Yes : comp.sys.ibm.pc.soundcard.music
 215   34 :  Yes   Yes :   Yes : comp.sys.ibm.pc.soundcard.games
 213   34 :  Yes   Yes :   Yes : comp.sys.ibm.pc.soundcard.advocacy
 218   32 :  Yes   Yes :   Yes : comp.sys.ibm.pc.soundcard.misc 
                                    (replaces comp.sys.ibm.pc.soundcard)
   2 invalid votes

For group passage, YES votes must be at least 2/3 of all valid (YES and NO)
votes.   There also must be at least 100 more YES votes than NO votes. 

There is a five day discussion period after these results are posted.  If no
serious allegations of voting irregularities are raised, the moderator of
news.announce.newgroups will create the group shortly thereafter.


Voting closed at 23:59:59 GMT, 30 May 1994.

This vote was conducted by a neutral third party.

Vote-taker's address:           asolovay@geoworks.com (Andrew Solovay)
Group proponent's address:      vincie@cs.jhu.edu (Michael Young Ko)


Newsgroups line:
comp.sys.ibm.pc.soundcard.tech  Technical questions about pc soundcards.
comp.sys.ibm.pc.soundcard.music Music and sound questions using soundcards.
comp.sys.ibm.pc.soundcard.games Questions about using soundcards with games.
comp.sys.ibm.pc.soundcard.advocacy      Advocacy for a particular soundcard.
comp.sys.icm.pc.soundcard.misc  Soundcards in general.

CHARTERS (culled from the Call for Votes)

comp.sys.ibm.pc.soundcard.games 

    Unmoderated discussion of using IBM-PC compatible games with a
    specific soundcard, resolving compatibility problems of a certain
    soundcard with a particular game, discussing campaigns at software
    groups to have more native soundcard support, questions if a
    particular game supports a certain soundcard, and questions on
    which soundcard is best for a particular game or all games in
    general.

comp.sys.ibm.pc.soundcard.music 

    Unmoderated discussion of software that plays back and record
    sound and music files, music formats such as WAV, VOC, MIDI, MOD,
    STM, 669, ULT, ROL, etc., resolving problems with musical
    software, discussing which software or hardware is best for a
    particular musical or sound project, and questions concerning
    sampling or sound patch making.

comp.sys.ibm.pc.soundcard.tech 

    Unmoderated discussion of questions concerning programming a
    particular soundcard, discussing hardware problems such as loss of
    sound from a particular channel, discussing the pros and cons of a
    particular sound generation scheme, questions on the compatibility
    of the soundcard to a particular computer type, operating system,
    and peripheral such as a CD-ROM drive, questions about the
    functionality of a particular soundcard, and resolving hardware
    problems.

comp.sys.ibm.pc.soundcard.advocacy

    Unmoderated discussion of the pros and cons of soundcards in
    general. This discussion will possibly overlap some discussions on
    the other soundcard groups. Also reviews of soundcards and future
    opinions and tests of soundcards will be placed in this group to
    be discussed by the users.

comp.sys.ibm.pc.soundcard.misc

    Unmoderated discussion of topics concerning soundcard hardware and
    software that is outside of the above mentioned topics. These
    could include upcoming product release or updates for soundcard
    software. (This group would supersede the existing group
    comp.sys.ibm.pc.soundcard.)

comp.sys.ibm.pc.soundcard reorganization Final Vote Ack


  comp.sys.ibm.pc.soundcard.misc (replaces comp.sys.ibm.pc.soundcard) -------+
                                   comp.sys.ibm.pc.soundcard.advocacy ------+|
                                      comp.sys.ibm.pc.soundcard.games -----+||
                                      comp.sys.ibm.pc.soundcard.music ----+|||
                                       comp.sys.ibm.pc.soundcard.tech ---+||||
                                                                         |||||
0005920651@mcimail.com                                   Ron Mac Quarrie YYYYY
A.P.North1@student.lut.ac.uk                                Adrian North YYYYY
aa37+@andrew.cmu.edu                                         Ali E Aydar YYYYY
aa393@freenet.carleton.ca                                Ramesh Fernando YYYYY
achiu@mprgate.mpr.ca                                           Alan Chiu YYYYY
adams@kona.wes.army.mil                                       Paul Adams NNNNN
af705@freenet.carleton.ca                                   Donald Young YYYYY
agranhol@bilbo.abo.fi                                 Alexander Granholm YYYYY
ak605@freenet.carleton.ca                                   Adrian Kwong YYYYY
al198723@academ01.mty.itesm.mx                           Eugenio Sanchez YYNNN
anders@uss-enterprise.bu.edu                          Anders M Jorgensen NNNNN
andrewd@sunrise.sli.unimelb.edu.au                     Andrew Disseldorp YYYYY
andyl@harlequin.com                                           Andy Latto YYYYY
antersbe@informatik.tu-muenchen.de                   Stefan Antersberger NYYNY
apervazo@sas.upenn.edu                                  Andrian Pervazov YYYY-
argyle@cegt201.bradley.edu                                     Lee Saito YYYYY
asimard@emr.ca                                              Andre Simard YYYYY
aspencer@austin.ibm.com                                     Alex Spencer YYYYY
audra_russell@il.us.swissbank.com                          Audra Russell YYYYY
ault@cs.albany.edu                                            James Ault YYYYY
babar@vipunen.hut.fi                                    Anton Vuorilehto YYYYY
bens@wrgate.wr.tek.com                                      Benjamin Sam Y--YY
bergius@cc.helsinki.fi                                   Petteri Bergius YYYYY
BiGMAX@mpcclub.msk.su                                       Max Gavrilin YYYYY
boutell@netcom.com                                        Thomas Boutell YYYYY
brawicz@sfu.ca                                              Bolko Rawicz YYYYY
brax@gemstar.com                                         Robert M Crespo YYYYY
bre@os.is                                            Bjarni R. Einarsson YYYYY
brodskyf@std.teradyne.com                               Franklin Brodsky YYYYY
bromage@mundil.cs.mu.oz.au                                Andrew Bromage YYYYY
bruce@big.att.com                                          Bruce Hillyer YYYYY
bryanw@microsoft.com                                   Bryan A. Woodruff YYYYY
bturner@ida.org                                               Ben Turner YYYYY
burt+@cmu.edu                                               Burt Holzman YYYYY
calvid@rpi.edu                                              David Calvin YYYYY
catseye@minerva.cis.yale.edu.                             Mark Kupferman NNNNN
ccastge@prism.gatech.edu                                  Guy Elden, Jr. YYYYY
ccdvu@cc.uq.oz.au                                               David Vu YYYYY
ceemjw@cee.hw.ac.uk                   Mike Weavind <ceemjw@cee.hw.ac.uk> YYYYY
charding@turing.raynet.com                            Charles D. Harding YYYYY
Charles_Wong@mindlink.bc.ca                            Charles K.F. Wong YYYYY
Chevnut@osuunx.ucc.okstate.edu    The Tramp (chevnut@osuunx.ucc.okstate. YYYYY
chipper@gilead.connected.com                             Scott McDermott YYNYY
chrism@huey.nic.bc.ca                                       Chris Mackay NYYNY
chrsbmw@aimla.com                                     Christopher Mihaly YYY-Y
cjackson@csugrad.cs.vt.edu                                 Chris Jackson NNNNN
cju@garnet.msen.com                                       Chris Unsicker YYYYY
cjw@oclc.org                                             Craig J. Wright YYYYY
ckalin@cae.uwm.edu                                  Christopher A. Kalin YYYYY
close@lunch.asd.sgi.com                               Diane Barlow Close NNNNN
cornel@ephsa.sat.tx.us                                       Cornel Huth YYYYY
cote@seismo.emr.ca                                              Tim Cote YYYYY
cowles@hydra.convex.com                                      John Cowles YYYYY
crouchkp@flidh102.delcoelect.com                  Kenneth P. Crouch, Jr. NNNNN
cthomas@glenayre.com                                      Clinton Thomas YYYYY
d91mn@efd.lth.se                                        Mikael Nordqvist YYYYY
dantonio@tay2.dec.com                                    David D'Antonio YYYYY
darla@shell.portal.com                                        Kuby Downs YYYYY
davec@ss114.comm.mot.com                                      David Crim YYYYY
david@qtac.edu.au                                           David Taylor YYYYY
davidp@sdt.com                                              David Pedigo YYYYY
dball@hp8c.nrl.navy.mil                                David George Ball YYYYY
dbasinge@bronze.ucs.indiana.edu                      D. Michael Basinger YYYYY
ddebry@dsd.es.com                                             Dave DeBry YYYYY
devuns@alsys.fr                                           Olivier Devuns NNNNN
df@eyrie.demon.co.uk                                        Derek Fawcus YYYYY
djh@newt.phys.unsw.edu.au                                  Daniel Hatadi YYYYY
dkiehl@romulus.ncsc.mil                                     Dana L Kiehl YYYYY
dmcintyr@muselab.ac.runet.edu                        D. Michael McIntyre YYYYY
dowtin@ncat.edu                                             Brian Dowtin YYYYY
drayer@minerva.cis.yale.edu                               Rebecca Drayer NNNNN
dtaylor@cis.ohio-state.edu                             david alan taylor YYYYY
duane@zadall.com                                          Duane Hargrave YYYYY
dvolpe@kodak.com                                               Dan Volpe YYNNY
eab@msc.edu                                               Edward Bertsch YYYYY
ebingham@mhs.mendocino.k12.ca.us                             Eli Bingham YYYYY
echuang@cco.caltech.edu                                    Ernest Chuang NNNYN
em439572@rsfddi2.cem.itesm.mx                          Jes#s L"pez Amaro YYYYY
erbo@rain.org                                           Eric J. Bowersox YYYYY
ERH6HALLS@cluster.north-london.ac.uk                       Simon R. Hall YYYYY
ernst@tymnet.com                                            Dennis Ernst YYYYY
ez040231@bullwinkle.ucdavis.edu                        Jeffrey Bernstein YYYYY
FCROSSEN@ccvax.ucd.ie                                    Francis Crossen YYYYY
fsspr@camelot.acf-lab.alaska.edu                            Sean P. Ryan NNNNN
gedra@lise.unit.no                                     Geir A. M. Drange YYYYY
gkmaier%crlvax.dnet@crl.mobil.com                             Greg Maier YYYYY
gmoy@nwu.edu                                                 Gabriel Moy YYYYY
godfrey2@rowan.coventry.ac.uk                               Bill Godfrey YY--Y
gorkom@marvels.hacktic.nl                               Ramon van Gorkom YYYYY
gosain@itd.nrl.navy.mil                                    Ankush Gosain YYYYY
h149373@proffa.cc.tut.fi                                 Jori H{m{l{inen YYYYY
hade@snakemail.hut.fi                                      Jussi Hattula YYYYY
HALVORSEN@nbivax.nbi.dk                                  Bjorn Halvorsen YYYYY
haroldf@alnitak.usc.edu                                      Jeff Lawson YYYYY
HD0022%ALBNYVMS.bitnet@uacsc2.albany.edu                     Chip Dunham NNNNN
herm@owlnet.rice.edu                                     Hermann Gartler YYYYY
hh@jwd.ping.de                                     Henning Holtschneider YYYYY
hoa.ho@ablelink.org                                               Hoa Ho YYYYY
holt@holt.camax.com                                        Jonathan Holt YYYYY
holzmann@kirk.fmi.uni-passau.de                         Andreas Holzmann YYYYY
hson@ludd.luth.se                                        Roger Hakansson NNNNN
itu1!mostert@itu1.sun.ac.za                                   A. Mostert YYYYY
J.C.vanderWal@research.ptt.nl                           Kees van der Wal YYYYY
j.d.brinck@bham.ac.uk                                       Jason Brinck YNYYY
jag@df.lth.se                                                 Jan Gajdos YYYYY
jaj@dallas.dal.mcd.mot.com                               John A. Johnson YYYYY
james@maths.ex.ac.uk                                       Jamie Andrews YYYYY
jaroharj@snakemail.hut.fi                                Markus Aroharju YYYYY
jbryer@trog.mbb.sfu.ca                                        Jeff Bryer NNNYN
jdp9w@watt.seas.virginia.edu                              John D. Palmer YYYYY
jds@hardy.math.okstate.edu                                Jennifer Smith YYYYY
jfortt@dorsai.dorsai.org                                    Joseph Fortt YYYNY
JGR@1211.ericsson.se                                Jesus A. de Gregorio YYYYY
jheng@ncube.com                                                John Heng NNNNN
jimb@etgn01.webo.dg.com                                       James Buja YYYYY
jiml@up.edu                                                   Jim Little YYYYY
jk@snafu.muncca.fi                                        Janne Korkkula YYYYY
jleon@chaph.usc.edu                                     Juan Carlos Leon YYY-Y
jmdaluz@kquest.com                                         Jose M. daLuz YYYNY
jnoon@kn.pacbell.com                                           Jeff Noon YYYNY
johan@borksoft.kiss.wlink.nl                              Johan Borkhuis YYYYY
JOHNSODC@caedm.et.byu.edu                                Dean C. Johnson YYYYY
jonyi@mit.edu                                                     Jon Yi YYYYY
joshua.appel@realexposure.com                               Joshua Appel YYYYY
jpm@mdata.fi                                       Jani Petteri Mattsson YYYYY
jrm@globalvillag.com                               John R. MacWilliamson NNNNN
jrp@unixa.nerc-wormley.ac.uk                               James Perrett YYYYY
jsciv@polaris.async.vt.edu                                Joseph Cochran YYYYY
jtcapps@netcom.com                                         John T. Capps YYYYY
J_A_Paulin%mbcorp2@mbmgate1.mitre.org                   Joseph A. Paulin YYYYY
Kari.Hurtta@fmi.fi                                        Kari E. Hurtta NNNNN
ken@zadall.com                                            Ken Hargreaves YYYYY
kherron@ms.uky.edu                                        Kenneth Herron NYYYY
kmk@stekt11.oulu.fi                                       Markus Kukkula YYYYY
koutch_t@epita.fr                                         LEROY FRANCOIS YYYYY
kperry@dorsai.dorsai.org                                       Ken Perry YYYYY
krish@vuse.vanderbilt.edu                                                NNNNN
ks@physik.unizh.ch                                      Kurt Sonnenmoser YYYYY
L15D@zfn.uni-bremen.de                                  Martin Schr"oder YYYYY
lb43+@andrew.cmu.edu                                         Lyren Brown YYYYY
lovesexy@css.itd.umich.edu                          Michael Todd Glazier NNNNN
lpkruger@phoenix.princeton.edu                              Louis Kruger YYYYY
luochu@chert.CS.ORST.EDU        Chung-Cheng Luo (luochu@ada.cs.orst.edu) NYYYN
manser@ezinfo.vmsmail.ethz.ch                                 Urs Manser YYYYY
markw@jsb.co.uk                                                Mark West YYYYY
martin@osiris.cs.csufresno.edu                         Martin von Loewis YYYYY
mcharsley@cix.compulink.co.uk                              Mark Charsley YYYYY
mct@trenga.tredydev.unisys.com                                Matt Thul  YYYYY
mdda@eng.cam.ac.uk                                        Martin Andrews YYYY-
meshreki@eecis.udel.edu                                   Samer Meshreki YYYYY
MFROOMKI@umiami.ir.miami.edu                            Michael Froomkin YYYYY
mg@ac.duke.edu                                             Michael Grubb YYYYY
Michael_Rodgers@mindlink.bc.ca                           Michael Rodgers YYYYY
michl@cogs.susx.ac.uk                                    Michael Lefevre YYYYY
mmedia!mcfarlin@notes.tssi.com                           DAVID MCFARLING YYYYY
mmeltzer@glue.umd.edu                                       Marc Meltzer YYYYY
mmt@redbrick.com                                           Maxime Taksar NNNNN
mnlerg@cs.umu.se                                            Erik Renberg YYYYY
mrogers@afit.af.mil                                     Martin H. Rogers YYYYY
msmeissn@cip.informatik.uni-erlangen.de                  Marcus Meissner YYYYY
mughal@alumni.caltech.edu                                    Asim Mughal YYYYY
mww2g@virginia.edu                                        Michael Wells  YYYYY
n4zfd!frodo@uunet.uu.net                                     Jim Blakely YYYYY
nfdsouza@elecom2.watstar.uwaterloo.ca                       Noel D'Souza YYYYY
nix@gs86.sp.cs.cmu.edu                                     Nick Thompson YYYYY
njdowell@iastate.edu                                          N J Dowell YY---
NJUHASZ@btkstud.jpte.hu                                   Norbert Juhasz YYYYY
nmstough@e4e.oac.uci.edu                               Neal M. Stoughton YYYYY
NSX@chip.cba.ufl.edu                                       Mark Sterling YYYYY
nyfx!piza!pcunnell@csfb1.fir.fbc.com                        Paul Cunnell YYYYY
osaki@viper.arc.nasa.gov                                    Robert Osaki YYYYY
Peng.Yanming@mech.kuleuven.ac.be                            Yanming PENG YYYYY
peterb@telerama.lm.com                                      Peter Berger YYYYY
peterrb@compnews.co.uk                                        Peter Boyd YYYYY
pgut01@cs.aukuni.ac.nz                                     Peter Gutmann YYYYY
phudw@csv.warwick.ac.uk                                       Ian Hutton YYYYY
PINKERTONA@delphi.com                                     Alan Pinkerton YYYYY
plutchak@porter.geo.brown.edu                              Joel Plutchak YYY-Y
quinn@phoenix.princeton.edu                                Michael Quinn YYYYY
ralf@wpi.edu                                             Ralph Valentino YYNYY
rdj@iastate.edu                                               GUS RuleZ! YYYYY
richard@ide.com                                         Richard P. Davis YYYYY
rick@bcm.tmc.edu                                          Richard Miller YNNYN
ricochet@netcom.com                                             A. Kilna YYYYY
riegel@almaden.ibm.com                                       Jeff Riegel YYYYY
riku.saikkonen@compart.fi                                 Riku Saikkonen YYYYY
rohrers@dmapub.dma.org                                       Stan Rohrer YYYYY
rspangle@micro.caltech.edu                           Randall R. Spangler YYYYY
ruhtra@turing.toronto.edu                                Arthur Tateishi YYYYY
rwebb@panix.com                                             Russell Webb YYYYY
s106275@ee.tut.fi                                            Anssi Saari NNNNN
SAAST8@vms.cis.pitt.edu                              Seyed A. Alavizadeh YYYYY
saswta@unx.sas.com                                          Bill Arnette YYYYY
SCARMAN@hfrd.dsto.gov.au                                   Gavin Scarman YYYYY
scsavett@acad.ursinus.edu                                Scott C. Savett YYYYY
sdrennan@bnr.ca                                            Scott Drennan YYYYY
sean@starlight.smos.com                                      Sean Gugler YYYYY
shaneb@actrix.gen.nz                                       Shane Borrett YYYYY
sheldon@iastate.edu                                        Steve Sheldon YNNNY
shemavo@ecf.toronto.edu                                Derek Shemavonian YYYYY
Simon@geordie.demon.co.uk                                    Simon Crute YYYYY
smailer@titan.ucs.umass.edu                                  Ira Smailer NNNNN
smarry@turing.toronto.edu                                 Marc Moorcroft NNNNN
smullen@crl.com                                          Michael Smullen YYYYY
smustain@magnus.acs.ohio-state.edu                         Mike Mustaine YYYYY
sorensen@isye.gatech.edu                                    Tom Sorensen YYYYY
stainles@bga.com                                            Dwight Brown NNNNN
steina@alkymi.unit.no                               Stein M H Aasmundsen YYYYY
strongbw@crash.cts.com                                    Colin Ritchie  YYYYY
stu@valinor.mythical.com                                    Stu Labovitz NYY-Y
sveijgen@sthp.wi.leidenuniv.nl                        Sebastiaan Veijgen YYYYY
swartz@sfu.ca                                              Norman Swartz YYYYY
symon@radonc.unc.edu                                         James Symon YYYYY
t.d.g.sandford@comp.brad.ac.uk                      Thomas D.G. Sandford YYYYY
taft!mesniepl@goofus.wustl.edu                              Phil Mesnier YYYYY
tauritz@stpc.wi.leidenuniv.nl                          Daniel R. Tauritz YYYYY
tbbusser@mailhost.ecn.uoknor.edu                             Tod Bussert YYYYY
tbranham@mm.wellesley.edu                                    Tom Branham YYYYY
tclee@iss.nus.sg                                           Lee Teck Chee YYYYY
tdh@manta.dwp.la.ca.us                                        Tom Honles YY-YY
tfj@apusapus.demon.co.uk                                  Trevor Jenkins YYYYY
tfl@psp.co.uk                                                 Thomas Lee YYYYY
tgm@netcom.com                                      Thomas G. McWilliams YNNNN
ThomasD@tps.com                                               Thomas Day YYYYY
tillman@swdev.si.com                                       Brian Tillman YYYYY
tim.gentry@mccaw.com                                          Tim Gentry YYYYY
TISEP@newton.mayo.edu                                         Paul Tiseo YYYYN
Tobias_Wenzel@2nd.fido.de                                  Tobias Wenzel YYYYY
todd@falcon.natinst.com                                      Todd Brower YYYYY
Tom.Deneau@amd.com                                    Tom.Deneau@amd.com YYYYY
tom@amber.ssd.csd.harris.com                           Thomas A. Horsley YYYYY
tom@ksr.com                                                 Thomas Varga YYYYY
tord@cee.hw.ac.uk                                            Tord Faeroy YYYYY
tpa@utu.fi                                                   Tomi Aarnio YYYYY
TRIPLETT@utsw.swmed.edu                                Terry L. Triplett YYYYY
trondj@lise.unit.no                                        Trond Johnsen YYYYY
ts0jwa@orac.sunderland.ac.uk                                   J.Waghorn YYYYY
TTruong.ESCP10@xerox.com                                      Ton Truong YYYYY
twwoehr@iastate.edu                                            Tim Woehr YYYYY
u8211512@cc.nctu.edu.tw                                         I.C Yang YNNNY
urena@titan.ucs.umass.edu                               Richard R. Urena YYYYY
v912382@si.hhs.nl                                                        YYYYN
vincie@zebra.cs.jhu.edu                                 Michael Young Ko YYYYY
voges001@maroon.tc.umn.edu                                     Hal Voges YYYYY
vsuhocki@cbnewsm.att.com                                      VP Suhocki YYYYY
WADLEIGH@process.com                                        Hal Wadleigh YYYYY
wang@hpodb05.cup.hp.com                                      Thomas Wang NNNNN
WARD@ernie.van.forintek.ca                                  Ward F. Bush NNNNN
wessantee@symantec.com                                        WES SANTEE YYYYY
whitmore@tahoma.cwu.edu                                  Stuart Whitmore YYYYY
wmays@motown.ge.com                                         William Mays YNNYY
zarkdav@eddy.frmug.fr.net                                Benjamin RYZMAN YYYYY
zawodny@arbd0.larc.nasa.gov                             Joseph M Zawodny YNYNN


Votes in error
------------------------------------------------------------------------------
mikem@rahul.net                                                  Mike McCammon
   ! No vote statement in message
scottshk@alpha2.csd.uwm.edu                                     Scott Petersen
   ! No vote statement in message

 
USENET FACT: Big-8
BIG-8 hierarchies are the 8 traditional top hierarchies of the Usenet. See the following page for more