VOGONS

Common searches


First post, by iconoclast12

User metadata
Rank Newbie
Rank
Newbie

Hello,

I'm attempting to get both Future Shock and Skynet running but am having issues with both games crashing right after starting a new game or loading a save. I can hang out in the main menu as long a I like, however, with no issues.

I have the original discs for both games, and I'm installing the games from the discs. It does not matter which order I install them in (other than doing Skynet second, it offers to detect Future Shock during the installation).

One of the computers I attempted this on is an older Windows 7 Dell with a core i3, 6gb ram and a geforce 8600 gts card (yes the graphics drivers are up-to-date and yes I already thought of that).

The other computer I've attempted it on is an Alienware laptop with Windows 10, 8th gen i7, 16gb ram and a geforce 1060 6gb.

I'm running version 0.74 of Dosbox (at least that is what the damn icon says).

Game versions are both 1.00 on the discs but I have patched both Future Shock and Skynet to 1.30 and 1.01 respectively. (I have also tried getting the games to run patched AND un-patched with the same results!)

Games are installed to my C: drive in this folder C:\dosgames

I open dosbox and type the same thing I've typed for literally every other freaking dos game I've installed through dosbox (Every other WORKING dos game, mind you!)

mount c c:\dosgames
mount d d:\
d:
cd shock
install.exe

mount c c:\dosgames
mount d d:\
d:
cd skynet
install.exe

(I do this for both games. Both games install successfully)

After the games are installed. I copy the patch files (sky101.exe and tfs130.exe) to their respective folders in c:\dosgames\shock and c:\dosgames\skynet

I then run them from the dosbox prompt. Both games patch successfully.

For whatever reason, I CANNOT get Future Shock to run independently by itself. Every. Single. Time. I install the game. I run the following commands..

(physical disc in physical drive)
mount d d:\
mount c c:\dosgames
c:
cd shock
shock.exe

(Throws some error about the disc not being detected in the drive)

So, yeah, Future Shock whines and moans about the disc not being in the drive no matter what I do, so there's that problem.

However, if I startup Skynet, the game actually works and I can use the main menu to get to Future Shock from there, however here is where the real problem comes in..

Both Future Shock and Skynet run for mere seconds before dosbox crashes. Every. Single. Time.

"Dosbox ran into an unexpected problem and needs to close" EVERY. TIME.

I've attempted running the games without configuring any sound and also without running in 640x480 just to test it out to see if the resolution or audio is causing the problem, and funny enough, I can run both games for maybe 10-15 minutes in low-res without audio, until they crash. However, they still crash, it just takes longer..

What am I doing wrong here? I have over a dozen other games installed through dosbox, some of which are from the late 1980's that still work fine. These are literally the only two dos games I cannot get running in dosbox.

I see people with videos on youtube running computers similar to mine, without having to do any of the crap I've had to do to get these games working.

I should note that I can get Skynet running by itself if I use the unofficial 2017 patch on it, and it works with both audio and high-res but if I try to switch over to Future Shock after using this patch, I get kicked back to the dosbox prompt with some weird error message involving characters that I can only describe as wingdings.

And that's that..

Reply 1 of 8, by DracoNihil

User metadata
Rank Oldbie
Rank
Oldbie

It's been a long time since I ever touched Future Shock (I don't have SkyNET) but I know two things you absolutely should not do:

1: Try to replace the DOS Extender stub with something else. (You can with Daggerfall with great positive effect, just not with these Terminator games)
2: Try to run the game with a 64-bit binary DosBOX. (I've had a lot of non-descript "Segmentation fault" errors if I try to use 64-bit DosBOX builds, make sure you're using a 32-bit build)
3: memsize being set below 31. (You might even need to set it to 63, I know I had to do this with Daggerfall atleast)

Mind you though, Bethesda games are always this temperamental. They can and will crash at anytime for seemingly any reason. But, Windows saying DosBOX itself is crashing means the emulation is segfaulting somewhere. So I'd first make sure you're trying to use a 32-bit EXE of DosBOX first.

If DosBOX doesn't crash when core is set to "normal" as opposed to "dynamic" then there's something seriously wrong.

Steam Profile
YouTube Channel
Seal of Nehahra

Reply 4 of 8, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie
DracoNihil wrote on 2020-04-27, 19:30:

2: Try to run the game with a 64-bit binary DosBOX. (I've had a lot of non-descript "Segmentation fault" errors if I try to use 64-bit DosBOX builds, make sure you're using a 32-bit build)

That seems strange. I would have thought that the emulated 'DOS PC' that the 64-bit version of DOSBox mimics would be identical to the DOS PC that the 32 bit version of DOSBox mimics. I wouldn't have expected any differences that would affect the real, host PC to result from running a 64-bit version of DOSBox versus a 32-bit DOSBox build (of the same initial DOSBox source code). Is there an as yet unfixed bug in the 64-bit DOSBox build that causes this?

Reply 6 of 8, by DracoNihil

User metadata
Rank Oldbie
Rank
Oldbie
Kerr Avon wrote on 2020-05-03, 17:19:

That seems strange. I would have thought that the emulated 'DOS PC' that the 64-bit version of DOSBox mimics would be identical to the DOS PC that the 32 bit version of DOSBox mimics. I wouldn't have expected any differences that would affect the real, host PC to result from running a 64-bit version of DOSBox versus a 32-bit DOSBox build (of the same initial DOSBox source code). Is there an as yet unfixed bug in the 64-bit DOSBox build that causes this?

I have no idea, I asked about this a long time ago wondering why Archmedian Dynasty among several other protected mode games causes DosBOX to segfault and ended up coming across something (not on the VOGONS forums) mentioning apt-get'ing the i386 arch rather than the x86_64 arch package of DosBOX and that worked.

Unless it's a bug that has been fixed, or if it's some sort of compiler bug, it's probably best to use 32-bit binaries of DosBOX instead of 64-bit binaries.

Steam Profile
YouTube Channel
Seal of Nehahra