RF> ./semaphore/mis2.bsy
 RF> - I'm using mis2, but I'm using that as my binkp server.

There is no such thing as MIS2, it was removed maybe 40 builds ago. 

You have a mix match of old vs new versions of Mystic and that is particularly
bad to do with A37 because it had data file format changes.  It also means the
busy change (which was just correcting a typo in a filename) is unrelated.

So lets start here: Make sure you have all of the latest binaries and none of
the old ones... This is not limited to only MIS/MIS2 but all of the binaries -
please double check them.

After they are double checked, we should probably validate the binaries are all
set to the proper user/group and chown -R everything in the Mystic directory
structure to that user/group.  Finally do a "fidopoll killbusy all" so we're
starting with a clean slate with no residue (validate that with your find
command).

Keep an eye on the access rights, particularly directory ownership of temp
directories, and especially if you deleted mis and kept mis2 on your disk while
you ran mis2.  During mis2 development there were a couple of things that could
cause it to start creating files and directories with the wrong access.

Once this is all done try going through everything manually, starting with
running fidopoll the same way your event would execute it.  Check for BSY files
after it runs, or note obviously if it crashes or something.  Since you say
you can reproduce this every time, it should be obvious where the problem
occurs when you execute through the steps manually.

--- SoupGate-Win32 v1.05
 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)