View Single Post
Old 09-25-2005, 01:30 PM  
Senior Member
Join Date: Jul 2005
Posts: 153

Originally Posted by ADDiCT
My suggestion would be to run each instance in a separate user environment, for example: one as LocalSystem service, the other in the Administrator desktop (or as Administrator service). When using sitewho for the bot, you would need 2 bots in this example, each one started through io to make sure they are in the same environment as the ioFTPD about which they need to show information.
i'll go ahead and repeat this post here:

Originally Posted by _panic_
there is an undocumented name/value pair in the [Threads] section of ioftpd.ini. it is called WindowName, and defaults to "ioFTPD::MessageWindow". you can change this in one of your running ioftpd configurations, which will take care of the problem from ioftpd's side. you'll also of course, need to fix sitewho.exe to look for another window name. not sure how to do this part.
can sitewho be made to behave the same way? i.e. look in the ioftpd.ini file for this resource name and use it if it exists? that might be a simpler way of fixing this problem.
_panic_ is offline   Reply With Quote