[Is there gonna be a new feature for old windows games]

On 1/9/2018 at 9:41 AM, Zombeaver said:

I installed Shivers in Windows 3.1 and keep getting error about waveoutopen device already in use

I installed Shivers in Windows 3.1 and added the whole package in Launchbox's DOSBox.

I added the full path in win.ini so everything is loaded immediately when I double click on the game in DOSBox, however, i keep getting error about waveoutopen device already in use and that the game needs a wave driver in order to play it.

But if I load the game after from Win 3.1 - Program manager - Sierra - Shivers - sierraw.exe, the game loads fine without error.

The video card driver (S3) and sound blaster driver are both installed in Win3.1 before I installed Shivers.

Any solution about this waveoutopen device error?

Thank you,

Daniel

Quote

 

If you're feeling adventurous, you can actually setup an instance of Windows 3.1 within DOSBox (I recommend DOSBox Daum for this; I use regular old DOSBox for standard DOS games, but Daum handles the 3.1 environment better than normal DOSBox). I've done this to setup quite a few 3.5 era games (including Darkseed 2):

Burn:Cycle
Cosmology of Kyoto
Crusader: Adventure Out Of Time
Darkseed 2
Four-Sight
Frankenstein: Through The Eyes of the Monster
Gadget: Invention, Travel, Adventure
In The 1st Degree
Jewels of the Oracle
The Journeyman Project Turbo!
Karma: Curse of the 12 Caves
Logical Journey of the Zoombinis
Majestic Part 1: Alien Encounter
The Martian Chronicles Adventure Game
Math Blaster: In Search of Spot
Mirage
Noir: A Shadowy Thriller
Panic In The Park
The Residents: Bad Day on the Midway
Shivers
Spaceship Warlock

There are quite a few guides out there on how to do this. The way I've done it is to setup my instance of 3.1 as a base with no games installed, then I duplicate that folder and rename it after the game title whenever I want to setup a new game. I add disc images to the .conf file, boot up 3.1, use the 3.1 file explorer to install the game, exit, then edit the "Load=" line in the WIN.INI to direct it to the game exe; this way as soon as I start that copy of DOSBox, it boots 3.1 and then immediately boots the game. Then I add that copy of DOSBox to LB like you would any other game .exe. It starts DOSBox, boots 3.1, then boots the game.