First part: I right clicked, Properties, it didn't allow me to change the path.

Second part: I don't know what you mean by 'exit' statement? I didn't see Exit if that's what you meant.

3rd part: That fixed the fullscreen issue, but it wasn't that big of a deal, I'd just Alt+Enter as I'd mentioned.

Game still crashes randomly.

On your Shortcut tab, there is a section labeled "Target:" The information in this box may vary between your system and mine, thus I included an [install path] placeholder. I apologies for the confusion.

Just to explain what is going on within "Target:"
You probably see something like: "C:\Program Files\GoG.com\Blood\DOSBOX\dosbox.exe" -conf dosboxBlood.conf -noconsole -c "exit", or you did before you took out -noconsole as directed earlier.

The first part: "C:\Program Files\GoG.com\Blood\DOSBOX\dosbox.exe", tells windows "This is the application I want to run." Now, each exe file, or even scripts can be given specific options to launch with, these are called the "Command Line Parameters" and they are what the -conf, -noconsole and -c switches represent. Together, they tell Windows "I want to run DOSBox with these options."

When Blood, or Redneck Rampage crash on you, if you have the -noconsol, and -c "exit" parameters set in the target of the shortcut, DOSBox just assumes you are done with the application and will close itself out, so you observe that it just crashes to the desktop. If they were not there, you might be presented with a flashing C:\> prompt and some sort of statement like "src\sound.cpp(516): Playback failed, possibly due to an invalid or conflicting IRQ"

We are trying to determine the nature of the crash, and if DOSBox just closes itself out, you won't get a chance to see if there are any clues as to what is going on.

"exit" is a command line statement that will close DOSBox, if it was there under [Autoexec], it would execute at some point and would still cause the same result as the -noconsole and -c "exit" switches, I mentioned before.

In your dosboxBlood.conf file, under the [autoexec] section at the bottom, you should see something akin to:

@ECHO OFF
mount C "."
imgmount D game.inst -t iso
c:
cls
BLOOD.EXE
exit

You might want to remove the "@echo off" statement if it is there, you can comment it out with a "#" symbol so you can restore it when you are done. the same thing with the "cls" and "exit" statements. These will all obfuscate what messages are displayed at command prompt.

so you will have:

# @ECHO OFF
mount C "."
imgmount D game.inst -t iso
c:
# cls
BLOOD.EXE
# exit

Appreciate the effort, but it's still crashing. Just I get to the Crystal Lake level too and hear the Ch Ch Ch Ha Ha Ha.

Adding the # to the conf file seemed to work, it loaded differently. But it still crashes and didn't give me a reason why.

I also deleted the "-noconsole and -c switches" from the Target and no difference.

Okay, Update: After following DustyStyx's advice, I changed the graphics mode back to Overlay and it seems to be working. I played through an entire level without it crashing. So far so good, don't want to jynx myself.

It's good to hear that you were able to play a level through to completion, but we want to be sure that the issue is resolved and it wasn't just a fluke.

When you say it still crashes, are you now presented with the flashing C prompt? Or does DOSBox still close out completely?

If it closes out completely, you might want to try upgrading your version of DOSBox if you haven't done so already. The version GoG included with Blood is .73, the current stable release is .74, and there has been a recently released SVN version that addresses some CD playback issues.

I spoke a little too soon :( in that I have the same issues with Cryptic Passage. I never got a chance to play that expansion.

I might try upgrading Dosbox later. I assume I just download the latest version and place it in the Dosbox/Blood folder, right?

Pretty much, yeah. Make a backup of the original DOSBox folder first, but copy the new dosbox.exe and associated DLL files over top those found in your blood\DOSBOX folder.

Well, I jynxed myself. Even though I was able to get through 2 levels last night without a single crash, it's been crashing like crazy.

I tried updating to the latest Dosbox and it crashes even more. Only good to come of this is that I was able to get some sort of error message one time.

http://i1103.photobucket.com/albums/g466/3stest2501/dosboxbuggg2.jpg

Is there any troubleshooters with GOG that could help? This is the most annoying and random bug I have ever seen.

Well, you did get a screenshot of it crapping out on you, so that's good. It means that DOSBox isn't dying, so we can tweak it so Blood will work better for you.

I noticed that your screenshot is still showing that it is running 0.73, when you upgraded, did you just install to your Program Files\DOSBox-0.74 folder? You will want to copy the entire DOSBox-0.74 folder into your Blood folder, then rename the original DOSBOX folder something like DOSBOX-old, and then rename the new DOSBox-0.74 to DOSBOX. Just copying overtop might have missed some DLLs that could be causing an issue. Copy and rename your folders.

I'd limit the number of cycles
so change cycles=max to
cycles=max limit 60000

of course you can change that number. It was an example in order to determine if that weird (too high) cycle counts cause problems as you have a powerful machine.

Sorry for the delayed response. Yes, that's what I meant. However if you just copy the folder across and you don't rename the new folder from DOSBox-0.74 to take the place of the old folder, the shortcut will still point to the old 0.73 DOSbox.exe file. You can tell what version you are running by checking the top left corner of your DOSBox window when it is running. In your screenshot, it still displays 0.73.

What folders do you have in your Blood directory now?

Did that, STILL crashes. I have some juicy pics showing off two occasions where it crashed.

http://i1103.photobucket.com/albums/g466/3stest2501/dosboxcrash.jpg

This one's weirder. I was playing, and for no reason at all it went to this prompt but I could still hear the music from the game playing.

http://i1103.photobucket.com/albums/g466/3stest2501/dosboxbug5.jpg

I am really pissed that GOG does not have any kind of tech support. There is no reason for this game to crash constantly unless it's compatibility issue with Win 7. Because I actually downloaded a torrent of Blood with Dosbox that was scripted like the GOG release, and it worked perfectly on my old crappy XP64 setup.

Try disabling all sound in the game configuration and then playing the game.

If that works then your sound settings are misconfigured