Subj : Re: BUSY NODES on A38 (windows) issue since updating
To   : Vitus Zeel
From : g00r00
Date : Sat Jan 20 2018 05:11 pm

 VZ> i have busy nodes. can't delete the .bsy file by using fidopoll.exe
 VZ> killbusy also not by using fidopoll.exe killbusy force

Sounds like an access issue or you have a process stuck running, although I
am not clear on what you're trying to show in the logs vs what you're
reporting.

 VZ> if i start mutil it creates all .bsy files. if i delete all by hand
 VZ> during muti is running the tosser will do his work. in the new error.log
 VZ> which i will post at the end of my msg you can see every one mutil start
 VZ> with an error 216...

The errors in the log you posted do not show MUTIL errors it shows MYSTIC
errors.  Mystic has no interaction with .BSY files at all.  Are you talking
about nodes that are reporting users online when they're not?  This is
confusing.

Why are you trying to delete .BSY files while MUTIL is running? MUTIL needs
those BSY files to run, thats why its creating them.

--- Mystic BBS v1.12 A39 2018/01/18 (Windows/32)
 * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

.