文件列表:

PCI32.EXE (110080, 2007-07-20)
CLASSES.PAS (9611, 2005-08-30)
GWIOPM.PAS (22061, 2004-07-01)
PCI32.PAS (77983, 2007-07-20)
GWIOPM.DCU (13365, 2005-02-24)
GWIOPM.SYS (3904, 1998-06-03)
ICON.RES (876, 2002-06-21)
PCIDEVS.TXT (828991, 2007-11-08)

{\rtf1\adeflang1025\ansi\ansicpg1252\uc1\adeff0\deff0\stshfdbch0\stshfloch0\stshfhich0\stshfbi0\deflang3081\deflangfe3081{\fonttbl{\f0\froman\fcharset0\fprq2{\*\panose 02020603050405020304}Times New Roman;}{\f1\fswiss\fcharset0\fprq2{\*\panose 020b0604020202020204}Arial;} {\f3\froman\fcharset2\fprq2{\*\panose 05050102010706020507}Symbol;}{\f37\froman\fcharset238\fprq2 Times New Roman CE;}{\f38\froman\fcharset204\fprq2 Times New Roman Cyr;}{\f40\froman\fcharset161\fprq2 Times New Roman Greek;} {\f41\froman\fcharset162\fprq2 Times New Roman Tur;}{\f42\fbidi \froman\fcharset177\fprq2 Times New Roman (Hebrew);}{\f43\fbidi \froman\fcharset178\fprq2 Times New Roman (Arabic);}{\f44\froman\fcharset186\fprq2 Times New Roman Baltic;} {\f45\froman\fcharset163\fprq2 Times New Roman (Vietnamese);}{\f47\fswiss\fcharset238\fprq2 Arial CE;}{\f48\fswiss\fcharset204\fprq2 Arial Cyr;}{\f50\fswiss\fcharset161\fprq2 Arial Greek;}{\f51\fswiss\fcharset162\fprq2 Arial Tur;} {\f52\fbidi \fswiss\fcharset177\fprq2 Arial (Hebrew);}{\f53\fbidi \fswiss\fcharset178\fprq2 Arial (Arabic);}{\f54\fswiss\fcharset186\fprq2 Arial Baltic;}{\f55\fswiss\fcharset163\fprq2 Arial (Vietnamese);}}{\colortbl;\red0\green0\blue0; \red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128; \red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;}{\stylesheet{\ql \li0\ri0\nowidctlpar\wrapdefault\faauto\rin0\lin0\itap0 \rtlch\fcs1 \af0\afs24\alang1025 \ltrch\fcs0 \f1\fs24\lang3081\langfe3081\cgrid\langnp3081\langfenp3081 \snext0 Normal;}{\s1\ql \li0\ri0\nowidctlpar\wrapdefault\faauto\outlinelevel0\rin0\lin0\itap0 \rtlch\fcs1 \af0\afs24\alang1025 \ltrch\fcs0 \f1\fs24\lang3081\langfe3081\cgrid\langnp3081\langfenp3081 \sbasedon0 \snext0 heading 1;}{\*\cs10 \additive \ssemihidden Default Paragraph Font;}{\* \ts11\tsrowd\trftsWidthB3\trpaddl108\trpaddr108\trpaddfl3\trpaddft3\trpaddfb3\trpaddfr3\trcbpat1\trcfpat1\tblind0\tblindtype3\tscellwidthfts0\tsvertalt\tsbrdrt\tsbrdrl\tsbrdrb\tsbrdrr\tsbrdrdgl\tsbrdrdgr\tsbrdrh\tsbrdrv \ql \li0\ri0\widctlpar\wrapdefault\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \rtlch\fcs1 \af0\afs20 \ltrch\fcs0 \fs20\lang1024\langfe1024\cgrid\langnp1024\langfenp1024 \snext11 \ssemihidden Normal Table;}} {\*\latentstyles\lsdstimax156\lsdlockeddef0}{\*\rsidtbl \rsid6634106}{\*\generator Microsoft Word 11.0.8134;}{\info{\operator Merlin}{\creatim\yr2007\mo12\dy19\hr6\min32}{\revtim\yr2007\mo12\dy19\hr6\min33}{\version2}{\edmins1}{\nofpages1}{\nofwords4008} {\nofchars22850}{\nofcharsws26805}{\vern24611}{\*\password 00000000}}{\*\xmlnstbl {\xmlns1 http://schemas.microsoft.com/office/word/2003/wordml}{\xmlns2 urn:schemas-microsoft-com:office:smarttags}} \paperw12240\paperh15840\margl1800\margr1800\margt1440\margb1440\gutter0\ltrsect \widowctrl\ftnbj\aenddoc\donotembedsysfont0\donotembedlingdata1\grfdocevents0\validatexml0\showplaceholdtext0\ignoremixedcontent0\saveinvalidxml0\showxmlerrors0\horzdoc\dghspace120\dgvspace120\dghorigin1701\dgvorigin1***4\dghshow0\dgvshow3 \jcompress\viewkind4\viewscale100\rsidroot6634106 \fet0{\*\wgrffmtfilter 013f}\ilfomacatclnup0\ltrpar \sectd \ltrsect\linex0\sectdefaultcl\sftnbj {\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang {\pntxta .}}{\*\pnseclvl2 \pnucltr\pnstart1\pnindent720\pnhang {\pntxta .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang {\pntxta .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang {\pntxta )}}{\*\pnseclvl5\pndec\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}{\*\pnseclvl6 \pnlcltr\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}\pard\plain \ltrpar\ql \li0\ri0\nowidctlpar\wrapdefault\faauto\rin0\lin0\itap0 \rtlch\fcs1 \af0\afs24\alang1025 \ltrch\fcs0 \f1\fs24\lang3081\langfe3081\cgrid\langnp3081\langfenp3081 {\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 README for PCI32.ZIP}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par This is a very quick note to explain PCI32. \par \par PCI32 is just a port of my 16-bit DOS program 'PCI' to "true" win32 - that is, functionality under the 32-bit x86 builds of Windows NT 4.0, 2000, XP, 2003, Longhorn/Vista and so on. This program will NOT work under DOS/WIN9x/ME/OS2/Linux etc, or any ***-b it OS!!! \par \par PCI32 is tested and works under any Microsoft win32 OS e.g. NT4.0, Win2000, XP, 2003, & "Longhorn/Vista", including all server versions and other variants (media centre, SBS server, tablet edition, enterprise edition, etc). I have never tested it under a cluster, but I would expect it to report on the attributes of whatever hardware node it\rquote s actually run on. \par \par The new reader is recommended to read PCI.DOC (Included in the archive) for historical information regarding this software. \par \par 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 a rea that PCI32 proves to be of great use - I quite simply don't have the resources to guarantee it. \par \par 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 function s not relevant in the win32 environment have been removed - pci32 /? lists the functions that work... \par \par Support website:\tab http://members.datafast.net.au/dft0802 \par Email:\tab \tab \tab chart (at) datafast (dot) net (dot) au\tab \tab \tab (Damn Spam!!) \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 How to use it?}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par 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. \par \par General advice for beginners: \par \par }\pard \ltrpar\ql \fi-360\li720\ri0\nowidctlpar\tx720\wrapdefault\faauto\rin0\lin720\itap0 {\rtlch\fcs1 \af3\afs20 \ltrch\fcs0 \f3\fs20\insrsid6634106 \'b7\tab }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 Unzip pci32 to a new folder e.g. C:\\ PCI32. Use winzip or winrar or windows XP\rquote s built-in \'93extract all\'94 command. You should get a bunch of files, including this document. \par }\pard \ltrpar\ql \fi-360\li720\ri0\nowidctlpar\wrapdefault\faauto\rin0\lin720\itap0 {\rtlch\fcs1 \af3\afs20 \ltrch\fcs0 \f3\fs20\insrsid6634106 \'b7\tab }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 Open the command prompt (start \endash run \endash (type in) }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 CMD}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 or start \endash all programs \endash accessories \endash command prompt) and you get a black screen with white text. \par }{\rtlch\fcs1 \af3\afs20 \ltrch\fcs0 \f3\fs20\insrsid6634106 \'b7\tab }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 Type in }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 C:}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par }{\rtlch\fcs1 \af3\afs20 \ltrch\fcs0 \f3\fs20\insrsid6634106 \'b7\tab }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 Type in }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 cd \\pci32}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par }\pard \ltrpar\ql \fi-360\li720\ri0\nowidctlpar\tx720\wrapdefault\faauto\rin0\lin720\itap0 {\rtlch\fcs1 \af3\afs20 \ltrch\fcs0 \f3\fs20\insrsid6634106 \'b7\tab }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 Type in }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 pci32 \par }\pard \ltrpar\ql \fi-360\li720\ri0\nowidctlpar\wrapdefault\faauto\rin0\lin720\itap0 {\rtlch\fcs1 \af3\afs20 \ltrch\fcs0 \f3\fs20\insrsid6634106 \'b7\tab }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 Type in }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 exit}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 to close the black screen, when you\rquote re finished \par }\pard \ltrpar\ql \li0\ri0\nowidctlpar\wrapdefault\faauto\rin0\lin0\itap0 {\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par Your report will probably scroll off the top of the screen. Use the window\rquote s vertical scrollbar slider to go back \'93up\'94 and read from the top, or use the send-to-notepad method as per below: \par \par 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: \par \par PCI32 > report.txt \par notepad report.txt \par \par \'85Which will generate the report and then launch notepad with the results opened. You can then cut/paste/print/email/etc to your hearts content. As a free bonus, the file 'report.txt' is saved for you to come back to in future. Wow :-) \par \par Also, check out the available options. PCI32 /? Will tell you all about lots of other useful functions! \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 If it won't run...}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par - You need at least PCI32.EXE, GWIOPM.SYS and PCIDEVS.TXT present for it to run. If any file is missing, it won't work. \par \par - 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. \par \par - You need to run it from a local disk drive; it will not run from a mapped drive or UNC path, because windows will not allow device drivers which are not located on local drives, to be loaded. \par \par - You must 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. \par \par - PCI32's driver seems to conflict with \'93motherboard monitor\'94 by LiveWireDev.com Remove MBM (and reboot) before using PCI32. MBM is now outdated, unreliable, unsupported software and should be removed anyhow. \par \par - PCI32 is a 32-bit program and will NOT function under any ***-bit version of Windows eg XP-***, server 2003 ***-bit edition, IA*** or A*** or Itanium ***-bit OS'S, nor will it run on plain DOS or 16-bit windows 95/***/ME/3.x or OS/2 (use plain PCI for these systems). \par \par - Always remember that help is available by running pci32 /? You\rquote ll also discover some interesting extra features there. \par \par - 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. \par \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 Updating the PCI database}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par 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 publishe d (on average) about twice a month, or as often as updates are received and processed. \par \par 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. \par \par 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. \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 Your Contributions Are Requested}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par 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: \par \par If you have any information on a PCI device which is not in my databa se, 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. \par \par Contributions from hardware dev elopers 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! L isting 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. \par \par To add an entry to the database, at minimum I need the PCI Vendor ID, D evice 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. \par \par 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 i nside 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! \par \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 A commentary on PCI databases}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par My database 'PCIDEVS.TXT' is the most extensive listing I can find on the web. There are other listings, such as the Linux list (pci.ids) and BSD 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 y ou 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 maintaine d before concluding that another list is better/bigger/more accurate. \par \par 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 t h e 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 me r ges 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 yo u are free to use it AS-IS, you cannot alter it or call it yours. (See the legal section at the end). \par \par 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 a ny 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! \par \par I strongly urge developers to use th e 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 today. All I ask is that you mention thi s 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 sourc e by editing it to remove my name and links. \par \par 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. \par \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 Compiling the program}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par 100% of all source and object code required to recompile yourself is supplied. You don't need anything else besides a copy of {\*\xmlopen\xmlns2{\factoidname place}}Delphi{\*\xmlclose} to recompile yourself. I compile with Borland Delphi 7.0 standard (Delphi 4 works; other versions of {\*\xmlopen\xmlns2{\factoidname place}}Delphi{\*\xmlclose} are untested and may or may not work). Do *NOT* load into {\*\xmlopen\xmlns2{\factoidname place}}Delphi{\*\xmlclose}'s GUI!!! At the command prompt run }{ \rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\ul\insrsid6634106 dcc32 pci32.pas }{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 to compile (Ignore the warnings with gwiopm.pas)! \par \par 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. \par \par \par \par }{\rtlch\fcs1 \ab\af1\afs20 \ltrch\fcs0 \b\fs20\insrsid6634106 Legal mumbo Jumbo}{\rtlch\fcs1 \af1\afs20 \ltrch\fcs0 \fs20\insrsid6634106 \par \par PCI32 is freeware. Use it, it's free. Also, no need to ask before you incorporate this code into commercial software. Credit would be app reciated 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 \endash I\rquote 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 ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：