Guest Vrioniavas Posted December 19, 2008 Share Posted December 19, 2008 Hi all! I'm really excited about trying this mod, because playing Torment again in higher resolution would be really cool. However, I keep getting these error messages: WeiDU v 20900 Log D:\Program Files\Black Isle\Torment\setup-widescreen.exe [./CHITIN.KEY] loaded, 178649 bytes [./CHITIN.KEY] 372 BIFFs, 12135 resources [dialog.tlk] loaded, 8041168 bytes [dialog.tlk] 106497 string entries [./autonote.ini] loaded, 9994 bytes [./beast.ini] loaded, 9985 bytes [./Keymap.ini] loaded, 4012 bytes [./layout.ini] loaded, 18 bytes [./quests.ini] loaded, 33883 bytes [./Torment.ini] loaded, 1109 bytes Possible HD/CD Path: [D:\Program Files\Black Isle\Torment] Possible HD/CD Path: [D:\PTDISK\CD1\] Possible HD/CD Path: [D:\PTDISK\CD2\] Possible HD/CD Path: [D:\PTDISK\CD3\] Possible HD/CD Path: [D:\PTDISK\CD4\] Possible HD/CD Path: [D:\PTDISK\CD5\] [dialogf.tlk] loaded, 8041168 bytes [dialogf.tlk] 106497 string entries [D:\Program Files\Black Isle\Torment\setup-widescreen.exe] Using scripting style "PST" [dialog.tlk] claims to be writeable. [dialog.tlk] claims to be a regular file. Using Language [English] [English] has 1 top-level TRA files [widescreen/tra/english/setup.tra] has 20 translation strings Would you like to display the readme? [Y]es [N]o Install Component [Widescreen Mod]? nstall, or [N]ot Install or [Q]uit? Installing [Widescreen Mod] Creating 1 directory BIFF may be in hard-drive CD-path [D:\PTDISK\CD5\/MOVIES4.BIF] BIFF may be in hard-drive CD-path [D:\PTDISK\CD4\/movies4.bif] [D:\PTDISK\CD4\/movies4.bif] 131208652 bytes, 14 files, 0 tilesets [widescreen/libsmall/get_dim.tpa] PARSE ERROR at line 29 column 1-3 Near Text: SET GLR parse error [widescreen/libsmall/get_dim.tpa] ERROR at line 29 column 1-3 Near Text: SET Parsing.Parse_error ERROR: parsing [widescreen/libsmall/get_dim.tpa]: Parsing.Parse_error Stopping installation because of error. ERROR Installing [Widescreen Mod], rolling back to previous state [widescreen/backup/0/UNSETSTR.0] SET_STRING uninstall info not found Will uninstall 0 files for [WIDESCREEN/WIDESCREEN.TP2] component 0. [widescreen/libsmall/get_dim.tpa] PARSE ERROR at line 29 column 1-3 Near Text: SET GLR parse error [widescreen/libsmall/get_dim.tpa] ERROR at line 29 column 1-3 Near Text: SET Parsing.Parse_error ERROR: parsing [widescreen/libsmall/get_dim.tpa]: Parsing.Parse_error Error Uninstalling [WIDESCREEN/WIDESCREEN.TP2] component 0: Parsing.Parse_error ERROR: Parsing.Parse_error PLEASE post the contents of the file SETUP-WIDESCREEN.DEBUG to this forum: http://forums.gibberlings3.net/index.php?showtopic=12988 Using Language [English] [English] has 1 top-level TRA files [widescreen/tra/english/setup.tra] has 20 translation strings Install Component [Widescreen Mod]? nstall, or [N]ot Install or [Q]uit? I did a clean re-install of the game, I edited the torment.ini file to point to cds 2, 3 and 4 on the hard drive for the full install, and applied the official 1.1 patch prior to trying the WSM again. Thanks in advance! Link to comment
Guest Vrioniavas Posted December 19, 2008 Share Posted December 19, 2008 Oh, and I'm using Windows XP. Link to comment
the bigg Posted December 19, 2008 Share Posted December 19, 2008 For now, see the fix in http://forums.gibberlings3.net/index.php?showtopic=16311. A fix will be uploaded ASAP. Link to comment
Guest Vrioniavas Posted December 19, 2008 Share Posted December 19, 2008 It worked! At first I changed the wrong "set f = 1" because Notepad showed get_dim.dpa all in a jumble. After I changed it to look like this: OUTER_PATCH ~~ BEGIN WHILE ~%sure%~ STRING_COMPARE_CASE ~y~ BEGIN SET x = 0 SET y = 0 SET f = 1 WHILE x < 640 BEGIN TEXT_SPRINT x ~foo~ WHILE ! IS_AN_INT ~%x%~ BEGIN PATCH_PRINT @17 PATCH_READLN x END END WHILE y < 480 BEGIN TEXT_SPRINT y ~foo~ WHILE ! IS_AN_INT ~%y%~ BEGIN PATCH_PRINT @19 PATCH_READLN y END END PATCH_PRINT @20 PATCH_PRINT @13 PATCH_READLN sure END END OUTER_SET f = 1 COPY - ~%gameini%~ ~.../dump~ REPLACE_EVALUATE ~Full Screen=\([01]\)~ BEGIN SET f = ~%MATCH1%~ END ~%MATCH0%~ Everything went fine. Thanks for the prompt response! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.