home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Freesoft 1999 February
/
Freesoft_1999-02_cd.bin
/
Recenz
/
Utility
/
HWinfo
/
HWINFO.DOC
< prev
next >
Wrap
Text File
|
1999-03-01
|
47KB
|
1,020 lines
╔════════════════════════════════════════════════════════════════════════════╗
║ HWiNFO ∙ Copyright (c)1995-99 Martin Malík - REALiX(tm) ║
║ ────────────────────────────────────────────────────────────────────────── ║
║ Version 4.5.1; Last Update: Mar-03-1999 ║
╚════════════════════════════════════════════════════════════════════════════╝
┌──────────────────────────────────────────┐
│ USE THIS PROGRAM ONLY AT YOUR OWN RISK │
└──────────────────────────────────────────┘
CONTENTS
1. Intro
2. Updates and download
3. Requirements
4. Utilities distributed with HWiNFO
5. Registration
6. Creating a logfile
7. Limitations
8. Running HWiNFO under V86 Memory Managers and Windows
9. Resetting the CPU
10. HWiNFO Crash
11. Secondary Video Info
12. PCI chipsets comparison
13. IDE Disk Transfer Modes
14. Miscellaneous notes
15. Some abbreviations
16. Codenames
17. Thanks
18. Disclaimer
## 1. Intro ##################################################################
HWiNFO is a *POWERFUL* hardware detection program. It is simple, quick and
on most systems very efficient. It "tries" to give only important information
about all the hardware devices in your computer so that you need not look
inside the PC to see what's there.
## 2. Updates and download ###################################################
The newest version is always (immediately) available at:
My homepage - http://www.svf.stuba.sk/~malik/hwinfo.html
SAC ftp - ftp.elf.stuba.sk/pub/pc/utildiag
http://ftp.elf.stuba.sk/packages/pub/pc/utildiag
SAC BBS - +421 7 5438 232 (19,200 Baud)
+421 7 5438 295 (28,800 Baud)
At other sitez/BBS later...
SimTel - ftp.simtel.net/pub/simtelnet/msdos/sysinfo
SAC mirrors - ftp.uakom.sk/pub/mirrors/sac/utildiag
ftp.intec.sk/sac/utildiag
ftp.vse.cz/pub/msdos/SAC/pc/utildiag
ftp.cs.tu-berlin.de/pub/msdos/mirrors/stuba/pc/utildiag
ftp-beer.bke.hu/vol1/pub/sac/pc/utildiag
ftp.pwr.wroc.pl/pub/pc/sac/utildiag
cert.unisa.it/pub/PC/SAC/utildiag
ftp2.itb.it/pub/PC/SAC/utildiag
ftp.nsysu.edu.tw/PC/SAC/utildiag
192.217.228.45/SAC/pub/pc/utildiag
ftp.comp.hkbu.edu.hk/pub/sac/utildiag
ftp.cdrom.com/pub/sac/utildiag
## 3. Requirements ###########################################################
- 80386 or better CPU
- cca. 400 (+50) KBytes of free System Memory
- cca. 700 KBytes of free XMS Memory (XMS manager preferred)
## 4. Utilities distributed with HWiNFO ######################################
There are four utilities distributed along with HWiNFO:
GETBIOS.COM This utility retrieves all BIOS images and saves them to
files <BIOSseg>.ROM
This program doesn't run in V86 mode in order to avoid
BIOS relocation.
GETDDC.COM This utility saves VESA Display Data Channel data to file
DDC.DAT if your video card and monitor support DDC
GETPCI.EXE This utility stores all data from PCI configuration space
registers into files <VendorID><DeviceID>.PCI
GETPNPRS.EXE This utility saves resource data for all Plug-and-Play
capable devices into files PNP<CSN>.RES
GETPIROM.EXE This utility gets the content of Processor Information ROM
(P.I.ROM) and stores into file PIROM.DAT. This feature is
available only on Intel Pentium(R) II Xeon(TM) Processors.
These utilities are free and are designed to help me improve HWiNFO if
you send me the results.
## 5. Registration ###########################################################
HWiNFO is shareware, meaning that you can test the program for free whilst
checking if it is useful for you. The public (unregistered) version has all
the features as the registered version except the "Create report file"
feature. The other disadvantage is the message that HWiNFO isn't registered
and that you have to press a random key while the results are shown.
If you think you could use this program and don't want to see that stupid
message, or if you continue using it after a trial period of 14 days, you
should register. Otherwise after this period HWiNFO becomes an illegal copy
and you have to delete it (ho-ho-ho :-)).
If you decide to register, you should print out the file REGISTER.FRM,
fill it and send to the address in the file.
If you include your Internet e-mail address, you will receive the
key file via e-mail, otherwise snail mail.
Once you have obtained the key file needed to register, copy it to the
HWiNFO directory and the current version will become registered. Of course,
you mat not distribute the key file, it's only for your personal use.
Well, the Registration fee is:
╔══════════════════╦══════════════════╗
║ Non-Commercial ║ Commercial ║
╠═════╤═════╤══════╬═════╤═════╤══════╣
║ DEM │ US$ │ Sk/KC║ DEM │ US$ │ Sk/KC║
╔═══════════════╬═════╪═════╪══════╬═════╪═════╪══════╣
║ 1 User ║ 35 │ 20 │ 500 ║ 70 │ 40 │ 1000 ║
╟───────────────╫─────┼─────┼──────╫─────┼─────┼──────╢
║ 2-10 Users ║* 30 │* 16 │* 450 ║ 60 │ 32 │ 900 ║ per copy
╟───────────────╫─────┼─────┼──────╫─────┼─────┼──────╢
║ 11-20 Users ║* 25 │* 13 │* 400 ║ 50 │ 26 │ 800 ║ per copy
╟───────────────╫─────┼─────┼──────╫─────┼─────┼──────╢
║ 21-50 Users ║* 20 │* 10 │* 300 ║ 40 │ 20 │ 600 ║ per copy
╟───────────────╫─────┼─────┼──────╫─────┼─────┼──────╢
║ 51-100 Users ║* 15 │* 7 │* 200 ║ 30 │ 14 │ 400 ║ per copy
╟───────────────╫─────┴─────┴──────╫─────┴─────┴──────╢
║ UNLIMITED ║Contact the author║Contact the author║
╚═══════════════╩══════════════════╩══════════════════╝
* for schools, educations, etc.
When registering with Eurocheque or bank transfer please add 10% to
the total price to cover bank transfer costs.
For any special requirements contact the author.
A registration is valid for all future versions.
And there will be a lot of newer versions of course.
You should register NOW !
## 6. Creating a logfile #####################################################
There are three possible methods how to create a logfile:
1. Simple log
After pressing the <F2> key, HWiNFO adds the results from current screen
to a logfile.
2. Report file ("-r" switch) [REGISTERED VERSION ONLY]
HWiNFO creates AUTOMATICALLY a COMPLETE logfile at startup.
This logfile has the same format as the one created with <F2> key, but
there's no need to navigate HWiNFO through all the screens.
3. Short report file ("-s" switch) [REGISTERED VERSION ONLY]
HWiNFO creates AUTOMATICALLY a logfile, which contains only the
MOST IMPORTANT items. This format is suitable for further automatical
processing (or printing) of logfiles (e.g. if you would like to create
an inventory of more machines). Here's a sample of the format:
CPU=Intel Pentium II Xeon, 400.0 MHz
Bus=ISA + PCI + A.G.P.
Chipset=Intel 82440GX AGPset
Memory=128 MBytes
...
VideoChipset=3DLabs Permedia 2
VideoMemory=8192 KBytes
3Daccel=3Dfx Voodoo 2
...
The default log filename is "HWiNFO.LOG". You can change its name if you
enter it as a paramater to HWiNFO (e.g. "HWiNFO.EXE -r HOME.LOG").
## 7. Limitations ############################################################
The Mainboard Chipset identification works only on newer (≈ 1991 and above)
AMI and newer AWARD BIOSes. HWiNFO is also able to detect some chipsets, not
depending on the type of BIOS (see HWiNFO.LST).
Fixed Disk Buffered Data Transfer rate reads data from one physical sector
until 4 seconds. Some caches (like Hyperdisk; but NCACHE or SMARTDRV don't)
could cause invalid results. Also some mainboards, which have incompatible
timers could cause problems.
Fixed Disk Average Seek receives results while seeking permanently 100* from
cylinder 0 to a cylinder, which is 1/3 of the max. cylinder number. Thus some
programs could report another result if they seek to an another cylinder.
SCSI disks and some Cache programs (Hyperdisk) don't generate Seek requests,
thus the Seek and RPM result is abnormal and HWiNFO displays <N/A>.
PCMCIA detection requires Socket Services or Card Services to be installed.
If you want more info about sockets, install Card Services.
The VESA Local Bus can be detected only if a VLB card is present.
CD-ROM benchmark requires MSCDEX.EXE (Microsoft CD-ROM Extensions) to
be installed and an inserted data CD.
## 8. Running HWiNFO under V86 Memory Managers and Windows ###################
In order to achieve best results, HWiNFO accesses directly the hardware.
Some of the routines (privileged) require to be run in Real mode or at
privilege level 0 (PL0, most privileged), but in V86 mode are all
applications run at PL3. This means, if such a routine is run, the CPU
raises an exception, which is handled by the V86 manager. Note, that
V86 mode is the only way to run a DOS application (Real mode) under
MS Windows (Protected mode). EMM (Expanded Memory Manager) also use the
V86 mode to provide paging.
But HWiNFO v3.00+ is able to run the privileged routines in V86 mode under
some circumstances. There is a special call (called WINDOWS INIT BROADCAST),
which can be used to force an V86 manager to switch to Real mode (of course,
the V86 manager must support it). This call was originally used by
MS Windows while starting, while an Expanded Memory Manager was running
(this is needed, because EMM is running in Protected mode and Windows too).
Such known EMM managers are:
- Microsoft EMM386 Expanded Memory Manager
- Quarterdeck QEMM386 Expanded Memory Manager
- Qualitas 386MAX Expanded Memory Manager
- Nu-Mega Soft-ICE Debugger
...
So HWiNFO uses this call to force the manager to switch back to Real mode.
HWiNFO works best under EMM386 (I haven't found any problems).
But there are some disadvantages while runnig in V86 mode:
- The FPU benchmark returns another results (it's slower) as in real mode.
- Some V86 managers are able to relocate BIOSes, so HWiNFO won't be able
to identify BIOS type and some video cards.
- A crash while detecting the CPU type could happen on some older
CPUs requiring CPU RESET to identify them properly.
The other case is, if a manager doesn't support the call. This happens if
you are running under Microsoft Windows95 OSR2 or Windows98 DOS mode.
If these managers receive the Windows INIT BCAST, they display a message
about running an incompatible application and stop. So the only way is
to skip the privileged routines.
Pre v4.4.1 of HWiNFO refused to run under this circumstances, but
later versions run with the following restrictions (skip privileged routs):
- CPU frequency can't be measured using TSC
- CPU RESET can't be performed (this is needed only for older CPUs)
- TI486 Potomac CPUs can't be identified
- L2 cache ECC presence can't be detected (P-II, Xeon)
- CPU Update Revision can't be reported (PPro and above)
- Cache state, branch prediction and instruction execution can't be reported
If you try to run HWiNFO directly from Microsoft Windows (DOS box), it will
refuse to continue. This is because Windows controls also access to some
ports and doesn't allow a direct access from a DOS application. This
means, that if HWiNFO wouldn't refuse to run, but continue, it would be
unable to return info about IDE/ATAPI drives, COM/LPT ports, BIOS scan,
PnP resources, Benchmarks wouldn't be accurate...
Windows NT VDM (Virtual DOS Machine) is even more strict.
## 9. Resetting the CPU ######################################################
The CPU ID is available only on 386+ CPUs and HWiNFO uses three ways to
obtain this ID:
Method 1 - Resets the CPU while A20 is Enabled.
This method works on all systems, but the Reset handler gets
control after BIOS. And some BIOSes (some newer AMI/Award BIOSes)
destroy CPU ID (EDX) and therefore this ID could be invalid.
This method is default <Enabled> in Setup section.
Method 2 - Resets the CPU while A20 is Disabled.
This method works only on some machines, which do have a
Fully-Terminated bus. It's the best way to obtain CPU ID, because
it gets control immediately after Reset (the BIOS can't destroy
EDX). I've found some problems with this method while running
with Norton cache.
This method is default <Disabled> in Setup section.
Method 3 - Try to use this method if your BIOS destroys CPU ID. But it works
only on systems, which do not have Main BIOS (area at 0F000:0)
Write-Protected, because it modifies it for a bit, and then
restores back. This method is on some machines the only way
to obtain CPU ID.
This method is default <Enabled> in Setup section.
HWiNFO tries to determine CPU ID this way, via: 1. CPUID instruction
2. BIOS (INT 15h)
3. Method 2 (if Enabled)
4. Method 3
5. Method 1
If you have an UMC U5SX/SD/SLV/486DX2/SX2, Enhanced Am486DX2/DX4/DX4-WB,
AMD-K5 and above, Intel 486DX/SX/DX2 SL-Enhanced, IntelDX4, IntelSX2,
IntelDX2 W-B Enh. or Intel Pentium(R) and above, there is no need to Reset
the CPU (these CPU support CPUID instruction). Most CPUs today support
CPUID instruction.
Note: NexGen Nx586 does NOT support the CPUID instruction.
Cyrix 5x86 and above support the CPUID instruction only if CPUIDEN bit
in CCR4 register is set. HWiNFO 3.0.7+ sets this bit automatically.
Disabling "CPU ID detection via Method 1, 2 and 3" reduces your CPU
detection ability. And if there's no other way to obtain this ID
(via BIOS or CPUID instruction), it won't identify 386SL, i386CX/EX,
486DX2, IBM 486... and some other CPUs. Do this only if your system
hangs while attempting CPU detection.
Some BIOSes simply OVERWRITE the CPU ID (EDX) :-< ! In this case an
invalid CPU ID is displayed and the CPU is probably incorrectly identified.
If this problem occurs, try to use Method 3 (but your Main BIOS must be
Write-Enabled !). If it doesn't work, try to use Method 2 (but you must
have a Fully-Terminated bus !). And if HWiNFO still displays, that Method 1
was used to obtain CPU ID, not Method 2 nor 3 can obtain it.
## 10. HWiNFO Crash ##########################################################
- S3 ViRGE cards seem to crash while performing the TV Tuner test.
If so, disable the "Check TV Tuner" option in Setup.
- Stacker Compression Card and 3Com EtherLink III Adapter detection
routines can cause crashes with some Network cards. You can disable
them in the Configuration section (Stacker check is default disabled;
3Com EtherLink III detection is enabled).
- If HWiNFO crashes while starting or while the "Flushing Disk Caches..."
message is displayed, disable the "FlushDiskCache" option in HWiNFO.INI
or HWiNFO|Setup.
- The test for a TIGA graphics adapter may cause problems with some
adapters.
## 11. Secondary Video Info ##################################################
RISC Graphics Processor: currently identifies only Hitachi HD63484 ACRTC
Scanning for TMS: checks for TMS340x0 processor on several ports and tries
to get vendor and device name (detection routine from
SPEA GDC drivers, I don't know if it works with other TMS
cards too)
TMS Boot EEPROM: gets info from Boot Software; this won't probably work
with other cards than SPEA (I don't know :-( )
TIGA driver: gets info from TIGA driver if it's loaded (TIGACD.EXE)
Also found as: identifies all SPEA Graphiti series cards from GDCINI.DAT
and checks for HP IGC-20 and NEC MultiSync Graphics Engine
You can obtain info such as:
e.g.: RISC Graphics Processor: Hitachi HD63484 (ACRTC)
Scanning for TMS: N/A
TMS Boot EEPROM: N/A
TIGA driver: N/A
Also found as: SPEA Graphiti Flash 1G2-HE
or: RISC Graphics Processor: N/A
Scanning for TMS: (C) SPEA Software AG HILITE1024
TMS Boot EEPROM: SPEA HiLite1024
TIGA driver: N/A
Also found as: SPEA Graphiti HiLite1024
or: RISC Graphics Processor: N/A
Scanning for TMS: <I really don't know what it'll display>
TMS Boot EEPROM: -||-
TIGA driver: HP A1083A Intelligent Graphics Controller 20
Also found as: Hewlett Packard IGC-20 A1083A
## 12. PCI chipsets comparison ###############################################
┌────────────────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┐
│ Chipset │ Intel │ Intel │ Intel │ Intel │ Intel │ Intel │ Intel │
│ │ 430LX │ 430NX │ 430FX │ 430VX │ 430HX │ 430MX │ 430TX │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ North Bridge │82434LX│82434NX│82437FX│82437VX│82439HX│82437MX│82379TX│
│ │ PCMC │ PCMC │ TSC │ TVX │ TXC │ MTSC │ MTXC │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ P5 │ P5, │ P54C │ P54C │ P54C │ P54LM │ P54C, │
│ CPUs │ │ P54C │ K5, │ K5, │ K5, │mobile │ P55C, │
│ │ │ │ M1 │ M1 │ M1 │ │ K5,K6 │
│ │ │ │ │ │ │ │ M1,M2 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. bus freq. │ 66 │ 66 │ 66 │ 66 │ 66 │ 66 │ 66 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ SMP (max CPUs) │ - │ - │ - │ - │ 2 │ - │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. memory │ 192M │ 512M │ 128M │ 128M │ 512M │ 128M │ 256M │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ SPM │ SPM │ SPM, │ FPM, │ FPM, │ SPM, │ FPM, │
│ Memory │ │ │ EDO │ EDO, │ EDO │ EDO │ EDO, │
│ Types │ │ │ │ SDRAM │ │ │ SDRAM │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ ECC/Parity │ - │ - │ - │ - │ X │ - │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Cacheability │ 192M │ 512M │ 64M │ 64M │ 512M │ 64M │ 64M │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ South Bridge │82378IB│82378IB│82371FB│82371SB│82371SB│82371MX│82371AB│
│ │ SIO │ SIO │ PIIX │ PIIX3 │ PIIX3 │ MPIIX │ PIIX4 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ PCI support │ 2.0 │ 2.0 │ 2.0 │ 2.1 │ 2.1 │ 2.0 │ 2.1 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ A.G.P. │ - │ - │ - │ - │ - │ - │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Concurrent PCI │ - │ - │ - │ X │ X │ - │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ USB │ - │ - │ - │ X │ X │ - │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Power Mgmt. │ - │ - │ - │ - │ - │SMI/APM│ ACPI │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Ultra-DMA mode │ - │ - │ - │ - │ - │ - │ 2 │
└────────────────┴───────┴───────┴───────┴───────┴───────┴───────┴───────┘
┌────────────────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┐
│ Chipset │ Intel │ Intel │ Intel │ Intel │ Intel │ Intel │ Intel │ Intel │ Intel │
│ │ 440FX │ 450GX │ 450KX │ 440LX │ 440EX │ 440BX │ 440ZX │ 440GX │ 450NX │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ North Bridge │82441FX│82453GX│82453KX│82443LX│82443EX│82443BX│82443ZX│82443GX│82451NX│
│ │ PMC │82454GX│82454KX│ PAC │ PAC │ │ │ │82454NX│
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ P6, │ P6 │ P6 │ P-II │ P-II, │ P-II │ P-II, │ P-II, │ Xeon │
│ CPUs │ P-II │ │ │ │Celeron│ │Celeron│ Xeon │ │
│ │ │ │ │ │ │ │optimi-│ │ │
│ │ │ │ │ │ │ │ zed │ │ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. bus freq. │ 66 │ 66 │ 66 │ 66 │ 66 │ 100 │ 100 │ 100 │ 100 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ SMP (max CPUs) │ 2 │ 4 │ 2 │ 2 │ - │ 2 │ - │ 2 │ 4 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. memory │ 1G │ 8G │ 1G │1G(EDO)│ 256M │ 1G │ 256M │ 2G │ 8G │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │FPM,EDO│ FPM │ FPM │ EDO, │ EDO, │ EDO, │ SDRAM │ SDRAM │ EDO │
│ Memory │ BEDO │ │ │ SDRAM │ SDRAM │ SDRAM │ │ │ │
│ Types │ │ │ │ │ │ ** │ │ │ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ ECC/Parity │ X │ X │ X │ X │ - │ X │ - │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Cacheability │ *** │ *** │ *** │ *** │ *** │ *** │ *** │ *** │ *** │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ South Bridge │82371SB│optio- │optio- │82371AB│82371AB│82371EB│82371EB│82371EB│82371EB│
│ │ PIIX3 │ nal │ nal │ PIIX4 │ PIIX4 │PIIX4E │PIIX4E │PIIX4E │PIIX4E │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ PCI support │ 2.1 │ 2.0 │ 2.0 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ A.G.P. │ - │ - │ - │ 2x │ 2x │ 2x │ 2x │ 2x │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Concurrent PCI │ X │ **** │ **** │ X │ X │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ USB │ X │ **** │ **** │ X │ X │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Power Mgmt. │ SMM │ SMM │ SMM │ ACPI │ ACPI │ ACPI │ ACPI │ ACPI │ ACPI │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Ultra-DMA mode │ - │ - │ - │ 2 │ 2 │ 2 │ 2 │ 2 │ 2 │
└────────────────┴───────┴───────┴───────┴───────┴───────┴───────┴───────┴───────┴───────┘
┌────────────────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┐
│ │ VIA │ VIA │ VIA │ VIA │ VIA │ VIA │ VIA │
│ Chipset │Apollo │Apollo │Apollo │Apollo │Apollo │Apollo │Apollo │
│ │ VP1 │ VPX │ VP2 │ VP3 │ MVP3 │ Pro │ProPlus│
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ North Bridge │82C585 │82C585 │82C595 │82C597 │82C598 │82C691 │82C693 │
│ │ VP │ VPX │ │ /AT │ /AT │ │ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ P54C, │ P54C, │ P54C, │ P54C, │ P54C, │ P6, │ P-II, │
│ CPUs │ K5, │ P55C, │ P55C, │ P55C, │ P55C, │ P-II │Celeron│
│ │ M1 │ K5,K6 │ K5,K6 │ K5,K6 │ K5,K6 │ │ │
│ │ │ M1,M2 │ M1,M2 │ M1,M2 │ M1,M2 │ │ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. bus freq. │ 66 │ 75 │ 66 │ 100 │ 100 │ 100 │ 100 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ SMP (max CPUs) │ - │ - │ - │ - │ - │ - │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. memory │ 512M │ 512M │ 768M │ 1G │ 1G │ 1G │ 1G │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ FPM, │ FPM, │ FPM, │FPM,EDO│FPM,EDO│FPM,EDO│FPM,EDO│
│ Memory │ EDO, │ EDO, │ EDO, │SDRAM, │SDRAM, │SDRAM, │SDRAM, │
│ Types │ SDRAM │ SDRAM │ SDRAM │SDRAM2 │SDRAM2 │SDRAM2 │ VCM │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ ECC/Parity │ - │ - │ X │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Cacheability │ 512M* │ 512M* │ 512M* │ 512M *│ 512M *│ *** │ *** │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ South Bridge │82C586 │82C586B│82C586B│82C586B│82C586B│82C596A│82C596A│
│ │ │ │ │ │ │ │ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ PCI support │ 2.1 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ A.G.P. │ - │ - │ - │ 2x │ 2x │ 2x │ 2x │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Concurrent PCI │ X │ X │ X │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ USB │ X │ X │ X │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Power Mgmt. │ APM │ ACPI │ ACPI │ ACPI │ ACPI │ ACPI │ ACPI │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Ultra-DMA mode │ - │ 2 │ 2 │ 2 │ 2 │ 4 │ 4 │
└────────────────┴───────┴───────┴───────┴───────┴───────┴───────┴───────┘
┌────────────────┬───────┬───────┬───────┬───────┬───────┬───────┐
│ Chipset │ SiS │ SiS │ SiS │ SiS │ SiS │ SiS │
│ │ 5511 │ 5596 │ 5571 │ 5581 │ 5597 │ 5591 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ North Bridge │ 5511 │ 5596 │ 5571 │ 5581 │ 5597 │ 5591 │
│ │ PCMC │ │ │ │ │ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ P54C, │ P54C, │ P54C, │ P54C, │ P54C, │ P54C, │
│ CPUs │ K5, │ K5, │ P55C, │ P55C, │ P55C, │ P55C, │
│ │ M1 │ M1 │ K5,K6,│ K5,K6,│ K5,K6,│ K5,K6,│
│ │ │ │ M1,M2 │ M1,M2 │ M1,M2 │ M1,M2 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. bus freq. │ 66 │ 66 │ 75 │ 75 │ 75 │ 66 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ SMP (max CPUs) │ - │ - │ - │ - │ - │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Max. memory │ 512M │ 512M │ 384M │ 384M │ 384M │ 768M │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Supported │ FPM, │ FPM, │ FPM, │ FPM, │ FPM, │ FPM, │
│ Memory │ EDO │ EDO │ EDO, │ EDO, │ EDO, │ EDO, │
│ Types │ │ │ SDRAM │ SDRAM │ SDRAM │ SDRAM │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ ECC/Parity │ - │ - │ - │ - │ - │ - │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Cacheability │ 256M *│ 256M *│ 128M *│ 128M *│ 128M *│ 256M *│
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ South Bridge │ 5513 │ 5513 │ 5513 │ 5513 │ 5513 │ 5595 │
│ │ │ │integr.│integr.│integr.│ │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ PCI support │ 2.0 │ 2.0 │ 2.1 │ 2.1 │ 2.1 │ 2.1 │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ A.G.P. │ - │ - │ - │ - │ - │ 2x │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Concurrent PCI │ X │ X │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ USB │ - │ - │ X │ X │ X │ X │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Power Mgmt. │ SMM │ SMM │ SMM │ ACPI │ ACPI │ ACPI │
├────────────────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ Ultra-DMA mode │ - │ - │ - │ 2 │ 2 │ 2 │
└────────────────┴───────┴───────┴───────┴───────┴───────┴───────┘
* - Depends on L2 cache size:
┌───────┬───────────────┐
│ cache │ cacheable │
│ size │ region │
├───────┼───────────────┤
│ 256K │64M-cache_size │
│ 512K │128M-cache_size│
│ 1M │256M-cache_size│
│ 2M │512M-cache_size│
└───────┴───────────────┘
** - EDO and SDRAM cannot be mixed
*** - no L2 cache on-board (depends on on-chip L2 cache size in CPU)
**** - available if 82371SB PIIX3 is used
## 13. IDE Disk Transfer Modes ###############################################
HWiNFO reports transfer modes for all IDE/ATAPI drives, which support it.
Max. PIO transfer mode: PIO x
DMA Transfer Modes: SW: a1 (m1), MW: a2 (m2), Ultra: a3 (m3)
Where:
x = Maximum supported PIO transfer mode
SW = Singleword DMA transfer mode
MW = Multiword DMA transfer mode
Ultra = Ultra-DMA transfer mode
a1, a2, a3 = Current active mode
m1, m2, m3 = Max. supported mode
┌─────────────┬───────────────┐
│ Transfer │ Maximum │
│ Mode │ Transfer rate │
├─────────────┼───────────────┤
│ PIO 0 │ 3.33 MB/s │
│ PIO 1 │ 5.22 MB/s │
│ PIO 2 │ 8.33 MB/s │
│ PIO 3 │ 11.11 MB/s │
│ PIO 4 │ 16.66 MB/s │
├─────────────┼───────────────┤
│ DMA 0 │ 4.16 MB/s │
│ DMA 1 │ 13.33 MB/s │
│ DMA 2 │ 16.66 MB/s │
├─────────────┼───────────────┤
│ Ultra-DMA 0 │ 16.66 MB/s │
│ Ultra-DMA 1 │ 25.00 MB/s │
│ Ultra-DMA 2 │ 33.33 MB/s │ Ultra-DMA/33
│ Ultra-DMA 3 │ 44.44 MB/s │ Ultra-DMA/44
│ Ultra-DMA 4 │ 66.66 MB/s │ Ultra-DMA/66
└─────────────┴───────────────┘
## 14. Miscellaneous notes ###################################################
On some old motherboards, random numbers are obtained from unused I/O ports
and this may cause invalid identification of some hardware (e.g. WSS).
I don't know how to solve this problem.
Video Throughput benchmark depends only on External CPU frequency and the
type of Video board used; e.g. 486DX-33 with the same graphics board as an
i486DX4-100 (running at 3*33 MHz) report the same Video Throughput speed !
Intel Pentium(R) and above CPUs do not report, that the "APIC on-chip"
feature is present. Most of them (P54C yes, but P54CQS and P54LM don't)
have an on-chip APIC, but don't report it, if it isn't supported by
external hardware.
Dhrystone benchmark tests the performance of CPU and Memory, but only in
16-bit code. Therefore a 150 MHz Pentium Pro (which is designed and tuned
especially for 32-bit code) returns a rather low Dhrystone result.
So its performance while running with 16-bit applications is comparable
to a 100 MHz Pentium P54C.
If you have an Intel 420LX/420NX/430FX/430HX/430VX/430MX/430TX,
SiS 85C501/5120/5511/5571/5581/5596/5597/5591, AMD-640 chipset or
VIA Apollo VP-1/VPX/VP-2/VP3/MVP3, HWiNFO is able to detect the type of
External Cache and its size direct from the PCI chipset registers.
The report of CPU temperature sensor requires:
- Temperature sensor connected to CPU:
- National Semiconductor LM75 sensor or
- Mobile Intel Pentium(R) II Processor or
- Intel Pentium(R) II Mobile Module or
- Intel Pentium(R) II Xeon(TM) Processor
- Intel 82371AB PIIX4 (or 82371EB PIIX4E) south bridge
- SMBus
The report of MB temperature, voltages and FAN speed requires:
- National Semiconductor LM78 or compatible sensors
Compatible are: - National Semiconductor LM79
- National Semiconductor LM80
- National Semiconductor LM81
- Winbond W83781D
- Dallas Semiconductor DS1780 (maybe SMBus interface only)
- Analog Devices ADM1024 (maybe SMBus interface only)
- These chips must be present at standard ISA I/O locations 280h or 290h
## 15. Some abbreviations ####################################################
FPM = Fast-Page Mode (old standard DRAM type)
EDO = Extended Data-Out
SDRAM = Synchronous DRAM
DDR SDRAM II = Double Data Rate SDRAM II
BDDR SDRAM II = Bi-directionally strobed DDR SDRAM II
BEDO = Burst EDO
EC = Error Check only
ECC = Error Check and Correction
DRAM = Dynamic RAM
VRAM = Video RAM
WRAM = Window RAM
SDRAM = Synchronous DRAM
SGRAM = Synchronous Graphics RAM
RDRAM = Rambus DRAM
MDRAM = Multibank DRAM
VRT = Voltage Reduction Technology
APIC = Advanced Programmable Interrupt Controller (required for DP)
DP = Dual Processing
FRC = Functional Redundancy Checking (requires DP)
MMX = Multimedia Extensions
(57 new instructions, SIMD architecture, 64-bit regs)
MMX-2 = 3D Multimedia Instructions (Intel)
3DNow! = Additional floating point MMX instructions (AMD, Cyrix)
KNI = Katmai New Instructions
(70 SIMD floating-point instructions, that can be run
in a special CPU mode)
ISSE = Internet Streaming SIMD Extensions
(official name of KNI)
S.E.C = Single Edge Contact
MPS = Multi-Processor System
P.I.ROM = Processor Information ROM
TLB = Translation Lookaside Buffer
(small cache for page translation)
PnP = Plug-and-Play
ESCD = Extended System Configuration Data
DMI = Desktop Management Interface
ACPI = Advanced Configuration and Power Interface
APM = Advanced Power Management
VESA/VBE = Video Electronics Standards Association /
Video BIOS Extensions
DDC = Display Data Channel
(DDC1: Monitor->PC, DDC2B: Monitor<->PC)
## 16. Codenames #############################################################
Codenames for Intel Processors:
P5 - Intel Pentium(R) Processor:
Old 50/50 (Engineering Sample), 60/60 and 66/66 MHz.
P54C - Intel Pentium(R) Processor:
Later 75/50, 90/60, 100/50, 100/66, 120/60, 133/66, 150/60,
166/66, 180/60, 200/66 and 233/66 MHz without VRT, with
on-chip APIC, Dual Processing Features and FRC support.
P54CM - Intel Pentium(R) Update Processor:
Old 90MHz Slave processor in Dual Processor system.
P54CQS - Intel Pentium(R) Processor:
75/50, 100/66, 120/60, 133/66, 166/66 and 200/66 MHz
without VRT, on-chip APIC, Dual Processing Features, Upgrade
and FRC support.
P54LM - Intel Pentium(R) Mobile Processor:
75/50, 120/60, 133/66 and 150/60 Low Power versions (2.9 V)
supporting VRT. These Processors are shipped without APIC
on-chip, Dual Processing Features, Upgrade and FRC support.
P24T - Intel Pentium(R) OverDrive(R) Processor:
PODP5V63 63/25 MHz and PODP5V83 83/33 MHz OverDrive
for 486 CPUs.
P24CT - Intel Pentium(R) OverDrive(R) Processor:
OverDrive for IntelDX4(TM) Processor.
P5T - Intel Pentium(R) OverDrive(R) Processor:
PODP5V120 120/60 MHz and PODP5V133 133/66 MHz OverDrive for
Intel Pentium(R) P5 60/60 and 66/66 MHz Processors.
P54CT - Intel Pentium(R) OverDrive(R) Processor:
PODP3V125 125/50 MHz, PODP3V150 150/60 MHz and
PODP3V166 166/66 MHz OverDrive for Intel Pentium(R) P54C
75/50, 90/60 and 100/66 MHz Processors.
P55C - Intel Pentium(R) Processor with MMX(TM) Technology:
166/66, 200/66, 233/66 and 266/66 MHz
MMX, 32 KBytes First Level Cache and better Branch Prediction.
P55LM
Tillamook - Intel Mobile Pentium(R) Processor with MMX(TM) Technology:
200/66, 233/66, 266/66, 300/60 and 300/66 MHz,
VccCORE=1.6-2.1 V, VccIO=2.3-2.6 V
P55CTP - Intel Pentium(R) OverDrive(R) Processor with MMX(TM) Technology:
PODPMT60X150 125/50, 150/60, PODPMT66X166 166/66,
PODPMT60X180 180/60 and PODPMT66X200 200/66 for Intel Pentium(R)
75/50, 90/60 and 100/66 Processors.
P6 - Intel Pentium(R) Pro Processor:
133/66 (Engineering Sample), 150/60, 166/66, 180/60 and 200/66,
256K, 512K and 1024K of L2 cache.
P6T - Intel Pentium(R) Pro OverDrive(R) Processor.
P6L
Klamath - Intel Pentium(R) II Processor:
233/66, 266/66 and 300/66,
P6 with MMX(TM) Technology and without Level-2 on-chip cache,
S.E.C. cartridge, Slot 1, 512K half speed ECC/Non-ECC L2
cache on substrate, .35 µm, VccCORE=2.8V or 1.6V,
up to 2 CPUs in MPS
Deschutes - Intel Pentium(R) II Processor:
333/66, 350/100, 400/100 and 450/100 MHz,
512K ECC half speed L2 cache, MMX, .25 µm, VccCORE=2.0V
Mobile
Deschutes - Mobile Intel Pentium(R) II Processor:
233/66, 266/66 MHz and 300/66, VccCORE=1.7V or 1.6V,
ECC L2 cache
P6X - Intel Pentium(R) II Xeon(TM) Processor:
400/100 and 450/100 MHz, 512K, 1M or 2M o full speed L2 cache,
MMX, Slot 2, up to 8 CPUs in MPS, full ECC, FRC,
SMBus (thermal sensor, P.I. ROM, scratch EEPROM)
P6C
Covington - Intel Celeron(TM) Processor:
266/66 and 300/66 MHz, no L2 cache, MMX, no MPS, Slot 1
Mendocino - Intel Celeron(TM) Processor:
300A/66, 333/66, 366/66 and 400/66 MHz, 128K on-chip L2 cache,
Slot 1 or PPGA (Socket 370)
Dixon - Intel Mobile Pentium(R) II Processor:
266PE/66, 300PE/66, 333/66 and 366/66, 256K on-chip L2 cache,
VccCORE=1.6 V, Mini-cartridge, MMC-1 or MMC-2 for Mobile Module
or BGA package
Katmai - Intel Pentium(R) III Processor:
450/100, 500/100 and 550/100, ISSE, 512K half speed L2 cache,
Slot 1
Tanner - Intel Pentium(R) III Xeon(TM) Processor:
500/100 MHz, ISSE, Slot 2, 512K/1M/2M full speed CSRAM L2 cache
Coppermine - 533 MHz, .18 µm, Slot 1, 512K half speed L2 BSRAM cache,
133 MHz FSB
Cascades - 600 MHz, .18 µm, Slot 2, 256K full speed L2 cache,
133 MHz FSB
Willamette - .18 µm, 800 MHz
Merced - Intel + HP project
IA64 architecture, EPIC, PA-RISC compatible
Foster - For servers, 1 GHz
## 17. Thanks ################################################################
I want especially to thank:
∙ Beta testers: Boris Hurínek [BHsoft] (hurinek@axa.sk)
Erik Francisci (jumper!franci@dec3.dcs.elf.stuba.sk)
Igor Junas (junas@axis.sk)
Matús Rosa (rosa@???.sk)
Milan Marusinec (marusin@lithec.sk)
∙ Alex V. Potemkin and Potemkin's Hackers Group (avp@stelth.dvm.msk.ru)
∙ Aad Offerman (offerman@einstein.et.tudelft.nl) - CHIPLIST
∙ Ján Gúcik (jan.gucik@vslib.cz) - IntroScope
∙ Tomás Lehuta (lehuta@elf.stuba.sk) - GUS Memory routs, hints
∙ Peter Hubinsky (hubak@elf.stuba.sk; SAC fileadmin) - distribution
∙ Emil Laurentiu (lcarmen@u1.ici.ro) - hints
∙ Andrew Nelson (anelson@atlas.co.uk) - English language suggestions :-)
∙ Marek Smihla (ceit@internet.sk) - reports & hints
∙ Jiang Hong (zlzhang@pku.edu.cn) - BL3 & hints
∙ Intel and its support (support@intel.com) - excellent dox, insight CD
∙ Tamas Miklos (fieryofup@geocities.com) - WSS&Modem rout, hints, ASMDEMO
∙ ESCOM CS (escom_support@brn.pvtnet.cz) - info, reports
∙ Olivier Cahagne (cahagn_o@epita.fr) - SysInfo observatory, reports
∙ Thomas Mainka (100112.2132@compuserve.com) - reports
∙ Christian Klak (drk-soft@gmx.net) - Acer info
∙ Gershon Mikulsky (mikuls@shani.net) - ATI info
∙ Janusz Bubik (j.bubik@micronic.cz) - reports
∙ EliCZ (elicz@post.cz) - AMD-K6 DRx bug
∙ ATI Developer Relations (devrel@atitech.com) - id of ATI chips
∙ All other people, who have sent bug reports and suggestions (*!*@*.*)
Greetings to:
∙ Lubos Vrtik (vrtik@vuje.sk) - cracking <-> protecting impressions, HMVS
∙ C00LMAN [Siam Hacker's Gang] - KeY GeNeRaToR 4 HWiNFO v<4.0.0
(I'm waiting 4 keYGen 4 HWiNFO v4.0.0+)
∙ eGIS [pCE] - *v3Ry nICE* K3YG3N 4 HWiNFO ≤4.2.4, 4.2.5
(No idea how to receive the true magic numbers for v4.0.0+ ?)
∙ EliCZ [pCE] - {Ni<E W<>rK} - keygen 4 HWiNFO <4.4.4
(A little bit complicated, but at least something new.
Let's see what comes as next...)
∙ dEVIL [uCF] - *nICE* kEYZ 4 HWiNFO v4.2.2, ReGGeD v4.3.0
(try brute force attack ;-))
∙ Dark Paw - Nice Try (also w/ comments)
(Still waiting for registered users ?)
∙ lorian [uCF] - The first usable keymaker for HWiNFO <4.5.0 !
∙ All unknown members of HWiNFO <Ra<KiNG challange :-)
## 18. Disclaimer ############################################################
╔════════════════════════════════════════════════════════════════════════════╗
║ All product names are copyright and registered trademarks/tradenames of ║
║ their respective owners. ║
╚════════════════════════════════════════════════════════════════════════════╝
HWiNFO IS COPYRIGHTED MATERIAL AND PROTECTED BY APPLICABLE
COPYRIGHT LAWS AND INTERNATIONAL TREATY PROVISIONS.
THE PROGRAM AND ITS DOCUMENTATION ARE COPYRIGHTED BY THE ORIGINAL
PROGRAMMER/AUTHOR (COPYRIGHT HOLDER). ALL RIGHTS ARE RESERVED CONCERNING
FUTURE CHANGES OF THE NAME AND CONTENTS OF THIS DISTRIBUTION PACKAGE. NO
CHANGES MUST BE MADE FOR ANY REASONS AT ANY TIME BY ANYBODY IN ANY ASPECT,
INCLUDING, BUT NOT LIMITED TO, MODIFICATION OF THE COPYRIGHT NOTICE OR
CHANGES OF THE COMPILED BINARIES HEREBY ALTERING THE ORIGINALLY INTENDED
PROGRAM EXECUTION FLOW.
REALiX SPECIFICALLY DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, AND
ALL LIABILITY, INCLUDING CONSEQUENTIAL AND OTHER INDIRECT DAMAGES, FOR
THE USE OF THIS SOFTWARE, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY
PROPRIETARY RIGHTS. REALiX DOES NOT ASSUME ANY RESPONSIBILITY FOR ANY
ERRORS WHICH MAY APPEAR IN THIS CODE NOR ANY RESPONSIBILITY TO UPDATE IT.
THE PERSON USING THE SOFTWARE BEARS ALL RISKS AS TO THE QUALITY AND
PERFORMANCE OF THIS SOFTWARE.
## END #######################################################################