This is a simple DestopX object that shows the sensor values from 2 temperatures and 3 fan values from Motherboard Montior 5.  

Before use, the DLL (MBM-AX.DLL) in the DLL directory needs to register, either via the install.bat file, or via "regsvr32 MBM-AX.DLL" from a command prompt in the directory containing the file.  If you move the file to another location, then you will need to reregister it so that Windows can find it again, so put in a relatively non-volatile directory.  Once this has been done, you can check that it is working either through running the test.vbs script contained inside the DLL directory, or by directly importing the object in DesktopX.  

About the object
================

MBM uses sensors number, which go approximately from 0 to 100 (this isn't check at the moment so if you use to high a number it will give you an error).  The test.vbs script will output a text file (which can be renamed to test.csv and viewed in Excel), which will give you the current status of 66 sensors, along with the names of the sensors, which is the current limit on my system.  Anything that gets a 255 value, is a sensor that isn't connect.  You can take these numbers, and use them in your own DX object (one that is sure to look nicer than mine ;), by simply changing the sensor number that the value is for.  If you look at the script for the blue background object, then you can see a relatively simple demonstration of what happens.

At the moment, the only properties implemented as part of this DLL are 

sensor_value - Be it voltage, temperature, percentage...
sensor_type -
 1 = Temperature
 2 = Voltage
 3 = Fan
 4 = CPU Frequency (MHz)
 5 = CPU Usage Percentage 
path - Path of the MBM executable
sensor_name - Name of the sensor (which can be changed via MBM, although you will need to restart)
alarm1 - By the looks of it, the high alarm value (if set)
alarm2 - By the looks of it, the low alarm value (if set)
high - The highest reading for the sensor since it has been started
low - The lowest reading for the sensor since it has been started
readout - ???? Don't know, was implemented in the header file, so if someone can let me know...
version - The version of MBM in use.

Have a look at the test.vbs for how the use it, or the script for the background rectangle.

Known Problems
==============

If you put a number that is too large, you will come up with a seg fault error in wscript.  Will hopefully be fixed properly in the next version.

It restarts the MBM dll everytime the class in reinitialized, so for example with each time the script is called, so high and low can be useless, unless the script is run multiple times, ie with timers in DX.  This also adds to the time taken to start both the scripts (loading the starter DLL followed by loading a second DLL).  Haven't come up with a solution that works, because it the script is run without this is the code, it won't be able to get MBM's data, even if another program has already started the DLL.  

The full list of things to be implemented is not complete as yet, but these will come with the next version.

As it stands, I decide to release this software to check that it actually works (and someone else might get some use out of it).  Any comments let me know via 

mark@kuchel.net and/or markkuchel@bigpond.com (The first is a little dodgy atm, but the second may change soon).

Credits to Danny Couture (dcouture@popupsolutions.com) for the MBM shared memory access code from the MBM site, which I freely pinched and made use of.

For licensing details, please see LICENCE.txt in the DLL folder.