"Aloke Prasad" < XXXX@XXXXX.COM > wrote in message
news:WsoJb.2146$ XXXX@XXXXX.COM ...
I discovered an even better solution after also discovering Active Monitor
uses SMBus 184.108.40.206 and Control Center uses 220.127.116.11.
I had already unzipped the downloads - both of them - and found the SMBUS
directory. Nicely tucked away in there was a README with the command line
switches for SETUP. There's an "-overwrite" switch that forces the
installation regardless of the version.
Active Monitor doesn't like seeing SMBus 4.0.4 - it is really sensitive
about seeing either 4.0.3 or an earlier version it can upgrade.
So ... run the SMBus SETUP from the Active Monitor download with the
"-overwrite" switch to downgrade the SMBus to 4.0.3, reboot and reattempt
the Active Monitor installation.
Then, if you really want to, do the same SETUP -OVERWRITE using the Control
Center's SMBUS installation to bring it up to 18.104.22.168. (Active Monitor seems
to run just fine with the newer SMBus. It just doesn't like to install with
the newer SMBus.)
Control Center is still complaining, though.
I think the problem with Control Center might have to do with SMBIOS. It is
one of the first things Control Center tosses on the machine and it seems to
require some, if not all, of a previous installation in order to continue.
In the process of trying to troubleshoot Control Center, and the eventual
reinstallation of Active Monitor, I located some files in the
\SYSTEM32\DRIVERS directory and the \SYSTEM32 directory that were associated
with SM in one form or another. Specifically:
Part of the trial-and-error troubleshooting involved deleting these files
after uninstalling Active Monitor and Control Center.
After finally forcing Active Monitor back onto the system, I thought I'd
give Control Center another try. It came back and complained:
... Desktop Control Center can be installed only on Intel desktop boards
that support IDCC. ...
Rather interesting. I specifically recall the D875PBZ was on the list of
Digging through the Recycling Bin, I located the SYSTEM32\DRIVERS\SMBIOS.SYS
and restored it. (The attempted reinstallation of Control Center replaced
the ISMBIOS*.DLL files in the SYSTEM32 directory already.)
Reboot and reattempt. It installed.
Still getting that error from Control Center, though. What a PITA this
little exercise has been.
Here's where it gets interesting, and might support my suspicion that SM
BIOS needs to be forcefully upgraded:
The SYSTEM32\DRIVERS\SMBIOS.SYS is version 22.214.171.124
Located in the Control Center directory is SMBIOS.SY_ (curious, yes?) and is
There is also a duplicated ISMBIOS.DLL. In Control Center's directory, it is
version 126.96.36.199 and in the SYSTEM32 directory, it is 188.8.131.52. The
copyright on the supposedly newer (SYSTEM32) version is 2000 while the
copyright for the one in the Control Center directory is 2000-2003.
Just to confuse matters even more (as if they aren't confused enough
already), also in the Control Center directory is something called
ISMBIOSDLL.DLL. Same description and copyright as ISMBIOS.DLL in Control
Center's directory, but version 184.108.40.206 and its "original filename" is
actually ISMBIOSDLL.DLL hinting that this is intentional.
Now, if I can just get my hands on a standalone installation of