Sound blaster 16 ms dos driver

User icon An illustration of a person's head and chest. Sign up Log in. Web icon An illustration of a computer application window Wayback Machine Texts icon An illustration of an open book. Books Video icon An illustration of two cells of a film strip.

Video Audio icon An illustration of an audio speaker. Audio Software icon An illustration of a 3. Software Images icon An illustration of two photographs. Daqarta will use the BLASTER environment string, but also allows you to use different settings, for example to avoid some conflict that doesn't arise when using other programs. Daqarta reads the old settings before changing anything, and restores them on Quit.

The D: parameter specifies the DMA level for 8-bit operation while the H: parameter is for bit operation. The driver will start in the mode that corresponds to whichever of these is given last. For example, if you give: SB If no DMA parameters are given, the default mode is also bit. Allowable values for D: are 0, 1, or 3. The factory default is 1. Allowable values for H: are normally 5, 6, or 7. The factory default is 5. Note, however, that you can set the H: value to match the D: value.

This is used to notify the SB You thus should use this only if you don't have an available bit DMA channel on your machine. If you set D: and H: equal and have also used B:Dn to specify full duplex operation, Daqarta will exit with 'Full duplex mode requires H: value 5, 6, or 7. CFG file in this case. The need for this interrupt should not be confused with interrupt-driven sampling used for RTime operation on some "basic" laboratory- type boards, where an interrupt request is generated for each sample acquired.

Here the IRQ is used only in conjunction with DMA sampling, to signify the completion of an entire buffer full of data. Allowable values for I: are 2, 5, 7, or Although the time to give this extra command is unlikely to ever be a problem, you might want to use 5 or 7 if there is no other conflict.

However, any program that runs before Daqarta in the same DOS session may change non-PnP board settings to something you don't intend for Daqarta. Note that Daqarta requires the : to be inserted between the letter and value. On Quit ting Daqarta, the settings are restored to their previous values, which were read from the board registers at the start of the session.

This insures that Daqarta never disturbs any other use of your SB16 board. Unless it is a PnP board that has not been set up by a configuration utility , in which case it is invisible to the system. To get around this conflict, this driver allows you to control the settings that are stored in the SB16 board registers.

Note that using this option may cause conflicts with other software that uses the SB16 board, so caution is advised. The following instructions apply only to non-PnP boards. Only the configuration manager can make changes to PnP boards. Of course, it is assumed here that the other device can perform a similar function so that when it is not in use it will not conflict with the SB Conversely, you can use a K instead of the C to Keep the relevant value when you Quit Daqarta, and it will be set into the board register regardless of what value may have been present at startup.

In either case, the C or K only applies to the specific parameter it appears with. You may mix and match as needed, and any parameter that has neither of these will have its initial value restored upon Quit.

Setting F:0 on the ADC configuration line tells the driver not to look for the file. You would probably only want to use this option if you are really short of DOS memory, since loading the Help file only increases memory use by a few hundred bytes for its separate link stack and directory. The file itself shares the text buffer of the Main Help file.

If this is present, no individual module Help will be loaded. Note that this does NOT actually change the sensitivity of the input Instead, the G: parameter allows you to compensate for externally-applied Gain from a preamp or attenuator, for example. It also allows correction for the differing undocumented sensitivities of various Sound Blaster models. When you switch between them via the Input item of the Board menu , the range calibration will change to match.

Note, however, that all inputs are assumed to have the same units, which you can change via the main User Units Name control. The G: parameter must be followed by a letter to indicate the input it applies to, followed by the sensitivity value. For example, SB ADC G:M The Range may be changed via the R: parameter or the board menu Range control, and the sensitivity will be scaled appropriately.

See the Calibration section for details on setting the G: value for ranges other than 0. These are the same letter codes that can be used with the C: Channel parameter.

The value that follows the input letter may be either a normal decimal value or may use "European" notation , with the units prefix replacing the decimal. Otherwise, this is case-sensitive: 'm' is 'milli' and 'M' is 'Mega', for instance.

Neither the integer nor fraction part of the entry may exceed If no fraction part is desired, it may be omitted completely. The following are all valid entries: SB ADC G:m12u ; ADC G:L ADC G:d0f ; 0.

The rest will remain at default values, which are The values entered this way have no effect on which input is selected at startup Note that the G:An option to change All inputs except Mic is handy for compensation of undocumented sensitivity differences of Sound Blaster models.

The Calibration section describes how to measure the sensitivity of your particular board. If your board differs from this calibration by a small percentage such as if your crystal reference time-base is out of spec , you can modify the values reported to Daqarta.

You will need to make an accurate measurement of the actual sample rate for a given setting. This requires a frequency counter that you trust more than the crystal on the board. Ideally, it should have a "period" mode to measure the duration of a single cycle, since this typically gives higher resolution with audio frequencies.

The basic idea is to use STIM3 to generate a pure sine wave whose frequency is locked to the sample rate. Measuring the sine wave frequency then allows you to calculate the actual sample rate. Connect the Right output Line or Spkr to the input of the frequency counter, and also to the Line input for monitoring. If you use the Right Line input , make sure it's selected on the Board menu.

Move down to the Stimulus item in that menu and toggle it to StGen if it isn't already. Set the Right Output to dB or so initially, so the monitored level is not too big for the input. These are the reference values for the respective time-bases. Hit the R-key to go to RTime operation, which is needed to produce continuous tones. You should see a default Hz waveform on the trace. Hit the F-key and you will note that it does not fall exactly on a spectral line Hit the X-key to Xpand the trace for a closer view.

Now move down to the step value below and enter 2. This will force output frequencies to move in steps of 2 spectral lines, assuming point FFTs, or single lines for the default point FFTs which we are assuming here. Install updated programs to your Sound Blaster directory. INF if necessary.

If you choose to update the drivers in your Windows directory, the program will perform the following tasks: a. Remove all out-dated drivers from your Windows directory. Install updated drivers to your Windows directory. INI contains the correct name of the Sound Blaster driver s. LOG will be created in your Sound Blaster directory. You may use a text editor to view this file. Alternatively, you may follow the steps below: a. Change to your Sound Blaster directory. We refer to this as the "Sound Directory".

They are only required by: a. Make sure that the two drivers are installed properly if you wish to use the above software. If you are running applications in Windows or playing computer games that use their own sound driver, you do not need to install these two drivers. SYS using a text editor. SYS files. SYS file. Note - Please refer to the following section on how to optimize your memory with the low level drivers installed.

If your audio card comes with the Creative Advanced Signal Processor, the installation program will add the following statement before the two low level drivers. You will need this driver for your DOS and Windows applications. Without it, your audio card will not be able to support the hardware audio compression and other additional software like Text-to-Speech offered by Creative separately. In view of that, these drivers are designed to be able to load into high memory. SYS, you can optimize your memory usage in one of the following ways.

If you are using Microsoft DOS 6. If you have a memory manager like QEMM or MAX, please refer to their respective user manuals on how to optimize the memory and load the drivers to the high memory. With multiple boot sessions, you can boot up the system with the low level device drivers installed only when you need it.

In situations where you don't require the low level drivers, your system will not have the drivers loaded into memory.