Howdy.

I've got a small problem with Monolith's Blood on Dosbox. I'll make the rounds and fill in the list from this forum as best I can.

• 1 Motherboard - Can't remember, sorry.
  2 Processor type and speed - Intel Core 2 Quad Q95500 2.83 GHz
  3 Amount and type of RAM - Not sure on type, 3.25 GB (4GB)
  4 Video board w/ RAM amount and type - Radeon 4870 1GB
  5 Sound board - Just your average onboard job
  6 Operating system - Windows XP SP 3
  7 Game name (and version, if applicable) - Blood, 1.21 OUWB
  8 Description of problem (be detailed: saying "it's jerky" doesn't help, saying "the player sprites seem to be jerky when I'm pressing any of the arrow keys" does) - See below
  9 Reproducibility of problem (always, only once, always but only on a specific level, etc.) - See below
  10 Sound mode used - sblaster
  11 Video mode (Software, OpenGL, Direct3D, or Glide, and resolution) - overlay. Odd, I thought I'd changed it to opengl. Trying for 800x600
  12 Version of emulator (for VDMSound, probably 2.0.4 or 2.1.0; for DOSBox, 0.58+) - Dosbox 0.74
  13 Steps already attempted to solve the problem (please say you've read the README if you haven't, and READ IT IF YOU HAVEN'T!) - I've read the readme...

Hopefully the techies of the board can help me out of this. With a bit of luck, maybe this will assist other people in beating this problem.

Long story short, I've tinkered around a bit with Visual Studio in the past and because I tend to veer towards older games and aim for widescreen support in them, I've often hit a few speedbumps on the way. I've noticed that since the installation of Visual Studio the crashing for most anything has resulted in a window with some message about a JIT compiler and it offers me the unique opportunity to debug the problem. Great.

Perhaps it's nothing, but I could swear that the presence of Visual Studio seemed to encourage errors of this sort, though don't take that as a sign that the machine's faulty, as I can run a handful of things without a blip for days.

Yes, that's the short version.

Now, all was fine and dandy until Dosbox 0.74's release. I could run Blood with impunity, but upon running Blood in Dosbox 0.74, I am greeted with this message after about ten or so minutes of play. This problem repeats.

In a brazen effort to combat this, I actually deleted my Visual Studio, but to no avail; the problem persists in the form you see above.

Any assistance or direction would be appreciated!

P.S. Reverting to a previous Dosbox version is not desirable, as Blood receives a notable performance boost with the upgrade.

P.P.S. I am actually willing to format the machine in an effort to alleviate this, but I'm hoping that's a last resort.

P.P.P.S. Not playing Blood is not an option.

Take care, everyone!