Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Detrivus]

Hey guys,

I'm trying to play DF on my desktop which runs Windows 7 Ultimate.  Everything works fine, except when I try to embark (after setting up dwarf skills, items, etc) the OS kills the process because it appears to freeze, when in fact it's in the process of embarking.  Is there a way to suppress this feature of Windows 7, so that I can play the game in peace?

Thanks for reading.

[SpiralDimentia]

I get that too sometimes, and I use Vista. It does it when I embark, when I save, when I abandon, and VEYR RARELY during gameplay. But I just leave it alone and after a few seconds it comes back and works fine. It hasn't done anything but slightly annoy me so far, though.

[Detrivus]

Yeah, it'd be nice if it just did that but it actually kills the program after long enough.  In other words, unless I choose my map as a 2x2 or something restrictive like that, there's no chance I'll get to play before it kills the program.

This seems like a newer feature, as I had no problem playing it on my old machine which ran Windows XP.  Does anyone know a way to prevent this response?

[BigD145]

Does anyone know a way to prevent this response?

Ask someone at Microsoft?

[DrKillPatient]

My W7 computer is screwed up currently, so I haven't had much time to play DF on it, but I've never heard of or seen that kind of crash before... Do you do anything else, like click the window while it's processing? Or is it left alone, and just crashes to desktop immediately?

Does anyone know a way to prevent this response?

Ask someone at Microsoft?

"Pay hundreds of dollars for a simple upgrade in order to disable this function!"
But seriously, I doubt there's a solution like that. Vista and onward have been involved in the 'not responding' fiasco for a while.

[BigD145]

My W7 computer is screwed up currently, so I haven't had much time to play DF on it, but I've never heard of or seen that kind of crash before... Do you do anything else, like click the window while it's processing? Or is it left alone, and just crashes to desktop immediately?

Does anyone know a way to prevent this response?

Ask someone at Microsoft?

"Pay hundreds of dollars for a simple upgrade in order to disable this function!"
But seriously, I doubt there's a solution like that. Vista and onward have been involved in the 'not responding' fiasco for a while.

http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/688e4769-9c84-4826-9b01-9e1af0bdeb67

[Detrivus]

Hmmm... I followed the instructions but none of those entires appear to be in the registry.

[BigD145]

I just did a quick search and threw up a link. I didn't even read the whole thing. I use an XP64 machine as my main.

[Ghills]

Do you have a Nokia graphics card? That seems to be one of the problems mentioned in the other thread.

[Detrivus]

No to the Nokia graphics card... I've got a Radeon 5770.  I'll try some test embarks and watch more closely, see if I can't get a better idea of what's going on.