FU Globals & Control conflict

[j.x.]

Hi All,
When I install Dialsoft Control 4 (seems to be version 2.01 from the in BBS menu) I've noticed that all USER class accounts are blocked from viewing or using the ;global commands from FU Globals, while Sysop accounts can utilise them as normal. Also non-sysop level users seem to be being forced into invisible mode on login and prevented from accessing public areas of the teleconference module. It's almost as if Control automatically revokes users privileges and demotes them to some scummy impoverished user class. Both modules have registrations keys entered.

When I disable the Dialsoft Control module, USER class accounts can access the FU Globals and public areas of Teleconference once again.

Any advice? I was hoping to run Dialsoft Control in order to keep track of IPs that connect to the BBS, however am considering disabling/removing it altogether if I am unable to give USER level accounts access to the FU Globals commands.

I can't seem to find a key to add to users keychains to provide access to the globals, there was a _FUMKEY (or something similar) by default in the globals options which is apparently to control access to the FU Globals module, I had changed that key requirement to SYSOP since I don't plan on having a sub-sysop class that would need access, nor expect that USER class accounts would need to be able to access that module setup page (looks like it's for SYSOPs only) also I don't think that's the cause of the issue since disabling Dialsoft Control fixes the problem, even without giving USER accounts that _FUMKEY.

I figure there must be something simple that I'm missing...

[Silicon™]

Yeah 2.01 sucks... heres the latest copy with everything you should need to run it

http://www.fileden.com/files/2010/7/28/2927150/C.O.N.T.R.O.L.zip

tested and works every time without a problem