moo script and moo.dll

Download: moo script - no more moo.dll! v3.15

What is moo?
moo is the project name of a stats output script for mIRC.

Why moo?
“moo” is often just a generic word used in place of “example” or “test”, or even “foo”. It is of course it is the status output of a cow, usually signifies life. Ask mark.

What is moo.dll?
moo.dll is an mIRC dll designed to return system information for mIRC scripts, that reports various statistics, made by mark.

However, moo.dll is no longer developed as mark says the functions can be done using mIRC’s COM objects and WMI functions, and there is no longer a need for an external dll to gather the information.

What is moo script?
moo script was originally a script I wrote that displays your systems information via mIRC using moo.dll created by mark.

Recently moo script has changed, it no longer requires moo.dll, as it uses mIRC’s COM objects with WMI functions.

This script shows the stats of your system, including: operating system, uptime, cpu, memory, memory usage, screen resolution, network and hard drives, all in all, a useful script.

Example Output of Moo Script:

moo: os: Microsoft Windows XP Professional - Service Pack 2 (5.1.2600) up: 1wk 6days 1hr 26mins 6secs cpu: AMD Athlon(tm) XP 2200+ at 1800MHz (8% Load) gfx: ATI Technologies Inc. ATI RADEON 9600 Series AGP (0×4150) 128MB res: 1280×1024 32bit 70Hz ram: 887/1279.5MB (69.31%) [|||||||---] hdd: C:\ 22.08GB/55.89GB D:\ 55.95GB/111.78GB F:\ 12.23GB/18.64GB net: SiS 900 PCI Fast Ethernet Adapter - 100MB/s 1.74GB In 267.35MB Out

Is moo.dll a virus or backdoor?
No, this is often a mis-conception as moo.dll is sometimes packaged up with trojans made with mIRC, such as GTbot, it is then used to retreive that systems information. It is NOT possible for moo.dll to be a backdoor or virus as it does not have the functionality to do so, all it does is return a strings of text.

HndlWCare: he may have written what incorporates moo.dll, but he did not write moo.dll — moo.dll was written by a college roommate of one of our ops who has admitted inserting a backdoor into it.
Marky: don’t make me laugh.. check any antivirus website where a virus which has included moo.dll has been disassembled - check the description of moo.dll.. it’s usually “harmless mirc addon” or suchlike.. and you can be sure the anti virus people have disassembled it thoroughly.

I have checked the source code AND disassembled moo.dll, and have found there are NO functions that are harmful.

What are moo.dll’s functions?

The functions can be used within mIRC for example: //echo -a $dll(moo.dll,version,_) or //say $dll(moo.dll,version,_)

Function Description  
$dll(moo.dll,version,_) Returns the version of moo.dll  
$dll(moo.dll,osinfo,_) Returns the Operating System information  
$dll(moo.dll,uptime,_) Returns the uptime of your Operating System.  
$dll(moo.dll,cpuinfo,_) Returns the CPU make, speed, cache and load.  
$dll(moo.dll,meminfo,_) Returns the systems RAM usage.  
$dll(moo.dll,screeninfo,_) Returns the systems screen resolution, bit rate and refresh rate.  
$dll(moo.dll,gfxinfo,_) Returns the make and model of your graphics card.  
$dll(moo.dll,connection,_) Returns details of the RAS dialup connection.  
$dll(moo.dll,interfaceinfo,_) Returns the details of your network cards.  
$dll(moo.dll,diskcapacity,_) Returns the free space and total space of your hard drives.  
$dll(moo.dll,testing,_) Returns some CPU information that was under test.  
$dll(moo.dll,mbm5info,1) If mbm5 is running it will return MBM5 details, otherwise it will error.  


Note: This information was taking from my old site, this page will become the new home of moo.


  1. asdasd said,

    March 18, 2007 @ 3:06 pm
    I use CIM_OperatingSystem).TotalVisibleMemorySize and CIM_OperatingSystem).FreePhysicalMemory to get RAM stats

  2. Jim said,

    April 15, 2007 @ 10:54 am

    Cheers asdasd
    That memory fix worked a charm

  3. neo said,

    June 29, 2007 @ 9:10 am

    any way to get the MBM info into the new script or use the mbminfo dll that i still have? there doesnt seem to be a reference for this in the new script.

  4. c4p said,

    July 26, 2007 @ 11:44 am

    n1 with the memory fix.

    Any neat way to show if the os is 64-bit? System Information/System Summary lists a System Type entry as X86-based PC or X64-based PC, so it should be there. Checked the ms page but couldn’t find anything tho. Anyone?

  5. hm2k said,

    August 31, 2007 @ 9:55 am

    I don’t have a 64bit machine to test this on…

  6. surge\ said,

    September 5, 2007 @ 12:59 am

    i run vista x64
    lemme know if i can help
    feel free to email me

  7. Marantz said,

    September 15, 2007 @ 4:42 pm

    I don’t get an info returned for my internet connection
    Using windows Vista Home Premium (32 bit)

  8. Navarr said,

    September 19, 2007 @ 12:16 am

    I wish you’d bring back Moo with the moo.dll file. I’m running Moo w/out DLL on Vista and its freezing mIRC, sometimes even crashing. The Moo.dll runs much faster though.

  9. Govvy said,

    November 2, 2007 @ 9:25 am

    I just tried it out, it’s works a treat, code looks nice and clean too. Death to my moo.dll!

  10. Boars said,

    November 10, 2007 @ 11:30 am

    Is there anyway to get network drives showing?

    Anyway this is great… nice not to have to bother with the .dll file anymore. Many thanks…

    P.S. any other commands or modifiers for /moo ? didn’t seem to find any documented at any rate, maybe I’m blind :) Something like being able to customise output?

  11. Locksmith said,

    November 18, 2007 @ 2:46 pm

    Scipt is nice and simple, one bug though, cpu speed doesn’t read overclocked values.

  12. dj exentrix said,

    November 24, 2007 @ 11:14 pm

    This script works very well i like it. As said previously it doesn’t however read the true clock speed of the CPU as i also have mine overclocked. Below is what i’m running if it helps with testing.

    System Info: os: Microsoft Windows Vista Home Premium - (6.0.6000) cpu: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz at 2400MHz ram: 1135/2038.6MB (55.66%) [||||||----]

    P.S. I’m running 64bit.

  13. Rylos said,

    January 15, 2008 @ 10:09 pm

    I use this to pull single drives, network or local.

    if ($1 == singlehdd) { %mydrive = $?=”Enter the drive letter you want to report:” | var %i 1 | var %var %var $disk(%mydrive).path Type: $disk(%mydrive).type $+($bytes($disk(%mydrive).free).suf, (free)/,$bytes($disk(%mydrive).size).suf) | return %var }

  14. EcKstasy said,

    February 13, 2008 @ 2:46 am

    i installed mIRC,and the moo.dll is greyware/spyware ,i have done several tests with this dll and it HASN’T got the capabilites to hold any trojans or viruses,but it has got the capabillites to handle greyware & spyware,the reason for these tests is because,i did realise i had greyware on my system,i checked my pc over and over to see if i had made any mistakes,then to double check i was correct,i ran an online test on trend micro and moo.dll was listed under GREYWARE/SPYWARE,i found out myself that this dll is not needed to display system info in mIRC,it has nothing to do with mIRC,nor any other scripts,but it has a little bit to do with generating some malicious codes through mIRC,if you have mIRC installed,or kill-script (Based on mirc) ,please go to C:\KiLL-ScRipT\dll (<< Kill script directory) OR C:\Mirc\dll (Mirc Directory) and uncheck hidden,delete moo.dll ,mIRC company has been told by me personally that this dll is contained in there scripts and that they have taken all precausions of other dll’s ,please be aware that mark from made this dll (moo.dll) ,we have no further information about this,we will however get back to you

  15. hm2k said,

    February 20, 2008 @ 12:09 pm

    There’s only one reason I let the above comment through, and that’s so I could comment on it.

    mIRC does NOT come with moo.dll, moo.dll is NOT spyware or greyware, it’s impossible, the only thing moo.dll can do is read system information once called via mIRC.

    If you’re using my new script, then moo.dll is not required to read the system info, that is why it’s dubbed “no more moo.dll”.

    My advise would be to avoid using mIRC script packs such as KiLL-ScRipT in the first place.

    I’ve spoken to mark at on many occasions, I have all the information I need on moo.dll, which I have provided above.

  16. Wyse said,

    February 23, 2008 @ 5:18 pm

    I was sent a Beta of 3.14 from the author that incldued the detection of 32bit/64bit systems. If anyone is intereted in seeing this please email me.

  17. sirkit said,

    February 28, 2008 @ 6:41 am

    i’ve been using your wmi_get as a base to make my own pc stats, I havent figured out how to fix network/load percentage on a dual core proc., however
    $round($calc($comget(Win32_OperatingSystem).FreePhysicalMemory / 1024), 1) $+ MB $+ $chr(47) $+ $round($calc($comget(Win32_OperatingSystem).TotalVisibleMemorySize / 1024),1) $+ MB free)
    Computer make and model:
    $comget(Win32_ComputerSystem).Manufacturer $comget(Win32_ComputerSystem).Model
    Number of Processes:

  18. Gabriel said,

    March 6, 2008 @ 9:39 pm

    When I type moo all I got that answer

    * No such Com ‘cominfo2′ open (line 153, moo.mrc)

    what does that mean?

  19. hmm said,

    March 23, 2008 @ 1:35 pm


    how can i get rid of this annoying message?
    * $dll: unable to open ‘C:\edgepro\system\external\moo.dll’ (line 64, functions.epa)

    like how do i switch to moo.mrc from this?


  20. jjaomni said,

    March 25, 2008 @ 10:05 pm

    how do i change the script to just total up the drive space instead of displaying all the drives which get’s it cut off in a msg?

  21. Lord said,

    May 6, 2008 @ 5:37 pm

    How do I get a carriage return to work? Have tried everything.

    alias -l moor return 2moo: $iif($mooi(name), $moof(os) $ moof(up) $moof(cpu) (etc etc)c.)

    so that my output is:

    OS: information
    up: information
    cpu: information

    etc etc

  22. Cybergeek2021 said,

    May 27, 2008 @ 10:06 pm

    Hi, i’ve been using moo for a long time now but now all i get when i type /moo is: moo: lookup error can anyone help me?


  23. Kevin Whiteside said,

    June 24, 2008 @ 7:56 pm

    was bored so made the gfx line work with my dual cards also bypassed the normal output and i got this…

    if ($1 == gfx) { msg $chan 15Graphics04: 15Card 04109: 14Manufacturer09: $mooi(gfxmake, 1) 14 $+

    Model09: $mooi(gfxproc, 1) 14 $+ Memory09: $mooi(gfxram, 1) $+ MB 04- 15Card 04209: 14 $+

    Manufacturer09: $mooi(gfxmake, 2) 14 $+ Model09: $mooi(gfxproc, 2) 14 $+ Memory09: $mooi(gfxram, 2) $+ MB | return $null }

    all the strange symbols are for the colour if you hadn’t guessed, maybe you could use this in future releases

    if ($1 == gfxmake) { return $wmiget(Win32_VideoController, $2).AdapterCompatibility }
    if ($1 == gfxproc) { return $wmiget(Win32_VideoController, $2).VideoProcessor }
    if ($1 == gfxram) { return $bytes($wmiget(Win32_VideoController, $2).AdapterRam) }

    these will also be useful aswell, if someone else has posted it or you don’t find it of any use then just remove this post

  24. iagainstme said,

    July 2, 2008 @ 5:56 am

    Thanks. This works great.
    I’m using Vista Home Premium and can’t see any errors yet.

  25. ATA2D said,

    July 5, 2008 @ 2:45 am

    excelent question jjaomni [how do i change the script to just total up the drive space instead of displaying all the drives which get’s it cut off in a msg?] would be nice to have both but even a way to switch from one to the other would be GREAT

  26. Keiro said,

    July 14, 2008 @ 3:38 pm


    How in the heck do I get the moo to work?

    I’ve made certain as best as I can that it goes where it should.

    But I see no ReadMe files. Not even an explanation as to how to use moo script. :/

    Mind including a ReadMe file or something similar?

    I tried /moo in v6.21 of mIRC. Nothing happened. :/

    Then I tried the moo script with the moo.dll (Older version) and could not get it to work either.

    Maybe I’m missing something here, but I’m pretty sure I did it right. >_>;

  27. misfit said,

    July 21, 2008 @ 12:21 pm

    cpu output is wrong. shows my intel dual core duo is a p3 xeon

  28. GlassWolf said,

    August 3, 2008 @ 12:00 pm

    Has anyone else experienced issues with SLI video cards reporting improper data?
    my system is using mIRC 6.33 (reg’ed), windows vista ultimate x64, and twin nVidia (Zotac) 9800GTX cards (512MB each) in SLI @ 750core/2300mem.
    this is what I get back from moo.mrc:
    moo: os: Microsoft® Windows Vista Ultimate - Service Pack 1 (6.0.6001) up: 3days 12hrs 38mins 30secs cpu: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (x64) at 3201MHz (4% Load) gfx: NVIDIA NVxx 0B res: 1600×1200 32bit 60Hz ram: 2624/8189.6MB (32.05%) [|||-------] hdd: C:\ 387.36GB/596.18GB net: NVIDIA nForce Networking Controller - 100MB/s 887.3MB In 2.2GB Out

    The “NVIDIA NVxx 0B” is the part I’d like to correct. I’d also be willing to test any changes made if needed for both SLI and x64 responses.

    thank you

    PS great work so far. love the lack of the .dll file.

  29. GlassWolf said,

    August 4, 2008 @ 1:51 am

    PS I see the x64 notation, but I couldn’t get the above poster’s ipdates to the script to work with my SLI cards.
    perhaps I did something incorrectly.

    thanks again

RSS feed for comments on this post · TrackBack URL

Leave a Comment