Re: Windowed Mode [message #20135 is a reply to message #19878] |
Tue, 12 June 2007 05:14   |
 |
Keshire
Messages: 1266 Registered: July 2005
|
Administrator
|
|
|
shujyou wrote on Fri, 08 June 2007 19:50 | Okay, I know this is old and I'm not sure bumping is welcome here, but it's better than posting a new topic, so...
I've tried this, and tried using older versions of 3DAnaylze (some website said the new ones wouldn't work) but Fable just crashes.
At first, a black screen came up and a visible program crash window came up. After I spent the last half hour setting my vendor ID and device ID, it crashes (no popup notifying me of that) with this in the event logs:
"Faulting application fable.exe, version 25.7.13.149, faulting module unknown, version 0.0.0.0, fault address 0x00000000."
Since other people have got it to work, I'm wondering if my version of Fable was released later or something. (If there're more than one version of TLC, how would I tell?)
... oh. And I tried another program first, D3DWindower (which I'm fairly familiar with) but I get the same error.
|
Tends to be a video card issue.
Apathy Cannot Inspire.
Ambivalence cannot lead.
Loved me. Feared me.
Changed me. Killed me.
Anything would be something.
But nothing is worst of all.
|
|
|