that the chipset disconnects Front Side Bus after receiving request generated by the processor. Majority of K7 chipsets support this, but on older motherboards this is often not enabled by default due to problems with this feature. Those problems are usually in form of sound crackles, lowered HDD performance, PCI problems etc. For proper functionality of this feature, you need a chipset-enabled FSB disconnect after Halt special system bus cycle (set by BIOS, otherwise use WPCREDIT/WPCRSET). Higher divisors result in lower frequency what turns in somewhat lower temperature and lower power consumption. On the other hand, those higher divisors tend to cause problems described above and sometimes even to systems hangs. The result of enabling C1/Halt Bus Disconnect can be as much as 15 degrees Celsius temperature decrease. Different divisors have somewhat lower effect, the difference between 8 and 512 can be 5 degrees at most.
<li><b>Stop Grant Disconnect Clock Divisor</b> - this is the same as for Halt Disconnect Clock Divisor with the difference that this one sets frequency divisor for C2/Stop Grant power saving mode. The effect of power requirements reduction is the same as in case of C1/Halt mode, but there are few differences. First - chipset has to be set to disconnect FSB upon receiving Stop Grant request, not Halt request. On many chipsets, there are separate bits for Halt and for Stop Grant, so be sure to set the right one. Second - you do not need any program to enter to C2 Stop Grant state because Windows 2000/XP have already integrated mechanism that does this, provided that C2 state is defined and allowed to be used in the ACPI table.
<li><b>Full Ramp</b> - determines a max possible delay when ramping up/down the internal CPU clock. No information is currently available for this setting, so it's best to leave it default.
<li><b>Ramp Delays (Clock Change Timings)</b> - these settings affect time between clock changes inside the CPU while entering to/from C1/Halt or C2/Stop Grant states, provided that the Halt/Stop Grant Bus Disconnect is enabled in the chipset settings. Faster settings mean lower latencies and therefore higher performance and better resistance to problems with sound cards, HDD performance etc. But on the other hand, faster settings impose higher requirements on internal clock generator. If you experience problems with stability, use the slower settings (e.g., 8 or 16 for all fields).
<li><b>Enable Stop Grant APIC Bus Disconnect</b> - controls whether the CPU should reject any APIC Bus messages while being in C2/Stop Grant state. If you have problems with this low-power mode, try disabling this option.<br>
<b>NOTE:</b> APIC Bus Disconnect has nothing to do with the AMD S2K Bus Disconnect feature that is enabled separately in the chipset configuration registers settings and is beyond the scope of RMClock utility.
</ul>
<h4>P-State Transitions Settings</h4>
<p>The utility must be restarted for these settings to have an effect.</p>
<ul>
<li><b>Stop Grant Timeout Count</b> - defines the amount of the system bus cycles the CPU will enter into a Stop Grant state for, after completing a FID/VID transition.
<li><b>FID Transition Stabilization Time</b> - sets the amount of the artificial CPU delay after every single FID transition, in microseconds.
<li><b>VID Transition Stabilization Time</b> - sets the amount of the artificial CPU delay after every single VID transition, in microseconds.
<li><b>VID Table Select</b> - lets the user choose whether the utility will use an internal K7 VIDs table for a mobile or a low-power desktop CPU.
</ul>
<p><b>Remember these settings</b> - makes the utility apply the low power modes settings every time the utility starts (or when the system is restored from Standby/Hibernate states).</p>
<h3><a name="ui_adv_k8"></a>Advanced page (AMD K8 processors)</h3>
<h4>Power Management Settings (Per ACPI State)</h4>
<ul>
<li><b>ACPI State to Show/Modify</b> - sets the ACPI power management state to manipulate with. These states correspond to PMM0-PMM7 System Management Action Field (SMAF) codes and are as follows: PMM0 = C2 (Stop Grant); PMM1 = C3 (Sleep); PMM2 = C0, FID/VID Change; PMM3 = S1 (POS); PMM4 = S3 (STR); PMM5 = C0, Throttling; PMM6 = S4/S5 (STD/SOFF); PMM7 = C1 (Halt).
<li><b>Clock Divisor Select</b> - specifies the divisor to use when ramping down the CPU clock or the Northbridge clock.
<li><b>CPU Low Power Enable</b> - causes the CPU clock to ramp down according to the clock divisor specified in <b>Clock Divisor Select</b>.
<li><b>Northbridge Low Power Enable</b> - causes the Northbridge clock to ramp down according to the clock divisor specified in <b>Clock Divisor Select</b> and puts the DRAM in self-refresh mode. The CPU clock must also be ramped down (see <b>CPU Low Power Enable</b>).
<li><b>FID/VID Change Enable</b> - enables a change in Frequency ID (FID) and/or Voltage ID (VID). The CPU and the Northbridge clocks must also be ramped down (see <b>CPU Low Power Enable</b> and <b>Northbridge Low Power Enable</b>).<br>
<b>NOTE:</b> this setting should normally be enabled only for the &quot;C0, FID/VID Change&quot; ACPI state.
<li><b>Alt VID Change Enable</b> (revision E cores only) - For mobile processors that are revision E and later revisions that use discrete graphics, the hardware can be programmed to drive an alternate VID code during the C3 processor power state. The purpose of the AltVID is to reduce the processor voltage to the minimum operational level while the processor is in the C3 state. This setting enables a VID change to the value specified in the Alternate VID field after CPU clocks and Northbridge clocks are ramped down. This mode should never be set for FID/VID changes or when UMA graphics are used.
<li><b>Alternate VID</b> (revision E cores only) - specifies the alternate VID while in low power states with AltVID Change enabled. If an attempt is made to write a VID value that is greater than MaxVID, then the MaxVID value is written instead. If an attempt is made to write a VID value that is lower than the MinVID, then the MinVID value is written instead.
<li><b>Alternate VID Stabilization Time</b> (revision E cores only) - indicates the amount of time required to stabilize the voltage regulator. For revision E and later mobile systems that enable AltVID, this field should be programmed to account for the time it takes to ramp the voltage from AltVID to the VID for the 800MHz P-state, i.e.: VSTIME = ((800 MHz VID) - AltVID) * 1us/mV.
<li><b>Defaults</b> - loads the predefined values (as recommended by the vendor) for Mobile, Desktop or a Server processor.<br>
<b>NOTE:</b> it is possible (and recommended) to apply &quot;Desktop&quot; or even &quot;Mobile&quot; profile on Opteron-based server systems (including the multiprocessor ones). This will significantly reduce CPU power consumption during Halt (but may slightly reduce system performance).
</ul>
<h4>Clock Power/Timings</h4>
<ul>
<li><b>Good Phase Error</b> - defines the BCLK PLL time until good phase error, in microseconds. Counting occurs when at full frequency.
<li><b>Clock Ramp Hysteresis</b> - a non-zero value enables a hysteresis time (in nanoseconds) which prevents the CPU clock grid from being ramped down after processing a probe. It avoids unnecessary changes of the CPU clock grid when the probe arrival rate is relatively low.
<li><b>HTT Clock PLL Lock Counter</b> - indicates how long it takes for the slowest HyperTransport technology clock PLL to ramp to its new frequency and lock (in microseconds).
<li><b>Defaults</b> - loads the predefined values for the systems with Unbuffered or Registered DIMMs.<br>
<b>NOTE:</b> if you experience problems with the AMD Cool`n'Quiet(tm) technology operation and have multiple memory modules installed, try applying &quot;Registered DIMMs&quot; profile, which will force the CPU to use longer stabilization times.
</ul>
<h4>P-State Transitions Settings</h4>
<p>You must restart the utility for these settings to have an effect.</p>
<ul>
<li><b>Stop Grant Timeout Count</b> - sets the amount of the system bus cycles the CPU will enter into a Stop Grant state for, after completing a single FID transition.
<li><b>Max Ramp Voltage Offset</b> - defines the maximal amount of extra voltage, in milliVolts, that is applied when performing a series of VID transitions. This extra voltage is removed after completing a FID/VID transition sequence.
<li><b>FID Transition Stabilization Time</b> - sets the amount of the artificial delay applied after every single FID transition, in microseconds.
<li><b>VID Transition Stabilization Time</b> - sets the amount of the artificial delay applied after every single VID transition, in microseconds.
<li><b>Follow AMD P-State Transitions rules</b> - instructs the utility to use the official AMD P-state transitions rules (with the VCO frequency change steps of 200 MHz or less and the 25-mV VID change steps).<br>
<b>NOTE:</b> the availability of lower FIDs (4x to 7x) in this case depends on the CPU model installed.
<li><b>Use Direct P-State Transitions</b> - relaxes the official AMD P-state transitions restrictions and allow direct jumps between any FID values, including all lower FIDs.<br>
<b>NOTE:</b> VID transitions are still performed in 25-mV steps. This behavior is by design for versions 1.5 and higher.
<li><b>Allow Half FIDs</b> - allows the utility to use half FIDs (not officially documented by AMD). This setting is available only for the Direct P-State Transitions scheme.
</ul>
<p><b>Remember these settings</b> - makes the utility apply the user-defined ACPI power management and clock power/timing settings every time the utility starts (or when the system is restored from Standby/Hibernate states).</p>
<h3><a name="ui_adv_centrino"></a>Advanced page (Intel Centrino platform / Processor settings)</h3>
<h4>Automatic Thermal Protection</h4>
<p>Sets the preferred way of automatic thermal protection (Thermal Monitor 1 or Thermal Monitor 2, if available).<br>
<b>NOTE:</b> the CPU is operating out of spec when both TM1 and TM2 are disabled.</p>
<h4>Thermal Monitor 2 Target</h4>
<p>Defines the FID and VID values the CPU will transition to on activation of the Thermal Monitor 2 feature, provided the CPU supports TM2 and TM2 target programming.</p>
<h4>Enhanced Intel SpeedStep (EIST) Settings</h4>
<ul>
<li><b>Enable Enhanced Intel SpeedStep Technology</b> - allow to enable/disable the Enhanced Intel SpeedStep (EIST) technology. EIST must be enabled for the P-state transitions management feature to work.<br>
<b>NOTE:</b> some processors have this setting as a read-only - i.e., trying to disable the enabled setting or enabling the disabled won't have any effect.
<li><b>FID/VID Transition Stabilization Time (us)</b> - sets the amount of the artificial delay applied after every single FID+VID transition, in microseconds.
</ul>
<h4>Enhanced Low Power States</h4>
<p>These settings allow to enable or disable any of the given enhanced C-states (C1E, C2E, C3E, C4E and Hard C4E) available on Intel Core Solo/Core Duo processors. When an Enhanced C-state is enabled, the CPU is automatically put into the lowest frequency/voltage mode when it enters a given C-state.</p>
<h3>Advanced page (Intel Centrino platform / Platform settings)</h3>
<ul>
<li><b>Enter C4 on C3 command</b> - causes the chipset to transition the CPU into a deeper power-saving C4/Deep Sleep state when a C3/Sleep state is requested. This setting is available for mobile chipsets only (ICH4-M, ICH6-M and ICH7-M).
<li><b>Enable CPUSLP# in C3/C4</b> - enables CPUSLP# signal to go active in C3 and C4 power-saving states, thus reducing the processor power. This setting is available only for i855 chipsets (ICH4/ICH4-M); this feature is always enabled on ICH6/ICH7 chipsets.
<li><b>Enable CPUSLP# in S1</b> - enables CPUSLP# signal to go active in S1 (Power On Suspend) state, thus reducing the processor power. This setting is available only for ICH6 and ICH7 families; this feature is always enabled on ICH4.
<li><b>Enable C4 in S1-M</b> - if this option is set, then when entering the S1-M state, the ICH4-M will use the C4 sequence, rather than the standard sequence. This setting is available only for ICH4-M.
<li><b>Enable Popup mode</b> (auto C3/C4 to C2) - when this option is off, any bus master traffic causes the chipset to return from C3 or C4 state into C0 (working) state. When this option is on and the chipset observes a bus master request, it will take the system from C3 or C4 state into C2 state and enable bus masters. This will let snoops and memory access occur. This setting is available only for ICH6-M and ICH7-M.
<li><b>Enable Popdown mode</b> (auto C2 to C3/C4) - this option should be used in conjunction with Popup mode. When this option is off, the chipset will not attempt to automatically return into a previous C3 or C4 state. When this option is on, and the chipset observes no bus master requests, it can return into previous C3/C4 state. This setting is available only for ICH6-M and ICH7-M.
<li><b>CPU PLL Lock Time</b> - indicates the amount of time the processor needs to lock its PLLs (it has an effect while entering into/returning from C3/C4 states). A minimal lock time of 30.72 us is used by default. This setting is available for ICH4-M, ICH6 and ICH7 family chipsets.
<li><b>CPUSLP# to STPCLK# Delay</b> - sets the delay between CPUSLP# going inactive to STPCLK# going inactive, in 3.84 ns units. The default value is approximately 50.045 us. This setting is available for ICH4 family chipsets only.
<li><b>DPSLP# to CPUSLP# Delay</b> - sets the amount of time the chipset waits from the deassertion of DPSLP# to the deassertion of CPUSLP#. By default, this is determined by the CPU PLL Lock Time. This setting is available only for ICH6-M and ICH7-M.
<li><b>DPRSLPVR to STPCPU# Delay</b> - sets the amount of time the chipset waits from DPRSLPVR going inactive to STP_CPU# going inactive. This provides a programmable time for the processor's voltage to stabilize when exiting from a C4 state. This setting is available only for ICH6-M and ICH7-M.
</ul>
<p><b>Remember these settings</b> - makes the utility apply the user-defined Automatic Thermal Protection, Enhanced SpeedStep and Centrino chipset settings every time the utility starts (or when the system is restored from Standby/Hibernate states).</p>
<h3><a name="ui_adv_p4"></a>Advanced page (Intel Pentium 4 and Xeon processors)</h3>
<h4>Automatic Thermal Protection</h4>
<p>Sets the preferred way of automatic thermal protection (Thermal Monitor 1 or Thermal Monitor 2, if available).<br>
<b>NOTE:</b> the CPU is operating out of spec when both TM1 and TM2 are disabled.</p>
<h4>Thermal Monitor 2 Target</h4>
<p>Defines the FID and VID values the CPU will transition to on activation of the Thermal Monitor 2 feature, provided the CPU supports TM2 and TM2 target programming.</p>
<h4>Enhanced Intel SpeedStep (DBS) Settings</h4>
<ul>
<li><b>Enable Enhanced Intel SpeedStep Technology</b> - allow to enable/disable the Enhanced Intel SpeedStep (DBS) technology. DBS must be enabled for the P-state transitions management feature to work.
<li><b>FID/VID Transition Stabilization Time (us)</b> - sets the amount of the artificial delay applied after every single FID+VID transition, in microseconds.
</ul>
<h4>Misc Settings</h4>
<ul>
<li><b>Enable Enhanced Halt State (C1E)</b> - enables/disables the Enhanced Halt state (C1E) feature available in Prescott and Nocona/Irwindale cores, revisions E0 and later. When Enhanced halt state is enabled, the CPU automatically puts itself into the lowest frequency/voltage mode when it enters a C1 state.
</ul>
<p><b>Remember these settings</b> - makes the utility apply the user-defined Automatic Thermal Protection, Enhanced SpeedStep and misc settings every time the utility starts (or when the system is restored from Standby/Hibernate states).</p>
<h3><a name="ui_adv_tmta"></a>Advanced page (Transmeta processors)</h3>
<h4>Power Source Select</h4>
<p>Displays current power source (upon Refresh button), and allows to select the power source you want to view/modify the settings for.</p>
<h4>LongRun Status and Control</h4>
<ul>
<li><b>LongRun Bounds</b> - displays/sets the lower and upper boundaries of the processor's performance window. A performance window (i.e., variable CPU performance according to its current load level) can be achieved by specifying different values for upper and lower boundaries. A fixed performance level can be achieved by specifying the same value for both the upper and lower boundary. Setting both boundaries to 100% effectively disables LongRun, and results in maximum performance, but shorter battery lifetime. By contrast, setting both boundaries to 0% results in minimum performance, but best battery lifetime. The processor will round the specified values up or down to the nearest value, depending on how many performance levels are supported. If both directions of rounding are possible, then the processor will round up.
<li><b>Operation Mode</b> - controls whether LongRun is in &quot;economy mode&quot; or in &quot;performance mode&quot;. In &quot;economy mode&quot; the processor attempts to maximize battery lifetime, by powering down aggressively. By contrast, in &quot;performance&quot; mode it attempts to maximize performance, by powering down conservatively.
<li><b>Defaults</b> - allows you to load one of the predefined LongRun Bounds values (Minimal, Maximal, or Automatically Variated).
</ul>
<h4>LongRun Advanced Thermal Management</h4>
<p><b>ATM Level</b> - selects the processor power reduction target. LongRun will attempt to meet or exceed the power reduction level specified in this field by lowering the processor frequency and voltage. This setting has priority to reduce the processor frequency below that which is selected in the LongRun Bounds. This setting will never have the effect of increasing the processor freqeuency and voltage.</p>
<h4>LongRun Table Interface Data</h4>
<p>Lists available processor's LongRun levels, with detailed info on each of them.</p>
<p><b>Remember these settings</b> - makes the utility apply the user-defined LongRun and LongRun ATM settings every time the utility starts, when the system is restored from Standby/Hibernate states and when the power source changes.</p>
<h3><a name="ui_tray"></a>Tray icon menu</h3>
<h4>Main tray icon menu</h4>
<ul>
<li><b>View/Hide Main Window</b> - shows/hides the main application window. This is the default action performed by double-left-clicking the main tray icon.
<li><b>Profile</b> - provides a quick access to the profiles selection menu. This menu is also shown by left-clicking the main tray icon. This feature is unavailable when both PST and ODCM management are not supported by the CPU.
<li><b>Show Balloon Tooltips</b> - enables/disables display of the info balloon tooltips.
<li><b>Show Performance Level in Icon</b> - animates the main tray icon with the current CPU performance level when the Performance on Demand mode is used.
<li><b>Show CPU Frequency in Tray</b> - enables/disables display of the CPU frequency indicator in the system tray.
<li><b>Show CPU Load in Tray</b> - enables/disables display of the CPU/OS load indicator in the system tray.
<li><b>Alert on CPU Thermal Throttling</b> - enables the utility to alert user with a warning balloon tooltip whenever the CPU enters into a thermal throttling state (i.e., on activation of TM1 or TM2). This feature is available only for Intel Pentium M and Pentium 4/Pentium D processor families.
<li><b>Window Always on Top</b> - makes the main application window stay on top of all other windows.
<li><b>Start Minimized to Tray</b> - makes the utility start minimized to tray (not showing the main application window).
<li><b>Run Automatically at Startup</b> - adds a shortcut to the application executable to the HKCU\Software\Microsoft\Windows\Current Version\Run registry key so that the application starts automatically whenever the user's Windows session starts.
<li><b>Exit</b> - exits RMClock utility.
</ul>
<p><b>CPU frequency indicator menu</b></p>
<ul>
<li><b>View/Hide monitoring</b> - if the application window is hidden, shows the application window, going directly to the Monitoring page; otherwise, hides the application window. This is the default action performed by double-left-clicking the frequency indicator tray icon.
<li><b>Display</b> - sets the display mode (CPU Frequency or CPU Throttle indication).
<li><b>Hide Icon</b> - hides the CPU frequency indicator icon.
<li><b>Exit</b> - exits RMClock utility.
</ul>
<p><b>CPU load indicator menu</b></p>
<ul>
<li><b>Launch Task Manager</b> - launches Windows Task Manager application.
<li><b>Display</b> - sets the display mode (CPU Load, OS Load, or both).
<li><b>Hide Icon</b> - hides the CPU load indicator icon.
<li><b>Exit</b> - exits RMClock utility.
</ul>
<h3><a name="ui_cmd"></a>Command-line parameters</h3>
<p>Beginning with version 1.6, RMClock can be launched with command-line parameters. Some of these commands work only at the first program startup (diagnostic or debug commands), others require that the utility is already running (control commands). Currently implemented command-line parameters include:</p>
<ul>
<li><b>-?, -help</b> - displays list of the command-line options
<li><b>-profile <i>n</i></b> - sets the profile (AC or Battery, depending on the power source) of the currently running application instance to <i>n</i>.
<ul>
<li><i>n</i> = 0: No Management
<li><i>n</i> = 1: Minimal
<li><i>n</i> = 2: Maximal
<li><i>n</i> = 3: Automatic Management
</ul>
<li><b>-nextprofile</b> - sets next profile, relative to current profile.
<li><b>-prevprofile</b> - sets previous profile, relative to current profile.
<li><b>-resume</b> - simulates a &quot;resume&quot; event (normally occurring at a resuming from Standby/Hibernate or a power source change).
<li><b>-exit</b> - exits currently running instance of the application.
<li><b>-unload</b> - attempts to uninstall currently loaded instance of the RTCore32/RTCore64 driver (must be specified at the program startup).
</ul>
<h3><a name="ui_misc"></a>Miscellaneous options</h3>
<ul>
<li>There're additional configuration options (tweaks) available beyond the application's user interface and command-line parameters. For a list of these options and their possible values, see <i>RMClock_Tweaks.reg</i> file. To apply these settings, just double-click this file to update the program registry entries.
<li>To wipe out all program settings stored in the registry, apply the <i>RMClock_WipeOut.reg</i> registry file. <b>NOTE:</b> Please use this feature only in extreme cases (e.g., if you set too unrealistic values so that RMClock can no longer start without locking up your system).
</ul>
<h2><a name="compat"></a>Compatibility</h2>
<h3>CPU Power Management drivers/software</h3>
<p>RMClock is compatible with AMD Cool`n'Quiet(tm) / PowerNow!(tm), Enhanced Intel(R) SpeedStep(tm) and Transmeta LongRun(tm) software, provided it is not currently active. There's no need to uninstall existing processor driver, moreover, beginning with version 2.0, RMClock automatically disables the driver's power management by selecting its own power scheme at the program start-up. Current power scheme is automatically restored upon exiting RMClock utilty.</p>
<h3>Performance analyzing software</h3>
<p>Since RMClock relies upon CPU-specific performance monitoring counters (PMC) to determine the CPU usage level, compatibility issues are possible with application performance analyzing applications like Intel VTune or AMD CodeAnalyst, which use the same counters to monitor processor-specific performance events. Therefore, you should quit RMClock utility before using this kind of software.</p>
<h3>Benchmarking software</h3>
<p>As with any power management software, the performance/power management features of RMClock should be disabled before running any benchmarking software (e.g., your profile should be set to &quot;No Management&quot;, or one of the fixed performance state profiles). Otherwise, you may get incorrect benchmark results.</p>
<h2><a name="faq"></a>Frequently Asked Questions</h2>
<p><b>Q: How do I quickly set up RightMark CPU Clock Utility so that it performs automatic management of my CPU performance/power?</b></p>
<p><b>A:</b> Beginning with version 2.05, the easiest way to set up your new or updated RMClock installation is to go to the <b>Management and Profiles</b> page and click the <b>Defaults</b> button. Confirming this action will set up all four basic profiles with their default values, apply the management settings defaults and set the &quot;Performance on Demand&quot; profile as your current profile. Your CPU must support the required power management features, otherwise, this option will be disabled.<br><b>NOTE:</b> Your system might lock up as a result of this action if your hardware isn't properly configured to support the CPU power management features (e.g., for AMD Athlon 64 systems, if you have a motherboard not certified for AMD Cool`n'Quiet or have disabled Cool`n'Quiet support in the BIOS settings).</p>
<p><b>Q: How do I uninstall RightMark CPU Clock Utility?</b></p>
<p><b>A:</b> Uninstalling RMClock is really easy. It is enough just to exit the utility if it is currently running and completely delete the folder you have installed it into. To ensure a complete clean-up of the program registry settings, you can apply the <i>RMClock_WipeOut.reg</i> file found in RMClock folder before deleting.</p>
<p><b>Q: Why can't I run RMClock as a regular user?</b></p>
<p><b>A:</b> RMClock is a low-level system utility that requires privileged access to the CPU hardware, which can be done only via a kernel-mode driver (RTCore32/64.sys, which is dynamically extracted and installed at runtime). Administrative rights are required to install and load this driver, therefore, current versions of the utility can be run only by the users with administrative privileges.</p>
<p><b>Q: CPU voltage indicated by RMClock greatly differs from the voltage reported by my vendor-supplied monitoring software. What's wrong?</b></p>
<p><b>A:</b> Nothing. RMClock reports the CPU VID, i.e., just the <i>requested</i> CPU voltage level. It is up to the motherboard logic to decide whether this request should be handled or ignored. Most motherboards designed to properly support processor's power-saving features (e.g., AMD Cool`n'Quiet(tm) technology) should adjust the real CPU voltage so that it's close to the requested VID level. Other models may apply some extra over-voltage (e.g., +0.1 or +0.2V), which is useful for overclocking. Finally, there are many motherboard models that can be set up (via BIOS settings) to supply constant voltage to the CPU, which is far from being good for achieving significant power saving.</p>
<p><b>Q: Why can't I set CPU voltage above 1.55V (or even 1.45V), or below 1.1V on my Athlon 64? BIOS setup offers the voltages from 0.8V up to 1.7V. Is there a way to unlock these &quot;hidden&quot; voltages?</b></p>
<p><b>A:</b> RMClock manipulates with VID and not directly with the CPU voltage. Maximal VID value you can set is dictated by the CPU itself (as indicated in the &quot;Maximal VID&quot; field of the General page), as well as the Minimal VID. 1.55V is the <i>absolute maximum</i> VID for all Athlon 64 processors family; usually, maximal VID is even lower (e.g., 1.45V). There's no way to set current VID value higher than the maximal, as the CPU will choose maximal value instead (the same is true for FID, the bus clock multiplier). It is also impossible to program a VID being lower than the Minimal VID reported by the CPU. The voltage level you adjust in the BIOS is set in entirely different way, via direct manipulation with the CPU VRM and not involving VID changes. Please also note that the voltages you set manually in the BIOS setup cause the motherboard logic to ignore VID change requests, thus greatly diminishing power saving features of the AMD Cool`n'Quiet(tm) technology.</p>
<p><b>Q: In the Advanced page I can adjust the Halt and Stop Grant bus disconnect divisors for my Athlon XP, but they don't seem to have any effect. What's wrong?</b></p>
<p><b>A:</b> Nothing. These settings only affect the CPU internal clock divisors. They do not enable bus disconnect for a Halt and/or Stop Grant state, which must be done in a chipset-specific way. No support for this and numerous chipsets series is ever planned.</p>
<p><b>Q: In the Advanced page I see various ACPI states for my Athlon 64. What state should I choose?</b></p>
<p><b>A:</b> You don't have to choose anything particular. This is just a selector that allows changing the settings of a given ACPI state. It does not enable or even put the CPU into this particular state.</p>
<p><b>Q: In the Advanced page of RMClock I see really a lot of settings for my Athlon 64. What are these all settings for? What settings should I choose?</b></p>
<p><b>A:</b> These are advanced settings that should not be changed without a good knowledge. In fact, they should be left alone if you don't experience any problems with you system. However, it is safe to load one of the predefined sets of defaults by using the corresponding buttons. If you're interested in these settings in detail, please look through Chapter 9 of the public AMD document <i>&quot;BIOS and Kernel Developer's Guide for AMD Athlon(TM) 64 and AMD Opteron(TM) Processors&quot;, order #26094</i>.</p>
<p><b>Q: My Athlon 64 system locks up when I enable automatic PST management in RMClock, what to do?</b></p>
<p><b>A:</b> Before you start, please be sure to disable the power management features of the AMD processor driver by setting your current power scheme (in Windows control panel) to &quot;Home/Office Desk&quot; or &quot;Always On&quot;. This step is not necessary if you are using RMClock version 2.0 or higher and haven't disabled Windows power management handling in your profile settings.
<p>First, make sure you have selected relatively safe minimal and maximal FID/VID settings in your current profile settings (the ones selected by clicking Defaults button should be completely safe to begin with, provided your CPU is not overclocked).</p>
<p>Second, ensure that your CPU is properly setup to support FID/VID change requests. This should be done by a BIOS during POST, however, if your motherboard is not certified by AMD for Cool`n'Quiet(tm) technology support, it might be necessary to do this manually. Most efficiently, this can be done in the Advanced tab by loading the Power Management Settings defaults for a Desktop or Mobile processor (depending on the model you have). To automatically use these settings every time you launch RMClock, please check &quot;Remember these settings&quot; option.</p>
<p>Third, even if your motherboard is properly set up for AMD Cool`n'Quiet(tm) operation, you may experience problems with PST management if you have two or more memory modules installed, even with official AMD processor driver's management. In most cases, it is possible to solve this problem by applying the defaults for Registered DIMMs in the Clock Power/Timing Settings of the Advanced page. Once again, to automatically use these settings whenever you launch RMClock, please enable &quot;Remember these settings&quot; option.</p>
<p>If none of the above help, try updating your motherboard BIOS to the latest version. If this still doesn't help, we're sorry to inform you that you have a motherboard which is incompatible with AMD Cool`n'Quiet(tm) technology. RMClock does support a greater number of motherboards than the official AMD driver does, but it's not possible to support all of them in software, the compatibility must also exist on a hardware/motherboard design level.
<p><b>Q: I have an overclocked system that locks up when I exit the utility (or disable PST management), what to do?</b></p>
<p><b>A:</b> The problem is related to the &quot;Restore CPU Defaults on Exit&quot; setting, which is enabled by default. This setting causes the hard-coded CPU defaults (FID and VID) to be applied when you exit the utility or completely disable PST management. If your FSB clock is too high, the resulting CPU frequency is very likely to go beyond the safety margin. You can either totally disable this feature or alter its functionality so that it applies the FID/VID settings it found at the program startup instead of the CPU defaults (see RMClock_Tweaks.reg file).</p>
<p><b>Q: My processor is detected as an &quot;Unknown CPU&quot;. What's wrong? Will RMClock work properly with my CPU?</b></p>
<p><b>A:</b> It means that you have a new CPU core/revision, which RMClock isn't yet aware of. The CPU detection is implemented according to the official docs from the vendors, which are not updated as frequently as the new processors get launched. There's nothing to worry about, RMClock will work properly with your processor, provided that it supports the necessary power-saving features (as indicated in the &quot;PM Features&quot; box in the General page).</p>
<p><b>Q: The core frequency/throttle of my Athlon 64 CPU reported by RMClock stays the same, despite the FID changes. What's wrong?</b></p>
<p><b>A:</b> This is the OS implementation bug. It is usually observed on a multiprocessor systems (including AMD multi-core processors), when ACPI Multiprocessor PC kernel is used, as well as on a current Windows XP x64 Edition release, regardless of the kernel type. The problem is related to the High-Performance Counter (HPC) featured by the OS. Normally, the ACPI timer is used as a clock source for this counter, when the processor's Time Stamp Counter (TSC) frequency is known to get changed over time (as it does on a Cool`n'Quiet(tm)-enabled system). However, some OS implementations/kernels, like those mentioned above, erroneously choose TSC as a source of HPC clock, thus violating the main requirement for this counter (the frequency of HPC is guaranteed not to change over time). Since HPC frequency is no longer constant and changes in line with TSC frequency, we are getting incorrect TSC/HPC ratio and, therefore, incorrect CPU frequency indication.</p>
<p>Fortunately, a solution exists for this bug, and it requires editing the <b>boot.ini</b> file found at the root directory of your system disk drive (e.g., C:\boot.ini). To force the OS use the ACPI timer as HPC clock source, you need to add /USEPMTIMER option to your current system settings, e.g.,</p>
<blockquote>
<p><i>&quot;multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&quot;Microsoft Windows XP Professional&quot; /noexecute=optin /fastdetect&quot;</i></p>
</blockquote>
<p>should become:</p>
<blockquote>
<p><i>&quot;multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&quot;Microsoft Windows XP Professional&quot; /noexecute=optin /fastdetect /usepmtimer&quot;</i></p>
</blockquote>
<p><b>Q: I want to see feature &quot;X&quot; in future versions of RMClock. Would you add it for me?</b></p>
<p><b>A:</b> Feature requests are welcome, however, in order for a feature to be possibly incorporated in future versions of RMClock, it must meet the following criteria:</p>
<ul>
<li>It is a feature that is of possible interest and benefit for a wide variety of the users and not for your specific purpose.
<li>It is a feature directly related to the CPU performance/power states management. RMClock utility is designed for this particular purpose; no features unrelated to this task are to be ever incorporated.
<li>It is a feature depending only on the CPU model and not on the other parts of the hardware/firmware (chipset, BIOS, or motherboard components). RMClock is a small and generic utility, i.e., it is designed to work on all supported CPU models with no awareness of any other specific hardware present or installed (with some exception to Intel Centrino mobile platform). Specific hardware-dependent features that are never planned to be incorporated in RMClock include, but not limited to:
<ul>
<li>CPU temperature, voltage, fan speed monitoring and/or control;
<li>CPU temperature-dependent performance state and/or fan speed switching;
<li>Tweaking with the chipset bits (e.g., Halt disconnect, Stop Grant disconnect and FID/VID change enable bits);
<li>Implementation of older, chipset-based forms of Intel SpeedStep technology, chipset-based CPU throttling, etc.
</ul>
</ul>
<h2><a name="revhist"></a>Revision History</h2>
<h3>RMClock Version 2.05</h3>
<ul>
<li>Added full support for Intel Core Duo and Core Solo (Yonah core) processors.
<li>Added support for new Centrino/Centrino Duo (Napa) platform with ICH7-M Southbridge.
<li>Implemented independent monitoring of every physical/logical CPU present in the system.
<li>Returned &quot;animated icon&quot; feature much requested by users.
<li>Added display options for the CPU Frequency and CPU Load tray indicators.
<li>Added option to turn off per-profile handling of Windows power management settings.
<li>Fixed AMD Athlon 64 X2 and Dual Core Opteron management.
<li>Fixed minor CPU Frequency indicator &quot;1000 MHz&quot; bug.
<li>Minor UI design changes.
</ul>
<h3>RMClock Version 2.0</h3>
<ul>
<li>Completely new user interface design, new icons.
<li>CPU frequency and CPU/OS load system tray indicators.
<li>Integration with Windows power management and standard LCD backlight interface.
<li>Flexible per-profile and per-power source PST, ODCM and Windows power management settings.
<li>Improved ODCM management with user-customizable throttle states table feature.
<li>New CPU performance level management logic allowing instant multiple-states PST/ODCM transitions.
<li>Determination and support for new CPUs: Intel Pentium D and Pentium Extreme Edition 900 series, Intel Core Solo and Core Duo processors (preliminary); new Intel logos.
<li>Support for &quot;non-mobile&quot; versions of ICH4 and ICH6 south bridges in Intel Centrino mobile platform advanced settings.
<li>New command-line profile-changing options (-nextprofile and -prevprofile).
<li>Fixed CPU frequency display on older Intel Pentium 4 models (Northwood/Willamette).
<li>EIST/DBS settings (Intel Pentium 4 / Pentium M advanced settings) are now always remembered, regardless of the &quot;Remember these settings&quot; option.
<li>Added user-definable delay (as a registry setting) to the management procedure start (on startup and resume from standby/hibernate).
</ul>
<h3>RMClock Version 1.8</h3>
<ul>
<li>Rewritten multi-processor (SMP/HT/multicore) monitoring and management code.
<li>Added on-suspend behavior selection; removed "Force Minimal State on Standby" option.
<li>Returned "Run HLT command when OS is idle" option as requested by users (Win32 only).
<li>Added determination of AMD Athlon 64 X2, Turion and Dual Core Opterons.
<li>Bugfixed AltVID settings on AMD K8 revision E cores.
<li>Corrected ODCM settings behavior on a Centrino platform.
<li>Bugfixed log file rotating feature.
<li>Fixed Intel Centrino mobile platform chipset settings.
<li>Corrected "Restore Defaults on Exit" behavior.
</ul>
<h3>RMClock Version 1.7</h3>
<ul>
<li>New RTCore driver, support for Windows XP/Server 2003 x64 edition.
<li>Fixed Centrino Platform/ICH6-M settings.
<li>Fixed Intel Pentium 4 illegal P-states being added to the table.
<li>Fixed Intel Pentium 4 invalid current VID indication.
<li>Proper Pentium 4 core frequency determination.
<li>New Pentium M P-states table (removed bogus 7x FID).
<li>Removed -dump command-line option, feature moved to GUI.
<li>Added new settings for AMD K8 cores revision E and higher.
<li>Added support for AMD K8 dual-core processors (latest AMD driver required).
<li>Added separate Performance/Power Preference for AC and Battery modes.
<li>Automatic process priority lowering when no management is enabled.
<li>Added driver uninstall command-line option.
<li>New P-States Table design.
<li>Fixed settings save on Windows session ending.
<li>Defaults to &quot;Use OS load-based management&quot; on Intel Centrino platforms.
<li>Fixed possible lock-up when entering Susped state.
</ul>
<h3>RMClock Version 1.6</h3>
<ul>
<li>New P-States Transitions management with user-definable P-States table feature.
<li>New unified PST/ODCM management scheme (when both PST and ODCM are used).
<li>Single set of profiles for PST, ODCM and PST+ODCM management schemes.
<li>Added optional OS load-based management (a workaround for Intel Centrino platform).
<li>Removed &quot;Run HLT command when OS is idle&quot; option.
<li>Fixed restoring of Advanced CPU settings upon resume from Standby/Hibernate modes.
<li>Added more configuration options for AMD K7 CPU family.
<li>Added power management-related chipset configuration options for Intel Centrino platform (i855/i915M series).
<li>Added FID/VID transition stabilization time setting for Intel Pentium 4 and Pentium M processors.
<li>Fixed Transmeta LongRun Table Interface info.
<li>Added independent AC and Battery settings for Transmeta processors.
<li>CPU Load and Throttled Clock are now reported as &quot;N/A&quot; when CPU does not support necessary features.
<li>Added logging period limiting and log file &quot;rotating&quot; (when max logging period elapses and at the program startup).
<li>Added command-line parameters support (CPU info dump, profile change and exit commands).
</ul>
<h3>RMClock Version 1.5</h3>
<ul>
<li>Returned Balloon tooltips setting.
<li>Removed &quot;Alternate CPU Load Determination&quot; setting from the UI.
<li>Added more configurational options for AMD K8.
<li>Added Transmeta LongRun Technology support.
<li>Added independent AC and Battery performance/power profiles.
<li>Added warning messages for settings that require application restart.
<li>Duplicated tray icon settings in the General tab.
</ul>
<h3>RMClock Version 1.4</h3>
<ul>
<li>Changed P-state transitions scheme for AMD K8 in accordance with official AMD recommendations.
<li>Added more advanced configuration options for AMD K7 and K8 CPUs.
<li>Added support for dynamic on-demand CPU clock modulation (ODCM) management.
<li>Added CPU thermal throttling alert.
<li>Added optional forcing of the Minimal power management profile when running on batteries.
<li>Added support for running an HLT command when the system is idle (a workaround for Intel 855 chipset series).
<li>Added CPU core and revision ID display.
<li>Added preliminary support for Transmeta CPUs.
<li>Added automatic startup feature.
<li>Grouped management-related settings into a new tab.
</ul>
<h3>RMClock Version 1.3</h3>
<ul>
<li>New (tabbed sheet) user interface design.
<li>Added CPU clock, load level and FID/VID monitoring graphs with text file logging feature.
<li>Added CPU load level determination on Intel Pentium II/III/M/4 family CPUs.
<li>Added throttled CPU clock determination for any forms of CPU clock throttling.
<li>Added support for multi-processor (SMP/HT) systems (for both monitoring and FID/VID management features).
<li>Added support for &quot;mobile&quot; and &quot;server&quot; (DBS) Enhanced Intel SpeedStep technology on Intel Pentium M and Xeon (Nocona) CPUs.
<li>Added CPU-specific power management related settings for AMD K7, AMD K8 and Intel Pentium M/Pentium 4/Xeon family CPUs.
<li>Added Minimal FID/VID determination and display (where available).
<li>Added CPU power management features presence and status display.
<li>Improved CPU/OS load measurement with load-averaging feature.
<li>Improved FID/VID control logic with CPU load level &quot;noise filtering&quot; (spike removal) feature.
<li>Changed default process priority to Realtime priority class.
<li>Bugfixed CPU usage determination after resume from Hibernate mode.
<li>Bugfixed program settings saving upon termination of Windows session (shutdown/logoff).
</ul>
<h3>RMClock Version 1.2</h3>
<ul>
<li>New UI and popup menu design, including animated icon feature.
<li>Support for mobile/low-power desktop AMD Athlon XP CPUs featuring AMD PowerNow! technology.
<li>Improved FID/VID control logic.
<li>Additional stabilization-related tweaks.
<li>Additional CPU-specific tweaks for AMD Athlon 64 and Athlon XP family CPUs.
<li>Bugfixed &quot;Restore Defaults on Exit&quot;.
</ul>
<h3>AMD64CLK Version 1.1</h3>
<ul>
<li>Realtime CPU usage determination using the CPU performance counters.
<li>FID/VID values locking (preventing from being changed).
<li>FID/VID automatic management (based on the CPU usage).
<li>Additional configuration options.
</ul>
<h3>AMD64CLK Version 1.0</h3>
<ul>
<li>Initial release. Supports instant FID/VID changes on AMD K8 processors.
</ul>
<h2><a name="feedback"></a>Feedback</h2>
<p>Please post your comments and questions regarding RightMark CPU Clock Utility that are not already answered in the FAQ section of this manual at the dedicated <a href="http://forum.rightmark.org/?id=6">CPU RightMark forum</a>. In urgent cases, please contact <a href="mailto:dmitri_b@ixbt.com">Dmitri Besedin</a>, main program developer.</p>
</body>
</html>