Assuming the .conf file is exactly the same in both cases, then it's probably some woefully obscure bug in the compilation of the Macintosh version of DOSBox.

You can always try to run the Windows version of DOSBox under Wine in OS X, I think.

Are you using the same installation of Windows 3.x and that game on bith machines?

Works fine for me with 0.74 and latest SVN of Dosbox on OS X (Yosemite).

Jorpho wrote:

Assuming the .conf file is exactly the same in both cases, then it's probably some woefully obscure bug in the compilation of the Macintosh version of DOSBox.

Other than the specified file paths, it is the same.

Dominus wrote:

Are you using the same installation of Windows 3.x and that game on bith machines?

Yes, the version of Windows is the same and the game version is the same. I am able to boot Windows 3.1 without a problem, and I can run another game made by the same developer, but this particular game throws a heap error. I can't seem to figure it out. 😢

EDIT:

Works fine for me with 0.74 and latest SVN of Dosbox on OS X (Yosemite).

I just tried it with the version in your signature and got the same error. Bugger. I guess it wasn't meant to be.

Just out of curiosity, try normal core and no more than 20,000 cycles.

bryantjs6 wrote:

Dominus wrote:

Are you using the same installation of Windows 3.x and that game on bith machines?

Yes, the version of Windows is the same and the game version is the same. I am able to boot Windows 3.1 without a problem, and I can run another game made by the same developer, but this particular game throws a heap error. I can't seem to figure it out

I didn't mean whether it is the same version, but whether it is the same installation. Seems it isn't. So why don't you try the same installation? Just move the whole thing (Windows 3.x and whatever games) to a stick and mount it the same on OS X than on Windows (of course adjust the paths from Windows to OS X paths, e.g. if you used "mount c c:/dosgames" use "mount c /volumes/usbstick/dosgames" instead and same for mounting d).

Since the game runs fine for me, you can rule out an error with Dosbox and expect some kind of difference in your windows 3.x or Dust installation.

Edit: another thing to try is whether the installation type makes a difference, Dust offers three different ways. I chose typical.

I see what you mean now, but that is what I did. Same exact ISO images and same exact Windows files. Everything works exactly as expected on OS X except for this.

I probably should have mentioned that the program does run initially, but pressing Play is where I experience the problem.

collector wrote:

Just out of curiosity, try normal core and no more than 20,000 cycles.

Setting the core to Normal has given me a different error message:

Win32s - Error

Initialization of a dynamic link library failed. The process is terminating abnormally.

I'm not sure if this is a step forward or back.

I also tried manipulating the number of cycles and disabling sound. The heap error was still being thrown with those changes.

EDIT: Just now tried uninstalling and reinstalling the game. No luck.

Dominus wrote:

Edit: another thing to try is whether the installation type makes a difference, Dust offers three different ways. I chose typical.

I initially did the typical installation which worked fine on the PC. When it didn't work on Mac, I went in and did a custom install which installed the rest of the files (mainly things like animations and the like to speed up the game). Still got the same error.

So, I know this is repeating but I want to make sure, you did NOT install Windows 3.x on OS X Dosbox?
Can you post your dosbox preference file from OS X? I want to doublecheck whether I have something set differently.
Also which graphics driver did you install in Windows 3.x?

It HAS to work - we NEED to find out what's wrong!!! 😉

bryantjs6 wrote:

Setting the core to Normal has given me a different error message: […]
Show full quote

Setting the core to Normal has given me a different error message:

Win32s - Error

Initialization of a dynamic link library failed. The process is terminating abnormally.

I'm not sure if this is a step forward or back.

Win32s games generally require cputype=486_slow or cputype=pentium_slow in DOSBox.conf. That might help.

It is also perhaps worth trying a bootable hard drive image rather than using mounted folders, especially since that way you can make extra sure that both the DOS and Mac versions are using the same data in the same way.

I'll give it a try on my Windows 3.x install that followed my guide. Right now I had tried it on my install from the 90ies that I had on a backup and might have some fixes (and which I prefer since it has all kinds of bells and whistles 😉)

Edit: sorry to say, but it also works fine in my bare bones Windows 3.1 installation, which has almost no alteration to the lock stock preference/config file.

Dominus wrote:

So, I know this is repeating but I want to make sure, you did NOT install Windows 3.x on OS X Dosbox?

I had not installed it on the OS X DOSBox, so I just did. I am still getting the same error messages. I initially got a very different messages when I had the core set to normal, but I think it was because the Win32s install failed. I reinstalled it and got back to the same error messages.

Here is my conf file.

Jorpho wrote:

Win32s games generally require cputype=486_slow or cputype=pentium_slow in DOSBox.conf. That might help.

This did not work, unfortunately.

Dominus wrote:

So, I know this is repeating but I want to make sure, you did NOT install Windows 3.x on OS X Dosbox? Can you post your dosbox p […]
Show full quote

So, I know this is repeating but I want to make sure, you did NOT install Windows 3.x on OS X Dosbox?
Can you post your dosbox preference file from OS X? I want to doublecheck whether I have something set differently.
Also which graphics driver did you install in Windows 3.x?

It HAS to work - we NEED to find out what's wrong!!! 😉

Dominus wrote:

Also which graphics driver did you install in Windows 3.x?

Whoops, I forgot to post this one. I used the s3 driver you have in your guide. The specific display I chose is:

S3 Trio64V 1.70.04 640x480 256

I'm gonna try later with that res...

Thanks. I appreciate the assistance.

The game recommends the resolution and color depth I selected which is why I picked that one. I also tried 800x600 with 256 colors but had the same issues. These settings all work on the PC, but no dice on the Macbook.

Haven't had time to further test it but am still puzzled...
So, you followed my guide. What of all the stuff I mention there did you install, what did you skip? Did you install anything in addition to this? Did you change any system.ini/win.ini stuff or added some other driver or change through the control panel? What version of Windows 3.x? WfW or plain Windows 3.1?
Trying to find the difference between our setups... So list any little thing you did differently/additional to the guide...

I only skipped the joystick and QuickTime. Before I created this thread, I skipped Win32s, VfW, and WinG. Dust installed Win32s itself, and then after getting errors, I installed the other two.

The only changes I made were to the DOSBox .conf file. No .ini files were touched.

It's just Windows 3.1. Not Workgroups or anything like that.

Still not able to reproduce this 🙁

One thing I noticed, though, is that you are using output=surface in your dosbox.conf. Set this to opengl, for me surface is really really slow, no such crash, though.
If I have time tomorrow, I'lll try with a new install and try hard to test it on each step...

The most easy way is to transfer working (or nonworking) installed files from one to another. If behavior will differ, then the problem is external.