----==================================---- ----====< DOS/WINDOWS VIRTUAL SB >====---- ----====< BETA RELEASE SOFTWARE >====---- ----====< Version 0.87 >====---- ----==================================---- What is the Virtual Sound Blaster? The Virtual Sound Blaster is a 386 driver for Windows 3.0. It allows SB specific code to run on the Pro Audio Spectrum from either Windows or 386 DOS shells. How does it work? By using the 386 hardware virtualization, this code traps all low-level reads/writes to the SB and makes the appropriate translation to the PAS card. Both DOS and Windows SB applications will be able to use the Virtual SB. Are there any special conditions needed to run it? This code is currently incompatible with the Media Vision Multi Media drivers. Basically, a device contention occurs when the MV drivers try to use the hardware at the same time a virtual SB session is running. How Do I install the Virtual Sound Blaster? PLEASE follow these instructions. You may be sorry later if things dont work out. 1. As explained in "READ.ME", unpack the the contents of SB2MV.zip 2. Copy SB2MV.386 to your Windows system DOS>copy SB2MV.386 c:\windows\system 3. Change directories to the Windows subdirectory. Typically, like this: DOS>cd c:\windows\system 4. Make a backup copy of your SYSTEM.INI!!! Typically, like this: DOS>copy system.ini sysbk This is critical in case the Windows configuration is ever corrupted. You will be able to restore everything back to the original configuration just by replacing the current SYSTEM.INI with the backup copy. 5. Edit the SYSTEM.INI file using a text editor. Add the next two lines: DEVICE=SB2MV.386 DMABUFFERSIZE=064 to the end of following area: [386Enh] These two entries must be the last two entries in this section. At the Bottom of the SYSTEM.INI file, insert the following lines: [mvwave.drv] dma=1 int=5 port=220h mpu401=0 If you have already installed the Multi- Media Extensions to Windows, the above section may already exist. Just add the "port=" and "mpu401=" lines. The MPU-401 emulation is not yet complete, so let it equal zero. This will disable virtualizing the MPU-401 I/O addresses. 6. Start Windows, then remove any PAS Multi-Media drivers. How do I run Wing Commander II? You must have the following drivers loaded in your config.sys: HIMEM.SYS EMM386.SYS Checkout the example CONFIG.SYS later in this file. There must be 1.5 to 2 megabytes of expanded memory to run Wing Commander using the speech pack. Once installed, run Windows and shell out to a DOS VM. Check to see how much memory is installed. There must be at least 584k available. I had to update to DOS 5.0, unload most drivers and TSRs from config.sys and autoexec.bat before I had enough memory. Here is a very critical performance requirement. Use the example GAMES.PIF included in this ZIP to run Wing Commander II. This PIF specifies the memory requirements, but more inportant, tells Windows not to monitor the video I/O. Most of the performance loss will occur due to wrong PIF settings. GAMES.PIF gives requests all the system resources to be used exclusively to this DOS shell. What other software works with the Virtual Sound Blaster? Disney's Mickey Mouse Jigsaw. Gary Maddox's Blaster Master. Dave Young's Silly String. Creative Labs' VPLAY.EXE. Creative Labs' VREC.EXE . Creative Labs' Dr. Sbaitso. Creative Labs' Talking Parrot. Sierra On-Line Leisure Suite Larry, I. PG Music's Band In a Box. and more... What doesn'nt work? Broderbund's Carmen San Diego, Tree House, and KidPix. To use these games, run the DOS Virtual Sound Blaster TSR. Creative Labs' VOXKIT.EXE What else is needed? As mentioned above, you may need DOS 5.0 to make enough memory available in the DOS shell. Also, you MUST use the example PIF to get the most performance out of the DOS shell. How do I restore the Windows setup to it's original configuration? You can easily restore the configuration by copying the backed up copy SYSTEM.INI into the Windows subdirectory; thereby, overwriting the current file. The best approach would be to have two backup copies of SYSTEM.INI. One that is the original and the other having the Virtual SB installed. To run either configuration, just copy the correct file into the Windows subdirectory, then fire up Windows. My CONFIG.SYS file: | |device=c:\dos\setver.exe |device=c:\dos\himem.sys |device=c:\mwindows\emm386.sys 2048 frame=e000 |lastdrive=h |files=20 |buffers=20 |shell=c:\dos\command.com c:\dos\ /e:512 /p |DOS=HIGH | My SYSTEM.INI file: | |[boot] |display.drv=mmv7vga.drv |shell=progman.exe |sound.drv=SOUND.DRV |;;;;sound.drv=mmsound.drv |sound.drv=sound.drv |386grabber=v7vga.gr3 |286grabber=vgacolor.gr2 |network.drv= |language.dll= |fixedfon.fon=vgafix.fon |comm.drv=comm.drv |oemfonts.fon=vgaoem.fon |fonts.fon=vgasys.fon |mouse.drv=mouse.drv |keyboard.drv=keyboard.drv |system.drv=system.drv |drivers=mmsystem.dll | | |[drivers] |;;;wave=tbwave.drv | |;;;[mci] |;;;WaveAudio=mciwave.drv | |[keyboard] |subtype= |type=4 |oemansi.bin= |keyboard.dll= | |[boot.description] |display.drv=Video 7 VGA VRAM I 640x480 with 256 colors |network.drv=Network not installed |language.dll=English (American) |keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards |mouse.drv=Microsoft, or IBM PS/2 |system.drv=MS-DOS or PC-DOS System | |[386Enh] |ebios=*ebios |display=*vddvga |keyboard=*vkd |mouse=*vmd |network=*vnetbios, *dosnet |device=*vpicd |device=*vtd |device=*reboot |device=*vdmad |device=*vsd |device=*v86mmgr |device=*pageswap |device=*dosmgr |device=*vmpoll |device=*wshell |device=*vhd |device=*vfd |device=*vpd |device=*parity |device=*biosxlat |device=*vcd |device=*vmcpd |device=*combuff |device=*cdpscsi |local=CON |FileSysChange=off |DMABUFFERSIZE=064 |device=sb2mv.386 | |CGA40WOA.FON=CGA40WOA.FON |CGA80WOA.FON=CGA80WOA.FON |EGA40WOA.FON=EGA40WOA.FON |EGA80WOA.FON=EGA80WOA.FON | |[standard] | |[NonWindowsApp] | |[Multimedia.Setup] |;;;audio=mvwave.drv,0,0,0 |display=v7vga | |[mvwave.drv] |dma=1 |int=5 |port=220h |mpu401=0 | |[mvmidi.drv] |int=5 | |[tbwave.drv] |port=220 |int=2 |