Jag results may vary, a bunch of those bomb out on Windows because of reading from a bad pointer (the way the blitter code uses memory is quite awful, done for speed but it means it ends getting a pointer to memory then reading from addresses way after it (my original fix to stop tempest 2k writing over it's own ROM was addressing that very issue for writes because once it had the pointer it didn't care if it was ram or rom it was trashing ;-)
I don't see how that's a negative. Fix the blitter bounds checking (or more likely the ALU errors making it go out of bounds, as Ville has been doing) and you have a bunch of games running for a lot less work than the Jaguar driver was previously assumed to need.
