🚀 go-pugleaf

In article <74ccdh$sg3@catapult.gatech.edu>, willday@rom.oit.gatech.edu 
says ...

>Second, you might also want to include comp.sys.ibm.pc.games.action,
>since it's specific to Half-Life.  I know lots of people keep up with the
>Half-Life traffic there.  And if you're including alt groups, you
>probably want to add alt.games.half-life as well.

This is the problem with the Internet.  Instead of having one place to 
handle something, we have so many places.  Please feel free to share any 
information with those groups.  I don't want to waste any more bandwith 
than I am already.    :)

>Third, let me share with you my post from last week.  Be warned, it's a
>bit of a rant:

I'm used to it.     :)

>    First, as drivers, I find these files highly suspect.  They look
>    entirely unlike any drivers I've downloaded from Aureal before.  The
>    zip file contains only the 3 DLLs/VXDs.  Where's the usual raft of
>    files - large variety of VXDs, help files, and especially INF files?
>    Is this a real driver release, or just a pseudo/hack release?

Maybe this needs some explaining.  With your A3D card, you have two sets 
of drivers.  One set of drivers powers your chipset - this allows you your 
WAVE, MIDI, etc functionality.  These differ from sound card to sound 
card.  There is also a second set of drivers - the A3D drivers.  These are 
only used when an A3D game calls them.  There is no INF or install or help 
files.  You just copy the two files into your Windows System folder.  
These drivers are not card specific; they work with all true A3D cards.  
So, it is a real driver release and not a hack.  Having this dual 
architecture makes it easier for us to upgrade drivers for all our various 
users whether they have a card based on the Vortex 1, Vortex 2, Diamond 
Freedom PCI, Oak OTI-610, or any other true A3D-capable chipset.  It also 
reduces your download time.  The lack of a README was a little good, and I 
will correct that on Monday.

>    Second, the directions are equally questionable.  

I will correct that on Monday.

>    Third, a previous set of supposed a3d 2.0 drivers I downloaded
>    included a windows registry file, which I was loathe to apply
>    because, as I said, it all seemed rather suspect.  

I believe this was removed because we believed that the Half Life patch 
had incorporated this.  If we find that it hasn't done so, or done so 
correctly, we will include it again.  All this patch does is register the 
A3DAPI.DLL file so that games that call it will do so correctly.


------------------------------------------------------------
David A Gasior                           h: dgasior@home.com
Developer Relations, Aureal               w: dgasior@a3d.com
------------------------------------------------------------
Please note that this post reflects my own opinions, and not
necessarily those of my employer.