Drop all references to the MBM website, it's gone now.

git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4857 7894878c-1315-0410-8ee3-d5d059ff63e0

doc/FAQ

@@ -355,10 +355,9 @@ for candidates, then *note Help::)
 
   3. Check the manufacturer's website or ask their support
 
-  4. Check the Motherboard Monitor (http://mbm.livewiredev.com/)
-     website and the "links"
-     (http://www.lm-sensors.org/wiki/UsefulLinks) page on our website
-     (http://www.lm-sensors.org) some good cross-references.
+  4. Check the "links" (http://www.lm-sensors.org/wiki/UsefulLinks)
+     page on our website (http://www.lm-sensors.org) some good
+     cross-references.
 
 3.2.2 Do you support motherboard XYZ?
 -------------------------------------
@@ -861,13 +860,12 @@ it was misidentified. We are working on improving that too.
 --------------------------------------
 
 Do you own an ASUS motherboard?  Perhaps your chip is being
-misidentified.  Look on the motherboard (or at
-`http://mbm.livewiredev.com') for a 'Winbond' or Asus chip.  Often the
-real device is an Asus as99127f. If so, the driver can be forced to
-recognize the as99127f with `force_as99127f=BUS,0x2d' where `BUS' is
-your i2c bus number.  Cat /proc/bus/i2c to see a list of bus numbers.
-Read the w83781d module documentation (`doc/chips/w83781d') for more
-details.
+misidentified.  Look on the motherboard for a 'Winbond' or Asus chip.
+Often the real device is an Asus as99127f. If so, the driver can be
+forced to recognize the as99127f with `force_as99127f=BUS,0x2d' where
+`BUS' is your i2c bus number.  Cat /proc/bus/i2c to see a list of bus
+numbers.  Read the w83781d module documentation (`doc/chips/w83781d')
+for more details.
 
 4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!
 ------------------------------------------------
@@ -1085,9 +1083,6 @@ Either
 
   2. Check the manufacturer's website.
 
-  3. Check the Motherboard Monitor (http://mbm.livewiredev.com/)
-     website.
-
    When you know what chips you have, check the Driver Status
 (http://www.lm-sensors.org/wiki/Devices) web page to see if support has
 been added for your chip in a later release or in SVN.

doc/lm_sensors-FAQ.html

@@ -588,7 +588,7 @@ for candidates, then see <a href="#Help">Help</a>)
      <ol type=1 start=2>
 <li>Look at your motherboard. 
 <li>Check the manufacturer's website or ask their support
-<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website and the
+<li>Check the
 <a href="http://www.lm-sensors.org/wiki/UsefulLinks">"links"</a>
 page on <a href="http://www.lm-sensors.org">our website</a> some good cross-references.
         </ol>
@@ -1371,8 +1371,7 @@ misidentified. We are working on improving that too.
 <h4 class="subsection">4.17.5 Bad readings from a w8378[12]d!</h4>
 
 <p>Do you own an ASUS motherboard?  Perhaps your chip is being
-misidentified.  Look on the motherboard (or at
-<a href="http://mbm.livewiredev.com">http://mbm.livewiredev.com</a>) for a 'Winbond' or Asus chip. 
+misidentified.  Look on the motherboard for a 'Winbond' or Asus chip. 
 Often the real device is an Asus as99127f. If so, the driver can be
 forced to recognize the as99127f with
 <samp><span class="command">force_as99127f=BUS,0x2d</span></samp> where <code>BUS</code> is your i2c bus number. 
@@ -1643,8 +1642,7 @@ Run <samp><span class="command">devfs</span></samp> in the kernel to get the <sa
    <p>But in any case you should figure out what is on the board:
      <ol type=1 start=1>
 <li>Look at your motherboard. 
-<li>Check the manufacturer's website. 
-<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website.
+<li>Check the manufacturer's website.
         </ol>
 
    <p>When you know what chips you have, check the

doc/lm_sensors-FAQ.texi

@@ -317,7 +317,7 @@ If that doesn't work:
 @enumerate 2
 @item Look at your motherboard.
 @item Check the manufacturer's website or ask their support
-@item Check the @uref{http://mbm.livewiredev.com/, Motherboard Monitor} website and the
+@item Check the
 @uref{http://www.lm-sensors.org/wiki/UsefulLinks, "links"}
 page on @uref{http://www.lm-sensors.org, our website} some good cross-references.
 @end enumerate
@@ -902,8 +902,7 @@ misidentified. We are working on improving that too.
 @subsection Bad readings from a w8378[12]d!
 
 Do you own an ASUS motherboard?  Perhaps your chip is being
-misidentified.  Look on the motherboard (or at
-@uref{http://mbm.livewiredev.com}) for a 'Winbond' or Asus chip.
+misidentified.  Look on the motherboard for a 'Winbond' or Asus chip.
 Often the real device is an Asus as99127f. If so, the driver can be
 forced to recognize the as99127f with
 @command{force_as99127f=BUS,0x2d} where @code{BUS} is your i2c bus number.
@@ -1123,7 +1122,6 @@ But in any case you should figure out what is on the board:
 @enumerate
 @item Look at your motherboard.
 @item Check the manufacturer's website.
-@item Check the @uref{http://mbm.livewiredev.com/, Motherboard Monitor} website.
 @end enumerate
 
 When you know what chips you have, check the

doc/useful_addresses.html

@@ -253,11 +253,6 @@ implementations. Please report any other references you have found!</p>
 </li>
 <li><span class="toplvl"><a name="other">Other hardware monitoring implementations (not using LM Sensors)</a></span>
 	<ul>
-	<li><a href="http://mbm.livewiredev.com/">Motherboard Monitor</a>
-		<br />A very comprehensive package for Windows, unfortunately discontinued.
-		Supports many many devices. Also has a <a href="http://mbm.livewiredev.com/mobolist.html">great
-		database of motherboards</a>. We wish to thank the author, Alex van Kaam, for the
-		great cooperation we had.</li>
 	<li><a href="http://www.lysator.liu.se/~alla/files/lm78_stuff/">Alexander Larsson's
 		LM78 module</a>
 		<br />The original module LM Sensors is based upon.</li>