I've been trying to get my original CD version running under WINE, but the game is proving to be very unstable.

This is using a 32-bit wine environment (the installer wouldn't run otherwise), and Windows 98 emulation.

I'm using the software rendering mode.

I needed to use the MouseWarpOverride registry setting to get the mouse to work properly in-game (but this also messes it up for some of the menu screens, so you may need to alternate that setting while getting things configured).

Unfortunately, I'm suffering very frequent in-game crashes, so it's not practical to play at present. I don't know if there's anything I can do about that. Is anyone else having better success, either with the original game or with the GOG version?

Interestingly, I've experienced a great many crashes after loading a mid-mission save, but the game seems more stable when playing missions from the start?

Or at any rate, I just completed two and a bit missions before crashing, whereas I was regularly crashing after a minute or so of gameplay when loading a save file.

Well, since then I've only had one other crash during a mission, and I'm over half way through the game, so in fact this is far more stable than I originally suggested.

I haven't tried saving/loading mid-mission again, mind; only between missions.

The way I'm launching it is a bit awkward, mind, and I don't know WINE well enough to know the sensible way of doing these things... (a) I couldn't avoid getting issues in full-screen when the desktop resolution was larger than the game resolution, so I'm changing it explicitly before and after; (b) I couldn't see what the proper way of launching the game directly was, while still letting it see the correct current working directory, so I'm actually running explorer, and then double-clicking uprising.exe. It works, so I've not bothered researching it more.

xrandr --size 640x480; WINEPREFIX=$HOME/.wine32 wine explorer 'c:\games\uprising'; xrandr --size 1920x1080

WINEPREFIX=$HOME/.wine32 wine start /Unix "$HOME/.wine32/drive_c/games/uprising/pathToEXE"

The wine start doesn't always work. Sometimes games will crash instead of launch and some games work better with the other form using the Wine internal Windows style path without /Unix. Typically with /Unix works better for me.

I tried it in Crossover 15.0.1 under 64-bit Linux (3.10.x kernel, Intel video). Wine itself is 32-bit in Crossover. It works without any tweaking with the only exception that it crashes when I complete any mission (either campaign or training). In-game reloading doesn't work (though it loads after restarting the program without any problems). I am yet to try it under vanilla WINE.

Right. I think I had already tried this both with and without /Unix paths, and it always immediately crashed, so I assumed I was doing it wrong. Oh well; launching it from Explorer is fine as a workaround.

Edit: Actually, that does run the game, but it switches back to a 1920x1080 desktop when it starts (with the game occupying the top-left 640x480 region). If I try to solve the desktop size by adding /desktop=Uprising,640x480 it then crashes.

That's frustrating. I've had the occasional crash when exiting the game completely, but those ones are harmless. I've not had any crashes at mission completion, though.

WINE is a joke. It never has worked for me. What a gimmick.

Um, wow?!

WINE is absolutely amazing.

It's not perfect (it would be excessively optimistic to hope for that) and it doesn't work for everything, and there are niggles or hoops to jump through; but it absolutely blows my mind how well it works in general.

I've also played some older games that run better under WINE than they'd run under any version of Windows for years.

It's a huge shame that it's not working for you; but it is neither a joke nor a gimmick, and it does work for a great many people, and the engineering know-how and countless hours of hard work that has gone into it is very much deserving of respect.