I should already know this...but with many of the echoes being more than 8 letters...how would one go about naming your bases to be able to allow your tosser to know where to toss the messages/files? If you're attempting to use TIC to automatically setup your bases...how would you get around/work with
the 8 letter limit?

To add some humor...was at work today & a lady asked me if a certain type of paint was good for a bathroom...as well as the rest of the house. Without missing a beat...said yes it would be good for her whole
home/bathroom...except for my bathroom. Thought she was going to choke
from the drink she was drinking from for laughing so hard.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)

Quoting Phoobar to All <=-

I should already know this...but with many of the echoes being more
than 8 letters...how would one go about naming your bases to be able to allow your tosser to know where to toss the messages/files? If you're

You can just name the files anything. ie: 000001 etc.

attempting to use TIC to automatically setup your bases...how would you get around/work with the 8 letter limit?

The TIC issue I can't help you with. Any long file names come here I
just delete them, it's too difficult to re-zip, change the tic file
etc etc. Most of the FSX tic file hatches just get deleted.
Exception are the info pack, and apam's stuff which is always 8. ;)

Shawn

... Windows 95: You thought OS/2 had a lot of directories?!?

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

I should already know this...but with many of the echoes being more than 8 letters...how would one go about naming your bases to be able allow your tosser to know where to toss the messages/files? If you're

You can just name the files anything. ie: 000001 etc.

It's what I was doing...but started doubting myself that I was doing it correctly with TG/2.

attempting to use TIC to automatically setup your bases...how would y get around/work with the 8 letter limit?

The TIC issue I can't help you with. Any long file names come here I
just delete them, it's too difficult to re-zip, change the tic file
etc etc. Most of the FSX tic file hatches just get deleted.

Okay. Will conquer this whenever it happens & deal with it like this or just rename the file to whatever.

Exception are the info pack, and apam's stuff which is always 8. ;)

Oh yeah! Just didn't want the discussion to restart about the 8.3 & whether
or not it matters.

Thanks for the info! Got tomorrow off...back to the mines for 1 & three from there.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)

On 23 May 20 20:30:17, Phoobar said the following to All:

I should already know this...but with many of the echoes being more than 8 letters...how would one go about naming your bases to be able to allow your tosser to know where to toss the messages/files? If you're attempting to use TIC to automatically setup your bases...how would you get around/work with the 8 letter limit?

The simple explanation is that 8.3 filenames are generally used in the forwarding and processing of Tic files to other systems due to many systems still running software only capable of processing such names. But what you do on your own system with naming is up to you.

Atreyu

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (21:1/176)

tosser to know where to toss the messages/files? If you're attempting t TIC to automatically setup your bases...how would you get around/work w the 8 letter limit?

The simple explanation is that 8.3 filenames are generally used in the forwarding and processing of Tic files to other systems due to many systems still running software only capable of processing such names.
But what you do on your own system with naming is up to you.

I find the older I get...the more age catches up with me & grabs me by the throat. ;)

Was going to work on getting TG/2 set up with SGMail/Squish...but ended up zonked out most of the day from work the day before.

Thanks to everyone who's answered this. Drives me up the wall that my body takes over for my will.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)

On 23 May 2020, Phoobar said the following...

I should already know this...but with many of the echoes being more than
8 letters...how would one go about naming your bases to be able to allow your tosser to know where to toss the messages/files? If you're
attempting to use TIC to automatically setup your bases...how would you get around/work with the 8 letter limit?

All DOS tossers will support more than an 8 char ECHOTAG just change the path to only be 8 chars.. IE: sample AREAS.BBS file

!C:\JAMBASE\JAMAREA SOMELONGERTAGNAME <links>

so regardless, it will toss SOMELONGERTAGNAME into c:\areas\jamarea

Tossers like FastEcho when a node is configured to auto add areas will
generate a random 8 char JAM base

Hope this helps

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Internal Dimension [id-bbs.ddns.net:59] (21:1/178)

All DOS tossers will support more than an 8 char ECHOTAG just change the path to only be 8 chars.. IE: sample AREAS.BBS file
!C:\JAMBASE\JAMAREA SOMELONGERTAGNAME <links>

Got it! Was looking at what FE was doing & what TG/2 was doing.

Started working on getting Squish setup to toss the messages from SGMail.
Have set it up where every network gets its own folder...rather than
everything being tossed into one folder like I was doing with Mystic.

Tossers like FastEcho when a node is configured to auto add areas will generate a random 8 char JAM base

This was my worry that I would have a ton of bad messages because the tosser would know about them...but TG/2 wouldn't.

Thanks again for providing an answer!

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)

On 28 May 2020, Phoobar said the following...

This was my worry that I would have a ton of bad messages because the tosser would know about them...but TG/2 wouldn't.

Unfortunatly, once Fastecho/etc creates the area, you have to modify/add it
to your Telegard bases

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Internal Dimension [id-bbs.ddns.net:59] (21:1/178)

This was my worry that I would have a ton of bad messages because the tosser would know about them...but TG/2 wouldn't.

Unfortunatly, once Fastecho/etc creates the area, you have to modify/add it to your Telegard bases

Am getting my current JAM message bases copied over to TG. At least if the
name of the echo right...TG/2 has no problem displaying the messages...unlike Lora 2.99.41.

Have the areas created in FE. Each network has its own folder with the
messages in the folder. In TG...I will setup "allfix_file" as "allfix_f" for
TG to be able to use it. The thing I am confused about is do I need to set up this in FE as "allfix_file" or "allfix_f" to match what TG has...since the
name is longer than 8 letters?

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)

On 02 Jun 2020, Phoobar said the following...

Have the areas created in FE. Each network has its own folder with the messages in the folder. In TG...I will setup "allfix_file" as "allfix_f" for TG to be able to use it. The thing I am confused about is do I need
to set up this in FE as "allfix_file" or "allfix_f" to match what TG has...since the name is longer than 8 letters?

Ok, so the TAGNAME (ECHONAME) will be ALLFIX_FILE and the path to JAM
messages will be <wherever your jam msgs are>\ALLFIX_F

Catch my drift? If not, send me your AREAS.BBS file and I will do a couple so you can understand it (AREAS.BBS does not contain any information other than the areas so no worries about privacy)

I dont happen to have a copy of FastEcho installed yet, I just got
eComstation running in Virtualbox, but having problems installing it on real hardware so as far as I have gotten is getting TG2 installed with SIO2k but
in Virtualbox it doesn't seem to want to accept any connections from other
than localhost .. will figure that one out after.. more than likely it's because of the bridged network adapters that I am using

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: Internal Dimension [id-bbs.ddns.net:59] (21:1/178)

to set up this in FE as "allfix_file" or "allfix_f" to match what TG has...since the name is longer than 8 letters?

Ok, so the TAGNAME (ECHONAME) will be ALLFIX_FILE and the path to JAM messages will be <wherever your jam msgs are>\ALLFIX_F
Catch my drift? If not, send me your AREAS.BBS file and I will do a
couple so you can understand it (AREAS.BBS does not contain any information other than the areas so no worries about privacy)

Does make sense...but am going to go ahead & send a few lines...since I know
of others who are working with TG or RG. Seeing the BinkD config messages helped me to understand what was going on because it was out in front of me...especially being a visual learner.

$D:\BBS\MSGS\FIDO ALL-POLITICS 3:770/1
$D:\BBS\MSGS\FIDO ALLFIX_FILE 3:770/1
$D:\BBS\MSGS\FIDO ALT-BBS-WILDCAT 3:770/1
$D:\BBS\MSGS\FIDO AMATEUR_RADIO 3:770/1

SIO2k but in Virtualbox it doesn't seem to want to accept any
connections from other than localhost .. will figure that one out
after.. more than likely it's because of the bridged network adapters
that I am using

Can't remember the exact setting for a VM...but when I hooked up the Warp box to another router which is on another network...can connect to the box at
this address: acmebbs.ddns.net:2666 for testing purposes. On the other hand...when I had the box on the same network as my main box...could only connect on port 23.

Not sure if this will help...but it solved the issue with connecting for me.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)