Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: -Turambar90-
« on: January 06, 2011, 09:46:21 AM »

edit: it was not weidu's fault; the .key was corrupted and the installation process was messed up. LOG worked perfectly on a new installation.
Posted by: -Turambar90-
« on: January 06, 2011, 09:11:30 AM »

As I was trying to understand why a mod faied to copy some files, I tryed to use the new LOG action to check the size of some files (to see if they were corrupt; is there any limit on the number of .bif the installer can load?). But I discovered that no messages were printed on the .debug file: neither the strings I wanted to print with LOG commands, nor those I printed with PRINT nor with WARN. The last two were regularly displayed in the dos window, but not recorded into the .debug file.