Content of documentation

User documentation

Administrator documentation

Index of terms

Technical Support

Search on-line

VoiceChange saves its text log files into common/ini/ directory (valid for VoiceChange until version 4.6.19). For every VoiceChange script line0.vbs, line1.vbs to line#.vbs is created one log file line0.ini.log, line1.ini.log to line#.ini.log.

All output which VoiceChange kernel and applications print via Log.Write function is copied into those logfiles.

When VoiceChange is started, previous log is renamed to line#.ini.log.bak and a new log is created. So in directory common/ini/ are always two logs for every script - current (data are written here or if Voicechange is stopped, data from last run) and previous. This ensures that disk will not be wasted by old log files.

Since VoiceChange version 4.6.20 scripts write their logs into common/logfiles/ folder by default, log name is in form
<line name>_<year>-<month>-<day>.work.log, so logs are rotated by days. Name can be changed by $Log.FileName parameter in common/ini/common.ini file. Name can contain wild-cards %l (line name), %d (date), %t (time). In general filename must be constructed using %l to create separate file for every script (log can not be shared between more scripts). We recommend to use default setting.
It is suitable to delete older logs after some time - daily log for one line has size in megabytes.

User applications can use one more log tool - AppLog object and logs created by this object. Here are written only these information, which user wants to write.

Aplication log files are saved into common/logfiles/ directory. Its name has following format:

<year>-<month>-<day>.<script name>.log

for example 2000-03-07.line1.log. For every script and every day a new log is created, what allows to delete old logs safely and make their processing easier.

Application logs were proposed to allow simple automatic statistic processing.

Technology of application logs is better described in VX script reference.

Brooktrout TR114 low-level driver has its own logfile - faxinit.log in /winnt/bfax/ directory. Information about last Brooktrout card initialization is stored in that file. So if your card has bad hardware configuration, you'll probably find text "couldn't find any fax/voice boards" in this file.

back to top