Why doesn't the hack (Supposed to show detailed processor info. like stepping, etc.) in the registry where you add a space between the "VendorIdentifier" string value under HKEY_LOCAL_MACHINE\Hardware\Description\System\CentralProcessor\0 work after I installed 98SE Service Pack?
Thanks
Page 1 of 1
Misc. Bugs... Some of my thoughts
#2
Posted 05 December 2005 - 01:25 AM
303, on Dec 5 2005, 09:55 AM, said:
Why doesn't the hack (Supposed to show detailed processor info. like stepping, etc.) in the registry where you add a space between the "VendorIdentifier" string value under HKEY_LOCAL_MACHINE\Hardware\Description\System\CentralProcessor\0 work after I installed 98SE Service Pack?
Please look at this topic.
#3
Posted 05 December 2005 - 01:32 AM
303, on Dec 5 2005, 07:55 AM, said:
Why doesn't the hack (Supposed to show detailed processor info. like stepping, etc.) in the registry where you add a space between the "VendorIdentifier" string value under HKEY_LOCAL_MACHINE\Hardware\Description\System\CentralProcessor\0 work after I installed 98SE Service Pack?
Thanks
Thanks
It seems to be problem of SYSDM.CPL 4.10.2224 from Q272620 - Negative Hard Disk Free Size Reported on Virtual Memory Tab in System Properties. You may try to use the old one from W98SE CD.
BTW, how it is on Windows Me with SYSDM.CPL 4.90.3001?
BTW2: in the SYSDM.CPL binary is contained string Hardware\Description\System\CentralProcessor\0 VendorIdentifier Identifier but Regmon shows it is not called. Maybe somebody could chceck why?
Petr
Gape, on Dec 5 2005, 08:25 AM, said:
303, on Dec 5 2005, 09:55 AM, said:
Why doesn't the hack (Supposed to show detailed processor info. like stepping, etc.) in the registry where you add a space between the "VendorIdentifier" string value under HKEY_LOCAL_MACHINE\Hardware\Description\System\CentralProcessor\0 work after I installed 98SE Service Pack?
Please look at this topic.
You were quicker than me :-)
It is interesting that on ME it shows processor information (see MDGx post in the referenced thread) and on W98 not.
Petr
#4
Posted 06 December 2005 - 03:48 AM
It appears that the cosmetic bug described in MSKB: Q272620: Negative Hard Disk Free Size Reported on Virtual Memory Tab in System Properties can be solved easily by changing string 205 in string resource 13 in sysdm.cpl file - from:
205,%c:\ %dMB Free
to
205,%c:\ %luMB Free
Patched file is here: http://www.winpack.o...tr/98/sysdm.zip
But what about all other changes in 4.10.2224 version of sysdm.cpl file? Does anybody know about them?
Petr
205,%c:\ %dMB Free
to
205,%c:\ %luMB Free
Patched file is here: http://www.winpack.o...tr/98/sysdm.zip
But what about all other changes in 4.10.2224 version of sysdm.cpl file? Does anybody know about them?
Petr
#5
Posted 07 December 2005 - 02:38 AM
Petr, on Dec 6 2005, 03:48 AM, said:
It appears that the cosmetic bug described in MSKB: Q272620: Negative Hard Disk Free Size Reported on Virtual Memory Tab in System Properties can be solved easily by changing string 205 in string resource 13 in sysdm.cpl file - from:
205,%c:\ %dMB Free
to
205,%c:\ %luMB Free
Patched file is here: http://www.winpack.o...tr/98/sysdm.zip
205,%c:\ %dMB Free
to
205,%c:\ %luMB Free
Patched file is here: http://www.winpack.o...tr/98/sysdm.zip
#6
Posted 07 December 2005 - 03:34 PM
Petr, on Dec 6 2005, 10:48 AM, said:
It appears that the cosmetic bug described in MSKB: Q272620: Negative Hard Disk Free Size Reported on Virtual Memory Tab in System Properties can be solved easily by changing string 205 in string resource 13 in sysdm.cpl file - from:
205,%c:\ %dMB Free
to
205,%c:\ %luMB Free
Patched file is here: http://www.winpack.o...tr/98/sysdm.zip
But what about all other changes in 4.10.2224 version of sysdm.cpl file? Does anybody know about them?
Petr
205,%c:\ %dMB Free
to
205,%c:\ %luMB Free
Patched file is here: http://www.winpack.o...tr/98/sysdm.zip
But what about all other changes in 4.10.2224 version of sysdm.cpl file? Does anybody know about them?
Petr
Quote
MORE INFORMATION
This fix also limits the spinner control to 4,096 megabytes (MB) because that is the upper boundary for a paging file.
This fix also limits the spinner control to 4,096 megabytes (MB) because that is the upper boundary for a paging file.
Not a very interesting fix. Meaby just changing the resource will do for most people
Share this topic:
Page 1 of 1



Help
Back to top









