Worked fine for me, even in 0.65 i think.
Maybe disable ems/xms or something, and try compiling the 0.70 release yourself.

WD, thanks for your heads up. I will try the memory tweaks and see if they work. I'm afraid it worked for you without the tweaks, so the chances are slim for me, but we never know.
I will also try the 0.70 version.
When I have something new, either good or bad news, I will post.
Cheers.

3dsr4 uses the pharlap extender, which is always a bit picky.
See if it works any better if you create an empty directory,
mount that as c: (like mount c c:\oldstuff\cdrive) and then
install 3dsr4 onto c.

Hi, everybody.
No luck yet, not even messing with the xms, ems and umb settings.
WD, by saying "install 3dsr4 onto c", do you really mean it? What if I don't have the installer anymore? I just have the thing in a dir, where it used to run, and point DosBox to this dir. What do you say?

Thanks a lot.

PS: running 0.70 on Windows XP x64 also crashes after a render.

Why don't you have the installer? 3DSr4 requires a hardware key unless you have some dodgy cracked version and if you do that could be the cause of your woes.

DMurray wrote:

Hi, everybody. No luck yet, not even messing with the xms, ems and umb settings. WD, by saying "install 3dsr4 onto c", do you re […]
Show full quote

Hi, everybody.
No luck yet, not even messing with the xms, ems and umb settings.
WD, by saying "install 3dsr4 onto c", do you really mean it? What if I don't have the installer anymore? I just have the thing in a dir, where it used to run, and point DosBox to this dir. What do you say?

Thanks a lot.

PS: running 0.70 on Windows XP x64 also crashes after a render.

What where the file/folder paths for the application before you tried to run it from DOSBox? And what are they now, seen from inside DOSBox?

Think having it in c:\3ds4 (or 3dsr4) should be best as it's the default installation directory.
That is if you copied it into c:\oldstuff\3ds4 then use "mount c c:\oldstuff"

Try reconfiguring it, using "3ds vibcfg" to bring up that setup dialog.

"unless you have some dodgy cracked version". DH4RM4, you pretty much nailed it :shy: . I never thought it could be the cause of the problem, hopefully you are wrong, my friend. =) But it doesn't crash in DOSEMU, like I mentioned before, but the render is only grayscale and DosBox has much better stability in this particular app. 3DS sometimes "hangs" for a few seconds during the use, it happened when I changed from a Pentium 100 to a K6 233, and DOSEMU "emulates" the hangs, but DosBox doesn't, which is good.
The path on which it currently runs is, indeed, 3DS4. The partitions are arranged this way: C: is NTFS, WinXP partition, D: is FAT32, which I use as a swap space between Linux and Windows, plus the Linux partitions.
3DS4 is in D:, so I mount as "mount C D:\" or "mount C /media/hda5" if in Linux, and then navigate to 3DS4 to execute the 3ds.exe (C:, cd 3ds4).
As for VIBCFG, I used a Tseng ET6000 2D PCI card with the ET4000 driver, worked fine in its time. Now that I use a Geforce 6800 AGP, I seem to have no choice other than using the VESA driver, 1024x768x256 colors is the best I can use, since 1280x1024x256 colors doesn't pass the test (I can't see the pattern). I have no idea on what other driver could work.

If you guys need some more info, please let me know. Anyway, I will post the error message which is output when 3DS crashes in DosBox for Windows. When I get back from work, I do it.

Thanks in advance.

DMurray wrote:

The path on which it currently runs is, indeed, 3DS4. The partitions are arranged this way: C: is NTFS, WinXP partition, D: is FAT32, which I use as a swap space between Linux and Windows, plus the Linux partitions.
3DS4 is in D:, so I mount as "mount C D:" or "mount C /media/hda5" if in Linux, and then navigate to 3DS4 to execute the 3ds.exe (C:, cd 3ds4).

I don't care shit about how it is *now* - I want to know how it *was* before you tried to run it in DOSBox.

It was always 3DS4. The thing was backed um in a CD and now copied to the hard disk the way it was.
"And what are they now, seen from inside DOSBox?", I thought you wanted to know how it looked "now".

Cheers.

You seem to be able to run it under windows, so be sure you
try dosbox 0.70 there. Does it crash exactly the same way as
in linux? When?
Does it happen with core=normal as well?

DMurray wrote:

As for VIBCFG, I used a Tseng ET6000 2D PCI card with the ET4000 driver, worked fine in its time. Now that I use a Geforce 6800 AGP, I seem to have no choice other than using the VESA driver, 1024x768x256 colors is the best I can use, since 1280x1024x256 colors doesn't pass the test (I can't see the pattern). I have no idea on what other driver could work.

I'd recommend that you try YHKWONG's CVS Build (check the CVS thread here on the forums) as that has an ET4000 built in.

DMurray wrote:

It was always 3DS4. The thing was backed um in a CD and now copied to the hard disk the way it was.

I doubt that. And you still haven't answered my question. But that is your choice. If you don't want to answer me, I won't bother try to help you.