Found an interesting thing tonight. It seems if you want to hatch a new file out more than once and it has the same name in the same file echo then htick does not like it and upon copying the hatched file to the defined filearea it turns the new file into a 0kb one...
I found I was hatching 0kb files when trying to rehatch the infopack.
The only way I could seem to fix it was to set a command to manually remove the fsxnet.zip file from the defined filearea in the main config file :(
Found an interesting thing tonight. It seems if you want to hatch a new file out more than once and it has the same name in the same
file echo then htick does not like it and upon copying the hatched file to the defined filearea it turns the new file into a 0kb
one...
Hmm... I dont think I've come across this issue as you've described...
And I'm sure I've hatched out a file (an infopack) more than once
without issues...
Something is up (at least for me) I can see the same issue occurring if
I try to hatch a nodelist out twice within a week. The same compressed nodelist file name is being a 0kb file in the file area Htick sends the
Something is up (at least for me) I can see the same issue occurring I try to hatch a nodelist out twice within a week. The same compresse nodelist file name is being a 0kb file in the file area Htick sends t
Hold that thought... it may be working OK for me for the nodelist.. Hmm
Sysop: | Gary Ailes |
---|---|
Location: | Pittsburgh, PA |
Users: | 132 |
Nodes: | 5 (0 / 5) |
Uptime: | 109:36:34 |
Calls: | 733 |
Files: | 2,171 |
Messages: | 81,483 |