Probably a good idea is to try v1.19 of Glidos. There isn't a link to it on my web site, but its there. You just use the link to v1.22 and edit the 22 to a 19 (before downloading the file, obviously, not afterwards 😀 😀 ). I have somebody with a similar problem find that v1.19 works for them.

Thank you very much! That version works. 😀 Thanks again for all of your help.

Heh, Paul, you brooooooooke it!

Martin Westmark wrote:

Thank you very much! That version works. 😀 Thanks again for all of your help.

Martin, please keep following this thread. Using an old version of GLIDOS is no TRUE solution. Paul should soon figure out your problem (I hope). So don't think you are forced to use this old version forever!

Snover wrote:

Heh, Paul, you brooooooooke it!

Not necessarily. Martin could you try v1.22 again, but using the version of Glide2x.dll from v1.19?

Well if it won't mess up my saved games, I'll be happy to try it and tell you the results.

Originally posted by Martin Westmark Well if it won't mess up my saved games, I'll be happy to try it and tell you the results.

Just archive them first. That way, if they are corrupted, you can just replace them with your original files.

Well I tried it. The game loads, though the resolution is all messed up.

The... resolution... is all messed up.
*cough*
What the hell is that supposed to mean? Is it running at 992x120.55 or something? 😜

Unregistered wrote:

Well I tried it. The game loads, though the resolution is all messed up.

Please would you expand on that. This info could very useful.

1) Is it the case that v1.22 crashes, but using the version of Glide2x.dll from v1.19 stops the crashing?

2) Although the crashing stops, there is some other problem with the resolutions. What is that problem?

I can't see what I've broken. Can I ask for some help with this one. Martin, would you mind retrying:

v1.22

v1.19

v1.22 (but with the Glide2x.dll file from v1.19)

v1.19 (but with the Glide2x.dll file from v1.22)

Note it is Glide2x.dll not Glide2x.ovl

Cheers,
Paul

and almost 3 years later i'm having the exact same problem as this guy had, only i'm using v1.32. Ever figure it out?

This thread is too confused. Tell me exactly what you are seeing.

I am seeing a thread about a guy that had a problem running redguard using v1.22. the problem is that glidos crashes upon trying to load the game and windows asks to send a error report.

"Tell me exactly what you are seeing" - that was me preparing to give up some of my time to give you some help.

"I am seeing a thread" - that's a very good way to piss me off so that I can no longer be bothered.

I am sorry for that, i actually thought you were referring to the forum and not the glidos server. Stupid people (me) don't realize they are being stupid the majority of the time. Whether you are still willing to help me or not, I will describe my problem with actually running the game this time. I managed to get the problem of glidos crashing and wanting to send an error report to microsoft to go away by putting the play disk in the drive. However, it still wouldn't run properly. I run glidos, select redguard, and hit start. Some DOS commands come on the screen about VDMSound and then the executable starts. I get the hard drive access resticted message and click ignore, per the instructions on the glidos website about running redguard. Before, this is the point glidos crashed, but now i get another glidos window that i cannot see, simply titled "Warning". Unsure of what to do, I directed keyboard focus to the unseen window and hit enter. The window went away, and after a 30 seconds or so, the other glidos window went away, replaced by a message window that said "Read failure". If i have pissed you off and you do not care to help anymore, you have my complete understanding. Thank you.

Sorry, I seem to have been a bit tetchy this morning.

Teething problems when getting Glidos going aren't unusual, but the main app crashing is. What graphics card do you have, and where did you get the graohics drivers for it? (Glidos uses OpenGL which isn't supplied with the graphic drivers that Microsoft distribute)

A good thing to try is setting Glidos out of fullscreen mode, and setting the resolution to 640x480. That gives you some chance of seeing any windows that pop up.

Have you used Glidos with any other games?

sorry to have forgotten to mention the screen modes. When it crashes it does go to a full screen mode initially, but i am able to alt+enter back to a windowed mode, but when i get the warning the dos command window dissappears or doesn't refresh, but doesn't go to fullscreen at all. I will check to see if I have OpenGL installed and my video card is a Radeon 7000/Radeon VE Family.

ok, more info, I updated the display driver to ensure there are no problems there. I did manage to see the warning message and it said something to the effect of 'you are using a non-accelerated OpenGL, things can get really slow', and it DOES go to full screen mode, but only for a sec before the warning comes up.

I have not tried other games, nor do i have any of the other games.

Are you saying that you see the "non-accelerated OpenGL" message even now after updating your drivers? If so you updated them in the wrong way. You need to go to ATI's web site and download the Catalyst drivers. That will fix it.