home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
readme.mwv
< prev
next >
Wrap
Text File
|
1994-09-01
|
34KB
|
850 lines
IBM Mwave OS/2 Beta License Agreement
Please read the following carefully. If you do not agree to the terms,
then you must destroy or erase all copies you have of the code. Installing
this code on your machine implies agreement with the terms.
LICENSE AGREEMENT FOR BETA MWAVE OS/2 SOFTWARE
(c) Copyright IBM Corporation 1993, 1994. All rights reserved.
IF YOU DOWNLOAD OR USE THIS SOFTWARE, YOU AGREE TO THESE TERMS.
International Business Machines Corporation grants you a license to
use the Program, only in the country where you acquired it. The
Program is copyrighted and licensed (not sold). We do not transfer
title to the program to you. You obtain no rights other than those
granted you under this license.
Under this license, you may:
1. make copies of the program for backup purposes only.
You may NOT:
1. use, merge, copy, display, adapt, modify, execute,
distribute, or transfer the Program, except as provided
in this license.
2. sublicense, rent, lease, or assign the Program.
3. reverse assemble, reverse compile, or otherwise
translate the Program.
This is Beta code and may not be at the quality level of production
IBM code. The code is provided "AS IS" without warranty of any kind.
1. You may terminate this license at any time.
2. We may terminate this license if you fail to comply with any of its terms.
3. This License expires 2 months after the code is generally available.
In all three cases you must destroy all your copies of the Program.
You are responsible for payment of any taxes resulting from this
license.
You may not sell, transfer, assign, or subcontract any of your rights
or obligations under this license. Any attempt to do so is void.
Neither of us may bring a legal action more than two years after the
cause of action arose.
If you acquired the Program in the United States, this license is
governed by the laws of the State of New York. If you acquired the
Program in Canada, this license is governed by the laws of the
Province of Ontario. Otherwise, this license is governed by the laws
of the country in which you acquired the Program.
Mwave OS/2 Installation Guide Windsurfer OS/2 External Beta Version 1.04
This beta version of OS/2 Mwave Software supports the Windsurfer ISA
Communications Adapter and the Windsurfer MCA Communications Adapter.
Description of Files
The following files available on this BBS make up this beta version:
OS_2Dx.ZIP: Required. Download and unzip these two files to create
2 installation diskettes for Windsurfer OS/2.1 Mwave support
(ISA and MCA).
MMPM_EXT.ZIP Required if you wish to use OS/2 MMPM audio. Download and
unzip this file to create an installation diskette for Mwave
mmpm audio. Use the -d option when unzipping this one.
WINOSFIX.ZIP Required for WIN-OS/2 operation. A separate set of fixes
is required for a full OS/2 system and an OS/2 for
Windows system. Both sets are included in this file.
Two files, timer.drv and mciseq.drv are required for
full OS/2. Five files, wincom.com, winos2.com,
fixmgr.dll, timers.scr, and mciseqs.scr are reqired
for OS/2 for Windows.
In addition, one fix is provided for Version 4.0 of the
Windows Windsurfer support. This fix is also required
only for WIN-OS/2 support
These files can be unzipped to
any convenient place on your fixed disk.
README MWV This file
Users wanting to operate in a WIN-OS/2 session will also need the
appropriate Windows Windsurfer software. Product versions of this
software for both ISA and MCA adapters are available from the IBM
Complementary Products BBS at (704) 594-3799.
Summary of Changes
Here is a summary of the changes between this beta and the previous (1.03)
beta:
1. Files previously provided on EXTRA.ZIP have been incorporated
into the OS_2Dx.ZIP files.
2. Delays associated with System Sounds has been fixed.
3. WIN-OS/2 and Dual boot support for OS/2 for Windows is included.
This support requires manual installation of 5 updated Windows
files. These files are included in WINOSFIX.ZIP.
Users of OS/2 for Windows who wish WIN-OS/2 support must install the Mwave
Windows diskettes in the WIN-OS/2 session BEFORE installing the Mwave OS/2
diskettes. Also, DO NOT reboot your system between the times you install
the Mwave Windows diskettes and the Mwave OS/2 diskettes.
4. System Sounds concurrency with Modem is provided.
5. An AUX control app has been added to the Mwave folder. To play CDs,
the AUX control must be open. (The earlier work-around of opening
Digital Audio will still work, but this uses more MIPs. For best
results, use the AUX Control).
6. At the end of the installation of the two OS Mwave diskettes, no
installation complete message is produced. When your OS/2 command prompt
reappears, the OS Mwave diskette installation is complete.
7. There is no requirement to remove the previous beta
prior to installing the new one. (Any real old betas..prior to
5/27/94, should be removed).
Restrictions
If the modem is active and you click on Digital Audio, you will receive an
Internal Error #5088. If you click on OK, you get the message again. If
you click OK again, it looks like things are OK, but they are not. You
will have no sounds until you reboot.
You can recover from the 5088 error if you do the following:
Don't click on OK when the 5088 error occurs. Rather, close the message
box from the top left corner pull-down menu. A GPF will occur, but no long
term damage, and all your sounds will continue to work.
Installation Summary
Here is a summary of the steps required to install this software. More
information is provided later in the document.
1. Read this README
2. Download and unzip OS_2Dx.ZIP to diskettes labelled OS DISK1 and
OS DISK2.
3. If you want OS/2 Mwave mmpm audio, download and unzip MMPM_EXT.ZIP to
diskette labeled MMPM_EXT.
4. If you want WIN-OS/2 support, download and unzip WINOSFIX.ZIP
(to any convenient place on your fixed disk). Note that for
WIN/OS/2 support, you will also need version 4 of the Windsurfer
Windows software. This is available from the IBM Complementary
Products BBS at (704) 594-3799.
5. Follow the installation procedures described below. Individual
procedures are described for native OS/2, WIN-OS/2, and native
Windows (for dual boot users).
6. If you run into problems, review the information in the section
"Usage Hints" 7. For WIN-OS/2 systems, use the hints described
in the section "WIN-OS/2 Settings".
Requirements
1. OS/2 2.1 or higher or OS/2 for Windows 2.11 or higher must be installed
on your system.
2. Multimedia Presentation Manager (MMPM/2) must be installed on your system.
3. Windsurfer (ISA or MCA) is installed on your system.
4. Any MwaveOS/2 beta prior to 5/27/94 must be removed.. See Removal
Process at the end of this README.
Configurations Supported
Here is a general description of the configurations supported by this
version of the OS/2 Mwave software:
Native OS/2 Mwave
Native OS/2 Mwave enables Mwave applications on either OS/2.1 or OS/2.11
for Windows. Native OS/2 Mwave support in this version includes the
following items:
-Base Mwave
-Mwave Manager
-MwaveOS
-MEIO
-Modem
-Discriminator
-TAM and FAX drivers
-Sample TAM and FAX applets
-No applications.
WIN-OS/2 Mwave
WIN-OS/2 Mwave refers to the capability to run Mwave Windows
applications in a WIN-OS/2 full screen Windows session under OS/2 or
seamlessly from the OS/2 desktop as a WIN-OS/2 Window. In each
case, the base operating environment is either full OS/2 containing its
own Windows or OS/2 for Windows. Note that if you plan to use WIN-OS/2
Mwave with an OS/2 for Windows system, you must install the Mwave
Windows diskettes before installing the Mwave OS/2 diskettes.
All Mwave applications which run under Windows run under WIN-OS/2
Mwave.
OS/2 systems supporting WIN-OS/2 can be dual boot systems. With
these systems, users can decide to boot DOS and run native Windows
Mwave applications.
Native Windows Mwave
Native Windows Mwave refers to Mwave which runs under native Windows.
Some OS/2 users may wish to run Native Windows Mwave as part of a dual
boot system.
Installing OS/2 Mwave
Installation of the various groups of Mwave capabilities (as defined
above) is provided using three different installation diskettes sets:
OS/2 Mwave diskettes, Windows Mwave diskettes, and MMPM audio disdettes.
These diskette sets are used either singly or in combination to provide
the different functionalities described above.
Installing Native OS/2 Mwave Support
If you install Native OS/2 Mwave support, you will be able to run
OS/2 Mwave applications. (Note that the current version includes
only sample applets for FAX and TAM). You will not be able to run
Windows applications either in a full screen WIN-OS/2 session or
seamlessly from the desktop.
To run Windows applications in OS/2 (WIN-OS/2), you will need to
additionally install the Windows Mwave diskettes in a WIN-OS/2 session.
To use MWave WIN-OS/2 with an OS/2 for Windows sytem, make sure to
install the Mwave Windows diskettes before installing the Mwave OS/2
diskettes.
Native OS/2 Mwave support is installed using the OS/2 set of Mwave
installation diskettes. Place OS DISK 1 into drive a and type
a:setup from an OS/2 command prompt. Then follow the installation
instructions that appear on the display.
At the end of the installation of the two OS Mwave diskettes, no
installation complete message is produced. When your OS/2 command
prompt reappears, the OS Mwave diskette installation is complete.
If you do not plan to run Windows Mwave applications under your OS/2
system, and if you do not plan to run Mwave under native Windows
(via dual boot or boot manager), and you do not plan to run Mwave
MMPM audio, this completes your Mwave installation activity.
Installing Mwave MMPM Audio
If you wish to run OS/2 Mwave mmpm audio, install the software
contained on the disk you labeled as MMPM_EXT. To install, insert
the diskette into drive a, type a:setup, and follow the instructions
that appear on the display. Also, always install the native OS/2 Mwave
diskettes before installing the MMPM Audio diskettes.
Installing WIN-OS/2 Mwave
If you wish to run OS/2 Mwave applications and you wish to run
Windows applications in a WIN-OS/2 full-screen session or seamlessly
from the OS/2 desktop, you do two separate installations.
First install the Windows Mwave diskettes as described below and then
install the OS/2 Mwave diskettes as described in "Installing Native
OS/2 Mwave Support", above. Note that for WIN-OS/2 Mwave, the Windows
Mwave diskettes must be installed in a WIN-OS/2 session under OS/2.
To install the Windows Mwave diskettes under WIN-OS/2, bring up the
full-screen WIN-OS/2 session,place diskette number 1 of the Windows
installation set in drive a and type a:setup from the Windows
File║Run menu. Then follow the instructions that appear on the
display.
If you have a dual boot environment, and you also wish to run Native
Mwave support, you will need to additionally do the installation
described in "Installing Native Windows Mwave" below.
WIN-OS/2 Fixes
Mwave operation under WIN-OS/2 requires that you manually install
two sets of updated system modules provided in
WINOSFIX.ZIP.
If you have a full OS/2 system, copy mciseq.drv and timer.drv into
the \os2\mdos\winos2\system directory.
If you have an OS/2 for Windows system, copy win.com and
winos2.com into your \windows directory and copy fixmgr.dll,
timers.scr and mciseqs.scr into your \windows\system directory.
Note that you must copy these fixes into your system manually. They
are not automatically copied as part of the installation procedure.
In addition to the above, run ADDFIX from an OS/2 DOS box to install
the second fix. Do this regardless of the type of your OS/2 system
(full OS/2 or OS/2 for Windows).
Installing Native Windows Mwave (for dual boot..or boot mgr systems)
If you install just the Native Windows Mwave support, you will be
able to run Windows Mwave applications in Native Windows. You will
not be able to run Windows Mwave Applications under OS/2. (To run
Windows applications in OS/2, install the Windows Mwave diskettes in
a WIN-OS/2 session under OS/2. See above).
Native Windows Mwave support is installed using the most recent
Windows Windsurfer installation diskettes.
To install, place disk 1 of the Windows Windsurfer diskettes into
drive a and type a:setup from the Windows File║Run menu. Then
follow the installation instructions that appear on the display.
Native Windows Mwave also requires the ADDIFX installation mentioned
above. For native Windows Mwave, run ADDFIX in a Windows DOS box.
Full-blown Install
A full-blown install would include these separate installation steps.
-Install the Windows Mwave diskettes under WIN-OS/2 (if you want
WIN-OS/2 Mwave support). Do not reboot between this step and the
next.
-Install the Native OS/2 Mwave diskettes under OS/2 (for the native
OS/2 Mwave support).
-Install the MMPM_EXT diskette (for audio support). The native OS/2
diskettes must be installed before the MMPM_EXT diskette.
-Install the Windows diskettes under native Windows if it isn't already
on your system (if you want dual boot Mwave Native Windows support).
-Install the appropriate fixes from WINOSFIX (if you use WIN-OS/2 or
native Windows Mwave).
Usage Hints
Here is a list of Mwave OS/2 usage hints compiled over the last few
weeks. Thanks to all our beta users whose input has contributed to
this list.
Installation Stuff:
1. Assure OS/2 2.1 or higher or OS/2 for Windows 2.11 is installed on
your system.
2. Multimedia Presentation Manager (MMPM/2) must be installed
on your system prior to installing any of the beta. When presented
with the option screen during MMPM/2 installation, select Software
Motion Video (if you have no CD-ROM). If you have a CD-ROM, select
CD Audio (either in addition to or instead of Software Motion
Video). Do not select SoundBlaster.
3. If after installing MMPM_EXT your Multimedia folder contains more than
one MIDI or one Digital Audio icon, something is messed up.
Likely, you requested SoundBlaster during the MMPM/2 install. If
this is the case, you can change sound cards using hint 9 below.
4. The order of installation of parts of the beta is important. For OS/2
for Windows, this order is different than earlier betas.
- First, if you want WIN-OS/2 support, install the Mwave Windows
diskettes in a WIN-OS/2 session (must be first if you run OS/2 for
Windows; can be first with full OS/2).
- Next, without rebooting, install the two OS/2 Mwave disks.
- Next, install the MMPM_EXT disk.
- Install the fixes from WINOSFIX if you run WIN-OS/2 Mwave.
5. If after reinstalling over previous betas, your system hangs during
booting, it's likely that the ordering of lines in config.sys has
gotten messed up.
Make sure that the lines
DEVICE=\MMOS2\AUDIODD\AUDG2.SYS P N:AUDIOV1$
DEVICE=\MMOS2\VAUDIO.SYS
follow the
DEVICE=\MWAVEOS2\BIN\MWAVEDD.SYS
They needn't follow immediately, they just need to follow. If the
two lines precede the MWAVEDD.SYS line rather than follow it, the
system fails during boot-up..
During a beta reinstall (or if the MMPM_EXT is mistakenly installed
before the OS/2 diskettes), this out-of order situation can occur.
One way to prevent the problem is to remove the first two DEVICE
statements from your config.sys prior to reinstalling the beta.
6. If after reinstalling over previous betas, you can't get the system to
work, it's likely that there is some vestige of an old beta hanging
around and messing things up. Lots of folks have been able to
recover by removing the old beta as described in the README.MWV.
When doing this, make sure that you also remove the
DEVICE=\MMOS2\AUDIODD\AUDG2.SYS P N:AUDIOV1$
DEVICE=\MMOS2\VAUDIO.SYS
statements from config.sys. The existing README.MWV does not tell
you about removing these statements.
7. If, when installing the OS/2 beta disks, you get a message that says
"Only the Runtime Will Be Installed", it's likely that MMPM/2 is
not installed on your system. Install MMPM/2 before any of the
beta.
8. If you reinstall your Mwave Windows code (in a WIN-OS/2 session)
for any reason, follow that with a reinstall of your OS/2 Mwave
diskettes.
9. To change sound cards (for example, to change from SoundBlaster
to Windsurfer), you need to reinstall MMPM/2 and then install (or
reinstall) OS/2 Mwave and MMPM_EXT.
Follow these steps:
a. Install MMPM/2. When you are asked for your sound card, select the
one you are changing from (for example, SoundBlaster). When you're
asked how many cards you are installing, select 0. Continue with
the MMPM/2 installation to completion.
b. Reboot. You may receive error messages
indicating the system cannot find msg files. This is OK. Ignore
these messages. Install OS/2 Mwave. When you are asked, indicate
the card you're installing (for example, Windsurfer). Select yes
to the question that asks if jumper settings have changed
(ISA only) so that you can verify the correct values are set.
Continue with the OS/2 Mwave installation to completion.
c. Reboot. You may again receive error messages
indicating the system cannot find message files. This is still OK.
Install MMPM_EXT.
d. Reboot. There should be no error messages, and the new sound card
should be functional.
10.If OS/2 and particularly MMPM is installed from a CD, the files in
MMOS2 will be marked read-only and the MMPM_EXT installation will
fail. If you have this situation, reset the attributes by making
\mmos2 your current directory and issuing attrib -r *.* prior to
installing MMPM_EXT.
Audio Stuff:
1. The message produced if you try to start MIDI w/ insufficient MIPS
available is inaccurate. In OS/2, it says:
Unable to open device "MIDI". A DOS or WIN-OS/2 program may
have exclusive use of the device."
In WIN-OS/2, it says:
There are no MIDI devices installed on the system. Use the
Drivers option in Control Panel to install the driver.
Each of these messages is usually produced as a result of
insufficient MIPS. If you get either, try closing a running Mwave
application and restarting MIDI.
2. Playing System Sounds temporarily interrupts concurrent MIDI. (Not a
problem in WIN-OS/2).
3. If you get no System Sounds, assure they are enabled. Click on
Multimedia, then click on Sounds and make sure the
System Sounds Enabled box is checked.
4. Our current OS/2 MIDI support is not as good as the Windows (or
WIN-OS/2) MIDI. We are working towards a common code base for
these. When we get there, the support will be equivalent.
Unfortunately, for the time being, if you want the better MIDI
quality, you have to run the Windows or Win-OS/2 MIDI.
5. If in WIN-OS/2, you installed the 16 voice synthesizer (available
as part of Windsurfer Version 4), you will have an icon in the
Windsurfer group titled Select Synthesizer. The intent of this
is to allow you to select either the 8 voice or 16 voice
synthesizer. (You use the 16 voice for better quality and the 8
for greater concurrency...there is no modem concurrency with the 16
voice).
This Synthesizer selection will not work in OS/2. If you try to
change selections, the system will ask you to
select Restart Windows and then the system will tell you it
can't restart Windows.
Here's what you can do if you want to change between the 8 and 16
voice synths:
a. Exit WIN-OS/2.
b. Go to \mww\midisnth where there are 3 relevant files:
-mwsynth.drv
-mwsynth.8
-mwsynth.16q
c. For 8 voices, copy mwsynth.8 to mwsynth.drv; for 16, copy
mwsynth.16q to mwsynth.drv.
d. When you restart WIN-OS/2, your new selection will be active.
6. If you have no WIN-OS/2 sounds, check system.ini in \OS2\MDOS\WINOS2.
In the boot section is a line that should say either
drivers=mmsystem.dll, MWGAMES
or
drivers=mmsystem.dll
If the first parameter, mmsystem.dll, is missing, add it. In some
cases where users update from OS/2 2.0 to 2.1 or Windows 3.0 to
3.1, this entry gets lost.
Modem Stuff:
1. An inoperative modem or modem application is often the result of
a conflict in the area of port address and/or interrupt assignments.
If you have an ISA adapter, review Appendix C of your Windsurfer
User's/Installation Guide for guidance. For MCA Adapters, review
Appendix A.
2. If you like, you can explicitly change the OS/2 modem speed
to either 9600 or 2400 by opening the Settings associated with the
modem and selecting the desired speed.
3. If you use the modem in WIN-OS/2, make sure to close it prior to
to exiting. If the modem is not closed prior to exiting, the phone
line will remain allocated, and you will be unable to restart the
modem in either OS/2 or WIN-OS/2 until the system is rebooted.
Other Stuff
1. The WIN-OS/2 version of the discriminator ends abnormally when you try
to close it. You can still use the discriminator. Just ignore the
messages at shutdown.
2. If you use the TAM applet, assure that the .TAM files are in the same
subdirectory as TAM.EXE.
3. If you get an error 0x15BD when initiating the TAM applet, try
deleting mwtam.ini from your system and retrying. This error often
occurs after a reinstall if the TAM applet is installed in a
different directory on the reinstall. The original mwtam.ini
points to the original directory
and the applet doesn't find its message files. Deleting mwtam.ini
allows the applet to builds a new one pointing to the correct new
directory.
WIN-OS/2 Settings
Since the early versions of this beta contain no extensive
application programs, it's anticipated that significant use will be made
of its WIN-OS/2 support. This section contains WIN-OS/2 Settings hints
to facilitate Mwave operation in a WIN-OS/2 Session.
To run Mwave applications in a WIN-OS/2 Session , it is necessary to
check/modify four WIN-OS/2 Settings for that WIN-OS/2 Session. The four
WIN-OS/2 Settings are:
-WIN_RUN_MODE - set to "3.1 Enhanced Compatibility"
-HW-TIMER - set to "ON"
-INT_DURING_IO - set to "ON"
-DOS_BACKGROUND_EXECUTION - set to "ON"
The procedure for checking/modifying these four WIN-OS/2 Settings is
dependent upon the WIN_OS/2 Startup process that you use. Refer to your
OS/2 manual to determine the procedure for checking/modifying the
WIN-OS/2 Settings for the Startup process that you use, and be sure that
these four WIN-OS/2 Settings agree with the values shown above.
Three sample procedures for checking/modifying the WIN-OS/2 settings are
given below. Depending upon your WIN-OS/2 Startup technique, you may be
able to use one of these procedures.
Sample 1. WIN-OS/2 Settings For Migrated Programs
If you migrate a program written for Windows to your OS/2 Desktop, you must
check/modify the WIN-OS/2 Settings for each migrated program individually.
Use the following procedure on each migrated program:
-Start by migrating the Windows program using the instructions
from your OS/2 manual
-After migration, an Icon for the program will appear in the
"Additional Windows Programs" folder
-To modify the WIN-OS/2 settings for this program,
click on the migrated program's icon using mouse button #2,
(mouse button #2 is usually the right button)
-Select the Arrow to the right of Open
-Select Settings
-Select the Session Tab
-Select WIN-OS/2 Settings
-From the displayed list:
Scroll to and Select WIN_RUN_MODE (usually the first entry)
Select 3.1 Enhanced Compatibility
Scroll to and Select HW_TIMER
Select ON
Scroll to and Select INT_DURING_IO
Select ON
Select Save
Scroll to and Select DOS_BACKGROUND_EXECUTION
Select ON
Select Save
Close all windows
Sample 2. WIN-OS/2 Settings For WIN-OS/2 Full Screen Startup
If you intend to start WIN-OS/2 programs from the WIN-OS/2 Full Screen, use
the following procedure to check/modify the WIN-OS/2 settings. Unlike the
Migration procedure given above which must be performed on each migrated
program, this procedure need only be performed once. If you follow this
procedure now, a copy of the new WIN-OS/2 settings will be saved and used in
the future for any program started from a WIN-OS/2 Full Screen session. You
may want to perform the following procedure now.
-From the OS/2 Desktop, open the OS/2 System folder.
-Open the Command Prompts folder, and click on WIN-OS/2 Full Screen using
mouse button #2 (mouse button #2 is usually the right button).
-Select the Arrow to the right of Open.
-Select Settings.
-Select the Session Tab.
-Select WIN-OS/2 Settings.
-From the displayed list:
Scroll to and Select WIN_RUN_MODE (usually the first entry)
Select 3.1 Enhanced Compatibility
Scroll to and Select HW_TIMER
Select ON
Scroll to and Select INT_DURING_IO
Select ON
Select Save
Scroll to and Select DOS_BACKGROUND_EXECUTION
Select ON
Select Save
Close all windows.
Sample 3. WIN-OS/2 Settings For OS/2 Desktop Startup From an Object
Created Using Templates
If you intend to use OS/2 Templates to create an OS/2 Desktop object
for a WIN-OS/2 program and to start that WIN-OS/2 program and session
by selecting that Desktop object, use the following procedure to
check/modify the WIN-OS/2 settings. Unlike the Migration procedure
given above which must be performed on each migrated program, this
procedure need only be performed once. If you follow this procedure
now, a copy of the new WIN-OS/2 settings will be saved and used in the
future for any WIN-OS/2 program started from a OS/2 Desktop object
created with Templates. You may want to perform the following
procedure now. This procedure should be performed in addition to
sample 2 above and not in place of it. Sample 2 and Sample 3 will
check/modify two different copies to the WIN-OS/2 settings.
-From the OS/2 Desktop, open the OS/2 System folder.
-Open the System Setup folder.
-Double click on WIN-OS/2 Setup.
-Select WIN-OS/2 Settings.
-From the displayed list:
Scroll to and select WIN_RUN_MODE (usually the first entry)
Select 3.1 Enhanced Compatibility
Scroll to and Select HW_TIMER
Select ON
Scroll to and Select INT_DURING_IO
Select ON
Select Save
Scroll to and Select DOS_BACKGROUND_EXECUTION
Select ON
Select Save
Close all windows and return to the OS/2 Desktop.
Playing MIDI Files From the OS/2 Desktop
To play MIDI files in a WIN-OS/2 session from the OS/2 desktop, the
program MWS.EXE must be running in the same Session as the program
that runs the MIDI file.
Migrating MWS.EXE to the OS/2 Desktop
MWS.EXE is a Windows program that must be running before MIDI files can be
played in a WIN-OS/2 session. MWS.EXE will start whenever you open a full
screen WIN-OS/2 session, but you must start it manually if you start a
WIN-OS/2 MIDI application from the OS/2 Desktop. MWS.EXE must be running in
the same session as the MIDI application that plays the MIDI file. If
multiple WIN-OS/2 sessions are started, MWS.EXE must be started in each
session. One way to run MWS.EXE is to migrate it to the OS/2 Desktop and
start it before starting the MIDI Application. To migrate MWS.EXE to the
OS/2 Desktop, use the following procedure:
-From the OS/2 Desktop, open the OS/2 System folder
-Open System Setup
-Double click on Migrate Applications
-Highlight all hard drives (unless you know which drive has MWS.EXE)
-Deselect DOS and OS/2, select Windows
-Select Find
-A list of all the *.EXE programs in the default database will be
displayed, but MWS.EXE should not be in the default database, and
should not be displayed
-Deselect ALL the programs listed
-Select Add Programs
-A list of all programs NOT in the default database will be
displayed, and MWS.EXE should be on this list
-Find MWS.EXE and highlight it
-Select Add
-Select OK
-Select migrate
-Select OK at the migration complete notice
-Select exit and yes
-Close the System Setup window
-Close the OS/2 System window
-Open the Additional Windows Programs folder (this may be a new folder)
-Click mouse button #2 (usually the right button) on the MWS.EXE
icon
-Select the Arrow to the right of Open
-Select Settings
-Select the Session Tab
-Select WIN-OS/2 Settings
-From the displayed list:
Scroll to and Select WIN_RUN_MODE (usually the first entry)
Select 3.1 Enhanced Compatibility
Scroll to and Select HW_TIMER
Select ON
Scroll to and Select INT_DURING_IO
Select ON
Select Save
Close all windows.
To play a MIDI file in a WIN-OS/2 session from the OS/2 Desktop in the
future, first start the migrated program MWS.EXE by opening the Additional
Windows Programs folder and selecting the MWS.EXE icon. Then start the
WIN-OS/2 program that will run the MIDI file IN THE SAME WIN-OS/2 SESSION as
MWS.EXE (This program would also have been migrated to OS/2 and the WIN-OS/2
settings modified as given in "WIN-OS/2 Settings For Migrated Programs".)
Both programs must be running in the same WIN-OS/2 Session.
Closing WIN-OS/2 Mwave Session From OS/2
Do not attempt to close a WIN-OS/2 session that uses the Mwave Adapter from
the objects pop-up menu, or from the Window List.
Full screen WIN-OS/2 sessions that use the Mwave Adapter, should be closed
from the WIN-OS/2 Program Manager Title-Bar Icon (upper left corner of the
Program Manager window).
WIN-OS/2 sessions that are started from the OS/2 Desktop should be closed by
closing each of the applications within that session from the Title-Bar Icon
(upper left corner of each application Title-Bar).
Removal Process
To remove previous Mwave OS/2 Beta support, please follow these steps
carefully. If no Mwave OS/2 Beta support prior to 5/27/94 is
installed, ignore this section.
In your CONFIG.SYS file:
1. Remove all d:\MWAVEOS2 paths from LIBPATH
2. Remove all d:\MWAVEOS2 paths from SET PATH
3. Remove all d:\MWAVEOS2 paths from SET DPATH
4. Remove all d:\MWAVEOS2 paths from SET HELP
5. Remove all d:\MWAVEOS2 paths from SET BOOKSHELF
6. Remove all d:\MWAVEOS2 paths from SET LIB
7. Remove all d:\MWAVEOS2 paths from SET INCLUDE
8. Remove all DEVICE=d:\MWAVEOS2\BIN\xxxx
8a.Remove DEVICE=d:\MMOS2\AUDIODD\AUDG2.SYS P N:AUDIOV1$
8b.Remove DEVICE=d:\MMOS2\VAUDIO.SYS
9. Remove SET MWROOT
10. Remove SET MWPATH
11. Remove SET MWOSNAME
12. Remove SET MWBIOS
13. Remove SET MWCARD
14. Remove SET MWFT_PATHNAME
15. Remove all RUN=d:\MWAVEOS\BIN\xxxx
In your STARTUP.CMD file:
16. Remove anything like "START d:\MWAVEOS2\BIN\MWAVEDM.EXE"
From WPS (your OS/2 desktop):
17. Stop all applications which are using your Mwave software.
18. Delete the "Mwave for OS/2" folder from your OS/2 desktop (or where
ever it and copies or shadows of it may be located).
19. Delete any "Mwave Manager for OS/2" icons from your OS/2 desktop (or
where ever it and copies or shadows of it may be located). Be sure
to check your "Start Up" folder!
20. Delete any "Mwave Modem" icons from your OS/2 desktop (or where ever
it and copies or shadows of it may be located).
21. Delete any "Mwave Discriminator" icons from your OS/2 desktop (or
where ever it and copies or shadows of it may be located).
Finally:
22. Stop MWAVEDM.EXE by closing it's session or restarting OS/2. If
RUN=d:\MWAVEOS2\BIN\MWAVEDM.EXE was in your CONFIG.SYS, you must
shutdown and restart OS/2 (using your new CONFIG.SYS at this point.
23. Delete (or erase and remove) the d:\MWAVEOS2 directory structure and
files from your disk.
24. If you didn't just restart OS/2 in step 22, then shutdown and restart
OS/2, now.