<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://cs.thefoleyhouse.co.uk/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search Results matching tag 'Hardware and Drivers'</title><link>http://cs.thefoleyhouse.co.uk/search/SearchResults.aspx?o=DateDescending&amp;tag=Hardware+and+Drivers&amp;orTags=0</link><description>Search Results matching tag 'Hardware and Drivers'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator><item><title>Windows 7 on an HP DV9000 (DV9292EU)</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2009/11/15/windows-7-on-an-hp-dv9000-dv9292eu.aspx</link><pubDate>Sun, 15 Nov 2009 21:30:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:1512</guid><dc:creator>Karl</dc:creator><description>&lt;P&gt;I've been having a bit of an install fest this weekend with Windows 7 Ultimate on my HP DV9292EU, Windows 7 Enterprise on my Work laptop and Android (!) on my trusty ASUS eeePC 701. All went fine except the HP laptop which had three unknown devices in device manager after the install.&lt;/P&gt;
&lt;P&gt;One was labeled as a co-processor. I don't know what it was, but downloading the NVidia Nforce 430 drivers from here solved it:&lt;BR&gt;&lt;A href="http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk"&gt;http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Select Legacy, NForce 4 and then one of the 430 drivers. It downloaded this file which worked for me:&lt;BR&gt;15.49_nforce_winvista_win7_32bit_international_whql.exe&lt;/P&gt;
&lt;P&gt;The two other device were labeled &lt;STRONG&gt;Base System Devices&lt;/STRONG&gt; and proved to be some sort of Ricoh devices.&lt;BR&gt;Downloading the Windows 7 drivers from the Lenovo site fixed these for me!&lt;BR&gt;&lt;A href="http://www-307.ibm.com/pc/support/site.wss/WIN7-BETA.html#rmcr"&gt;http://www-307.ibm.com/pc/support/site.wss/WIN7-BETA.html#rmcr&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;It now all looks good!&lt;/P&gt;</description></item><item><title>D-Link DCS-6620G - HTTP 400 Bad Request</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2008/09/27/d-link-dcs-6620g-http-400-bad-request.aspx</link><pubDate>Sat, 27 Sep 2008 15:59:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:1069</guid><dc:creator>Karl</dc:creator><description>&lt;P&gt;After the install of Silverlight - My D-Link DCS-6620G camera started returning HTTP 400&amp;nbsp;Bad Request&amp;nbsp;errors.&lt;BR&gt;After a bit of investigation, I found this:&lt;BR&gt;&lt;A href="http://silverlight.net/forums/p/7452/77779.aspx"&gt;http://silverlight.net/forums/p/7452/77779.aspx&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Locating the key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Accepted Documents, I removed a couple of XML document type I figured that I would never use.&lt;/P&gt;
&lt;P&gt;Everything now works fine.&lt;/P&gt;&lt;FONT size=2&gt;&lt;/FONT&gt;</description></item><item><title>VMWare Server v1.0.3 unable to bridge to wireless network on Vista</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2007/07/18/vmware-server-v1-0-3-unable-to-bridge-to-wireless-network-on-vista.aspx</link><pubDate>Wed, 18 Jul 2007 12:34:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:791</guid><dc:creator>Karl</dc:creator><description>&lt;P&gt;I've been trying to&amp;nbsp;test some printing configurations on SLES 10 SP1 but I couldn't get my laptop running Windows Vista Ultimate and VMWare Server v1.0.3 to successfully bridge onto the wireless adaptor.&lt;/P&gt;
&lt;P&gt;I could use NAT but then it was difficult to test connectivity to the server.&lt;/P&gt;
&lt;P&gt;Having hunted around a bit I found this useful post: &lt;A class="" href="http://www.abstractpath.com/weblog/2007/06/vmware-wireless-network-adapter-and.html" target=_blank&gt;Abstract path:VMWare, Wireless Network Adapter and Bridging&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This pointed to a &lt;A class="" href="http://kb.vmware.com/selfservice/dynamickc.do?cmd=show&amp;amp;forward=nonthreadedKC&amp;amp;docType=kc&amp;amp;externalId=1212&amp;amp;sliceId=2&amp;amp;stateId=009345265" target=_blank&gt;VMWare article&lt;/A&gt; which allows the Vista adaptor bridging feature to be enabled between the onboard wireless card and the virtual adaptor created by VMware.&lt;BR&gt;&lt;/P&gt;
&lt;P&gt;Before this fix I could only contact the host wireless IP address, now I can connect to everything but! If anyone knows how to get the VMWare native bridging feature to work, please get in touch.&lt;/P&gt;
&lt;P&gt;N.B. The only step missing from the above articles was that you must create a VMware virtual adaptor (I used adapator #2) and delete the DHCP scope for it. Fail to do the and you will leak DHCP onto your wireless network!&lt;/P&gt;</description></item><item><title>Linux NIC Bonding</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2006/11/29/linux-nic-bonding.aspx</link><pubDate>Wed, 29 Nov 2006 14:38:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:743</guid><dc:creator>Karl</dc:creator><description>&lt;P&gt;I had a query on how to setup NIC bonding in RHEL4 so thought I would document it for the blog.&lt;/P&gt;
&lt;P&gt;I'll start with a standard server with 2 NICs, eth0 and eth1. Here is the output from 'ifconfig':&lt;BR&gt;&lt;IMG style="WIDTH:720px;HEIGHT:400px;" height=400 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/740/original.aspx" width=720&gt;&lt;/P&gt;
&lt;P&gt;The configuration scripts are found in /etc/sysconfig/network/network/scripts:&lt;BR&gt;&lt;IMG style="WIDTH:466px;HEIGHT:47px;" height=47 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/742/original.aspx" width=466&gt;&lt;/P&gt;
&lt;P&gt;eth0 is a static interface configured in /etc/sysconfig/network/network-scripts/ifcfg-eth0:&lt;BR&gt;&lt;IMG style="WIDTH:483px;HEIGHT:133px;" height=133 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/738/original.aspx" width=483&gt;&lt;/P&gt;
&lt;P&gt;eth1 is a static interface configured in /etc/sysconfig/network/network-scripts/ifcfg-eth1&lt;IMG style="WIDTH:480px;HEIGHT:131px;" height=131 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/739/original.aspx" width=480&gt;&lt;/P&gt;
&lt;P&gt;The hardware is configured in /etc/modprobe.conf:&lt;BR&gt;&lt;IMG style="WIDTH:649px;HEIGHT:197px;" height=197 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/741/original.aspx" width=649&gt;&lt;/P&gt;
&lt;P&gt;First we add a config file for bond0, /etc/sysconfig/network/network-scripts/ifcfg-bond0:&lt;BR&gt;&lt;IMG style="WIDTH:197px;HEIGHT:131px;" height=131 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/729/original.aspx" width=197&gt;&lt;/P&gt;
&lt;P&gt;Now we edit /etc/sysconfig/network/network-scripts/ifcfg-eth0:&lt;BR&gt;&lt;IMG style="WIDTH:481px;HEIGHT:117px;" height=117 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/730/original.aspx" width=481&gt;&lt;/P&gt;
&lt;P&gt;Now we edit /etc/sysconfig/network/network-scripts/ifcfg-eth1:&lt;BR&gt;&lt;IMG style="WIDTH:481px;HEIGHT:118px;" height=118 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/731/original.aspx" width=481&gt;&lt;/P&gt;
&lt;P&gt;Network scripts are now complete in /etc/sysconfig/network/network-scripts:&lt;BR&gt;&lt;IMG style="WIDTH:478px;HEIGHT:65px;" height=65 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/734/original.aspx" width=478&gt;&lt;/P&gt;
&lt;P&gt;Add the bonding driver to /etc/modprobe.conf:&lt;BR&gt;&lt;IMG style="WIDTH:650px;HEIGHT:213px;" height=213 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/733/original.aspx" width=650&gt;&lt;/P&gt;
&lt;P&gt;Shut down the network with 'service network stop'&lt;/P&gt;
&lt;P&gt;Insert the bonding driver with 'modprobe bonding -o bond0 miimon=100 mode=1'&lt;/P&gt;
&lt;P&gt;Start the network with 'service network start':&lt;BR&gt;&lt;IMG style="WIDTH:719px;HEIGHT:128px;" height=128 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/735/original.aspx" width=719&gt;&lt;/P&gt;
&lt;P&gt;Check the interfaces with 'ifconfig':&lt;BR&gt;&lt;IMG style="WIDTH:720px;HEIGHT:400px;" height=400 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/732/original.aspx" width=720&gt;&lt;/P&gt;
&lt;P&gt;Check the routing is ok with 'route -n':&lt;BR&gt;&lt;IMG style="WIDTH:719px;HEIGHT:80px;" height=80 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/737/original.aspx" width=719&gt;&lt;/P&gt;
&lt;P&gt;View the&amp;nbsp;status with 'cat /proc/net/bonding/bond0':&lt;BR&gt;&lt;IMG style="WIDTH:491px;HEIGHT:309px;" height=309 src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/736/original.aspx" width=491&gt;&lt;BR&gt;&lt;/P&gt;</description></item><item><title>Disgusting Keyboard</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2006/09/20/Disgusting-Keyboard.aspx</link><pubDate>Wed, 20 Sep 2006 19:10:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:616</guid><dc:creator>Karl</dc:creator><description>&lt;p&gt;When my keyboard has got really bad in the past I just bought a new one.&amp;nbsp; Today I decided to clean it:&lt;/p&gt;&lt;p&gt;After I took all the keys off&lt;br /&gt;&lt;a href="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/613/original.aspx" title="Ewwww!" target="_blank"&gt;&lt;img alt="Ewwww!" height="239" src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/613/500x239.aspx" style="width:500px;height:239px;" title="Ewwww!" width="500" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;After I cleaned it&lt;br /&gt;&lt;a href="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/614/original.aspx" title="Cleaner..." target="_blank"&gt;&lt;img alt="Better" height="242" src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/614/500x242.aspx" style="width:500px;height:242px;" title="Better" width="500" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;All back together again&lt;br /&gt;&lt;a href="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/615/original.aspx" title="That&amp;#39;s better!" target="_blank"&gt;&lt;img alt="That&amp;#39;s better!" height="242" src="http://cs.thefoleyhouse.co.uk/photos/karls_pictures/images/615/500x242.aspx" style="width:500px;height:242px;" title="That&amp;#39;s better!" width="500" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>XGL on Dell Inspiron 5100 with SUSE 10.1</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2006/07/01/607.aspx</link><pubDate>Sat, 01 Jul 2006 09:58:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:607</guid><dc:creator>Karl</dc:creator><description>&lt;P&gt;This documents my attempt to install XGL on my Dell Inspiron 5100 laptop using Suse 10.1. I first tested it with the &lt;A href="http://kororaa.org/static.php?page=static060318-181203"&gt;Kororaa Xgl Live CD&lt;/A&gt; so I knew that it would work. I had some problems with the login screen (seen this reported elsewhere - but I don't have it with SUSE 10.1) but overall it worked well. The following procedure works for me!&lt;/P&gt;First a bit on hardware:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;Dell Inspiron 5100 
&lt;LI&gt;Radeon 7500 Mobility with 32 MB Video RAM 
&lt;LI&gt;Using Xorg "radeon" driver with 3d dri enabled&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;I mainly followed the procedure on Opensuse.org &lt;A href="http://en.opensuse.org/Using_Xgl_on_SUSE_Linux"&gt;here&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;Download the following RPMs from &lt;A href="http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/"&gt;Suse factory i586&lt;/A&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/libwnck-2.12.2-33.i586.rpm"&gt;compiz&lt;/A&gt; 
&lt;LI&gt;&lt;A href="http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/libwnck-2.12.2-33.i586.rpm"&gt;xgl&lt;/A&gt; 
&lt;LI&gt;&lt;A href="http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/libwnck-2.12.2-33.i586.rpm"&gt;libwnck&lt;/A&gt; &lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Download the following RPM from &lt;A href="http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/noarch/"&gt;Suse factory noarch&lt;/A&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;A href="http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/noarch/xgl-hardware-list-060526-4.noarch.rpm"&gt;xgl-hardware-list&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Install the RPMs. I had a dependency issue when I tried this:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;error: Failed dependencies: libpng12.so.0(PNG12_0) is needed by compiz-cvs_060621-2.i586&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;I used --nodeps and it installed with no apparent side ill effects. There is a libpng12.so.0 in /usr/lib provided from libpng-1.2.8-17 so I am not sure why I got the error.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Make sure that you have enabled 3d acceleration from YaST:&lt;/P&gt;
&lt;P&gt;&lt;IMG height=420 src="http://www.thefoleyhouse.co.uk/files/xgl/3daccel.png" width=539 border=0&gt;&lt;/P&gt;&lt;BR&gt;
&lt;P&gt;Activate the desktop effects from the Gnome Control centre:&lt;/P&gt;
&lt;P&gt;&lt;IMG height=117 src="http://www.thefoleyhouse.co.uk/files/xgl/xglcc.png" width=117 border=0&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It didn't work for me first time because it said 3D acceleration enabled although it was. I saw this:&lt;/P&gt;
&lt;P&gt;&lt;IMG height=419 src="http://www.thefoleyhouse.co.uk/files/xgl/no3d.png" width=333 border=0&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I checked the status with glxinfo I got this so I know it's working:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;name of display: :0.0&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;display: :0 screen: 0&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;direct rendering: Yes&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;BR&gt;
&lt;P&gt;After a bit of research I found the XGL control applet sometimes does not identify that 3d acceleration is enable and that if you hold shift and double click on “3D Acceleration: Disabled” then you can force it to on:&lt;/P&gt;
&lt;P&gt;&lt;IMG height=344 src="http://www.thefoleyhouse.co.uk/files/xgl/3don.png" width=273 border=0&gt;&lt;/P&gt;&lt;BR&gt;
&lt;P&gt;You can now click on “Enable Desktop Effects” and you now have XGL!&lt;/P&gt;
&lt;P&gt;The only problems I have are:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;I occasionally get lines or corrupted pixels on screen. A quick spin of the cube (CTRL+ALT+ARROW) sorts these out quickly.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;Windows have pink lines around them after restoring from hibernation. I have to restart the X server to sort these out.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;The display does not handle full screen dvd video very well. Either use a hardware player (!) or turn of desktop effects to be able to play video at any decent speed.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description></item><item><title>SUSE 10.1 Wireless on Dell Inspiron 5100</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2006/06/24/605.aspx</link><pubDate>Sat, 24 Jun 2006 07:19:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:605</guid><dc:creator>Karl</dc:creator><description>As always I had to use ndiswrapper to get my wireless working but this time was the easiest ever.&amp;nbsp; I followed the following proceedure:&lt;br&gt;&lt;ol&gt;&lt;li&gt;Downloaded the latest drivers for my minipci from &lt;a href="http://support.euro.dell.com/support/downloads/format.aspx?c=uk&amp;amp;cs=ukdhs1&amp;amp;l=en&amp;amp;s=dhs&amp;amp;SystemID=INS_PNT_P4_5100&amp;amp;os=WW1&amp;amp;osl=en&amp;amp;deviceid=4394&amp;amp;libid=5&amp;amp;typecnt=2&amp;amp;vercnt=19&amp;amp;releaseid=R115320"&gt;here&lt;/a&gt;.&amp;nbsp; Bear in mind that I am in the UK so these are the non US/Japan drivers.&amp;nbsp; Click &lt;a href="http://support.euro.dell.com/support/downloads/previousversions.aspx?c=uk&amp;amp;cs=ukdhs1&amp;amp;l=en&amp;amp;s=dhs&amp;amp;deviceid=4394&amp;amp;SystemID=INS_PNT_P4_5100&amp;amp;osl=en&amp;amp;os=WW1&amp;amp;releasetype=DRVR&amp;amp;vercnt=19&amp;amp;typecnt=2&amp;amp;libid=5"&gt;here&lt;/a&gt; if you want the US or Japanese drivers. (If you don't want to download the 48MB packages you can find the UK bcmwl5.inf and bcmwl5.sys as a download &lt;a href="http://www.thefoleyhouse.co.uk/files/suse101ndiswrapper/bcmwl5.tgz"&gt;here&lt;/a&gt;.)&lt;br&gt;&lt;/li&gt;&lt;li&gt;Used Yast to install ndiswrapper.&amp;nbsp; It seems that Novell have split the drivers into tools&amp;amp;docs in one package and kernel modules in another.&amp;nbsp; I selected ndiswrapper-1.10-19 in Yast and it auto selected&amp;nbsp; ndiswrapper-kmp-default-1.10_2.6.16.13_4-19 for my Kernel.&lt;/li&gt;&lt;li&gt;Followed the instructions I found in /usr/share/doc/packages/ndiswrapper/README.SUSE. (Copy &lt;a href="http://www.thefoleyhouse.co.uk/files/suse101ndiswrapper/README.SUSE"&gt;here&lt;/a&gt;.)&lt;/li&gt;&lt;li&gt;The only thing that didn't work was the WEP key instructions.&amp;nbsp; Because I elected to use the new user mode network control I had to use the&amp;nbsp; Network applet to join the wireless network.
&lt;p align="center"&gt;&lt;img id="yeehaa" src="http://www.thefoleyhouse.co.uk/files/suse101ndiswrapper/yeehha.png" alt="Yeehaa!"&gt;&lt;/p&gt;
&lt;/li&gt;&lt;/ol&gt;</description></item><item><title>PC line PCL-RP100 Rumble Game Pad</title><link>http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2006/04/13/pc-line-pcl-rp100-rumble-game-pad.aspx</link><pubDate>Thu, 13 Apr 2006 09:40:00 GMT</pubDate><guid isPermaLink="false">72ff1f2b-f56d-431e-a40a-3b65004deded:597</guid><dc:creator>Karl</dc:creator><description>&lt;P&gt;I always like to install the latest drivers but when buying OEM hardware it proves difficult to track down the drivers.&lt;BR&gt;&lt;BR&gt;For this particular device it proved to be a company called &lt;A href="http://www.ruling.com.sg/"&gt;Ruling Technologies&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;I am also informed by Glen that:&lt;/P&gt;
&lt;P class=MsoPlainText style="MARGIN:0cm 0cm 0pt;"&gt;&lt;A href="http://www.rockfire.com.tw/"&gt;&lt;FONT face=Consolas size=3&gt;&lt;EM&gt;http://www.rockfire.com.tw/&lt;/EM&gt;&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;&lt;A href="http://www.rockfire.com.tw/"&gt;&lt;FONT face=Consolas size=3&gt;&lt;/A&gt;&lt;/FONT&gt;
&lt;P&gt;&lt;FONT face=Consolas size=3&gt;&lt;EM&gt;Is the manufacturer, drivers are by Padix (same company)&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Consolas size=3&gt;&lt;EM&gt;Work fine with XP but not with Vista&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoPlainText style="MARGIN:0cm 0cm 0pt;"&gt;&lt;FONT face=Consolas size=3&gt;&lt;EM&gt;Enjoy :-)&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description></item></channel></rss>