Alright working on an app that includes SetFSB for overclocking purposes. Using ShellExecute() or something similar to launch the app silently with parameters.
One of the parameters is the FSB setting.
I know that SetFSB has a flaw in its design to where it shows data based on a fixed ram ratio with the fsb 2:1.
Do people who don't have that ratio have to supply an other than actual fsb speed when sending the parameters to the command line.
If not my jobs easy if yes then i have to detect the FSB:Ram ratio and compensate for input.
-
RainMotorsports Formerly ClutchX2
-
moral hazard Notebook Nobel Laureate
The answer is no, so your job is easy.
Can you send me a beta version of your app -
RainMotorsports Formerly ClutchX2
LOL its targeted as a replacement for Direct Console on some ASUS models but stripped down it makes an alright replacement for something like that auto clock tray tool that already exists.
There will be a beta thread. First version will target G50 users (and G51 if u have or dont mind using the newer shareware setfsb.) I dont have the time to code the whole thing to release as a beta so itll be peice by peice.
Still waiting on news about lighting control on some of the ASUS Models. -
RainMotorsports Formerly ClutchX2
Bah had been awhile since i had tried.
Turns out you can not set the fsb using the real number if the ram fsb ratio isnt correct. SetFSB reads myne as 200 mhz when its at 266mhz setting it to 300 instant crashes but 220 sets it to 293...
Yay.... -
moral hazard Notebook Nobel Laureate
Seems to work fine for me.
EDIT:
I used this:
http://forum.notebookreview.com/hp-...52887-2510p-owners-lounge-36.html#post5737939
http://rapidshare.com/files/438674198/faster.zipAttached Files:
-
-
RainMotorsports Formerly ClutchX2
Rather interesting I will have to find out what makes the difference. Otherwise I would have to leave it up to the users to supply absolutely correct values.
The only thing SetFSB detects correctly on my machine is the CPU Clock. ICS9LPR604AGLF is the PLL the G50's use, might just be the PLL thats the problem. But the SetFSB help file specificly says thats its a known bug that on this chipset and many others the ratio is 1:2 fixed making 2:3 setups not read right.
SetFSB Ram Ratio Command Line Setting Question
Discussion in 'Windows OS and Software' started by RainMotorsports, Dec 20, 2010.