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.0 This beta version of OS/2 Mwave Software supports the Windsurfer ISA Communications Adapter and the Windsurfer MCA Communications Adapter. For those users who do not have the latest versions of Mwave Windows support, that software is provided as well. The following configurations are supported: -Native OS/2 Mwave -WIN-OS/2 Mwave -OS/2 for Windows Mwave -Native Windows Mwave 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. WSISA4Dx.ZIP: Optional. Download these three files if you want WIN-OS2 (or native Windows) Mwave support for a Windsurfer ISA bus adapter. Unzip the files to create 3 installation diskettes. Use the -d option when unzipping these files. WSMCA4Dx.ZIP: Optional. Download these three files if you want WIN-OS2 (or native Windows) Mwave support for a Windsurfer MCA bus adapter. Unzip the files to create 3 installation diskettes. Use the -d option when unzipping these files. WINOSFIX.ZIP: Required for WIN-OS/2. Download and unzip this file to create updated OS/2 modules (mciseq.drv and timer.drv) required for WIN-OS/2 operation. These files can be unzipped to any convenient place on your fixed disk. EXTRA.ZIP: Optional. Download and unzip this file to create two OS/2 Mwave sample applets (fax.exe and tam.exe) and an Mwave utility (mwflush.exe). These files can be unzipped to any convenient place on your fixed disk. README: This file Note that unzipping these files requires Version 2.04g (or greater) of PKUNZIP. 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, and WSISA4Dx.ZIPs (for isa bus machines), or WSMCA4Dx.ZIPs (for mca bus machines). Label diskettes from WSxxxxxx.ZIP: WIN DISK1, WIN DISK 2 and WIN DISK 3. (Unzip WINOSFIX.ZIP to any convenient place on your fixed disk.) 5. If desired, download and unzip EXTRA.ZIP to any convenient place on your fixed disk. 6. Follow the installation procedures described below. Individual procedures are described for native OS/2, WIN-OS/2, and native Windows (for dual boot users). 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 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.1 for Windows. Native OS/2 Mwave support in this version includes the following items: -Base Mwave -Mwave Manager -MwaveOS -MEIO -Modem -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 full OS/2 containing its own Windows (not OS/2 for Windows). 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. OS/2 for Windows Mwave OS/2 for Windows Mwave refers to Mwave which runs using OS/2 for Windows. With two exceptions, all Mwave facilities described above are also available with OS/2 for Windows. The two exceptions are dual boot (or boot mgr) and WIN-OS/2. In an OS/2 for Windows system, the current beta version does not support Mwave running in a dual boot OS/2 for Windows - Dos Windows system and it does not support Mwave running in a WIN-OS/2 session. It is our intention to support these facilities in later versions. 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, you will need to additionally install the Windows Mwave diskettes in a WIN-OS/2 session. See below). Additionally, in order to run Mwave MMPM audio applications you must install it from the MMPM_EXT disk as described in the next section. 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. Prior to doing the OS/2 install, assure that the Mwave daemon from an old version of the beta is not running. (It won't be running if you removed the old beta as described in the section, Removal Process). 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 auido, 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. Note thatthis installtation requires that MMPM/2 be already installed on your system. During this installation, references to the Audiovation Adapter appear on the display. Don't worry about this. The code being installed is really for the Windsurfer adapter. 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. Install the OS/2 Mwave diskettes as described in "Installing Native OS/2 Mwave Support", above, and also install the Windows Mwave diskettes. 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 (WIN DISK 1) in drive a and type a:setup from the Windows File|Run menu. Then follow the instructions that appear on the display. This procedure will work for both a full OS/2 environment and an OS/2 for Windows environment. 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 two updated OS/2 modules: mciseq.drv and timer.drv. These modules replace existing versions of the modules in \os2\mdos\winos2\system. These updated modules are provided in EXTRA.ZIP. For WIN-OS/2 operation, you must manually copy these two modules into \os2\mdos\winos2\system. They are not automatically copied as part of the installation procedure. In an OS/2 for Windows system, similar fixes are required. These fixes are not yet available. 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 Windows set of Mwave installation diskettes. Most current Mwave users already have native Windows Mwave support installed and therefore can skip this step. To install, place WIN DISK1 into drive a and type a:setup from the Windows File|Run menu. Then follow the installation instructions that appear on the display. Full-blown Install A full-blown install would include these separate installation steps. The ordering is not important. -Install the Native OS/2 diskettes under OS/2 (for the native OS/2 Mwave support). -Install the Windows diskettes under WIN-OS/2 (if you want WIN-OS/2 Mwave support. Also, copy the two updated OS/2 modules to \os2\mdos\winos2\system if running with a full OS/2 system or copy the two updated Windows modules to \xxx\xxx if running with an OS/2 for Windows system. -Install the Windows diskettes under native Windows if it isn't already on your system (if you want dual boot Mwave Native Windows support). Windows Mwave Support Included in This Version The following support is included in the Windows Mwave support provided by the WINDISAx and WINDMCAx disk images. -Mwave Base -Synthesizer w/ base patch set -Half duplex speaker phone -Voice/FAX discriminator -V.17 FAX (14400 bbs) -V.32 Modem (9600 bps) -V.32 bis Modem (14400 bps) -V.42 Modem (Error Correction) -V.42 bis Modem (Compression) -Audio Applets -DOS Games audio Known Limitations Following are known limitations of this version of OS/2 beta: 1. The MMPM driver does not fully support the AUX source (CD, LineIn, Mic). To listen to this AUX source, open the Digital Audio Application 2. The WIN-OS/2 version of the discriminator blows up when you shut down the discriminator application. 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 from the OS/2 desktop, the Mwave Adapter's Audio Mode must be set to Normal (not Audio/Image Synch) and the program MWS.EXE must be running in the same Session as the program that runs the MIDI file. These procedures are given below. Setting the Mwave Adapter's Audio Mode to Normal The default Audio Mode is Normal but if you change it to Audio/Image Synch, you must change it back to Normal before you can play MIDI files from the OS/2 Desktop. To change the Audio Mode: -Open the Mwave folder -Open the Mwave Audio Control folder; the Mwave Audio Control window appears (looks like an audio mixer) -Click on the Control Menu Box in the upper left corner of the Audio Output Control window; the Options window appears -Select Normal for the Audio Mode and click on OK -Close all windows. Refer to the "Additional Audio Controls" section, of the "Audio Control" chapter for more information about Audio Modes. 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). If you close a WIN-OS/2 session from the objects pop-up menu or the Window List, the Mwave DSP's programs may continue to run. This will consume DSP resources and may prevent you from starting another Mwave application. If this happens, you can use the utility program MWFLUSH.EXE to free up the leftover dsp resources. Use MWFLUSH with caution since it removes all tasks from the DSP. Removal Process To remove previous Mwave OS/2 Beta support, please follow these steps carefully. If no previous Mwave OS/2 Beta support 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 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.