Bugzilla

Received the zip file ok. Thanks. On unzip, the first line is all 0's and is 99% of the file it seems. No idea where that is coming from. I can delete the first line and the file is a normal size and contains expected content.

Also, I've seen the files with "Child" in the name and have no idea what that is about. Kind of looks like backups or something. They all seem to be zero length too, per you "dir" output. I've always just ignored them.

Don't mean to "point fingers" at the unix tools but don't know what else, other than defective tb, could cause it. Maybe you've done this but for grins, try this:

Run tb and record the log. Don't run any other utilities.
Click "get messages" to ensure some activity occurs.
Shutdown tb
Open log file with notepad.
Is the file OK or does it have the bad 0s?

I know the logfile may not be completely written until you completely shutdown tb. At least on linux, ls still shows non-zero length for the log file even with tb running. Not sure how windows dir works in this respect.  (The "sync" logging option I mentioned is supposed to force a write to the log file more often. However, I've never seen it actually make a difference.)

Received the zip file ok. Thanks. On unzip, the first line is all 0's and is 99% of the file it seems. No idea where that is coming from. I can delete the first line and the file is a normal size and contains expected content.

Also, I've seen the files with "Child" in the name and have no idea what that is about. Kind of looks like backups or something. They all seem to be zero length too, per you "dir" output. I've always just ignored them.

Don't mean to "point fingers" at the unix tools but don't know what else, other than defective tb, could cause it. Maybe you've done this but for grins, try this:

Shutdown tb and all associated windows.
Run tb and record the log. Don't run any other utilities.
Click "get messages" to ensure some activity occurs.
Shutdown tb
Open log file with notepad.
Is the file OK or does it have the bad 0s?

I know the logfile may not be completely written until you completely shutdown tb. At least on linux, ls still shows non-zero length for the log file even with tb running. Not sure how windows dir works in this respect.  (The "sync" logging option I mentioned is supposed to force a write to the log file more often. However, I've never seen it actually make a difference.)