ABITEQ vs. MBM 5, an object lesson in incompatibility of software.
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
I'm gonna stick this in Widnows as it is two Windows software monitoring apps that conflict. The start of this post will not look like it is software, but the fix WAS a soft fix totally.
MBM 5 uses an Winbond monitoring core by default. It works on the IC7-Max3 IF you do not put the ABITEQ util on the XP install ALSO< AT SAME TIME as MBM 5 is on that install. IF you put both on (I tried version 1 of ABITEQ and 1.1 also), you get this:
Cold boot box, immediate ABITEQ alarm and if ABITEQ is set to shutdown (which thank whoever watches over explorers of IT things I did not do) the box does an immediate shutdown. The only clue was this-- on Abit's site, for the 1.1 version, they say to uninstall the WinBond hardware monitor (the one they provide as an alternate util) if you want to install ABITEQ. I did not even have that version yet, already was getting this, and did not have ABIT's subversion of the Winbond monitor loaded, only MBM 5 (and MBM 5 alone had been up for three days BEFORE I stuck the ABITEQ on to see what it looked like and acted like).
Conclusion, proven by experimentally pulling MBM 5 off of the P4 box, you cannot run ABITEQ and a Winbond hardware monitor with a core supplied by WidnBond (which the author of the MBM 5 pack DOES do, with thanks in the FAQs for the help from WinBond on various things, and the uninstall asked me if I wanted to pull the WinBond specific files he used when I unloaded MBM 5) if you want to run a IC7-Max3. You CAN run MBM 5 OR ABITEQ, both work. AND conflict only raises its ugly head AFTER you have both installed and warm or cold boot box. Lesson here, is this can be a pure software thing, when weird hardware things happen.
Side note-- ABITEQ locks in alarm mode when it locks, but the temp and fan speed display still updates. I let it run for about 3 min of alarm, and the temp update for the OTES fan, which was showing ZILCH, suddenly showed speed when both were present, and then the OTES fan shut off. This is dangerous, the OTES needs its CAP tunnel fan running to be safe for long running. When MBM 5 probes the OTES fan, the ABITEQ software thinks fan is off, and makes that happen. Windows does not lock. If you gt a fan-on alarm and have two pieces of monitoring software going and you run 2 montior softwares, check for software compatibility, PLEASE, and do not RMA the board right off. Seems to me something happened to anothr IC7-Max3 purchaser along these lines, but I cannot find that thread, so here is an answer I hope they will find but the compatibility thing applies to lots of Widnwos software and tTHAT is the lesson. IF you install that one last thing, and suddenly what seems like holy heck breaks loose, check the software and O\S also, but start with what you last installed by uninstalling it. Then if you do not mind experimenting, replicate the problem and fix to prove it was just software.
That is PART of what I was up to today, and one reason I got an IC7-Max3 was to explore this very possibility-- the "want to know why" bug bit big time along with the "gotta fold FASTER" bug.
John D.
MBM 5 uses an Winbond monitoring core by default. It works on the IC7-Max3 IF you do not put the ABITEQ util on the XP install ALSO< AT SAME TIME as MBM 5 is on that install. IF you put both on (I tried version 1 of ABITEQ and 1.1 also), you get this:
Cold boot box, immediate ABITEQ alarm and if ABITEQ is set to shutdown (which thank whoever watches over explorers of IT things I did not do) the box does an immediate shutdown. The only clue was this-- on Abit's site, for the 1.1 version, they say to uninstall the WinBond hardware monitor (the one they provide as an alternate util) if you want to install ABITEQ. I did not even have that version yet, already was getting this, and did not have ABIT's subversion of the Winbond monitor loaded, only MBM 5 (and MBM 5 alone had been up for three days BEFORE I stuck the ABITEQ on to see what it looked like and acted like).
Conclusion, proven by experimentally pulling MBM 5 off of the P4 box, you cannot run ABITEQ and a Winbond hardware monitor with a core supplied by WidnBond (which the author of the MBM 5 pack DOES do, with thanks in the FAQs for the help from WinBond on various things, and the uninstall asked me if I wanted to pull the WinBond specific files he used when I unloaded MBM 5) if you want to run a IC7-Max3. You CAN run MBM 5 OR ABITEQ, both work. AND conflict only raises its ugly head AFTER you have both installed and warm or cold boot box. Lesson here, is this can be a pure software thing, when weird hardware things happen.
Side note-- ABITEQ locks in alarm mode when it locks, but the temp and fan speed display still updates. I let it run for about 3 min of alarm, and the temp update for the OTES fan, which was showing ZILCH, suddenly showed speed when both were present, and then the OTES fan shut off. This is dangerous, the OTES needs its CAP tunnel fan running to be safe for long running. When MBM 5 probes the OTES fan, the ABITEQ software thinks fan is off, and makes that happen. Windows does not lock. If you gt a fan-on alarm and have two pieces of monitoring software going and you run 2 montior softwares, check for software compatibility, PLEASE, and do not RMA the board right off. Seems to me something happened to anothr IC7-Max3 purchaser along these lines, but I cannot find that thread, so here is an answer I hope they will find but the compatibility thing applies to lots of Widnwos software and tTHAT is the lesson. IF you install that one last thing, and suddenly what seems like holy heck breaks loose, check the software and O\S also, but start with what you last installed by uninstalling it. Then if you do not mind experimenting, replicate the problem and fix to prove it was just software.
That is PART of what I was up to today, and one reason I got an IC7-Max3 was to explore this very possibility-- the "want to know why" bug bit big time along with the "gotta fold FASTER" bug.
John D.
0