DOC

HWINFO

By Jane Lawson,2014-09-15 22:31
10 views 0
HWINFO

     ,????????????????????????????????????????????????????????????????????????????,

     HWiNFO ?Copyright (c)1995-2003 Martin Malk - REALiX(tm)

     ??????????????????????????????????????????????????????????????????????????

     ; Version 4.8.8; Last Update: Jan-21-2003 ;

     ?????????????????????????????????????????????????????????????????????????????:

     ???????????????????????????????????????????;

     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. Hardware monitor chip support

     14. IDE Disk Transfer Modes

     15. Miscellaneous notes

     16. Some abbreviations

     17. Codenames

     18. Thanks

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

     You can contact the author at: martin@hwinfo.com

     or: malik@svf.stuba.sk

     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. 500 KBytes of free System Memory

     - cca. 1.5 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 .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 .PCI

     GETPNPRS.EXE This utility saves resource data for all Plug-and-Play

     capable devices into files PNP.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.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:

     ,??????????????????:??????????????????,

     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 authorContact the author

     ??????????????????????????????????????????????????????:

     * for schools, educations, etc.

     When registering with a check or wire transfer please add 10% to

     the total price to cover bank transfer and conversion 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.

     Please read Terms of License at the end of this file.

     You should register NOW !

     ## 6. Creating a logfile #####################################################

     There are three possible methods how to create a logfile:

     1. Simple log

     After pressing the 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 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).

     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 .

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

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

     - 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

Report this document

For any questions or suggestions please email
cust-service@docsford.com