SUBSIM Radio Room Forums - View Single Post

Amizaur · 10-31-05, 01:03 PM

Maybe something indeed happens while files are copied. Like read-only files, or something I didn't anticipated. You could have just check it. Before installing mod, remember/write somwhere filesizes and more impoortant dates of all database files. Apply install or uninstall and check what happened in the folder. Are all files with new date ? Or maybe some are unchanged ? And so on. I would ask you to try find the reason yourself if you can, sometimes when error is reported I look and at once understand what gone wrong, what was wrong. But sometimes I can't -everything seems to be absolutely all right and this may be computer specyfic thing (or at least - NOT specyfic for MY coputer). It's hard to tell on a distance what's happening on other's computer

So if you can, try to find the source of problems yourself. Look into bat files, you see what they should do. Run them and check if they have done what they should. Are files really overwritten ?
Personally if I report a bug to SCS, I try to find it's source/reason if I can, and if I can even find possible solution.
About files that are left from the mod and not overwritten. Well we'll add delete command I think and then everything would be clear. The remaining mod files were not deleted, because they don't interfere with anything, they really should not hurt agt all. And second - while testing we have in database/doctrine folders many different non-game files like DWEdit, doctrine checker, and also many versions of different doctrines and backup files. So I prefered that only files that matters were overwritten. But OK, if you suspect that this may be source of problems, I'll ad delete to the bats. But please, if you can, try to determine yourself what's happening, are files really overwritten as they should ect.
Also if you experience incompatibility problems after manual installing 2.02 mod, try to rever to 2.01 and check if then everything is OK ? If yes, then we'll search for error in 2.02. Bats were not changed. Also, there is no need to reinstall the game, if you have originall database and doctrine folders stored. The mod is confined to database and doctrine folders only, no other changes.

P.S. Yep, returning to 2.01 to see if all goes smoothly there is good idea. If problems with 2.02 are so serious you can't play, return to 2.01 please and give us day or two, we'll try to determine source of problems with 2.02.

10-31-05, 01:03 PM	#17
Amizaur Sonar Guy Join Date: Nov 2002 Location: Poland Posts: 398 Downloads: 0 Uploads: 0	Maybe something indeed happens while files are copied. Like read-only files, or something I didn't anticipated. You could have just check it. Before installing mod, remember/write somwhere filesizes and more impoortant dates of all database files. Apply install or uninstall and check what happened in the folder. Are all files with new date ? Or maybe some are unchanged ? And so on. I would ask you to try find the reason yourself if you can, sometimes when error is reported I look and at once understand what gone wrong, what was wrong. But sometimes I can't -everything seems to be absolutely all right and this may be computer specyfic thing (or at least - NOT specyfic for MY coputer). It's hard to tell on a distance what's happening on other's computer So if you can, try to find the source of problems yourself. Look into bat files, you see what they should do. Run them and check if they have done what they should. Are files really overwritten ? Personally if I report a bug to SCS, I try to find it's source/reason if I can, and if I can even find possible solution. About files that are left from the mod and not overwritten. Well we'll add delete command I think and then everything would be clear. The remaining mod files were not deleted, because they don't interfere with anything, they really should not hurt agt all. And second - while testing we have in database/doctrine folders many different non-game files like DWEdit, doctrine checker, and also many versions of different doctrines and backup files. So I prefered that only files that matters were overwritten. But OK, if you suspect that this may be source of problems, I'll ad delete to the bats. But please, if you can, try to determine yourself what's happening, are files really overwritten as they should ect. Also if you experience incompatibility problems after manual installing 2.02 mod, try to rever to 2.01 and check if then everything is OK ? If yes, then we'll search for error in 2.02. Bats were not changed. Also, there is no need to reinstall the game, if you have originall database and doctrine folders stored. The mod is confined to database and doctrine folders only, no other changes. P.S. Yep, returning to 2.01 to see if all goes smoothly there is good idea. If problems with 2.02 are so serious you can't play, return to 2.01 please and give us day or two, we'll try to determine source of problems with 2.02.