if you want glidos to work on xp with blood you need a VESA high resolution patch called nolfb. go here:

http://www.advsys.net/ken/build.htm

download nolfb.zip, extract and run in a .bat file along with 3dfx.exe
example

nolfb.com
3dfx.exe

note: you should check if this works with regular non-3dfx blood first

you also need to modify your glidos.ini file to have the .bat file in place of 3dfx.exe
example

Name: Blood
Executable: E:\Blood\(name of file).bat
ControlJudderFix: 100 <--(also try changing this value see if that helps)
Resolution: 3
FullScreen: Yes
ForcedTextureSmoothing: Yes (turn this off it shoulnt make any difference)
BloodFix: Yes

I did have nolfb.com already in the folder (forgot to mention).

However, I made the changes to glidos.ini you suggested, and separately tried changing ControlJudderFix to 1

Same symptoms (frozen menu screen)

Another few noteworthy items
- while at the first prompt for "Press any key to continue . . ." the PC is running slugishly, as though the DOS app is consuming a lot of CPU cycles
- while at the second prompt for "Press any key to continue..." (the one on the page with the 3dfx alpha message) the system is almost non-responsive outside of the DOS box, by which I mean clicking on windows apps or menu buttons take - literally - minutes to respond. However, selecting the DOS app, and pressing the space bar, blood boots instantly
- while at the Blood menu screen, same behavior as above - windows not responsive - except that Blood itself is also non-responsive

Any ideas?

I'm not clear on whether setting up VDM shortcuts and properties for 3dfx.exe will change the emulation environment of Blood when launched through Glidos or not? If the answer is that it does, are there any experiments to try there?

What about the warnings in the VDMS log about DMA requests? Is that a possible source of problems?

I have posted my blood.cfg file also (VESA mode, no sound fx or music).

thanks for help received so far!

Otipher

== blood.cfg
[Setup]
;Setup File for Blood
SetupVersion = "1.10"
;
;
[Screen Setup]
;
;
;ScreenMode
; - Chained - 0
; - Vesa 2.0 - 1
; - Screen Buffered - 2
; - Tseng optimized - 3
; - Paradise optimized - 4
; - S3 optimized - 5
; - RedBlue Stereo - 7
; - Crystal Eyes - 6
;
;ScreenWidth passed to engine
;
;ScreenHeight passed to engine
;
;
ScreenMode = 1
ScreenWidth = 640
ScreenHeight = 480
;
;
[Sound Setup]
;
;
FXDevice = 13
MusicDevice = 13
FXVolume = 220
MusicVolume = 200
NumVoices = 8
NumChannels = 2
NumBits = 1
MixRate = 11000
MidiPort = 0x330
BlasterAddress = 0x220
BlasterType = 3
BlasterInterrupt = 7
BlasterDma8 = 1
BlasterDma16 = 5
BlasterEmu = 0x620
ReverseStereo = 0
;
;
[KeyDefinitions]
;
;
Move_Forward = "Up" "Kpad8"
Move_Backward = "Down" "Kpad2"
Turn_Left = "Left" "Kpad4"
Turn_Right = "Right" "KPad6"
Turn_Around = "BakSpc" ""
Strafe = "LAlt" "RAlt"
Strafe_Left = "," ""
Strafe_Right = "." ""
Jump = "A" "/"
Crouch = "Z" ""
Run = "LShift" "RShift"
AutoRun = "CapLck" ""
Open = "Space" ""
Weapon_Fire = "LCtrl" "RCtrl"
Weapon_Special_Fire = "X" ""
Aim_Up = "Home" "KPad7"
Aim_Down = "End" "Kpad1"
Aim_Center = "KPad5" ""
Look_Up = "PgUp" "Kpad9"
Look_Down = "PgDn" "Kpad3"
Tilt_Left = "Insert" "Kpad0"
Tilt_Right = "Delete" "Kpad."
Weapon_1 = "1" ""
Weapon_2 = "2" ""
Weapon_3 = "3" ""
Weapon_4 = "4" ""
Weapon_5 = "5" ""
Weapon_6 = "6" ""
Weapon_7 = "7" ""
Weapon_8 = "8" ""
Weapon_9 = "9" ""
Weapon_10 = "0" ""
Inventory_Use = "Enter" "KpdEnt"
Inventory_Left = "[" ""
Inventory_Right = "]" ""
Map_Toggle = "Tab" ""
Map_Follow_Mode = "F" ""
Shrink_Screen = "-" "Kpad-"
Enlarge_Screen = "=" "Kpad+"
Send_Message = "T" ""
See_Coop_View = "K" ""
See_Chase_View = "F7" ""
Mouse_Aiming = "U" ""
Toggle_Crosshair = "I" ""
Next_Weapon = "'" ""
Previous_Weapon = ";" ""
Holster_Weapon = "ScrLck" ""
Show_Opponents_Weapon = "W" ""
BeastVision = "B" ""
CrystalBall = "C" ""
JumpBoots = "J" ""
MedKit = "M" ""
ProximityBombs = "P" ""
RemoteBombs = "R" ""
;
;
[Controls]
;
;
;Controls
;
;ControllerType
; - Keyboard - 0
; - Keyboard and Mouse - 1
; - Keyboard and Joystick - 2
; - Keyboard and Gamepad - 4
; - Keyboard and External - 3
; - Keyboard and FlightStick - 5
; - Keyboard and ThrustMaster - 6
;
;
ControllerType = 1
JoystickPort = 0
MouseSensitivity = 32768
ExternalFilename = "EXTERNAL.EXE"
EnableRudder = 0
MouseAiming = 0
MouseAimingFlipped = 0
MouseButton0 = "Weapon_Fire"
MouseButtonClicked0 = ""
MouseButton1 = "Move_Forward"
MouseButtonClicked1 = "Open"
MouseButton2 = "Weapon_Special_Fire"
MouseButtonClicked2 = ""
JoystickButton0 = "Weapon_Fire"
JoystickButtonClicked0 = ""
JoystickButton1 = "Strafe"
JoystickButtonClicked1 = "Inventory_Use"
JoystickButton2 = "Run"
JoystickButtonClicked2 = "Jump"
JoystickButton3 = "Open"
JoystickButtonClicked3 = "Crouch"
JoystickButton4 = "Aim_Down"
JoystickButtonClicked4 = ""
JoystickButton5 = ""
JoystickButtonClicked5 = ""
JoystickButton6 = "Aim_Up"
JoystickButtonClicked6 = ""
JoystickButton7 = ""
JoystickButtonClicked7 = ""
MouseAnalogAxes0 = "analog_turning"
MouseDigitalAxes0_0 = ""
MouseDigitalAxes0_1 = ""
MouseAnalogScale0 = 65536
MouseAnalogAxes1 = "analog_moving"
MouseDigitalAxes1_0 = ""
MouseDigitalAxes1_1 = ""
MouseAnalogScale1 = 65536
JoystickAnalogAxes0 = "analog_turning"
JoystickDigitalAxes0_0 = ""
JoystickDigitalAxes0_1 = ""
JoystickAnalogScale0 = 65536
JoystickAnalogAxes1 = "analog_moving"
JoystickDigitalAxes1_0 = ""
JoystickDigitalAxes1_1 = ""
JoystickAnalogScale1 = 65536
JoystickAnalogAxes2 = "analog_strafing"
JoystickDigitalAxes2_0 = ""
JoystickDigitalAxes2_1 = ""
JoystickAnalogScale2 = 65536
JoystickAnalogAxes3 = ""
JoystickDigitalAxes3_0 = "Run"
JoystickDigitalAxes3_1 = ""
JoystickAnalogScale3 = 65536
GamePadDigitalAxes0_0 = "Turn_Left"
GamePadDigitalAxes0_1 = "Turn_Right"
GamePadDigitalAxes1_0 = "Move_Forward"
GamePadDigitalAxes1_1 = "Move_Backward"
;
;
[Comm Setup]
;
;
ComPort = 2
IrqNumber = ~
UartAddress = ~
PortSpeed = 9600
ToneDial = 1
SocketNumber = ~
NumberPlayers = 2
ModemName = ""
InitString = "ATZ"
HangupString = "ATH0=0"
DialoutString = ""
PlayerName = "CALEB"
RTSName = "BLOOD.RTS"
RTSPath = ".\"
UserPath = ".\"
PhoneNumber = ""
ConnectType = 0
CommbatMacro#0 = "I love the smell of napalm..."
CommbatMacro#1 = "Is that gasoline I smell?"
CommbatMacro#2 = "Ta da!"
CommbatMacro#3 = "Who wants some, huh? Who's next?"
CommbatMacro#4 = "I have something for you."
CommbatMacro#5 = "You just gonna stand there..."
CommbatMacro#6 = "That'll teach ya!"
CommbatMacro#7 = "Ooh, that wasn't a bit nice."
CommbatMacro#8 = "Amateurs!"
CommbatMacro#9 = "Fool! You are already dead."
PhoneName#0 = ""
PhoneNumber#0 = ""
PhoneName#1 = ""
PhoneNumber#1 = ""
PhoneName#2 = ""
PhoneNumber#2 = ""
PhoneName#3 = ""
PhoneNumber#3 = ""
PhoneName#4 = ""
PhoneNumber#4 = ""
PhoneName#5 = ""
PhoneNumber#5 = ""
PhoneName#6 = ""
PhoneNumber#6 = ""
PhoneName#7 = ""
PhoneNumber#7 = ""
PhoneName#8 = ""
PhoneNumber#8 = ""
PhoneName#9 = ""
PhoneNumber#9 = ""
PhoneName#10 = ""
PhoneNumber#10 = ""
PhoneName#11 = ""
PhoneNumber#11 = ""
PhoneName#12 = ""
PhoneNumber#12 = ""
PhoneName#13 = ""
PhoneNumber#13 = ""
PhoneName#14 = ""
PhoneNumber#14 = ""
PhoneName#15 = ""
PhoneNumber#15 = ""

== glidos.ini
Name: Blood
Executable: E:\Blood\myblood.bat
ControlJudderFix: 1
Resolution: 3
FullScreen: Yes
BloodFix: Yes

=== E:\Blood\myblood.bat
nolfb.com
3dfx.exe

-- messages when Glidos launches DOS screen for blood
VDMSound DOS loader, version 2.01 (Aug 04 2001)
Copyright (C) 2000-2001 Vlad ROMASCANU.

VDMSound is covered by the GNU Public License (GPL), version 2 or later, as
published by the Free Software Foundation, Inc. (http://www.fsf.org/).

Loading 'VDDLoader.dll'...
Successfully loaded & initialized (hVDD = 0x01).

E:\BLOOD\>nolfb.com
NOLFB by Ken Silverman (advsys.net/ken) 09/21/2002
E:\BLOOD\>set BUILD_640X480=1

E:\BLOOD\>set BUILD_CONVTEXTURES=1

E:\BLOOD\>set BUILD_GAMMA=1

E:\BLOOD\>set BUILD_RESAMPLE=1

E:\BLOOD\>pause
Press any key to continue . . .

[ then I get a new dos screen with the 3dfx alpha warning message, and hit space to continue ]

Do you have nView desktop manager enabled? If so disable it. On my system nView stops v1.21 of Glidos working, although v1.22 seems to struggle on.

nView was enabled, disabled it.

Unfortunately still same symptoms (frozen).

I attach a screenshot of the Blood menu screen I get to.

This time I managed to CTRL-ALT-DEL, and kill the glidos task. The PC is still almost non-responsive, and that is when I found that NTVDM process is consuming 99% of the CPU cycles. By killing that from task manager I could recover my PC without needing to reboot.

Any other diags for VDM or glidos I can turn on to provide more info (I've already given the VDM log which has some warnings)

I assume others have gotten the retail version of Blood to work?

thanks!

Otipher

Are you sure that sound is disabled?

Have you tried Blood without GliDos?

Video: 320X240 (NO VESA MODES)
Sound/Music: Set to none

I have tried a couple of times in the past as I was playing with different options. I'll try again. For clarity. are you suggesting I try running Blood without VDMS & NOLFB (just XP compat) or with one or both of these.

I'm not Sure that sound is disabled in Blood even though I have configured it (look at the config file I posted). If all else fails, perhaps I'll try editing the blood cfg to set fxdevice and musicdevice to zero or something...

Otipher

Does "frozen" mean the blood isn't dripping, or just no response to key input?

No dripping, or any other kind of animation in the menu.

Here is one curious thing -

1. I configure "no sound fx, no music" in setup, FXDevice = 13, MusicDevice = 13 in blood.cfg, menu is exactly as shown in jpg

2. I configure "sounblaster fx, music soundblaster" in setup, then FXDevice = 0, MusicDevice = 0 in blood.cfg, and menu is frozen but the top option (New Game) is highlighted.

So enabling/disabling sound makes a difference as to whether I get a default menu selection highlighted ?!

Playing around with Blood without glidos or VDM, I get the following:

1. use setup to set 320x200 non-VESA mode (ScreenMode=2 in blood.cfg).
Ran Blood.exe, get message "using setup file: BLOOD.CFG", then screen clears and is totally black/blank - need to CTRL-ALT-DEL and kill blood process

2. use setup to set 320x200 VESA mode (ScreenMode=1 in blood.cfg).
a. Ran blood.exe, get message "using setup file: BLOOD.CFG", then DOS box is killed and I'm back to windows
b. created "blood.bat" with "nolfb.com, blood.exe" - ran blood.bat, get message "using setup file: BLOOD.CFG", then screen clears and is totally black/blank as for (1) above - need to CTRL-ALT-DEL and kill blood process

So it seems that I cannot run Blood in any meaningful way without a Glidos/VDM environment.

Otipher

I'm afraid I have no idea. All I can say is you are doing the right sort of things. Randomish experiments sometimes uncover the cause of these problems.

It is strange that you see the first screen of blood and then nothing, because that screen is built of load od little triangles. Blood has to get a long way into its initialisation and Glidos has to do a lot of work to display that. It must be that Glidos has sent the first frame load of triangles and a BufferSwap command, folowed by confirmation request to the server, and it is stuck waiting for the confirmation response. One direction of the communication pipe must be stuck. There's a problem a bit like this with ATI card, when in TR1 you hit ESC to get the menu. I might be able to come up with some debugging code that might locate the problem.

Oh one silly suggestion: have you tried clicking the mouse. Sometimes that can activate a window, and start things going. Also the ESC key, but that can sometimes throw you out of the game.

thanks, the mouse and the ESC key don't help (already tried).

I'm ready to expend some effort to figure this out, so if there are any debugging versions of Glidos you want to run by me, I'm game.

Any of those DMA warning messages in the VDM log worthy of investigation?

Otipher

New information.

Installed Blood on my second computer, and had much more success on that machine.

One noteworthy difference is that this 2nd computer (Dell) has Directx 8.1 rather than the Directx 9.0a of my main PC and gaming machine - see dxdiag highlights below.

Tried a bunch of tests on this second PC:

1. sound disabled, run blood.exe w/o Glidos, runs in 320x200 mode, menu works, start new game, cut-scene plays, game begins - everything is good but no sound

2. as above, but with SoundFX set to Soundblaster, IRQ7, others paras default. DOS window quits in late Blood initialization and dumps me back to windows (probably expected behavior with no sound emulation)

3. sound disabled, run setup to configure VESA modes. Tried to launch Blood from Glidos (glidos.ini set to launch 3dfx.exe). Shows blood initialization messages, then game window killed and back to windows.

4. sound disabled, run setup to configure VESA modes. Tried to launch Blood from Glidos (glidos.ini set to launch blood.bat which contains nolfb.com,3dfx.exe). Shows blood initialization messages, then game window killed and back to windows.

So my summary is:

A. on my main PC, something is preventing blood from running even in 320x200 mode w/o Glidos. Maybe this is the reason Glidos also does not work with it. If there are any diags for Glidos that could help understand what is wrong, bring it on!

B. on my second PC, blood works in 320x200 no sound mode. However, it still doesn't work with Glidos or with sound. Note that Glidos on my second PC probably isn't registered (I only bought one license) so I don't know if that will cripple Blood play or not?

I would appreciate help with either getting Blood to work on either machine, but given this forum is about Glidos, maybe I should only hope for help with B...

thanks to all for the help so far.

Otipher

=== dxdiag of second PC =======
Operating System: Microsoft Windows XP Home Edition (5.1, Build 2600) Service Pack 1 (2600.xpsp1.020828-1920)
Language: English (Regional Setting: English)
System Manufacturer: Dell Computer Corporation
System Model: Dimension 4300
BIOS: DELL - 6
Processor: Intel(R) Pentium(R) 4 CPU 1.60GHz
Memory: 256MB RAM
Page File: 173MB used, 444MB available
Primary File System: n/a
DirectX Version: DirectX 8.1 (4.08.01.0810)

Card name: 32MB ATI Rage 128 Ultra
Manufacturer: ATI Technologies Inc.
Chip type: RAGE128 PRO II, (AGP 4X/PCI)
DAC type: Internal DAC (350Mhz)
Display Memory: 32.0 MB
Current Mode: 1024 x 768 (32 bit) (100Hz)
Monitor: Dell D1025TM
Monitor Max Res: 1600,1200
Driver Name: ati2dvaa.dll
Driver Version: 6.13.3279.0000 (English)
DDI Version: 8 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 9/27/2001 00:33:36, 297120 bytes

Description: SB Live! Audio [DCE0]
Device ID: PCI\VEN_1102&DEV_0002&SUBSYS_80401102&REV_05
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.01.0244 (English)
Driver Attributes: Final Retail
Driver Signed: Yes
Date and Size: 3/22/2002 13:09:40, 835636 bytes

Main PC:

Usually the failure of DOS games to load under NT is caused by monitoring programs such as "Motherboard Monitor" and the like. Motherboard Monitor was fixed a couple of vers back but it's likely that another program could be causing the same symptomps. Do you have any other DOS games like Duke3D, Shadow Warrior, or any other DOS games? Doom, Heretic, Wacky Wheels...etc...etc.

Second PC:
Bleh, Rage 128. It looks like those drivers didn't come with XP...perhaps on a CD or something? Any other OGL games working properly on that computer? What would be best is if you could try out OpenGlide on a Windows Glide game. That would tell us if OGL was working properly on your system. Then we could at least eliminate the video equation.

Main PC:

Closed down everything (zonealarm, norton virus, display managers etc.), killed a bunch of processes in task manager and tried Blood again. Symptoms of problem still the same.

I thought I saw a post on this forum recently where there was speculation that DX9 had broken some DOS compatibility for old games? I was wondering about that, although that may not be the real problem.

I have Tomb raider 1 working through Glidos on this machine, which I think fits into your category of DOS games? It hangs on exit from the game (have to reboot the PC) but otherwise plays fine (cut-scens, sound, action etc.).

Second PC:

Yeah, the Rage 128 is nothing special, came with the Dell. Thats why I don't use it for gaming. I think I downloaded updated drivers from Dell's site long ago.

Serious Sam configured for Glide works fine on this PC. Also Tomb raider 1 plays fine when configured with Glidos (that uses Openglide right?). TR1 also doesn't hang on exit like it does on my main PC.

Any chance older versions of Glidos may work better with Blood on second PC?

Otipher

Hmmm, GF4 in the main PC and an ATI Rage 128 in the other.....

Not the best options for VESA...

When you tried Blood and had it configured for VESA...were you using any resolutions above 640X480? Some GF4's have problems with Build games at displaying resolutions above 640. As for the ATI 128, I've never games with those in NT using VESA so I'm unsure of it's compatibility there.

I set resolutions to 640x480, no joy.

On my main PC I tried Glidos 1.2 and then came back to 1.22 (no difference). As an FYI, when I went back to 1.2 I forget to register it, and at the "frozen" blood menu screen, I noticed the Glidos logo still spins, even though Blood is "frozen".

I attach a screenshot of something you may already know about, or maybe not - don't know if its relevant. It shows that when Glidos creates a DOS box to launch Blood, the title bar of the DOS box is "TOMB". Does this indicate Glidos is getting confused, or is this just a cosmetic anomaly? I see this artefact on both my PCs.

Something I've been attempting as a diagnostic step, is to supply 3dfx.exe with command line arguments -quick -nocd -nodemo. These are described in bloodhlp.txt. This may eliminate some problem areas. However, I cannot get Glidos to pass these through to 3dfx.exe - I tried both the below:

1. changing glidos.ini to invoke e:\blood\3dfx.exe -quick -nocd -nodemo. Glidos complains that it cannot find the game to launch (it seems to think the options are part of the file path it has to launch?)

2. creating a blood.bat specified to glidos.ini that invokes nolfb.com, 3dfx.exe -quick -nocd -nodemo. when glidos does its stuff, I never see these arguments echoed (always just 3dfx.exe is the command).

I'm also surprised to see that a file glidos.bat seems to get created regularly in the e:\blood directory. Is this file sometimes being called by Glidos to launch blood instead of the one I specify? The content are similar so its not so easy to tell.

Otipher

hmm, interesting.

showthread.php?s=&threadid=31

According to the thread above I don't need it for XP, but the mention of Blood 3D and freezing at startup caught my eye...

Q. When do I need to run CLI2NOP?
A. When most compatibility lists suggest that you do so. Generally speaking, it is a problem that largely affects BUILD engine based games (Duke Nukem 3D, Blood 3D) and other popular games which use the same engine that DOOM, DOOM2, and Hexen use. That is, any game which is a protected-mode application and requires DPMI emulation to be enabled when you attempt to run the game, say, enabled with a utility such as VDMSound Launchpad. So the two factors to pay attention to are:
if it requires DPMI
it freezes / locks up sometimes at "start-up."

When you try VESA modes without Glidos, you still need to use NOLFB.

One thing not to forget is that when you try with Glidos, you get the first frame, and that means a lot of things are working up to that point. That means your OpenGL is probably okay.

Sorry, not much else that might be useful I can think to say.

Well, thanks for support so far anyway.

Did you have any thoughts on my last post prior to the CLI2NOP one where I mentioned the TOMB DOS box title and my question on the role of glidos.bat in the blood directory?

Oitpher

I'm pretty sure I didn't use CLI2NOP on Blood.

One thing I have remembered: VDMSound comes in two parts. There's an installer, and an archive of files that form an upgrade. I use only the former. The one time I tried the upgrade under XP, I got lock ups.

Glidos creates glidos.bat in the target game folder on every invocation. If you specify a .bat file in glidos.ini, then glidos.bat will call your .bat file.