HELP!!: Intel SpeedStep and Windows 2000 DISABLED

[brosen]

I have not been able to make work the Intel SpeedStep module within Windows 2000, the SpeedStep TAB within the Power applet in Control Panel, is DIMMED, so it is not possible to modify any option, any idea why the SpeedStep is disabled ?, thanks

[domi]

I'm having the same problem on my brand-new X60s. Have you been able to find a solution? PRPCUI.EXE and PRPCUI.DLL did get copy to \WINNT\SYSTEM32, but PRPCUI.EXE won't load (doesn't show up in Task Manager) and all options for the SpeedStep tab in Power Options are greyed out.

[domi]

I have not been able to make work the Intel SpeedStep module within Windows 2000, the SpeedStep TAB within the Power applet in Control Panel, is DIMMED, so it is not possible to modify any option, any idea why the SpeedStep is disabled ?

Some meager progress on the SpeedStep front with W2K: after disabling the CoreDuo feature in BIOS, I was able to get prpcui.exe to load, and the SpeedStep tab options in Power Options were no longer greyed out. Also, the "From OS" option (Method to get the frequency) was no longer greyed out in MobileMeter (before that, I only had "Measure Actual"). However, even with "From OS" selected, the CPU speed got stubbornly stucked at 1.66GHz, which means I'm still not able to change the speed using power profiles. Lack of SpeedStep support in W2K with the new Core Duo machines really sucks

[brosen]

I have not been able to make work the Intel SpeedStep module within Windows 2000, the SpeedStep TAB within the Power applet in Control Panel, is DIMMED, so it is not possible to modify any option, any idea why the SpeedStep is disabled ?

Some meager progress on the SpeedStep front with W2K: after disabling the CoreDuo feature in BIOS, I was able to get prpcui.exe to load, and the SpeedStep tab options in Power Options were no longer greyed out. Also, the "From OS" option (Method to get the frequency) was no longer greyed out in MobileMeter (before that, I only had "Measure Actual"). However, even with "From OS" selected, the CPU speed got stubbornly stucked at 1.66GHz, which means I'm still not able to change the speed using power profiles. Lack of SpeedStep support in W2K with the new Core Duo machines really sucks

The old utilities like MobileMeter, I do not know why, but they do not work with CoreDuo, you need to use the newer ones, like EVEREST, Rightmark CPU, NHC, etc. they will show you the right speed, even in Windows XP Mobilemeter will always show MAX SPEED value, please could you tell me more about your experience with Windows 2000 with CoreSolo, I am afraid I will loose a lot of performance compare to CoreDuo, thanks

[brosen]

I'm having the same problem on my brand-new X60s. Have you been able to find a solution? PRPCUI.EXE and PRPCUI.DLL did get copy to \WINNT\SYSTEM32, but PRPCUI.EXE won't load (doesn't show up in Task Manager) and all options for the SpeedStep tab in Power Options are greyed out.

The only way is to configure the machine as CoreSolo

[domi]

The old utilities like MobileMeter, I do not know why, but they do not work with CoreDuo, you need to use the newer ones, like EVEREST, Rightmark CPU, NHC, etc. they will show you the right speed,

I downloaded all three utilities (took me some time, as I only have a GPRS-based connection right now). We may be in luck with the latest NHC 2.0. See
http://www.pbus-167.com/nhc/nhc_faq.htm ... ease_notes
:

NHC 2.0 - Pre-Release-02 (01.08.2006)
- fixed the bug (Read Processor Policy failed) on Windows 2000

NHC 2.0 - Pre-Release (31.07.2006)
- removed the Intel Core Duo CPU Speed bug
- add CPU Speed Control for Windows 2000 and Windows Vista (preliminary)

even in Windows XP Mobilemeter will always show MAX SPEED value,

Well, not in my experience: MobileMeter displayed the right speed immediately as I switched from one profile to another.

please could you tell me more about your experience with Windows 2000 with CoreSolo, I am afraid I will loose a lot of performance compare to CoreDuo, thanks

I'll let you know as soon as I get a chance to play with my X60s under W2K. I'm not too worried about using its CoreDuo as a CoreSolo, my main interest lies in reducing the CPU speed and heat emissions.

[brosen]

The old utilities like MobileMeter, I do not know why, but they do not work with CoreDuo, you need to use the newer ones, like EVEREST, Rightmark CPU, NHC, etc. they will show you the right speed,

I downloaded all three utilities (took me some time, as I only have a GPRS-based connection right now). We may be in luck with the latest NHC 2.0. See
http://www.pbus-167.com/nhc/nhc_faq.htm ... ease_notes
:

NHC 2.0 - Pre-Release-02 (01.08.2006)
- fixed the bug (Read Processor Policy failed) on Windows 2000

NHC 2.0 - Pre-Release (31.07.2006)
- removed the Intel Core Duo CPU Speed bug
- add CPU Speed Control for Windows 2000 and Windows Vista (preliminary)

even in Windows XP Mobilemeter will always show MAX SPEED value,

Well, not in my experience: MobileMeter displayed the right speed immediately as I switched from one profile to another.

please could you tell me more about your experience with Windows 2000 with CoreSolo, I am afraid I will loose a lot of performance compare to CoreDuo, thanks

I'll let you know as soon as I get a chance to play with my X60s under W2K. I'm not too worried about using its CoreDuo as a CoreSolo, my main interest lies in reducing the CPU speed and heat emissions.[/url]

Excellent, I'll test it today

[dclee012]

*bump*

Was this issue ever resolved? Speedstep in Win2k is also disabled for me. It doesn't seem to play well with Core Duo's Enhanced SpeedStep...

Any help?
-Dave