Nameless Voice on 2/5/2009 at 19:40
Quote Posted by Kyle2k
but it seems to me the prepatched EXE points to the ddfixGui executable in order to run
Of course it doesn't. The prepatched exe is the game exe with the hex changes to enable DDFix already applied. The GUI just automates the application of these changes. Once DDFix is installed, you no longer need the GUI.
Quote Posted by Kyle2k
and I still receiving the same DX7 error message over and over again.
Sounds like a case of Didn't Read The FAQ:
(
http://www.ttlg.com/forums/showthread.php?t=121449#NeedDirectX7) I get the error "DirectX version 7 or higher is not installed" when starting the game - how do I fix this?
sNeaksieGarrett on 2/5/2009 at 23:01
Quote Posted by Kyle2k
do you remember the old fixed exe for the old GeForce MX400's black screen issue, posted here a long time ago?
since the game installs and run fine (even the movies and sound), I think this old EXE could make Thief2 compatible with W7...but I can't find it anymore.
Afraid I don't know.
NV, I don't think he's missing ddfix.dll because it comes with ddfixGUI.exe, and he already stated that the files are in his directory.
He's got a unique situation apparently.:erg:
Kyle, I'm assuming you've already used the prepatched exe and it's not working?
bikerdude on 6/5/2009 at 00:11
Im running Windows 7 RC, and so far its the same as the beta, thief 1/2 are fine (still no fog though), Ive just disabled DEp and am gonna see if T3 now works or not...
Aja on 6/5/2009 at 03:08
I ran Thief 3 on the beta with no problem. The only time DEP got in the way was when I tried to use a particular no-cd crack. A different patch worked fine.
Dahenjo on 8/5/2009 at 13:59
Is anyone else noticing that Darkloader takes a very long time to start?
The logo comes up right away, but then it takes about 3 minutes for the application window to appear. Once it does it works normally though. I'm now running Win7 RC but it did the same thing with the beta.
I usually don't reinstall T1/T2 or Darkloader, somewhat like Bikerdude mentioned, and everything works fine. But I've also tried reinstalling Darkloader from scratch and end up with the same problem. I think it has to do with the size of darkloader.ini - on a fresh install it'll start right up, but after you point it to the FM directories (~600 FMs) the INI file gets huge and then the long startup issue begins. So it must have to do with parsing the INI data, which even in Vista was never an issue.
If others are having the same problem, maybe Tom/Telliamed could look into it. Thanks for any feedback, fellow Taffers.
bikerdude on 8/5/2009 at 16:12
Quote Posted by Dahenjo
Is anyone else noticing that Darkloader takes a very long time to start? The logo comes up right away, but then it takes about 3 minutes for the application window to appear.
you may need to run the executable in "compatability mode", right click on 'darkloader.exe' and click on the compatability tab, then select 'windows xp sp3'
Dahenjo on 8/5/2009 at 20:29
Quote Posted by Bikerdude
you may need to run the executable in "compatability mode", right click on 'darkloader.exe' and click on the compatability tab, then select 'windows xp sp3'
Thanks Biker ... are you using Darkloader, if so is there any lag on your system?
Should have mentioned I've already tried compatibility modes as well as the various 'Settings' items on the same tab; even shut off indexing for the file under the General tab/Advanced, but none of that makes any difference. I've never needed any of that stuff under Vista or XP for DL (or T1/T2 for that matter) to start in 2-3 seconds and run fine.
When I setup DL pointing to test folders containing only 20 FMs, it starts up in 5-10 seconds (as opposed to 3
minutes for all 600+ FMs), so I'm pretty sure the size of the darkloader.ini somehow correlates to the problem.
Btw, system is AMD Phenom II 940 Quad-core @3.2GHz, 4 GB 1066 RAM, GeForce 9800 GTX+/512MB, 64-bit Win7 RC. The beta was 32-bit and I had the same issue with it. I have a dual-boot on this pc, and on the XP side everything is perfect, so I'm thinking it must be OS related.
I'd appreciate hearing if others *
aren't* having this problem with DL 4.3 under Windows 7, then I'd know it's something specific to my installation. Thanks much!
bikerdude on 8/5/2009 at 20:54
Quote Posted by Dahenjo
I'd appreciate hearing if others *
aren't* having this problem with DL 4.3 under Windows 7, then I'd know it's something specific to my installation. Thanks much!
I have been using gLoader, but I will install darkloader and see how it works..
Telliamed on 13/5/2009 at 00:47
(
http://whoopdedo.org/projects.php?dl) DarkLoader 4.3b1 is compatible with Windows 7
If anyone cares (I don't) to file a bug report with Microsoft, it's an issue with the (Read/Write)PrivateProfile* functions. The problem will likely occur in other 10+ year-old apps. Though perhaps not as significantly as DL which abuses the INI file quite a bit.
I've often wondered if the "compatibility" tab, like Lord Bafford's library, isn't just for show.
Nameless Voice on 13/5/2009 at 01:29
Telliamed: What exactly is the problem with the PrivateProfile functions? Are they being discontinued?
I generally prefer those functions to using the registry (I like portable programs), and was even considering using them in a script at some point.
