GUS Daily Digest            Tue, 18 Oct 94  9:37 PST     Volume 15: Issue  11 

Today's Topics:
						   Announcing 2PAT
	  Can I get the Gravis Piano teaching system software only ?
						  Contacting Gravis
			   FAQ: Gravis Ultrasound ("GUS") FAQ v1.55
				 First encounter with the HMI-driver
						  GNN October Update
					 GUS & CDROM problem (2 msgs)
							   gus0043
					GUS CD in polled mode (answer)
						GUS Daily Digest V0 #1
				  GUS Daily Digest V15 #10 (5 msgs)
				   GUS Daily Digest V15 #8 (2 msgs)
					Latest version of GUS software
						Master of Magic & GUS
						Masters of Magic / GUS
					   mega-em and Tie-Fighter
						  Origin GUS support
					 Origins GUS Support (2 msgs)
						  Promotion J"urgen
						  Space Hulk and MOM
	  To the attention of the staff at Gravis! Reg. card probs.
						  which type of DRAM

Standard Info:
	- Meta-info about the GUS can be found at the end of the Digest.
	- Before you ask a question, please READ THE FAQ.

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

Date: Mon, 17 Oct 94 22:36:28 +0100
From: f93-maj@nada.kth.se
Subject: Re: Announcing 2PAT

>>  Licensing policy has changed to Shareware, so now you MUST pay a small fee
>>  to get the legal right to use it. See REGISTER.TXT.
>Hey, are you serious ? You didn't say anything about 2PAT going to be
>a shareware when you asked all the Ensoniq EPS information from me.
>I mean, I don't want any money for it or so, but this sounds strange
>to me. You surely did a lot of work yourself, but the product is strongly
>based on the "shared Internet knowledge" collected by many people for
>free.
>Just wanted to say this.
>                                 Martin Grecner

It is indeed based on information gained mostly from "shared Internet
knowledge", but, and I must point this out, this doesn't mean that all the
work I've put into it, not just in collecting all the information (and there IS
professionals making a living on collecting'free'information for other people),
but also implementing it and spending many many hours coding and testing it,
should count for nothing.

Information in itself is worth nothing if not put to use; and the information
is still 'free' and no less 'shared'. The very meaning of thoose words implies
that anyone may do whatever he/she wants with it (including basing comercial
product upon it, e.g. what does a newpaper consist of? (apart from severly
degenerated trees and some ink i.e.)), and I have never, ever denied anyone who
have asked for it any of the file format info I've collected during my work, so
if anyone wants to spend all the time required to do it themselves rather than
use my work, well, be my guest...

The reason the initial versions were not Shareware was that I did not think
it functional and/or bug free enough to ask any money for it, I certainly
hope now one that has submitted info to me feels cheated by this, but remember
that v0.0 through v1.1 were and still are free. Besides it's clearly stated in
the licensing terms for previous versions that the licensing policy could
change any time.

And I really don't think it is immoral to ask that you pay a small sum to me
if you choose to use it (perhaps even getting money for product created using
it) on a regular basis (wich is what the license covers, perhaps I used a
little to strong phrasing in the revision history, of course you can 'evaluate'
the software for free before agreeing to anything (as with all Shareware)),also
unlike many others, a license for 2PAT is a one time cost, it covers all future
versions as well and I have choosen to distribute a fully functional version of
the software and not some crippled stuff.
For people submitting info for future versions,see it like this,for absolutely
no extra charge whatsoever, I will spend a considerable amount of time
implementing the features you want, what 'commercial' companies would do that?

It's on your consiousness wether you think all the work I've put into it is
worth the small fee I'm asking for it, or not.

Just wanted to say this, hope I've not wasted too much bandwidth,


regards,        F. Markus J.

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

Date: Mon, 17 Oct 94 10:37:53 -0700
From: Fred Handloser <fredh@hpcvusd.cv.hp.com>
Subject: Can I get the Gravis Piano teaching system software only ?

I got a brochure the other day advertising the Gravis Piano teaching
package.   It includes a lot of stuff including a GUS card and
a MIDI keyboard.   I already have a GUS and a MIDI keyboard so I
was wondering if any of you had heard of a "software only" 
package for this teaching system.

Fred Handloser
Corvallis, Oregon

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

Date: Mon, 17 Oct 1994 10:11:39 -0700 (PDT)
From: Doug Whittier <COMPTEC93063@camins.Camosun.BC.CA>
Subject: Contacting Gravis

-Hi, I posted this around the time the list first started back up and didn't
-get any response so maybe nobody read it.  Anyway, here it is again, and
-I really need some help.  Even just a name and address where I can reach
-Gravis at directly would be a big help.  I'd hate to junk the entire board
-just because one little GAL burned out.


Phone (604) 431-5020 for main line, or 431-1807 for tech support.
Or, mail to tech@gravis.com

Cheers.

Doug Whittier

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

From: Matthew E. Bernold <MEB117@psuvm.psu.edu>
Subject: FAQ: Gravis Ultrasound ("GUS") FAQ v1.55

ReprintFrom: comp.sys.ibm.pc.soundcard,comp.music,rec.music.makers.synth,

Archive-Name: PCsoundcards/gravis-ultrasound/faq
Last-Modified: 94/02/26
Version: 1.55


		GRAVIS ULTRASOUND ("GUS") FAQ VERSION 1.55 [94/02/26]

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

QUICK NOTE: There is now a file posted that lists changes to the current
			FAQ from the last posting.  This file is intended for those
			of you out there who have already read the FAQ, and don't
			want to have to read it all again to find changes.  Look for
			it to be posted along with the FAQ.

		Certain questions concerning the Gravis UltraSound ("GUS")
sound card are asked over and over on the UltraSound Daily Digest (a
mailing list for GUS users) and on comp.sys.ibm.pc.soundcard.  In an
attempt to alleviate some redundancy from the lives of USENET/Internet
folk, this FAQ (Frequently Asked Questions, with answers) list has
been created.  It is maintained by Matthew Bernold (MEB117@PSUVM.PSU.EDU)
If you have any questions, comments, complaints, or extra cash, (especially
the cash) please feel free to send them to him.  Please do not send your
question more than once, as Matthew does have other things to do aside from
answering FAQ mail.  If you do not get an answer after a month or so, then
there may be a mail problem.  :-)

NOTE: All submissions by mail to the GUS FAQ must have a subject line that
	  looks like one of the following:

	  Subject: GUS FAQ Q*: rest of subject
	  Subject: GUS FAQ: rest of subject

	  If the submission refers to a specific question in the FAQ, use the
	  first subject line and replace "*" with the question number.

	  Any FAQ submissions that do not have the proper Subject line may be
	  deleted accidentally while I'm sifting through my mail discarding junk,
	  so please, for my sanity, try to use the Subject lines above.

		If you would like to join the mailing list and be privy to the
latest and greatest information, banter, and poor spelling concerning
the GUS, mail to <gus-general-request@mail.orst.edu>.  The automated
server will tell you how to sign up for the mailing list, tell you
where the FTP sites associated with the Digest are (they recieve
software updates directly from Gravis often), and other such
information that will eventually lead you down the trail to Nirvana,
Valhalla, Heaven, or whatever Land O' Happiness your religion wants to
get to.

		BTW: All FAQs, including this one, are available on the
archive site rtfm.mit.edu in the directory pub/usenet/news.answers.
The name under which a FAQ is archived appears in the "Archive-Name:"
line at the top of the article.  This FAQ is archived as
PCsoundcards/gravis-ultrasound/faq.

		Special thanks are due to many people who helped (and are
helping) with this FAQ.  I won't try to name off people; I'll probably
forget half of you, and you all know who you are, anyway.

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

		BIG IMPORTANT NOTE: Neither this FAQ, the mailing lists or
digests, nor the FTP sites are owned or operated by Gravis.  Gravis
employees *read* the digest and mailing lists and they upload things
to the FTP sites, but that's it.

		SO: Please don't email me about problems with your card, if
the latest release of software hasn't arrived on disks in the mail
yet, lack of documentation, etc., etc.  I'm doing this on my own time,
and I have no desire to receive hate mail intended for Gravis.

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

Index of Questions
------------------
		 1] What is the GUS?
		 2] How does the GUS emulate other soundcards?
		 3] Where can I get a GUS, and how much will it cost?
		 4] What version of the GUS hardware is the latest?
		 5] What GUS software is available?  What version is it?
		 6] Where can I get the latest GUS software?
			(AKA: Where is the GUS FTP site and/or Gravis BBS?)
				6a] What if I don't have FTP access?
		 7] What machines will the GUS work with?
				7a] I've heard about problems with the OPTi chipset...
		 8] Why should I upgrade the memory onboard my GUS?
		 9] Where can I get memory for the GUS, and how much will it cost?
		10] I'm having trouble getting the GUS to work with Windows...
		11] What new hardware is coming out for the GUS?
		12] How do I build the MIDI interface for the GUS?
		13] What exactly is GUS 3D?
		14] What are *.PAT *.VOC *.WAV *.SND *.MOD *.669, and *.MID
				files, and how do I use them?
		15] What exactly is Wavetable Synthesis?
		16] Is there a GUS device driver for Linux/BSD386/*IX?
		17] How do I get the GUS to work with OS/2?
		18] How do I go about programming the GUS?
		19] What are the pinouts for the CD Audio IN on the GUS?
		20] I'm having trouble with... GENERAL TROUBLESHOOTING TIPS
		21] I can't seem to fit the new disks onto a floppy.
		22] Why shouldn't I use the comp.sys.ibm.pc.soundcard.GUS
				newgroup?
		23] What are "Miles Drivers", and how do I use them?
		24] Where can I find more information on the GUS?

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

 1] What is the GUS?

		The Gravis UltraSound (generall referred to as the "GUS") is a
sound card built by Advanced Gravis Technologies (GRVSF on the Nasdaq
exchange).  It is a stereo card that can play 32 synthesized voices
and 32 sampled voices simultaneously.  It is also MIDI compatible.

		The synthesizer on the GUS is based on a technology called
Wavetable Synthesis (WS) instead of FM synthesis (like the Adlib and
Soundblaster series).  WS is flexible enough to emulate FM synthesis,
and so an emulator has been created so SoundBlaster and Adlib programs
can use the GUS (see question #2).

		The GUS, in its basic state, can sample 8 bit stereo at 44kHz.
It can playback 16 bit stereo samples at 44kHz.  There is a
daughterboard that you can buy (to be released) and plug on to the GUS
that makes it possible to sample at 16 bit stereo 44kHz.

		Each voice can play independantly, but as the maximum number
of voices goes up, the sample playback rate drops.  With 14 active
voices, the GUS can playback at 44100Hz.  At 28 active voices, the
playback rate drops to 22050Hz.  With the maximum 32 voices, the GUS
can playback at a rate of 19293Hz.  Following is a chart taken from the
GUS SDK v2.01 listing the number of active voices and the playback rate.

  Active   Playback    Active   Playback    Active   Playback
  voices     rate      voices     rate      voices     rate
	14      44100        21      29400        27      22866
	15      41160        22      28063        28      22050
	16      38587        23      26843        29      21289
	17      36317        24      25725        30      20580
	18      34300        25      24696        31      19916
	19      32494        26      23746        32      19293
	20      30870

		If you tell the GUS to play at a different rate than listed
above, the GF1 processor automatically interpolates the sample, and
simulates playback at the desired rate.

		Each voice also has 15 panning positions, and 4096 settings of
volume.  The GUS has automated volume-ramping that can be used as
one-shot or oscillating volume modulators.  Thus, amplitude envelopes
use very little CPU horsepower.  For more technical information, read
the GUS SDK (see question #24).

		The GUS has the following "external" ports:
		o Stereo line in
		o Stereo line out
		o Stereo amplified out
		o Stereo microphone in
		o Game port / MIDI port

		The GUS has several "internal" ports, including:
		o CD Audio IN
		o Expansion ports for daughtercards (see question #15).
		o Other as of yet unexplained pins/ports.

		The game port can be changed to MIDI in/out/through ports by
means of an adapter available from Gravis.  Alternatively (and for a
LOT less money) you can build your own (see question #17).

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

 2] How does the GUS emulate other soundcards?

		Right now, there are several ways the GUS may emulate other
soundcards/soundcard combinations.  Following is a list of combinations
that the GUS may emulate, and the program to be used for this emulation:

		Sound Blaster/Adlib        SBOS
		Roland/SB Digital          MegaEm
		General MIDI/SB Digital    MegaEm

-----
Written by: Don ????? (????@????????)  Don, please get in touch so I
									   can fix this.

		The GUS can currently emulate the Sound Blaster (mono), and also
the Roland MT32/LAPC1 and Sound Canvas, and even a combination of
Roland+SB.

		The Sound Blaster FM music emulation is provided by a software
program called SBOS - Sound Board Operating System.  This is a TSR which
links to the Non-Maskable Interrupt (NMI).  SBOS is currently supplied
with the GUS but is continually being updated.

   [NOTE: A small number of motherboards have the NMI disabled.  This
   is unacceptable practice and makes the motherboard not IBM-AT
   compatible.  There may be a jumper to re-enable it.  You should be
   within your rights to demand a motherboard with NMI enabled.  If you
   have this problem help is around the corner - read on..]

		The emulation quality depends on the particular game but ranges
from very comparable to yuck, much of which is personal preference.
However FM synthesis as used by the Sound Blaster never sounds good
compared the GUS's native sound and other emulations.

		Sound Blaster DAC emulation is provided by two programs - SBOS,
(giving full SBemulation for games), and Mega-em.

		The latest version as of 18Jan94 of SBOS is 3.7.  This is
available at the FTP archive sites and Gravis support BBSs around the
world.

		Mega-em also provides the Roland MT32/LAPC1 and Sound Canvas
cards emulations.  Mega-em uses no conventional memory but does require
and EMS memory manager suchas EMM386.EXE,QEMM,etc.

		A lot of older games support MT32.  Most new games support the
Sound Canvas as a'General MIDI' device.  These games expect these
devices to be connected to a MPU-401 compatible MIDI port and Mega-em
emulates this.  Mega-em then sets up theGUS's patches to match either
the MT32 or General MIDI.

		The sound quality of Mega-em is very good.  Emulation of General
MIDI is better than MT32.

   [Many games support the MT32 by reprogramming it's patches to create
   new sound effects and new instruments.  Mega-em cannot emulate these
   new instruments on thefly so some instruments/sfx may sound quite
   wrong.  However you can manually replace patches in Mega-em's setup
   to more closely match the desired instrument/sfx.]

		Mega-em's SBDAC emulation means that you can use General MIDI
for the music andSB for the sfx on many games.  Only versions later than
2.3b support SBDAC.

		This program is available the same places as SBOS but is not
currently suppliedwith the GUS and it's free.  Latest version is 2.02

		Now the good news for NMI problems, it is planned for Mega-em to
support the Sound Blaster's FM music in the near future.  It is also
probable that Mega-em will provide full MPU-401 emulation for the GUS
MIDI port under DOS.
-----

The G-List:  (See also Q24)

		There is a GUS compatibility list available from the GUS FTP
sites.  It is called the G-List (glist.zip).  This list tells you
what programs work with the GUS, how well they work, and how you get
them to work with your card (which emulator to use).  It also tells
you the latest version of the emulators, and where to find them.

		The author of this program, Marc Paulin
(markus@clement.info.umoncton.ca), has made this program available by
posting to netnews weekly, placing the latest version on the FTP sites,
and by making the G-List his .plan file.  If you can use finger, you can
get the G-List by typing:

		finger markus@clement.info.umoncton.ca

In unix, to put this in a file glist.txt, type:

		finger markus@clement.info.umoncton.ca > glist.txt

For other operating systems, ask your sysadmin.

		This list is based on contributions from GUS users, so if you
find a mistake in the list, or try a new game that works with the GUS,
or anything else, mail him with the info.

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

 3] Where can I get a GUS, and how much will it cost?

		The "suggested retail" for the card is $200 (U.S. dollars),
but if you pay that much, you haven't done your homework.  However,
homework on this card isn't easy because Gravis still hasn't actually
advertised (they have a weird policy concerning advertising).

Here are some mail order places that supposedly carry the GUS.  Since
prices tend to change faster than FAQs, I am not posting prices.  For
our non-american users, there are some FAX or non-800 numbers as well.

Vendor                 800 Number          FAX             Voice
Bit Wit Software     1-800-259-2453   1-214-306-9603   1-214-539-5473
Chips & Bits         1-800-753-4263   1-802-767-3382   1-802-767-3033
Computer Express     1-800-228-7449   1-508-443-5645
Disk-Count Software  1-800-448-6658   1-908-396-8881   1-908-396-8880
Incredible Universe                                    1-503-682-8100
Mission Control      1-800-999-7995   1-201-677-9484   1-201-677-1400
Viking Software      1-800-852-6187   1-404-840-7925
Zeroes & Ones        1-800-788-2193   1-702-897-1571

		If you call around, you should have no trouble getting the GUS
for less than $150.  Suggested places are Babbages, Bizmart, OfficeMax,
and Disk-Count software.

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

 4] What version of the GUS hardware is the latest?

		This is a question that is actually pretty irrelevant.  Yes,
there have been different "releases" of the GUS card (the number is
etched into the board), but there really aren't any differences.
Evidently, some of the newer cards have been redesigned to require
less hardware (and less cost to Gravis), but no functionality changes
have been made.

		Also, the newest versions of the GUS (v3.4+) have volume
control on some of the inputs, and adds an on/off and volume control
on the CD input.  The new windows mixer takes advantage of this.
If you have an older GUS, the mixer just grays out the volume sliders.

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

 5] What version of the GUS software is the latest?


	Title       Ver    Filename   Where?
	---------  -----   ---------  -------
	Install    2.06L              GUS FTP
			   2.06               Mailed by Gravis to Registered owners
	SBOS       3.7B2              GUS FTP
	MegaEm     2.02               GUS FTP
	UltraMID   2.06               GUS FTP

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

 6] Where can I get the latest GUS software?
	(AKA: Where is the GUS FTP site and/or Gravis BBS?)

		Ok everyone, here it is.  archive.epas.utoronto.ca will now
hold ONLY submissions and the latest files. (files that were validated
during the previous validation period)  The main archive site for
the ultrasound will now be:
	archive.orst.edu /pub/packages/gravis

		This site will hold all gus files, INCLUDING the submit directory
mirrored VERY frequently.  The rest of the sites will hold all gus files
as well, but may or may not mirror the /submit directory.

		Submissions will still be taken at archive.epas.utoronto.ca
in the /submit directory as they always have.

GUS FTP sites:

	North America:
		archive.orst.edu             /pub/packages/gravis
		wuarchive.wustl.edu          /systems/ibmpc/ultrasound

	Europe:
		theoris.rz.uni-konstanz.de   /pub/sound/gus

	Asia:
		nctuccca.edu.tw              /PC/ultrasound

	Submissions and newly validated files:
		archive.epas.utoronto.ca     /pub/pc/ultrasound

GUS Mailserver:
		mail-server@nike.rz.uni-konstanz.de

		NOTE: theoris is a low-bandwidth site.  The sysadmins have
requested that ONLY european users access the GUS archive from that
site.  Please respect this, or it might disappear.

		BTW: You can get a LOT more than just GUS software releases
from Gravis on the FTP sites.  There's lots of PD software written
specifically for the GUS, music (midi music, midi patches, mods, 669
music, samples, etc., etc), tech info on the card, back issues of the
UltraSound Daily Digest, etc., etc... check it out!

Gravis BBS:
		(604) 431-5927

6a] What if I don't have FTP access?

		Use the GUS Mailserver!

		Send mail to mail-server@nike.rz.uni-konstanz.de with the body
of the message as follows:

		begin
		send help
		end

		Alternatively, you can call the Gravis BBS.  There are several
major disadvantages with this, though:

		1] Long distance to Canada (no offense to you Canadians :).
		2] 2400 baud.
		3] The BBS doesn't have all the public domain stuff that
				the FTP sites do.
		4] It's almost *always* busy.

		Please *DO NOT* ask people to post binaries to
comp.sys.ibm.pc.soundcard.  It's not a binary newsgroup, and that's a
lot of wasted bandwidth to people who don't want the programs.  Use
email.  It saves bandwidth, fights cavities, and builds character.

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

 7] What machines will the GUS work with?

		You need an IBM compatible computer with at least a 286
processor.  It needs to be at least a 386 if you want to use the GUS
with Windows.

7a] I've heard about problems with the OPTi chipset...

		There have been troubles with the GUS if your computer's
chipset is made by OPTI.  Not all OPTI chipsets are bad, but some of
them have a faulty DMA controller.  We're still trying to pin down
which chipsets are flawed; when we have a better idea of exactly which
ones are bad they'll be added here.  Until then, be careful if your
computer has an OPTI set, and try reading the UltraSound Daily Digest,
or comp.sys.ibm.pc.soundcard on USENET.

Written by: dantonio@magick.tay2.dec.com
		Actually, it's not just OPTi chipsets, UMC has been implicated
as well (Gravis first noticed the problem with UMC chipsets) and
according to Digital Audio Labs (who told Gravis what was going on),
the bad datacode is 9149 and the bad chip is the 82C206.  This is all
explained in the docs for GUS0013.ZIP (I think), the OPTi fix posted
to the GUS FTP sites.

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

 8] Why should I upgrade the memory onboard my GUS?

		For starters, the announcement has already come out of Gravis
that the standard GUS will come with 512k instead of 256k.  This means
that software companies will write their programs to use *at least*
512k onboard the GUS.  And with all the users going to 1meg, chances
are that things will be written for that limit.

		It's a cheap upgrade.  If your board came with 256k, it will
only cost you about $30 to go up to 1meg (see question #10).

		There's already a lot of MIDI files out there that require the
full 1meg to play them, because they use lots of different instrument
patches.

		If you plan on doing any sampling, you'll need the space.  You
can do direct-to-disk sampling, but it can cause "skips" to go into
the sample each time the sample goes down the bus to the drive.  In a
worst case situation, you could be sampling 16 bits in stereo at
44kHz.  So, you're doing 88000 samples (stereo, remember) of 16 bits
each every second.  That's 171k (176000 bytes) every second, which
means the full 1meg memory will fill up in 5 seconds at that rate.
With only 256k, you can get about 1.5 seconds.

		Of course, only people doing very serious stuff with the card
need to sample at that high of a rate in 16 bits.  MOD files generally
do 16kHz 8 bit mono samples.  But upgrading the card is still pretty
important in that case... do the math, and you'll see.

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

 9] Where can I get memory for the GUS, and how much will it cost?

		You need six 256x4 DRAM chips, with speeds of 80ns or better
(in other words, 80ns OR LESS).  They tend to run about $4 a piece, so
the total price will be $24 + shipping.  Make sure you ask for
"page mode" ram, or they will not work correctly with your GUS.

		To find  a  place with them, just  look through  the  Computer
Shopper magazine.  Check the index for  'memory' and call a few places
for prices.  (After a little calling, I found a place selling them for
$3.45 apiece.)

		To ensure compatibility, look for the number "44256" in the
chip number.  If you do not see this number, you probably do not have
the right chip.

		NEW NOTE: Gravis is now offering to sell the chips directly to
you for a much lower cost (they can buy in bulk).  Give them a call
for latest chip prices.

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

10] I'm having trouble getting the GUS to work with Windows...

		There in one possibility that accounts for about 50% of the
problems people have with the GUS and Windows: you can't have SBOS
loaded before going to Windows.  (You don't need it... if the Windows
program was written right, Windows will handle the link to the card;
the program shouldn't care.)  Try running ULTRINIT (it clears the GUS'
program memory), or rebooting.

		Other problems:

(a) No sound at all in Windows...

Written by: dantonio@magick.tay2.dec.com
		People often put ultrasnd.ini into \windows\system which they
shouldn't.  They SHOULD put \ultrasnd\windows\midimap.cfg into
\windows\system to get the MIDI stuff setup correctly.

(b) I'm not getting any sound when I play MIDI files under Windows.
		The Patch Manager shows empty boxes.

Written by: bs@mda.ca (Bruce Sharpe)
		You need a file  called ULTRASND.INI.  You  can find this file
in any one of the following places:

		1. The v2.06 distribution disk set.
		2. One of the GUS FTP sites.
		3. The Gravis BBS.
		4. CompuServe: GO PCVENB, Library 14, name is ULTSND.INI
				(rename it to ULTRASND.INI after downloading).

		ULTRASND.INI must be placed in the directory pointed to by the
environment variable ULTRADIR (usually C:\ULTRASND).  It does *not* go
into the WINDOWS or WINDOWS\SYSTEM directory.

		Even if you have an ULTRASND.INI in your ULTRADIR directory,
look at it.  It should have many lines in it saying things like
"0=acpiano".  If it is only a few lines long, get another copy and put
it into the ULTRADIR directory.  Reboot Windows and you will soon be
hearing beautiful music!

		(The purpose of the ULTRASND.INI file is to let the Windows
driver know what patch file goes with what patch number.  If the
driver doesn't find the .INI file in the ULTRADIR directory it creates
a truncated version with no patch names in it.)

(c) All the list boxes are blacked out in the UltraSound Patch
		Manager.

Written by: bs@mda.ca (Bruce Sharpe)
		This was a problem that was fixed in v1.02.  It only occurs in
certain Windows color schemes (e.g., Ocean).  If you can't get your
hands on a more recent PatchManager, then change your color scheme.

(d) Other general Windows/GUS problems.

Written by: john.smith@gravis.com (John Smith)
		At least one major problem people have been having with the
new release has been solved.  Many thanks to Fransisco Perez. He
noticed that he had a grvsultr.386 file in his \windows directory and
it was NOT the new one.  Apparently, windows looks in the path and
uses the first one that it finds. It should have gotten the one in the
windows\system directory. Using the old one with the new patches etc.
causes SERIOUS problems. The old install software required the user to
copy some things manually and some people put the files in the windows
directory instead of the windows\system directory.  The new install
will install windows automatically and puts the files in the
windows\system directory.  To correct the problem, make sure the
following files are in your windows\system and ultrasnd\windows
directory ONLY!!!  If you find them anywhere else, you should remove
them....


 ..\windows\system\
	grvsultr.386                     <
	midimap.cfg                      < These files are also located
	ultmport.drv                     < in the UltraSnd\Windows
	ultrasnd.drv                     <

 ..\ultrasnd\
	ultrasnd.ini

 ..\ultrasnd\windows\
	ultrasnd.ini
	oemsetup.inf
	mixer.exe
	patchmgr.exe
	patchmgr.hlp
	ultrahlp.hlp

		Some of you have been trying to re-run the automatic Windows
install simply by running WINGUS from your UltraSound\Windows
directory.  The problem with this is WINGUS is looking for an install
script file that has an extension of .INF.  The first file it
encounters is OEMSETUP.INF, which it trys to execute but because this
is NOT a script file you will get MANY error messages.  Try renaming
OEMSETUP.INF to OEM.TMP then run WINGUS.  WINGUS will then see WIN.INF
and load that instead.

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

11] What new hardware is coming out for the GUS?

Ed. Note: I know this list is out of date, but I don't have anything
		  better/more up to date, so I'm leaving it.  If you have
		  some more recent info, let me know, and I'll put it in here.

Written by: Bruce Sharpe (bs@mda.ca)

   -------------------------------------------------------------------
   | Advanced Gravis Product Support BBS      Pricing & Availability |
   -------------------------------------------------------------------
   |                Item                           When?    SRP($US) |
   -------------------------------------------------------------------
   | MIDI Connector Box                        |  Apr '93  |  $49.95 |
   | 16-bit Stereo Recording Interface Card    |  Apr '93  | $149.95 |
   | LMSI CD-ROM Daughter Card for CM205 and   | Qtr 1 '93 |  $59.95 |
   |  and CM215 (Phillips, Magnavox, LMSI)     |           |         |
   | Sony CD-ROM Daughter Card for Sony 31A    | Qtr 1 '93 |  $49.95 |
   | Mitsumi CD-ROM Daughter Card              | Qtr 1 '93 |  $49.95 |
   | SCSI CD-ROM Daughter Card                 | Qtr 1 '93 |   TBA   |
   -------------------------------------------------------------------

Details?  Good question.

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

12] How do I build the MIDI interface for the GUS?

Written by: pcunnell@micrognosis.co.uk (Paul Cunnell)

> Has anyone made the midi interface for the GUS that is in the FAQ?
> If so, were did you find the part# 6N138?  I cant seem to locate
> this anywhere.  Also, (excuse my ingorance i'm not an EE) but
> what exactly is that part and its purpose? Thanks...

		The 6N138 is a high sensitivity opto-isolator, manufactured by
Hewlett Packard (and I believe, a company called Quality Technology)
The main point in using this part as opposed to other more common
opto-isolators is the low LED ON current spec. (1.6mA)

		A midi out circuit is basically a LED in series with 600 ohms,
and a 5V supply. Taking into account the 1.7V forward drop across the
LED, you get about 5mA in the on state.  Other optos generally need
more current to turn them on (say 15-60mA, but this varies a lot). A
'high speed' 6N137 opto will also work, I believe, but that would be a
bit marginal on the input current (spec. is min 5mA).

		Since a number of people have been asking, I'll add below the
midi circuit that I'm using, plus a bit of general explanation I've
culled from other peoples' postings on the subject.

Generic Midi Out/In/Through Circuit
===================================

The following shows a typical OUT, cable, and IN circuit

	  MIDI OUT port ---->|<- cable ->|<---- MIDI IN port              +5V
																 270   |
			+5V        DIN           DIN                     +--\/\/\/-+
			 |  220    +-+ +-------+ +-+   220    +--------+ |
		|\   +-\/\/\/--|4|-|-------|-|4|--\/\/\/--|  OPTO  |-+-+- UART RXD
 UART   | \            | | |       | | |          |ISOLATOR|   |
 TXD ---|  \---\/\/\/--|5|-|-------|-|5|----------|        |-+ |
		|  /    220    | | +-------+ | |          +--------+ | |
		| /         +--|2|-+       +-|2|            6N138   GND|
		|/ 7407     |  +-+           +-+                       |
				   GND                                         |
															   |
				   +-------------------------------------------+
				   |
				   |      +5V        DIN
				   |       |  220    +-+
				   |  |\   +-\/\/\/--|4|
				   |  | \            | |
				   +--|  \---\/\/\/--|5|   MIDI THRU
					  |  /    220    | |
					  | /         +--|2|
					  |/ 7407     |  +-+
								 GND

		Note that when the UART TXD is high, no current flows through
the resistors and optoisolator's LED, causing the optoisolator's
phototransistor to remain off, allowing the UART RXD to be pulled high
by the 270 ohm resistor.  When the UART TXD is low, current flows
through the resistors and optoisolator's LED, turning on
optoisolator's phototransistor, grounding the UART RXD.  The voltage
drop across the optoisolator's LED is typically 1.5 volts, leaving 3.5
volts to be dropped across (3 times 220) 660 ohms, which allows about
5 ma to flow.

		The reason a current loop is used is that it allows an ground
isolated interconnection.  Note that the ground from the MIDI OUT
port's device is not connected to the ground of the MIDI IN port's
device.  This prevents ground loops in systems where appropriate
attention has not been paid to grounding issues, such as the case of
typical musicians in a typical club!

Gravis Ultrasound Circuit
=========================

15 pin D connector
										  220R
pin-1 +5v ----+--------------------------/\/\/\---------------\
			  |                                                \ 4
			  |                                          Gnd--2   MIDI OUT
			  |      |\      |\            220R                / 5
pin-12 tr >---|------| o-----| o----------/\/\/\--------------/
			  |    13|/ 12 11|/ 10
			  |                            220R
			  +---------------------------/\/\/\-------------\
			  |                                               \ 4
pin-15 rx <---|--------------------+                    Gnd--2    MIDI THRU
			  |      |\      |\    |        220R              / 5
			  |   +--| o-----| o---+-------/\/\/\------------/
			  |   | 1|/ 2   3|/ 4
			  |   |
			  |   +------+
			  |   270R   |                       220R
			  +--/\/\/\--+    +------+----------/\/\/\--------\
			  |B         |C   |A     |                         \  4
			+-|----------|----|-+    |                             MIDI IN
			|  8        6     2 |  -----                       /  5
			|                   |   / \ IN914 or IN4148     +-/
			|      6N138        |   ---                     |
			|                   |    |                      |
			|           5     3 |    |                      |
			+------------|----|-+    |                      |
						 |    |K     |                      |
pin-5 Gnd  --------------+    +------+----------------------+

		Inverters are 74LS04. (This is a 14-pin IC containing 6
inverters.  Connect pin 14 to +5V, pin 7 to GND)

		Leave pin 2 of the MIDI IN unconnected (Don't connect to ground).

Some hints for testing your circuit
===================================

		1] Check *all* connections (use a continuity tester, and tick
them off on a printout of the circuit).

		2] Check them again ;-)

		3] Make sure you have the latest (GUS0012.zip) windows midi
driver, and make sure it is installed properly.

		4] Make sure your midi sequencer package is set up to use the
Ultrasound Midi In/Out ports. (As opposed to the Ultrasound Synth)

		5] If you still have no joy,

				a] Just connect the +5V and GND to your midi circuit,
		(leave the d-connector pins 12 and 15 unconnected), and then
		connect pin 13 of the 7404 to +5V check you have (about) +5V
		appearing on pin 10.  This checks midi out.

				b] Connect pin 4 of the midi-in DIN socket via 2 extra
		220R resistors to +5V.  Check pin 4 of the 7404.  It should be
		low (about 0V).  Then connect pin 4 of the midi-in DIN socket
		to 0V.  Pin 4 of the 7404 should go high.  This checks midi in.

				c] Reconnect the d-type pins 12 and 15, and connect a
		midi cable between midi-out on the circuit and and midi-in on
		your synth.  Set up your sequencer to use the Ultrasound MIDI
		port as an output, and ensure that one of the tracks is set to
		use this port.  Check your synth is expecting MIDI data on the
		same channel as sequencer is transmitting.  Start sequencer
		playing.  Check that midi data is being transmitted at pin 12
		of the d-type (look at it with an oscilloscope, if possible).

Note
====

		Standard disclaimers apply - use this information at your own
risk, and if your fry your card/PC/synth/toaster, then you have my
sympathy, but not much else ;-)

		If you're not happy about messing with circuits and soldering
irons and wires and stuff, then you may wish to wait for the midi
connector box from Gravis to become available.

		I notice that in the older FAQs, there is a description (from
Dustin Caldwell <DUSTIN@gse.utah.edu>) of the solder side pinout for a
15-pin D-type connector. This looks wrong to me. I have a 15-pin male
d-type in from of me, and it looks like this from the solder side
(i.e. the side you attach the wires to, rather than the side with the
pins that plugs into the card):

					Gnd             +5V
		 8   7   6   5   4   3   2   1
 +-----/-------------------------------\-----+
 |     \ o   o   o   o   o   o   o   o /     |
 | ( )  \                             / ( )  |
 |       \ o   o   o   o   o   o   o /       |
 +--------\-------------------------/--------+
		   15  14  13  12  11  10  9
		   Rx          Tx

		It is easy to get the pins confused on these connectors - the
female version seen from the solder side of course has everything the
other way around (pin 1 is on the left hand side).

		Hope this helps (or at least doesn't add to the confusion :-).
All reasonable quality D-type connectors have pin numbers marked
against the pins anyway.

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

13] What exactly is GUS 3D?

		First and foremost: YES, this is SOFTWARE.  You will NOT need
to upgrade your GUS to be able to do the GUS-3D stuff.

Written By: dionf@ERE.UMontreal.CA (Francois Dion)

		There are several systems that are in use to get 3D sounds on
recordings and some have been around since the 50s. Now i wont go into
the "how it works" of the more recent ones, but i think this will
clear up some confusion.  The first part is a "hands-on" experiment,
the second is informations, including the address and phone of the
owner of the technology that is used with the Gravis Ultrasound.

		Let's get back to the early days of stereo. One record company
(i cant seem to remember) was pushing it, while another (again, blank.
anyone?)  competed.  Interestingly enough, technological development
was put on stereo, and not on the first 3D system which was called
"binaural recording" and it simply consisted of two microphones placed
like the ears. You can try it this way:

		Go to a hat store and buy an extruded foam mannequin head.
You'll then need two microphones. Condenser will do, but you will need
to power them if you want to use them with the GUS, since it take a
dynamic microphone because it does not supply phantom power like some
mixer with XLR plugs. I will post a circuit later for Radio-shack
condenser mike unit (a small element that cost about 2$) if there is
some interest. If you dont want to mess with that, go with a cardiod
dynamic element.  Note that sensitive enough cardiod will cost you a
lot, so think about that.  You cut holes in the ears of the head, to
insert the microphone units (dont forget to make the wires of the
elements go inside the head and out the rear (or wherever). Use glue
to fill the crack around the mic.  Also, the more the ears look like
real ears, the better it will work. If you trim the foam, dont forget
to use an hairdryer to soften it (it will be more uniform). That's it.
Try recording sounds, and you'll be surprised.  I was! I did the
experiment with a polystyrene head on which i incrusted two PZM
microphones.

		Now that you understand how 3D recording is nothing like
stereo recording, we'll see what is accesible presently.

		First, the gadget we just built in the previous section exist
commercially, and is called "Mikey" and is made by Spherical Sound.
It's the only system commercialised where the microphones are placed
in a head.

		Another system is made by Virtual Audio and claims to enhance
stereo depth, but is not labeled 3D audio. I dont have much more info
on it, but from the description it looks like the same thing as the
"mikey".

		Two other systems use less restraining microphones situation
and can also be used on any signal because a DSP simulate a 3D signal
from parameters entered on the machine.  QSound (no hyphen) was
developped in Quebec, and the inventor sold the concept to another
company (Archer it seems). It is not that good even with electrostatic
headphones, and is pretty bad if you are listening to it thru speakers
and you are not in the sweet spot. And for trivia: Madonna, Sting,
Wilson Phillips and Paula Abdul to name a few have used the QSound on
their latest recordings. Another trivia: The Q logo is very very close
to Hydro-Quebec logo... QSound cost around 18K$ and is not midi
controllable.

		The other variant with a DSP is Roland RSS (Roland Sound
Space). It is a bit better (depending on how it is used) than QSound
with headphones, but suffers the same faith as QSound when you are
listening with speakers. Just move a bit from the sweet spot, and
suddenly what was in front left is now back left. RSS was used on
Suzanne Cianni _Hotel Luna_ album.  RSS cost around 40K$ and is midi
controllable.

		Another system on which i have zero information is called
Audio Cybernetics.

		The last technology is called Focal Point 3D Audio. It was
developped by Bo Gehring and first used on the Macintosh computers
with a modified Audiomedia (Digidesign). It cost around 1400$ in this
configuration. But, Gravis saw that (Focal Point is from Seattle) and
it is the system that we will be getting. At a much better price. The
system produce the sounds with these parameters: direction, elevation
and distance.  I am pretty sure that Gravis will have to develop a
SYSEX command set. We already need it badly, but with 3D, i will shoot
myself if i cant control it thru sysex.

		By the way, here's how to get in touch with Focal Point 3D
Audio, if you're interested.

		Focal Point(tm) 3D audio
		1402 Pine av., #127
		Niagara Falls, NY 14301
		Voice/fax: 1-416-963-9188

		Ok, you have read the 3D thing, and you cant wait. You want
big sound. The only possibility for now is surround. Now surround cost
a lot of money, and it will not be useable anymore once you get the 3D
driver. Wrong.

		Now, i hope you have an amplifier, cause if you dont, you
can't use this little hack to get surrounding sound. WARNING: i am not
responsible for any damage resulting from the use or misuse or
anything else related to this circuit.  Check that your - posts are
connected to ground and not the +. If it's the case reverse the
connections to the amplifier.

		It works surprisingly well considering the cost. Have fun!

  | Amplifier |
  | + -   - + |   You connect the front speakers as usual (dont mixup
   /| |   | |\    the polarities!)          _
  | |_|   |_| |   FLS: Front left speaker (/_\)
  | /_\   /_\ |   FRS: Front right speaker
  | FLS   FRS |   R: variable pot 50 ohm. 10 watts or more (depends on
  |_         _|      the amplifier)
  > |       | <
  ><'R     R'><    RLS: Rear left speaker (use a much smaller speaker
  >           <         for rear than front. 8 ohm also.)
  | RLS   RRS |    RRS: Rear right speaker (")
  |  _     _  |
  | \_/   \_/ |    the 2 - on front speakers are connected to the
  |_/ \_._/ \_|    ground of the amplifier internally, so you dont
   +   -|-   +     have to connect them.
		|_
		> |
		><'R
		>          Here, you do need to connect the 2 - thru R to the
	   _|_         amplifier ground.
		-  AMP GND

		Put the 3 potentiometer in a box so that you have the control
in one place, and use enough wire so you can move with it. You'll have
to experiment so that the R going to ground is a little higher than
the other 2 and once that adjusment made, the other two must be
adjusted so that the rear speakers are just adding a touch of depth
(if you turn them off, you notice that the surround is gone). Also, if
you have A-B speaker selection, plug the rear speakers on the + of B
instead of A, you will then be able to switch them off easily.  Of
course, when you will use the 3D audio, it will affect the signal, so
it's better to unplug the rear section.  But for your video, tape, CD
and regular GUS, you will still find it cool.

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

14] What are *.PAT *.VOC *.WAV *.SND *.MOD *.669, and *.MID files, and
		how do I use them?

Written by: Matthew E. Bernold <MEB117@PSUVM.PSU.EDU>

		These are all different types of sound files.

		*.PAT files are GUS instrument files, or PATCH files.  These
files are what your GUS uses to recreate the various instruments it is
capable of playing.  Your .PAT files should be in your /ULTRASND/MIDI
and /ULTRASND/SBOS directories.

		*.VOC and *.WAV files are basic digital sound files with
headers.  The *.VOC files are used on the soundblaster, and the *.WAV
files are used by Microsoft Windows.  Players capable of using these
formats can read information on sampling rate, 8 or 16 bit, and
mono/stereo from the header of these files.  *.WAV files can be played
in MS Windows by many programs.  *.VOC files can be converted to *.WAV
by many different programs, including SOX which is available via FTP.
The latest version (7.0) has been ported to PC clones and can be found
on the GUS FTP sites.

		*.SND files are raw sound files with no header information.
This is the format currently used by the GUS.  This means that you
have to tell the player program about the sample, because the
information on how to play it is NOT in the file, like with the *.VOC
or *.WAV files.  You can play these files using PLAYFILE which came
with the GUS.

		*.MOD files are 4-voice 15 or 31 instrument music files which
originated on the Amiga.  They use 8-bit, 16kHz samples to produce the
instruments, and note information to play the songs.  *.MOD files are
similar to MIDI files, but they are a bit more flexible because you
can use any sample as an instrument (including voices and sound
effects) instead of relying on the MIDI synth's own built in
instruments.  You can play these files using GUSMOD which can be found
on epas.

		*.669 files are 8-voice music files.  I don't know much about
them, so maybe Tran (author of the GUS 669 player) can fill in this
area.  You can play these files using P669GU0 which can be found on
epas.

		*.MID files are MIDI files.  You can play these files with
PLAYMIDI that came with the Ultrasound package, or with MediaPlayer in
MS Windows.  You might have to create a *.cfg file for the MIDI file
if it was originally created for a synth that does not conform to the
GM Midi standard.

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

15] What exactly is Wavetable Synthesis?

Written By: dionf@ERE.UMontreal.CA (Francois Dion)

		It is easier to find the Holy Grail than to find a text
describing precisely what synthesis method the GUS uses, so it's time
i take a shot at it. For this text i have searched thru ftp archives
troughout the world, have asked info from Ensoniq, Roland,
TurtleBeach, Advanced Gravis, Forte Creative Labs and i also took into
account the numerous comments, praise and flames i received to model
the text. Since this text is a result of a collective internet and
industry wisdom, flames will go the way of /dev/nul.  And please, read
the text carefully, because i have received some comments from people
who were thinking i wrote something when in fact i wrote the opposite
(particularly from non anglophones).

		You probably have heard about the GUS beeing a wavetable
soundcard.  I have received some comments that the GUS is not such a
thing, but since the industry uses this term (i.e. CL waveblaster,
GUS, TB multisound etc...), i am not in a position to create confusion
by renaming the technology.  Wavetable explains perfectly what it is.
A table containing a waveform.

		The GUS uses the third generation of wavetable synthesis, so
before i start explaining it, i'll talk about the first two
generations first.

		The first generation of wavetable synthesis was actually a
_digitally_ controlled _analog_ oscillator(s) where parameters
controlling the waveform were kept in memory. The curtis based synths
and some others are directly derived from this concept.

		The second generation of wavetable synthesis uses a digital
oscillator, with the waveform held in memory in it's basic form (one
period usually).  Parameters to alter the oscillator behaviour are
also in memory.  I use the general term "memory" instead of RAM,
because in some case it's actually ROM, FlashROM, PROM, EPROM,
switches, buffers etc... The Ensoniq chip found in the Macintosh Plus
is an example (8 bit, 4 oscillators, 4096 byte wavetable).

		The third generation of wavetable synthesis which can be found
in two flavors (RAM or ROM) is based on the second generation, but
uses bigger wavetables to hold the waveform (either in single period
or multi period format) including this time the attack and release. In
this section, i will focus only on the GUS implementation, which
basically encompass all other implementations.  Basically, what you
have are 32 oscillators which can do the exact same thing, and be
programmed separately and/or simultaneously. What the hardware can do
without the operating system is not too important here since we are
looking at what the GUS _can_presently_do_ (with modifications to the
OS, the GUS could do pretty much any synthesis method one can dream
up), not what it would have done if the OS wasn't available.  Of
course, more processing done in hardware means more CPU cycles left
for other things.

		So in the GUS, you have some RAM (up to 1Mb) that holds 1, 2,
3, etc, wavetables which consist of a sampled (or soft-synthesised)
waveform, some parameters and optionally a sampled attack and release.
The GF1 chip (an asic based on the Ensoniq DOC-II chip) will then
playback a waveform when triggered based on some parameters it is
given, and on others it will fetch from the wavetable. I dont know if
all parameters can be fetched from RAM by the GF1, nor if the GF1 can
fetch some instructions from RAM, but by using the current OS built in
the windows drivers or in the DOS library, this is what the GUS
_can_presently_use_ to synthesise music:

		- sampled or envelopped attack in 8/16 bit, signed/unsigned
				format *
		- sampled waveform (anything! a period, or a several seconds
				sample) *
		- sampled or envelopped release *

with:
		- velocity (volume) *
		- panning (balance) *
		- precise frequency playback rates (with frequency based
				antialiasing and oversampling) *
		- mixing of all the channels *

Up to here, it's sample playback. But there is more:

		- full vibrato (FM, depth, rate, sweep)
		- full tremolo (AM, depth, rate, sweep)
		- LFO (Low Frequency Oscillator) *
		- forward, reverse, dual direction looping or no looping *
		- the loop points can be anywhere (for sampled attack and release) *
				|-------|-------------|--------------|
				Start   Start loop    End loop     End
		- 6 point envelope
		- tuning *
		- fractional endpoint *
		- combination of oscillators (up to 4 if the GF1
				implementation is the same as Ensoniq) *
		- previous waveform usage *

And more recently:
		- 3D (focal point 3D positioning)

		( "*" indicates that the operation is done in hardware. Some
others may be done in hardware but i have not done any tests or found
any technical information to confirm it. I also base 1 item on the DOC
II capability, which should be implemented in the GF1.)

		Also, reverb, flanger, phasing etc...  could be easily
implemente within the drivers. Presently it can be done with a little
work on the patches and/or midi timestamp (i have succesfully made
flanger and phasing).  Another thing that could be implemented is
dynamic patch loading since the card supports it (i have done it). You
can even get a distorted sound (ideal for guitars, vox, analog synths)
by simply changing the 2's complement flag (work best with
soft-synthesised patches).

		Last, it is far better to have a RAM wavetable synth than a
ROM one, since you can upload your samples.  Even sound canvas owners
(and other synths too) complain that their ROM based GS synth lacks
interesting drum and bass sounds, cannot play sound effects, and is
not usable for dance and techno.  Also you can have more space for
each samples, because you always have only the samples you need in
memory, so you can have better sampling rates and better waveforms.

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

16] Is there a GUS device driver for Linux/BSD386/*IX?

		There is a group of people working on device drivers and C
libraries for Linux, BSD386, 386bsd, Minix, SysVR3/386, and whatever
other PC/UNIX flavors there are out there.

		The GUS driver is now included in the Linux kernel
v0.99.14 or later, so you don't even need to get a seperate
driver.  Thanks to Hannu Savolainen...the writer of this driver.

		I do not have any information about GUS support on other
PC-unix platforms.  If you use the GUS on a Unix platform other
than Linux, please let me know so I can include that in this FAQ.

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

17] How do I get the GUS to work with OS/2?

		As of now, there is no OS/2 specific device driver for the
GUS.  According to Gravis, they are working directly with IBM to get
OS/2 drivers for the GUS written.  A specific release date has not
been announced.

		There are a few simple tricks to get the GUS to work with OS/2
to a small degree right now:

Written by: Thomas Wong <twong@civil.ubc.ca>

		As it is right now, what you'll have to do is use a 8 bit DMA
channel in your setup of the GUS to make it work under a DOS window
under OS/2.  If you have already installed/setup your GUS card, just
go into the c:\autoexec.bat file under OS/2 and manually change the
number in the environment variable.  So, for example, use DMA channel
#1.  By doing this, you can now use playmidi, 669 player, gusmod... a
number of GUS programs. But you still can't run playfile or SBOS (it
may crash).  In other words, you can use a play a list of midi, 669,
mod...etc files in a DOS window, but can't play games.  Gravis did say
they will come out with an OS/2 driver but no date is set.

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

18] How do I go about programming the GUS?

		Gravis and Forte have released a very detailed SDK for the
GUS.  It includes source code, libraries, documentation, etc., etc,
and it's available on the FTP sites (see question #6).

		Also, there are two UltraDox files written by Phat Tran up for
FTP as well.  Read them carefully, learn to love them.

		(If you want to use the GUS with another OS besides MSDOS,
read questions #21 and #23.)

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

19] What are the pinouts for the CD Audio IN on the GUS?

Written by: <grtorlba@seattleu.edu>

		About two days ago I posted requested some info on the 4-pin
CD audio pin on the GUS.  I never got a reply but I got the info by
downloading volume 1 of the digest.

		The pin info was:

		left ground ground right

		I've tried this pin assignment and it seems to work.  The
articles in the digest pointed out that they weren't certain of the
left-right assignment but the two pins in the middle are definitely
the grounds.

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

20] I'm having trouble with... GENERAL TROUBLESHOOTING TIPS

Written by: john.smith@gravis.com (John Smith)

		It looks like a lot of the problems are incorrect
installations.

		Make sure that you put ALL the correct files in the
/ultrasnd/sbos directory and remove any old ones. Sbosdrv.exe,
Loadsbos.exe and Sboslib.sbs MUST all be from the same release
revision. They are NOT mixable. A lot of the problems you are seeing
could happen if the wrong driver is used with the new loader and patch
library.  To make sure you are using the correct files, delete ALL
files from /ultrasnd/sbos. Then unzip the new release into the sbos
directory. Then COPY sbosdrv.exe up to the /ultrasnd directory.  Then
COPY loadsbos.exe up to the /ultrasnd directory also.  Now pick either
sboslo.bat or sboshi.bat up to /ultrasnd/sbos.bat.  These two batch
files assume you are using emm386. If you are using another memory
manager (like qemm, 386max etc), use the appropriate command to load
it into high memory.  (NOTE: If you installed your software in some
other directory, substitute it in place of /ultrasnd).  ] Not all of
the tips below apply to all programs. This is just a brief summary of
some of the things we had to do to get some games running properly.

		1) Make sure the BLASTER environment string tracks our
ULTRASND string. Many games look at BLASTER to set up their stuff.
SBOS needs ULTRASND. If they are not the same, the game will be
looking one place and SBOS will using another. This is another reason
NOT to have an SB and GUS in the same system. Presumably, the SB would
want BLASTER set up for it and any game looking at it would not work
with SBOS. BLASTER is set up like this:

	BLASTER=A220 I5 D1 T1
			  |    |  |  |
			  |    |  |  -  Type of SB (1 = regular SB)
			  |    |  ----- DMA channel (MUST be 1)
			  |    -------- IRQ used.     (same as GUS midi irq)
			  ------------- I/O base address

		This variable is set up by the GUS setup program.  It should
never need to be modified unless you modify ULTRASND by hand.

		For example, wolf3d looks at BLASTER to get its parameters.
Sound will NOT function if the IRQs are different, but it will detect
an Adlib.

		2) Make sure that SBOS is up and running BEFORE you install
your game. Some games configure themselves during their installation
procedure. If SBOS is not running, it will assume there is no sound
board present.

		3) Some games have a separate setup/configuration section.
Make sure you run this after you install the game OR change the
ULTRASND variable. They are usually called setup, install or config.
Look around for it. Some games also save the last configuration to use
the next time the game is run. This means that if it didn't detect the
card (because SBOS wasn't loaded), it will save that info and will
start up the NEXT time with sound disabled. You will have to manually
turn sound back on somehow.  See your games manual. For example,
Wolf-3d will do this.

		4) Some games need all available RAM to run.  Since SBOS
currently takes approximately 19K, it may not have enough to run. Some
games will shut off some of the sounds if RAM is short.  Check your
manual. It may also be necessary to load SBOS high to reclaim some of
the RAM.

		5) If you have poor performance with SBOS loaded, see if you
have an expanded memory manager running.  (qemm, 386max, emm386 etc)
There is a SEVERE performance penalty to be paid if you run with
these. Its a byproduct of your machine running in protected mode.
Usually, only games that use direct I/O (mod players for example) are
seriously effected by this. If you must have SBOS loaded high, then
you will have to live with this. It is possible to disable the virtual
DMA if you are using qemm. (NOVDS) Doing so should speed things up a
bit.

Comments on above paragraph by mike@batpad.org (Mike Batchelor)
]
]               This paragraph contains some errors, from where I sit.
]       You may disagree, but I offer my perspective anyway:
]
]               1.  Virtual 8086 mode entails no more than a 5%
]       performance penalty over real mode.  It does not matter which
]       memory manager you use, the degradation is dependent on the
]       CPU and the motherboard.  In any case, the penalty is hardly
]       what you might call SEVERE.
]
]               2.  QEMM's NOVDS parameter has NOTHING to do with
]       virtualization of the standard DMA channels.  There is no
]       switch to disable this feature of QEMM, DMA would not fuction
]       in V86 mode if the memory manager does not virtualize it.
]       They all do this, they all MUST do this.  NOVDS tells QEMM not
]       to support the Virtual DMA Specification, which has to do with
]       virtualizing non-standard DMA used by bus-mastering adapters
]       (usually SCSI host adapters, but can be network cards, etc.).
]       The VDS spec is a means by which these non-standard DMA
]       operations may be virtualized in V86 mode.  QEMM normally
]       virtualizes the DMA channels handled by the motherboard's DMA
]       controller.  So-called bus-mastering disk controllers do DMA
]       on their own, without help from the DMA controller, so the
]       normal way of virtualizing DMA will not work.  VDS is the
]       solution for this.  Adding NOVDS to the QEMM line will disable
]       support for ASPI4DOS.SYS, USPI24.SYS and other VDS-supporting
]       SCSI host adapter drivers.  This will prevent the user from
]       loading anything into mapped memory in the first megabyte
]       (High RAM) from the SCSI hard disk.
]
]               The usual way to improve DMA performance is to
]       increase QEMM's DMA buffer.  The default on ISA systems is
]       12K, and 64K on MCA systems.  It can be increased to 128K max.
]       DMA=nnn specifies how large the length of a single DMA
]       transfer can be, in nnn Kb.  QEMM should prompt you to
]       increase the DMA buffer if a program attempts to exceed the
]       capacity of the current buffer.  I have found that 64K is
]       plenty for all programs I have used with the GUS.

		6) It is possible for an application to detect the Adlib side
of the GUS without SBOS being loaded. It depends on the method it uses
to detect it. Obviously if that happens, the application will think it
has an Adlib, but nothing is going to work.

		7) Many games need to detect (and use) extended/expanded RAM
before some sounds will be activated (usually digitized stuff) Refer
to your manual for these kind of problems.  An SB will not operate
properly under these conditions either.  For example, Falcon III will
not play digitized sounds until EMS is set up properly.  SBOS has
nothing to do with this problem.

		8) Some games hard code their I/O address and/or irq
selections. Refer to your manual.  You will have to make the GUS'
selections match these. I believe some Sierra games do this.  Wing
Commander requires a base port of address of 220 for digital speech to
work.

		9) Unless you are POSITIVE that a particular game needs an
option, (-o1 -o2 etc) DON'T specify one, 99% of the games do NOT need
one. You may screw up the driver by specifying one that you don't
need.  You should unload and reload the driver before specifying an
option. Since it is possible to use more than one option, you may be
telling it conflicting things if you don't unload it.

		10) There are several new features in SBOS that you should be
aware of:

				a) SBOS reloads its patches before an application
		runs.  This should eliminate having to reload it between
		running windows or a native GUS application (GUSMOD Star Con
		II, playmidi etc) and a game that uses SBOS.

				b) You can change the vector that it uses for
		communicating between sbosdrv.exe and loadsbos.exe.  The
		option is -Cxx, where xx is the new software vector to use.
		This is specified to sbosdrv.  Currently, only 1 application
		is known to need this.  Netroom uses the default vector (7E)
		so sbosdrv thinks it is already loaded.  If you are using
		netroom, you MUST change the vector #.  Netroom is the only
		application that we know of that has this problem.  There may
		be others.  We don't know of ANY games that do.

				c) You can tell SBOS to leave line-in enabled by
		specifying a -L when SBOS is loaded. This can be useful if you
		want to monitor some other audio output source thru the GUS.

		11) The volume up and down keys (defaults are [ and ]) do not
work in all games. Any game that takes over the keyboard vectors will
disable this feature. You must use the -V option when loading sbos to
alter the volume for these games.  This option works like this: -vxx
where xx ranges from 0 to 31 (31 being max volume) Note: in SOME
versions prior to 1.4B2, hitting the volume keys would hang your
system. This has been fixed.

		12) Some games grab all possible SB irqs (2,5 and 7) when they
initialize to find what IRQ the SB is on.  If they do this with SBOS
and SBOS happens to have the UltraSound IRQ on one of the SB irqs, it
will not let SBOS get its irq. Make sure that you set the UltraSound
irq to one of the upper ones (11,12 or 15). Jill of the Jungle is an
example of a game that exhibits this problem.

		13) Now for some simple things to look for.

				a) Is board seated properly?
				b) Is DRAM in sockets correctly (bent pins etc)?
				c) Are stereo/speakers hooked up properly?
				d) Are you connected to the right outputs on GUS?
				   (Some Ultrasound boxes are labeled wrong ...)

						TOP OF ULTRASOUND
						=================

						Amplified Out
						Line Out

						Joystick/Midi 15 pin connector

						Microphone In
						Line In

						BOTTOM OF ULTRASOUND
						====================

				e) Do you have enough environment space for ULTRASND
				   and BLASTER variables?
				f) Did you set the volume too low?
				g) Is \ultrasnd in your path?
				h) Could you have gotten a bad download of new SBOS?

		14) Several people have complained about sbos loading VERY
slowly.  Is your joystick or MIDI plugged in?  Try unplugging it.  As
of now, we haven't been able to reproduce this problem.  It may be
related to installing the software incorrectly or a DMA conflict.

		15) If your joystick doesn't operate properly in a game, look
for these things.

				a) Has it been calibrated (see manual)
				b) Do you have 2 games ports in your system? (GUS and
				   another game port). If so, one MUST be disabled.
				c) DO you have a line like the following in your autoexec

				   joycomp 20

				   where 20 is the compensation factor determined thru
				   the calibration utility, ultrajoy.

		16) There are several things people have noticed that seem to
effect SBOS that need to be investigated. None of these have been
verified, but you should be aware of them and you might try
eliminating them as possible sources of your problem.

				a) Loading SBOS hi can cause some FM stuff to sound
				   'weird'.
				b) Using 'Stealth' mode on QEMM seems to have a
				   detrimental effect.
				c) Change sbos.bat file to use loadhi instead of lh if
				   using QEMM.
				d) Stacker seems to cause some people problems.  It
				   works OK for others.
				e) Order that TSR's are loaded may have an effect. Try
				   loading SBOS first, last etc.
				f) When using XWing make sure that you have at least
				   896K of EMS (not XMS) and 563K of conventional.  If
				   you are having problems with slowdowns try turning
				   off the music.

		17) The only other thing we can think of is a hardware problem
on your card. The diagnostics in the new setup program should be able
to isolate it.

		Granted, we are a bit biased, but we believe that you should
get SUPERB sound out of your GUS.  If you are getting less than
satisfactory results, there can only be a few explanations.

				a) in windows, make sure its in 'high fidelity' mode.
				b) Incorrect software installation.
				c) Incorrect hardware installation (IRQ,DMA etc)
				   (probably)
				4) Bad hardware.(PC or GUS)

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

21] I can't seem to fit the new disks onto a floppy.

		First of all, the files need to go on to a HD 3.5" disk.

		Next, some of the disks were zip'ed a second time to include a
small README file (in other words, the .zip file you downloaded
contains two files: a README file, and another .zip file).  This would
have been a good idea, except the .zip file got bigger; too big for a
HD 3.5" disk.  So, you'll need to unzip the file, read the README, and
copy the new .zip file to a floppy.

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

22] Why shouldn't I use the comp.sys.ibm.pc.soundcard.GUS newgroup?

		c.s.i.p.s.GUS wasn't created legally; ie: there was no formal
call for discussion, voting, etc., etc.  As such, many sites refuse to
carry the group.  Posts there get to few readers.

		If anyone wants to take the time and energy to go through the
steps needed to get a new group created the correct way, I'm sure all
the GUSers would be more than happy to move there.

		(USENET tip for newbies: Don't create a new group for every
new topic that comes along.  Find the group that your topic fits best
in, and use that.  If you don't like all the other posts in the group,
learn the magic incantations that go along with killfiles in your
newsreader.)

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

23] What are "Miles Drivers", and how do I use them?

Written by: Matthew E. Bernold <MEB117@PSUVM.PSU.EDU>

		Miles drivers (also known as MIDPAK/DIGIPAK) are a set of
drivers that software companies to easily support many soundcards.
The game is programmed to use these drivers, and then any soundcard
with an appropriate driver will automatically be supported.  The Miles
drivers for the GUS can be found on the Epas archive site.  The
current version of these drivers is v.97beta (filename GUSAIL97.ZIP)

		There are three driver files and one TSR in the GUS Miles
Drivers.  The drivers are GF1MIDI.ADV, GF1DIGI.ADV, GF166.COM and the
TSR is ULTRAMID.EXE In order to use these drivers, you need to copy
them over existing sound drivers for another card.  These drivers
should have easily recognizable names like:

		(List taken from Monopoly Deluxe)

		SBDIG.ADV               Sound Blaster Digital
		SBFM.ADV                Sound Blaster FM Music
		SBPDIG.ADV              Sound Blaster Pro Digital
		SBP1FM.ADV              Sound Blaster Pro v1 Music
		SBP2FM.ADV              Sound Blaster Pro v2 Music (OPL3)
		MT32MPU.ADV             Roland MT32 Music
		PCSPKR.ADV              PC Speaker driver

		The above names are typical, but they may change.

		To get the game to work, you should do the following (This
example assumes that your Ultrasound directory is c:\ultrasnd and that
your miles drivers are in c:\ultrasnd\miles and your game is in the
directory c:\game):

		1) Change into your Game's directory

C:\>CD GAME

		NOTE: Any of the below steps MAY not be necessary, depending
on what your application uses.  If the app uses only Digital sound,
and no MIDI music, for example, you will not have to do step 3.

		2) Copy GF1DIGI.ADV over a Digital driver.  I would suggest
choosing the one that is most functional.  Choose the SBPro driver
over the SB one and you MIGHT get stereo (depending on what the game
does) and choose the PAS-16 driver (if one is present) and you MIGHT
get 16-bit sound if the game uses it.  We'll choose the SBPro driver.

C:\GAME>COPY C:\ULTRASND\MILES\GF1DIGI.ADV SBPDIG.ADV

		3) Copy GF1MIDI.ADV over a Music driver.  Here, I would
suggest that you try different ones and see which sounds best.
Sometimes the program plays a different version of the music depending
on your card.  For Terminator 2029, I found that the MT32 setting
sounds better, but the SCC-1 setting sounds more like the movie music,
even though it isn't as clear and nice sounding.  For this example,
we'll try the MT32 driver.

C:\GAME>COPY C:\ULTRASND\MILES\GF1MIDI.ADV MT32MPU.ADV

		4) Copy GF166.COM over the .COM file for the card you selected
above.  This should be fairly simple.  If you chose 2 different cards
as we did in this example, then copy the GF166.COM over the .COM file
for BOTH cards (just to be safe)

C:\GAME>COPY C:\ULTRASND\MILES\GF166.COM SBLASTER.COM

		(For this game [Monopoly Deluxe] there doesn't seem to be a
 COM file for the Roland MT32, so I didn't copy over it here)

		5) This step is MANDITORY.  Run the game's SETUP utility and
choose the cards you chose above.  In this example, we chose SBPro for
Digital, and MT32 for Music.  If the SETUP utility does NOT allow you
to choose two different cards, you must redo steps 2-4 patching only
ONE card's drivers.  Most programs now allow you to choose 2 cards,
however.

		6) Run ULTRAMID.EXE.  This needs to be done before you run any
games that use the Miles Drivers.  There should be instructions on
different command line options for ULTRAMID in the readme file that
comes with the archive.  Realize that ULTRAMID takes around 50k right
now, so you may have to load it high to get enough conventional memory
to run your game.

		That's it!  Your game SHOULD now have full GUS support.  If it
doesn't, here are a few hints on how to possibly fix things:

		1) Try copying the GUS's *.ADV drivers over ALL the *.ADV
drivers in the game's directory.  According to the README file, a good
indication of what a driver is is that if the driver is <10k then it
is a Digital driver, and should be replaced with GUSDIGI.ADV, if
larger, then it is a MIDI driver, and should be replaced with
GUSMIDI.ADV.  The name should also give you a clue as to what to
replace it with.

				a) MIDI drivers: MT32, SCC1, ADLIB (Usually), Anything
		with 'FM' like SBFM or SBP2FM

				b) Digital drivers: SBDIG, SBPDIG, PASDIG, PCSPKR.
		Usually these drivers will have 'DIG' in them, but not
		necessarily.

		2) Try copying the GF166.COM file over ALL the .COM files in
the directory.  BE CAREFUL WHEN YOU DO THIS!  Some games have .COM
files other than the music drivers that should NOT be copied over.
Most of the time, the .COM files you are looking for will be small,
and will usually have a recognizable name, although this is not always
the case.

		3) Some games on the list in the readme file from the archive
may use the Miles drivers, but NOT have *.ADV files anywhere.  From
what I understand, the Miles drivers will have the word "Miles"
embedded in them somewhere near the beginning.  Look through some of
the smaller files in the directory with an editor and see if you can
find the word "Miles" somewhere.  Some games rename the Miles drivers
to *.DRV.

		Good luck, and happy GUSing.

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

24] Where can I find more information on the GUS?

	1) GUS FAQ       Posted in Netnews about every 2 weeks.
					 Located on FTP sites in ..../info/gusfaq.txt

	2) 00Index.ALL   Recursive listing of all GUS files on the FTP
					 sites with brief info.  Located in the root
					 directory of GUS archive sites.

	3) GUS digest    The ultrasound digests are mailing lists for
					 ultrasound owners/users.  Following are the
					 addresses for the various digests available.

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

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

Date: Mon, 17 Oct 94 20:10:58 MET
From: Broderdue <iqivar@hp1.cbs.dk>
Subject: First encounter with the HMI-driver

The November Issue of PC Power has a demo of Nascar Racing included
on one of it's two cd-roms. The game has gus support, and guess what ?
It uses the HMI drivers.

It was an ambivalnt experience. The bad thing was that the program
was unable to play any music; a brief error message flash over the
screen as the program starts. Do we need to load patches first, is
there a special HMI-patch loader that is not released yet ?

Anyway, HMI beats AIL, both protected and non-protected hands down. The
reason for this is that it plays several digital sounds at the same time
in stero. This is AIL's major drawback, so in WC 3 we will have several
s/fx on top of music.

The effects and samples were clean and without hissing and popping sounds.


Nice work Gravis.... :)


	\////
	|. .|
	( - )   Broderdue
	Ivar Froelich - Copenhagen, Denmark.

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

From: gnnlist@ora.com (The GNN Subscription Account)
Subject: GNN October Update

		
		GNN October Update
 -----------------------------------------------------
CONTENTS:

1) New GNN Master Server
2) Recent Redesign of Home Page
3) Launch of I-media Center
4) Important Story -- Copyright Crisis
5) Mosaic Handbook Now Available

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

SPECIAL:  GNN is One Year Old

We're almost too busy to celebrate it, but GNN has 
reached its first birthday.  We are still learning to 
walk!  Next week, look in GNN NetNews for DC Denison's 
article on our first year: GNN Birth Daze.  If you have 
any ideas and suggestions -- critical or complimentary 
-- about GNN, send them to me (dale@ora.com) and we'll 
put them online for all to see.  It's been an exciting, 
challenging year, and we are all amazed not just by what 
we are doing, but by all the activity on the Net.

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

1. New GNN Master Server

We now have a new, faster master server located at
NEARNET in Cambridge, Massachusetts.  It replaces a 
smaller machine that had been overtaxed. Its host name 
is gnn.com, although nearnet.gnn.com also works.  The 
URL for the GNN Home Page is:

  http://gnn.com/gnn.html

Please continue to use our GNN Mirror sites if they
provide better performance for you.  These dozen sites 
are updated daily and should always be in sync with our
master server.  For a list of our mirror sites, look at:

  http://gnn.com/wel/sites.html

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

2.  Recent Redesign of Home Page

Like the proverbial box of detergent, GNN's Home Page 
is new and improved.  The most noticeable change is 
that the Home Page is organized into several sections:

  * An introductory section that links to What's Up in 
	GNN, our Welcome page, and our Subscription form.

  * A Navigating the Net section that contains links to 
	The Whole Internet Catalog and the GNN Business Pages, 
	as well as Netizens, Best of the Net, and the 
	Internet Help Desk.
  
  * A New section that contains GNN Netnews.

  * The Special Interest Publications where we cover 
	Travel, Personal Finance and now I-media.  We also 
	list there our special edition magazines, such as 
	The Digital Drive-In.

Jennifer Niederst, John Labovitz, Joan Callahan, and
Todd Lash worked on the redesign effort, testing the 
previous design with new users and getting valuable 
feedback.  As a result, there is more descriptive text 
on the Home Page explaining the different parts of GNN.

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

3. Launch of I-media Center

We have launched a new center in GNN, called I-media, 
to look at how the Internet is emerging as a new medium.  
The I-media Center will cover the design, strategy and 
new technology of publishing on the Internet.  The editor 
for the I-media Center is Richard Koman, co-author (with 
me) of the The Mosaic Handbook.  Richard is the technology 
editor for Communication Arts, a national graphic design 
magazine, and he was formerly the editor of Online Design.
The center will also cover important issues affecting 
consumers and producers of information, as it demonstrates 
with the articles entitled "Copyright Crisis," described 
below.

The URL for the I-media Center is:

  http://gnn.com/meta/imedia/

If you have ideas for the center or would like to 
contribute to it, please contact Richard at rkoman@ora.com.

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

4. Important Story -- Copyright Crisis

The I-media Center presents a very important issue 
that we feel all Netizens should be concerned about.  
The Clinton Administration has a proposal to amend the 
Copyright Act to make the National Information 
Infrastructure safe for digital publishers.  We think 
the Task Force that prepared the proposal has gone too 
far in making recommendations that would change the law 
to the benefit of publishers.  It ignores the public 
interest and would make illegal some practices that are 
common on the Internet today.  This is not to argue for 
the free flow of all information.  However, any change 
should acknowledge the difference between private and 
public use of information -- as the current law 
provides for.

Pam Samuelson of the University of Pittsburgh Law School
has provided GNN with a copy of an article that she wrote 
for an upcoming issue of the Communications of the ACM.  
Richard Koman has solicited opinions of others on the Net, 
such as Richard Stallman and John Perry Barlow.

To quote from Samuelson's article: "Not since the King of 
England in the 16th century gave a group of printers
exclusive rights to print books in exchange for the 
printers' agreement not to print heretical or seditious 
material has a government copyright policy been so skewed 
in favor of publisher interests and so detrimental to the 
public interest."

To follow this story, go to the I-media Center in GNN:

  http://gnn.com/meta/imedia/

Remember the Clipper Chip!

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

5) Mosaic Handbook Now Available

O'Reilly & Associates now has all three editions of
The Mosaic Handbook available for ordering directly from 
O'Reilly or from your favorite bookstore.  The Handbook, 
written by Dale Dougherty and Richard Koman, has editions 
for Microsoft Windows and Macintosh platforms, with 
Enhanced NCSA Mosaic on disk.  Licensed from Spyglass, 
Enhanced NCSA Mosaic provides a consistent feature set 
across all platforms, and proves to be more robust than 
the public domain versions.  The edition for the X Window 
System contains the public domain version of NCSA Mosaic 
(version 2.4) on CD-ROM with a special free offer to 
upgrade X users to Enhanced NCSA Mosaic when it becomes 
available.  These versions of Mosaic have an extra menu 
for GNN, allowing you to select GNN publications very 
easily.

For more on this book, you can use the following URLs:

  Windows edition:
	http://gnn.com/bus/ora/catalog/moswin.desc.html
  Mac edition:
	http://gnn.com/bus/ora/catalog/mosmac.desc.html
  X edition:
	http://gnn.com/bus/ora/catalog/mosx.desc.html

All editions sell for $29.95 and can be ordered directly
from O'Reilly by calling 1-800-998-9938 or 707-829-0515.
(In the next month or so, we will announce online 
ordering via Web as well as all O'Reilly titles.)

If you order directly from O'Reilly, and tell them you
are a GNN subscriber, we will also send you a Mosaic 
Handbook tote bag, while supplies last.  Please provide 
the O'Reilly Customer Service person with Code: gnns

Finally, check out the GNN Personal Finance Center
with its special feature: "Network Money: The Future of Banking
and Commerce of the Internet."  Its URL is:

http://gnn.com/meta/finance/feat/emoney.home.html 

-- 
Dale Dougherty    (dale@ora.com)
Publisher, Global Network Navigator, http://gnn.com/
O'Reilly & Associates, Inc.
103A Morris Street, Sebastopol, California 95472 
(707) 829-0515 

-- 
The Global Network Navigator 
Subscription Account * gnnlist@gnn.com
GNN Registration Page URL * http://www.ora.com/
GNN HomePage URL * http://www.gnn.com/gnn/gnn.html
800-998-9938 (US/Canada) 707-829-0515 (all others) 707-829-0104 (FAX)

To: Patric Gauderer <gauderer>
Cc: schmitz
Subject: Re: Bastelarbeiten...  
In-Reply-To: Your message of "Tue, 04 Oct 94 10:30:39 +0100."
			 <9410040930.AA05762@borodin.telematik.informatik.uni-karlsruhe.de> 

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

Date: Tue, 18 Oct 1994 06:25:03 +0100
From: A.PAUW@ELSEVIER.nl
Subject: GUS & CDROM problem

> Date: Mon, 17 Oct 1994 12:19:23 +0100 (BST)
> From: Mark.Harvey@ee.surrey.ac.uk
> Subject: GUS & CDROM problem
> 
> I've just recently got a Mitsumi double-speed CDROM. My GUS MAX manual says
> it can't handle DMA channels 5,6,7 for the CDROM so I'll have to use polling
> rather than interrupts. Since I have both a separate interface for the CDROM
> and a SoundBlaster ASP MCD, I thought I'd use either one of those interfaces.
> 
> However despite disabling the CDROM interfaces on the GUS and making sure there
> are no conflicts between it and the SB/Interface card, the GUS always cocks
> things up and I can't get my CDROM to work - or rather the driver installs
> okay but then comes up with 'device not ready' or something like it when I try
> and do a dir on the drive.
> 
> Anyone had this problem?
> Cheers,
> 
> Mark...
> 
> p.s. My system is Gateway 486-DX2-50, PCI.
> 
> ------------------------------
> 
> Date: Mon, 17 Oct 1994 08:46:58 EST
> From: "Carl" <CARL@BUSOP.CIT.WAYNE.EDU>
> Subject: GUS-MAX CD-ROM interface & Mitsumi double speed?
> 
> Hello, over the weekend I tried unsuccessfully to hook up my Mitsumi 
> double speed drive to the CD-ROM interface on my GUS-MAX.  I disabled 
> all IRQ's and DMA channels by removing the jumpers as instructed in 
> the manual (the GUS-MAX does not support DMA for double speed 
> Mitsumi), and installed the polled i/o driver for the mitsumi drive.
> What happened is, it worked fine in DOS, but everytime I tried to 
> boot Windows it would just freeze with the hour glass (you couldn't 
> even move it), I even tried to reinstall Windows.  Does anyone have a 
> solution to this problem?  Thanks.
> 
> --
> Carl Mueller                                               
> WSU Detroit, Michigan      
> 
>        "take away the clouds, give me colours, that's all i want now"
> 
I own a vanilla UltraSound (no MAX) and also have this Mitsumi
double speed CD-ROM drive (FX001D, yes it was quite cheap but it
works fine). I installed it and have no problems. I'll give you
my DMA/IRQ/Address set up. By the way I also have a
(`Flinstones') SoundBlaster 2.0 card up and running, no
problemo. Ok here is my setup:
486SX/33, 5 Mbyte
==================================================================
		Address     IRQ     DMA
SoundBlaster    220h        5       1 (fixed)
UltraSound  240h        7 (Midi)    6 (playback)
				11 (GF1)    7 (record)
CD-ROM (FX001D) 300h        10      5 (default values)
==================================================================
Two footnotes: I don't have a printer so I can use IRQ 7. For the
Mitsumi I use it's own controller. For the driver I can use the
IRQ/DMA transfer one.

I suspect Windows is not giving the polling driver enough time
slices to do the work properly, I don't like this polling thing.
In Windows it may even lead to a `time-out' message for the
device and give the device not ready message. Make a list of all
DMA/IRQ/Addresses of ALL your cards (no matter what they are)
and put them on different settings and use the IRQ/DMA driver
for the Mitsumi CD-ROM. Also note that: some cards don't like 16
bit DMA (DMA 4-7), I believe DMA 4 is used by DMA 5-7 (I read this
somewhere) 0-3 are 8 bit DMA. Mind you the Mitsumi is a 16 bit
interface and can use 16 bit DMA transfer. SoundBlaster's are
always fixed on DMA 1 (the Pro's can be changed but most
software use DMA 1).

I hope you can use this information.

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

Date: Tue, 18 Oct 94 09:23:35 BST
From: csfb1!csfp.co.uk!pcunnell@uunet.uu.net (Paul Cunnell)
Subject: Re: GUS & CDROM problem

Mark.Harvey writes:

>I've just recently got a Mitsumi double-speed CDROM. My GUS MAX manual says
>it can't handle DMA channels 5,6,7 for the CDROM so I'll have to use polling
>rather than interrupts. Since I have both a separate interface for the CDROM
>and a SoundBlaster ASP MCD, I thought I'd use either one of those interfaces.

I have a similar setup - GUS, SB16 ASP and Mitsumi CDROM with its own 
interface card. Machine is a Gateway 486/66 PCI. After much juggling and
tweaking, I have found the only way to make things work reasonably well
is to have the GUS on I/O address 210. The CROM uses its own interface,
on address 320 or thereabouts. I use the DMA version of the CDROM
driver. I still get some odd behaviour - on a cold boot, ultrinit seems to
crap on the disk device driver - the C:\ directory appears completely
corrupt. Ctrl-Alt-Delete fixes this, however. 

Hope this helps.

Paul.

--
Paul Cunnell CSFB FOS (csfb1!csfp.co.uk!pcunnell@uunet.uu.net) +44 71 516 2946

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

Date: Mon, 17 Oct 1994 14:18:19 -0700
From: jsbernstein@ucdavis.edu (Jeffrey Bernstein)
Subject: gus0043

Is anyone else having a beep or chirp after certain .wav's are played for
Windows events?  I've only noticed this since I installed the files in
gus0043.  Is there a fix or workaround or anything for this?

Sorry if this has been covered before, I haven't had the time to go through
all the digests since it's reappeared.
--

												Jeff Bernstein
												jsbernstein@ucdavis.edu

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

Date: Mon, 17 Oct 1994 18:32:41 -0400 (EDT)
From: Mike Batchelor <M.Batchelor@babylon4.clark.net>
Subject: Re: GUS CD in polled mode (answer)

Not the GUS Server once wrote...
> 
> Date: Mon, 17 Oct 1994 12:19:23 +0100 (BST)
> From: Mark.Harvey@ee.surrey.ac.uk
> Subject: GUS & CDROM problem
> 
> I've just recently got a Mitsumi double-speed CDROM. My GUS MAX manual says
> it can't handle DMA channels 5,6,7 for the CDROM so I'll have to use polling
> rather than interrupts. Since I have both a separate interface for the CDROM
> and a SoundBlaster ASP MCD, I thought I'd use either one of those interfaces.

You don't have to operate in polled I/O mode.  MTMCDE.SYS will operate in
interrupt mode, without a DMA channel:

DEVICE=C:\DOS\MTMCDE.SYS /D:MSCD001 /P:340 /A:0 /M:20 /T:S /I:10 /X

It's that /T:S switch that tells it not to use a DMA channel.  But it still
uses an interrupt, and works quite well.  I can't tell the difference. 
Works great with my GUSMAX in DOS and Linux (which doesn't use DMA for
Mitsumi anyway).

> Also - Do the GUS Windows drivers work for NT as well? If not are there any
> available?

No and no.

> Date: Mon, 17 Oct 1994 08:46:58 EST
> From: "Carl" <CARL@BUSOP.CIT.WAYNE.EDU>
> Subject: GUS-MAX CD-ROM interface & Mitsumi double speed?
> 
> Hello, over the weekend I tried unsuccessfully to hook up my Mitsumi 
> double speed drive to the CD-ROM interface on my GUS-MAX.  I disabled 
> all IRQ's and DMA channels by removing the jumpers as instructed in 
> the manual (the GUS-MAX does not support DMA for double speed 
> Mitsumi), and installed the polled i/o driver for the mitsumi drive.

See above.  

> What happened is, it worked fine in DOS, but everytime I tried to 
> boot Windows it would just freeze with the hour glass (you couldn't 
> even move it), I even tried to reinstall Windows.  Does anyone have a 
> solution to this problem?  Thanks.

See above.  Not a problem for me.

> ------------------------------
> 
> Date: 16 Oct 1994 00:00:00 +0000
> From: tom@cat.ping.de (Thomas Adams)
> Subject: which type of DRAM?
> 
> If I rip six 514256 off my old video board could I use them to upgrade my  
> GUS to 1 MB?

As long as they are 70ns or faster.  80ns may work, too.

-- 
M.Batchelor@babylon4.clark.net

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

Date: Mon, 17 Oct 1994 14:27:35 -0500 (EST)
From: "Joseph A Martin" <jam237@psu.edu>
Subject: Re: GUS Daily Digest V0 #1

> Date: Sat, 08 Oct 1994 19:57:45 -0500 (CDT)
> From: triplett@UTSW.SWMED.EDU (Terry L. Triplett)
> Subject: Strange chirping w/new GUS drivers in Windows-How to get rid of?
>
> Hello everybody.  What a shock to find the digests coming in again-I had
> not realized how much I had been missing them.  Yesssssssssssss!!!!!!!
>
> I thought I would submit a question just to get things rolling:
>
> I am using the latest windows drivers from gus0043.zip on EPAS, and have
> noticed that ever since I installed them, I hear this annoying 'chirp'
> when software accesses the card.  Now that I am thinking about it, I
> don't recall hearing this when playing MIDI files, only when playing
> digital samples from either the hard drive or from CD-ROM (usually along
> with video clips, eg. Quicktime or Video for windows, but also using
> media player).  The sound occurs at the beginning of the clip, and again
> at the end when the player is relinquishing control of the GUS.
> This was never heard with any drivers before this version.
> Anyone else experiencing this phenomenon?  Can it be eliminated?
>
> Some info:  I have an original GUS, purchased sometime in 1993, with 1meg
> RAM on board.
> It's running in a 80486, 33mHz noname clone with 8 megs of RAM, Windows
> for Workgroups, Norton Desktop for Windows 3.0, Stacker 4.0, with a cheap
> Philips single-speed CD-ROM Drive.  Oh, and Qemm 7.04.
>
> Thanks,
> Terry
> triplett@utsw.swmed.edu

Get the newest drivers released in September.  They should be in the
archive.epas.utoronto.ca /pub/pc/ultrasound/submit directory.

GUS356A.ZIP
GUS356B.ZIP
GUS356C.ZIP
GUS356D.ZIP
GUS356E.ZIP
GUS356F.ZIP

These are a FULL release of the Version 3.56 diskettes.
REM INCLUDE: 'Legal.Disclaimer.Document.Long'

	  ((( *** I M P O R T A N T   L E G A L   N O T I C E *** )))

THIS MESSAGE IS FULLY PROTECTED UNDER THE UNITED STATES COPYRIGHT LAWS,
EXCEPT FOR PORTIONS IN WHICH THE AUTHOR EXPRESSLY STATES ARE BEING
DONATED INTO THE PUBLIC DOMAIN.  THIS INCLUDES ANY AND ALL SOURCE CODE,
FORMS, LEGALESE, COPYRIGHT NOTICES, AND OTHER TYPES OF SPEECH.
ALTHOUGH THE CODE IN THIS AND ALL MESSAGES IS TESTED EXTENSIVELY TO
PROTECT AGAINST UNFORSEEN DEFECTS, AND ALL RESAULTANT EXECUTIBLES HAVE
BEEN CHECKED BY ANTI-VIRAL SOFTWARE TO PROTECT AGAINST UNINTENDED
INFECTION.  THE AUTHOR CLAIMS NO RESPONSIBILITY FOR THE EFFECTS OF
ANYTHING THAT IS IN THIS MESSAGE, AND SHALL NOT BE HELD RESPONSIBILITY
FOR ANY ADVERSE EFFECTS THAT ANY CODE IN THIS DISTRIBUTION HAS, DUE TO
THE VAST NUMBERS OF SYSTEMS THAT CAN BE CALLED IBM COMPATABLE PCs I
CAN NOT KNOW IF THIS CODE MAY NOT WORK ON YOUR SYSTEM.

REM INCLUDE: 'Legal.Disclaimer.Document.Short'

In short:  If your system gets screwed up for anything in this message
		   and you would be the type of person that would want to sue
		   me for those damages.  DO NOT READ THIS MESSAGE!

REM INCLUDE: 'SigFile'
--
Joseph Alex Martin
101 Holmes Hall
University Park, Pa. 16802

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

Date: Mon, 17 Oct 1994 12:48:24 -0700 (PDT)
From: Dylan Nicolle <dnicolle@tcsgi.mhs.mendocino.k12.ca.us>
Subject: Re: GUS Daily Digest V15 #10

On Date: Sun, 16 Oct 1994 14:11:40 -0400 (EDT)
From: Peter Berger <peterb@telerama.lm.com> wrote about
Subject: Epas submit dir.


>I'm not blaming anyone for this -- obviously, this is a hobby, and we 
>can't expect someone to monitor it full time.  Can anyone think of 
>alternate ways of structuring submissions that would still allow some 
>vitality?  Perhaps an approved list of submitters, so that if someone is, 
>for example, uploading pirated stuff, there's some degree of accountability?
There is a list, which is sent out every so often which shows the latest 
files which have been uploaded and the .txt file which goes with it. 
TONNES of help. Cant remember the listserver that runs it.

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

Date: Mon, 17 Oct 1994 16:05:13 -0400 (EDT)
From: Phat Hong Tran <ptran@sciborg.uwaterloo.ca>
Subject: Re: GUS Daily Digest V15 #10

On Mon, 17 Oct -1, GUS Server wrote:

> Date: Sun, 16 Oct 1994 12:31:15 -0700 (PDT)
> From: sabe@sdcc13.ucsd.edu (Shige Abe)
> Subject: Playing MIDI
> 
> Since the GUS plays MIDI files differently than any other
> soundcard, I assume the software to play .MID files is important.
> Currently, I'm using "playmidi".  Is "playmidi" better than the
> media player in Windows?  What Windows or DOS programs should I get
> for absolute best sound quality?  Should I use any options in
> "playmidi" to optimise sound?

Under Windows, all MIDI is handled by the GUS' Windows MIDI driver, so
as long as the apps you're using to play .mids under Windows is sending
the correct MIDI events to the driver, they all should sound about the
same.  However, there is a difference between the Windows driver and
playmidi.  In my experience, I find that I encounter frequent dropped
notes when playing MIDI files under Windows, whereas I haven't noticed
the same with PlayMIDI.  Also, PlayMIDI supports the use of .cfg files
for custom MIDI maps for each .mid file.

The most important parameter for PlayMIDI that you should play with
is the -x<nn> switch, where <nn> is a number from 14 to 32.  This
switch sets the number of voices PlayMIDI will use to play a .mid.
The higher the number of voices used, the lower the overall sampling
rate, but the greater the polyphony (the number of notes that can
sound at once).

> Date: Mon, 17 Oct 1994 11:45:02 -0400
> From: "Christopher D. Mckillop" <cdmckill@novice.uwaterloo.ca>
> Subject: Recording .wav under windows...
> 
> Hello all...
> 
> 
>   Well, my problem is......I am unable to get Windows to grab the 
> wave data that is going thru the GUS.  I am setting everything properly 
> since I can record under DOS.  I have turned off the muting radioboxes on 
> the mixer and I can hear myself thru my stereo when i speak in the mic.  
> When I press record and then say something, then press stop, I get the 
> message....
> 
>       "No Waveform Data Collected", or something along those 
> lines..Anyhelp???

What app are you using to record?  Do you have SoundStation active and
its VU meter enabled while you're trying to record?  (SoundStation's VU
meter occupies the recording facilities while it's on.)

> Date: 16 Oct 1994 00:00:00 +0000
> From: tom@cat.ping.de (Thomas Adams)
> Subject: some questions
> 
> I had a GUS some years ago and I sold it but now again I bought a GUS  
> (V3.4) which leads me to some questions.
> 
> - Where are all the PALs/GALs or whatever they were gone? Into the small  
> chip soldered to the PCB underneath the GF1?

A bunch of discrete components have been integrated into ASICs or larger
PALs on newer GUSes.

> - What is the "small chip" good for?

See above.

> - Are the latest drivers released on disk V2.06? I can't believe that.

The latest disks are 3.56, I think.

> Date: 16 Oct 1994 00:00:00 +0000
> From: tom@cat.ping.de (Thomas Adams)
> Subject: which type of DRAM?
> 
> If I rip six 514256 off my old video board could I use them to upgrade my  
> GUS to 1 MB?

Those look like they're the 4x256 bit chips that the (older) GUSes use.
They might not be the right speed, though.  (100ns or faster [i.e. less]
should work).

Phat.

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

Date: Mon, 17 Oct 1994 22:32:32 GMT
From: maughc@rpi.edu (Curt "Star Commander" Maughs)
Subject: Re: GUS Daily Digest V15 #10
Message-ID: <maughc.64.2EA2FB7F@rpi.edu>

>Date: Sun, 16 Oct 1994 18:24:40 -0400
>From: JeffOw@aol.com
>Subject: Space Hulk and MOM

>2)  I've heard that Microprose's new Master of Magic (similar to Master of
>Orion) is NOT GUS compatible.  Does anyone know if an independent patch will
>be made like one was for MOO.  (I've also heard the game is pretty buggy
>right now, so I'm probably gonna wait awhile before buying it.)

DO you mean it doesn't work with SBOS. I tried the demo version of it and it 
worked perfectly with it. I just wish though that they would add native support
for the GUS through the AIL drivers since they still seem to use the same 
drivers as MOO.

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

Date: Tue, 18 Oct 1994 14:02:51 +0100 (MET)
From: gauderer@tmipe0.telematik.informatik.uni-karlsruhe.de (Patric Gauderer)
Subject: Re: GUS Daily Digest V15 #10

From: Patric Gauderer <gauderer>
To: voigt, schmider, schmitz, gauderer
Subject: Bastelarbeiten...
Status: OR

Hallo,
wie ihr ja sicher schon wisst ist am 24.10.94 Juergen's
Promotion zu feiern. Wir als Studenten und HiWis von Juergen
sind damit beauftragt den Wagen und den Hut zu "designen".
Bitte setzt euch noch im Laufe dieser Woche mit mir oder
Jochen Seitz (der ist aber naechste Woche im Urlaub) in Verbindung,
damit wir einen Termin ausmachen koennen.
Der Titel von Juergens Dis ist "KARMA".

ciao, 

Patric

 -----------------------------------------------------------------------
Patric Gauderer                                  INSTITUT FUER TELEMATIK     
Dipl.-Inform.                                    UNIVERSITAET KARLSRUHE TU 
e-mail : gauderer@telematik.informatik.uni-karlsruhe.de
mail   : Hoehenstr. 16 D-75210 Keltern 
phone  : 49 7236 2229
 -----------------------------------------------------------------------

	(5.65c8/IDA-1.2.8) id AA02929; Wed, 5 Oct 1994 09:35:12 +0100
To: hpn-ml@telematik.informatik.uni-karlsruhe.de
Subject: FWD : PhD proposal at INRIA Sophia Antipolis

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

Date: Tue, 18 Oct 94 10:44:49 EST
From: rmcclint@tmac.com (Richard McClinton)
Subject: Re: GUS Daily Digest V15 #10

Janne Korkkula <jk@snafu.muncca.fi>:
  You'll never get anywhere demanding perfection from human beings.  Quit 
trying, shut up, and enjoy the best damn game in existance.  I really have
to wonder if you're doing something wrong.. it's the only thing I can assume,
as I honestly don't have any static, screwed up sounds, or lockups when I play.
as for a lack of frequency response, I dunno. I push the bass boost button on
my cheap speakers and smile.

Rick McClinton
rmcclint@tmac.com


 --------------------------------
> Date: 16 Oct 1994 00:00:00 +0000
> From: tom@cat.ping.de (Thomas Adams)
> Subject: which type of DRAM?
> 
> If I rip six 514256 off my old video board could I use them to upgrade my  
> GUS to 1 MB?
> 
> -tom
> 
> ## CrossPoint v3.02 ##

  That's what I did.  That's the same number on the other chips on the GUS, 
right?  and it's got the same number of 'legs'? Just might work.  Get the other
test program from the ultrasound archive and use both of them.

rmcclint@tmac.com

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

Date: Mon, 17 Oct 1994 11:47:14 -0600 (MDT)
From: rkornilo@nyx.cs.du.edu (Ryan Korniloff)
Subject: Re: GUS Daily Digest V15 #8

> > Date: Thu, 13 Oct 1994 11:54:49 -0600 (MDT)
> > From: rkornilo@nyx10.cs.du.edu (Ryan Korniloff)
> > Subject: Bad MIDI mapping
> > 
> > Maybe it's just me (I don't THINK it is) but it seems to me that Gravis 
> > STILL has not been able to get the MIDI map correct on either General 
> > MIDI OR Sound Canvas. Another example I just ran into is with Day Of The 
> > Tentacle. If you select Gen. MIDI instead of Sound Canvas some 
> > instruments are different than with the Sound Canvas setting. The Sound 
> > Canvas setting sounds really weird to the point of being annoying. Can 
> > anyone give me any insite into this??? 
> 
> Well, the Sound Canvas (i.e. SCC-1) isn't strictly General MIDI.  It's 
> also GS (anybody care to expand this acronym?), meaning that it has 
> instruments and effects not part of the GM standard.  (GS is a superset 
> of GM.)  Thus, it shouldn't surprise you that the music for the Sound 
> Canvas configuration sounds different than that for the GM configuration.

Well, if SCC's GM mode works. Then why can't Mega_Em?>
 
> Now, Mega-Em isn't truly GM, GS, or MT-32 compliant.  It tries its best to
> approximate all three.  (Well, it has two different MIDI maps, but since
> GS and GM are pretty close, one of the maps is used to approximate two 
> standards.)  Work was done over the summer to optimize the GM approximation
> for the next release of Mega-Em, though.

Uhhh, then why does it claim it's compliant? This seems so stupid. What 
good is music capability if it's not gonna play right? FM sux -- but it 
plays right! What's the problem with using 3 maps? I don't know about 
you. But I can spare the extra 6K of disk space for another map.

Doesn anyoine know where I can get an official MIDI map so I can go and 
edit this thing myself.


		   -- Ryan Korniloff
		   -- rkornilo@nyx10.cs.du.edu
 

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

Date: Tue, 18 Oct 94 00:10:14 -0400
From: "Barrie Rody" <brody@fox.nstn.ca>
Subject: Re: GUS Daily Digest V15 #8

>#flame on
>>Date: Thu, 13 Oct 1994 18:46:50 -0400 (EDT)
>>From: Phat Hong Tran <ptran@sciborg.uwaterloo.ca>
>>Subject: Re: GUS Daily Digest V15 #6
>>
>>FWIW, Gravis had not been working on OS/2 until the past summer.  (They
>>were planning to for a long time, but other projects overrode OS/2 in
>>priority.)  But over the summer, Forte had a preliminary version of the 
>>OS/2 driver already working, and Gravis also put one of their own 
>>programmers on the OS/2 project.  (The programmer Gravis placed on OS/2
>>is an unabashed OS/2 fanatic, and very competent.)
>

Suspicions confirmed!! 

Since I was an OS/2 user, prior to purchasing my GUS in Jan 94, I called 
Gravis to ask if OS/2 drivers were available.  I was assured that they were 
in the final stages of development and would be available sometime in the 
first half of 94.  In May, I was assured "The core of the drivers are 
looking good but are not making sound yet." also, now Gravis couldn't give 
me an expected release date.  I have not received a reply to my more 
recent queries.  So much for supporting Canadian companies. 

Now when friends ask about my soundcard I tell them Gravis lied to me 
and if they are that hard up for business they won't be around for the long 
haul so they should forget about GUS.

 ---------------------------------------------------------------------
 Barrie Rody                                             RR 6                     
 brody@fox.nstn.ca                                       Kingston N.S.
 Voice: (902) 765-8362                                   B0P 1R0           
							  
			OS/2 - Arriving in Chicago earlier than expected.

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

Date: Fri, 14 Oct 94 16:53:12 EDT
From: "Henrique 'Snoopy' Vianna" <HVIANNA@BRUFPEL.BITNET>
Subject: Latest version of GUS software

Hi folks!
 
Which is the latest version of the GUS software available? Since the
digest vanished, I've been out of the new releases.
 
Thanx,
  Snoopy.

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

Date: Mon, 17 Oct 1994 14:44:35 -0400
From: jgamache@courrier.usherb.ca (Jerry Gamache)
Subject: Master of Magic & GUS

***A little note from the one who made the MOO patch for GUS.***

		After trying the Master of Magic demo WITH GUS SOUND I am quite sure 
(>95% sure) that the patch I made for Master of Orion will work with Master 
of Magic (since the patch worked with the demo). Personally I will postpone 
buying MoM until it is fully debugged, so if one of you GUSers wants to try 
it, the instructions I put in the README of MOO_GUS.ZIP applies fully.

IF success THEN
--->FLAME ON
		THE GUYS AT MICROPROSE DID NOT DO THEIR HOMEWORK...
		The file named SNDDRV.LBX is simply a bunch of Miles             
drivers concatenated. It should have been VERY easy to           simply 
include the ones for the GUS. Send them some mail.
--->FLAME OFF
ELSE
--->IGNORE
ENDIF
								Waiting for replies...
								Jerry Gamache   
								jgamache@courrier.usherb.ca

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

Date: Mon, 17 Oct 1994 11:40:33 -700 (PDT)
From: Matt Bachand <raistlin@cts.com>
Subject: Masters of Magic / GUS
Message-ID: <Pine.SCO.3.90.941017113937.5545A-100000@crash.cts.com>

I have no problem getting Masters of Magic to work with Mega-Em at all. I 
just run it and then run the game. It works perfectly. 

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

Date: Tue, 18 Oct 94 12:11:46 +0100
From: Stefan <S.Magdalinski@cs.ucl.ac.uk>
Subject: mega-em and Tie-Fighter

Hi, I've been using the mega-em that comes with tie-fighter, and
noticed that it doesn't seem to load anywhere near 1024k of patches.

I was wondering if it would be possible to load the patches as 16 bit
instead of 8 bit, and so get EVEN better sound. I thought that there
might be a command line option, or maybe one could run emuset and
mega-em, and then reload the patches using a different program.
Maybe build a dummy mid with the appropriate patches and use playmidi
to play it? Is there a way of finding out which patches the TF version
of mega-em loads? 

Any ideas would be much appreciated.

Stefan

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

Date: Mon, 17 Oct 1994 15:57:51 -0700 (PDT)
From: Seth Delackner <dax@rahul.net>
Subject: Origin GUS support

Someone asked why Armada doesn't support GUS, and System Shock does.  
Well, supposedly Armada is origin's last game not to support the GUS, and 
after System Shock, their using HMI so ALL their games (including WC3) 
will have GUS support... Course this is the third time they've waffled on 
this in recent history, so who knows.

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

Date: 18 Oct 94 08:41:31 EDT
From: Jon Grieve <100102.145@compuserve.com>
Subject: Origins GUS Support
Message-ID: <941018124131_100102.145_BHJ44-1@CompuServe.COM>

Attn: Student User #20(GV) <gv20@homer.prahran.swin.edu.au>

Origin did say to me a couple of weeks ago that "Yes" they will support the GUS
in all future titles.

As far as WC III and WC Armarda - I would think the reason III has support and
Armarda doesn't is reasonably obvious.  One is a vast multimedia extravaganza
with a huge budget, the other is just yet another re-hash of an existing game
that never had GUS support.

 ---------------------------------------------------------------------
Jon Grieve                   100102.145@compuserve.com
 ---------------------------------------------------------------------

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

Date: Tue, 18 Oct 1994 14:31:36 +0100 (MET)
From: Roberto Bonet <d93-rob@nada.kth.se>
Subject: Re: Origins GUS support

 The latest news about Origin is that every product AFTER WC Armada will 
have GUS support. That means System Shock and WC III among others and NOT 
WC Armada.
 ---------------------------------------------------------------------------
Roberto Bonet                                  Computer Science
d93-rob@nada.kth.se                        Royal Institute of Technology
Phone: +46-858081964                           Stockholm, Sweden

"I have an idea and it doesn't include explosives."
									-Max the Rabbit
 ---------------------------------------------------------------------------

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

From: Michael Hild <hild>
Subject: Promotion J"urgen

Hallo Patric,

hiermit melde ich mich zur Mithilfe bei den Vorbereitungen
zu J"urgen's Promotion.

Um es gleich vorwegzunehmen, ich habe keine Wagen (Wenn man von
einem alten Daimler absieht :-))

Bitte ber"ucksichtige bei evtl. Detailplanung, da"s ich J"urgen
versprochen habe, ihm beim Aufbau an dem bewu"sten Montag zu helfen.

Viele Gr"u"se
Michael

To: gauderer
Subject: Juergens Promotion 

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

Date: Tue, 18 Oct 1994 10:49:46 +0100 (MET)
From: Michael Rohrdrommel <mrohr@wiwi.uni-frankfurt.d400.de>
Subject: Space Hulk and MOM

> 2)  I've heard that Microprose's new Master of Magic (similar to Master of
> Orion) is NOT GUS compatible.  Does anyone know if an independent patch will
> be made like one was for MOO.  (I've also heard the game is pretty buggy

Dunno, but MOM works fine with Megaem using either Roland or GM and you 
get some nice Digi Sounds too.

> right now, so I'm probably gonna wait awhile before buying it.)

There is already a patch available that fixes some bugs (e.g. MOM 
sometimes like to corrupt it's maps ).

If someone is interested in getting the patch, let me know and i'll put 
it on our ftp-site.

cu,

Michael


 -----------------------------------------------------------------
Michael Rohrdrommel                      Network/News Administrator
mrohr@wiwi.uni-frankfurt.d400.de         Institute of 
										 Applied Computer Sciences
Fax  : +49 69 798 8585                   University of Frankfurt
 -----------------------------------------------------------------

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

Date: Tue, 18 Oct 1994 18:36:15 MET-1
From: "The Magic Friend" <SZABO@btkstud.jpte.hu>
Subject: To the attention of the staff at Gravis! Reg. card probs.

		Hi everybody, mainly, you Vince for revitalizing this list!
		
	My problem is about the registration card. I live in Hungary, I 
bought my GUS in the spring in a local computer store, I sent my 
registration card to the Logitech SA, to Switzerland in April, but up 
till now there is no answer at all. :( A big flat dump SILENCE! For 
more than a half year... I do not believe that the processing of the 
arrived reg. cards takes so long...
	I could imagine that my card was lost during the mailing, but I 
am not the only one who has no reply as I know it. I know other people 
here in Hungary having the same 'nothing'. Has Gravis any problem 
with the ex- East-European block countries (i.e. mailing 
difficulties etc.), especially with mine or something else is wrong?
	Any help would be appreciated
	Bye
								  Lorand Szabo
								  

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

Date: Mon, 17 Oct 1994 22:01:46 -0400 (EDT)
From: "Christopher M. DiPierro" <cdipierr@wam.umd.edu>
Subject: Re: which type of DRAM

On Mon, 17 Oct -1, GUS Server wrote:

> If I rip six 514256 off my old video board could I use them to upgrade my  
> GUS to 1 MB?

Any 256x4 DRAM chips will work on the original GUS.  I believe that the 
Ultrasound requests 100ns chips or faster, so beware of that, but 
otherwise if the video card uses these chips, then it should work fine. 
(256x4 means that 8 chips = 1 meg).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Chris DiPierro: cdipierr@wam.umd.edu
University of Maryland at College Park
To quote IBM: "Think"

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

From: schmitz

Hallo!
Ich bin erst seit gestern wieder hier und weiss von nichts...
Na gut, jetzt weiss ich es. 
Eigentlich habe ich im Verlauf der naechsten Woche immer Zeit,
wenn moeglich aber nicht frueh morgens, ok?
Gib mir am besten per Mail bescheid.
Danke

Stefan (schmitz)

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

From: jensen

Hallo Patric,

ich bin bereit beim Dekorieren des Wagens und beim Basteln des Huts 
zu helfen. Sehr wahrscheinlich komme ich morgen in die Kaffeerunde.
Anschliessend koennten wir uns noch einmal darueber unterhalten.

Tschuess
Peter.

Subject: New User Info

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

From: gus-general-request@gaia.ucs.orst.edu (GUS Server)

X-Star-Trek-Quote: He's Dead Jim.
X-School: Penn State University
X-Nickname: <<APOCALYPSE>>, Lord of Destruction

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

From: Walid Dabbous <Walid.Dabbous@sophia.inria.fr>

Dear all,

There is a possibility for a PhD grant from INRIA on the following
subject. 

Support of Multimedia Applications on Networks with Mobile Hosts

Multimedia conferencing is supported on the Internet. 
Problems concerning network congestion and resource sharing
are being addressed and solutions proposed for "adaptive"
multimedia applications. These applications probe continuously
the network and adapt their throughput in order to avoid network
congestion (e.g IVS or INRIA Videoconference System developed at
INRIA). 

The deployment of mobile hosts introduces a large component of
variable bandwidth links in the Internet. These hosts can be accessed
over radio links with differents characteristics (speed and error
rate). The support of multimedia applications on mobile hosts requires
therefore algorithms to control the transmission taking into account
the adaptability of these applications, and the constraints from the
changing topology of the network.


Prerequisite:

Diplome d'Etude Approfondies (DEA) or M.Sc in networking or computer science.
to master C/Unix programming.
Preferably courses on multimedia applications and mobile networks.


If interested please send your resume to me at:

Walid Dabbous                       | Email : dabbous@sophia.inria.fr
INRIA U.R. de Sophia Antipolis      | Phone : +33 93 65 77 18
 2004, Route des Lucioles BP 93     | Telex :      97 00 50 F        
 06902 Sophia Antipolis CEDEX France| Fax   : +33 93 65 77 65       







------- End of Forwarded Message


Originator: gnn-announce@gnn.com
Sender: gnn-announce@amber.ora.com

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

From: Torsten Braun <Torsten.Braun@sophia.inria.fr>

------- Forwarded Message

	(5.65c8/IDA-1.2.8) id AA19083; Tue, 4 Oct 1994 19:15:49 +0100
	(5.65c8/IDA-1.2.8) id AA07005; Tue, 4 Oct 1994 19:15:21 +0100
		  by iraun1.ira.uka.de with SMTP (PP); Tue, 4 Oct 1994 19:10:58 +0100
		  Tue, 4 Oct 1994 15:39:52 +0100
To: end2end-interest@ISI.EDU
Subject: PhD proposal at INRIA Sophia Antipolis

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

End of GUS Daily Digest V15 #11
*******************************
