CSS acting screwy...

[LegendaryKA8]

Hey again. Here's the situation:

I just moved my T42 2373-M3U motherboard and hard drive from my old 'Frankenpad' setup to a 15" chassis I had laying around(Flexview is awesome, BTW). Since the M3U has a fingerprint reader, I purchased a 15" palmrest with a fingerprint reader on it, hacked a hole in the top of the hard drive cage for clearance, and put it all together.

I removed the backup battery while I switched motherboards. While everything else is working correctly, CSS is not. I had 8.0 on the machine at first, and it kept asking me to activate the security chip every startup. I would do so, and even though I verified the security chip was enabled through the BIOS the CSS program still 'thought' it was disabled.

Seeing that 8.0 didn't officially support the T42, I went ahead and uninstalled it, reinstalling 7.0 in its place. Now when I try to activate the security chip, the program pops up something to the effect of "The SM Bus Driver failed to load. Please restart your computer." I restart to the same effect.

My Device Manager lists the TPM chip as working correctly and with all drivers installed. The entire setup was working just fine when I had it in my 14.1" chassis. Any thoughts on what might be wrong with this?

[Tim M]

I am having the identical problem after replacing a dead CMOS battery (was getting a checksum error at boot-up). I can activate/deactivate the chip in the BIOS, but I am always told that the chip is inactive when booting into Windows. After "logging in normally," I am presented with a CSS window allowing me to activate the chip, as described in this thread. Activating will change the state of the chip as reported in the BIOS, but I still am told that the chip is inactive when logging in to Windows.

Any thoughts on how to solve this problem? And please, no debates on the merits/pitfalls of CSS as I simply want to resolve this software fault. Thanks.

EDIT:I was able to resolve this issue by clearing the security chip via the option in the BIOS. With the chip enabled, CSS detected it, prompted me that it had been cleared, and proceeded to restore the keys.