Advanced Gravis Computer Technology Ltd.
HEAD OFFICE: US DISTRIBUTION CENTER:
3750 North Fraser Way, #101 Suite H, 3140 Mercer Ave.
Burnaby, BC, Canada Bellingham, WA, USA
V5J 5E9 98225
Tel (604) 431-5020 Fax (604) 431-5155 FTP: ftp.gravis.com
WWW: http://www.gravis.com Email: ntsound@gravis.com
_________________________________________________________________________
INSTALLATION INSTRUCTIONS AND README
for the
UltraSound Plug & Play Windows NT
Driver / Software Installation Instructions
Public Beta 2
- July 11, l997 -
_________________________________________________________________________
CONTENTS
1. Introduction
2. Installation of the Windows NT Plug & Play Subsystem
3. Running the UltraSound Plug & Play Windows NT Driver Uninstall
4. Installing the UltraSound Plug & Play Windows NT drivers
5. Using the 4 Megabyte RAM patch set from the UltraSound CD-ROM
6. Using other RAM patch sets
7. Troubleshooting
8. Bugs fixed
1. INTRODUCTION
Enclosed in this package are drivers and instructions for using the
UltraSound Plug & Play in Windows NT. Please read through this document
completely before beginning installation process.
It is recommended you print this file so you have the instructions
handy during the installation process. It is also recommended that you
copy all these files to a floppy in the A: drive and install from
there.
You must log into Windows NT as "administrator" otherwise the
installation will not be successful. If you are using a non-English
version of NT that does not use the word "administrator", create a
user with full admin privileges and you should then be able to perform
the installation as that user.
2. INSTALLATION OF THE WINDOWS NT PLUG & PLAY SUBSYSTEM
The PnP subsystem of Windows NT 4.0 must be installed prior to
installing the UltraSound drivers. If the PnP subsystem is already
installed, go to section 3.
NOTE: The Windows NT PnP subsystem is not normally installed during the
Windows NT installation process, even if you have ISA Plug & Play
cards in your system. Most people will need to follow this step.
Step 1: Insert the Microsoft Windows NT 4.0 CD-ROM into your CD-ROM
drive.
Step 2: When the Windows NT setup screen show up, select "Browse this
CD". (Alternatively you can browse using Windows Explorer).
Step 3: Browse to the directory \DRVLIB\PNPISA\X86, right click on the
file PNPISA.INF (the file that looks like a notepad) and select
"Install".
Step 4: When prompted to restart your computer, select "Yes". When
Windows NT restarts, you will need to follow the instructions
in section 4.
3. RUNNING THE ULTRASOUND PLUG & PLAY WINDOWS NT DRIVER UNINSTALL
If you wish to install over existing UltraSound Plug & Play drivers, or
you have previously installed the PnP subsystem but did not install any
drivers for the UltraSound, you must follow this step.
Step 1: Run UNINSTNT.EXE included in this package, either by selecting
"Run" from the Start menu, or by double clicking on it from
Windows Explorer.
Step 2: Select OK to remove any drivers and clear the system registry
of UltraSound Plug & Play information.
Step 3: When prompted to restart your computer, select "Yes". When
Windows NT restarts, you will need to follow the instructions
in next section.
4. INSTALLING THE ULTRASOUND PLUG & PLAY WINDOWS NT DRIVERS
When Windows NT restarts after following the steps in section 2 or
section 3, make sure you log in as "administrator". The installation
proceeds as follows:
Step 1: A "New Hardware Found - UltraSound Plug & Play (Synth & Codec)"
dialog will appear, indicating Windows NT has found the
UltraSound Plug & Play.
Step 2: Select "Driver from disk provided by hardware manufacturer",
then click "Ok".
Step 3: At the "Install from disk" dialog, select A: drive and click
"Ok". If you are not installing from drive A:, select "Browse"
and browse to the directory where the UltraSound Plug & Play
drivers are located.
Step 4: Select "UltraSound Plug & Play Synth/Codec" and click "Ok".
Step 5: The "Ultrasound PnP COnfiguration" screen should appear.
If there are no conflicts, select "Ok". If there are conflicts,
change the resource values to clear them, then select "Ok".
NOTE: Windows NT does not always correctly identify all
conflicts. See the troubleshooting section below if you have
audio problems after completing the installation.
Step 6: If prompted for an IDE driver, select "Windows NT Default
Driver", or "Do not install driver" if you do not wish to use
the UltraSound's IDE interface.
Step 7: If prompted to install "UltraSound Plug & Play (SB Compatible
Audio)" or "UltraSound Plug & Play (MPU-401 GM Music", select
"Do not install driver"; these items are not currently available
and this should eliminate the finding of new hardware when
restarting Windows NT.
Step 8: When prompted to restart, select "Yes". When Windows NT
restarts, audio should be working correctly.
5. USING THE 4 MEGABYTE RAM PATCH SET FROM THE ULTRASOUND CD-ROM
If you have already installed the 4 megabyte patch set for use in
Windows 95 or Windows 3.x, it should already be accessible in Windows
NT, provided you installed it to the C:\GRAVIS\ULTRASND\PATCHES
directory. Otherwise follow these steps.
Step 1: Using EDIT, add the following line to C:\AUTOEXEC.BAT:
SET INTERWAVE=C:\GRAVIS\ULTRASND
This line may already be there from a Windows 95/Windows 3.x
installation.
Step 2: Insert your UltraSound Plug & Play CD into your CD-ROM drive.
Step 3: When the Setup runs, click the "4MB Patch Set" button.
Step 4: Install the patch set to C:\GRAVIS\ULTRASND\PATCHES
The patch set should now be accessible in Windows NT. To select it,
load the "InterWave Properties" from control panel, select the "MIDI"
tab, select the "4MB RAM Patch Set" and click "Apply".
NOTE: If you really want to use the patch set from a different
directory, you must change the IWDIR environment variable.
To do this, run REGEDIT and change the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Environment\IWDIR
6. USING OTHER RAM PATCH SETS
If you have used other RAM patch sets with the UltraSound Plug & Play
under Windows 95 or Windows 3.x, you would have had to edit the IW.INI
file. The Windows NT drivers do not use the IW.INI file, instead they
store all information in the system registry.
To use your own patch set, you will need to manually edit the registry
with regedit, by changing keys under HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\guspnp\Parameters\Device0. Information is
organized in the same manner as the IW.INI file, except that when
defining patch directories, environment variables (such as IWDIR)
can be automatically expanded.
7. TROUBLESHOOTING
The most common cause of problems are resource conflicts. Tell tale
signs are system lockups when trying to play sound is being played
(DMA channel conflict), or looping sounds (IRQ conflict).
Unfortunately Windows NT does not correctly identify all conflicts.
If you think you have a DMA channel or IRQ conflict, try changing
the resource value and restarting your system. Resources (and other
UltraSound settings) can be changed in the "InterWave Properties"
control panel applet.
(Start->Settings->Control Panel, InterWave Properties).
8. BUGS FIXED
Unable to change Patch Set:
Has been fixed. A bug in guspnp.sys could cause this on a per machine
basis, the return value of one of the kernel functions was not set.
This problem seems to only show up in a free build version of the
drivers, on some machines. This has also been fixed.
New Hardware Found messages at startup:
Fixed with use of new .INF file allowing user to not install drivers.
Changing volume in various apps causes drivers crash:
Many different apps that showed a volume slider could cause the drivers
to crash, or go to zero volume when the volume was changed. This was a
problem in the handling of the WODM_SET_VOLUME message. This has been
fixed.
Sound breaks up in Diablo under Service Pack 3:
We increased the number of interrupts per second. This seems to have
improved performance quite a lot.
Interwave Control Panel not removed during uninstall:
Has been fixed.
Midi in doesn't work:
This was a timing issue that had happened before the first release.
It appears to have resurfaced during our last round of changes.
Has been fixed.
[END OF FILE]
