If you modify ur openglid.ini file to these settings:

Configuration File for OpenGLide

Version=Version0.07b4

[Options]
EnableMMX=1
CreateWindow=0
InitFullScreen=1
EnableMipMaps=0
IgnorePaletteChange=1
EnableFog=1
EnablePrecisionFix=1
EnableWrap565=0
EnableMultiTextureEXT=1
EnablePaletteEXT=1
EnablePackedPixelsEXT=1
EnableVertexArrayEXT=0
EnableSecondaryColorEXT=1
EnableFogCoordEXT=1
TextureMemorySize=16
WrapperPriority=2
FrameBufferMemorySize=8

you can get a better rsult with blood

Nicht Sehr Gut wrote:

I downloaded Paul's files on a whim. Was stunned when it didn't lock up. Wasn't exactly viewable though. But the "mechanics" were working. I recognized some of the graphics, but it appears that there's no "erasing" of any graphics. So everything is a blur. Interesting to see running though, as I could never get it to work before at all.

BTW, this was on Win98SE. XP does nothing with it, as expected.

The blur is because you have different resolutions set in the cfg file and in Glidos. Make them the same (either 640x480 or 800x600) and all should be well.

Unregistered wrote:

I ran blood on my winXP it performed fine but the graphics are still wrong? (at least it doesnt crash though)

maybe paul coul add a selection between 2 diferent color modes to solve the problem, but makeing glidos run ARGB color might just be too much to do

How are you getting it to work under Windows XP? I get just the background of some of the menu screens

If the graphics are just a big blurry grid then you have the GLidos resolution and the blood.cfg resolution different.

Unregistered wrote:

If you modify ur openglid.ini file to these settings: […]
Show full quote

If you modify ur openglid.ini file to these settings:

Configuration File for OpenGLide

Version=Version0.07b4

[Options]
EnableMMX=1
CreateWindow=0
InitFullScreen=1
EnableMipMaps=0
IgnorePaletteChange=1
EnableFog=1
EnablePrecisionFix=1
EnableWrap565=0
EnableMultiTextureEXT=1
EnablePaletteEXT=1
EnablePackedPixelsEXT=1
EnableVertexArrayEXT=0
EnableSecondaryColorEXT=1
EnableFogCoordEXT=1
TextureMemorySize=16
WrapperPriority=2
FrameBufferMemorySize=8

you can get a better rsult with blood

The only thing I can see there that might help is IgnorePallette Change. That might disable some of Blood's lighting effects, and may speed things up for ATI cards.

Glidos wrote:

How are you getting it to work under Windows XP? I get just the background of some of the menu screens

Yeah, I'd like to know that too. I guess CLI2NOP won't work in this case... heh... and I guess it didn't work in Windows 2000...

Maybe the Unregistered guy meant he got Blood, not Glide Blood, working?

Glidos wrote:

Make them the same (either 640x480 or 800x600) and all should be well.

Actually no, I had both set to 640x480 when I tested it. It's no so much "blurry" as it is like video "stutter". I'll post a pic when I get a chance.

This is more of a curiosity for me than anything else. I'm just amazed that you could even get it to start up. If you ever get it fully functional, I'm going to have to mail you some lead bars so you can transform them into gold for me.

I can get most of the textures right (some are still fuzzy) most keep recuring over and over and the text is slghtly distorted but readable,
I;m not sure why Im getting good results with WINXP though it probably my graphics card (Nvidia geforce 2 Ti)

Also how do I fix this framerate problem on blood I have the same problem with GTAFX

I've been reading this thread for the past 2 days but haven't gotten around to testing Blood. Finally played with it for about 15mins this morning and got it working.

Tested under Windows 2000. Radeon 9700 Pro

Blood v1.11

1. Patch blood with 3DFX patch.
2. Download and install GLIDOS
3. Download GLIDOS Blood Update and follow the instructions.
4. Download NOLFB and copy to Blood directory or into your path.
5. Edit blood.bat and add NOLFB.com before the SET statements.
6. Modify GliDOS.ini Blood entry to look like this

Name: Blood
Executable: L:\Blood\blood.bat
DosGraphics: Yes
VESASupport: No
ControlJudderFix: 1
Resolution: 2
FullScreen: No

*Change FullScreen to whatever you wish. Doesn't matter.
*GliDOS VESA doesn't work for BUILD engine games in NT...at least for me it doesn't.

7. Run Blood Setup.exe and turn off SFX if you are using NT4/Windows 2000. Also setup Graphics to the same as that set in GliDos.

DosFreak wrote:

Blood v1.1 Name: Blood Executable: L:\Blood\blood.bat DosGraphics: Yes VESASupport: No ControlJudderFix: 1 Resolution: 2 FullScr […]
Show full quote

Blood v1.1
Name: Blood
Executable: L:\Blood\blood.bat
DosGraphics: Yes
VESASupport: No
ControlJudderFix: 1
Resolution: 2
FullScreen: No

Tried it your way. Slightly less graphic distortion on Win98SE. Nothing for XP. Having said that, my version is 1.21 (One Whole Unit release).

I found out how to make glidos blood to work on windows xp!

all u have to do is run nolfb.com once, (and only once!) in blood.bat without glidos vesa support,
then delete nolfb.com from blood.bat and then run blood with glidos vesa support (It looks the same as the previous picture though)

Odd, no graphics problems here. (Except for vertical lines in the sky) Hmmm, guess we'll have to compare our blood ver's so I can find out which files I'll need to convert mine to your ver.

Unregistered wrote:

I found out how to make glidos blood to work on windows xp!

all u have to do is run nolfb.com once, (and only once!) in blood.bat without glidos vesa support,
then delete nolfb.com from blood.bat and then run blood with glidos vesa support (It looks the same as the previous picture though)

Your post doesn't may ANY sense to me....

Running a program like nolfb only affects the current DOS window.

what your saying (from your post) is:

1. Place nolfb.com in blood.bat.
2. Disable Gldvesa.exe in GliDos.ini
3. Run blood.
4. Quit blood?
5. Remove nolfb.com from blood.bat
6. Re-enable gldvesa.exe in GliDos.ini
7. Run blood.

huh? If Gldvesa works for your then why enable LFB? Exactly what video mode do you have Blood set to?

I am currently running blood in 800x600 in Windows 2000 with no graphical anamolies except for the vertical lines in the sky. NOLFB is required for EVERY graphics card in NT OS's for BUILD engine games as far as I know....

Nicht Sehr Gut wrote:

Tried it your way. Slightly less graphic distortion on Win98SE. Nothing for XP. Having said that, my version is 1.21 (One Whole Unit release).

r u using the glide2x.dll provided with v1.19 or the new openglide .dll?

ehh, ignore me. Shouldn't matter anyway.

well I dunno if that didnt help I dunno why mine works? confusing?

Also with The vertical lines in the sky they have always been there even on voodoo1 card
3dfx never fixed the sky problem because they couldnt be bothered with blood after the alpha patch

I wonder if 3dfx blood will ever work??

Interesting results. I get the same with gldvesa as with nolfb, but I am suspicious of gldvesa with blood. I haven't tried turning off SFX yet. Maybe that's why it doesn't work for me under W2k.

So far it seems that 640X480 & 800X600 work for me with Blood 3DFX & GliDos in Windows 2000. Anything past 800x600 and Blood drops back to the desktop with no errors in Glidos. Haven't tested with just Blood & NOLFB just to make sure but I'm betting it's some limitation of this 3dfx executable.

Also MAKE SURE that you guys have both your GLidos.ini and your .CFG set to the same RES. Otherwise you will get the screwed up looking graphics where you can't see anything. (Lines where the text is supposed to be).

How are you doing that? It wont work for me under W2K. I tried disabling SFX but that didn't help. Is it Blood one whole unit you are using? If so could you try putting your working copy of Blood somewhere safe, and do a reinstall from scratch. Maybe that will fail and you will be able to see differences between the working and non-working copies.

When I try it on W2K, it is as though it can't find the files in its folder.

Hmmm, my copy is v1.11. Have had it since 1997 but don't remember exactly where I got it from. I simply patched it with the 1.20 3dfx patch.

Then just follow the steps that I posted above....

What do you mean it seems like it can't find the files? Can you run Blood without GliDos? heh. You know what your doing so I'm not gonna go through the basic troubleshooting checklist. 😉

Anyway, forgetting W2K for a moment, here is a new version of Glide2x.ovl to slip into your Glidos folder. It will partially make the mouse work if Glidos is in full screen mode; movement but no buttons. I need to take a look at the build engine source to work out what on earth it is doing about the buttons.

The mouse seems inverted to me and the sensitivity is wrong, plus you really want left/right to strafe when you have a mouse. I have included my blood.cfg file which fixes all that. Anybody who has W2K working, for god's sake don't lose your current cfg file: copy it somewhere safe.

Hmm, Paul what kind of Vid card do you own?