Sounds like what would happen when using something other than the machine=svga_s3 setting. Otherwise, dunno, never heard of anyone having that problem before.

ripsaw8080 wrote:

Sounds like what would happen when using something other than the machine=svga_s3 setting. Otherwise, dunno, never heard of anyone having that problem before.

Hmm... Nope, my .conf says svga_s3...

Well I seem to have solved it. Before when I ran the setup, I was choosing "recognize" to have the game detect my display (which it seemed to successfully do, detecting SVGA S3). I tried choosing "VESA" instead and proceeded from there and the game no longer hung at the driver loading, Weird.

This is a very badly coded game indeed (all of the projects from this studio were kind of trainwrecks). The user interface is horrendous too. Candidate for #1 most unintuitive and unergonomic inventory management ever.

For what's it worth, this is my dosbox conf file for this game:

1[dos]
2ems=emm386
3
4[autoexec]
5imgmount d "cd/bigredadventure.cue" -t iso
6mount c game
7c:
8cd BIGRED
9d:
10d:\sbeff 544 7
11d:\adlibmsc
12d:\mdrv
13d:\adv -l0 -cC:\BIGRED -dD
14d:\uninst
15exit