1. piper301.zip Driver
2. readme.txt File Contents

readme.txt Driver File Contents (piper301.zip)

This README.TXT file contains instructions for the following activities:

1. Card Installation and PS/2 Configuration
2. OS/2 Warp Driver and Software Installation
3. OS/2 Warp Notes
4. Win-OS/2 Driver and Software Installation
5. Win-OS/2 Notes
6. Contacting Piper Research Technical Support

=====================================================================
====                          Section 1                          ====
=====================================================================

Preparing a PS/2 Reference Diskette
==================================
If you have an older PS/2 system, prepare a backup copy of your PS/2 system
Reference Diskette before you install the SoundPiper card.  Then copy the
file @5130.ADF from this diskette to the backup copy Reference Diskette.
You'll need this backup diskette to configure your system after you've
installed the SoundPiper card.

Installing the SoundPiper
=========================
1. If you have been using your system, turn your computer off.
2. Remove the computer's cover.
3. Select the expansion slot where you will install the SoundPiper.
4. Remove the blank expansion slot cover from the computer back panel
   at the position where you will install the SoundPiper.
5. Insert the SoundPiper card into the selected system expansion slot.
6. Connect the internal CD-ROM audio cable if appropriate.
7. Replace the cover on the system unit.
8. Connect the appropriate interface cables between the SoundPiper
   connectors and your sound output (speakers) or input (microphone) devices.
9. Turn the computer on. If you have an older PS/2 system, use the backup
   copy of your Reference Diskette you prepared earlier for startup. Run
   the automatic configuration option in the 'Set Configuration' program.
   If you have a newer system, the program, supplied on your hard disk,
   will start automatically. The SoundPiper hardware installation is complete.

=====================================================================
====                          Section 2                          ====
=====================================================================

OS/2 Warp Installation Procedure
================================

PLEASE NOTE:
============
If your OS/2 system already has a Sound Blaster Pro MCV driver installed
it must be removed before installing these drivers as directed below.

The easiest method for removal is to edit the CONFIG.SYS file and REMARK
out the two lines in question.  These lines are typically:

device=C:\MMOS2\SBP2D2.SYS 1 1 5 240 4 /N:SBAUD1$
device=C:\MMOS2\AUDIOVDD.SYS SBAUD1$

These should be changed to

REM device=C:\MMOS2\SBP2D2.SYS 1 1 5 240 4 /N:SBAUD1$
REM device=C:\MMOS2\AUDIOVDD.SYS SBAUD1$

After the CONFIG.SYS file has been changed and SAVED, the system should be
SHUTDOWN and RESTARTED before proceeding with the process detailed below.

Driver Installation
===================
In an OS/2 Window type: A:\OS2\EINSTALL SP32

PLEASE NOTE:  THE "SP32" MUST BE ALL UPPER CASE!

Proceed with the installation as prompted on your screen.

=====================================================================
====                          Section 3                          ====
=====================================================================

OS/2 Warp Notes
================================

3D Audio (ES938) support
========================
An application, ES938.EXE, is provided to control the ES938 3D
Stereo Processor.

MIDI/Wavetable support
======================
In the OS/2 CONFIG.SYS file (after driver installation) the following
lines will be present:

DEVICE=C:\MMOS2\SP32.SYS /W:1 /N:SP321$
DEVICE=C:\MMOS2\VAUDDRV.SYS SP321$

The /W:x parameter has the following definition.

/W:1 parameter means use the external MIDI port for MIDI play.  This would
typically be used for the SoundPiper 32 with a Wavetable Daughter Card.
This is the default setting for a SoundPiper 32

/W:0 parameter means use the internal FM Synthesizer for MIDI play.  This
is the default setting for the SoundPiper 16.

Device sharing between OS/2 and WIN-OS/2
========================================
The audio device can be shared between Windows applications and
OS/2 under an exclusive sharing arrangement.  If the device is
not currently being used by an OS/2 application, when Windows
runs an audio application, Windows will own the audio device
until the Windows application (or session) is terminated.  Then
ownership will pass to the next application requesting it (OS/2
or Windows).  This all occurs while maintaining the state of the
device for all applications.


Limited MPU-401 support
=======================
If MPU-401 is enabled, the OS/2 driver will send out MIDI data
when MIDI files are played.  If MPU-401 interrupt is enabled,
MIDI data can be received into the Port.  A MIDI file has to be
opened for the input of MIDI data to be sent to the FM synthesizer. 
MIDI record is not supported.  In WIN-OS/2 only MIDI out is supported,
but the driver requires a MPU-401 interrupt to start.  In OS/2 if a
MIDI file is played while the MIDI port is receiving, the MIDI file
has priority.  After a stop command is sent to the MIDI file,
MIDI input will continue generating FM music.  Note that the stop
command is only sent when the MIDI file play is completed or
rewound or there is a switch between two MIDI files.

Input monitoring
================
Input source monitoring during non-recording time is
implemented.  However, there are some limitations to this
feature due to the design of MMPM/2.  When Digital Audio is launched,
the default microphone input source is used.  If you want to
switch to line in, you must start recording to send the
information down to the driver.  If the input source
is switched back to the default microphone because a wave file
is opened, you have to turn monitor off and then on to switch
to the line in source.

Known Problems
==============
For OS/2 Warp 3.0, opening too many MIDI files makes the
OS/2 system unstable. This problem is related to MMPM/2 and
depends on available system resources.  On systems with 8 MB
of memory the limit is 3 open files for 16 MB systems the
limit is 6.

Tempo in MIDI files may not be 100% accurate due to timing
delay and MMPM/2 architecture.

For OS/2 Warp 3.0, running MCI commands "seek wave to #" and
then "play wave" to a 16-bit wave file will sometimes generate
a very loud static noise.  Likewise using "record wave from #"
to record a 16-bit wave file may generate the wrong file contents.
This behaviour is related to the seek position.

The OS/2 driver allows sharing of audio and MPU-401
interrupts, but it is not recommended.  If both are shared,
occasionally too much MIDI in data will lock up SoundPiper's
interrupt processing when a wave file is played or recorded.
To get out of this situation, stop the wave file, stop the
MIDI in source, close all MIDI files, and restart the wave
file to re-initialize AudioDrive's interrupt processing.

Due to the nature of MIDI music, enabling MIDI input while
MIDI input data is present at the port may not generate the
correct sounds. It is recommended that the external MIDI device
producing the MIDI input stream be stopped prior to enabling the
MIDI port for input.

Icons in the Multimedia Folder        
==============================
Since OS/2 Warp 3.0 MINSTALL.EXE changes the icons of the MIDI
player and the Digital Video player to that of the Digital Audio
player in the Multimedia folder, you may want to change them
back to the originals.  To change the icon of the MIDI player,
right click MIDI player to bring up the menu.  Select
Settings, select General, and click the Find... button.  In
the Start Folder window, enter \MMOS2\INSTALL.  Click the
Find button and a window of all found icons appears.  Select
MIDIPLAY.ICO and click OK.  Close the MIDI player Settings
notebook.  For the Digital Video player, repeat the above steps
but select the VIDPLAY.ICO instead.

Files Copied to the Disk
========================

These are the files copied to your hard disk:

\MMOS2
   SP32.SYS
   VAUDDRV.SYS
\MMOS2\DLL
   CARDINFO.DLL
   ESSVSD88.DLL
\OS2\BOOT
   CLOCK01.SYS
   CLOCK02.SYS
   TIMER0.SYS
\WINDOWS or \OS2\MDOS\WINOS2
   AUDDRIVE.HLP
   AUDMPU.HLP
\WINDOWS\SYSTEM or \OS2\MDOS\WINOS2\SYSTEM
   AUDMPU.DRV
   ES1688WN.386
   ES1688WN.DRV
   MIDIMAP.CFG
   MSMIXMGR.DLL

=====================================================================
====                          Section 4                          ====
=====================================================================

Win-OS/2 Driver and Software Installation
=========================================
Use this diskette. Start a Full Screen Win-OS/2 sessions and
follow these steps.

1. From Program Manager File Menu, select RUN.
2. From the RUN menu, select BROWSE to choose the drive where this diskette
   is located. (usually A:)
3. Select the \OS2 subdirectory.
4. Select SETUP from the file menu and OK.  Follow the on screen directions
   to complete the SoundPiper Driver installation.
5. After Windows Restarts, from the RUN menu, select BROWSE to choose the
   drive where this diskette is located. (usually A:)
6. Select the \ARACK subdirectory.
7. Select SETUP from the file menu and OK.  Follow the on screen directions
   to complete the SoundPiper Software (AudioRack) installation.
8. After installtion, the application icons appear in the AudioRack program
   group. Double-click an icon to launch an application. Each application
   has on-line Help that can be accessed from that application's Menu Bar.

=====================================================================
====                          Section 5                          ====
=====================================================================

WIN-OS/2 Notes
==============

Session Settings
================
The following changes to your WIN-OS/2 session settings may be required
for proper WIN-OS/2 operation:

Change the WIN-OS/2 session settings to the following if necessary:
        AUDIO_ADAPTER_SHARING = Required
        INT_DURING_IO = On

Device(s) Not Found
===================
If problems occur with your WIN-OS/2 install resulting in error messages
such as NO MIXER DEVICE FOUND or NO RECORDING CONTROL FOUND, please
edit your WIN-OS/2 SYSTEM.INI file (e.g. C:\OS2\MDOS\WINOS2\SYSTEM.INI)
and make sure that the following line in the [boot] section is correct.

Old Line usually reads:
device=MMSYSTEM.DLL

New line:
device=MMSYSTEM.DLL MSMIXMGR.DLL

If other parameters are on the original line leave them and just add
the msmixmgr.dll entry.

MIDI Playback Issues
====================
If the MIDI playback is not smooth in WIN-OS/2, you need to
change the timer resolution.  Edit SYSTEM.INI in your Windows
directory.  Under [timer.drv] are TIMERMax386Res and
TIMERMax286Res.  You need to change the values to less than 8
from the default of 10. (typically 5 or 6)

=====================================================================
====                          Section 6                          ====
=====================================================================

Contacting Piper Research, Inc.
===============================
Piper Research technical support may be contacted by the following methods.

Telephone:  (612) 459 - 2770
Facsimile:  (612) 458 - 1978
E-Mail:     support@piper-research.com
Mail:       Piper Research, Inc.
            Attn: Tech Support
            303 21st Street - Suite 241
            P.O. Box 241
            Newport, MN  55055