Directo Console Modification for Overclocking

I was wodnering if there is any way to modify the direct console program and set new overclocking values.
thanks!

 

What's the point though? The benefit of Direct Console is that it can take our CPUs to a higher speed but WITHIN warranty.

There are a few other apps you can use to OC your cpu outside of direct console, such as setfsb.

 

The benefit of Direct Console is that it douwnclocking RAM, so CPU can be OC more, than with setfsb. ANY knowlegable man
sorry for my bad english

 

It's er... kinda non-legible.

 

directconsole uses a GetStep/SetStep function combo. where it is getting the values from idk (i dont have vista or a debugger for vista), but my guess is some undocumented powerprof/acpi functions unique to vista's powerprof.dll (meaning it will NOT WORK WITH XP). i have tried remapping the renamed functions (eg. GetDCIndexValue -> GetDCValue or whatever the recognizeable ones were), still crashes with an entry point not found.

my guss is SetStep uses GetStep and adds X where X is GetStep + a normal integer (as defined by the register holding the Normal/High/Performance values). two methods of changing it:

1) with a debugger, find the mem registers (with a breakpoint before the addition). then find the data and change it in hex (its a normal signed integer, so it should be visible from the code).

2) create your own interface for the OvrClk.dll file. they are all decorated functions, built with MSVC9. you can use their undecorator for parameters.

directconsole does NOT underclock the ram. at 400MHzDDR it is stable for ~3.1GHz. underclocking it would lower the highest achievable setfsb value. the cpu is more than good atm, so unless i absolutely need more power and install vista, i cant try anything.

 

this: http://xs.to/xs.php?h=xs135&d=09043&f=cpu-z_and_win_score265.jpg
from here: http://forum.notebookreview.com/showpost.php?p=4425818&postcount=500
looks promising. the GetStep/SetStep arguments fit, so it might not be a coincedence. i haven't used RMClock for anything besides temps, so maybe im doing something wrong, but theres an "UnlockFid" tweak in the registry (i don't see any additional FIDs).

it could be worth a shot.

and, are the people on vista on a 95% throttle? DMI doesn't have much CPU info, so i'll look through the intel microcode for some common types.

nothing containing 95 in the microcode.

 

any news ............