Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Getting sound blaster 16 to work in DOS on 98SE box.

- - - - -

  • Please log in to reply
18 replies to this topic

#1
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08
Hey all, my first post here.

Down to business. I've installed my ct4740 pci sound blaster 16 in my windows 98 machine, installed the drivers, and it works perfectly under the 98 interface. However, I'll be playing a bunch of games in dos, and I need to figure out how to get sound working.

I suspect I need to load dos drivers for the soundcard, since thusfar, no sound at all is coming out of the speakers in dos.

I've played around with autoexec.bat extensively, but I can't seem to find any resources or people that are intimate with its workings. Nothing I've tried so far has gotten any sound to come out at all. I've tried many set blaster= settings.

I need a page that covers autoexec.bat *thoroughly*, and I need to figure out how to edit autoexec.bat and config.sys properly to get sound playing. "http://www.computerh...ope.com/ac.htm" is not a thorough resource, and leaves a lot of commands and parameters out.

Upon further inspection, it would appear that my cd drive isn't loading in dos either. I suspect config.sys and autoexec.bat are completely screwed.

All help is greatly appreciated. :)
-Yeti

Edited by yetiamchosen, 13 April 2008 - 06:53 PM.



How to remove advertisement from MSFN

#2
idisjunction

idisjunction

    Newbie

  • Member
  • 37 posts
  • Joined 01-May 07
You might need to configure your BLASTER variable. Boot from a plain DOS disk with a diagnostic program on it, and find out what IRQ and DMA your card uses. Then edit AUTOEXEC.BAT to say something like

SET BLASTER=A220 I5 D3 T6

"A" is the address range, almost always 220. "I" is the IRQ. "D" is the DMA channel. "T" is the type of card, usually at least 3 or higher should work. I would suggest configuring the BIOS so that your card doesn't use an interrupt higher than 5. Otherwise, some games might not sound right.

Edited by idisjunction, 13 April 2008 - 07:28 PM.


#3
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08

You might need to configure your BLASTER variable. Boot from a plain DOS disk with a diagnostic program on it, and find out what IRQ and DMA your card uses. Then edit AUTOEXEC.BAT to say something like

SET BLASTER=A220 I5 D3 T6


Port is 220, IRQ is 7, DMA is 1. The code I'm currently using is SET BLASTER=A220 I7 D1 H7 P330 T6, though I've tried it without the H7 and P330 as well. Just going off sample autoexec.bat codes. I can't find anything really informative that tells me what it SHOULD be, just a lot of examples.

And I still need to tell it where to find the dos drivers. Help?

Also: How do I configure the BIOS so that the interrupt is 5 rather than 7? I took a quick look through, but I didn't see a place to change that.

Edited by yetiamchosen, 13 April 2008 - 07:32 PM.


#4
idisjunction

idisjunction

    Newbie

  • Member
  • 37 posts
  • Joined 01-May 07

Port is 220, IRQ is 7, DMA is 1. The code I'm currently using is SET BLASTER=A220 I7 D1 H7 P330 T6, though I've tried it without the H7 and P330 as well. Just going off sample autoexec.bat codes. I can't find anything really informative that tells me what it SHOULD be, just a lot of examples.

Try configuring it so that it uses a lower IRQ, like 5. Some games don't like such high IRQs. The setting SHOULD be whatever your card follows.

And I still need to tell it where to find the dos drivers. Help?


A true Sound Blaster doesn't need drivers, unless it is a PCI card.

#5
idisjunction

idisjunction

    Newbie

  • Member
  • 37 posts
  • Joined 01-May 07

Also: How do I configure the BIOS so that the interrupt is 5 rather than 7? I took a quick look through, but I didn't see a place to change that.


It should be under something "IRQ reservation." The exact settings vary from computer to computer. Just reserve IRQ 7, so that nothing can claim it. The card should then claim IRQ 5.

#6
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08

A true Sound Blaster doesn't need drivers, unless it is a PCI card.


I said that it was a pci card in my first post.

It should be under something "IRQ reservation." The exact settings vary from computer to computer. Just reserve IRQ 7, so that nothing can claim it. The card should then claim IRQ 5.


I just finished looking through every setting in the bios, nothing about IRQ reservation. :(

I've seen bits and pieces of info around the net about needing to enable dos drivers. Perhaps that's misinformation. Still trying to get this thing to put sound out of the speakers...

Btw, thanks for your help, idisjunction, I appreciate it.

Edited by yetiamchosen, 13 April 2008 - 07:53 PM.


#7
idisjunction

idisjunction

    Newbie

  • Member
  • 37 posts
  • Joined 01-May 07

A true Sound Blaster doesn't need drivers, unless it is a PCI card.


I said that it was a pci card in my first post.


Sorry, I missed that. This driver should work, if I am not mistaken:

Driver - Site doesn't allow hotlinking.

More info can be found here:

http://easymamecab.m...ml/snddosdr.htm

Edited by idisjunction, 13 April 2008 - 08:47 PM.


#8
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08
Looking into it... Thanks again for all your excellent help. Watch this spot.
-Yeti

#9
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08
Ok, I've installed the driver, and now (thank god) the card is recognized in dos. I'm using a sound utility that comes with TIE Fighter to test the sound. When I tell it to detect sound, it detects the SB16, detects port 220, irq 5, and dma 1, but when it tries to play sound, it goes through the motions, but nothing comes out of the speakers. Before, it wouldn't detect anything at all, so we're definitely making progress. When I tell windows to detect the sound card, it goes to irq 7. I don't know why windows is picking 7 and dos is picking 5, but I'm assuming dos is running off of the SET BLASTER= I5 variable and windows is going off of something else entirely.

So now the card is recognizing, everything is running smoothly, the only thing left is... actually making the speakers do something?

Thanks for the help so far!

Also: Important to note, the readme file for the drivers says that your sound blaster pci card cannot use irq 5. At the same time, it gives you a new autoexec.bat file with the irq set to 5. Odd? Hit me back.

Edited by yetiamchosen, 13 April 2008 - 08:54 PM.


#10
idisjunction

idisjunction

    Newbie

  • Member
  • 37 posts
  • Joined 01-May 07
Windows detects IRQ 7 because that is what the card actually runs at. The driver for DOS emulates a Sound Blaster at IRQ 5. Thats why there was a discrepancy.

I don't know why the sound isn't playing properly. I had a similar problem when exiting from Windows into DOS: sound would play, but it would be just random noise. I think Windows may be doing a TSR that is interfering. If you can, see if you can start DOS without launching Windows first.

#11
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08
I've been running DOS upon initial boot, without windows, from the beginning.

Any idea why it says that the card can't run at irq 5, yet supplies an autoexec.bat with i5 as the given variable?

Hit me up.

Edited by yetiamchosen, 13 April 2008 - 09:14 PM.


#12
Glenn9999

Glenn9999

    Senior Member

  • Member
  • PipPipPipPip
  • 674 posts
  • Joined 23-April 07
  • OS:Windows 8 x64
  • Country: Country Flag
FWIW, I don't have SB16 config lines, but I have the SB64 Awe's lines still in my DOS CD...might be worth it to check against - most of the card initialization remained the same:

CONFIG.SYS
DEVICE=A:\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
DEVICE=A:\CTMMSYS.SYS

AUTOEXEC.BAT
SET BLASTER=A220 I7 D1 H5 P330 T6
SET SOUND=C:\SB16
SET MIDI=SYNTH:1 MAP:E
CTCM
AWEUTIL /S
MIXERSET /P /Q
SBRESET

Don't get too hung up on SET BLASTER, since it is primarily there for backwards compatibility from the ISA days.

#13
BenoitRen

BenoitRen

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 988 posts
  • Joined 21-October 06
  • OS:95
  • Country: Country Flag
I had an adventure getting sound to work 100% properly in DOS about a year ago. I used to have the configuration panel program that detects the settings. I looked for it on the web, and uploaded it.

The SoundBlaster having an IRQ of 7 is not much of a problem for 95% of games. However, there are some that have the IRQ of 5 hardcoded in their program. Changing the IRQ through the Configuration Panel of Windows doesn't work too well, especially if you have devices like a printer and network card also installed. In my case the network card was hogging IRQ 5, and I found that the best solution was to just put it in a different PCI slot.

You haven't got the drivers with the SoundBlaster card? There are drivers for Windows and DOS, even though Windows has drivers for such cards itself. On exit to DOS, Creative's Plug & Play Manager should kick in. If you boot directly to DOS, you have to activate it manually. This is usually ctcm.exe, and its settings are stored in ctpnp.cfg. Both are in the Windows directory.
Using Windows 95 OSR 2.5
SeaMonkey - surfing the net has never been so suite
Posted ImageLight Blue Ribbon Campaign for Freedom of Skin

#14
willperk

willperk
  • Member
  • 6 posts
  • Joined 19-December 07

- - - - - - -

I've played around with autoexec.bat extensively, but I can't seem to find any resources or people that are intimate with its workings. Nothing I've tried so far has gotten any sound to come out at all. I've tried many set blaster= settings.

I need a page that covers autoexec.bat *thoroughly*, and I need to figure out how to edit autoexec.bat and config.sys properly to get sound playing. "http://www.computerh...ope.com/ac.htm" is not a thorough resource, and leaves a lot of commands and parameters out.

Upon further inspection, it would appear that my cd drive isn't loading in dos either. I suspect config.sys and autoexec.bat are completely screwed.

All help is greatly appreciated. :)
-Yeti

==================
Yeti -
Do you have the Creative "Readne.txt" file that came with your application CD?
There are a number of instructions of operations to perform in order to get sound and the CD working in DOS mode.
If you don't have the 'Reademe' file, I can post it here ...... it might be of some help.
I, too, have a Creative 16 (Vibra 16C) audio card, but I'm not a gamer and have never had any need to have sound in the dos mode.
-- willperk

Edited by willperk, 14 April 2008 - 12:53 PM.


#15
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08
BenoitRen -- Thanks for your help. I've got the drivers, they just don't seem to be working properly. As far as getting it activated from dos, unfortunately ctcm.exe in the windows directory. It looks like one of my usb ports was hogging IRQ 5, though I've disabled it now, and as far as I know that shouldn't even be active in dos anyway.

Oddly, I've discovered that the sound seems to work (though I'm not yet sure how well) when I select 'exit to ms dos', just not when I boot to dos natively (which is what I need it to do).

willperk, thanks for your suggestions. Unfortunately, both the readme file and the pdf file that came on the driver cd had no instructions at all on how to get the card working in dos. My best progress so far has been using the sound blaster 16 pci drivers for dos in sbpci.zip linked by idisjunction here: http://www.msfn.org/.....les/SBPCI.zip

The card recognizes and activates in natively booted dos, though it seems to claim an irq of 3 (oddly). When detection tools are run, they detect it running at irq 5, but no sound actually comes out of the speakers.

All help is appreciated.

Edited by yetiamchosen, 14 April 2008 - 02:57 PM.


#16
willperk

willperk
  • Member
  • 6 posts
  • Joined 19-December 07

- - - - - - - - ~

willperk, thanks for your suggestions. Unfortunately, both the readme file and the pdf file that came on the driver cd had no instructions at all on how to get the card working in dos. My best progress so far has been using the sound blaster 16 pci drivers for dos in sbpci.zip linked by idisjunction here: http://www.msfn.org/.....les/SBPCI.zip

The card recognizes and activates in natively booted dos, though it seems to claim an irq of 3 (oddly). When detection tools are run, they detect it running at irq 5, but no sound actually comes out of the speakers.

All help is appreciated.


Here is the "Readme" file from my 'C > Program Files > Creative > CTSND' folder .....
Perhaps it might be of some help .......
-- willperk

Sound Blaster 16 Readme File
============================

This file contains additional information to supplement the manual.
Please read all the sections before you proceed with the installation.

This file contains the following sections:

1. Installation
2. Uninstallation
3. DOS Environment settings
4. DOS Audio Driver Support under Windows 95 DOS Box
5. Using CREATIVE IDE CD-ROM drive in MS-DOS Mode
6. BLASTER settings under MS-DOS Mode
7. Full-Duplex Constraints
8. Online Documentation
9. Acknowledgments


1. INSTALLATION

The full installation option requires about 6 MBytes of hard disk
space for the program files and an additional 2 MBytes for working space.
You might need more if your drive is in compressed form.


2. UNINSTALLATION

Before uninstalling the software package, ensure that all Sound
Blaster 16 applications are closed. Any Sound Blaster 16 application
that is running while uninstallation is in progress will not be deleted
Also, files that are added to the Sound Blaster 16 directory after
the initial software installation will not be deleted by the
uninstallation process. You will have to manually delete these files
after the uninstallation process is completed.

Some of the files in the Windows directory can be shared by other
applications. The uninstallation will prompt you when it tries to
delete these files. You should choose not to delete the files unless
you are very sure that the files are no longer used by Windows.


3. DOS ENVIRONMENT SETTINGS

Some of the existing DOS programs require the presence of MIDI and
SOUND environments in order for them to work. The Setup program will
add the SET MIDI and SET SOUND environment lines at the beginning of
the AUTOEXEC.BAT file.


4. DOS AUDIO DRIVER SUPPORT UNDER WINDOWS 95 DOS BOX

Some of the DOS applications are developed with Creative's Sound
Blaster Developer Kit. These applications require the low-level
DOS audio device drivers to be loaded. To load the DOS audio
drivers, you need to add the following lines to the CONFIG.SYS file:

DEVICE=<C:\dir>\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 /WIN95
DEVICE=<C:\dir>\DRV\CTMMSYS.SYS

Remarks:

a. <C:\dir> is the sound directory where the audio software is located.

b. The /BLASTER parameter specifies the Sound Blaster base I/O port
address (A), interrupt request line (I), low 8-bit DMA channel (D)
and high 16-bit DMA channel (H).

c. The settings in the /BLASTER parameter must tally with the actual
settings allocated by Windows 95. To find out the actual settings,
go into Windows 95 DOS box, and type SET and press <Enter> at the
DOS prompt. You will see one of the lines displayed is:

BLASTER=A220 I5 D1 H5 P330 T6

The values after the A, I, D and H are the actual settings to be
used for the /BLASTER parameter.

To help you set up the DOS audio drivers, we have prepared a text
file CONFIG.TXT in the sound directory. This text file contains
the above lines to specify the DOS audio drivers. The sound
directory in the text file had been updated by the installation
program. You just need to update the /BLASTER parameter and copy
the lines into the CONFIG.SYS file.


5. USING CREATIVE IDE CD-ROM DRIVE UNDER MS-DOS MODE

When you open an MS-DOS Mode session, the system will close all other
active Windows-based or DOS-based programs. You can return to
Windows 95 by typing exit. There are two ways that you can do to open
an MS-DOS Mode session:

- Shutdown the system and choose the "Restart the computer in
MS-DOS Mode" option.

or

- Change your MS-DOS session properties by checking the MS-DOS mode box
under the Advanced Program Settings. You can specify whether you want
to use the current MS-DOS configuration, or specify a new MS-DOS
configuration.

If you connect Creative IDE CD-ROM drive to the IDE interface that comes
with your card, you need to do the following steps to make your CD-ROM
drive work under MS-DOS Mode:

5.1 Shutdown and restart the computer in MS-DOS Mode

You need to add the following lines inside the DOSSTART.BAT :

<C:\dir>\CTLOAD <C:\dir>\DRV\SBIDE.SYS /D:MSCD001 /V /P:1E8,11,3EE
<C:\win95dir>\COMMAND\MSCDEX /D:MSCD001 /V /M:8

NOTES:

a. DOSSTART.BAT is a batch file in the Windows directory.
It is executed each time you restart in MS-DOS Mode.

b. <C:\dir> is the sound directory where the audio software is located.

c. <C:\win95dir> is the Windows 95 directory.

To help you set up the DOS audio drivers, we have prepared a
text file DOSSTART.TXT in the sound directory. This text file
contains the above lines to specify the DOS CD-ROM drivers.
The sound directory in the text file has been updated by the
installation program. You don't need to change any of the parameters.

5.2 Changing MS-DOS session properties and selecting MS-DOS Mode with
current configuration

You need to do the same steps as above.

5.3 Changing MS-DOS session properties and selecting MS-DOS Mode with
new configuration

You need to add the following lines inside the new AUTOEXEC.BAT :

<C:\win95dir>\CTCM
<C:\dir>\CTLOAD <C:\dir>\DRV\SBIDE.SYS /D:MSCD001 /V /P:1E8,11,3EE
<C:\win95dir>\COMMAND\MSCDEX /D:MSCD001 /V /M:8

NOTES:

a. <C:\dir> is the sound directory where the audio software is located.

b. <C:\win95dir> is the Windows 95 directory.

c. Make sure that the settings in the /P parameter tally with the
actual settings allocated by Windows 95.


6. BLASTER settings under MS-DOS Mode

Whenever you change your Audio hardware configuration manually, the
BLASTER environment under MS-DOS Mode will only be valid after you reboot
the system once.

However, if you proceed to MS-DOS Mode without rebooting, you need to run
CTCM.EXE which is in your Windows directory. This program makes the
BLASTER environment tally with the actual hardware settings.


7. FULL-DUPLEX CONSTRAINTS

Your audio card supports full-duplex recording and playback. However, to
make full use of this feature, please make sure you observe the following
constraints:

a. Start only one session of simultaneous playback and recording.
b. Use the same sampling rate for both operations.
c. Preferably play back and record audio files which are in uncompressed
(that is, Pulse Code Modulation or PCM) wave format.
d. Reduce the sampling rate for both operations if your audio playback
and recording session is too slow.

NOTE: The Full-Duplex and DirectSound capabilities are mutually exclusive.
If you activate the full-duplex feature, the DirectSound capability
cannot be enabled. And vice versa.


8. ONLINE DOCUMENTATION

To help you get information on the applications in this package easily,
we have compiled a set of online documentation which can be accessed from
your audio card's program group. Just click the START button on your
Windows 95 taskbar. Select "Programs", followed by "Sound Blaster 16" and
then "User's Guide".


9. ACKNOWLEDGMENTS

MS-DOS, Windows 3.x and Windows 95 are trademarks of Microsoft Corporation.
All other products are trademarks or registered trademarks of their
respective owners.

********** E N D O F R E A D M E **********

#17
BenoitRen

BenoitRen

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 988 posts
  • Joined 21-October 06
  • OS:95
  • Country: Country Flag

As far as getting it activated from dos, unfortunately ctcm.exe in the windows directory.

You mean it isn't in there?

It looks like one of my usb ports was hogging IRQ 5, though I've disabled it now, and as far as I know that shouldn't even be active in dos anyway.

USB can be used in DOS. You just need drivers. :)

I'm not convinced that the drivers offered at the MAME site could work. A lot of unnecesary parameters and several batch programs. It's not that complicated on my end.

All you should need is the ctcm program, its configuration file, and possibly some files associated with it. The settings in autoexec.bat should reflect the settings of your card. There is no need to have extra files loaded via config.sys.

What exactly do you see when the sound card is supposedly being detected by DOS?
Using Windows 95 OSR 2.5
SeaMonkey - surfing the net has never been so suite
Posted ImageLight Blue Ribbon Campaign for Freedom of Skin

#18
yetiamchosen

yetiamchosen
  • Member
  • 8 posts
  • Joined 13-April 08
Yes, sorry, I meant that ctcm.exe isn't present. I don't think plug and play managers work for sb16 pci, do they? I think creative's pnp manager is only for their isa cards. Correct me if I'm wrong.

Dos recognizes it with this:

sound blaster pci 128 initialization driver, ver 5.23
copyright bla bla bla

fname: c:\dosdrv\sbpci.ini
SB PCI @ Port df00, IRQ 3
output mode is analog
initiliazation complete.

And then there's imuse, a tool from lucasarts that comes with tie fighter and autodetects the kind of card you have. After using iconjunction's drivers, it recognizes it properly as a sounblaster 16, etc, it just doesn't actually play anything. Without his drivers, it wouldn't recognize anything at all, muchless display the above message.

Thanks for the help, keep working on it!

#19
ShadeTreeLee

ShadeTreeLee

    Junior

  • Member
  • Pip
  • 82 posts
  • Joined 19-February 07
Once upon a time it helped my nephew to add this line to the [386Enh] section of his system.ini file.
DMABufferSize=64

Strangely Windows doesn't have a DMA buffer natively, one has to manually provide for it with the above line. Yet without the DMA buffer some hard drives use even UDMA just fine - it's only SoundBlaster that chokes without one set aside.

Any Joy?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users