home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 4 Drivers
/
04-Drivers.zip
/
3DSOS2.ZIP
/
README.TXT
< prev
next >
Wrap
Text File
|
1996-11-21
|
14KB
|
332 lines
C o n t e n t s
A. Overview
B. Release Notes
C. System Requirements
D. Included Files
E. Driver Installation
F. Trouble Shooting
G. Problems In This Release
----------------------------------------------------------------------------
A. O v e r v i e w
This README.TXT contains instructions to install and configure the OS/2 Wrap
3.0 driver for the 3D WebSound.
----------------------------------------------------------------------------
B. R e l e a s e N o t e s
This release of the OS/2 Wrap 3.0 driver supports the following features on
the 3D WebSound.
1. MPC Level 3 Mixer
2. Digital Mixer
3. WSS Codec
4. SBPro Codec
5. Game Port
6. MIDI Port
7. I2S1
8. 3D Sound Control
The following features are NOT supported by this release:
1. Extra Logical Device
2. DSP Serial Port
3. Power Management
4. I2S0
This driver is designed to run under OS/2 wrap 3.0 only. If you install a
version below the requirement. We encourage you to upgrade your OS/2 system.
If you install the OS/2 merlin, the driver shall be ready for a few weeks.
----------------------------------------------------------------------------
C. S y s t e m R e q u i r e m e n t s
- 80486 PC-AT compatible or faster machine.
- 8 MB DRAM or greater.
- 1 free 16-bit ISA-bus expansion slot.
- 400 KB free hard disk space for minimum software installation.
- IBM OS/2 Wrap 3.0
----------------------------------------------------------------------------
D. I n c l u d e d F i l e s
AD1816DD.SYS - AD1816 Soundport controller driver
AD1816DD.SYM - AD1816 Driver symbols file
CARDINFO.DLL - AD1816 Soundport controller card
information file
AD1816.HLP - AD1816 Soundport controller help file
AD1816.SCR - AD1816 Soundport controller driver file
list
CONTROL.SCR - Install script for MINSTALL
README.TXT - This file
UPDTCLK.BAT - Batch file for updating timer basedevs
RSTRCLK.BAT - Batch file for restoring timer basedevs
MPU401.SYS - MPU-401 driver
MPURES.DLL - MPU-401 resource DLL
AUDPLAY.ICO - Audio ICON
MIDIPLAY.ICO - MIDI ICON
JOYSTK.ICO - Joystick ICON
OPLRES.DLL - OPL3 resource file
OPL3.DLL - OPL3 driver
OPL3.HLP - OPL3 Help File
CLOCK01.SYS - Timer driver
CLOCK02.SYS - Timer driver
TIMER0.SYS - Timer driver
GAMEDD.SYS - Joystick driver
GAMEVDD.SYS - Joystick driver
JOYSTK.CH - Joystick install script
----------------------------------------------------------------------------
E. D r i v e r I n s t a l l a t i o n
Before You Begin.
Proper operation of the 3D WebSound board requires that:
--You are using OS/2 Warp version 3.
--The OS/2 Multimedia Extensions are installed.
--The 3D WebSound driver is installed.
NOTE: You must have the OS/2 Multimedia Extensions installed BEFORE you
install this driver. You will use the OS/2 Multimedia Extensions to
install and configure the 3D WebSound driver.
If your installation fails, you may need to update some of your OS/2
system files. See the "Trouble Shooting" section for more information.
Check for the OS/2 Multimedia Extensions.
If the extensions are already installed, you will see the "Multimedia"
icon on your OS/2 desktop. If the extensions are already installed,
skip ahead to the procedure "Installing the 3D WebSound Driver".
If the "Multimedia" icon is not visible, OS/2 Multimedia Extensions
may not yet be installed. Install the extensions using the following
procedure.
Install the Multimedia Extensions.
1. Open the "OS/2 System" folder on the OS/2 desktop. Double-click the
"System Setup" icon.
2. From the "System Setup" window, double-click the "Selective Install"
icon to display the "System Configuration" window. The box labeled
"Multimedia Device Support" in the lower left corner of the "System
Configuration" window should read "None". We will install the sound
board driver later.
3. Click the "OK" button. The "OS/2 Setup and Installation" window
appears.
4. Click the box next to "Multimedia Software Support". You should now
see a check mark in that box.
5. Click the "Install" button. OS/2 will begin installing the extensions.
Follow all on-screen instructions, including the last one that instructs
you to restart your system. Once your system has restarted, use the
following procedure to install the driver for the 3D WebSound board.
Installing the 3D WebSound Driver.
1. Double-click the "Multimedia" folder icon on the OS/2 desktop. run the
"Multimedia Application Install" program.
2. Insert the 3D WebSound Driver Diskette into your diskette drive.
3. Use the drop-down "Drive" list box to select the drive letter, A: or B:,
that contains the diskette. Then choose "OS2" in the "Path" list box.
4. Click the "Analog Devices AD1816" line to place a check mark next to
the selection. By default, the 3D WebSound driver installation does
not install the MPU-401 support for MIDI devices (since this is not a
very common installation option). You you want MPU-401 support, click
the "IBM MPU-401" line to place a check mark next to it.
5. Click the "Install" button. If you receive a warning that the program
will change your CONFIG.SYS file, click the "Yes" button to allow the
program to make the required changes.
6. The "Analog Devices AD1816" window appears. This window displays the
configuration information for the 3D WebSound board. Adjust the
configuration information if they are conflicted.
7. Click the "OK" button. You will receive several additional notifications:
installation windows for several driver components, that your CONFIG.SYS
file was backed up, and that the installation is complete. Click "OK" on
each of these alerts.
8. Exit OS/2 and reboot your system. When you reboot your system, you should
hear the OS/2 start-up sounds, indicating that the 3D WebSound board is
properly installed and working.
Configuring the 3D Sound Features:
The 3D WebSound board can produce sound in simulated 3D. This feature is
controlled using the card's configuration window. To access these settings:
1. Open the "OS/2 System" folder on the OS/2 desktop. Double-click the
"System Setup" icon.
2. From its window, run "Selective Install" to display the "System
Configuration" window.
3. In the "System Configuration" window, the "Multimedia Device Support"
drop-down list should show the "Analog Device AD1816 Soundport" as the
active device. Click the square button next to the device name.
4. Click the "Device Settings" button to display the card's hardware
settings. The "Analog Devices AD1816" window appears. This window
contains controls to turn 3D effects on or off, and change the
acoustic properties of the 3D simulation algorithm.
5. After you have changed the settings, click the "OK" button. The changed
settings take effect immediately, and are written to your CONFIG.SYS
file to be used when you start OS/2.
----------------------------------------------------------------------------
F. T r o u b l e S h o o t i n g
A majority of problems observed with the 3D WebSound drivers for OS/2 wrap
version 3 are caused by inconsistent versions of the following system
files: CLOCK01.SYS, CLOCK02.SYS, TIMER0.SYS, and OPL3.SYS. Before continuing,
make sure that your versions of these system files match the 3D WebSound
driver install diskette files:
\OS2\BOOT\CLOCK01.SYS
\OS2\BOOT\CLOCK02.SYS
\MMOS2\TIMER0.SYS
\MMOS2\OPL3.SYS
This is done by visually comparing the file time, date, and size for each
one of the files listed above against the same filename on the driver
install diskette.
If your files do not match the versions on the diskette, then either copy
the diskette files over the files on your system, or use the UPDTCLK.CMD
or UPDTCLK.BAT command files to update your system files.
Note that this command file saves a copy of CLOCK01.SYS and CLOCK02.SYS to
CLOCK01.WRP and CLOCK02.WRP respectively. Do not overwrite or delete these
files as these files can be used to restore your original configuration,
if required. Use the RSTRCLK.BAT command file to restore your original
CLOCK01.SYS and CLOCK02.SYS drivers in the \OS2\BOOT directory.
----------------------------------------------------------------------------
G. P r o b l e m s I n T h i s R e l e a s e
Problems Observed and Possible Solutions:
1. Exception in device driver: CLOCK$
TRAP 00d
This problem is due to mismatched or inconsistent revision levels of
CLOCK01.SYS, CLOCK02.SYS, and and TIMER0.SYS drivers installed on
your system. Make sure that the CLOCK01.SYS, CLOCK02.SYS and TIMER0.SYS
drivers from the AD1816DD.SYS driver install diskette are copied into
the proper subdirectories of the system. Make sure that the CLOCK01.SYS
and CLOCK02.SYS has its read-only attributes reset. Use ATTRIB CLOCK0?.SYS
to view the attributes, and ATTRIB -r to reset the read-only attributes,
if required. To install the files:
Copy CLOCK01.SYS to \OS2\BOOT
Copy CLOCK02.SYS to \OS2\BOOT
Copy TIMER0.SYS to \MMOS2
Or, use the UPDTCLK.BAT command file to update these drivers.
2. MINSTALL Display "MMPM/2 Copy Failed File in Use" while doing install
This problem is due to some CLOCK01.SYS and CLOCK02.SYS files having the
read-only attribute set. Use OS/2's ATTRIB.EXE utility to reset the
read-only attribute for these files. Note that on some versions of Warp,
an option is presented to retry the operation, and when a retry is
attempted, the copy appears to have succeeded, and in fact fails.
This problem may manifest itself as a trap when trying to play a MIDI file
(see TRAP in CLOCK$ driver when opening MIDI player). If you see this
problem, be sure to check the files CLOCK01.SYS and CLOCK02.SYS in the
\OS2\BOOT subdirectories to make sure that these were properly copied
from the install diskette.
3. When performing a shutdown while the MIDI player is still open, the
system hangs.
This problem is due to mismatched CLOCK01.SYS, CLOCK02.SYS, and TIMER0.SYS
drivers. Use the procedure described above to correct this problem.
4. When playing a MIDI file, switch to Audio Player, then back to MIDI player.
No audio is heard, and an error occurs when start, pause, or stop.
This problem is due to an inconsistent version of OPL3 with the version
OS/2 wrap 3 and the TIMER0.SYS set of drivers. Use the procedure
described above to correct this problem.
List of Known Problems:
This driver is a Beta-level release. There are four known problems that we
are working to correct. Where required, we are working with IBM to resolve
these problems as quickly and efficiently as possible. Three of the problems
relate to a conflict between multimedia applications and the use of system
sounds. These problems can be solved by turning off system sounds.
Problem 1
The Digital Audio applet gives an error message after you:
1. Click Record.
2. Click Stop.
3. Click New.
4. Click Discard.
The error message may say that either the device is busy or that there
was a device error. This is a problem wih the way Digital Audio interacts
with the device driver while Warp trys to play system sounds. To avoid
this problem, turn off system sounds. Alternatively, close Digital Audio
and restart it to continue, or save the recorded audio to a file.
Problem 2
The MIDI Player Applet displays an error after you take the following
steps:
1. Start playing a MIDI file using the MIDI Player applet.
2. Bring up another multimedia application, such as Master Volume or
Digital Audio.
3. Click on the MIDI Player applet.
4. Close the other application.
5. Click the MIDI Player applet Start button.
This is a problem wih the way MIDI Player interacts with the device
driver while Warp trys to play system sounds. To avoid this problem, turn
off system sounds.
Problem 3
When playing a MIDI file, switching to master volume control, then back
to MIDI play causes the MIDI audio to appear to be muted.
This is a problem with the way Warp plays systems sounds. Turn off the
system sounds to avoid this problem.
Problem 4
The 3D WebSound boards are plug-and-play cards. Since OS/2 Wrap 3 does
not support plug-and-play, the Warp 3 driver for these cards needs to
set the resources according to what resources the user knows is not
being used. In a few cases, the system BIOS does not support plug-and-play
BIOS enumeration in cooperation with a non plug-and-play enabled operating
system, such as Warp 3. This is complicated by the fact that since the
3D WebSound devices are not critical to system operation (such as a hard
disk controller, or graphics controller) the card is not enabled by the
BIOS. In some cases, the system plug-and-play BIOS does not properly
setup system resources to coexist with the 3D WebSound device. If the
system appears to behave strangely, that is, audio files play continuously,
or the system appears to freeze, or a sound file snippet plays
continuously, or other devices behave unexpectedly, some ROM setup
modifications may be necessary. Most plug-and-play enabled systems have a
ROM-based setup menu which allows different plug-and-play options. It may
be necessary to try different plug-and-play settings within these ROM-
based BIOS settings to allow proper operation of 3D WebSound board in
certain systems.