The Fire Eater on 23/3/2010 at 20:06
Since I was in the files after playing the game again for a bit, I decided to recheck the DDFix.ini to make sure my settings for my screen size was still there, which it was but then when I tried opening the cam.cfg file that I had modified yesterday as well with the added line screen-size, that file is now completly empty? When I clicked properties it says it has 738 bytes but nothing is showing??? Of course I've still been getting the message on the game screen whenever I hit the Esc key that my screen size could not be used even yesterday when that command was there, but now todays event makes it even worse. Now what do I do?
I wonder if I take a look at the installations on the disk, would it be possilbe to copy that file and put it back into the game files and let it over-ride the one that's there, if that might work? If I could even get at it? Any ideas anyone? Please help me.
System Specs: XP-Sp3; ATI Radeon HD3850 1mg vid mem (drv.9.2); CPU AMD Athlon 64X2 5400+ 2.8Ghz; Creative X-Fi Gamer; Pioneer DVD combo; 630W PS; and a 23" Samsung WS VGA/DVI *using DVI hookup (1440x900 or 1920x1080 res only).
The Fire Eater on 24/3/2010 at 03:15
Quote Posted by The Fire Eater
Since I was in the files after playing the game again for a bit, I decided to recheck the DDFix.ini to make sure my settings for my screen size was still there, which it was but then when I tried opening the cam.cfg file that I had modified yesterday as well with the added line screen-size, that file is now completly empty? When I clicked properties it says it has 738 bytes but nothing is showing??? Of course I've still been getting the message on the game screen whenever I hit the Esc key that my screen size could not be used even yesterday when that command was there, but now todays event makes it even worse. Now what do I do?
I wonder if I take a look at the installations on the disk, would it be possilbe to copy that file and put it back into the game files and let it over-ride the one that's there, if that might work? If I could even get at it? Any ideas anyone? Please help me.
System Specs: XP-Sp3; ATI Radeon HD3850 1mg vid mem (drv.9.2); CPU AMD Athlon 64X2 5400+ 2.8Ghz; Creative X-Fi Gamer; Pioneer DVD combo; 630W PS; and a 23" Samsung WS VGA/DVI *using DVI hookup (1440x900 or 1920x1080 res only).
I tried opening game just minutes ago and it won't start. Message I get references Thief ICD. Because there was no data in cam.cfg, thinking it was looking for it, I went ahead and copied the file from the CD and pasted it into the game over-riding the one. But now I'm not sure what to do next since I apparently put in the two mods right after installing game instead of, as I found out later when trying to re-read instructions, running the game first then shutting down and then apply modifications for DDFix/WS.
They are of course already in it and I could add the line back in manually again about setting screen size but I'm afraid I'll still get message about not being able to use size requested. Also today earlier when I was able to play the game and went to Esc and then use Quit, it crashed my computer out shutting machine down.
I don't know if I even have the latest WS patch, it shows V6 but in trying to do more research I did see somewhere that there is another one or maybe it was a newer DDFix file? I'm getting a little more confused actually. If this is a newer one that I should use what would be the difference that could help with this one particular issue as far as resolution size that I need? Does it apply to my system specs or is it designed for others..i.e. Win 7 and or nVidia issues as an example?
Thank you.
UPDATED 3/25: Problem with corrupted cam.cfg file and the game playing have been resolved. The use of the patched T2.exe fixed game start and play and my recopying of the original cam.cfg file from disk, putting it in game directory overriding the one in there, adding line back in for desired screen res, then the rerun of the WS.bat file has made game playable again for the most part. I have another issue that is seperate from this topic, so this matter is closed...GAME ON! :)
