The End of Motherboard Monitor, MBM

The author, Alex Van Kaam, has decided to call it quits. Citing the inability to obtain technical information from key manufacturers as the main source of his frustrations, Alex has decided that 7.5 years of development is enough.

The full story can be found at Alex's MBM homepage.

<A HREF="http://mbm.livewiredev.com/" target="_new">http://mbm.livewiredev.com/</A>

<b>56K, slow and steady does not win the race on internet!</b><P ID="edit"><FONT SIZE=-1><EM>Edited by phsstpok on 07/09/04 09:35 AM.</EM></FONT></P>
14 answers Last reply
More about motherboard monitor
  1. never liked the program anyway.

    <font color=blue>My dick is so big, that my dick has a dick. And my dicks' dick is bigger than yours.</font color=blue>
  2. Thats some bad news it was a realy good program...

    Athlon 2700xp+ (oc: 3200xp+ with 200fsb)
    Radeon 9800pro (oc: 410/360)
    1024mb pc3200 (5-3-3-2)
    Asus A7N8X-X
  3. I've also heard many good things about that program, but never liked it personally

    ------------
    <A HREF="http://geocities.com/spitfire_x86" target="_new">My Website</A>

    <A HREF="http://geocities.com/spitfire_x86/myrig.html" target="_new">My Rig</A> & <A HREF="http://geocities.com/spitfire_x86/benchmark.html" target="_new">3DMark score</A>
  4. I quite like it, although it can be a pain to configure to start with, 'tis true.

    What are your preferred alternatives? Just curious

    ---
    Epox 8RDA+ V1.1 w/ Custom NB HS
    Summer's here! so ease off the overclock...
    XP1700+ @166x12 (~2Ghz), 1.45 Vcore
    2x256Mb Corsair PC3200LL 2-2-2-4
    Sapphire 9800Pro 400/730
  5. I don't know for alternatives, but I agree that MBM was somewhat useful, but it was so hard to configure even for advanced users... I really hated it for that reason. I often use it while I set up overclocking, then, I mostly never run it.

    I would better like, a more intuitive application with less eye-candy. I don't know who will take over this project... I mean who will start from scratch for this? If I were good enough in programming I might be interesting in doing it, but I'm not good enough in VB to do it!

    But, basically, it's a simple thing to do, some read call, display them, keep the lowest/highest/average in variables. What's hard, it's probably to try figure out how to read from all those chipset/BIOS and different implementation!

    I think a good start would be with something like CPU-Z that already identify BIOS/Chipset/motherboard model and revision.

    --
    It's tricky to use words like <b><font color=green>AMD</font color=green></b> or <b><font color=blue>Intel</font color=blue></b> in a signature some users could think your are biased.
  6. hmm.. I assume even the windows API is too high-level to get much of that information :eek: ..

    I don't know in truth. Maybe I'll look into it if I'm bored sometime.

    I see what you mean - something <i>really</i> simple would be great. Just simply display temps & voltages, with a simple timer for Poll Interval & maybe some logging. I would certainly use it myself.

    ---
    Epox 8RDA+ V1.1 w/ Custom NB HS
    Summer's here! so ease off the overclock...
    XP1700+ @166x12 (~2Ghz), 1.45 Vcore
    2x256Mb Corsair PC3200LL 2-2-2-4
    Sapphire 9800Pro 400/730
  7. Quote:
    something really simple would be great. Just simply display temps & voltages, with a simple timer for Poll Interval & maybe some logging.

    Yes, this is the way to go! Simplicity is often underestimated!

    Quote:
    Summer's here! so ease off the overclock...
    XP1700+ @166x12 (~2Ghz), 1.45 Vcore

    My answer to that :
    It's Summer, crank up overclocking to burn that AXP chip! I want an A64 asap!!! :smile:
    XP 1800+ @ 166x12 (2.0GHz), 1.8 Vcore

    --
    It's tricky to use words like <b><font color=green>AMD</font color=green></b> or <b><font color=blue>Intel</font color=blue></b> in a signature some users could think your are biased.
  8. That's exactly what's hard, reading the sensor. Each chipset is different, no standard addresses or access methods between chipsets. The obtained values aren't even in degrees just arbitrary, unbuffered, digitized numbers. You have to create the correct formula for each sensor/chipset combination. You also have to determine the correct bias values, offset from the zero or default value. You can't use just high, low and average either. System interupts can cause intermittent nonsensical values which have to be detected and ignored. Plus it's all experimentation and trial and error if the manufacturers won't provide the necessary information.

    <b>56K, slow and steady does not win the race on internet!</b>
  9. So it's a good challenge for someone who likes messing with code/hardware. What would be great, it's an open-source project for this. So a lot of people could test or gives feedback to devellopers.

    --
    It's tricky to use words like <b><font color=green>AMD</font color=green></b> or <b><font color=blue>Intel</font color=blue></b> in a signature some users could think your are biased.
  10. I use winbond hardware doctor to monitor temp./voltage (supplied by ABIT)

    ------------
    <A HREF="http://geocities.com/spitfire_x86" target="_new">My Website</A>

    <A HREF="http://geocities.com/spitfire_x86/myrig.html" target="_new">My Rig</A> & <A HREF="http://geocities.com/spitfire_x86/benchmark.html" target="_new">3DMark score</A>
  11. That's a huge loss.

    <i><font color=blue>Edited by Scamtron on 10/11/01 09:58 PM
  12. Yes.

    It's too bad much of Alex's research was done under the contraints of NDAs. The information would have provide a huge headstart to such a project.


    <b>56K, slow and steady does not win the race on internet!</b>
  13. Hummm.. Would it be possible for him to "sold" informations or software to another company?

    I company liek FutureMark might be interested in this kind of software!

    --
    It's tricky to use words like <b><font color=green>AMD</font color=green></b> or <b><font color=blue>Intel</font color=blue></b> in a signature some users could think your are biased.
  14. Doubt it. Alex stated that he can't open his code to the public because of the NDAs (Non Disclosure Agreements).

    If the NDAs prevent him from giving away the information then he certainly can't sell the information.

    <b>56K, slow and steady does not win the race on internet!</b>
Ask a new question

Read More

Motherboards Font Monitors