Anyone about that can field a question about Fastecho?
Anyone about that can field a question about Fastecho?
There's a few of us still haunting the echo. If it's not too hard then I'll have a go at an answer.
BoC<tm> ;)
what's your question?
Thanks for the reply, actually I think I solved my issue. It related
to echoarea tags that broke the 8.3 convention. But I'm going to be looking at the stats output/reporting features of FE soon so may have
a few more questions about that and routing.
Long tags are fine, even those based on Usenet groups. If you let FE auto-create areas then even the filenames will still be kosher.
ButOfCourse<tm> ;)
yup... FE and most traditional tools still require 8.3 naming for the files they use... in the case of FE, one just needs to provide an max 8 character portion as the .3 portion is forced to be the JAM
extensions... the areatags can be pretty long but i don't recall exactly how long without going and looking...
aside: something i did a while back was to separate my areas into groups and then subdivided those by first letter to help avoid duplicate
names... FE does have an internal method of generating names (FExxxxxx) where the xes are hex (IIRC) and i think they are CRC16 of the areatag
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,017 |
Nodes: | 17 (0 / 17) |
Uptime: | 113:40:58 |
Calls: | 503,081 |
Calls today: | 16 |
Files: | 212,938 |
U/L today: |
1 files (4K bytes) |
D/L today: |
4,704 files (771M bytes) |
Messages: | 440,559 |