Forum Replies Created
-
Posts
-
I’m…rather embarrassed that I forgot to try that. Lo and behold, when I put it in compatibility mode (Win XP SP2 for future reference) it works just fine!
I guess it’s something to do with Win 10 that loader.exe doesn’t like.
Schmatzler, I ran I-War on my previous PC (which also had Win 10) just fine. I guess I just forgot to put it in comp. mode this time. It looks like it just needs compatibility mode turned on, and then it pretty much works fine. Thanks for all your help, guys!
I’m…rather embarrassed that I forgot to try that. Lo and behold, when I put it in compatibility mode (Win XP SP2 for future reference) it works just fine!
I guess it’s something to do with Win 10 that loader.exe doesn’t like.
Schmatzler, I ran I-War on my previous PC (which also had Win 10) just fine. I guess I just forgot to put it in comp. mode this time. It looks like it just needs compatibility mode turned on, and then it pretty much works fine. Thanks for all your help, guys!
I tried both solutions- none worked. I probably should have explained the problem better anyway… :blush:
I load up the main menu fine, and all the movies before that play correctly. It’s when I try to actually play that I encounter a problem. When I try to, for instance, enter Instant Action, I’ll get the loading screen, and the bar will quickly fill up maybe 5% before I get the error message.
I tried both solutions- none worked. I probably should have explained the problem better anyway… :blush:
I load up the main menu fine, and all the movies before that play correctly. It’s when I try to actually play that I encounter a problem. When I try to, for instance, enter Instant Action, I’ll get the loading screen, and the bar will quickly fill up maybe 5% before I get the error message.
My graphics drivers are fully up-to-date, but here’s the log file. I copy/pasted it into a text file because the site apparently doesn’t like the .log file extension.
My graphics drivers are fully up-to-date, but here’s the log file. I copy/pasted it into a text file because the site apparently doesn’t like the .log file extension.
You’ve got a point there. It is useful to know where that stuff actually is though. Thanks for the info!
