type //server -n | scid(or scon) -a server -n
and see

(all mIRC 6.x versions)

DONT TYPE THAT recursive windows, please when stating a bug stat what happens so people who dont understand these commands dont try them and lock themselves up

Warning for everyone else: the above causes an infinite loop that opens loads of windows.

I don't think it's a bug, here's why:

When you open a new server window (/server -n) you will have at least 2 status windows open, when /scon gets to the first connection it will open a third status window, when it reaches the second connection it will open a fourth and so on.

mIRC will never get to the final connection because you're opening a new one every time it gets to the next connection.

Bug or not, Khaled should implement some kind of control for this, such as a queue system...

By the way, executing those commands caused mIRC to crash within seconds. (mIRC v6.16 - Windows 2000 Professional SP4). Almost brought the system to its knees...

Thats just like the argument over timer -m 0 1, in that that should be controled. Its how it should work it works as it was designed.

mIRC was still opening windows when XP claimed it had stopped responding here.

Aye mine went till I ran outta memory

No it's not, there's no need to connect to any more than 10 servers and therefore no need for /scon -a to go through any more than 10, however, some people use timers that run an infinite amount of times (As long as mIRC's open).

I don't think that anyone can really say that 10 server connections is the most anyone would need. Maybe some people really like to chat a lot, and they need 11 servers. Or 12. Who's to say how many is too many? I think a hard limit is not what we need. Maybe /scid (and /scon) should be limited only to those server windows that were already open when the command was first executed. That would stop an infinite loop of this kind.

If a hard limit is implemented, though, I would think that something like 50-100 would be better. I can't think of any valid reason for having that many server connections at a time, but that doesn't mean that there isn't one. mIRC already seems to give users the benefit of the doubt by not having a set limit, and I like it that way.

Seconds? mahahaha you can do it instantly if u want, its easy to create an ininite loop, just recurse into an alias, Khaled cant protect agianst everything someone well do, oh wait he did stop that one, but its broken right now

Why not just put an option in the Options dialog that allows the user to specify the maximum number of windows that may be opened? IMO, this would be the logical thing to do so that everyone will be happy.

*Does command* I only got to 242 open thingies?

I don't believe this is a bug, just noncommonsense. Though I agress with the Options idea to help control it. Though this really isn't a bug since it does what it does without failure and does a good job at that. (of opening new server windows) :P