Confirming this works fine, CRC issue squashed for Windows 32 bit version.

Nice touch carrying the name of the file base name across in to auto created bases in the receiving Mystic system.

Two things I noted when testing.

A file base can be created without stating a echo tag. I think that should be mandatory field.

Removing a file base will allow you to delete the data file but does not give you the option of removing the files and directory created. I understand that this is a safer route but I wonder if it could be made an option to present
the question to remove those files and directory also? Perhaps as an option
if some sysops didn't want to have that. Just a thought.

Best, Paul

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

A file base can be created without stating a echo tag. I think that
should be mandatory field.

Not all file bases are networked file bases. The way Mystic determines if a file base is supposed to be networked or not is by looking at whether or not the base has a configured echotag.

Removing a file base will allow you to delete the data file but does not give you the option of removing the files and directory created. I understand that this is a safer route but I wonder if it could be made

This is exactly it. I don't want someone to make a mistake and accidentally wipe out their file bases, and if I had allowed that there is no doubt in my mind that it would have happened.

Maybe I could do some validation thing where I make the user type something in order to do it. Like pop up a box that says "Type the word CONFIRM" and press enter if you'd really like to do this" instead of a Yes/No box.

As far as only being able to tag like 90 bases when adding to echomail nodes I just fixed that (I think).

I've also added your suggested of tagged delete of bases to the TODO list.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 06/27/17, g00r00 pondered and said...

A file base can be created without stating a echo tag. I think that should be mandatory field.

Not all file bases are networked file bases. The way Mystic determines
if a file base is supposed to be networked or not is by looking at
whether or not the base has a configured echotag.

Good point I had not considered this. Thanks.

Removing a file base will allow you to delete the data file but does give you the option of removing the files and directory created. I understand that this is a safer route but I wonder if it could be mad

This is exactly it. I don't want someone to make a mistake and accidentally wipe out their file bases, and if I had allowed that there
is no doubt in my mind that it would have happened.

Maybe I could do some validation thing where I make the user type something in order to do it. Like pop up a box that says "Type the word CONFIRM" and press enter if you'd really like to do this" instead of a Yes/No box.

I think something like that would be a nice to have from a tidying up point
of view but I think we collectively agree something need to be in place to avoid a moment of sorrow :)

As far as only being able to tag like 90 bases when adding to echomail nodes I just fixed that (I think).

Thanks :) I had noted it when trying to add several hundred Usenet echoareas
to an echonode in one go. It made for painfully slow connecting.

I've also added your suggested of tagged delete of bases to the TODO
list.

Thanks - it's a nice touch that would be worth adding when time permits and keeps the user experience consistent.

Best, Paul

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)