VOGONS


First post, by Holonius

User metadata
Rank Newbie
Rank
Newbie

Hello,

I recently received the GOG version of Colonization for DOS and it runs perfectly accept for when I switch to FULL SCREEN I lose the sound effects (battle, chopping, wagon trains, etc). I cannot seem to find this issue posted anywhere on here (or via google for that matter). The sounds all work when the game is windowed but not when it's full screen and I would prefer full screen. The music plays in full screen and windowed mode. Just the sounds effects stop when full screen.

Would anyone have a fix for this? The follow is the dosbox .conf that the GOG installer makes for the game:

[sdl]
fullscreen=true
fulldouble=true
output=surface

[dosbox]
machine=svga_s3
memsize=30

[cpu]
core=auto
cycles=10000
cycleup=1000
cycledown=1000

[mixer]
prebuffer=20

[sblaster]
sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050

[autoexec]
@echo off
mount C .
imgmount D "MPS\COLONIZE\Colonize.dat" -t iso
c:
CD MPS\COLONIZE
cls
opening -g %1 %2 %3 %4 %5 %6 %7 %8 %9
exit

I've tried many different combinations in the sblaster section based on searches for sound issues with the game but nothing fixes this sound effects problem I'm having. My system stats:

Asus P5N-D
e6500 2.93 GHz Intel CPU
GeForce GT430 1Gig
5 GIG RAM
On Board sound
Windows 7 x64
Colonization DOS v3
DosBox .74

Thanks for your time.

Reply 1 of 4, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

Is your monitor connected via HDMI? Do other applications such as media players work when switched to fullscreen? What about other games in DOSBox, or other GOG games? (Teenagent is a free download, if you want to test something.)

Reply 2 of 4, by Holonius

User metadata
Rank Newbie
Rank
Newbie

Yes, my monitor (which is actually a TV) is connected via HDMI. Media players and other GOG games work (Reus is the most recent I've tried) full screen. I have not tried another game in dosbox.

I feel I should also mention that the sound and video are being handled by that single HDMI cable to a receiver then from that to my TV. I wouldn't have thought my setup was an issue seeing as it all works windowed but I'm guessing full screen and windowed are two different beasts.

The sound works when full screen on my netbook so obviously the problem has something to do with my hardware setup the game or dosbox doesn't like full screen.

UPDATE EDIT

So I ran the game on my A/V setup from my Netbook and the sounds work full screen. Now I just need to figure out what's different on / in my PC verses my Netbook. Thanks for pointing out something I didn't think to check.

Last edited by Holonius on 2013-06-03, 20:19. Edited 1 time in total.

Reply 3 of 4, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
Holonius wrote:

I have not tried another game in dosbox.

Isn't it awfully premature to say that it's a problem with Colonization, then?

It may actually be a problem with the SDL library that DOSBox uses and not DOSBox itself, so you might want to test another application that uses SDL – ScummVM, perhaps.
http://en.wikipedia.org/wiki/List_of_games_using_SDL

I feel I should also mention that the sound and video are being handled by that single HDMI cable to a receiver then from that to my TV. I wouldn't have thought my setup was an issue seeing as it all works windowed but I'm guessing full screen and windowed are two different beasts.

Your video card might be trying to reroute the audio signal in a way that your receiver does not expect. It might also be worth updating your video card drivers, and perhaps even your audio drivers or HDMI receiver drivers, if applicable.

Reply 4 of 4, by Holonius

User metadata
Rank Newbie
Rank
Newbie

Thanks for the quick reply. I edited my second post after reading your first reply and tried a few things. I'm going to have to figure out what's different between the two systems now.

I didn't actually say anything was 'wrong' with Colonization just that under my conditions the sound effects wouldn't play. I asked hoping someone had the same issue I'm having and came up with a solution or resolution at least. Now that I know it's something do to with my PC setup I'm in a better place to troubleshoot from.

Thanks again for your insight.