Strange. I don't think I've ever seen it crash. Redguard sometimes crashes when running under it, but that doesn't lead to VDos32 itself crashing.

What do you see when it happens?

I'll post a picture next time it happens (now its suddenly started working again despite no changes at all). It's a standard windows crash dialogue.

Its happened again, here are the error messages: http://img.photobucket.com/albums/v227/MMANUGITU/Err.jpg

Of course, I can send the full error report part if it's of use.

Strange. Worth checking your computer's memory isn't dodgy, and that the computer isn't overheating (VDos32 does push the CPU hard).

Give Orthos a try for a few hours

I ran it for approximately three and a half hours. 0 errors or warnings, and I was doing various other things at the same time (which probably stretched it even more).

Selecting all the text of that error, pasting it into a text file and sending that to me might help, but really I have no idea. No one else has reported this sort of thing.

Running orthos at the same time as a 3D game (other than Glidos ones) would be worth doing.

Try running the software version of TR1 via VDos32.

Try configuring no audio in TR1 and play like that to see if that helps.

I was running intensive games at the time I was using Orthos, so I've already did that, I've also tried the other suggestions (which didn't work).

It doesn't let me select the text of that error for copying, but I can send the text file it mentions.

Two of the suggestions were to try to get more information.

So running the software version of TR1 under VDos32 crashes in the same way?

Running setup.exe to configure TR1 to not use audio and then running it also leads to a crash?

Ah, new one: does it crash in the same way if you start a new game, rather than load a save game?

That text file might help. Worth a try.

Also I may be able to make a version that will display a few parameters which may tell us something. I'll look into that when I can find some time.

The sound test I did was turning it off in Glidos, so I'll try turning it off in DOS when it starts happening again (It's working again right now).

When it's crashing it happens whether I'm using VDos32 in Glidos or not (I haven't tested while it's working in Glidos; I'll go do that now).

Edit: VDos32 works on its own when it's working in Glidos, although it gives an error that Glidos isn't present after loading.

Ah, new one: does it crash in the same way if you start a new game, rather than load a save game?

This crash happens before the game starts, so I can't test that.

Heres the text file, if you can make sense of it:

That seems to be different info. I was hoping to get a file with the text you are unable to select from the dialog box. I don't know where that ends up though.

I've captured part of the message (capturing all of it would take ages, and the rest is all very similar to what I end on), it's a bit artifacted due to trying to keep the size small, but it hopefully doesn't make the text any less readable. You'll probably have to pause it throughout since I go relatively fast.

Here's the link (hopefully you can play it): http://files.filefront.com/Test0067avi/;83134 … ;/fileinfo.html

Neat idea with AVI, but sorry I can't work with that. I'd need to be able to do textual searches. There must be some trick or other for pulling out the text. Next time I have something crash, I'll see if I can find out.