Quote:
Originally Posted by radcapricorn
Hmm. Well, I guess to be absolutely sure we'd have to ask JScones  |
Actually, there is another way, as I mentioned above, and it is more reliable than asking the programmer to remember what he did 4 years ago. (I know from experience how reliable
that is!)
We know (can look in the Commander files and see) what changes Commander makes to text files before overwriting them. Start Commander. Start SH3. Pause SH3. Go to the altered files and look at them, to verify that the files have been altered. Unpause SH3. Now force a CTD. (Your choice of methods....) Now check the altered files to see if they have been restored. You will know unequivocally whether they are or not. Neither documentation nor programmer memory is ever a guarantee of what a program is actually doing. The only sure way to know what a program is doing is to see what it does.
Personally, I have had my share of CTDs. I don't want to create one intentionally, even to further human knowledge.
YMMV.