VOGONS


First post, by FesterBlatz

User metadata
Rank Member
Rank
Member

Greetings! Long time lurker, first time poster...

I'm in the process of building a 486 for the sole purpose of playing some old DOS games I enjoyed back in the 80-90s. I've based it on the infamous M912 VLB motherboard (mine has real L2 cache) with an 486DX4-100 WriteBack CPU, and Western Digital VLB video board. One key ingredient it's been missing is my favorite ISA sound card, the Ensoniq Soundscape. I was especially proud to run a Soundscape Elite back in the 90s since I live close to where they were headquartered in Malvern, Pennsylvania.

To hold me over while I struggle to find one, I purchased the easier to find OEM "Opus" flavor on Ebay thinking it should do the trick for now. Unfortunately, it seems that without Plug n Play BIOS support it's a no-go. In brief, to try and get it working I downloaded the Soundscape DOS driver ZIP from the Vogons drivers archives, configured the windows.ini and soundscape.ini files to match what I believe to be the correct settings for an Opus including specifying the sndscape.co3 "codefile", but SSINIT refuses to acknowledge the presence of the card.

I assume if I had used a motherboard with PnP support it would assign the necessary resources and everything would work fine.

I've attached a picture of the error, SSINIT claims it doesn't see the card at the port I've configured it for. Since the BIOS isn't configuring the card for me, I'm pretty sure that's the problem...

My question is, considering this is a DOS-only machine, is anyone aware of some kind of Plug n Play BIOS extension or utility I can run that will configure the card at boot-up, similar to the way Creative's CTCU tool does for their PnP Sound Blasters? Or better yet, did Ensoniq create their own similar tool that I have somehow overlooked?

Thanks!!
Dieter

IMG_1311.JPG
Filename
IMG_1311.JPG
File size
1.63 MiB
Views
1445 views
File comment
Ensoniq Opus SSINIT error
File license
Fair use/fair dealing exception

Reply 1 of 10, by Whiskey

User metadata
Rank Member
Rank
Member

Hi FesterBlatz (SQ3 YEA!), I did a little digging around for you and found this useful guide for your card/problem. http://permalink.gmane.org/gmane.comp.emulato … s.general/16030

I don't have any particular experience with this card, but I also had a similar problem with a SB16 Pnp (partly PnP as still required Jumpers to be changed), from what I've read the Opus has a couple of Address Jumpers on the board too. The guide by John Hupp describes the process of using SSINIT to test the hardware addresses and the states of the jumpers.

Hope this at least sets you off in the right direction. Good luck Dieter!

Will.

I stream retro games every wednesday here & I dump the recordings here

Reply 2 of 10, by FesterBlatz

User metadata
Rank Member
Rank
Member

Thanks Will!!

Unfortunately the problem turned out to be a damaged card. I noticed whenever I had it installed my system would become really unstable, and after looking the card over a little better I discovered at least a dozen pins on the OPUS chip were actually popped free from their pads and the whole chip shifted over a fraction of a mm. There were also a few loose pins on the DRAM chips next toe the OPUS. I think the PCB had been twisted pretty severely at one point to cause all those pins to come loose. I carefully re-flowed the OPUS, DRAM, Patch ROM, and 68000 MCU which got the card to initialize and work somewhat, but the wave-table output sounded really garbled especially when emulating MT-32. Space Quest 3 and Heros Quest (QFG1) used to sound awesome on my old Soundscape...not at all like this thing did. So I pushed my luck a little harder and tried re-flowing the OPUS pins once more but now the card fails to initialize again....so I think it's done for.

I may mount the patch ROM on a SO 8/16Mbit ROM breakout board for my device programmer and dump the patch ROM for archival purposes. I wish I could find a dump of a 2MB ROM to try and upgrade one of the 1MB boards to 2MB with a cheap 29F016 FLASH ROM, but I doubt it would be that simple...

Anyway, so the quest for a Soundscape continues...

Reply 3 of 10, by jesolo

User metadata
Rank l33t
Rank
l33t

The Soundscape cannot emulate an MT-32 effectively.

Firstly, games like Space Quest 3 sends sysex commands to the MT-32 to load custom patches (which the Soundscape will just ignore).
Secondly, games like Space Quest 3 requires an intelligent mode MPU-401 MIDI interface. The Soundscape only had the UART mode MPU-401 interface. However, you can use SoftMPU to overcome this problem to a large extent. I also recall some Ensoniq cards being able to "trick" the system into thinking that it had an intelligent mode MPU-401 MIDI interface, but I'll have to look it up again.

The games you mentioned had no direct support for the Ensoniq Soundscape. All the card is doing is to emulate a Sound Blaster 2.0 and/or Adlib sound card (if memory serves).

Reply 4 of 10, by boxpressed

User metadata
Rank Oldbie
Rank
Oldbie

There's a combo sound card/modem called the NEC Harmony. I've never owned one, but they're quite cheap on eBay. I spotted an Ensoniq Opus chip on the board along with a 1MB patchset ROM. Not sure about which drivers to use.

Reply 5 of 10, by yawetaG

User metadata
Rank Oldbie
Rank
Oldbie

I think I've mentioned this elsewhere, but PnP cards that are compatible with older non-PnP systems and OSes can usually be configured using a special setup utility that sets the IRQ etc. and stores these settings directly on the card. Such an utility is usually provided on a floppy with the card. Then, you use the DOS/Windows drivers as usual, eventually specifying the IRQ etc. if the drivers need that.

Reply 6 of 10, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Hello everyone,
I'm not sure if this also works for SQ3, but there's a patch for MT-32/SB-MIDI.
This way, you don't require any MPU-401 interface for certain Sierra titles.

http://sierrahelp.com/Utilities/SoundUtilities.html

"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 7 of 10, by FesterBlatz

User metadata
Rank Member
Rank
Member

The Soundscape boards equipped with an embedded 68000 family MPU on them will emulate an intelligent mode MPU-401 by responding to SYSEX commends with an ACK. Ensoniq designed the Soundscape with MT-32 emulation in mind and provided dedicated samples in the patch ROM for the MT-32 mode which can be enabled in the on-board MCU from a DOS executable (MT32.exe ON/OFF). I have personally played a number of Sierra titles using this MT-32 emulation on a Soundscape S-2000 and they didn't sound half bad. Certainly not true to real MT-32 form, especially considering it lacked the uploaded sound effects, but still perfectly enjoyable.

Once I repaired my damaged Soundscape PnP/"OPUS" referred to in my initial post to a somewhat working state, like the S-2000 I used to own it too responds to SYSEX commands and satisfies the Sierra MT-32 driver. Unfortunately, MT-32 titles don't sound nearly as pleasant as my old S-2000 did back in the 90s. The question is, is this because of the damaged/missing solder pad on the OPUS chip, or because the OPUS is a cost-reduced card with a smaller patch ROM and handicapped MT-32 emulation capabilities? Since General MIDI on it works perfectly, I fear it may be the latter.

I will soon find out since I now have a second OPUS on the way. I also purchased one of the NEC Harmony OPUS/Modem combos boxdepressed referred to, the eBay seller accepted an $8 offer so it was very inexpensive. I found a zip file provided by NEC for the board, and it appears to use the same initialization utilities as the purebred Soundcapes so it will be interesting to see how it works.

Hopefully someday I'll find someone willing to sell an S-2000, I dearly miss mine.

Cheers!

jesolo wrote:
The Soundscape cannot emulate an MT-32 effectively. […]
Show full quote

The Soundscape cannot emulate an MT-32 effectively.

Firstly, games like Space Quest 3 sends sysex commands to the MT-32 to load custom patches (which the Soundscape will just ignore).
Secondly, games like Space Quest 3 requires an intelligent mode MPU-401 MIDI interface. The Soundscape only had the UART mode MPU-401 interface. However, you can use SoftMPU to overcome this problem to a large extent. I also recall some Ensoniq cards being able to "trick" the system into thinking that it had an intelligent mode MPU-401 MIDI interface, but I'll have to look it up again.

The games you mentioned had no direct support for the Ensoniq Soundscape. All the card is doing is to emulate a Sound Blaster 2.0 and/or Adlib sound card (if memory serves).

Reply 8 of 10, by Whiskey

User metadata
Rank Member
Rank
Member

Glad to hear you had some success with fixing your OPUS Dieter!
I think your hypothesis about the Opus being a cost reduced relative is more than likely to be true. As with many other manufactures at the time it was certainly a trend to make and sell a cut-down card on the back of a previously well received one. Be sure to post your findings when your NEC Harmony OPUS arrives, I have to say I find this all very intriguing.

Cheers W.

I stream retro games every wednesday here & I dump the recordings here

Reply 9 of 10, by FesterBlatz

User metadata
Rank Member
Rank
Member

Well, I have an update for this topic. A few things have happened since my last post...

Firstly, I received my second OPUS board and wouldn't you know it, it had the same problem as the first with one of the "corners" of the OPUS chip coming loose from the PCB! Fortunately, unlike the first OPUS none of the pins were bent, only lifted from their pads. Either Ensoniq was having PCB assembly quality issues or I experienced one heck of a coincidence! In any event, after a quick dab of reflow flux and a few minutes with a fine-tip soldering iron the OPUS is as good as new again.

Just as I feared it behaves with early Sierra MT-32 titles exactly the same as the first OPUS that came with the damaged pin, so the damage was inconsequential.

Since then I managed to purchase a pair of Soundscapes from an AmiBay member in the Netherlands. One of them is the Soundscape-II (S2016-II-A) which is basically a Soundscape Elite without the ESP board and a "1M2" patch ROM. The other is an SPEA V7 media fx which is a clone of the original S-2000 with the full 2M patch ROM. I just tested both of these boards with the early Sierra titles and they both sound pretty similar to my OPUS...not good.

So I must have completely imagined Hero's Quest and Space Quest 3 sounding half decent on my old Gateway OEM Soundscape S-2000. The only other explanation I can think of is perhaps older versions of the on-board M68000 codefile loaded by SSINIT.EXE processor may have handled MT-32 emulation more eloquently but was later scarified for better Soundblaster 2.0 emulation instead...or something along those lines.

Anyway, I will try to track down older versions of the S-2000 DOS utils/codefiles to see if it makes a difference but at this point I think I'm going to stick with using MUNT on my RPI3 to emulate an MT-32 when playing classic Sierra titles...

Reply 10 of 10, by moturimi1

User metadata
Rank Member
Rank
Member
FesterBlatz wrote:
Thanks Will!! […]
Show full quote

Thanks Will!!

Unfortunately the problem turned out to be a damaged card. I noticed whenever I had it installed my system would become really unstable, and after looking the card over a little better I discovered at least a dozen pins on the OPUS chip were actually popped free from their pads and the whole chip shifted over a fraction of a mm. There were also a few loose pins on the DRAM chips next toe the OPUS. I think the PCB had been twisted pretty severely at one point to cause all those pins to come loose. I carefully re-flowed the OPUS, DRAM, Patch ROM, and 68000 MCU which got the card to initialize and work somewhat, but the wave-table output sounded really garbled especially when emulating MT-32. Space Quest 3 and Heros Quest (QFG1) used to sound awesome on my old Soundscape...not at all like this thing did. So I pushed my luck a little harder and tried re-flowing the OPUS pins once more but now the card fails to initialize again....so I think it's done for.

I may mount the patch ROM on a SO 8/16Mbit ROM breakout board for my device programmer and dump the patch ROM for archival purposes. I wish I could find a dump of a 2MB ROM to try and upgrade one of the 1MB boards to 2MB with a cheap 29F016 FLASH ROM, but I doubt it would be that simple...

Anyway, so the quest for a Soundscape continues...

Hi do you still work on that topic? I extracted the Ensoniq 2MB ROM.
Currently I am also thinking about extracting all available ROMs. (2M, 1M, 1M2, I doubt that I will extract the Elite ROM, afraid of breaking it)
If you are interested, I can send you the ROM.
Unfortunately my TL866 programmer does not programm the 29F016, but it can read it with an adaptor. But I will us a 27C016 instead. This one sould work. I will check that when I receive a Soundscape with "socket" ROM Chip next week.
Is it possible for you to dump and provide the 1M (8MBit Chip?)