I recently bought a few Xbox1 games from a used game store about 2 weeks ago, one of them was Dead to Rights. I already own the game, but I bought another copy since my other copy of it is out of reach (in another state with most of my Xbox games). So I dump the game, thinking "Yeah, now I can finally fix that crash I couldn't track before...". As soon as I get ingame, what happens? BSOD. Wtf? Cxbx hasn't given me a BSOD since that time I tried to emulate Wolfenstein back in 2004-05ish! The worst part is, I have no idea what's causing it. I think it's an issue with XP. It keeps bringing up win32.sys, so it's probably kernel related...
Back when I had vista, this wasn't a problem. I never thought I'd say it, but I actually do miss vista a little. While I and most other users hated it, Cxbx loves it with a passion, as it's the most compatible version of Windows running it. I tried Win7 and 8, and none of them ran Cxbx as well as Vista did.
"This game is on PC, who cares?" I do. This is a battle for completion, and I don't have as many games using XDK 4432 as I'd like, so...
Meh, I'm not going to worry about it too much, so I'll just have to work on some other games until I either fix what's wrong with this laptop or get a new PC altogether (the latter would be nice). Maybe I'll just keep bashing away at Otogi or something like that.
Maker Pro: Soylent Supply Chain
3 days ago