HWinfo v4.88

HWiNFO v4.95

IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII

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
13. Hardware monitor chip support
14. IDE Disk Transfer Modes
15. Miscellaneous notes
16. Some abbreviations
18. Disclaimer and Terms of License

## 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:

HWiNFO homepage - http://www.hwinfo.com

SAC ftp - ftp.elf.stuba.sk/pub/pc/utildiag
SAC WWW - www.sac.sk

At other sitez/BBS later...
SimTel - ftp.simtel.net/pub/simtelnet/msdos/sysinfo
SAC mirrors - ftp.sac.sk/pub/sac/utildiag
ftp.cdrom.com/pub/sac/utildiag
ftp.uakom.sk/pub/mirrors/sac/utildiag
ftp.vse.cz/pub/msdos/SAC/pc/utildiag
ftp.bke.hu/pub/mirrors/sac/utildiag
esca.atomki.hu/paradise/sac/utildiag
ftp.externet.hu/pub/mirror/sac/utildiag
ftp.osb.hu/pub/mirrors/sac/utildiag
ftp.cs.tu-berlin.de/pub/msdos/mirrors/stuba/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.comp.hkbu.edu.hk/pub/sac/utildiag
ftp.nsysu.edu.tw/PC/SAC/utildiag

## 3. Requirements ###########################################################

- 80386 or better CPU
- cca. 480 KBytes of free Conventional system memory
- cca. 2.0 MBytes of free XMS memory (XMS manager recommended)

## 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

GETSMBUS.EXE This utility reads data from all devices connected to SMBus
(e.g. HW monitors, P.I.ROM, Scratch EEPROM, SPD DIMM...)
and saves to files SMBUS<ADR>.DAT

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:

╔═════╤══════╗
║ US$ │ SKK ║
╔═══════════════╬═════╪══════╣
║ Home-user ║ 12 │ 400 ║
╟───────────────╫─────┼──────╢
║ 1 User ║ 25 │ 800 ║
╟───────────────╫─────┼──────╢
║ 2-10 Users ║ 23 │ 750 ║ per copy
╟───────────────╫─────┼──────╢
║ 11-20 Users ║ 21 │ 700 ║ per copy
╟───────────────╫─────┼──────╢
║ 21-50 Users ║ 18 │ 600 ║ per copy
╟───────────────╫─────┼──────╢
║ 51-100 Users ║ 15 │ 500 ║ per copy
╟───────────────╫─────┼──────╢
║ 101-500 Users ║ 11 │ 350 ║ per copy
╚═══════════════╩════════════╝

For any special requirements contact the author.

A registration is valid for all future versions.
Please read Terms of License at the end of this file.

## 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 III Xeon, 550.0 MHz
Bus=ISA + PCI + A.G.P.
Chipset=Intel 82440GX AGPset
Memory=128 MBytes
...
VideoChipset=nVIDIA GeForce 256 DDR
VideoMemory=32768 KBytes of SGRAM
3Daccel=3Dfx Voodoo 2
...

If you use a capital letter (either "-R" or "-S") the benchmark will not
be performed.

The "-v" switch enables Verbose Mode, where all screen outputs are supressed.

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 -S -v HOME.LOG").

Samples of logfiles can be found at HWiNFO homepage.

## 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).

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.

## 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 or to receive the Processor Number
while this feature has been disabled)
- 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)

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 ##########################################################

- If HWiNFO crashes while executing the CPU benchmark, please use
HIMEM.SYS (or another XMS manager).

- 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.

## 13. Hardware monitor chip support #########################################

Sensor chip Temps Voltages FAN Interface Misc
-------------------------------------------------------------------------------
National Semi. LM75 1 - - SMBus
Genesys GL523SM 1 - - SMBus
Maxim MX1617 2 - - SMBus
Maxim MX1617A 2 - - SMBus
Analog Devices ADM1021 2 - - SMBus
Analog Devices ADM1022 3 - - SMBus
TI THMC50 1 - - SMBus
Fairchild FMS2701 1 - - SMBus

National Semi. LM78 1 6 3 ISA, SMBus
National Semi. LM78-J 1 6 3 ISA, SMBus
National Semi. LM79 1 6 3 ISA, SMBus
National Semi. LM80 - 6 2 SMBus

Winbond W83781D 3 7 3 ISA, SMBus
Winbond W83782D 3 9 3 ISA, SMBus 5VSB, VBAT voltages
Winbond W83783S 2 6 3 SMBus
Winbond W83L784LR 3 4 2 SMBus Battery voltage
SMSC MON35W82 3 9 3 ISA, SMBus 5VSB, VBAT voltages
SMSC LPC61W492 3 9 3 ISA, SMBus 5VSB, VBAT voltages

Analog Devices ADM9240 1 6 2 SMBus
National Semi. LM81 1 6 2 SMBus
Dallas Semi. DS1780 1 6 2 SMBus

Analog Devices ADM1024 2 6 2 SMBus
Analog Devices ADM1025 2 6 2 SMBus
National Semi. LM87 2 6 2 SMBus

Analog Devices ADM1026 3 16 8 SMBus
Analog Devices ADM1028 2 - 1 SMBus
Analog Devices ADM1029 2 - 2 SMBus
Analog Devices ADM1030 2 - 1 SMBus

VIA VT82C686 Internal 3 7 2 ISA
SiS 5595 1 4 2 ISA
SiS 950 LPC 3 8 3 SMBus

Genesys GL518SM 1 1 2 SMBus
Genesys GL520SM 2 4 2 SMBus
Genesys GL525SM 2 5 3 SMBus
-------------------------------------------------------------------------------

Detection of chips with SMBus interface requires a supported SMBus Host Controller.

## 14. 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
│ Ultra-DMA 5 │ 100.00 MB/s │ ATA-100
│ Ultra-DMA 6 │ 133.33 MB/s │ ATA-133
└─────────────┴───────────────┘

## 15. 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.

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.

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.

## 16. 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 = Some enhancements to MMX (Intel)
3DNow! = Additional floating point MMX instructions (AMD, Cyrix)
ISSE / KNI = Internet Streaming SIMD Extensions (Katmai New Instructions)
(70 SIMD floating-point instructions, 128-bit registers)
S.E.C.C. = Single Edge Contact Cartridge (SECC1, SECC2)
PPGA = Plastic PGA (Pin Grid Array)
FCPGA = Flip-Chip PGA
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)

## 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.

LICENSE
=======

SHAREWARE COPY
--------------

A shareware (unregistered) copy of HWiNFO is the distributed package
of HWiNFO without any key file. This copy may be distributed freely,
but must not be modified in any way. It is not allowed to sell the
shareware copy of HWiNFO like a standalone program; a shareware copy
is free.

REGISTERED COPY
---------------

A registered copy includes the shareware copy plus a valid key file.
A user may use the registered copy of HWiNFO only when accepting
the terms of license. It is not allowed to distribute this copy.

LICENSE TYPES
-------------

A non-commercial license means, that the user may use the registered
copy for non-commercial purposes only (e.g. for own using, for
education, etc.). A commercial license enables the license holder to
use the registered copy of HWiNFO for commercial purposes also.

LICENSE AMOUNT
--------------

The license amount selects the amount of licensed copies, that are
allowed to run within the registered subject. A single-user license
allows the subject to use only one registered copy at a time. An
unlimited license enables the license holder to register any number
of copies of HWiNFO using the given key file.

TERMS OF LICENSE
----------------

A key file may be used ONLY by the appropriate registered subject
and only in such a way, that doesn't violate the license type and
license amount limitations. The name of license holder is displayed
in the first dialog after running HWiNFO (the "Registered to" line).
The license type and amount is displayed too.
A subject is using the program legally, only when accepting and not
violating the terms of license.

It is not allowed to:
- sell the shareware copy of HWiNFO like a standalone program
- modify a copy of HWiNFO or the key file
- give the key file to person, which isn't granted to use it
- distribute or sell the key file
- violate terms of license

http://www.hwinfo.com

IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII

Contact Binarica.com support for more info