No error message at all. The dialog box that's supposed to pop up does pop up, but it just says 0kb for the cache size. It happens on 2 different PC's. Windows XP with SP1 and all MS updates.
I got a suggestion from from a fellow at work. He figured that for some reason on my PC's, the script was failing to instantiate the Win32_Processor object. He added some error checking to the script to check for that, but it didn't error out. Then he sent me the following:
" run the program c:\windows\system32\wbem\wbemtest
hit the connect button, and enter the name
space of "root\CIMV2"
then hit the enum instances button and
have it enumerate "Win32_Processor"
This should pull back one instance of Win32_Processor, then double click on that and it should allow you to browse all the properties for the win32_processor object including cpu name, max clock speed and of course l2 cache size.
If you can view it then it is probably a problem with the vbscript, and I think there is registry setting that controls the default namespace for WMI (windows management). The default for machines that it works on is probably the root\CIMV2 namespace. On your machine it could be something else.... hard to say..."
I tried this. I WAS indeed able to browse all the properties of the win32_processor object, so that's not failing. BUT, sure enough, the value for the L2cachesize setting of the win32_processor was definitely listed as 0k. So however these Windows processes are reading the CPU hardware, it obviously isn't working on my PC.