Audio package 1.0.1b for OpenServer 5 [22 Mar 1999] Drivers for audio cards, audio configuration utility, and Plug and Play update. KEYWORDS: openserver v5 osr5 audio card creative sound blaster ess adapter driver 5.0.4 5.0.5 hardware supplement ftp downloadable configuration manager plug and play pnp realaudio RELEASE: SCO OpenServer Enterprise System Release 5.0.4, 5.0.5 SCO OpenServer Desktop System Release 5.0.4, 5.0.5 SCO OpenServer Host System Release 5.0.4, 5.0.5 HARDWARE: AdLib FM synthesizer card Aztech Sound Galaxy NX Pro BTC-1831 Sound card (ES 1688) Creative SoundBlaster 1.0 or 1.5 Creative SoundBlaster 16 Creative SoundBlaster 16 ASP Creative SoundBlaster 16 PnP Creative SoundBlaster 16 Vibra Creative SoundBlaster 2.x Creative SoundBlaster 32/AWE Creative SoundBlaster 32/AWE PnP Creative SoundBlaster AWE64 Creative SoundBlaster AWE64 Gold Creative SoundBlaster Pro Creative ViBRA16C PnP Creative ViBRA16CL PnP Creative ViBRA16X PnP ESS ES1868 Plug and Play AudioDrive ESS ES1869 Plug and Play AudioDrive ESS ES1878 Plug and Play AudioDrive Generic ESS ES1688 based sound card or motherboard Generic ESS ES688 based sound card or motherboard Generic Jazz16 based sound card Intel Endeavour builtin audio (SB16 Vibra) Logitech Soundman Games Logitech Soundman Wave Maxi sound 64 / Home Studio 64 (audio only) Media Vision Thunderboard MediaVision ProSonic 16 NOTE: The compatible bus type for the audio driver is ISA (no PCI). PROBLEM: I have a previous version of the Audio Configuration Manager. Do I need to remove it before installing this one? SOLUTION: Yes, this is required. If you are on 5.0.4 and have any form of audio manager, OSS drivers or pre-release of the PnP manager and driver installed, you must remove those prior to installing this new package. PROBLEM: I have a PnP sound card that I can configure in the PnP manager, but the Audio Manager fails to auto-detect it, and the card appears not to work. SOLUTION: If you have a Creative Labs sound card, configure it using the PnP manager, make a note of the settings you chose, then run the audio configuration manager, and add a sound card. Choose "Creative" for the manufacturer, and "SoundBlaster 16" for the model. When prompted, use the values that you selected in the PnP configuration manager. The same technique may apply to other vendors, although this has not been tested. PROBLEM: What drivers are available for audio cards under OpenServer? SOLUTION: This audio package adds support for various SoundBlaster compatible cards. It is based on version 3.7.1f of the OSS driver and supports the RealPlayer. This package is available at the following URLs: ftp://ftp.sco.com/pub/drivers/OSR505/audio ftp://ftp.sco.com/pub/drivers/OSR504/audio The package will also be available on the upcoming "SCO Open Server Optional Services" CD. NOTE: If installed on OpenServer 5.0.5, this package installs a few minor updates to the PnP utilities so that the audio configuration utility can exchange information with the PnP subsystem. OpenServer 5.0.4 has no PnP subsystem, so on 5.0.4, this package installs the PnP driver and associated utilities. NOTE: If your sound card is not supported by the provided drivers, 4Front Technologies sells additional drivers for SCO operating systems, one of which may support your card. 4Front's web site is http://www.4front-tech.com. PACKAGE VERIFICATION: $ sum -r VOL.000.000 31544 702 VOL.000.000 INSTALLATION: This package is required before installing the RealPlayer package. The Skunkware 98 version of this package also supports the RealPlayer, but upgrading is recommended. Do not use an older version of the OSS driver. 1. Before installing the audio package, remove any old version of the OSS driver that is configured in your kernel. This includes the OSS "pnp" driver, if it is installed. The "pnp" driver that came with previous versions of OSS is different from the "PnP" driver which SCO now provides. If you have an older copy of the OSS drivers installed, you should be able to remove it from the kernel by running "/usr/lib/oss/Remove". 2. Make sure that the OSS "pnp" driver is disabled. - If the file "/etc/conf/sdevice.d/pnp" exists, make sure that it contains a line such as the following, with "N" in the second field: pnp N 1 0 etc. etc.... - (For OpenServer 5.0.5) If the file "/etc/conf/sdevice.d/PnP" exists make sure that it contains a "Y" in the second field. 3. If you made any changes to your kernel configuration, rebuild the kernel with: /etc/conf/bin/idbuild Then, reboot your system. 4. Use custom to install the audio driver package. - If you are running OpenServer 5.0.5, install: + Audio configuration manager, utilities, and drivers + PnP Update for SCO OpenServer 5.0.5 (ONLY) - If you are running OpenServer 5.0.4, install: + Audio configuration manager, utilities, and drivers + PnP Configuration Manager and Driver for SCO OpenServer 5.0.4 + Boot update for SCO OpenServer 5.0.4 (ONLY) After installing the packages on OpenServer 5.0.4, you must reboot to activate the "PnP" driver. On OpenServer 5.0.5, the PnP update does not require rebooting. After this package is installed, this document, along with additional information on how to use the audio configuration utility to configure an audio card, can be found in /usr/lib/audio/README. -------------------------------------- CONFIGURATION: The two steps for configuring Plug and Play sound cards under OpenServer are: 1. Configure the Plug and Play resources. 2. Configure the audio driver. (For non-Plug and Play cards, you only need to configure the audio driver.) You can configure the Plug and Play settings manually by invoking /etc/pnp or using the Audio Configuration Manager. 1. Run "scoadmin audio" or choose the Audio Configuration Manager from scoadmin to begin configuring the sound card. 2. Choose "Soundcard->Add". - If you have a non-Plug and Play card, choose your manufacturer and card from the displayed list and click on "OK". - If you have a supported Plug and Play card, click on "Auto Detect" at the bottom of the window to detect your card automatically. If you choose "Auto Detect" and your card is not listed, see below under "What if my Plug and Play card is not recognized?" 3. Specify the card resources: - For a non-Plug and Play card, enter the resources your card is set to, and click on "OK" and skip to step 6. - For a Plug and Play card, click on "Settings" to view the card's current PnP settings. If the PnP card has not been configured, clicking on "Settings" runs the PnP Configuration Manager and automatically displays the settings for your audio card. When you have chosen appropriate values, click on "OK" and go to step 4. If the PnP card has already been configured, clicking on "Settings" displays the current card settings. To run the PnP Configuration Manager and change the settings, click on "Modify". (To accept the current settings, click on "Close".) Once the PnP settings for the card are configured, click on "OK" and skip to step 6. - NOTE: If the PnP manager reports a conflict with the device settings, and the conflict is for the card you are configuring, you can ignore the error. If the conflict is with any other device, you need to assign different resources. 4. When the main window of the PnP Configuration Manager appears, click on "Apply" to save the settings. 5. At the prompt to relink the kernel appears, click on "Cancel". The Audio Configuration Manager also requires a kernel relink so you can skip this relink. 6. At this point, you are in the Audio Configuration Manager and have accepted the settings for the card. You should see a dialog asking you to indicate whether or not you want the kernel to be relinked. If you choose "Cancel", all driver configuration will be done except for the final kernel link. If you choose "OK" the kernel will be relinked after the manager finishes making the driver configuration changes. Normally, you will say "OK" here. 7. At the main window of the Audio Configuration Manager, select "Host->Exit". 8. Reboot your system to activate the sound driver. 9. Test the card: - Start up the Audio Configure Manager and select "Soundcard->Test". - Enter the following command using a .au audio file: "cat .au > /dev/audio" "What if my Plug and Play card is not recognized?" First, make sure that the PnP module sees your card. Run "/etc/pnp" manually and see if your card is listed. If not, there is something wrong with the configuration of the PnP module. Run "cat /dev/string/cfg". If the PnP module is working, you will see a line much like this one: %PnP - - - nodes=1 bios=yes bus=os Nodes should be at least 1. If you do see this line, you have a very confusing problem because the module is in the kernel but it did not see your card. If you do not see this line, make sure that the PnP module is linked into the kernel. Even if your card does show up in "/etc/pnp", one of the following may be true: - You have a plug-and-play card for which SCO has not licensed drivers. In particular, there are cards which are supposedly SoundBlaster compatible, but which do not really function exactly like a SoundBlaster card. See the last paragraph in this section for a possible workaround for this situation. You might also want to visit the 4front web site (http://www.4front-tech.com/) to see which other drivers are available for the OpenServer platform. - You have a plug-and-play card for which there is a driver, but the Audio Configuration Manager does not know about your particular card's PnP ID. This can happen because there are many different PnP IDs which correspond to the same basic card and new IDs are created from time to time. If you suspect this is the case, contact SCO to see about having your card's ID added to the known card database. You might be able to get an unrecognized card working by specifying the settings with the PnP Configuration Manager and then choosing a non-PnP audio card (such as the "Creative SoundBlaster 16") from the list of possible cards in the Audio Configuration Manager. Enter the appropriate resources for your card, and click on "OK". KNOWN BUGS: French and Spanish support is not yet available. MODIFICATION HISTORY: This is a new package, although earlier versions of the OSS drivers were previously available as part of Skunkware. January 1999 The package has been updated to fix some problems when installing on 5.0.4 machines, and has an enhanced PnP driver for 5.0.5. The 5.0.4 driver also contains a new boot loader, which is patched as part of the normal installation process. March 1999 Updated this README with new instructions for PnP cards.