README for PCI32.ZIP This is a very quick note to explain PCI32. PCI32 is just a port of my 16-bit DOS program 'PCI' to "true" win32 - that is, functionality under Windows NT 4.0, 2000, XP and so on. This program will NOT work under DOS/WIN9x/ME/OS2/Linux etc..!!! PCI32 is tested and works under any Microsoft win32 OS e.g. NT4.0, Win2000, XP, 2003, & "Longhorn beta", including all server versions and other variants (media centre, SBS server, tablet edition, etc) The new reader is recommended to read PCI.DOC (Included in the archive) for historical information regarding this software. It is reported that PCI32 does work under a 32-bit WinPE Environment (such as BartPE), although I do not personally test it for use in that environment, and continued functionality is not guaranteed. I will try not to break WinPE compatibility, as WinPE is the sort of area that PCI32 proves to be of great use - I quite simply don't have the resources to guarantee it. Full documentation on the more abstract aspects of PCI32 such as the PCIDEVS.TXT official file format can be found in its sister program, PCI. Some functions not relevant in the win32 environment have been removed - pci32 /? lists the functions that work... Support website: http://members.datafast.net.au/dft0802 Email: chart at datafast dot net dot au (Damn Spam!!) How to use it? PCI32 is a console mode program - you run it from the command prompt. The results appear in text form in the command prompt window, just like "good old" MS-DOS... There is no 'GUI' interface. Like all good console mode software, it takes command line parameters (try pci32 /?), and can have it's output 'piped' to a file or device. So, if you really hate console mode, do this: PCI32 > report.txt notepad report.txt Which will generate the report and then launch notepad with the results opened. You can then cut/paste/print/etc to your hearts content. As a free bonus, the file 'report.txt' is saved for you to come back to in future. Wow :-) If it won't run... - You need PCI32.EXE, GWIOPM.SYS and PCIDEVS.TXT present for it to run. If any file is missing, it won't work. - You need administrator privileges to run (or at least, rights to install and start device drivers). This is because PCI32 seamlessly installs a device driver (gwiopm.sys) in order to directly accesses the PCI hardware. Gwiopm.sys is removed when the program exits - nothing left behind in memory or the registry and no need to reboot. How cool is that? This also means you can run it on a 'live' server (from a floppy, memory stick, CD, whatever). Handy, that. - You probably need to run it from a local disk drive; it may or may not run from a mapped drive or UNC path (Sometimes it works, sometimes not. Experiment a bit.) - You run it from the command prompt, NOT by double-clicking on it from explorer or via start-run. Otherwise the results just scroll by and the window closes. - You will need to use the CD command to make the directory with PCI32's files the CURRENT directory before running PCI32. This is because the program looks in the current directory for its files, not the program’s directory. - PCI32's driver seems to conflict with “motherboard monitor” by LiveWireDev.com Remove MBM (and reboot) before using PCI32. MBM is now unsupported software and should be removed anyhow. - PCI32 is a 32-bit program and will NOT function under any 64-bit version of Windows eg XP-64, server 2003 64-bit edition, IA64 or A64 or Itanium 64-bit OS'S. - Always remember that help is available by running pci32 /? You’ll also discover some interesting extra features there. - If none of the above makes sense, bear in mind that this is a technical tool written for technicians. Not to be nasty, but if the above is too confusing, perhaps you probably don't need whatever PCI32 does. Updating the PCI database The value of any PCI program is reflected directly by how current it's PCI device database (pcidevs.txt) is. If the database is too old, modern hardware won't be recognised, and therefore the program's net worth is much reduced. To counter this issue, I actively maintain and update the database on a daily basis. New (and previously unknown) devices are regularly added, and existing entries are updated to more accurately reflect the actual hardware or fix recognition issues. Updated lists are published (on average) about twice a month, or as often as updates are received and processed. All list entries are hand-edited, no scripts or automated procedures are permitted - this means that "garbage" is kept out of the list. Most other lists found on the web are full of errors, but this list is not, thanks to the validation of having a human actually checking the data as it is entered. Of course, typos and just plain incorrect information do make it to the list from time to time; therefore if you ever find an error, please email me the details, and it will be corrected immediately. Your Contributions Are Requested All this is only possible, however, if I receive update contributions from YOU, the public. I cannot possibly gain access to every piece of PCI hardware ever built, nor can I spend all my time trolling about people's computers, manufacturer manuals, driver .INF's and websites trying to locate PCI ID's. Here's how you can help: If you have any information on a PCI device which is not in my database, including the Windows driver's .INF file, a list of device ID's, web links, specifications documents, dumps from my PCI programs, etc etc. please send them to me!! My email address is listed at the top of this document. Contributions from hardware developers are especially appreciated. If you would like your products to be instantly recognisable, by your official product name, to a large number of diagnostic tools as well as the Linux and FreeBSD operating systems, then you should send me your ID's! Listing is of course completely free of charge, and you can be sure that your products will be correctly recognised using your preferred wording and official product naming conventions. To add an entry to the database, at minimum I need the PCI Vendor ID, Device ID, and a device description. Any bonuses would be information pertaining to device revisions, subsystem ID's, previous company names for the vendor, details of product families, details on how to tell similar products apart, and so on. The easiest way to do this is to get the .INF file from the Windows driver for the hardware, and send that to me. A Windows driver .INF file contains everything I need to know, and every driver must have an .INF file (Although it may sometimes be hidden inside an installer archive). As a bonus, .INF's often list a number of devices from the same product family, so I may be able to add recognition of a whole group of products, just from one INF! A commentary on PCI databases My database 'PCIDEVS.TXT' is the most extensive listing I can find on the web. There are other listings, such as the Linux list, however they don't keep track of as much basic information such as chip revisions, nor do they have as much "raw data" as mine. If you think my list is out of date, don't complain about it, contact me and help me make the list better for everyone! Be aware, however, that lists exist with large numbers of errors or are simply out of date. Ask yourself when and how the list is maintained before concluding that another list is better/bigger/more accurate. Many other PCI databases are actually just my list, reformatted or merged with other lists to form a new list. My list has a few subtle characteristics, which indicate list re-packaging, such as the vendor names with a (was: xxx) edit, and a few deliberate typos here and there. Whilst I fully support the use of my data in other programs, the wholesale cut-and-paste of my list by simply renaming, reformatting or deliberate alteration of the comments to hide it's true origin disgusts me, and I urge you to report any such lists to me so that I may take action against the parties involved. It is my understanding at this time that both the Linux and FreeBSD lists are the [partial] result of merges of my list. It's absolutely OK by me for them to do this, as they asked my permission first, and I granted it. Anyone else merging my list with other lists is doing so without my permission or approval. Remember, the list is Copyright, and although you are free to use it AS-IS, you cannot alter it or call it yours. (See the legal section at the end). In summary: You can use this list for anything you want, but only if you keep it intact, as-is - don't pollute it with merges from other lists or remove any part of the list, especially the comments at the top and bottom. If you think this list needs updating, don't merge your stuff in and keep it to yourself; please send ME the merge-data so that this list gets better! I strongly urge developers to use the list in your programs, rather than start your own list: my list is absolutely free, easy to use, regularly updated, and contains far more info than you could possibly assemble yourself if you started from scratch. All I ask is that you mention this website in your software, so your users know where to go to get updates, and that you keep pcidevs.txt intact (no editing please), and as a separate file - don't compile it into your program, don't rename the file, and don't try to "hide" it's true source by editing it to remove my name and links. You are welcome to come back to my website and download for yourself the most current database as often as you like. It's completely free, even for commercial use. There are no catches - this is a hobby of mine, not a money making enterprise. Compiling the program 100% of all source and object code required to recompile yourself is supplied. You don't need anything else besides a copy of Delphi to recompile yourself. I compile with Borland Delphi 4.0 standard (Other versions of Delphi are untested and may or may not work). Do *NOT* load into Delphi's GUI!!! At the command prompt run dcc32 pci32.pas to compile! Several other people's code is used in PCI32 (Device Driver & NT driver subsystem stuff) - read all the source code files to see who did what. Legal mumbo Jumbo PCI32 is freeware. Use it, it's free. Also, no need to ask before you incorporate this code into commercial software. Credit would be appreciated if you use parts of the code in your own programs, and an email would be nice if you do find a good use for it – I’ll be happy to mention your software on my website. As with all freeware products, the code is provided as-is, and no warranty or guarantee of fitness for any purpose is implied. PCIDEVS.TXT is also freeware, HOWEVER it is also Copyright. You are NOT permitted to alter or edit the file in any way, particularly not to remove my name from it or add yours. This is my list, you may USE and distribute it as-is, but you may not alter it. Consider the file READ-ONLY! You may make derivative works based on my file; eg you may merge the data contained within my list with yours to improve your list. Acknowledgement of my contribution, which is visible to your end-user, is required. GWIOPM.SYS is not mine. Before using that driver software, please read it's licence and decide for yourself if you can use it. The home of GWIOPM.SYS is at http://www.wideman-one.com/gw/tech/Delphi/iopm/index.htm Publishers wishing to include PCI32 on a free ‘Cover CD’ and/or write a review article on PCI32 for publication, are free to do so without making additional requests for approval; however the article must include attribution to the author “Craig Hart” and reference the official website http:://members.datafast.net.au/dft0802 Other than that, please use it at your leisure. Program Revision Info Version 0.50ß - inital relase. Crude, rushed port from DOS Version. Seems to work OK, but: no color no page pause some diagnostic modes removed as not relevant to win32 environment driver requires administrative privilages to load filesize 81k!! Version 0.51ß - added decode of driver load/unload error messages - added self-repair of previous failed driver-install to fix an issue where driver stuffs up if it couldn't load for a reason, and then PCI32 was re-run. (usually caused by no gwiopm.sys or not run with admin privilages) - added APIC mode detection & comment to IRQ info. - added run from anywhere feature - pci32 can now run from a path and still load pcidevs.txt. Unsure if UNC path works yet, but is likely... - got colour working in console display output. Version 0.52ß - Added major features to power management capability decoding - fixed major bugs with: printstatus() routine always dropping first message expROM sizing (again!) - removed code left over from DOS port which is not actually called in program! - will now run from a UNC path correctly in most cases; needs more testing to be certain... - updated with AGP 8x (Version 3.0) support - updated with 'classic' PCI v2.3 & v3.0 specs: New capabilities: HyperTransport capabiltiy AGP 8x capability Secure Device capability PCI Express capability MSI-X capability - updated with basic PCI Express support; much more to come yet PCI Express support is experimental and untested on actual hardware so far... Version 0.53ß - Bunch of bugfixes to do with scanning multi-function devices. This bug has existed since v1.0 of PCI!! - Obsure bug with revision checking in sybsystem code causing GPF fixed (Bug only visible on obscure Intel PCIe chipsets) Version 1.0 - Decided to drop the 'beta' label once and for all; hence version 1.0 - More issues with Expansion ROM detection/sizing fixed - Fixed problems with hex dump corruption (caused by ExpROM decode test) - some fixes to PCI Express code Version 1.1 - Fixed a big bug with configuration space write code – which was not actually writing anything sane into the PCI Configuration space registers. This has finally fixed the elusive Expansion Rom code once and for all - I Promise! - Added decoding of Power Management data register, if present. - Added maximum bus latency and minimum bus grant timer info to reports - Added –R option to draw a “tree” of the hardware Bus:Device:Function structure - Finally fixed log standing, stupid code bug with subsystems vs R entries. - Minor fix-ups to PCI Express code; more to follow yet. - Depreciated priority of legacy ‘PCI’ 16-bit version, which will continue to be maintained, but is given less priority than PCI32 in future. Expect to see new features in PCI32 first, with back-porting, where possible, later.