<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SetPoint Install Issue in Keyboards - Bluetooth</title>
    <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/210094#M6317</link>
    <description>It's not unfourtunate, it's an AUTROCITY! Using generic support means loosing key functionality you paid for.&lt;br&gt;&lt;br&gt;Now if Logitech would just release the source code for these dead drivers &amp;amp; support softwares GPL maybe someone else could fix them amazingly FOR FREE. They're in good company like Kensington who bought &amp;amp; killed the great Advanced Gravis name leaving us with buggy drivers, no support, and refusal to release the source code even though it's a dead division!&lt;br&gt;&lt;br&gt;Message Edited by dinovosux on &lt;span class="date_text"&gt;04-29-2008&lt;/span&gt; &lt;span class="time_text"&gt;12:41 AM&lt;/span&gt;&lt;br&gt;&lt;br&gt;Message Edited by Pegasus on &lt;span class=date_text&gt;05-01-2008&lt;/span&gt; &lt;span class=time_text&gt;05:04 PM&lt;/span&gt;</description>
    <pubDate>Fri, 02 May 2008 00:04:50 GMT</pubDate>
    <dc:creator>dinovosux</dc:creator>
    <dc:date>2008-05-02T00:04:50Z</dc:date>
    <item>
      <title>SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/66#M7</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;&#xD;
&lt;DIV&gt;&lt;/DIV&gt;Okay, I've simply had ENOUGH of Logitech's products.&lt;BR&gt;&lt;BR&gt;I am the owner of the MX5000 keyboard/mouse, and have learnt to live with the issues it has.&lt;BR&gt;&lt;BR&gt;I went out of town for 4 days, and returned today. Turned on my computer, and everything is working fine. Setpoint auto-upgrade pops up, saying it has new software to download. So like most software, I click okay, and let it download the huge download. It installs the software, and asks to restart my computer, sure, I let it do its thing.&lt;BR&gt;&lt;BR&gt;Thing is my computer doesn't restart properly. On restart, I get a BSOD. Thing is, the BSOD only lasts about 1 sec, then the computer restarts again (can't even read what the BSOD says). I should say, this is the FIRST time ever I have seen a BSOD with winxp sp2.&lt;BR&gt;&lt;BR&gt;Okay, no problem F8 and try to load in Safe mode. No luck, BSOD.&lt;BR&gt;&lt;BR&gt;What kind of&amp;nbsp;stuff is logitech letting out there? Wth am I suppose to do now? Reinstall windows. I think not. Logitech support is going to get a NASTY call from me in the morning. I have tons of work to do, and can't afford to be fixing my computer.&#xD;
&lt;P&gt;Message Edited by Rich on &lt;SPAN class=date_text&gt;05-23-2006&lt;/SPAN&gt; &lt;SPAN class=time_text&gt;10:52 AM&lt;/SPAN&gt;&lt;/P&gt;&lt;p&gt;Message Edited by Jon on &lt;span class=date_text&gt;05-23-2006&lt;/span&gt; &lt;span class=time_text&gt;11:39 AM&lt;/span&gt;</description>
      <pubDate>Tue, 23 May 2006 06:24:32 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/66#M7</guid>
      <dc:creator>Gujustud</dc:creator>
      <dc:date>2006-05-23T06:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/82#M9</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;So I spent an hour today farting around, trying to get my computer going with no luck (and coming into work late today to boot).&lt;BR&gt;&lt;BR&gt;I tried all options for safe boot, etc, but no luck. Here's what I do know:&lt;BR&gt;&lt;BR&gt;The system is freezing up on MUP.sys, which then causes the BSOD, which I finally was able to read all of:&lt;BR&gt;&lt;BR&gt;Stop: C000021a {Fatal System Error}&lt;BR&gt;&lt;BR&gt;The Windows Logon Process system process terminated unexpectedly with a status of 0xC0000139 (0x00000000 0x00000000).&lt;BR&gt;&lt;BR&gt;The system has been shut down.&lt;p&gt;Message Edited by Jon on &lt;span class=date_text&gt;05-23-2006&lt;/span&gt; &lt;span class=time_text&gt;11:40 AM&lt;/span&gt;</description>
      <pubDate>Tue, 23 May 2006 16:41:42 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/82#M9</guid>
      <dc:creator>Gujustud</dc:creator>
      <dc:date>2006-05-23T16:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/89#M10</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;&#xD;
&lt;DIV&gt;&lt;/DIV&gt;&#xD;
&lt;P&gt;Gujustud,&lt;/P&gt;&#xD;
&lt;P&gt;I understand your frustration, but please try to keep the language clean when you post. Profanity will not be tolerated on the boards. &lt;/P&gt;&#xD;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&#xD;
&lt;P&gt;Thank you,&lt;/P&gt;&#xD;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&#xD;
&lt;P&gt;Rich&lt;/P&gt;&lt;p&gt;Message Edited by Jon on &lt;span class=date_text&gt;05-23-2006&lt;/span&gt; &lt;span class=time_text&gt;11:40 AM&lt;/span&gt;</description>
      <pubDate>Tue, 23 May 2006 17:54:04 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/89#M10</guid>
      <dc:creator>Rich</dc:creator>
      <dc:date>2006-05-23T17:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Upgrade Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/93#M11</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;&#xD;
&lt;P&gt;Please contact Logitech's telephone technical support to get assistance with this issue. The number is 702-269-3457.&lt;/P&gt;&#xD;
&lt;P&gt;Regards,&lt;/P&gt;&#xD;
&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2006 18:37:00 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/93#M11</guid>
      <dc:creator>Jon</dc:creator>
      <dc:date>2006-05-23T18:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Upgrade Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/141#M17</link>
      <description>If you still are having problems then I might have a solution for you.&lt;br&gt;&lt;br&gt;If you have an empty pci slot open, purchase a cheap usb pci card and install the bluetooth adapter on it then try booting up. This should help with your BSODs because instead of running on the chipsets resources it will be running off of the pci bus.</description>
      <pubDate>Wed, 24 May 2006 08:11:39 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/141#M17</guid>
      <dc:creator>InnerVision</dc:creator>
      <dc:date>2006-05-24T08:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Upgrade Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/189#M22</link>
      <description>Did I really use profanity? 'sigh'&lt;br&gt;&lt;br&gt;Still no luck with the BSOD. I upgraded my BIOS as well, with no luck.&lt;br&gt;&lt;br&gt;I've tried loading my computer with a old ps/2 mouse/keyboard, and I still have the same issue, so I doubt it has anything to do with the bluetooth adapter.</description>
      <pubDate>Wed, 24 May 2006 19:17:00 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/189#M22</guid>
      <dc:creator>Gujustud</dc:creator>
      <dc:date>2006-05-24T19:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Upgrade Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/719#M44</link>
      <description>So I called Logitech, and just as I suspected, they told me &amp;quot;We can't help you because you can't get into windows. Please call Microsoft and once you can get into windows, we'll help you uninstall setpoint&amp;quot;.&lt;br&gt;&lt;br&gt;Seriously?&lt;br&gt;&lt;br&gt;So I didn't bother to waste my time, and I just formated/reinstalled windows, and we're back up and running. The funny thing I thought i'd see if I can download any old versions of setpoint, and it seems as though the NEW version is now taken off from their website.&lt;br&gt;&lt;br&gt;Great work!</description>
      <pubDate>Tue, 30 May 2006 06:45:21 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/719#M44</guid>
      <dc:creator>Gujustud</dc:creator>
      <dc:date>2006-05-30T06:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Upgrade Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/1600#M98</link>
      <description>I experienced this same exact issue with the same hardware and update. I let my system download the update yesterday but chose not to reboot, knowing that I'd be shutting down just a bit after. I powered on my system tonight when I got home from work and bluescreen.. tried various safemode options to no avail.&lt;br&gt;&lt;br&gt;I think this will be the last Logitech product I buy for a while..&lt;br&gt;&lt;br&gt;Logitech, I hope you do something about this. I'm having to reinstall my system because of your quality software.</description>
      <pubDate>Tue, 06 Jun 2006 03:46:14 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/1600#M98</guid>
      <dc:creator>Sememmon</dc:creator>
      <dc:date>2006-06-06T03:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/1917#M145</link>
      <description>&lt;div&gt;&lt;/div&gt;&lt;p&gt;&lt;span&gt;Gujustud,&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&lt;/font&gt;&lt;/font&gt; &lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;Is your computer on a network using connecting to any other client machines other than MS (Novell for one). If not, then the mup.sys &amp;quot;Multiple UNC provider service&amp;quot; basically a redirector for connecting to other servers on the network is essentially not needed.&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&lt;/font&gt;&lt;/font&gt; &lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;Since you cannot boot into Windows renaming mup.sys to mup.old (in the C:Windows\system32\drivers) is not possible. Your only other solution is to boot into the Recovery console: see instructions below&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&lt;/font&gt;&lt;/font&gt; &lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;1) Boot from the Windows XP cd-rom&lt;br&gt;2) When the first options window appears type &amp;quot;r&amp;quot; to enter recovery console&lt;br&gt;3) Select your windows XP (usually option 1) when prompted&lt;br&gt;4) Enter the Administator's password&lt;br&gt;5) On the command line type &amp;quot;disable mup.sys&amp;quot;&lt;br&gt;6) Then when finished, type &amp;quot;exit&amp;quot; to restart the computer.&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&lt;/font&gt;&lt;/font&gt; &lt;/p&gt;&lt;p&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&lt;/font&gt;&lt;/font&gt; &lt;/p&gt;&lt;p&gt;&lt;font size="3" face="Times New Roman"&gt;Hope this helps&lt;/font&gt;&lt;/p&gt;&lt;p&gt;&lt;font size="3" face="Times New Roman"&gt;GreenBug&lt;/font&gt;&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;Message Edited by GreenBug on &lt;span class="date_text"&gt;06-07-2006&lt;/span&gt;&lt;span class="time_text"&gt;06:40 PM&lt;/span&gt;&lt;/p&gt;&lt;p&gt;Message Edited by GreenBug on &lt;span class="date_text"&gt;06-07-2006&lt;/span&gt;&lt;span class="time_text"&gt;06:40 PM&lt;/span&gt;&lt;/p&gt;</description>
      <pubDate>Thu, 08 Jun 2006 01:33:57 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/1917#M145</guid>
      <dc:creator>GreenBug</dc:creator>
      <dc:date>2006-06-08T01:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/3481#M250</link>
      <description>Gee Rich, and not even a suggestion to help him? Typical, and the post that follows from Jon even more typical. The end result, so typical it's ludacris!!!&lt;br&gt;&lt;br&gt;After trying to understand why I could not load the new BT stack, I gave up and installed everything to go back to 2.22. Well the minute I reboot I was offered an auto-update from 2.22BT to 2.6BT when it evidently should have been the non-BT version, hosed my system so bad to go to backups. The answer? It was a fskup in the posted update!! 2 days lost on a $200 pile of poo and lax quality control, no surprise there.&lt;br&gt;&lt;br&gt;You guys are raking in the dough, do a 2:1 stock split yet you are putting crap unlike the quality of years passed???? It's amazing what the consumer will buy!&lt;p&gt;Message Edited by dinovosux on &lt;span class="date_text"&gt;06-19-2006&lt;/span&gt;&lt;span class="time_text"&gt;07:16 AM&lt;/span&gt;&lt;/p&gt;&lt;p&gt;Message Edited by dinovosux on &lt;span class="date_text"&gt;06-19-2006&lt;/span&gt;&lt;span class="time_text"&gt;07:22 AM&lt;/span&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 19 Jun 2006 14:13:53 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/3481#M250</guid>
      <dc:creator>dinovosux</dc:creator>
      <dc:date>2006-06-19T14:13:53Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/4331#M295</link>
      <description>I'm having this same exact problem, but I really don't want to reinstall XP as I was just recovering from the last time I had to reformat when I got this error, now at least I know whats causing it. I tried renaming mup.sys to mup.old, as I have access to the hard drive with XP installed on it through Windows Vista Beta 2. Renaming that file did not work, I still cannot get into XP.&lt;br&gt;&lt;br&gt;Anymore ideas/suggestions?&lt;br&gt;&lt;br&gt;*Windows Vista was installed before this problem and its on a separate hard drive, no dual boot.</description>
      <pubDate>Sat, 24 Jun 2006 06:10:41 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/4331#M295</guid>
      <dc:creator>jdrom17</dc:creator>
      <dc:date>2006-06-24T06:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/5489#M326</link>
      <description>I have just experienced that exact same issue. Auto update, and boom this error. Unbeleivable. Formatting is not an option for me and repair installs are not helping. I was so unhappy with this stupid MX keyboard to begin with, but this is pretty rediculous. How does this slip through testing? I will be monitoring forums for any advice to work around this. I dont have access to the HD, and I am stumped.</description>
      <pubDate>Sat, 01 Jul 2006 19:02:43 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/5489#M326</guid>
      <dc:creator>toddiscool</dc:creator>
      <dc:date>2006-07-01T19:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/6134#M354</link>
      <description>Yeah it really is annoying isn't it. I ended up just reformatting as nothing seemed to work. Sorry but I think you're going to have to reformat and maybe get a new keyboard and mouse while your at it, or just don't update SetPoint, better yet don't install it at all.&lt;br&gt;&lt;br&gt;You could download a distribution of Linux that boots and runs from CD only which would give you access to your hard drive, hopefully allowing you to backup your files.&lt;br&gt;&lt;br&gt;I'd still like to know how such an update for SetPoint got through development and released to the public with such a bug. Obviously someone is at fault at Logitech for releasing such poor software. A formal appolgy or something would be nice to see from Logitech for the inconvience they've caused to quite a few people on here and probably many more who don't bother posting here and just reformat or take their computer into a shop and pay someone to do so.&lt;br&gt;&lt;br&gt;I'm going to try install SetPoint 2.60 build 606, this time with a full hard drive image incase anything is to happen I can easily be back to before installation of this software.</description>
      <pubDate>Thu, 06 Jul 2006 03:10:03 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/6134#M354</guid>
      <dc:creator>jdrom17</dc:creator>
      <dc:date>2006-07-06T03:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Upgrade Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/26059#M1275</link>
      <description>Just figured I'd post a followup to this... I had an issue tonight where my system BSOD'd (an unrelated nvidia issue) and upon reboot I lost connectivity to my mx5000. I figured, &amp;quot;Hey, maybe the latest drivers are good now.&amp;quot; Installed them.. silly me, now I can't boot in to XP again.&lt;br&gt;&lt;br&gt;Fool me once, shame on me.. fool me twice..? MX5000 goes in the garbage.&lt;br&gt;&lt;br&gt;Logitech, this is the 2nd time I'll have to reinstall windows because of your drivers. I don't know what it is they're doing, but this is ridiculous. I won't be buying any more Logitech products after this.. and you can bet I'll be recommending my friends do the same.</description>
      <pubDate>Fri, 20 Oct 2006 08:25:27 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/26059#M1275</guid>
      <dc:creator>Sememmon</dc:creator>
      <dc:date>2006-10-20T08:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/194382#M5983</link>
      <description>Just a note for all, when getting a BSOD on boot up, at least in windows XP, remove the logitech hardware from your system before booting your system again. Their is obviously an issue with the logitech drivers and this will resolve the problem by not using them during system boot. Once the system has booted it is safe to connect the hardware again. At that time remove the logitech software as it is useless anyways, this should relieve your issues permanently. This worked for my MX revolution mouse and I can not see why it would not work for any other driver defective hardware. It's unfortunate that it has to come to this&lt;br&gt;&lt;br&gt;Message Edited by Turcogj on &lt;span class="date_text"&gt;03-08-2008&lt;/span&gt; &lt;span class="time_text"&gt;02:14 PM&lt;/span&gt;&lt;br&gt;&lt;br&gt;Message Edited by Pegasus on &lt;span class=date_text&gt;03-23-2008&lt;/span&gt; &lt;span class=time_text&gt;08:58 PM&lt;/span&gt;</description>
      <pubDate>Mon, 24 Mar 2008 03:58:32 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/194382#M5983</guid>
      <dc:creator>Turcogj</dc:creator>
      <dc:date>2008-03-24T03:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/210094#M6317</link>
      <description>It's not unfourtunate, it's an AUTROCITY! Using generic support means loosing key functionality you paid for.&lt;br&gt;&lt;br&gt;Now if Logitech would just release the source code for these dead drivers &amp;amp; support softwares GPL maybe someone else could fix them amazingly FOR FREE. They're in good company like Kensington who bought &amp;amp; killed the great Advanced Gravis name leaving us with buggy drivers, no support, and refusal to release the source code even though it's a dead division!&lt;br&gt;&lt;br&gt;Message Edited by dinovosux on &lt;span class="date_text"&gt;04-29-2008&lt;/span&gt; &lt;span class="time_text"&gt;12:41 AM&lt;/span&gt;&lt;br&gt;&lt;br&gt;Message Edited by Pegasus on &lt;span class=date_text&gt;05-01-2008&lt;/span&gt; &lt;span class=time_text&gt;05:04 PM&lt;/span&gt;</description>
      <pubDate>Fri, 02 May 2008 00:04:50 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/210094#M6317</guid>
      <dc:creator>dinovosux</dc:creator>
      <dc:date>2008-05-02T00:04:50Z</dc:date>
    </item>
    <item>
      <title>Re: SetPoint Install Issue</title>
      <link>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/257231#M7119</link>
      <description>&lt;p&gt;Logitech: Best hardware abailable.&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;Worst support and software in the industry.&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;You guys are lucky your products are good or you'd be out of the job. Maybe try getting some support that speaks english and can help rather than giving canned, unhelpful responses in broken language, and actually shelling out for a better software design team.&lt;/p&gt;</description>
      <pubDate>Sat, 04 Oct 2008 02:05:42 GMT</pubDate>
      <guid>http://forums.logitech.com/t5/Keyboards-Bluetooth/SetPoint-Install-Issue/m-p/257231#M7119</guid>
      <dc:creator>hsdjkfas</dc:creator>
      <dc:date>2008-10-04T02:05:42Z</dc:date>
    </item>
  </channel>
</rss>

