Hey, sorry if I post this on two sections of the forum, I really need help. ASAP
I had problem with my voodoo2 (win98) in the past using the provided drivers, the updated version of them and using the 3dfxzone drivers. But that was some unsuported gl drivers issue.
This amazed me: I recently installed a demo for Medal of Honor Allied Assault (from a very old cd) and the first time i run it, It crashed.
After rebooting the game tried to load 3dfxvgl.dll (that's the gl driver I was talking about) and winbloz freezed inmediatly (this only happened every once in a while using the gl driver and only when UNloading it).
Now i realized that when rebooting, windows freezed few seconds after loading the os. The same thing happened if I'd hurry and try to open the Screen Propierties dialog.
I tried altering some BIOS parameters, installing several drivers with different versions and using PowerProof mode (wich worked fine... but that only gave me the chance to disable voodoo2).
This dazzles me... Can someone help me?
PLZZZ!

Hey, sorry if I post this on two sections of the forum, I really need help. ASAP
I had problem with my voodoo2 (win98) in the past using the provided drivers, the updated version of them and using the 3dfxzone drivers. But that was some unsuported gl drivers issue.
This amazed me: I recently installed a demo for Medal of Honor Allied Assault (from a very old cd) and the first time i run it, It crashed.
After rebooting the game tried to load 3dfxvgl.dll (that's the gl driver I was talking about) and winbloz freezed inmediatly (this only happened every once in a while using the gl driver and only when UNloading it).
Now i realized that when rebooting, windows freezed few seconds after loading the os. The same thing happened if I'd hurry and try to open the Screen Propierties dialog.
I tried altering some BIOS parameters, installing several drivers with different versions and using PowerProof mode (wich worked fine... but that only gave me the chance to disable voodoo2).
This dazzles me... Can someone help me?
PLZZZ!

Yay, thanx for the replies
First of all, YES I have Winblowz and M$VC (vc6, no sp, wich is worse)
But I guess that's not the problem since I'm using precompiled mesafx 6.1
My thoughts were that if the precompiled dll worked for almost every opengl based game out there it should work aswell for my app (without compiling it)
So I used the precompiled in put opengl32.dll (mesa's) and glide3x.dll and fxmemmap (I know I don't need this last one, it's a DX driver).
Second, I don't need any tuts on wgl, I just wondered why my app crashes when that function gets called. And when looking thru CrystalSpace sources I saw that they called DeleteContext before MakeCurrent(NULL,NULL) (the opposite order from any tut I saw, specially, Nehe's).
So... I don't know what to do with the dll?
I can't compile it because i need masm and I couldn't make my way thru all the .mak files mess (no offense, but honestly it's messy).
I won't give up to my voodoo2 until I get I newer one (I don't know when will that be)...
So If you could just give me a tip on what could wglDelete to crash
Or maybe i should call a more mesa specific wgl call? I really dunno
Thanx, and your help is apreciated

I have a problem with MesaFX. I recently downloaded Mesa Sources and tried to compile MesaFX. It was chaotic and it took me a big effort. Finally I could just compile it in debug. When I used the opengl32.dll (mesafx dll) inside my directory it popped up a blank message box with title Error.
The other day I noticed I didn't needed to compile it myself and use the lib and headers... I read somewhere that mesafx could be used as a replace for the opengl32.dll driver in some games. Because of that the only possibilty that I thought of is that using standard gl headers and libs, at runtime the correct dll would be used and everything should work OK. The only compiled version I could use (and that works for me) is the MesaFX 6.1 (I noticed that glide3x.dll and fxmemmap needed to be in the same DIR, it didn't worked when copying it into windows/system).
Now onto the problem: my app (compiled with mesa headers and normal opengl libs) crashes every now and then (it can go perfectly fine but when I start it again it crashes, I can't seem to know whats makes it not to crash) when calling wglDeleteContext. I first do wglMakeCurrent(NULL,NULL) and, after that, the wglDeleteContext crashes the app (but as I said, every once in a while). I tried to call wglDeleteContext first and then wglMakeCurrent (i looked into CrystalSpace engine code, they did it like that) and now it crashed again on wglDeleteContext (so this is the problematic function).
I have voodoo2, win98. HELP!
PS2: I had problems while loading the 3dfxvgl.dll in the past (before using mesa). When I called FreeLibrary(lib); it crashed... but again... not always...
This makes me wonder if it's in any way related the the wgl problem.
THANKX!