Computer Installation Guide - Dragon Clan Series

home *** CD-ROM | disk | FTP | other *** search

/ Computer Installation Guide - Dragon Clan Series / CD2.iso / TEST / HWINFO / HWINF306 / HWINFO.DOC < prev next >

Wrap

Text File | 1997-01-05 | 18.7 KB | 443 lines

╔════════════════════════════════════════════════════════════════════════════╗ ║ HWiNFO - Copyright (c)1995-97 RealSoft, All Rights Reserved. ║ ║ ────────────────────────────────────────────────────────────────────────── ║ ║ Version 3.0.6 ; Last Update: Jan-06-1997 ║ ╚════════════════════════════════════════════════════════════════════════════╝ *** Any comments, logfiles or questions are welcome: malik@us.svf.stuba.sk *** **************************************************** malik@elf.stuba.sk ****** ┌──────────────────────────────────────────┐ │ USE THIS PROGRAM ONLY AT YOUR OWN RISK │ └──────────────────────────────────────────┘ HWiNFO is a !POWERFUL! hardware detection program. The whole code is written in pure assembler (btw about 30,000 lines), that is why it's so tiny. It is simple, quick and on most systems very efficient. It "tries" to give only important information about all the physical things in your computer so that you need not look inside the PC to see what's there. Most routines directly access the hardware, in order to avoid some programs which emulate non-existing computer hardware. I have excluded all unnecessary information, such as CMOS, Interrupts, Drivers, Partitions info and others because HWiNFO is more Hardware-oriented. 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: SAC ftp - ftp.elf.stuba.sk /pub/pc/utilmisc SAC BBS - ++42 7 5438 232 (19,200 Baud) ++42 7 5438 295 (28,800 Baud) At other sitez/BBS later... SimTel - ftp.simtel.net /pub/simtelnet/msdos/sysinfo SAC mirrors - ftp.vse.cz /pub/msdos/SAC/pub/pc/utilmisc ftp.cs.tu-berlin.de /pub/msdos/mirrors/ftp.elf.stuba.sk/pub/pc/utilmisc ftp-beer.bke.hu /pub/sac/pc/utilmisc 192.217.228.45 /SAC/pub/pc/utilmisc Garbo archive - garbo.uwasa.fi /pc/sysinfo ## Requirements ############################################################## - DOS 3.0 or newer - cca. 300 KBytes of free system memory - Needs to be executed from directory in which it's installed in ! (I suggest, you don't rename the executable file) Well, that's all. I hope, it will work on all machines. ## Registration ############################################################## HWiNFO is shareware, meaning that you can test the program free and check if it is useful for you. The public version is Unregistered, but works at FULL Power! As it's of no use to make a Shareware version of a hardware detection program with limited abilities. The only 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 keys via E-mail, otherwise snail mail. Once you have obtained the five keys needed to register, put exactly the same name (as included in REGISTER.FRM), and all keys into the [Register] menu of HWiNFO and the current version will become registered. Note: Remember the name string you've sent to me in REGISTER.FRM, because the Registration Keys depend on it ! Well, the Registration fee is: ╔═══════════════════╦═══════════════════╗ ║ Non-Commercial ║ Commercial ║ ╠═════╤═════╤═══════╬═════╤═════╤═══════╣ ║ DEM │ US$ │ Sk/KC ║ DEM │ US$ │ Sk/KC ║ ╔═══════════════╬═════╪═════╪═══════╬═════╪═════╪═══════╣ ║ 1 User ║ 20 │ 15 │ 300 ║ 40 │ 30 │ 600 ║ ╟───────────────╫─────┼─────┼───────╫─────┼─────┼───────╢ ║ 2-10 Users ║* 18 │* 13 │* 260 ║ 36 │ 26 │ 520 ║ per copy ╟───────────────╫─────┼─────┼───────╫─────┼─────┼───────╢ ║ 11-20 Users ║* 16 │* 11 │* 220 ║ 32 │ 22 │ 450 ║ per copy ╟───────────────╫─────┼─────┼───────╫─────┼─────┼───────╢ ║ 21-50 Users ║* 12 │* 8 │* 160 ║ 24 │ 16 │ 320 ║ per copy ╟───────────────╫─────┼─────┼───────╫─────┼─────┼───────╢ ║ 51-100 Users ║* 8 │* 5 │* 100 ║ 16 │ 10 │ 200 ║ per copy ╚═══════════════╩═════╧═════╧═══════╩═════╧═════╧═══════╝ * for schools, educations, etc. When registering per 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 - Does Reset 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 - Does Reset 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 setction. 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). The most CPUs today support CPUID instruction. Note: NexGen Nx586, Cyrix 5x86 and 6x86 do NOT support CPUID instruction. 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 CPU detection. Some BIOSes simply OVERWRITE the CPU ID (EDX) :-< ! In this case is an invalid CPU ID displayed and the CPU problably not correctly 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. ARIA sound card, Stacker Compression Card and 3Com EtherLink III Adapter detection routines cause crash with some Network cards. You can disable them the in Setup section (ARIA and Stacker check are default disabled; 3Com EtherLink III detection is enabled). On some old motherboards are random number obtained from not used I/O ports and this may cause invalid identification of Aria sound card or Hitachi CD-ROM. 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 82440FX NATOMA √ Intel 82450KX/GX ORION chipsets, not depending on the type of BIOS. Fixed Disk Data Transfer rate reads data from one physical sector until 4 secconds. 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 results 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 to be installed. 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. The Internal (1st level) Cache size reflects only Data cache. This means, that it gives real results on 486- systems, but on Pentium+ systems, which have separate caches for Data and Instructions, it returns only the size of Data cache. Maybe in the future I'll add a test for both parts. Intel Pentium Pro and above directly return information about TLB (Translation Look-aside Buffer), Level 1 and Level 2 on-chip caches -- info about TLB is displayed in CPU Identification section and L1, L2 cache implemented into System info. Intel Pentium and above CPUs do not report, that the "APIC on-chip" feature is present. They do have an Advanced Programmmable Interrupt Controller on-chip, 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. And so, 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 TRITON FX/HX/VX/MX or SiS 85C511 chipset, HWiNFO is able to detect the type of External Cache and its size directly from the PCI chipset registers. The possible types are: √ Synchronous Pipelined Burst Cache Synchronous Burst Cache √ Asynchronous SRAM Cache Dual-Bank Pipelined Burst Cache Also if you have an Intel TRITON FX/HX/VX/MX chipset, HWiNFO is able to detect if you are using EDO RAM. HWiNFO is able to detect these types of Video RAM: √ EDO DRAM/VRAM - for S3 chipsets √ WRAM - for Matrox MGA Millennium board SDRAM - (Synchronous DRAM) for Cirrus Logic chipsets (CL-GD5480) RDRAM - (Rambus DRAM) for Cirrus Logic chipsets (CL-GD546x) ## Running 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 correct. 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 didn't find 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 to run HWiNFO in Real Mode. >>> HWiNFO is unable to run under Microsoft Windows, Windows95, Windows NT 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 appz to directly access the disk and some hardware routines cause problems, thus it can't be supported. ## Seccond Graphics Accelerator ############################################## 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 ######################################################## You can create a log-file by pressing the <PrintScreen> 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 an Auto-Logging feature, that automatically logs all screens, which you open. You can enable it in the Setup menu. ## Thanx ##################################################################### I want especially to thank: ∙ Beta testers: Boris Hurínek (hurinek@axa.sk) Erik Francisci (franto@iris.elf.stuba.sk) Igor Junas (junas@isnet.sk) Matús Rosa (rosa@elf.stuba.sk) Milan Marusinec (marusine@ba-cvt.sanet.sk) ∙ Alex V. Potemkin and Potemkin's Hackers Group (root@chaos.remote.misa.ac.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 ∙ 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 ∙ All other people, who have sent me bug reports and suggestions (*!*@*.*) Greetings to: ∙ Lubos Vrtik (vrtik_l@inst.vujett.sk) - cracking <-> protecting ∙ Siam Hacker's Gang (?@?.?) - KeY GeNeRaToR 4 HWiNFO BTW, v3.0.6+ will not work with cracked keys for 3.05 :-) (C00LMAN, you must crack it again. I would like to contact you.) ## 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 #######################################################################