home *** CD-ROM | disk | FTP | other *** search
- ╔════════════════════════════════════════════════════════════════════════════╗
- ║ HWiNFO - Copyright (c)1995-97 RealSoft, All Rights Reserved. ║
- ║ ────────────────────────────────────────────────────────────────────────── ║
- ║ Version 4.2.7 ; Last Update: Jan-18-1998 ║
- ╚════════════════════════════════════════════════════════════════════════════╝
-
-
-
-
-
-
- ┌──────────────────────────────────────────┐
- │ USE THIS PROGRAM ONLY AT YOUR OWN RISK │
- └──────────────────────────────────────────┘
-
-
-
-
-
-
-
-
-
- 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. I hope you don't want HWiNFO to determine
- your mouse cable length or the speed of your computer fan... :-)
-
-
- The newest version is always (immediately) available at:
-
- My homepage - http://www.svf.stuba.sk/~malik
-
- SAC ftp - ftp.elf.stuba.sk/pub/pc/utilmisc
- http://ftp.elf.stuba.sk/packages/pub/pc/utilmisc
- 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/utilmisc
- ftp.intec.sk/sac/utilmisc
- ftp.vse.cz/pub/msdos/SAC/pc/utilmisc
- ftp.cs.tu-berlin.de/pub/msdos/mirrors/stuba/pc/utilmisc
- ftp-beer.bke.hu/vol1/pub/sac/pc/utilmisc
- ftp.pwr.wroc.pl/pub/pc/sac/utilmisc
- cert.unisa.it/pub/PC/SAC/utilmisc
- ftp2.itb.it/pub/PC/SAC/utilmisc
- ftp.nsysu.edu.tw/PC/SAC/utilmisc
- 192.217.228.45/SAC/pub/pc/utilmisc
- ftp.comp.hkbu.edu.hk/pub/sac/utilmisc
- ftp.cdrom.com/pub/sac/utilmisc
-
-
-
- ## Requirements ##############################################################
-
-
- - cca. 470 (+40) KBytes of free system memory
-
- Well, that's all. I hope it will work on all machines.
-
-
-
-
- ## Utils #####################################################################
-
-
- 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 saves all PCI devices data into files
- <VendorID><DeviceID>.PCI
-
- GETPNPRS.EXE This utility saves resource data for all Plug-and-Play
- capable devices into files PNP<CSN>.RES
-
-
- These utilities are free and are designed to help me improve HWiNFO if
- you send the results to me.
-
-
-
-
- ## 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 30 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 this address:
-
- Martin Malík
- Jakubovo nám. 3
- 811 09 Bratislava
- SLOVAK REPUBLIC
- EUROPE
-
- If you include your Internet e-mail address, you will receive the
- registration code via e-mail, otherwise snail mail.
-
- Once you have obtained the nice code needed to register, put exactly the
- same name, and the code into the [About|Register] menu of HWiNFO and the
- current version will become registered.
-
-
-
- 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 !
-
-
-
-
-
-
-
-
- ## Comments... ###############################################################
-
-
- 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 6x86 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.
-
-
- 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 Setup
- section (Stacker check is default disabled; 3Com EtherLink III detection
- is enabled).
-
-
- 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.
-
-
- The Mainboard Chipset indentification works only on newer (≈ 1991 and above)
- AMI and newer AWARD BIOSes.
-
- HWiNFO is also able to detect: √ Intel 82420TX SATURN
- Intel 82420EX ARIES
- √ Intel 82430LX MERCURY
- √ Intel 82430NX NEPTUNE
- √ Intel 82430FX TRITON
- √ Intel 82430HX TRITON II
- √ Intel 82430VX TRITON II
- √ Intel 82430MX MOBILE TRITON
- √ Intel 82430TX MOBILE TRITON II
- √ Intel 82440FX NATOMA
- Intel 82440LX AGPset
- √ Intel 82450KX/GX ORION
- √ AMD-640(TM)
-
- chipsets, not depending on the type of BIOS.
-
-
- Fixed Disk Data Transfer rate reads data from one physical sector for 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.
-
-
- 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 !
-
-
- CD-ROM benchmark requires MSCDEX.EXE (Microsoft CD-ROM Extensions) to
- be installed and an inserted data CD.
-
-
- 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.
-
-
-
-
- ## PCI Chipsets ##############################################################
-
-
- If you have an Intel 420LX/420NX/430FX/430HX/430VX/430MX/430TX, SiS 85C511
- of AMD-640 chipset, HWiNFO is able to detect the type of External Cache
- and its size direct from the PCI chipset registers. The possible types are:
-
- - Synchronous Pipelined Burst Cache
- - Synchronous Burst Cache
- - Asynchronous SRAM Cache
- - Dual-Bank Pipelined Burst Cache
-
-
-
- HWiNFO reports the size, memory type, DRAM Read Burst Timing, DRAM Write
- Burst Timing and Error Check/Correction type for each DRAM row for these
- chipsets:
-
- Reports Reports
- RAM Row Recognized DRAM R/W Recognized Error
- Chipset Size DRAM Type Burst Check/Correction Type
- ┌──────────────────┬───────┬─────────────────┬───────┬───────────────────────┐
- │ Intel 82420TX │ Yes │ FPM │ No │ - │
- │ Intel 82420EX │ Yes │ FPM │ No │ - │
- │ Intel 82420LX │ Yes │ FPM │ No │ - │
- │ Intel 82420NX │ Yes │ FPM │ Yes │ - │
- │ Intel 82430FX │ Yes │ FPM, EDO │ Yes │ - │
- │ Intel 82430MX │ Yes │ FPM, EDO │ Yes │ - │
- │ Intel 82430HX │ Yes │ FPM, EDO │ Yes │ Parity, ECC │
- │ Intel 82430VX │ Yes │ FPM, EDO, SDRAM │ Yes │ - │
- │ Intel 82430TX │ Yes │ FPM, EDO, SDRAM │ Yes │ - │
- │ Intel 82440FX │ Yes │ FPM, EDO, BEDO │ Yes │ None, Parity, EC, ECC │
- │ Intel 82440LX │ Yes │ EDO, SDRAM │ Yes │ None, EC, ECC │
- │ Intel 82450KX/GX │ Yes │ FPM │ No │ None, ECC │
- │ SiS 496/497 │ Yes │ FPM │ No │ - │
- │ AMD-640 │ Yes │ FPM, EDO, SDRAM │ No │ Parity, ECC │
- └──────────────────┴───────┴─────────────────┴───────┴───────────────────────┘
-
-
- Note: FPM = Fast-Page Mode (old standard DRAM type)
- EDO = Extended Data-Out
- SDRAM = Synchronous DRAM
- BEDO = Burst EDO
-
- EC = Error Check only
- ECC = Error Check and Correction
-
-
-
-
- ## Video Memory Types ########################################################
-
-
- HWiNFO is able to detect these types of Video RAM:
-
- √ DRAM/VRAM - many chipsets
- √ EDO - for S3 chipsets
- √ WRAM - for Matrox MGA-2064W, MGA-2164W (Millennium / II) card
- SDRAM - (Synchronous DRAM) for Cirrus Logic chipsets (CL-GD5480)
- √ SGRAM - (Sync Graphics RAM) for Matrox MGA-1064SG and S3
- √ RDRAM - (Rambus DRAM) for Cirrus Logic chipsets (CL-GD546x)
- √ MDRAM - (Multibank DRAM) for Tseng ET6000
-
-
-
-
- ## 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 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 - Mobile Intel Pentium(R) Processor with MMX(TM) Technology:
- 200/66 and 233/66 MHz
-
- 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
- Level-2 cache 256K or 512K.
-
- 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
-
-
-
- Note: VRT = Voltage Reduction Technology
- APIC = Advanced Programmable Interrupt Controller
- DP = Dual Processing
- FRC = Functional Redundancy Checking (requires DP)
- MMX = Multimedia Extensions in CPU - 57 new 64-bit instructions,
- SIMD architecture ...
- S.E.C = Single Edge Contact (CPU and Level-2 cache on one substrate)
-
-
-
-
- ## 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
- └─────────────┴───────────────┘
-
-
-
-
- ## Running HWiNFO under V86 Memory Managers ##################################
-
- HWiNFO (v3.00+) is able to run in Virtual86 mode under some circumstances
- (it means, under some applications, which turn the V86 mode on). But ONLY
- those which support the Windows INIT BROADCAST and handle it correctly.
- Such known applications are:
- - Microsoft EMM386 Expanded Memory Manager
- - Quarterdeck QEMM386 Expanded Memory Manager
- - Qualitas 386MAX Expanded Memory Manager
- - Nu-Mega Soft-ICE Debugger
- .......
-
- These applications are able to switch to Real mode when they receive the
- Windows INIT BROADCAST message. But if you run HWiNFO in V86 there may
- occur some problems, especially during CPU RESET (like hang, crash...).
- Also some Memory Managers, which relocate BIOSes, may cause misidentification
- of BIOS (like QEMM386's Stealth Mode). HWiNFO works best under EMM386
- (I haven't found any problems). The method of detecting CPU frequency via
- TSC (Time Stamp Counter) doesn't work if V86 mode is turned on.
- <<< So, I prefer runnig HWiNFO in Real Mode. >>>
-
- HWiNFO is unable to run under Microsoft Windows and Windows95 DOS box,
- Windows NT VDM and IBM OS/2, because they don't switch to Real Mode and
- also manipulate Benchmark results, BIOS scan, are able to control direct
- I/O operations, which can cause invalid results and Windows NT doesn't
- allow 16-bit applications to directly access the disk and some hardware
- routines cause problems, thus it can't be supported.
-
-
-
- ## 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
-
-
-
-
-
- ## Creating a logfile or whole report ########################################
-
- You can create a log-file by pressing the <F2> key; it will add the results
- from current screen to a file named "hwinfo.log". You can change the name of
- this file by entering the .log filename you want, as a parameter to hwinfo;
- e.g. "hwinfo.exe my_p7.log".
-
- There is also a "Create report file" feature, but it's available only for
- registered users. It will create automatically a complete logfile, when
- you start HWiNFO using the "-r" switch. There is no need to navigate HWiNFO
- through all screens.
-
-
-
-
-
-
-
-
-
- ## Thanx #####################################################################
-
-
- 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@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
- ∙ Robert Cline, Tim McCarthy (support@mailbox.intel.com) - id of Intel CPUs
- ∙ Tamas Miklos (fieryofup@geocities.com) - WSS rout, hints, ASMDEMO
- ∙ ESCOM CS (escom_support@brn.pvtnet.cz) - info
- ∙ Olivier Cahagne (cahagn_o@epita.fr) - SysInfo observatory
- ∙ Thomas Mainka (100112.2132@compuserve.com) - reports
- ∙ Christian Klak (drk-soft@gmx.net) - Acer info
- ∙ Gershon Miklusky (miklus@shani.net) - ATI info
-
- ∙ All other people, who have sent me bug reports and suggestions (*!*@*.*)
-
-
-
-
-
- Greetings to:
-
- ∙ Lubos Vrtik (vrtik@vuje.sk) - cracking <-> protecting impressions, HMVS
-
- ∙ C00LMAN of 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+ ?)
-
- ∙ dEVIL / uCF - *nICE* kEYZ 4 HWiNFO v4.2.2
- (Must have been a hard work)
-
-
-
-
-
-
-
-
-
-
- ## 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.
-
- RealSoft 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. RealSoft 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 #######################################################################