System information has been requested in the past. I'm sure it is probably on Khaled's list. One thing that can be a problem there, though...
$os is pretty easy. Every OS (I believe) will respond to the same command to get that. However, other system info items may use different commands depending on the OS. That being said, now that mIRC is only for newer versions of Windows and doesn't support stuff like 95 or 98, the commands are probably standard now. I know that when I set up COM to get this information in the past, I had to use different methods for the older versions of Windows. If you look into the COM objects on MSDN, you'll see that many of the commands require specific versions of Windows to work.
Anyhow, I'm sure it can be done and that it's on his list. And I'm sure the commands are standard now even though they weren't always standard in the past. So that should make it even easier.
Of course, I just use a single identifier for the majority of system information and just supply it with the name of the object to get the information from. So it's not too much code to do most of the things you'd want. You can do the same by taking just about any basic COM script and making the object name and properties $1 and $2 so you can supply them and then have it return the results. $sysinfo(object,property) for example. As long as the results are the same format, you can use that same identifier for everything. Just supply the object and property each time.
Also, there's the whole "where do you stop" question. How many identifiers should we add to mIRC for system info? You listed a few. But there are dozens more that someone will probably want. Should mIRC provide every single identifier? Or should it be left to scripting?
Last edited by Riamus2; 20/03/11 01:02 PM.
