Dolenc

Thank you for responding. Yes h5. I build on winxp, with winxpddk(2600) with win98sdk, vc6 headers and all other old stuff installed. I dont use win9x.obj, reverted to state on...

No this one doesnt work. 

Thanks for looking into it, I spent more time than Im willing to admit, with no resolve :)

Just tested it now, from your codebase as debug=1 doesnt work, will ignore user settings(switched about 3 weeks ago, forgot). This is the exact one Im using now: [sourceForgeDevelop.zip](https://github.com/sezero/glide/files/8856510/sourceForgeDevelop.zip) Wanted...

You trying a different compiler got me thinking. What if really isnt a code problem? So I tried a couple, and win2kddk compiles it correctly, registry path gets read. Ofc,...

Yes, mine has a bit different lines. Its just asm code, I think the way I have it now(with 2kddk istead of xp) it doesnt use nasm. I tried moving...

I dont think that win9x.asm is the problem in any way, since I also use sourceforge last build and that one doesnt use it. So right now, I can either...

Removed all ddk(s) from path, should be only vc6. As "make -f Makefile.win32 FX_GLIDE_HW=h5", dll comes out, not gonna test it, but should work. As "make -f Makefile.win32 FX_GLIDE_HW=h5 USE_X86=1",...

How about we do the oposite? Move the problematic code to seperate file, compile with nasm and have just calls to obj? Im not really an assembler(or C for that...

In minihwc.c every(complete) part thats in the error lines 62xx... 6350.... 685x#if GL_X86 and so on...