               _____________________________________________

                    GRAVIS ULTRASOUND Plug & Play (Pro)
               _____________________________________________

                                     F A Q 

                                  version 0.8

                                As of 10-24-96

                  Send comments to: M.Schmitt@fsw.ruu.nl
             GUS and games comments to: cambell@netlink.co.nz

                   Last Edited by deckerd@sd.cts.com 9-01-97

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


This is the sixth release of a mini FAQ for the Gravis Ultrasound Plug & play 
(Pro) [and probably the best, for advance users - ed.]. Many questions in the 
sound newsgroups make it a necessary move. 

From this moment on the filename for this FAQ will be: gpnpXX.FAQ where XX is 
the version number. So this particular one is called gpnp06.FAQ .


Latest News
===========


As of 10/96, the public beta of the GUS pnp 2.0 drivers are out. What do these 
drivers offer compared to the older ones we all loved to hate? First of a lot 
of fixes and additions. I will just name a few. IWSBOS and Windows DOS box 
support now works. Installations works flawlessly on most systems 
(*reinstallations* still don't). There is support for sysex commands (programs 
like BAN IN A BOX will not crash your system anymore). There is a new Control 
Panel applet that lets you see what your settings are, and edit a few. And 
probably most important to techies, the drivers allow them to change patch 
sets on the fly. 

The bad news? Like I hinted at in the last paragrapgh, reinstallation over the 
old 1.3 drivers requires manual Registry editing. Since this is a beta release 
there are still some minor bugs, like trashing your real mode config files ;) 
, but most you can live with I think. However, there is one big annoyance: all 
the GUS effects, like echo and reverb, are gone! <|( Gravis is aware of this 
problem, but because newer 64-bit sound cards that are much easier to install 
and configure, like the SoundBlaster 64, are out and the 16-bit cards are 
getting older, they will probably never have time to fix it or release future 
revisions to the drivers, so this is it, folks :(    


Internet Sites 
==============


Advanced Gravis Computer Technology Ltd.

HEAD OFFICE:                          US DISTRIBUTION CENTER:
Suite 101, 3750 North Fraser Way      1790 Midway Lane
Burnaby, BC V5J 5E9                   Bellingham, WA, USA
Canada                                98226

Tel (604) 431-5020  
Fax (604) 431-5155  
BBS (604) 431-5927 V32bis

Internet FTP: archive.epas.utoronto.ca
InterNET EMail: tech@gravis.com  

Web Site:  WWW.GRAVIS.COM
Alias for: ADVANCED.GRAVIS.COM (204.50.210.1)
Contact: Malcolm, Paul  (PM570) pmalcolm@gravis.com
         (604) 431-5020


WWW Sites: 
----------

http://src.doc.ic.ac.uk/packages/ultrasound/
http://members.aol.com/gravistec/home.html
http://src.doc.ic.ac.uk:/packages/ultrasound
http://www.st.nepean.uws.edu.au/pub/pc/ultrasound/
http://gpu.srv.ualberta.ca/~itam/digest.html
http://www.student.adelaide.edu.au/~godfathr/gus/gus.html
http://www.amd.com/html/products/ind/interwave/wave.html


FTP Sites
---------


      Site        Archive                 Directory
      ----------  ----------------------- -----------------------------

      MasterSite  ftp.gravis.com

      N.American   
      Mirror:     ftp.orst.edu            pub/packages/gravis

                  wuarchive.wustl.edu     archive/packages/ultrasound
      Asian
      Mirror:     nctuccca.edu.tw         PC/ultrasound

      European    src.doc.ic.ac.uk        packages/ultrasound
      Mirrors:
                  ftp.pwr.wroc.pl         pub/ultrasound
                  ftp://osiris.univ-mlv.fr


      Australian      
      Mirror:     ftp.mpx.com.au          /ultrasound/general

      South
      African       
      Mirror:     ftp.sun.ac.za           /pub/packages/ultrasound


Installation
============


Ram expansion
-------------

The AMD interwave chip can address 16 MB of memory. The GUS, however, can only 
address up to 8 MB of 30 pin SIMMs, no parity, 1mb, 2mb, or 4mb, 80 NS or 
better). 
         

Undocumented IWINIT Parameters
------------------------------          

If you type:

IWINIT -? 

You will get IWINIT's complete list of command line paramters, as follows:

UltraSound Initialization Version 2.23

USAGE: iwinit [options]

      ID=XXXXXX         vendor id for sound card

      INTERWAVE=X:\XXX  path & filename of configuration file. (.SYS driver)

      IWDIR=X:\XXX      path where software installed

      -q[X]   Quiet [X = 1: Error Messages Only; X = 2: No Messages]

      -v[Y]   Verbose [Y = 1..9; Verbosity level, 9 = Most Verbose]

      -r[Z]   PnP cards previously assigned read data port Z.  For use with
              non-standard configuration managers.

      -hunt   Hunt down card isolated by bad BIOS, bad CM, or other
              non-standard method.  Execute once, manually, not in autoexec.

      -off    Completely deactivate audio card.

      -pnp    force pnp initialization

      -legacy force legacy initialization


If you type:

IWINIT -V 

without a Y value, or if Y = 1..4, only the info will be given. If Y = 5, the 
hardware will be configured. If Y=6..9, the hardware will be configured, and 
the resulting settings will be saved into the IW.INI file.


QUESTIONS AND ANSWERS
=====================


Q. I run Windows 95. The sound in a DOS box is OK, even DOS games work great. 
However, I have no sound for *windows* apps. I have tried literally 
*everything*. I've even tried to reinstall the 2.0 drivers several times, to 
no avail. I have looked at every FAQ on the net - you name it, I've tried it. 
I have checked and rechecked my GUS environment variables. *NOTHING* will 
work. I've done everything short of hacking the Registry, looking for 
answers. I've even contacted Gravis Customer Support - but they said that 
they couldn't help me because my questions were way too advanced! :D
*WHAT* the heck is wrong? 

A. [...I had this problem for literally a month before I finally took the time 
to pull out *all* of the entries in the Registry relating to the GUS. 
Apparently, There are two very important files - MMCI.DLL, and MMDEVLDR.VXD - 
that you *must* have in your WINDOWS\SYSTEM subdirectory prior to installing 
the new GUS 2.0 drivers. If these files are not present, and/or not located in 
the correct place on your hard drive, the GUS 2.0 driver installation programs 
will not setup your GUS configuration correctly, especially the Registry 
entries, and thus no sound for Windows or its apps. To solve this problem, 
follow the REINSTALLING THE GUS DRIVERS procedures, at the end of this 
document. - ed.] 
 
Q. My Windows 95 apps will work, and I have great DOS box sound, but Media 
Player won't play WAV files, nor will any other MCI-compatible apps play WAV 
files. what's wrong?

A. There may be a problem with the driver file entries in the group of 
Registry entries dealing with WAVEAUDIO. For example, look through the 
Registry using Regedit to see if you're using MSACM32.DLL, especially in the 
MediaResources section. If you are, or if the path to the file you're using is 
wrong, change it to the correct path, and use MSACM.DRV.


Q. ARE THERE ANY GUS GURUS OUT THERE THAT I CAN CONTACT?

A. 

   * Justin Cooney Advanced Gravis jcooney@gravis.com

   * cambell@netlink.co.nz

   * [deckerd@sd.cts.com - ed.]

Q. WHEN I START A WIN95 DOS BOX AND TYPE 'IWINIT' OR 'IWSBOS' TO INITIALIZE 
   THE CARD, I GET A MESSAGE THAT SAYS "INTERWAVE CARD NOT FOUND" - WHAT 
   GIVES? 

A. This seems to be a known bug. Gravis suggests in the manual that you just 
type IWINIT a few more times, until the card does initialize. This has never 
worked for me. 

[It hasn't worked for me either - however, the problem is kept to a minimum if 
you follow the steps below: 

   1. Make sure you have a good, accurate copy of IW.INI (like you want it) in 
a subdirectory somehwere - I keep it in the INIBAK subdirectory under my GUS 
subdirectory.

   2. Add the line below to the very end of the lines that the GUS setup 
utilities add to your AUTOEXEC.BAT file (you want this line to be executed 
*last*, as far as GUS lines go):

copy [d:][path]iw.ini [d:][path]iw.ini >nul
   
   The first [d:][path] is the backup directory, and the second [d:][path] is 
the GUS directory. Apparently, when IWINIT generates the "INTERWAVE CARD NOT 
FOUND" message, it sets all the IRQS, Base Addresses, etc in the IW.INI file 
to 0. The line above refreshes the IW.INI file at boot-up, so that a good copy 
is always available to IWINIT. - ed.] 

Q. DOES MY INSTALLED MEMORY ACTUALLY WORK?

A. With the standard version you will have chorus and reverb if you install 
memory. If you have lots of memory like 4 or 8 Mb open cakewalk express. Load 
a few midi files in cakewalk express. After every file you will notice a drop 
in the available memory. Although cakewalk express uses patch caching, all the 
patches are still in memory. One last way is to look for disk activity during 
patch caching. If you use the standard gus set which is 5.6 Mb and you have 8 
Mb installed, disk activity should stop if the complete set is loaded. 

Q. HOW CAN I FIX PROBLEMS RELATED TO DMA/IRQ?

See REINSTALLING THE GUS DRIVERS, at the end of this document.

Q. HOW DO YOU INSTALL THE ULTRASOUNDCANVAS DRUM PATCHES?

In Ultrasouncanvas.zip the banks are bugged. i.e: all banks are 1 number 
higher than what they should be. in USC*.* they're ok. Cakewalk: Setup channel 
10 to use Roland GS Drumkits. you should then have a list of banks you can 
choose from. There are no instruments bank in USC, just drums. Remember that 
you have to set up a set in iw.ini that uses all the banks in the kit. 

Example: 

[vendors]

rom_amd_4m=ROMAMDGS_4_2_
rom_amd_1m=ROMAMDGM_1_1_
amd_4m=gsfull4m.fff
amd_1m=gmfull1m.ff8
ultraGS=ROMAMDGM_1_1_, std.fff, pwr.fff, room.fff, brush.fff, elec.fff
default=ultrags

[vendor ultraGS]

std.fff=c:\ultrapnp\ultra
pwr.fff=c:\ultrapnp\ultra
room.fff=c:\ultrapnp\ultra
brush.fff=c:\ultrapnp\ultra
elec.fff=c:\ultrapnp\ultra

Q. IS THE SDK RELEASED?

Yes - it's at:

ftp.gravis.com/public/sdk/pnpddk.zip

Q. HOW CAN THE CDROM/IDE/ATAPI/GAME PORTS ON THE GUS PNP BE DISABLED?

A. If you haven't installed the 2.0 drivers yet, do so according to 
REINSTALLING THE GUS DRIVERS, at the end of this document. Then run 
PNPCFG.EXE. 

Q. WHY DON'T EFFECTS WORK ON DRUM SOUNDS IN RAM PATCHES?

A. In Windows 95, it's because of a bug in the drivers. Gravis is working on a 
fix for this. 

In DOS and Windows 3.x, this is a result of faulty patch conversion. Since the 
GIPC utility still has a few bugs, some of patch parameters are incorrectly 
converted. One of the results is that effects on converted drums sounds do not 
work. The effects *do* work on the 1mb ROM patches and the 4 Mb amd patch set. 

Here's a fix for the problem suggested on usenet: 

"Some people owning a Gravis Ultrasound Plug&Pray with 1mb-> probably have
noticed that GIPC 1.11 converts the drum banks incorrectly, resulting no
effects (reverb, chorus) on drums at all...zilch! none.. So, what you'll
have to do is to have the converted patchset running (that is, you'll have
to be using it) and do the following. funny thing..it seems like I'm the
first one to actually accomplish this :=)

0) Quit every program you are running
1) Start Cakewalk
2) Select the Settings menu, and click on Midi Devices
3) A new window pops up. For Output, select InterWave MIDI synth, and
   deselect the others. For Input, leave those untouched :)
4) Press OK 
5) Load a midi-file
6) DO NO PLAY IT!
7) Load up Mediaplayer (the one installed/shipped by Windows)
8) Load the *SAME* midi-file as you did in Cakewalk

   (It's VERY important that you load the same midi-file in both programs

9) DO NOT PLAY IT YET!!...well..if it does..ok..just let it play.
10) Load up the InterWave Mixer
11) Move the Effects slider to maximum
12) Ok..start playing the tune in Mediaplayer. Enjoy.

What happens is that Cakewalk does something to your GUS in the background! 
Dunno why, but it works! And it surely sounds more heavy!! Anyway, if you want 
to hear the difference, try exiting MediaPlayer, and start playing the tune in 
Cakewalk...... 

If you want to keep the effects enabled on the drums, just keep Cakewalk in 
the background, with the same tune, not playing, just staying there doing 
nothing. Then load up a midi-file using Mediaplayer and the effects will be 
enabled. BUT as soon as you quit CakeWalk, the effects will be disabled. 
However, quitting Mediaplayer is ok. 

Hope this helps. Kevin Boye

Q. WHY DOESN'T PREPGAME WORK ANYMORE?

A. If prepgame game gives you the message: "only works with ultrasound pnp" 
you have to reinstall the DOS drivers. If everything works correctly be sure 
to make a backup of your root directory. The problem is caused by win95. If 
you return to a previous DOS or DOS 7 win95 overwrites the autoexec.bat and 
config.sys files with version belonging to that installation. When installing 
the Gus pnp DOS drivers the current autoexec.bat is patched but not the back 
up used by the win95 boot manager. 

Q. I HAVE TO KLUDGE MY IRQS IN DOS4GW GAMES IN DOS ONLY CONFIGS - WHY?

A. The standard version of DOS4GW only supports IRQs lower than 8. It supports 
up to 32MB ram, so for now, most games don't require the professional 
version, called DOS4G. That usually costs an additional $500, but I do believe 
it supports IRQ 8 - 15. Until more games require more than 32MB ram, you will 
still see this problem. However, one guy mentioned there is a patch; that 
might help. As a DOS4GW coder, I can tell you it makes life much easier to 
code 32-bit programs - that is why most games use the standard version of 
DOS4GW. Also, the standard version is royalty-free, so it is much cheaper than 
using the professional version. None the less, Rational Systems should fix 
this to allow for all IRQ lines. It has something to do with switching to 
Real-Mode to access those extra IRQ lines. What doesn't makes sense is, IRQ 8 
- 15 are tied to IRQ 2. That is why you often see the IRQ 2/9 option. Usually 
IRQ9, 10 and 11 are free for use. Sometimes 12 is too. 13-15 are used for 
other options, like the HD, CD-ROM, etc... (Kevin Duffy) 

Q. MY DOS TRACKER ONLY RECOGNIZES 1MB RAM. WHY?

Native interwave support is not yet implemented in DOS-only configurations, 
and now that everyone on this planet is using Windows 95, it probably never 
will, not even in a DOS box. 
                             
Q. IT POSSIBLE TO USE OTHER PATCHES WITH MEGA-EM?

A. No. The current version can only use the hardware patchset on thet GUS pnp. 

Q. WHY DOES IWINIT REPORT CARD BUSY, CLOSE ALL APPLICATIONS IN WIN95 DOS-BOX? 

A. If you are using the 1.3 drivers, if you haven't already, download the 2.0 
drivers, now out, and install them and all their information according to 
REINSTALLING THE GUS DRIVERS, at the end of this document. If you still get 
this error, well, Gravis is aware of this problem, but because newer 64-bit 
sound cards that are much easier to install and configure, like the 
SoundBlaster 64, are out and the 16-bit cards are getting older, they will 
probably never have time to fix this. Sorry <|( 
                  
As a kludge, try running a wav file with the media-player before opening the 
Dos-box. After that the card is free and you may get music in DOS programs. 
Sound Effects still won't work, though. 

Q. HOW CAN I USE THE CARD WITH LINUX?

A. You need to boot to DOS and run IWINIT, then *warm boot* to linux. It'll be 
detected as a gus, or if you run ultrinit also as a MAX. 

Q. NEW HARDWARE DIALOG IN WIN95 SAYS "l l V" INSTEAD OF "GRAVIS
   ULTRASOUND PLUG AND PLAY. WHAT IS HAPPENING?

A. The flash BIOS on the GUS pnp is not initialized in the proper way. 
   Download the new 2.0 drivers from the Gravis site to update your BIOS. 

Q. WHAT ABOUT THOSE OUT OF SPEC DIODES?

A. "I recently purchased a GUS for $200,00 for my new Pentium 133 and have 
really enjoyed playing with it the past few days. I decided to try the mic 
input on it to see if I could record some sounds. This is when I noticed a 
tremendous DC offset in the recording, about 50%. This means the signal will 
be clipped on one side long before the other. In looking at the card itself I 
noticed two glass surface mount diodes D1 and D2 that look like they are to 
protect the mic input on the AMD chip from voltage spikes. They go to ground 
and the +5V supply. I suspected that they were leaky so I got out the ol' 
soldering iron and removed them. A resistance check showed one to have 10K 
ohms and the other one a little more in the reverse direction. I installed two 
new diodes of a differeent type (1N4148's). Put the sound card back in and 
wala...NO more DC offset. It's fixed. It looks like Gravis had let a bad 
product get out of their factory. This is yet another example of why glass 
surface mount diodes should not be used in production where leakage current 
can affect the circuit. I would suggest that Gravis change the design to use 
an SOT type surface mount package for this aplication. This package has two 
diodes in the package, so it would even cut down the parts count." 

- From the usenet database...

Q. MY SYSTEM HANGS WHEN IWINIT TRIES TO INITIALIZE THE GUS PNP. WHY?

A. Apparently your BIOS is not compatible with the plug & play on the gus ( I 
am not sure though.. ). Try to run iwinit with the following switch: IWINIT -
bbios Note that bbios must be in lowercase otherwise it will not work. If this 
does not work and your PC has a pci bus system look in your BIOS setup and 
check if no IRQ's are reserved for isa slots. If so change all the IRQ's you 
need for the Gus pnp. If still no success try to upgrade the BIOS (this seems 
to be a problem with some versions of the AMI BIOS). The same problem can be 
caused by Microsoft InPort Mouse 1.0. removing the inport mouse will solve the 
problem. Another possibility to solve this problem is changing jumper 9 on the 
card. This will disable the plug & play capabilities of the gus pnp. 

Q. GIPC SAYS SOMETHING lIKE "CANNOT OPEN PATCH FILE...". WHY?

A. This is a known bug in GIPC; Change the following line in all sections 
   where it exists in the ULTRAINIT.INI file: 

PatchDir=C:\ULTRAPNP\midi 

to:

PatchDir=C:\ULTRAPNP\midi\ 

After conversion do not forget restore the lines! A suggestion would be to 
comment out the old lines before conversion, then uncomment them and comment 
the new lines after conversion.

Q. HOW CAN I CHANGE THE VOLUME IN DOS CONFIGURATIONS?

A. Use the DOS mixer, included in the 2.0 drivers package. Or, go to the 
Reveal website and download the Extreme drivers package; it contains a DOS-
mixer program. If you use mega-em for roland or soundblaster emulation you can 
set the volume also. 

Q. JOYSTICK PROBLEMS. WHAT CAN I DO?

A. Try running iwsbos (or sbos), then change the sound setting to 
Soundblaster. In this way you will lose sound quality but probably your 
joystick will work again. 

Q. CD AUDIO FAILS TO WORK. WHY?

A. You must use the MCI driver, whether you are running windows 3.x or win95. 

   You must also make sure that the wire connecting your CD-ROM's audio port 
   to the GUS has the correct pinout. Here's how:

   1) Get a small screwdriver (such as the ones used for eyeglasses) or a
      similar tool

   2) If you look at the white, block-ish plug that attaches to the GUS PnP,
      you will see that there are three wires that go into the plug. Each 
      wire has a crimped-on connector at the end. These connectors are held 
      in the plug by small, plastic fingers. One at a time, use the 
      screwdriver to lift each finger and pull the wire out of the plug.

   3) Look at how the cable connects to the CDROM and note which wire goes to 
      which lead. If you look at the GUS PnP, you will see that the four pins 
      on the boards are labeled 'GLGR' (or something like that). As you might 
      guess, G is for ground, R is for right and L is for left. Look at how 
      the plug needs to fit into the connector on the GUS board and figure out 
      how the leads need to be placed in the plug to make the right 
      connections. 

   4) To insert each wire back into the plug, just insert the crimped-lead 
      into the appropriate hole and push. It will snap into place. 

   5) Once all three leads are back in the plug, insert the plug back into the 
      GUS PnP connector. 

As a note, I've heard that some people prefer to file off the alignment key on 
theplug so that they can insert it backwards. This also works, but does cause 
permanant alteration to the plug. - Eric Karlson

Q. HEAR CLICKS AND GARBLED SOUND. WHAT IS HAPPENING?

A. IRQ conflicts - or schizophrenia :-). Change the IRQ of the gus pnp or the 
conflicting device. 

Q. PROBLEMS WITH SOUND IN DOS BOXES

A. The GUS's key DOS environment variables - ULTRASND and BLASTER - *must* be 
   correct. Change the SET ULTRASND= and SET BLASTER= lines in your 
AUTOEXEC.BAT file to what they should be.

Q. RECORDING WITH THE MICROPHONE SOUNDS BAD

A. On the card you will find a switch to disable the onboard amplifier for the 
mic input. If your recording sounds wrong, change the setting of this switch. 

Q. WHERE DO THE NEW 2.0 DRIVERS COME FROM?

A. They were written by E-Tek of Rochester New York for AMD, then distributed 
to Gravis. The drivers were designed to run on a Reveal WaveExtreme-32 
InterWave soundcard (which is virtualy identical to the AMD InterWave Standard 
Reference Design). Source code of these unfinished drivers is with Gravis now 
and after several beta's we have now the first public beta as implemented by 
Gravis. 

Q. HOW ABOUT OS/2 SUPPORT?

A. http://www.polsci.wvu.edu/Henry/Sander
   ftp-os2.cdrom.com (ultra120.zip)
   hobbes.nmsu.edu (ultra120.zip)

   Sander van Leeuwen (s509475@dutiwy.twi.tudelft.nl)
   Robert J. Manley (rjm@io.org)

Q. HOW DO I MAKE A GUS COEXIST WITH A SOUNDBLASTER 16?

A. Uuggh!! why? :D if you want to do *that*, get rid of *both* your gus and 
your soundblaster 16, and upgrade to any one of the new, fine 64-bit sound 
cards, like the SoundBlaster 64. Also, they are *much* easier to install and 
configure than the GUS ever was. 

Q. HOW ABOUT THE FUTURE OF THE INTERWAVE CHIP?

A. Since it is 16-bit, none, really, now that 32-bit and 64-bit audio DSP's 
are affordable. :)



ADVANCED QUESTIONS
==================



Q. I have multiple boot configurations, and run ID games. Anytime I run either 
the Gravis Setup or Windows 95 Setup, it trashes my configurations! What's the 
best way to handle this?

A. Make sure that the Windows 95 setup works *first*. Then make your DOS box 
batchfiles. *THEN* try to re-enable your DOS only configurations.

When you're all done, take all the setup lines in your AUTOEXEC.BAT file 
dealing with the GUS, and put them in their own separate batchfile. Then add a 
line in the AUTOEXEC.BAT file calling this batchfile. I call mine GUSINIT.BAT. 

It's a good idea to do this with MSCDEX and SMARTDRV, too, if you have ancient 
real-mode hardware and have to do this, as Windows 95 setup trashes these. 

Q. Why do the GUS utilities, such as PLAYSND and IWINIT.EXE, always report 
   "can't get message file" ? 

A. The path to the GUS .MLS file set is wrong in your IW.INI file. Fix the 
   english= line in the [languages] section so that the path is correct.

Q. Why does IWINIT.EXE report "Interwave card not found", even though my 
   INTERWAVE environment variable and IW.INI files are correct?

A. You will have to add the command-line switch -bbios to the IWINIT line:

   IWINIT.EXE -bbios

Q. How come I get a Blue screen with an EXCEPTION error in my VIWD.VXD file
   when I change my resources?

A. This is caused by the driver thinking there is another device using that 
   resource. Gravis is aware of this problem, but because newer 64-bit 
   sound cards that are much easier to install and configure, like the 
   SoundBlaster 64, are out and the 16-bit cards are getting older, they will 
   probably never have time to fix this. Sorry <|( The good news is that this 
   error is very rare.

Q. Why does Cakewalk Express run really slow after I have installed a MIDI 
   Input Port, without having a keyboard hooked up to the card? 

A. Due to a bug in Gravis's drivers, this happens on SOME systems. This does 
   NOT happen if you have a MIDI keyboard plugged in. Gravis recommends that 
   you do NOT select a MIDI IN device unless you have a MIDI keyboard plugged 
   in. This bug still exists in the 2.0 drivers, and will probably never be 
   fixed. <:(

Q. I've got more than 1 MB of RAM installed on my GUS, and I'd like to set up 
RAM support. How do I do this?

A. The format of the IW.INI file is similar to the format of the configuration 
files that Microsoft uses for its Windows products. The file is split up into 
sections. The beginning of each section is marked with a line with the format. 

[text]

Each line in the configuration file that is not a section header is either a 
blank line, a comment line, or a line containing information needed by the 
InterWave software. Comment lines, which start with a semicolon, and blank 
lines are ignored by programs processing the configuration file. The 
configuration file contains sections for saving mixer options, patches, chip 
setup and sound card emulation (SBOS) options. We'll look only at the patch 
section. 

The InterWave software does not have to assume a specific set of MIDI patches 
will ship with the UltraSound PnP card. The configuration file allows for 
mixing of different patches from different sources, whether they be in ROM, 
RAM, or some in each. A description of a patch configuration starts by listing 
the patch files and assigning a name to the list. For example, assume the 
patches are in three files a.fff, b.fff and c.fff. An entry describing these 
patch files would be found in the [vendors] section. 

[vendors]
favorite=a.fff, b.fff, c.fff

Some of the patches in the configuration files may be redundant. The InterWave 
software will choose the last patch it finds in the list. For example, if a 
music score is looking for a piano, and the piano patch is in both the c.fff 
file and the a.fff file, the software will choose the patch in c.fff. 

The location of the patches is determined by checking the filename. If the 
first three characters are ROM, then the filename is used to search for the 
appropriate set. If the first three letters of the filename are not ROM, then 
the configuration file is searched for a section labeled [vendor tag] where 
tag is the same tag used to identify the patch files. For example, the section 
to locate the patches described above might be: 

[vendor favorite]
a.fff=c:\patches\a_set
b.fff=d:\patches\more\b_set
c.fff=n:\public\sharwar\patches\c_set

Each patch file is listed on a separate line with the path to that file. The 
path is also used to locate any sample data associated with the patch file. 

By default, the UltraSound PnP uses the 1MB ROM patch set. In that case, the 
patches section looks like this: 

[vendors]
rom_amd_1m=ROMAMDGM_1_1_
default = rom_amd_1m

Because the patches are in ROM, there is no file path, and thus no [vendor 
rom_amd_1m] section. 

Now, say you wanted to add some patches that you converted using GIPC, and 
they are in a file called GIPC.FFF. If you wanted to use only the newly 
converted patches (and no others), you would setup the patches section as 
follows: 

[vendors]
rom_amd_1m=ROMAMDGM_1_1_ 
-this is the original ROM-only configuration

gipc=gipc.fff 
-add this line for the new configuration

default=gipc
-this line shows which configuration is chosen

[vendor gipc]
gipc.fff=c:\gipc\destdir
-where the new InterWave patch file is located

If you wanted to combine the ROM patches and your patches, with your patches 
taking precedence over the ROM patches, you would setup the patches section as 
follows: 

[vendors]
rom_amd_1m=ROMAMDGM_1_1_
rom_and_gipc=ROMAMDGM_1_1_, gipc.fff
default=rom_and_gipc

[vendor rom_and_gipc]
rom_and_gipc=c:\gipc\destdir

If you modify the InterWave initialization file in this way, you must reboot 
the system for the settings to take effect. 

If you have the Gravis CD, there are two utilities in the SETUP directory on 
it: SETRAM and SETROM4. 

Run SETROM4 to add RAM support for the Interwave Patch Set, and run SETRAM to 
add RAM support for older programs supporting the GF1 Patch Set. Note that you 
may have to run SETROM4 in plain MS-DOS mode, as a bug in the EXE won't 
recognize the INTERWAVE environment variable in DOS 7.0 (win95). If this 
happens, edit the PIF file that comes on the CD for this EXE so that it runs 
in MS-DOS mode.

SETRAM will create a subdirectory called MIDI in a subdirectory of your choice 
containing 5 MB of .PAT files. Once SETRAM has finished, you will also need 
ULTRASND.INI and ULTRINIT.EXE in your GUS directory. Make sure the paths 
listed in ULTRASND.INI are correct (you can change the name from MIDI to 
something else, by editing ULTRASND.INI, if you want).

SETROM4 will create an Interwave Patch Set on your hard disk - a 4 MB .DAT 
file in the subdirectory of your choice, plus the .FFF Interwave patch file. 
It will also add the path to this file in your IW.INI file: 

[vendor amd_4m]
gsfull4m.fff=[d:][path]

SETROM4 requires that the lines below be in your AUTOEXEC.BAT file when it 
installs: 

@REM ===== Gravis initialization (1.3) =====
@SET INTERWAVE=C:\FIRMWARE\GUS\IW.INI
@SET PATH=C:\FIRMWARE\GUS
@C:\FIRMWARE\GUS\IWINIT.EXE
@SET ULTRASND=220,6,6,7,5
@SET BLASTER=A220 I5 D1 T1
@SET ULTRADIR=C:\FIRMWARE\GUS
@REM ===== Gravis initialization ends =====

If you like to have these lines setup differently, put them in temporarily 
until SETROM4 finishes, then take them out again.

==========================================================================



REINSTALLING THE GUS DRIVERS 
----------------------------

(or, upgrading from the 1.3 drivers to the 2.0 drivers)

   1. If you haven't already, download the 2.0 drivers package from the 
      Gravis FTP or Web Sites and prepare the floppy disks as directed.

   2. Make sure that the MMDEVLDR.VXD and MMCI.DLL files are in your 
      WINDOWS\SYSTEM subdirectory. Use Explorer to see if they exist there. 
      The driver installation programs must be able to access these files. 

   3. Go into the Control Panel and choose Add/Remove Programs. Remove the 
      Ultrasound Plug & Play line. *Do not* reboot the system at this time, 
      unless you have no choice. 

   4. Delete the Gravis UltraSound section in the Start Menu, and delete any 
      shortcuts dealing with the GUS.

   5. Run REGEDIT. 

   6. Delete all entries that have INTERWAV and GRV in them, using the Find 
      and Find Next functions, especially in the MEDIA subkey.

   7. Go to HKEY_LOCAL_MACHINE/SOFTWARE and delete the Advanced Gravis and AMD 
      sections. 

   8. Close REGEDIT, then shutdown Windows 95. 

   9. In the UltraSound directory on your hard drive, move the EMM386.EXE file 
      to a safe place, then delete the UltraSound directory. If you use a 
      CONFIG.SYS file, make sure that all EMM386.EXE lines are correct 
      (especially the paths). 

  10. Delete the IWUNINST and ETEKMOD.INI files from the WINDOWS directory. 

  11. Delete the IWCFGPNL and SETULTRA.VXD files from the Windows SYSTEM 
      subdirectory. 

  12. Delete the OEM[0,1,2,...].INF file(s) in your INF directory.

  13. Delete the GUS directory, then check anywhere else and remove any 
      UltraSound software files you find...You should now have a completly 
      clean computer as far as the UltraSound software is concerned.

  14. Locate and delete (or comment out) each and every line in the 
      CONFIG.SYS, AUTOEXEC.BAT, WIN.INI, SYSTEM.INI, and DOSSTART.BAT files 
      that are related to the GUS soundcard, if any of these files exist on 
      your system. 

  15. Have the GUS 2.0 Drivers Floppy Disks that you prepared in Step (1) 
      handy, and run PNPMAP.EXE from the PREP disk as directed in the README. 
      Use GRAVNOCD.ROM if you want to disable the IDE port. Reboot the 
      computer by turning the computer off, waiting a few seconds, then 
      turning it on again. *BE SURE TO ENTER THE SAFE MODE DOS PROMPT*, not 
      Windows, so that you can continue on to the next step (we're not ready 
      to run Windows yet). 

  16. From the DOS/WIN3X disk, run PNPCFG.EXE to configure the GUS's ports. 
      PNPCFG will reboot the computer - just let it go all the way into 
      Windows.

  17. Let Windows 95 detect the plug and play drivers for the sound card. 
      Insert the WIN95 disk when directed. *DO NOT* reboot the computer, even 
      if Windows 95 asks you to, until *ALL 5* devices have been set up (even 
      if you have disabled one or more devices using PNPCFG, they still have 
      to be "installed"). 

  18. At the end of the Plug & Play detection process, and after Windows 95 
      has completed its boot up process, if the GUS Win95 setup program runs, 
      let it go and follow its directions. If the setup program does not start 
      up, run it from the WIN95 disk. Towards the end if its setup routine, it 
      will ask you to reboot the computer. Do so. If you have multiple system 
      configurations, use the same Windows 95 configuration that you started 
      the installation process from. 

  19. After the second Windows 95 reboot, and after the GUS Win95 setup 
      program has finished, Your Windows 95 apps, including the Windows 95 
      Sound System, should work. Test them, and if everything is ok, we 
      recommend that you back up all of your configuration files, including 
      CONFIG.SYS, AUTOEXEC.BAT, WIN.INI, SYSTEM.INI, and DOSSTART.BAT (if you 
      have one or more of them). As extra insurance, you can also open REGEDIT 
      and export the whole Registry to, say, BACKUP.REG, and include that file 
      in your backup. 

  20. Now, edit the DOS box kludge batchfiles for your DOS apps, until the 
      apps have sound, and again test the Windows 95 Sound System to make sure 
      it still works. If you want to really make sure, reboot the system and 
      test Windows 95 and DOS box sound, each and in that order, *again*.

  21. At this point, if everything is working ok, you're done, unless you have 
      set the GUI= line in your MSDOS.SYS file to 0 and have multiple system 
      configurations via a menu in CONFIG.SYS. If you have DOS-only configs 
      setup this way, it is at *THIS* point that you should try to re-enable 
      your DOS-only GUS  configurations. Be very careful when editing the 
      AUTOEXEC.BAT and CONFIG.SYS files, and if you need to reboot, *always* 
      turn the computer completely off and wait a second or two, rather than 
      just the three-fingered salute or the reset button. 




