303 Posted December 5, 2005 Posted December 5, 2005 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
Gape Posted December 5, 2005 Posted December 5, 2005 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.
Petr Posted December 5, 2005 Posted December 5, 2005 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?ThanksIt 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?PetrWhy 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
Petr Posted December 6, 2005 Posted December 6, 2005 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 Freeto205,%c:\ %luMB FreePatched file is here: http://www.winpack.org/petr/98/sysdm.zipBut what about all other changes in 4.10.2224 version of sysdm.cpl file? Does anybody know about them?Petr
LLXX Posted December 7, 2005 Posted December 7, 2005 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 Freeto205,%c:\ %luMB FreePatched file is here: http://www.winpack.org/petr/98/sysdm.zipIt looks like they originally thought you could have negative free space on a hard drive...
Acheron Posted December 7, 2005 Posted December 7, 2005 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 Freeto205,%c:\ %luMB FreePatched file is here: http://www.winpack.org/petr/98/sysdm.zipBut what about all other changes in 4.10.2224 version of sysdm.cpl file? Does anybody know about them?PetrMORE INFORMATIONThis 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
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now