Forums Scripts & Popups Could lots of DDE cause no buffer space available?

My never ending mission to find the cause of the "no buffer space" available error message in my bots has taken a new turn to look towards DDE. At first I was looking at the file saving "/saveini", "/save" or "/write". Since the instances at which my bots currently do any of these functions has been dramaitcally reduced I have seen little to no improvement. The following threads are a few of the things I have gone through and tried in regards to file saving and reducing its occurance.

https://forums.mirc.com/showflat.php?Cat=...=true#Post82224

https://forums.mirc.com/showflat.php?Cat=...=true#Post81907

As I may or may not have said in these posts that when getting the no buffer space error message in the recent instances it doesn't seem to be a cause of network issues as the entire system acts as if there is a general memory leak of some sort ie. icons not showing up properly or not at all (desktop explorer), not all mircs detecting file changes and not all mircs being able to save their var file before they exit completely and so on.

Since those posts I have moved the bots to a Athlon XP 1800 with 1gb of ram running WinXP Pro sp1. Same errors continue although some of the scripts to handle and restart mirc have evolved to help get them back up and running they still can't save the varibles file most if not all the time after getting this error and disconnecting from IRC.

So now I look towards my ever increasing need to use DDE with our HubBot. This special bot uses DDE to count the amount of channels each of 10 bots are on. It also uses DDE to dispatch and remove each of the 10 bots from channels on request. Fetching passwords, checking if a bot is currently on a channel and checking other lists and types of things on the 10 bots remotely (without having to message them through IRC which could lag at times). This DDE usage has also been one of many things that has been used more frequently since our serivce has come more popular. As always, any suggestions are welcome as they may give me or someone else reading this ideas on how to solve this problem.

I don't know if DDE would cause this.

• "WSAENOBUFS"
  
  No buffer space available.
  An operation on a socket could not be performed because
  the system lacked sufficient buffer space or because a queue was full.

Ohh, didn't think that anyone was reading this. However I have fixed the problem and am no longer getting the no buffer space "WSAENOBUFS" error. I have created an alias which is formatted much like that of /dde and $dde that caches the dde results (in varibles) for up to 8 hours on certain things and 16 hours on others. I have yet to see the error and the bots and system seem to be running better than ever. As I may have explained in other posts about my problem the system overall seemed to be out of buffer space, the no buffer space available just seemed to be one of many things errors that occured due to lack of system resources. I was unable to run programs or even remotely login via RDP.

Since our hub bot doesn't directly do dde nearly as much as it used to and the same system is operating much much better I must assume that the insane amounts of DDE calls and commands between our hub and the 10 other bots was causing the system to crap out.

Well it's good to hear you have it sorted now, although you didn't really say how you did.

For curiosity; exactly how much is "the insane amounts of DDE calls and commands between our hub and the 10 other bots"?
I have at times used scripts that use $dde|/dde a LOT, and never had this error.