OS/2 Shareware BBS: 15 Message/15-Message.zip/UU990918.zip/Ud990917.txt

Text File | 1999-09-18 | 54KB | 1,476 lines

                   comp.os.os2.multimedia           (Usenet)

                 Saturday, 11-Sep-1999 to Friday, 17-Sep-1999

+----------------------------------------------------------------------------+

From: [e-mail]                        11-Sep-99 00:22:09
  To: All                                               11-Sep-99 04:50:26
Subj: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Alex Taylor)

I'm using a Hauppauge WinTV/PCI card, and in order to get any sound,
I always need to issue the command "vxpvar wcast 1 s0_amux 2" before
starting WTV.

My question is, is there any way to set this up automatically?  Because
having to do this every time I reboot is a pain.  (In fact, is there any
way to make it "sticky", so the s0_amux variable STAYS at 2, even between
reboots?  That would simplify my question greatly.)

My idea is to write a CMD file that I tell OS/2 to run on bootup.

Unfortunately, VXPVAR.EXE demands that I type "y" before it'll make the
change (and doesn't accept a "/y" switch).  Plain OS/2 command files don't
allow this kind of interaction.

I assume a REXX script would make it possible.  Alas, my knowledge of
REXX programming is minimal.

Can anybody give me some help?  How have other people addressed this
problem?  Is there an easier way?

Thanks...
-----------------------------------------------------------------
 Alex Taylor                  BA - CIS - University of Guelph
 [e-mail]   http://eddie.cis.uoguelph.ca/~alex
-----------------------------------------------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network Canada (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                              10-Sep-99 19:37:02
  To: All                                               11-Sep-99 04:50:26
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail]

In <n34S6Erhpgnp-pn2-2970EjthdFxd@ifurita>, on 09/11/99
   at 12:22 AM, [e-mail] (Alex Taylor) said:

>My question is, is there any way to set this up automatically?  Because
>having to do this every time I reboot is a pain.  (In fact, is there any
>way to make it "sticky", so the s0_amux variable STAYS at 2, even between
>reboots?  That would simplify my question greatly.)

>My idea is to write a CMD file that I tell OS/2 to run on bootup.

I need to test this, but you should be able to redirect a file that
contains a 'Y' into the input of the command string like this:

   vxpvar wcast 1 s0_amux 2 < Y_File.TXT

The only contents of the Y_File.TXT is the letter Y and a carriage return.

-- --------------------------------------------------------
John B. Sandlin    [e-mail]
** New user?  Want to learn the ropes?
** Crusty old Guru?  Want to brush up your Netiquette?
** Check out: http://www.albion.com/netiquette/
-- --------------------------------------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           11-Sep-99 04:04:20
  To: All                                               11-Sep-99 04:50:26
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Lorne Sunley)

On Sat, 11 Sep 1999 00:22:19, [e-mail] (Alex Taylor)
wrote:

> I'm using a Hauppauge WinTV/PCI card, and in order to get any sound,
> I always need to issue the command "vxpvar wcast 1 s0_amux 2" before
> starting WTV.
>
> My question is, is there any way to set this up automatically?  Because
> having to do this every time I reboot is a pain.  (In fact, is there any
> way to make it "sticky", so the s0_amux variable STAYS at 2, even between
> reboots?  That would simplify my question greatly.)
>
> My idea is to write a CMD file that I tell OS/2 to run on bootup.
>
> Unfortunately, VXPVAR.EXE demands that I type "y" before it'll make the
> change (and doesn't accept a "/y" switch).  Plain OS/2 command files don't
> allow this kind of interaction.
>
> I assume a REXX script would make it possible.  Alas, my knowledge of
> REXX programming is minimal.
>
> Can anybody give me some help?  How have other people addressed this
> problem?  Is there an easier way?
>

Just to check, have you tried editing the "WCAST 1.INI" file that
is in \MMOS2?? This might do the trick.

Lorne Sunley

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                        11-Sep-99 13:38:10
  To: All                                               11-Sep-99 20:32:14
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Alex Taylor)

On Sat, 11 Sep 1999 04:04:41, [e-mail] (Lorne Sunley) wrote:

> > My idea is to write a CMD file that I tell OS/2 to run on bootup.
> >
> > Unfortunately, VXPVAR.EXE demands that I type "y" before it'll make the
> > change (and doesn't accept a "/y" switch).  Plain OS/2 command files don't

> > allow this kind of interaction.
> >
> > I assume a REXX script would make it possible.  Alas, my knowledge of
> > REXX programming is minimal.
> >
> > Can anybody give me some help?  How have other people addressed this
> > problem?  Is there an easier way?
>
> Just to check, have you tried editing the "WCAST 1.INI" file that
> is in \MMOS2?? This might do the trick.

Hmmm... what would I put in the file, though?  Right now it's an
empty file!

Here's what I've got...
-------------------------------------------------------
 5-13-99   6:07p         1           0  WCAST 1.INI
 5-13-99   6:07p         1           0  WCAST 2.INI
 9-09-99   7:05p     48227           0  wcast.sys

[C:\MMOS2]type "WCAST 1.INI"

[C:\MMOS2]
-------------------------------------------------------

Seems strange...

-----------------------------------------------------------------
 Alex Taylor                  BA - CIS - University of Guelph
 [e-mail]   http://eddie.cis.uoguelph.ca/~alex
-----------------------------------------------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network Canada (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                        11-Sep-99 13:40:05
  To: All                                               11-Sep-99 20:32:14
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Alex Taylor)

On Sat, 11 Sep 1999 00:37:04, [e-mail] wrote:

> >My question is, is there any way to set this up automatically?  Because
> >having to do this every time I reboot is a pain.  (In fact, is there any
> >way to make it "sticky", so the s0_amux variable STAYS at 2, even between
> >reboots?  That would simplify my question greatly.)
>
> >My idea is to write a CMD file that I tell OS/2 to run on bootup.
>
> I need to test this, but you should be able to redirect a file that
> contains a 'Y' into the input of the command string like this:
>
>    vxpvar wcast 1 s0_amux 2 < Y_File.TXT
>
> The only contents of the Y_File.TXT is the letter Y and a carriage return.

Interesting idea.  I was unsuccessful trying it just now, but maybe
I could play with it...

-----------------------------------------------------------------
 Alex Taylor                  BA - CIS - University of Guelph
 [e-mail]   http://eddie.cis.uoguelph.ca/~alex
-----------------------------------------------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network Canada (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           11-Sep-99 14:04:10
  To: All                                               11-Sep-99 20:32:14
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Lorne Sunley)

On Sat, 11 Sep 1999 13:38:20, [e-mail] (Alex Taylor)
wrote:

> On Sat, 11 Sep 1999 04:04:41, [e-mail] (Lorne Sunley) wrote:
>
> > > My idea is to write a CMD file that I tell OS/2 to run on bootup.
> > >
> > > Unfortunately, VXPVAR.EXE demands that I type "y" before it'll make the
> > > change (and doesn't accept a "/y" switch).  Plain OS/2 command files
don't
> > > allow this kind of interaction.
> > >
> > > I assume a REXX script would make it possible.  Alas, my knowledge of
> > > REXX programming is minimal.
> > >
> > > Can anybody give me some help?  How have other people addressed this
> > > problem?  Is there an easier way?
> >
> > Just to check, have you tried editing the "WCAST 1.INI" file that
> > is in \MMOS2?? This might do the trick.
>
> Hmmm... what would I put in the file, though?  Right now it's an
> empty file!
>
> Here's what I've got...
> -------------------------------------------------------
>  5-13-99   6:07p         1           0  WCAST 1.INI
>  5-13-99   6:07p         1           0  WCAST 2.INI
>  9-09-99   7:05p     48227           0  wcast.sys
>
> [C:\MMOS2]type "WCAST 1.INI"
>
> [C:\MMOS2]
> -------------------------------------------------------
>
> Seems strange...
>

The file doesn't have anything saved in it until you use
the "Multimedia Setup" program in the "Setup" folder
to set the parameters for the WCAST drivers. When you
exit the setup program the parameters are saved to
the "WCAST 1.INI" file (for the first Wincast/TV card).

Try this and then edit the parameters. The INI files are
loaded at system boot time. If the file is empty the
driver uses preset defaults.

Lorne Sunley


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                             11-Sep-99 10:58:26
  To: All                                               11-Sep-99 20:32:14
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: Alan Beagley <[e-mail]>

I've tried editing WCAST 1.INI, but it doesn't seem to accomplish anything. In
my
case, I need to set s2_amux  = 1 (instead of the default 3). Even if I edit
the INI
file, the value reverts to 3.

Alan

Lorne Sunley wrote:

> On Sat, 11 Sep 1999 13:38:20, [e-mail] (Alex Taylor)
> wrote:
>
> > On Sat, 11 Sep 1999 04:04:41, [e-mail] (Lorne Sunley)
wrote:
> >
> > > > My idea is to write a CMD file that I tell OS/2 to run on bootup.
> > > >
> > > > Unfortunately, VXPVAR.EXE demands that I type "y" before it'll make
the
> > > > change (and doesn't accept a "/y" switch).  Plain OS/2 command files
don't
> > > > allow this kind of interaction.
> > > >
> > > > I assume a REXX script would make it possible.  Alas, my knowledge of
> > > > REXX programming is minimal.
> > > >
> > > > Can anybody give me some help?  How have other people addressed this
> > > > problem?  Is there an easier way?
> > >
> > > Just to check, have you tried editing the "WCAST 1.INI" file that
> > > is in \MMOS2?? This might do the trick.
> >
> > Hmmm... what would I put in the file, though?  Right now it's an
> > empty file!
> >
> > Here's what I've got...
> > -------------------------------------------------------
> >  5-13-99   6:07p         1           0  WCAST 1.INI
> >  5-13-99   6:07p         1           0  WCAST 2.INI
> >  9-09-99   7:05p     48227           0  wcast.sys
> >
> > [C:\MMOS2]type "WCAST 1.INI"
> >
> > [C:\MMOS2]
> > -------------------------------------------------------
> >
> > Seems strange...
> >
>
> The file doesn't have anything saved in it until you use
> the "Multimedia Setup" program in the "Setup" folder
> to set the parameters for the WCAST drivers. When you
> exit the setup program the parameters are saved to
> the "WCAST 1.INI" file (for the first Wincast/TV card).
>
> Try this and then edit the parameters. The INI files are
> loaded at system boot time. If the file is empty the
> driver uses preset defaults.
>
> Lorne Sunley

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           11-Sep-99 16:38:25
  To: All                                               11-Sep-99 20:32:15
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Lorne Sunley)

Oh well, it was just something to try.....

If you have GRADD drivers installed you could try out my TV app
and Media Control Device (MCD/VSD) for the Hauppauge Wincast/TV
cards. The TV app allows you to set and save the amux setting. It
works
with DIVE as well but the CPU use for DIVE is pretty high.

URL  http://www3.mb.sympatico.ca/~lsunley/index.htm

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           11-Sep-99 17:42:00
  To: All                                               11-Sep-99 20:32:15
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Lorne Sunley)

Sorry about this but my replay was truncated for some reason.

Oh well, it was just something to try.....

If you have GRADD drivers installed you could try out my TV app
and Media Control Device (MCD/VSD) for the Hauppauge Wincast/TV
cards. The TV app allows you to set and save the amux setting. It
works
with DIVE as well but the CPU use for DIVE is pretty high.

URL  http://www3.mb.sympatico.ca/~lsunley/index.htm

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           11-Sep-99 17:47:19
  To: All                                               11-Sep-99 20:32:15
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Lorne Sunley)

For the third (fourth time) I'm trying to get the whole post
out. If you have a standalone "." on a line by itself the
post ends at that line (fairly obvious but easy to miss)

Oh well, it was just something to try.....

If you have GRADD drivers installed you could try out my TV app
and Media Control Device (MCD/VSD) for the Hauppauge Wincast/TV
cards. The TV app allows you to set and save the amux setting. It
works
with DIVE as well but the CPU use for DIVE is pretty high.

URL  http://www3.mb.sympatico.ca/~lsunley/index.html

It also allows the Multimedia REXX commands access to the
device variables with code like this. This code assumes the
Digital TV MCD/VSD installation gets "digitalvideo03" assigned
as the digital video device number. These are assigned
sequentially by the Multimedia Install so the actual number
will be one greater than the highest numbered "digitalvideo"
device present when the software is installed.

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

/* quicky REXX to set amux */
/* using the DigitalTV MCI Rexx capability */
/* assume Digital TV is digitalvideo03 */
/* this varies depending on the system */

/* load the REXX multimedia string command interface */

  CALL RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
  CALL SysLoadFuncs

  rc = RXFUNCADD('mciRxInit','MCIAPI','mciRxInit')
  InitRC = mciRxInit()

  mciCMD = 'open  digitalvideo03 alias tvalias shareable wait'
  rc = mciRxSendString(mciCMD,'macRC',0,0)
  if rc <> 0 then do
          macRC = mciRxGetErrorString(rc, 'ErrString');
          say 'Open Error =' rc ' String =' ErrString;
          end

/* acquire the device */
  mciCMD = 'acquire tvalias wait'
  rc = mciRxSendString(mciCMD,'macRC',0,0)
  if rc <> 0 then do
          macRC = mciRxGetErrorString(rc, 'ErrString');
          say 'Acquire Error =' rc ' String =' ErrString;
          end

/* set the device variable */
  mciCommand = 'devvariable tvalias set hardware s0_amux value 2 wait'
  rc = mciRxSendString(mciCommand,'macRC',0,0)
  if rc <> 0 then do
          macRC = mciRxGetErrorString(rc, 'ErrString')
        say 'Devvariable Error =' rc ' String =' ErrString
        say 'Command = ' mciCommand
        end

  mciCMD = 'close tvalias wait'
  rc = mciRxSendString(mciCMD,'macRC',0,0)
  if rc <> 0 then do
          macRC = mciRxGetErrorString(rc, 'ErrString')
          say 'Close Error =' rc ' String =' ErrString
          end

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

You could put this in a .CMD file and set up a program object
to it in your "Startup" folder.

Lorne Sunley

On Sat, 11 Sep 1999 14:58:53, Alan Beagley <[e-mail]>
wrote:

> I've tried editing WCAST 1.INI, but it doesn't seem to accomplish anything.
In my
> case, I need to set s2_amux  = 1 (instead of the default 3). Even if I edit
the INI
> file, the value reverts to 3.
>
> Alan
>
> Lorne Sunley wrote:
>
> > On Sat, 11 Sep 1999 13:38:20, [e-mail] (Alex Taylor)
> > wrote:
> >
> > > On Sat, 11 Sep 1999 04:04:41, [e-mail] (Lorne Sunley)
wrote:
> > >
> > > > > My idea is to write a CMD file that I tell OS/2 to run on bootup.
> > > > >
> > > > > Unfortunately, VXPVAR.EXE demands that I type "y" before it'll make
the
> > > > > change (and doesn't accept a "/y" switch).  Plain OS/2 command files
don't
> > > > > allow this kind of interaction.
> > > > >
> > > > > I assume a REXX script would make it possible.  Alas, my knowledge
of
> > > > > REXX programming is minimal.
> > > > >
> > > > > Can anybody give me some help?  How have other people addressed this
> > > > > problem?  Is there an easier way?
> > > >
> > > > Just to check, have you tried editing the "WCAST 1.INI" file that
> > > > is in \MMOS2?? This might do the trick.
> > >
> > > Hmmm... what would I put in the file, though?  Right now it's an
> > > empty file!
> > >
> > > Here's what I've got...
> > > -------------------------------------------------------
> > >  5-13-99   6:07p         1           0  WCAST 1.INI
> > >  5-13-99   6:07p         1           0  WCAST 2.INI
> > >  9-09-99   7:05p     48227           0  wcast.sys
> > >
> > > [C:\MMOS2]type "WCAST 1.INI"
> > >
> > > [C:\MMOS2]
> > > -------------------------------------------------------
> > >
> > > Seems strange...
> > >
> >
> > The file doesn't have anything saved in it until you use
> > the "Multimedia Setup" program in the "Setup" folder
> > to set the parameters for the WCAST drivers. When you
> > exit the setup program the parameters are saved to
> > the "WCAST 1.INI" file (for the first Wincast/TV card).
> >
> > Try this and then edit the parameters. The INI files are
> > loaded at system boot time. If the file is empty the
> > driver uses preset defaults.
> >
> > Lorne Sunley
>


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                              11-Sep-99 16:41:28
  To: All                                               12-Sep-99 04:17:18
Subj: Re: FAQ for all multimedia

From: "J. R. Fox" <[e-mail]>

Sander Nyman wrote:

>I was fortunate to have seen one of Jerry's OS/2 multimedia >presentations a
few months ago.  EXCELLENT!!!  If you are into >multimedia, this is a DO NOT
MISS!  In fact, he has updated, >and expanded his presentation for SCOUG's
Warp Expo West.

Quite possibly the best info available on this subject, most of
it seemingly based on extensive trial & error experimentation
(i.e., very practical), plus maybe a bit of hacking here and
there.

For the benefit of anyone who can't be on the left coast for this, I
hope that much of the content will ultimately find its
way into article(s) published somewhere, or perhaps posted on
the SCOUG website.  Let's hope so, anyway.

<jf>

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: EarthLink Network, Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                              11-Sep-99 16:46:26
  To: All                                               12-Sep-99 04:17:18
Subj: Re: Which photography applications work well with OS/2 for postprocessi

From: "J. R. Fox" <[e-mail]>

>Another tool might be Photographics pro from True Spectra.  >They have quit
marketing it but instead have placed it as a >FREE download on their support
web site
>http://www.truespectra.com/support.html until the end of
>the year.
>
>Download and follow the instructions to register it.  The >result is a full
featured copy of a very well respected >graphics program for OS/2.
>
> -----------------------------------------------------------
> "Kurt Petersen" [e-mail]

> -----------------------------------------------------------

Thanx for the heads-up on this.  What about the non-Pro ver.
of Photo>Graphics -- is that discontinued too ?  I have this
but never got around to sending in the registration card.

<jf>

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: EarthLink Network, Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                  12-Sep-99 00:38:09
  To: All                                               12-Sep-99 10:18:25
Subj: Digital Camcorders

From: [e-mail]

Are there any firewire cards out there that will
support the new digital camcorders firewire connectors?

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: SBC Internet Services (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                  12-Sep-99 15:03:04
  To: All                                               12-Sep-99 14:38:16
Subj: Call for Papers -- Testing Computer Software Conference (TCS2000)

From: [e-mail] (Peter Zuckerman)


                 CALL FOR PAPERS and PRESENTATIONS
                               for the

            17th International Conference and Exposition on

                  TESTING COMPUTER SOFTWARE (TCS2000)

           Theme: Testing Technology vs. Testers' Requirements

              June 12-16, 2000 * Washington, D.C. * USA
       (Conference: June 14-16; Workshops/Tutorials: June 12-13)

In cooperation with:

   Association for Computing Machinery (ACM) SIGSoft
   American Society for Quality (ASQ) Software Division
   IEEE Reliability Society
   Software Technology Support Center (STSC)

  You are invited to submit proposals for the TCS2000 Conference!

We are soliciting contributions for technical papers, tutorials and
workshops. The Conference will cover:

* The impact of increasingly complex software on testing
* Ways to improve the testing process
* Practical experience with the various techniques
* Which efforts have been most successful
* Which efforts have been least successful

* Planned tracks:
  * Management
  * Technical
  * Automation
  * Advanced Topics (Refereed papers)
  * Case Studies

While presentations that directly relate to the theme are encouraged,
other topics relevant to improving the testing process are invited and
will be accepted.

Submission guidelines are available at http://www.uspdi.org/tcs2000call/

Downloadable/printable brochure is available at
http://www.uspdi.org/tcs2000call/tcs2000callpdf.html

GUIDELINES FOR REGULAR PAPERS:
http://www.uspdi.org/tcs2000call/tcs2000callreg.html
Important dates:
Presentation proposals: October 15, 1999
   Notice of selection: December 15, 1999
    Materials deadline: March 15, 2000

GUIDELINES FOR REFEREED PAPERS:
http://www.uspdi.org/tcs2000call/tcs2000callref.html
Important dates:
Presentation proposals: October 15, 1999
   Notice of selection: December 15, 1999
    Materials deadline: March 15, 2000

We are interested in hearing from you. If you want to submit a proposal
for a presentation, or explore an idea for a presentation, please contact
the Program Chair, Genevieve Houston-Ludlam, by:

       Phone: [phone]; E-mail: [e-mail]
     (preferred submission method, ascii text only please)

For refereed papers (Advanced Topics) please contact Roger Alexander, by
 E-mail: [e-mail]; Phone: [phone]; Fax: [phone]

For more information on TCS2000 visit our web site at:

http://www.uspdi.org/conference/ or contact:

U.S. Professional Development Institute
E-mail: [e-mail]; Phone: [phone]; Fax: [phone]

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

         One complimentary Conference registration is provided
                   for each accepted presentation.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: HPN (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                               12-Sep-99 19:19:08
  To: All                                               12-Sep-99 20:01:29
Subj: Where is multimedia setup?

From: Mat Nieuwenhoven <[e-mail]>

Hi,

I've installed an ESS1688P based sound card in a test system which
previously did not have any sound. Although OS/2 audio is fine, I cannot
get the CD player to work (for audio, data is fine). I presume this is
because the drive letter is wrong. The on-line help says (and I remember
using it) to use multimedia setup. But this program is nowhere to be
found. Not in the programs->multimedia folder, nothing in the \mmos2 or
os2 directories look like it. I'm running two machines both with Warp4
FP10. Both of them don't have the program. Should this program be there,
what is its executable name, and could I change the drive letter
manually somewhere?

Thanks, mat Nieuwenhoven

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: A2000 Kabeltelevisie en Telecommunicatie (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                               12-Sep-99 19:23:06
  To: All                                               12-Sep-99 20:01:29
Subj: How to locate WINOS2 sound error?

From: Mat Nieuwenhoven <[e-mail]>

Hi,

after installing an ESS1688P sound card using the drivers from the ddpak
online (os21688.zip), The OS/2 side works fine, but the WINOS2 sounds
don't work. I get a small msg box when starting winos2, titled 'audio'
but otherwise empy. I presume an error message is supposed to show
there. Is there a way of logging the error msg somewhere, or make it
visible in any other way?
Apart from that, is there a know error with the installation routines
for the ESS drivers that could cause this? he machine is running Warp4
FP10 .

Thanks, Mat Nieuwenhoven

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: A2000 Kabeltelevisie en Telecommunicatie (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           12-Sep-99 18:07:28
  To: All                                               12-Sep-99 20:01:29
Subj: Re: Where is multimedia setup?

From: [e-mail] (Lorne Sunley)

On Sun, 12 Sep 1999 17:19:17, Mat Nieuwenhoven <[e-mail]>
wrote:

> Hi,
>
> I've installed an ESS1688P based sound card in a test system which
> previously did not have any sound. Although OS/2 audio is fine, I cannot
> get the CD player to work (for audio, data is fine). I presume this is
> because the drive letter is wrong. The on-line help says (and I remember
> using it) to use multimedia setup. But this program is nowhere to be
> found. Not in the programs->multimedia folder, nothing in the \mmos2 or
> os2 directories look like it. I'm running two machines both with Warp4
> FP10. Both of them don't have the program. Should this program be there,
> what is its executable name, and could I change the drive letter
> manually somewhere?
>
> Thanks, mat Nieuwenhoven

It lives in the "System Setup" folder inside the "OS/2 System" folder.

The program name is \MMOS2\STPM.EXE

Lorne Sunley

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                        12-Sep-99 21:40:15
  To: All                                               13-Sep-99 03:45:01
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Alex Taylor)

On Sat, 11 Sep 1999 14:04:21, [e-mail] (Lorne Sunley) wrote:

> > > Just to check, have you tried editing the "WCAST 1.INI" file that
> > > is in \MMOS2?? This might do the trick.
> >
> > Hmmm... what would I put in the file, though?  Right now it's an
> > empty file!
>
> The file doesn't have anything saved in it until you use
> the "Multimedia Setup" program in the "Setup" folder
> to set the parameters for the WCAST drivers. When you
> exit the setup program the parameters are saved to
> the "WCAST 1.INI" file (for the first Wincast/TV card).
>
> Try this and then edit the parameters. The INI files are
> loaded at system boot time. If the file is empty the
> driver uses preset defaults.

Well, I've created & edited the file, and rebooted a number of
times.  WCAST 1.INI still says S0_AMUX=2, but the driver value
stays at 1 until I expressly change it with vxpvar... as though
the driver is simply ignoring the INI file completely.

-----------------------------------------------------------------
 Alex Taylor                  BA - CIS - University of Guelph
 [e-mail]   http://eddie.cis.uoguelph.ca/~alex
-----------------------------------------------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network Canada (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                        12-Sep-99 21:46:09
  To: All                                               13-Sep-99 03:45:01
Subj: Re: [WINTV] Automatically setting 's0_amux' e.g. via REXX?

From: [e-mail] (Alex Taylor)

On Sat, 11 Sep 1999 17:47:38, [e-mail] (Lorne Sunley) wrote:

> Oh well, it was just something to try.....
>
> If you have GRADD drivers installed you could try out my TV app
> and Media Control Device (MCD/VSD) for the Hauppauge Wincast/TV
> cards. The TV app allows you to set and save the amux setting. It
> works
> with DIVE as well but the CPU use for DIVE is pretty high.
>
> URL  http://www3.mb.sympatico.ca/~lsunley/index.html

I've never yet been able to get GRADD working on my system... I'm
not sure if it supports the MGA G200 cards.

I may give this a try, though...

-----------------------------------------------------------------
 Alex Taylor                  BA - CIS - University of Guelph
 [e-mail]   http://eddie.cis.uoguelph.ca/~alex
-----------------------------------------------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network Canada (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                               13-Sep-99 11:05:21
  To: All                                               13-Sep-99 10:36:28
Subj: Check out : DCITU

From: "C.J." <[e-mail]>

DCITU
********
Digital Camera Image Transfer Utility
This program allows images to be transferred from various digital
cameras to an OS/2-based computer. The transfer is accomplished
using the standard serial port cable usually supplied with the camera.

Check it out and download DCITU for a free trial period from:
http://www.btsoftware.com/os2/dcitu.htm


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: C.J. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           14-Sep-99 08:47:24
  To: All                                               14-Sep-99 18:43:06
Subj: Audio Driver for DELL Latitude CPt400

From: Stefan Pelz <[e-mail]>

Does anybody know if there is an audio driver for
a Dell Latitude CPt400 notebook?
The specs say that it uses a NeoMagic 256AV (alias NM2200)
chipset for video and audio.

Regards,
    Stefan



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Orthogon GmbH, Stuttgart, Germany (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                     14-Sep-99 13:20:19
  To: All                                               14-Sep-99 18:43:06
Subj: Re: Sound card driver needed

From: Phillip Davenport <[e-mail]>

williamd1 <[e-mail]> wrote:
> I am using an AOpen FX 3D Plus card under Warp 3 & Win 95. The chip is
> Analog Devices AD1816AJS. Setup chose the Soundblaster Pro driver
> (with which the card is supposedly compatible)

Remove the SBPro drivers, _nothing_ other than a SBPro will work with
these drivers.

Blow away Multimedia and reinstall, be sure to choose 'None' for audio.

> I assume I need the correct driver for this card. It is unclear to me
> whether an os/2 version is available, and if so, where it may be
> found. The AOpen site does not mention it as one having an os/2
> driver.

And AD hides it.. Here - </ftp://ftp.analog.com/pub/cpdsound/1815_16_16a/>

  p

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Cloudnet - St. Cloud, MN [phone] (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                       14-Sep-99 18:19:23
  To: All                                               14-Sep-99 18:43:06
Subj: Re: Which PCI sound card?

From: [e-mail] (Timo Maier)

Hi Massimo!

>> I don't know what they mean with "a later date", but I think it won't take
>>too long.
>They fixed that some months ago with the new release...
I got ftp://ftp.cirrus.com/pub/drivers/audio/cwos2303.zip
the newest file in this archive are dated 15.04.1999

Can you tell me where I can get the latest drivers?

TAM
--
OS/2 Warp4, Ducati 750SS '92
http://www.privat.toplink.de/homepages/thunder
Remove "_" for eMail reply

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Freiburg/Germany (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                               15-Sep-99 10:09:15
  To: All                                               15-Sep-99 11:00:22
Subj: Re: Drivers for ESS Technology Canyon3D?

From: [e-mail]

In <[e-mail]>,
rjerant@no_spam,austin.rr.com (Rich Jerant) writes:
>On 9 Sep 1999 17:52:08 GMT, doug.bissett"at"ibm.net (Doug Bissett)
>wrote:
>
>>On Thu, 9 Sep 1999 04:09:00, rjerant@no_spam,austin.rr.com (Rich
>>Jerant) wrote:
>>
>>> No unfortunatly none of our Canyon 3D customers  have expressed
>>> interest OS/2 drivers. Which is really too bad because the DMX card is
>>> really nice. I wrote the Win 95/98 driver and was very impressed by
>>> it.
>>> Rich
>>>
>>
>>Now, here is a self defeating attitude.
>Why is that self defeating? This is a buisness, we sell pci audio
>devices to other companies who put them on pc motherboards and sound
>cards. We write whatever driver support they ask for.... OS/2
>included. If none of them request OS/2 drivers for a particluar chip
>we don't write them.  Does this make me happy ?? No not at all I would
>MUCH RATHER write OS/2 drivers than Win95/98, NT or WIN 2000 drivers,
>but it's a buisness, I don't do this for religous reasons I do it
>cause they pay me.
>
>> ** Os/2 user's have not shown  an interest in the card because there are no
OS/2 drivers
>Actually OS/2 drivers for the Canyon3D don't make much sense. The
>Canyon 3D was designed to accelerate direct 3D streams, OS/2 has no
>clue about 3d sound and never will. The DMX card is a great card but
>very expensive, for OS/2 save your money get a $9.00 Solo1 based card
>which has OS/2 drivers.
>..
>> **. On the other hand, OS/2 user's keep on asking (perhaps "begging" is a
better
>>word) for ANY card that is supported, properly, under OS/2. So far,
>>cards using the Crystal chip set (Cirrus logic) are winning the race,
>>because they DO have OS/2 drivers, that DO work, quite well
>Yes I agree Joe Nord has done a teriffic job on Crystal's drivers. But
>ALL of our PCI chips have OS/2 drivers except for M2E and Canyon 3D.
>
>>
>>It would be interesting to know just how many Crystal based cards were
>>sold, because of the OS/2 support.
>And this number would mean what ??
>Let's say that 50 percent of all personal computers that have sound
>and run os/2 have a crystal based audio solution... It's stilll a very
>small percentage of the all personal computers that have sound. The
>sad fact is that OS/2 just doesn't have enough market share to justify
>the resource required to support it.
>>
>>I, personally, have bought 4 of them (not just for OS/2 systems
>>either), and will continue to buy them, as long as they have the best
>>OS/2 support (they work very well in the "other" op systems as well).
>>When someone comes up with something better, I will buy that product.
>And as a American I support your freedom of choice. But if you are
>looking for someone to whine at because the best PC Operating System
>is dying a slow and painful death, go whine at IBM. It is their fault
>nobody cares about OS/2  not mine.....
>
>Rich
>
>
>

Yamaha Axra 3DSound is a low cost 16 bit full duplex PnP card, that comes with
 OS/2 drivers, and is found by OS/2 install, and has the install load OC3 (I
think)
drivers from the CD-ROM set.  Oh, I payed just under $15.00 Canadain for the
card.

The card has the I-Phone Connector, and supports MPU-401, with up to 48KHz
Sampling Rate..  Diagnostics ids it as a Crystal chip set.

RMView /da (I think) finds the card, shows the settings, for you to configure
into the software.

But, the settings for me don't save.  I've not yet used the CD-ROM that came
with the
card.  I guess thats the next step.



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: HARNESS tjhe ABILITY dial up BBS 1-416-604-1221 (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                      15-Sep-99 17:30:19
  To: All                                               15-Sep-99 15:44:15
Subj: Re: SB live and OS/2

From: [e-mail] (Carsten Frank)

On Wed, 15 Sep 1999 02:53:52, "[e-mail]" <[e-mail]>
wrote:

> I recall somewhere reading that IBM was preparing OS/2 drivers for the
> PCI based SoundBlaster Live card as a result of "overwealming" interest
> from user surveys. Any body know the official status of this??
> --
> "Windows N.T."  ........OS/2 for the masses?
>
>

This would be perfect. I hope this rumours will be true.

Ciao

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                  15-Sep-99 16:02:05
  To: All                                               15-Sep-99 21:36:07
Subj: Re: SB live and OS/2

From: "John E. Jones" <[e-mail]>

Has anyone got a fix for this now?

John

<[e-mail]> wrote in message news:[e-mail]...
> I recall somewhere reading that IBM was preparing OS/2 drivers for the
> PCI based SoundBlaster Live card as a result of "overwealming" interest
> from user surveys. Any body know the official status of this??
> --
> "Windows N.T."  ........OS/2 for the masses?
>
>


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Verinet Communications, Inc. (970/224-5551) (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                 15-Sep-99 22:01:23
  To: All                                               15-Sep-99 21:36:07
Subj: Re: DCITU and Canon..

From: [e-mail] (David LaRue)

  Hello Wassimo,

  I don't see any Canon cameras listed in last nights DCITU load.  Perhaps you
should contact the author, Stephane Charette, at [e-mail].
Support
can come pretty quickly if the Canon protocols are documented.

  Good luck,

  David LaRue

In <idHHM8QJdnVy-pn2-oUJf359q6ZcY@localhost>, [e-mail]
(Massimo) writes:
>Does or when DCITU will support Canon digital cameras?
>
>See you.
>
>Massimo S.
>  IBM OS/2 Warp 4
>  Certified Engineer
>  Sys Admin/Web Master
>--------------------------
> http://www.dinosoft.it
> http://www.itline.it/os2
> http://www.quasarbbs.com
>Efnet #Os2ita irc.telia.no
>--------------------------

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Intelligence Network Online, Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                           16-Sep-99 02:15:27
  To: All                                               16-Sep-99 04:30:09
Subj: Re: SB live and OS/2

From: [e-mail] (Ron McDermott)

On Wed, 15 Sep 1999 17:30:39, [e-mail] (Carsten
Frank) wrote:

> On Wed, 15 Sep 1999 02:53:52, "[e-mail]" <[e-mail]>
> wrote:
>
> > I recall somewhere reading that IBM was preparing OS/2 drivers for the
> > PCI based SoundBlaster Live card as a result of "overwealming" interest
> > from user surveys. Any body know the official status of this??
> > --
>
> This would be perfect. I hope this rumours will be true.

Except that a number of motherboards have problems with it (static).
Seems to be a motherboard problem more than a SB problem, but if
you're not getting good sound it really doesn't matter who's "at
fault"!

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                     15-Sep-99 21:18:29
  To: All                                               16-Sep-99 21:19:10
Subj: Re: Which photography applications work well with OS/2 for postprocessi

From: Joseph Loo <[e-mail]>

Try gimp. My understanding it is suppose to be comparable to adobe
photoshop or colorworks.
http://www.netlabs.org/gimp/
On Wed, 01 Sep 1999 20:55:38 GMT, [e-mail] wrote:

>I just got a digital camera today and now I have to find a good
>application to postprocess my photographs (PhotoShop, etc.).
>Which applications will run under OS/2?  How do they run (OS/2
>application, DOS application, Win3.1 Application)?
>

Joseph Loo
[e-mail]


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: rjerant@no_spam,austin.rr.com                     16-Sep-99 05:41:20
  To: All                                               16-Sep-99 21:19:10
Subj: Re: SB live and OS/2

From: rjerant@no_spam,austin.rr.com (Rich Jerant)

On Wed, 15 Sep 1999 02:53:52 GMT, "[e-mail]"
<[e-mail]> wrote:

>I recall somewhere reading that IBM was preparing OS/2 drivers for the
>PCI based SoundBlaster Live card as a result of "overwealming" interest
>from user surveys. Any body know the official status of this??
>--
This is good... there is very LITTLE chance of this happening. There
are NO, NONE , ZERO audio people left on the OS/2 development team.
Which means they will have to pay a outsider to do this work. And
outsiders that are capeable of doing audio drivers do not work cheap.
Unless a major customer pressures them or the IBM PC company starts
using SB live cards (and you can forget that one also) in some of
their products it just won't happen.

Rich

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: rjerant@no_spam,austin.rr.com                     16-Sep-99 05:45:19
  To: All                                               16-Sep-99 21:19:10
Subj: Re: Ensoniq ES1371 Driver

From: rjerant@no_spam,austin.rr.com (Rich Jerant)

On Wed, 15 Sep 1999 10:13:18 GMT, [e-mail] wrote:

>
>>Short of rearranging the cards in my system, any suggestions?  Does
>>anyone know if OS/2 Warp 4 is capable to detecting and using IRQ sharing
>>devices?
It's not a question of OS/2 being able to share irqs between devices.
It's  a matter of whether the device drivers for all the devices on
the irq are capable of sharing.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: rjerant@no_spam,austin.rr.com                     16-Sep-99 05:32:21
  To: All                                               16-Sep-99 21:19:10
Subj: Re: Which PCI sound card?

From: rjerant@no_spam,austin.rr.com (Rich Jerant)

On Tue, 14 Sep 1999 08:41:41 -0400, [e-mail]
(Raphael Tennenbaum) wrote:


>At the moment I'm booting with my old ESS drivers remmed out
>in config.sys.  Can I simply erase these, boot with the
>soundcard installed, and install the drivers?  Other general
>suggestions appreciated.
Well no it's not quite that easy... but it's not that hard either

erase the references to the ess driver from the config.sys.

boot to an OS/2 command prompt and tedit the mmpm2.ini
(C:\MMOS2\MMPM2.INI)
Make sure to boot to an OS/2 prompt befire you edit this file !

Page down the [Drivers] section
delete the following lines:
"Waveaudio="
"Ampmix="
"Sequencer="

File the mmpm2.ini and reboot

After you put the new card in boot OS/2 and go the hardware manager's
property page. Set the detection level for the boot to full hardware
detection.  Close the properties and reboot.

Put the new drivers on any you should be gold..

If you need more detail let me know

Rich

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                 16-Sep-99 14:02:13
  To: All                                               16-Sep-99 21:19:11
Subj: Re: Which PCI sound card?

From: [e-mail] (Mooo)

[e-mail] (Brian {Hamilton Kelly}) wrote:

>If anyone reading *does* know anything about this particular 4280 board,
>I'd be interested in hearing about it.

I use, supply and have had good results with the Pine 4280 based card.
It uses the latest crystal drivers and allows sound in winos2 as well
as os/2

Very nice (and cheap) card.

Craig

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Nothing I say is my own opinion (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                         15-Sep-99 22:05:25
  To: All                                               16-Sep-99 22:38:01
Subj: Re: How do I install support for my SB32 PnP?

From: Anssi Saari <[e-mail]>

[e-mail] writes:

> On Mon, 13 Sep 1999 21:42:50, Anssi Saari <[e-mail]> wrote:
>
> > This is what happens: I install MMOS2, with AWE32PnP selected for
> > soundcard. Result: after reboot WPS won't start, all I get is a popup
> > complaining that the thing pointed to by set runworkplace couldn't
> > start blah blah. And a black screen with a functional mouse
> > cursor.
>
> I remember something like this when I converted to Warp 4 a number of
> years ago.  It was one setting in the soundblaster line that was
> missing and Warp 4 wouldn't install it.  Compare this line and see
> what's different from yours.
>
> DEVICE=F:\MMOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /M:330
> /N:SBAUD1$ /Q /P /G

That's what goes into config.sys by default. I had to change the
address to 240, but it makes no difference whether the driver loads or
not. Well, I tried to restore files based on minstall.log, but that
didn't work either... Still the same thing.

Well, I got it working though. I used Colin Hildinger's fabulous
installation package. It wouldn't complete the installation until I
removed the GUS drivers, though. But now it finally works. Too bad the
SDRAM prices went so high, I probably won't upgrade that soon...

--
Anssi Saari - [e-mail]

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Tampere University of Technology (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                                     17-Sep-99 00:52:12
  To: All                                               17-Sep-99 03:55:00
Subj: Re: Which PCI sound card?

From: [e-mail] (Brian {Hamilton Kelly})

On Thursday, in article <[e-mail]>
     [e-mail] "Mooo" wrote:

> [e-mail] (Brian {Hamilton Kelly}) wrote:
>
> >If anyone reading *does* know anything about this particular 4280 board,
> >I'd be interested in hearing about it.
>
> I use, supply and have had good results with the Pine 4280 based card.
> It uses the latest crystal drivers and allows sound in winos2 as well
> as os/2

Phew!  Thank goodness for that :-)

Just for total clarity, are these "latest drivers" those in cwos2303.zip?

> Very nice (and cheap) card.

That's what I thought, for GBP12.50

--
Brian {Hamilton Kelly}                                         [e-mail]
    "But we're a university.  We /have/ to have a library!..."said Ridcully,
         "What sort of people would we be if we didn't go into the library?"
    "Students", said the Senior Wrangler, morosely. [TP: The Last Continent]

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Dragonhill Systems Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                            16-Sep-99 21:42:14
  To: All                                               17-Sep-99 03:55:00
Subj: Re: How to locate WINOS2 sound error?

From: "Esko Kauppinen" <[e-mail]>

On Sun, 12 Sep 1999 19:23:12 +0200, Mat Nieuwenhoven wrote:

>Hi,
>
>after installing an ESS1688P sound card using the drivers from the ddpak
>online (os21688.zip), The OS/2 side works fine, but the WINOS2 sounds
>don't work. I get a small msg box when starting winos2, titled 'audio'
>but otherwise empy. I presume an error message is supposed to show
>there. Is there a way of logging the error msg somewhere, or make it
>visible in any other way?
>Apart from that, is there a know error with the installation routines
>for the ESS drivers that could cause this? he machine is running Warp4
>FP10 .
>
>Thanks, Mat Nieuwenhoven

Can't tell about the logging but I also have not been able to get the
ESS1688 drivers to work on the WinOS side.

I can get sound from WinOS by using the Sound Blaster drivers but
they are a bit unreliable.

Esko


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: [e-mail]                               17-Sep-99 12:35:25
  To: All                                               17-Sep-99 20:04:19
Subj: Re: Which PCI sound card?

From: Capn Queeg <[e-mail]>

Does anybody have any experience with the Addonics PCI Awesome?
They claim it comes with OS/2 drivers.

http://www.addonics.com/product/awepci.htm

On Thu, 16 Sep 1999 11:38:29 -0400, "David T. Johnson"
<[e-mail]> wrote:

>
>
>Raphael Tennenbaum wrote:
>>
>> Since my sound card blew up, I'm in the market.
>
>I have found the Aureal A3D Vortex 1 card to be very nice for OS/2
>sound.  Digital recording MP3 sound are the best I have heard.  The only
>drawback is that there is no Win-OS2 sound.  I don't use Win-OS2 so this
>isn't a problem.  I have found four Aureal 8820-based cards. All are
>available retail at CompUSA so I have also listed the CompUSA SKU# and
>the retail price.
>

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Paranioa (1:109/42)

+----------------------------------------------------------------------------+

+============================================================================+