I've seen too many of thoes, but in my system it seems fine, no slowdowns or hd activity and the messages still appears even when it's idle.

---

CPU: AMD Athlon 64 3000+ @2.3Ghz - Motherboard: ASUS A8N-SLI nForce4 SLI - nForceLAN by eno - SuperNForceATA by Medevil - RAM:2 GB DDR 333Mhz Audio: ALC850 Video: XFX nVidia GeForce 8400GS 256Mb (0x06e4) QE & CI from Chameleon 2 RC4Ethernet: Realtek RTL 8139 Series (working out of the box) OS: Snow Leopard 10.6.4 (aryajuanda's guide) + Windows XP 64bits

yes i think everyone is having these error but the question is why are they showing up what is causing them

I used to receive those messages sometime ago, but after updating to the latest kernel from the #10.5 channel on irc.osx86.hu and the latest AppleSMBios from Macdotnub, they have since disappeared. It's definitely worth a shot.

---

MacBook Pro 15" | Mac OS X 10.6 • 2 GHz Intel Core Duo • 2 GB DDR2-667 • ATI Radeon Mobility X1600 128 MB • 100 GB Serial-ATA
Hackintosh | Mac OS X 10.5.6 • 3 GHz AMD Athlon 64 X2 6000+ • MSI K9N AM2 • 2 GB DDR2-667 • NVIDIA GeForce 8800 GT 512 MB • ALC888 Audio • 300 GB Serial-ATA
iPhone 3G • 8 GB

Interesting, because I am also running latest kernel (9.2.0 w/ shutdown fix) and AppleSMBios-27 from macdotnub. Oh, but which AppleSMBios exactly? There are many different ones for different RAM types and Mac identities. I am using the "default" one. Also, what are your specs?

Actually yesterday I upgraded AppleSMBios to the new version from netkas. The previous version I had installed was the hardcoded 667Mhz version. I'm also running the latest 9.2.0 with shutdown fix.

---

MacBook Pro 15" | Mac OS X 10.6 • 2 GHz Intel Core Duo • 2 GB DDR2-667 • ATI Radeon Mobility X1600 128 MB • 100 GB Serial-ATA
Hackintosh | Mac OS X 10.5.6 • 3 GHz AMD Athlon 64 X2 6000+ • MSI K9N AM2 • 2 GB DDR2-667 • NVIDIA GeForce 8800 GT 512 MB • ALC888 Audio • 300 GB Serial-ATA
iPhone 3G • 8 GB

Ah, good to know. Haven't tried that one yet. I'll give it a spin right now.

Running the new AppleSMBIOS right now. Reported RAM speed is wrong of course, but that is always the case for me and Netkas' versions of the file. No biggie. Runs good. Can't say that it did anything for these "code signing" messages, but I think it did cut down on the number of mDNSresponder messages I'm getting, which would be a plus. I could be mistaken though.