For some reason Blood keeps crashing to desktop. It seems to happen at random and it started doing this after playing a couple days with out any problems. I'm running the game on the default resolution and tried using the graphic set up to find a mode that worked. Still no luck. When I tried to run the game under windows 98 compatibility it would not start. Dosbox started, the dosbox window closed and that was it. Dosbox is still running in the background, but Blood never starts. Last thing I tried was downloading dosbox and installing it over the dosbox that came with the game. Same problem, Blood still crashed to the desktop.

I have tried every thing I can think of at this point. Any one else have some ideas?

It might just be DOSbox causing your issue.

Can you just run DOSBox.exe on it's own? It should just come up as a CMD like environment, with a Z:\> prompt.

On a side note, if you are running Blood in XP, there are ways to get Blood.exe itself to run, rather than to run it under emulation (DOSBox).

Try the BuildXP guide.

In the start menu find Blood folder, select "Graphics mode setup". Change "overlay" to something else. Usually Direct3D and OpenGL work fine, while "Overlay" cause crash. 99% it's the case.
@DustyStyx: If you run a DOS game on winXP you get poor performance and no sound - hardly an option.

Its not dosbox. I can run other games fine and so far blood is the only gave any kind of trouble.

Changing the video to direct3d or opengl has not fixed the problem as I stated in my first post.

I'm starting to think it sound related. Somes times when I play all I can here is the "cd" music off the hard drive. There have been a couple times the opening cut scene for the first episode didn't have sound at all. I'm going to mess around with it when I get home. I'm going to disable to the audio tracks and work on getting the cut scenes working with sound.

If you follow the BuildXP guide, which covers how to get the sound and video setup correctly, you can get better a performance under XP than you can out of DOSBox because it's running natively rather than under emulation. The only thing that DOSBox does better is that it offers an emulated network environment for BloodBath that is not present in XP. True, the guide was written circa XPSP2 and has more issues with SP3, but they can be dealt with.

@Satyr000, have you tried upgrading to DOSBox 0.74? You shouldn't have to start DOSBox in 98 emulation mode, they've compiled it to run as a native Win32 application. You could even compile it yourself and get better performance if you felt like doing the research.

There are a number of settings that you can play around with in the DOSBox config file. You can generally find the config file your One Unit Whole Blood.lnk file uses in your Blood directory, it's probably pointing to dosboxBlood.conf. For instance, my shortcut's target is:
D:\Programs\Games\Blood\DOSBOX\dosbox.exe -conf dosboxBlood.conf -noconsole -c "exit"

and it starts in:
D:\Programs\Games\Blood\

The "starts in" settings basically tells DOSBox "start in this directory and use the files located here"

Backup your dosboxBlood.conf and go to town with it in a text editor, try playing around with the sound card entries and perhaps even the video entries.

You know, I've found out that Cryptic Passage crashes while Blood+Plasma Pack works fine. Strange.

Cryptic Passage is "special" in that it was programmed in TurboPascal that and won't run on anything faster than a Pentium 200.

You can get it to run through Blood, just like any other user made mod, by renaming the CPART##.AR_ files to TILES###.ART and point the Blood.exe at the cryptic.ini using the -ini switch.

Actually, solution is simple. Start a new game in Cryptic Passage, save it, exit game, start Blood, load this game - ta-da! - game now runs fine. I wonder why Cryptic Passage has a separate exe at all.
Edit: Well, the only problem that Blood will load wrong levels, so you have to save before the endlevel horned switch, load Cryptic Passage, load game, advance to next level and save again. Not very convenient.
I wonder why GoG haven't fixed it. Description doesn't mention "You need Pentium 2 to access Cryptic Passage add-on".

When I clicked OWU icon. I noticed that the DOSbox window frame saying that It's version 0.72 not 0.74 IIRC. It pops up for a couple of milliseconds or so. So that may be the problem.
GOG needs to update Blood: OWU's DOSbox emulator to 0.74. I think GOG need to check all of the emulators in their games to see if they're up to date.

By running Cryptic.exe inside DOSBox, you won't run into have any CPU clock speed problems, so they wouldn't need to warn you of it.

There are a few small tasks that the cryptic.exe actually performs, but they can be accomplished without it. You can write a batch script that parrots what cryptic.exe does.

save the following into notepad and save it as as cryptic.bat

:: cryptic batch script
REN TILES007.ART TILES007.AR_
REN TILES015.ART TILES015.AR_
REN CPART07.AR_ TILES007.ART
REN CPART15.AR_ TILES015.ART
BLOOD.EXE -ini cryptic.ini
REN TILES007.ART CPART07.AR_
REN TILES015.ART CPART15.AR_
REN TILES007.AR_ TILES007.ART
REN TILES015.AR_ TILES015.ART

Hey, naturally I use dosbox, it's included with the GOG version. And Cryptic Passage is crashing.

I hope to have fixed the crashes with overlay in the next version of dosbox,
but as I don't experience them; it will be a gamble ;)