| |
CPU-Z is a freeware that gathers information on some of the main devices of your system. CPU
|
Install and Remove
CPU-Z does not need to be installed. Just unzip the files in a directory and run the .exe. In order to remove the program, just delete the files.
The program does not copy any file in any directory, neither writes in the registry.
Configuration file
CPU-Z uses a configuration file, cpuz.ini, that allows to set several parameters for the program. The cpuz.ini file must be in the same directory as cpuz.exe. It looks like this :
[CPU-Z]
TextFontName=Verdana
TextFontSize=13
TextFontColor=000060
LabelFontName=Verdana
LabelFontSize=13
PCI=ON
MaxPCIBus=256
DMI=ON
Sensor=ON
SMBus=ON
Display=ON
TextFontName |
Font used for the information boxes. |
TextFontSize |
Size of the font used for the information boxes. |
TextFontColor |
Color of the font used for the information boxes. Value is expressed in hexadecimal, and consists in a classic Red/Green/Blue color code : RRGGBB |
LabelFontName |
Font used for the label boxes. |
LabelFontSize |
Size of the font used for the label boxes. |
Sensor |
Set to OFF disables sensor chip detection and voltages measurement. |
DMI |
Set to OFF disables the DMI (Desktop Management Interface) information. This concerns BIOS vendor and version, motherboard vendor and revision. |
PCI |
Set to OFF disables the PCI information. This disables chipset, SPD and, depending on the hardware, sensoring information. |
MaxPCIBus |
Sets the maximum PCI bus to scan. Default value is 256. |
SMBus |
Set to OFF disables SMBus information : SPD, and, depending on the hardware, sensoring information. |
Display |
Set to OFF disables the video card information reported in the validator. |
Note that the use of this file is optional. If no .ini file is found, default values will be used.
Parameters
-txt=report |
Launch CPU-Z in ghost mode : no interface appears, the register dump (report.txt) is automatically created. Example : cpuz.exe -txt=c:\mydirectory\mysystem : runs CPU-Z in ghost mode. Report file mysystem.txt is automatically generated in directory c:\mydirectory. |
-html=report |
Same as "-txt" but generates the html report file. |
-core=id |
Displays clock speed of core #id (id can be set from 0 to "Number of cores minus one"). It is then possible to check the speed of each core by running as many instances of CPU-Z as necessary, using batch files for example : cpuz0.bat : cpuz.exe -core=0 cpuz1.bat : cpuz.exe -core=1 Note that the current core can be dynamically selected by right-clicking in the CPU page, and select the target core. This feature is available from version 1.42. |
-console |
Generates output in a command prompt (Windows XP only). |
Special Keys
The F5 key allows to save a screenshot as a bmp file in the application directory. These are named cpu.bmp, cache.bmp, mainboard.bmp and memory.bmp.
The F6 key copies the current page in the clipboard.
The F7 key saves the validation cvf file in the current directory.
Cache Latency Computation
The cache latency computation tool allows to gather information about the cache hierarchy of the system. For each cache level, it provides its size and its latency. Please note that code caches are not reported.
The latency tool can be downloaded here.
Q: CPU-Z reports my CPU speed below its stock frequency.
A: This is the effect of the CPU power reduction mechanism : C1E (Enhanced Halt State) and/or EIST (Enhanced Intel SpeedStep Technology) for Intel CPUs, Cool'n'Quiet and or PowerNow! for AMD CPUs. Load your system and you will see the frequency increase to its nominal value.
Q: Why does CPU-Z needs a long time to start on my computer ?
A: CPU-Z may require several seconds to gather memory SPD information, and consequently the time increases with the number of modules. However, this operation is not done when refreshing or when reporting html or SPD information file.
In order to reduce time, you can set the SMBus parameter to OFF in the configuration file.
Q: Why does CPU-Z misreport my memory module specification ? For example, my DDR PC3500 is reported as PC3200.
A: The SDR and DDR theorical bandwidth is computed using the module access time information for the maximal CAS# latency value, included in the SPD area. If the computed bandwidth is lower than the one specified on the memory module, that means in most cases that the SPD information on the module is not correctly programmed, and does not mean that the memory module does not handle its specifications.
Q: Why does CPU-Z not report my memory SPD ? Does that mean that my memory module does not provide SPD information ?
A: Several reasons may cause CPU-Z not to report SPD information. The most common one is that CPU-Z was not able to get the SPD interface, because the chipset is unknown or unsupported by the program. That's why the same memory module can provide SPD information when installed in another motherboard, recognized by CPU-Z.
On a few memory modules, SPD information are not programmed at all. In this case, CPU-Z is not able to translate them, so nothing is reported.
Version | Date | News and corrections |
1.47 | 08/27/2008 |
|
1.46 | 06/27/2008 |
|
1.45 | 05/10/2008 |
|
- Processors
Intel® Pentium™, Pentium™ MMX, Pentium™ Pro, Pentium™ II, Pentium™ !!!, Pentium™ !!!-M, Pentium™ 4, Pentium™ 4-M, Pentium™ M, Pentium™ D, Pentium™ XE, Pentium™ Dual Core, Core™ Solo, Core™ Duo, Core™ 2 Duo, Core™ 2 Quad, Core™ 2 Extreme, Celeron™ (P2/P3/P4/PM/CL) and Xeon™ (P2/P3/P4/C2D/C2Q) ; Core™ i7 ; Itanium™, Itanium™ 2 ;
AMD® Am5x86, K5™, Geode LX, K6™, K6™-2, K6™-III, K6™-2+, K6™-III+, Athlon™ (4, XP, MP), Duron™, Sempron™ (K7/K8), Athlon™ 64, Athlon™ 64 X2, Turion™, Opteron™, Athlon™ FX, Phenom™ ;
VIA® C3™ (Samuel, Samuel2, Ezra, Ezra-T, Nehemiah), C7™, C7™-M, Nano (Isaiah) ;
Transmeta® Crusoë™ TM3200, TM5400, TM5500, TM5600, TM5800 ;
- Chipsets
Intel® i430TX, i440LX, i440FX, i440BX/ZX, i810/E, i815/E/EP/EM, i840, i845, i845E, i845G, i850/E, i845PE/GE, E7205, E7500, E7520, i852, i855, i865P/PE/G, i875P, i915P/G, i915PM/GM, i925X/XE, i945P/PL/G/GZ, i945PM/GM/GT, i955X/XE, P965, Q965, G965, GL960/GM965/PM965, i975X, 5000X/P/Z, 5400A/B, P35, G33, G31, Q35, Q33, X38, X48, P45, X58 ;
VIA® Apollo VP3, Apollo Pro, Apollo Pro +, Apollo Pro 266, KX133, KT133(A), KT266(A), KT400(A), KT600, P4X266(A), PT880, PT880 Pro, K8T800, K8T890, K8T900, P4M800CE, P4M890, P4M900, CX700/VX700 ;
NVIDIA® nForce, nForce2, nForce3, nForce4, nForce4 SLI Intel Edition, GeForce 6100/6150 (nForce 410/430), nForce 520/550/560/570/590, GeForce 7050/7100/7150, 650i, 680i, 750a/780a, 750i, 7770i, 780i, 790i, MCP79/7A ;
ATi® RS350, RS400, RS480/RX480, RS482, RD580/RX580, RS600/RD600, RS690, RS700, RD790 ;
SiS® 645, 645DX, 648, 648FX, 649, 655FX, 655TX, 656, 662, 735, 756, 761GX, 760, 760GX, 755, 755FX, 741, 741GX, 671/FX/DX/MX ;
AMD® AM-751, AM-761, AM-762 (760MP), 780G, 790GX ;
- Memory
SDR, DDR, DDR2, FB-DDR2, DDR3, RDRAM (Rambus®) ;
EPP and XMP extended profiles ;
'S.W > System' 카테고리의 다른 글
[가상드라이브] DAEMON Tools Lite v4.30.4 32/64 Bits (with SPTD 1.58) (1) | 2009.04.27 |
---|---|
[가상드라이브] DAEMON Tools Lite v4.30.1 32/64 Bits (with SPTD 1.56) (0) | 2008.09.04 |
[가상드라이브] DAEMON Tools Lite v4.12.4 32/64 Bits (with SPTD 1.56) (0) | 2008.07.11 |
[시스템] CLICK TO TWEAK ( 버전 : 3.40 ) (1) | 2008.05.21 |
[가상드라이브] DAEMON Tools Lite v4.12.3 32/64 Bits (with SPTD 1.56) (0) | 2008.05.14 |