Hello g00r00,

I just received 6 files along with tic's from one of my hubs running Mystic A38. Two of the files had similar names, WHISPNET.103 and WHISPNET.zip. There was only 1 WHISPNET.tic for WHISPNET.103.

I suspect that Mystic created a WHISPNET.tic for WHISPNET.zip and when processing WHISPNET.103 created another with the same name, WHISPNET.tic
over writing the original?

Maybe when creating a tic file and it already exists a new filename needs to be used, like WHISPNET-1.tic or something similar, or use random names for tic files.

Ttyl :-),
Al


... I tried to drown my problems.. they like beer too!
--- SBBSecho 3.04-Linux
* Origin: The Rusty MailBox - Penticton, BC trmb.synchro.net (21:4/106)

Al wrote to g00r00 on 04-09-18 13:18 <=-

I just received 6 files along with tic's from one of my hubs running Mystic A38. Two of the files had similar names, WHISPNET.103 and WHISPNET.zip. There was only 1 WHISPNET.tic for WHISPNET.103.

I suspect that Mystic created a WHISPNET.tic for WHISPNET.zip and when processing WHISPNET.103 created another with the same name,
WHISPNET.tic over writing the original?

Maybe when creating a tic file and it already exists a new filename
needs to be used, like WHISPNET-1.tic or something similar, or use
random names for tic files.

A downlink of mine is having the same issue with his downlinks. If two files have similar names with different extensions, only one tic file will be made. I use HPT here so I never have an issue sending as many similarly named files as it creates alpha-numerical tics. I'm pretty sure Dan gave a heads up to g00r00 an
--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Badlands of NJ (21:2/141)

I just received 6 files along with tic's from one of my hubs running Mystic A38. Two of the files had similar names, WHISPNET.103 and WHISPNET.zip. There was only 1 WHISPNET.tic for WHISPNET.103.

Yep this is a known issue that someone else recently reported. It seems its accidentally overwriting the original .TIC instead of renaming it. I'll move that to near the top of the TODO list as its kind of a big deal.

Thank you for the report!

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

Re: Re: tic files and like named files
By: g00r00 to Al on Tue Apr 10 2018 02:35 pm

Yep this is a known issue that someone else recently reported. It seems its accidentally overwriting the original .TIC instead of renaming it. I'll move that to near the top of the TODO list as its kind of a big deal.

Not a big deal for me since I did get the file I needed. I suppose it might
be a big deal for hub nodes who need to pass the file along to their links.

Thank you for the report!

No problem and thank you for looking into it. :)

Ttyl :-),
Al


... Scotty, beam me to the Bahamas.
--- SBBSecho 3.04-Linux
* Origin: The Rusty MailBox - Penticton, BC trmb.synchro.net (21:4/106)

Yep this is a known issue that someone else recently reported. It see its accidentally overwriting the original .TIC instead of renaming it I'll move that to near the top of the TODO list as its kind of a big

Not a big deal for me since I did get the file I needed. I suppose it might be a big deal for hub nodes who need to pass the file along to
their links.

Yeah I consider it a pretty big mistake because when Mystic is hatching files for example, those files will never get tossed by the systems it ends up on without a .TIC.

Thanks for the reminder... I fixed it up today and I am going to build a new prealpha now.

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