It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Oi vei. I love this game, but it crashes about a minute after launching. Game runs fine, then about a minute later it crashes back to desktop. I'm running Win 7 64 bit. Quad Core cpu monster rig. And I set the compatibality to XP SP 3 and running it as Admin.

Sucks. I love this game, but I can't get it going. I heard of upgrading dosbox, can someon just go through a step by step on how to do that?

Please help a blood junkie
Are you talking about Blood 1 or Blood 2?

You shouldn't have to set XP compatibility for DOSBox (the emulator running Blood 1), but you will want to be sure that you grant yourself full read,write,execute permissions to the installation folder.

If you are running Blood 2, it might be related to some of the many video card problems that plague the game. Try disabling the DirectX features through the Advanced tab on the pre-launch menu.
I'm playing Blood 1.

Also would like to add that in the minute that the game runs before crashing to desktop, I cannot bind the 2nd mouse button for Alt fire.
Post edited June 20, 2011 by LouisCyphre
Did you put it in XP mode to counteract the crashing? I'm running a core i7, 6 GB ram and Windows 7 x64 w/ GTX 275 no problem.
I've set it to XP compatibility and run it under 7 compatibility. It runs fine for about a minute, I config the controls to a WASD setup, Space for jump, E to activate anything, and it crashes.
change the graphics option (provided by gog) to ddraw
I changed graphics to ddraw and it still crashes. And I changed it to OpenGL and it still crashes.

**Update: Changed graphics to overlay and it seems to work.
Post edited June 21, 2011 by LouisCyphre
Correction: Overlay seems to work for a while, but it soon crashes. Same problem with Redneck Rampage btw.

Also, how do you get this to run in a window? Whenever I run build engine games at fullscreen I start getting a headache.

*Update: Alt+enter fixes the window part of my problem.

But it STILL crashes randomly.
Post edited June 21, 2011 by LouisCyphre
there is still surface for you to try out.
avatar
Qbix: there is still surface for you to try out.
Did that, still crashes randomly.
avatar
Qbix: there is still surface for you to try out.
avatar
LouisCyphre: Did that, still crashes randomly.
I am not sure what is written in the gog shortcut for the game, but if you edit that one, could you remove the -noconsole option if that is present.

Then please check if something appears in the other window around the time it crashes
Post edited June 21, 2011 by Qbix
Did that, went into properties and removed '-noconsole' and it seemed to run fine for about 2 minutes. Then crashes again. Nothing appears. It just crashes back to desktop.

I think the game just doesn't like my system.
avatar
LouisCyphre: Did that, went into properties and removed '-noconsole' and it seemed to run fine for about 2 minutes. Then crashes again. Nothing appears. It just crashes back to desktop.

I think the game just doesn't like my system.
Are you talking about the game or DOSBox?

Try running DOSBox itself. (Download from www.dosbox.com)
Any game in dosbox crashes randomly to desktop. I mentioned earlier that I have the same problem with Redneck Rampage. Someone must know a solution. Blood is my favorite FPS of all time and I just want to play that for a while.
avatar
LouisCyphre: Did that, went into properties and removed '-noconsole' and it seemed to run fine for about 2 minutes. Then crashes again. Nothing appears. It just crashes back to desktop.

I think the game just doesn't like my system.
Did you remove the -c "exit" option as well? Try running it with just the -conf switch

ie: [install path]\dosbox.exe -conf dosboxBlood.conf

Also check the very end of your dosboxBlood.conf file and see if there is an "exit" statement under [autoexec]
While you are in there, you can set your full screen settings as well. Check the very first variable under the [sdl] section at the top and set: fullscreen=false
Post edited June 21, 2011 by DustyStyx