Unfortunately, Media Vision will not be supporting OS/2 WARP for any of the product line at this time. In the future, you may wish to contact IBM for multimedia support.
Media Vision apologizes for any inconvenience this change in stance may cause you.
Unfortunately, Media Vision does not support Windows NT for any of its product line at this time. Media Vision has not positioned or advertised its products as being a solution for the Windows NT market. Microsoft may be able to provide you with further information regarding NT support.
Download the files from the Media Vision BBS or from CompuServe. The file you need is OS2.EXE. The BBS number is 510-770-0527. Type GO MEDIAVISION to access our forum on CompuServe.
You need the OS/2 SCSI driver before you can load OS/2 from CD-ROM. Download OS2.EXE from the BBS. You may also obtain this file from CompuServe. Type GO MEDIAVISION to access the forum. Once you have the file, you will use TMV1SCSI.ADD to allow the CD-ROM drive to be seen by the OS/2 installation diskettes.
After the file, TMV1SCSI.ADD, has been extracted, copy it to the root-directory of the OS/2 install disk labeled Diskette #1. Edit the CONFIG.SYS of Diskette #1, and add one line to the very end of the file:
Save the file, and reboot the system using the Installation Disk. After a minute or two, the computer will prompt you to insert Diskette #1. Soon after this, it will read the CD-ROM driver, and access the CD-ROM.
As the installation proceeds, you will be asked if support is needed for various devices (mouse, video display, CD-ROM...). Check the CD-ROM Support option, and continue. Next, you will be asked for the model of CD-ROM. After making your selection, finish the installation. When the system is re-booted, you should have access to the CD-ROM.
Support for SCSI CD-ROMs is provided by the file TMV1SCSI.ADD. This base-level device driver can be downloaded from the Media Vision BBS (in the file OS2.EXE). After the file has been extracted, copy it to the root-directory of the OS/2 install disk named Diskette #1. Edit the CONFIG.SYS of Diskette #1, and add one line to the very end:
Save the file, and reboot the system using the Installation Disk. After a minute or two, the computer will prompt you to insert Diskette #1. Soon after this, it will read the CD-ROM driver, and access the CD-ROM.
As the installation proceeds, you will be asked if support is needed for various devices (mouse, video display, CD-ROM...). Check the CD-ROM Support option, and continue. Next, you will be asked for the model of CD-ROM. After making your selection, finish the installation. When the system is re-booted, you should have access to the CD-ROM.
1) Ensure that the mixer is turned down. It may be as simple as turning down the volume.
2) Make sure you have INT_DURING_IO set to ON and HW_TIMER set to ON under your session settings area.
3) Try shifting your use of DMA's and IRQ's. Try using DMA 3.
4) Make sure that you are using the SAME DMA and IRQ under both OS/2 and WINOS2.
5) Try adding /T1 to your MVPRODD.SYS line. /T1 will enable the on-board oscillator.
Here is a sample line:
There are several things to do. If you can't get the PAS 16 to operate in its native mode for WINOS2, you can use the SBWAVE.DRV driver, (to use the Sound Blaster compatible part of the card for WINOS2). This will only provide 8-bit sound, but it usually works without any problem. As you may know, Windows is a single-tasking OS, an expects to have full control of the hardware. Since OS/2 is providing all the needed support for the WINOS2 shell, WINOS2 can't have full control, which creates many problems.
Sound distortions occur in WINOS2 because of the differences between Windows, and WINOS2. There are some things to try to minimize the static and breakup:
Here are the steps for WINOS2 support for the PAS 16 (assuming you have the sound card setup on the OS/2 Desktop):
1) From the OS/2 Desktop, with no other applications running, RIGHT-click once on the DOS Full-screen icon. This will bring up a menu. Select OPEN-SETTINGS. You will have a notebook open now.
2) Click on the SESSION tab, on the right side. This will change the display to the Session page.
3) Click on the SETTINGS button. This will allow you to modify the settings for the DOS Full Screen session.
4) Scroll down to DOS_VERSION on the left, and click on it. This will change the right-half of the screen, and allow you to add a new entry. 5) Scroll down to the end of the right side. Click at the end of the last entry, and hit [enter].
6) We need to tell OS/2 that the installation program is a DOS application, and it is compatible with DOS 5.00. Add one new line:
7) Click on SAVE, and then CLOSE.
8) Double-click on DOS Full-Screen, and run the installation program. When it comes to the Windows directory information, make sure you use the correct directory (NOT C:\Windows). Proceed all of the way to the end, where you can change the configuration.
9) Make sure to use the same IRQ and DMA combination as the OS/2 CONFIG.SYS. This is VERY important.
10) On the option for "MODIFY DOS SYSTEM FILES," select NO. Otherwise it would add to the OS/2 config files, and may cause problems.
11) Accept the configuration. At the DOS prompt, type EXIT.
12) Now you are back at the OS/2 Desktop. Double-click on Windows Full-Screen, and you should hear TADA getting into Windows. Try playing a MIDI file in Media Player. This should also work.
If you get no sound, check the SYSTEM.INI file for modifications. If none were made, you will need to do a manual configuration. If so, we can fax you the entries to make. If the modifications were made, but you heard no sound, make sure no other applications are running on the OS/2 Desktop. Also check the volume levels in the Pocket Mixer.
NOTE:
A simpler method of adding WINOS2 sound support for the PAS 16 is to use the WIN145.EXE installation files available on the BBS or CompuServe. This set of installation files will prepare your Windows, (Windows 3.1, 3.11, or WINOS2) shell to operate your PAS 16. The installation is run from Windows.
You need to add the SET BLASTER statement to the AUTOEXEC.BAT file that is associated with the DOS session you are trying to use Sound Blaster compatibility. It is also possible that you need to load MVSOUND.SYS in the DOS_DEVICE setting of the DOS Session settings for the DOS session you are using. Here is a sample line for the DOS_DEVICE setting.
Pro Audio Spectrum 16
Main Menu
All files are copyrighted ©1995 Media Vision.