I've added a separate BUSY logging called "busylog.txt" that is created in the directory that MIS2, MUTIL, FIDOPOLL are stored in. Hopefully for you, you run them all in the same directories so that everything will be logged into the same log file.

Just wanted to let you know. If you have the BUSY issue again hopefully this will give us an idea of what happens.

This is in the latest version on the prealpha site that I just put up now.

--- Mystic BBS v1.12 A36 2017/11/19 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I've added a separate BUSY logging called "busylog.txt" that is created
in the directory that MIS2, MUTIL, FIDOPOLL are stored in. Hopefully
for you, you run them all in the same directories so that everything
will be logged into the same log file.

Well, I totally screwed up and only had it logging if it ERRORS when erasing
a busy file. I am going to put new fidopoll, mutil and mis2 .exe files for win32 in the prealpha area.

This will log ALL BUSY file actions which is going to end up being a giant
log file, but it should show me exactly where the issue happens.

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

On 11/19/17, g00r00 pondered and said...

This will log ALL BUSY file actions which is going to end up being a
giant log file, but it should show me exactly where the issue happens.

Gotcha and no probs..

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