Yandros on 13/5/2009 at 02:59
I don't personally have access to the Win7 DDK/MSDN but know of some who do at work. I can try and find out if they've intentionally deprecated the PrivateProfile fucntions, as opposed to unknowingly breaking them, if it would make any difference. No, I didn't think it would.
Actually now that I think of it, I vaguely remember that they had planned to drop them from Vista, effectively trying to force developers to using the registry. Well, at least it sounds like typical Microsoft behavior...
Nameless Voice on 13/5/2009 at 03:11
I guess it wouldn't be that hard to manually write new ini-handling functions.
Telliamed on 15/5/2009 at 00:29
Quote Posted by Nameless Voice
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.
(
http://msdn.microsoft.com/en-us/library/ms724348(VS.85).aspx)
"This function is provided only for compatibility with 16-bit applications written for Windows."
But I have doubts that anyone in Redmond has laid eyes on that code in a decade. The KB doesn't say anything about the functions having a size limit which DL ran into a while back. That's why I originally had to make 4.3b1.
Quote Posted by Nameless Voice
I guess it wouldn't be that hard to manually write new ini-handling functions.
I went with a homebrew INI parser. But that wasn't too far to go since I already had a parser for Dromed's CFG and STR files. Ended up with a generalized class that handles all three. (Source/CfgFiles.pas if you want to read Pascal.)
I suppose if you want to future-proof your apps you can serialize in XML just as easily. MSXML is standard in Windows these days.
bikerdude on 15/5/2009 at 16:13
Downloading now.
Dahenjo on 15/5/2009 at 20:42
This version completely resolved the delay problem I reported.
I did get a couple of errors after entering the setup paths when you first run Darkloader, which Tom knows about. It then shuts down but re-opened again fine with all my FMs listed and works normally.
Telliamed on 16/5/2009 at 20:18
Quote Posted by Dahenjo
I did get a couple of errors after entering the setup paths when you first run Darkloader, which Tom knows about. It then shuts down but re-opened again fine with all my FMs listed and works normally.
About that...
Quote Posted by Yandros
I don't personally have access to the Win7 DDK/MSDN but know of some who do at work.
"Access violation at address 7713ED87 in module 'ntdll.dll'." (build 7100)
Can you find out what function that's in?
Yandros on 16/5/2009 at 20:35
I'll ask around on Monday.
Kyle2k on 27/5/2009 at 22:54
Dear TTLG friends
I'm not sure if you have noticed, but something wonderful happened:
Windows 7 64bits, version 7127 is FULLY COMPATIBLE with Thief Gold and Thief 2, WITHOUT ANY TRICKS!!!
Almost a month ago I posted here in the TTLG forum: I've managed to install T1 and T2 in W7, the game started without problems...until I tryed to load the first level: all I got was a black screen.
This issue was reported by other friends. I tryed all sort of tricks we all know: "safe texture manager" in user.cfg, old and new fixed EXEs, AND (of course) ddfix (crashed) with the prepatched EXE...nothing worked at all.
I was running Windows 7 64bits, version 7100, with the first release of the nVidia W7 64 drivers (for my 8800GTS 512 graphic card).
A few days ago I installed the new RC version of W7 x64 (v.7127, clean install), with the SECOND release of the W7 nVidia driver...
...and it WORKED!!!
I've managed to run TG and TMA flawlessly, with a 1280x1024 res...
1. without the "user.cfg" trick
2. without ANY of the modifyed game EXEs (posted since the WinXP release)
3. without DDFIX
NOTHING!
Obviously, the multicore issue still there: it's a game compatibility with the multicore CPUs, not with the OS. You still need to set affinity with only one of the CPU cores.
The point is: NEVER in my life I saw a Windows version, since Windows 98, FULLY COMPATIBLE WITH A DARKENGINE-BASED GAME BEFORE!
Please, post your comments!
My system specs:
Intel Core2Quad, Q6600 CPU, Sound Blaster Audigy SE, 3GB RAM, GF 8800GTS 512 graphics, Windows 7 v. 7127.
sNeaksieGarrett on 28/5/2009 at 02:40
I could be wrong, but you're probably just lucky (not trying to bum you, in fact I hope you are right.) Problem is, PCs are so different from owner to owner. They aren't like consoles where the parts are the same essentially for each one. So, this might mean that while it works fine for you, it might not work fine for others.. And even if you are 100% right, you're using a 64-bit version. What about other versions? And of course, it's only a release candidate, so things might change by the final version.
Anyway, that's actually impressive!;)