VOGONS


First post, by Artex

User metadata
Rank l33t
Rank
l33t

I'm working on a new build this week and am having a hell of a time getting my Reveal Sound FX 32 card working with Windows 3.11. For those that don't know, this is basically an ISA-based Ensoniq SoundScape S-2000 with 2MB of midi sample ROM and 3 CD-ROM interfaces. This particular rev has a tone control chip as well.

It uses wave port 534 by default (set via jumper), MIDI port 330 and IRQ 7 for the MIDI port (yes, it does require a MIDI IRQ which sux!). It also uses Sound Blaster emulation using IRQ 7 and DMA 1. Sometimes this 'emulation' works, sometimes its awful - all depends on the game.

The card uses a DOS program called SSINIT that resides in C:\SNDSCAPE directory and is called in the autoexec.bat. This program allows testing of the hardware for IRQ conflicts. Right now it's set to use:

WAVE PORT: 534
MIDI PORT: 330
MIDI IRQ: 7
SB IRQ: 5
SB DMA: 1

The hardware tests come out fine, indicating no conflicts (I disabled the LPT1 port in the BIOS which was using IRQ7). Both PCM and MIDI output work fine in DOS.

Upon entering Windows, I get a series of screens that keep barking about VSNDSCP.386 not being able to find the Ensoniq SoundScape IRQ. The odd thing is that the GM output works fine and I can play MIDIs though the bundled "Orchestrator" app. I just don't get any PCM/WAVE output.

I checked the System.ini to make sure the SSINIT values are present and correct. I've tried the Reveal SC600 drivers (bundled in two zips) as well as the Ensoniq driver executable from Vogons Drivers. I have no other cards in the system whatsoever, so I'm at a loss. I've tried pretty much all combinations of IRQs at this point - but no dice.

My Retro B:\ytes YouTube Channel & Retro Collection
LihnlZ.jpg

Reply 1 of 5, by Cloudschatze

User metadata
Rank Oldbie
Rank
Oldbie

A couple of references specific to the SC-600 state that the following may need to be added to the [sndscape.drv] section of the SYSTEM.INI file:

ISDVB=1

If it's already there, you might try removing it to see if that makes any difference.

Reply 2 of 5, by Artex

User metadata
Rank l33t
Rank
l33t
Cloudschatze wrote:

A couple of references specific to the SC-600 state that the following may need to be added to the [sndscape.drv] section of the SYSTEM.INI file:

ISDVB=1

If it's already there, you might try removing it to see if that makes any difference.

Interesting, I believe mine's a rev 3 board (hand-written in marker) but I'll check this out. I know I've gotten my 'normal' Ensoniq SoundScape S-2000 working in Windows 3.x without issue.
http://driverzone.com/drivers/reveal/sc600/1308081a.htm

My Retro B:\ytes YouTube Channel & Retro Collection
LihnlZ.jpg

Reply 3 of 5, by Artex

User metadata
Rank l33t
Rank
l33t

That worked!! Thanks!

My Retro B:\ytes YouTube Channel & Retro Collection
LihnlZ.jpg

Reply 4 of 5, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Hello Artex,

I own the Rev C of the card and am looking for the original sc600 driver disks. Could you be so kind to provide a link to these - I like to use the card for gaming on my reanimated sx25

Many thanks

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5428 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 5 of 5, by Geoman

User metadata
Rank Newbie
Rank
Newbie
Cloudschatze wrote on 2015-02-06, 04:57:

A couple of references specific to the SC-600 state that the following may need to be added to the [sndscape.drv] section of the SYSTEM.INI file:

ISDVB=1

If it's already there, you might try removing it to see if that makes any difference.

Sir you rescued me! I had exactly the same problem as Artex.

In the readme file inside s2k0526a.exe, it says:

Soundscape S-2000 Release Notes

Date: 05/22/95
Version: 1.30.03

[...]

**Windows Driver**
The Windows driver is now backwards compatible with early Soundscape boards
having the TDA8421 tone control chip. This backwards compatibility is activated
by the assignment IsDvb=Yes in the [sndscape.drv] section of the SYSTEM.INI
file.

"IsDvb=Yes" didn't have any effect at all - the error persisted.

Your command "ISDVB=1" did indeed the trick!

Thank you!!

IBM Aptiva 2168-931