<?xml version='1.0' encoding='ISO-8859-1'?>
     <rss version='2.0'>
      <channel>
       <title>yaps.lha utility/hardware - Comments</title>
       <link>https://www.os4depot.net/?function=comments&amp;file=utility/hardware/yaps.lha</link>
       <description>Yet Another PCI Scan program</description>
       <language>en-gb</language>
       <lastBuildDate>Sun, 03 May 2026 17:40:04 +0200</lastBuildDate>
       <image>
        <title>OS4Depot.net</title>
        <url>https://www.os4depot.net/images/rss.gif</url>
        <link>https://www.os4depot.net</link>
       </image><item> <title>jtubbs (67.42.75.15) @ 06 Jan 2006, 06:10.07</title> <link>https://www.os4depot.net/?function=comments&amp;file=utility/hardware/yaps.lha</link> <description>&lt;STRONG&gt;By:&lt;/STRONG&gt;&amp;nbsp;jtubbs (67.42.75.15)&lt;BR /&gt;&lt;pre&gt;I am able to duplicate the problem, but it isn't making sense at the moment. The
CHIP: field uses the exact same routine, and works properly if the chip data
cannot be found.  It doesn't seem to be a problem with the data file being
corrupted. The problem is typical with an unitialized variable.  
&lt;/pre&gt;</description> <guid isPermaLink='false'>1136567407</guid> <pubDate>Fri, 06 Jan 2006 18:10:07 +0100</pubDate></item><item> <title>Capehill (82.128.189.249) @ 06 Jan 2006, 04:00.44</title> <link>https://www.os4depot.net/?function=comments&amp;file=utility/hardware/yaps.lha</link> <description>&lt;STRONG&gt;By:&lt;/STRONG&gt;&amp;nbsp;Capehill (82.128.189.249)&lt;BR /&gt;&lt;pre&gt;If the ID is corrupted, maybe description is too. There is very little the
author could do to validate a string if there are no checksums offered.
&lt;/pre&gt;</description> <guid isPermaLink='false'>1136559644</guid> <pubDate>Fri, 06 Jan 2006 16:00:44 +0100</pubDate></item><item> <title>STRICQ (65.191.33.56) @ 02 Jan 2006, 11:17.48</title> <link>https://www.os4depot.net/?function=comments&amp;file=utility/hardware/yaps.lha</link> <description>&lt;STRONG&gt;By:&lt;/STRONG&gt;&amp;nbsp;STRICQ (65.191.33.56)&lt;BR /&gt;&lt;pre&gt;YAPS outputs garbage if the DESCRIPTION string cannot be found:

00:06.0 3Com Corporation, VendorID: 0x0010b7
DeviceID: 0x00ffff
CHIP: Unknown, DESCRIPTION:
&amp;aring;&amp;lt;R@&amp;quot;&amp;aring;&amp;lt;&amp;Uacute;&amp;quot;&amp;aring;8
&amp;Ograve;

Yes, the 0xFFFF is correctly wrong.  It was damaged in a lightening strike that
traveled over my ethernet wiring.
&lt;/pre&gt;</description> <guid isPermaLink='false'>1136240268</guid> <pubDate>Mon, 02 Jan 2006 23:17:48 +0100</pubDate></item></channel> </rss>