As this area belongs to a Portuguese-echoed area at Fido,
I requested my RC a %RESCAN, but to my surprise I got only the
messages from outside my system... All the old messages from my
BBS got stuck into the DUPES area.
As my uplink uses FastEcho, is there a way to overcome
this?
As my uplink uses FastEcho, is there a way to overcome this?
I had recently an issue with a JAM area into my system that got
corrupted beyond repair.
As this area belongs to a Portuguese-echoed area at Fido, I requested
my RC a %RESCAN, but to my surprise I got only the messages from
outside my system... All the old messages from my BBS got stuck into
the DUPES area.
As my uplink uses FastEcho, is there a way to overcome this?
^^^As my uplink uses FastEcho, is there a way to overcome this?
Just the guy for a copy of his JAM files. :)
As my uplink uses FastEcho, is there a way to overcome
this?
But isn't this *your* system detecting them as dupes / already
imported?
As my uplink uses FastEcho, is there a way to overcome this?
maybe delete your dupe database and %RESCAN again??
As my uplink uses FastEcho, is there a way to overcome this?
maybe delete your dupe database and %RESCAN again??
You mean, deleting the DUPES area?
As my uplink uses FastEcho, is there a way to overcome
this?
But isn't this *your* system detecting them as dupes / already
imported?
Indeed. I was wondering if there were any way to "force"
the rescan and tell the messagebase to ignore the dupe setting.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,166 |
| Nodes: | 17 (1 / 16) |
| Uptime: | 417:15:56 |
| Calls: | 509,423 |
| Calls today: | 9 |
| Files: | 262,242 |
| D/L today: |
5,519 files (1,523M bytes) |
| Messages: | 469,851 |
| Posted today: | 4 |