I noticed something about hatched files in fsxNET.. I received a TIC for a hatched file brev988.zip .... this file ended up in my fsx\badfile directory. This is not the first time this has happened. Discovered that is I already have this file in a local Files Directory called GAMES the file that was sent from a TIC directly see this as a DUP. The TIC is told to send this file to FSX_DOORS .... however, this very file exists elsewhere.

Hummm ...

---

Rocket Town BBS - Telnet: rtbbs.ddns.net
fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Rocket Town BBS (21:1/203)

On 05 Feb 2020, Argos said the following...

I noticed something about hatched files in fsxNET.. I received a TIC
for a hatched file brev988.zip .... this file ended up in my
fsx\badfile directory. This is not the first time this has happened.

Take a look in mystic -cfg, under configuration, file base settings. There is
a setting there for Upload dupe scan. This tells Mystic where to look for possible dupe files. I have mine set for current, so it only looks in that
file area.

Hope this helps.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 05 Feb 2020 at 09:03p, Argos pondered and said...

I noticed something about hatched files in fsxNET.. I received a TIC
for a hatched file brev988.zip .... this file ended up in my
fsx\badfile directory. This is not the first time this has happened. Discovered that is I already have this file in a local Files Directory called GAMES the file that was sent from a TIC directly see this as a
DUP. The TIC is told to send this file to FSX_DOORS .... however, this very file exists elsewhere.

Hummm ...

Yep and this is behaviour by design as I figured it out... the reason is in your config > file base settings ... take a look at 'upload dupe scan' now
that will likely be set to All.... meaning if the file exists elsewhere it
will not be tossed in... but if you set it to 'current' then Mystic checks
for dupes based on the file base it's looking to import the new file into and if a dupe is found then it won't... but it still will if the file is being
sent with a REPLACE verb in the TIC (which files like this that I send out do :))

--- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I noticed something about hatched files in fsxNET.. I received a TIC for a hatched file brev988.zip .... this file ended up in my fsx\badfile directory. This is not the first time this has happened.

Take a look in mystic -cfg, under configuration, file base settings.
There is a setting there for Upload dupe scan. This tells Mystic where
to look for possible dupe files. I have mine set for current, so it only looks in that file area.

Hope this helps.

Thank you .... I will dive right into this and look.

---

Rocket Town BBS - Telnet: rtbbs.ddns.net
fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Rocket Town BBS (21:1/203)

I noticed something about hatched files in fsxNET.. I received a TIC
for a hatched file brev988.zip .... this file ended up in my
fsx\badfile directory. This is not the first time this has happened. Discovered that is I already have this file in a local Files Directory called GAMES the file that was sent from a TIC directly see this as a
DUP. The TIC is told to send this file to FSX_DOORS .... however, this very file exists elsewhere.

In your Configuration > File Settings, do you have "Upload Dupe Scan: All"
set? You can change that to "Current" if you only want it to check the
current area.

--- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
* Origin: Sector 7 (21:1/108)

I noticed something about hatched files in fsxNET.. I received a TIC for a hatched file brev988.zip .... this file ended up in my fsx\badfile directory. This is not the first time this has happened. Discovered that is I already have this file in a local Files Director called GAMES the file that was sent from a TIC directly see this as a DUP. The TIC is told to send this file to FSX_DOORS .... however, th very file exists elsewhere.

In your Configuration > File Settings, do you have "Upload Dupe Scan:
All" set? You can change that to "Current" if you only want it to check the current area.

I just finished upgrading my Production Mystic. Yesterday I upgraded my DEV without issue. Now I am on A44... Thank You and Nice Work!

I checked my configuration and sure enough I had that setting to ALL. I
change it to current... that will resolve that, my bad :(

Thanks!

---

Rocket Town BBS - Telnet: rtbbs.ddns.net
fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

--- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
* Origin: Rocket Town BBS (21:1/203)