
                            Using the Panasonic CR-563B in
                             an OS/2 Virtual DOS Machine
                                                                    12/28/93

     This document was written to assist those new owners of the Reveal
     Multimedia FX Kit, model MFX-04,  with the following symptoms:
     The OS/2 MMPM/2 Soundblaster Pro driver will not load properly or
     there is no driver letter assigned to the CD-ROM device in OS/2.
     This kit contains the Panasonic CR-563B CD-ROM internal drive and
     "SoundFX" (Soundblaster Pro II compatible) 16-bit sound card.
     The CD-ROM is AT-bus connected to the Panasonic interface on the
     sound card.  It appears that it may be a while before the correct
     drivers are available. I went ahead and setup a bootable VDM in
     OS/2 in which to load the drivers, providing full access and usage
     of the CD-ROM and sound card hardware.  In the VDM, I start my DOS
     based BBS, which runs merrily along automatically, while I am over
     in the Workplace Shell running other DOS or OS/2 tasks.  I can shut
     down the BBS and start Windows (WINOS2) to use the CD-ROM software
     included with the kit or stay in DOS to access the CD-ROM.  The
     following procedure will show, step by step, how to do it.

     The operating systems used in this example are OS/2 V2.1 GA and DOS
     version 6.2.

     Step 1.  Ensure that all the software and hardware provided in the
              multimedia kit have been installed and customized.  Either
              using Dual Boot feature or inserting a DOS-bootable diskette,
              boot your system to DOS. Run the install program on the
              Multimedia FX software diskette 1.  If you have Windows,
              install the CD-ROM applications to verify the CD-ROM device
              is functioning properly.  Otherwise, try installing one of
              the DOS-based programs.  Edit or browse the AUTOEXEC.BAT file
              on the "C" drive and make a note of the BLASTER and GALAXY
              SET statements.
     Step 2.  Create a bootable DOS system disk.  You can make one by
              placing a blank diskette in drive A: and entering
              "FORMAT A: /S".  (I would recommend at least DOS V6.0
              or higher.) This should be done while booted up on DOS.
     Step 3.  Using an editor, create a CONFIG.SYS file on the bootable
              diskette, specifying the following information:

                DEVICEHIGH=C:\OS2\MDOS\HIMEM.SYS
                DEVICEHIGH=C:\OS2\MDOS\EMM386.SYS RAM
                DOS=HIGH,UMB
                BUFFERS=30
                FILES=40
                LASTDRIVE=M
                SHELL=C:\DOS\COMMAND.COM C:\DOS\  /p
                DEVICE=C:\OS2\MDOS\FSFILTER.SYS
                DEVICEHIGH=C:\MMP16P\DRIVERS\CR56X.SYS /D:MSCD000

              Change the path information above for your particular
              setup, but notice that you are using the OS/2 version
              of the memory managers. The above example should yeild
              over 600K of memory below the 640 line.  The LASTDRIVE
              entry should be changed, if you are using multiple devices,
              to "Z".  Also, notice the SHELL entry points to a DOS
              command interface and not the OS/2 version.  Do not try
              to load the FSFILTER driver high, errors will occur.
     Step 4.  Using an editor, create an AUTOEXEC.BAT file on the
              bootable diskette, specifying the following information:
                @ECHO OFF
                PROMPT $p$g
                SET BLASTER=A220 I5 D1 T4
                SET GALAXY=A220 I5 D1 K2 P330 T6
                SET SOUND=C:\MMP16P
                C:\DOS\MSCDEX.EXE /D:MSCD000
                SET PATH=A:\;C:\;C:\DOS;C:\MAX;C:\OS2\MDOS;C:\OS2\MDOS\WINOS2;
                C:\OS2\MDOS\FSACCESS M=A
                SET TEMP=C:\DOS
                SET TMP=C:\DOS
                C:
              Ensure that the BLASTER and GALAXY set statements match the
              values noted earlier in step 1.  Change the PATH information
              to reflect your environment.  If you do not have a copy of
              the MSCDEX (Microsoft CD-ROM Extensions) device driver, check
              the directories on the diskettes that came with the kit. Or
              download it from one of your favorite bulletin boards.  Note
              the device name specifed on the MSCDEX (/D:MSCD000) must match
              exactly the device specified in CONFIG.SYS statement which loads
              the CR56X device driver.
     Step 5.  Boot your system using the new bootable diskette created in
              the previous steps.  You should expect errors trying to load
              some of the OS/2 related drivers (since OS/2 won't be running
              on this particular boot).  The CD-ROM device drivers should
              both load correctly, CR56X.SYS and MSCDEX.EXE.  After the boot
              has completed, the next available drive letter should be
              assigned to the CD-ROM drive.  On most systems it would be the
              letter "D" or "E".
     Step 6.  Remove the diskette and boot up OS/2.
     Step 7.  In the OS/2 Workplace Shell, create a new PROGRAM object on
              the desktop.  Give it a title of "DOS VDM" or whatever turns
              you on.  In the "Settings" object, specify an asterisk (*)
              in the box labeled "Path and Filename". Click the "Session"
              tab and then click "DOS Fullscreen".  Click the button labeled
              "DOS Settings".  The following parameters should be set to
              the values indicated below:
                 DOS_AUTOEXEC             should be blank
                 DOS_BACKGROUND_EXECUTION should be ON
                 DOS_HIGH                 should be ON
                 DOS_LASTDRIVE            should be Z
                 DOS_SHELL                should point to the OS/2/MDOS/COMMAND.COM
                 DOS_STARTUP_DRIVE        should be C:\VMB\DOS.IMG
                 DOS_UMB                  should be ON
                 EMS_MEMORY_LIMIT         should specify the total RAM amount
                 HW_ROM_TO_RAM            should be ON
                 HW_TIMER                 should be ON
                 IDLE_SECONDS             should be 60
                 IDLE_SENSITIVITY         should be 100
                 INIT_DURING_IO           should be ON
                 VIDEO_8514A_XGA_IOTRAP   should be ON
                 VIDEO_RETRACE_EMULATION  should be OFF
                 VIDEO_ROM_EMULATION      should be ON
                 XMS_MEMORY_LIMIT         should be set to 2048 or higher
              Click "Save" button.  Do not attempt to run this object yet!
              We still have to create the DOS image file specified in the
              DOS_STARTUP_DRIVE setting above.
     Step 8.  From the OS/2 System object, open the "Command Prompts" folder.
              Open the "OS/2 Full Screen" object.  At the "C:\" command
              create a directory called "VMB".  Change to that directory.
              Insert the bootable diskette you created earlier in step 2.
              Type the following command: VMDISK A: DOS.IMG
              where "A:" is the drive containing the bootable diskette.
              The process of creating the DOS image may take between 2 and
              10 minutes.  When completed, type exit and return to the
              desktop.
     Step 9.  Double click the object you created earlier in step 7.  The
              screen will clear and the DOS boot process will take place.
              Watch for errors during the load of the drivers.  If they
              all load correctly, you should have access to the CD-ROM.
              If an error occurs, you can change the CONFIG or AUTOEXEC
              by pointing to the "A:" drive.  The "A:" drive is actually
              imbedded within the the file C:\VMB\DOS.IMG.  To access the
              physical floppy drive A, specify the drive letter "M:".
     Step 10. You can start WINOS2 at the command prompt by simply typing
              "WIN".  Once Windows is started, select "File Manager" and
              see what drive letters are displayed.  Click the "D" or "E"
              or whatever your next drive letter was.  It is suggested that
              a CD, of some type, always be in the drive.  Run the setup
              program on each CD provided with the kit to ensure that
              the necessary support files are created for the WinOS2
              environment.  Run the install program on the Multimedia
              software diskette 1.  This DOS program will run install the
              soundblaster support in WINOS2.  When the install program
              asks for the path to the Windows directory, be sure to specify
              C:\OS2\MDOS\WINOS2.

     That completes the procedure.  That wasn't very difficult at all.
     If for some reason the VDM locks up or you simply want to end it,
     press CTRL-ESC to return to the desktop, where you can close the
     object.  Then, just restart it again when your ready.
     Have fun and enjoy!
