VOGONS


First post, by dosquest

User metadata
Rank Oldbie
Rank
Oldbie

Okay, I have a SB16 and I set it up for my windows 98 build and it worked great, so to test it I loaded the sb16 demo to test the channels and so on. Well, when it gets to the 16bit digitized sound part (1:20 in the youtube vid) I don't hear the footsteps sound I should be hearing (see video of how it should sound) http://www.youtube.com/watch?v=eOr6VUjGA9A I downloaded the files from the provided link in the video description and put it on a floppie and copied it to the c: drive of my windows 98 build (c:\sb\mmplay to be exact.)

Reply 1 of 11, by rfnagel

User metadata
Rank Oldbie
Rank
Oldbie

This is just a guess, but after having a look at the ZIP from the link in the dez for the video ( http://tinyurl.com/sb16demo ), it appears to be a file that I uploaded here at Vogons some time ago.

Anyhoo, that ZIP file contains several versions of the "CT-VOICE" driver file (CT-VOICE.DRV), as well as several versions of the "FOOTSTEP" VOC sound file (FOOTSTEP.VOC).

The different versions of the files are:

For "FOOTSTEP.VOC":
FOOTSTEP.16
FOOTSTEP.SB

For "CT-VOICE.DRV":
CT-VOICE.16
CT-VOICE.PRO
CT-VOICE.SB

In the ZIP file, the existing "FOOTSTEP.VOC" is copy of the "FOOTSTEP.SB" file (which is 8-bit), while the existing "CT-VOICE.DRV" in the ZIP is a copy of the "CT-VOICE.SB" file (which is the CT-VOICE driver for the original standard non-Pro Sound Blaster).

It's been a while, but IIRC the reason that I packaged this up like this was for use in DOSBox (to make it the most compatible with a default DOSBox installation, so's the demo would run properly), and the MMPLAY package (with the specific files copied to FOOTSTEP.VOC and CT-VOICE.DRV) was set up for a standard Sound Blaster (non-Pro version) with 8-bit sound.

I'm thinking that if you copy:

FOOTSTEP.16 to FOOTSTEP.VOC

...and copy:

CT-VOICE.16 to CT-VOICE.DRV

...overwriting the original files, it might just work for ya 😀

Like that, that's how the _original_ MMPLAY install was for the SB-16.

Rich ¥Weeds¥ Nagel
http://www.richnagel.net

Reply 5 of 11, by rfnagel

User metadata
Rank Oldbie
Rank
Oldbie
dosquest wrote:

Wait so re name or replace
FOOTSTEP.16 to FOOTSTEP.VOC
and CT-VOICE.16 to CT-VOICE.DRV

Correct 😀

...and a bit of further explanation/instruction for *other* Sound Blaster cards:

For a standard Sound Blaster (8-bit non-Pro):

Copy CT-VOICE.SB to CT-VOICE.DRV, and FOOTSTEP.SB to FOOTSTEP.VOC.

For a Sound Blaster Pro (8-bit):

Copy CT-VOICE.PRO to CT-VOICE.DRV, and FOOTSTEP.SB to FOOTSTEP.VOC.

For a Sound Blaster 16 (16-bit) (just like you described above):

Copy CT-VOICE.16 to CT-VOICE.DRV, and FOOTSTEP.16 to FOOTSTEP.VOC.

Rich ¥Weeds¥ Nagel
http://www.richnagel.net

Reply 8 of 11, by thefixer

User metadata
Rank Newbie
Rank
Newbie
Filename
mmplay.zip
File size
539.32 KiB
Downloads
88 downloads
File comment
IUC Innocent Until Caught Sound Blaster soundblaster sb drivers containing various CT-VOICE.DRV to try as originally submitted by user: rfnagel
File license
Fair use/fair dealing exception
rfnagel wrote:
Correct :) […]
Show full quote
dosquest wrote:

FOOTSTEP.16 to FOOTSTEP.VOC
and CT-VOICE.16 to CT-VOICE.DRV

Correct 😀

...and a bit of further explanation/instruction for *other* Sound Blaster cards:

For a standard Sound Blaster (8-bit non-Pro):

Copy CT-VOICE.SB to CT-VOICE.DRV, and FOOTSTEP.SB to FOOTSTEP.VOC.

For a Sound Blaster Pro (8-bit):

Copy CT-VOICE.PRO to CT-VOICE.DRV, and FOOTSTEP.SB to FOOTSTEP.VOC.

For a Sound Blaster 16 (16-bit) (just like you described above):

Copy CT-VOICE.16 to CT-VOICE.DRV, and FOOTSTEP.16 to FOOTSTEP.VOC.

I found the page with the drivers you uploaded:

http://www.vogons.org/viewtopic.php?t=8634

Try as I might, I can only get 2 drivers to work:

CT-VOICE.DRV (5.1 kB or 5,108 bytes) for sbpro2
or this one I found
CT-VOICE.DRV (3.9 kB or 3,894 bytes) for sb1 and sb2,
see my guide here:

http://www.vogons.org/viewtopic.php?f=33&t=10364&p=408787#p408787

The game doesn't respond to sb16 or the footsteps driver, and believe me I've tried all the .conf settings and renaming, etc.

With the 3.9 kB and 5.1 kB drivers the effects do work, but they are sparse and seem incomplete. The game's readme file said to also "SET BLASTER=" in the AUTOEXEC.BAT though I never got this mystery feature to work. I wonder if anyone has ever, through the past 25 years got the sound to work right with ALL the effects.....
--------
Anyway, here's a copy of your driver pack zip file

Reply 9 of 11, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

Some old Demos came with CT-Voice.drv but they don't work with my SB16.
If I put the SB16 CT-Voice.drv in the Demodirectory I also get an error. (could not load ct-voice.drv) name is correct.

http://nerdlypleasures.blogspot.de/2013/12/so … -dos-games.html

Retro-Gamer 😀PowerMac 6100-66/Houdini 486/66 - G4 Cube 450/Rage128pro OS9.0.1 - Macintosh LC/Apple IIe Card OS6.0.8 - Acorn A4000 Archimedes - Unisys CWD 486/66 + Aztech Washington

Reply 10 of 11, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Thanks for the link! But can anyone explain what the differences between sound.com and sbfmdrv.com are ?
I mean in terms of features and compatibility. Until now I used sound.com (Adlib) for everything.
Is there any benefit in using the Sound Blaster version ?

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 11 of 11, by Jepael

User metadata
Rank Oldbie
Rank
Oldbie
Jo22 wrote:

Thanks for the link! But can anyone explain what the differences between sound.com and sbfmdrv.com are ?
I mean in terms of features and compatibility. Until now I used sound.com (Adlib) for everything.
Is there any benefit in using the Sound Blaster version ?

I don't think they are compatible or interchangeable - either a game/program can use the Adlib sound.com driver interface or Creative sbfmdrv.com driver interface but not both.

Otherwise I don't know exact details, but each driver can be used to such things like loading instruments and playing notes, but most likely each driver require the instrument data in their own format.