[Zaragon]

Okay, this is annoying. Alt-tab from diablo 2 results in an instant crash.

Quote:

EventType: 0xEA - Thread Stuck in Device Driver

//
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.

I haven't had time to check and see if Diablo II is the only game that does it.

Also, I'm able to mostly fix the mouse feel by setting the following keys:

MouseSensitivity 0
MouseSpeed 1
MouseThreshold1 7
MouseThreshold2 8

However the fix disappears on the next boot... but the values in the registry stay the same! WTF?

System:
WinXP Home Edition
Athlon 750
512MB RAM
DPT 2144UW SCSI Host Adapter
UltraPlextor Wide CD ROM
Voodoo 5500 video board (I have a set of 3rdparty drivers from voodoofiles).

[Zaragon]

Couple more data points:

Alt-tab from Starcraft works fine.

Alt-tab from Need for speed High Stakes correctly brings you back to the desktop, but upon returning to the game the monitor is blank. I can still alt-tab back to the desktop again and kill it. Considering Win98 simply ignored alt-tabs in NFS:HS, I suppose this is acceptable.

I think I might have figured out what my problem is (though it is based on a very small sample set, I admit). WinXP, unlike win98, tries to draw the alt-tab box (with the list of applications to switch to) while you are still inside the game, as opposed to waiting until the desktop is redrawn. This appears to work in directdraw and direct3d games, but causes a infinite loop crash when in Glide mode.

I will test my hypothesis tonight by setting D2 to run in Direct3D mode and see if it still crashes. If not, I will pursue the problem further on the voodoo boards because at that point it is really not an XP issue...