«

[Neobros]

Ah, just now it hit me, it could be a file corruption, and indeed redownloading the Dos version works fine.
Thanks you two

[Jake Grey]

I've been experiencing much the same problem. It seems to happen most frequently after something I'm running in the background throws up a pop-up window, leading me to suspect it might be an artefact of the game's DOS heritage, but it's also been known to occur without any obvious prompting. I've considered hitting Ctrl+Alt+Delete and killing every single process except Explorer and Systray before starting it, but Windows 2000 makes this rather difficult.
However, now that I've got my hands on a working 98SE machine, I'll test it out on that and see if I can replicate the problem with fewer background processes, and in pure DOS for good measure; if I'm on the right lines, it gives some of us a workaround and me a starting point for finding a more permanent solution, which I'll be taking to a friend of mine who's just landed a programming internship at NASA's Jet Propulsion Laboratory. (I will be asking for voluntary contributions towards the cost of all the beer I'll have to bribe him with. )
More on this as it happens.

[Eagle of Fire]

Congratulation on resurecting a year old thread...

[Jake Grey]

*shrug* If I hadn't, someone only would have chimed in saying there was already a thread about it and scolded me for not looking first.

[dosraider]

Fact: Dosversion runs fine in dosbox 0.72.
The winversion adds nothing, but really nothing.
So: why try to run the winversion made for an old OS on a modern OS?
I wouldn't know.
Really not.

[Jake Grey]

In my case, it's because my machine has real trouble running DosBox, though it seems to take VDMSound in its stride. I'm also not terribly confident at tinkering with config files.