<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title><![CDATA[JKCC Ltd.]]></title>
<link><![CDATA[https://www.lightroom-plugins.com/support/]]></link>
<description />
<generator><![CDATA[Kayako Fusion v4.52.2417]]></generator>
<item>
<title><![CDATA[Windows 7 Upgrade very slow]]></title>
<link><![CDATA[https://www.lightroom-plugins.com/support/index.php?/Lightroom/Knowledgebase/Article/View/28]]></link>
<guid isPermaLink="false"><![CDATA[33e75ff09dd601bbe69f351039152189]]></guid>
<pubDate><![CDATA[Fri, 09 Apr 2010 18:01:06 +0000]]></pubDate>
<dc:creator><![CDATA[Jim Keir (Import)]]></dc:creator>
<description><![CDATA[There's a lot of fairly useless information about this, mainly from deniers who insist that an in-place upgrade will never take more than an hour on any hardware with any amount of files. Sadly, not true.

Two reasons I found during a recent upgrade:
...]]></description>
<content:encoded><![CDATA[There's a lot of fairly useless information about this, mainly from deniers who insist that an in-place upgrade will never take more than an hour on any hardware with any amount of files. Sadly, not true.<br />
<br />
Two reasons I found during a recent upgrade:<br />
<br />
<h3>The IP Helper service was disabled</h3><br />
This is only supposed to be used for IP6, but without this on the upgrade will stall frequently. The solution is simply to make sure the service is started. If you're running an upgrade, then Vista is still running in the background. Simply hit the "Windows" key on the keyboard to bring up the start menu, then right-click on Computer, then Manage. Enable the "IP Helper" service.<br />
<br />
<h3>Gathering files, settings and programs</h3><br />
Even after enabling the IP Helper service, this stage took over 24 hours to get to 44% before I started poking around some more. It seemed that the system registry was being written to a temp file with every change, which in my case was about 180Mb of file written and re-read for every key that got changed. The disk wasn't especially slow - hardware RAID in fact - but that's still a huge amount of I/O.<br />
<br />
To fix this, I downloaded and installed the "Dataram RAMDisk" from http://memory.dataram.com/products-and-services/software/ramdisk and created a 512Mb ramdisk. Once partitioned and formatted, I changed the system TMP and TEMP paths to point to the ramdisk. In the time it's taken me to type this, the installation has got to 83%.<br />
<br />
Just remember to reset the original values for TMP and TEMP after the installation completes.<br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[XCode's Storyboard doesn't work over VNC]]></title>
<link><![CDATA[https://www.lightroom-plugins.com/support/index.php?/Lightroom/Knowledgebase/Article/View/114]]></link>
<guid isPermaLink="false"><![CDATA[5fd0b37cd7dbbb00f97ba6ce92bf5add]]></guid>
<pubDate><![CDATA[Mon, 06 Aug 2012 18:14:29 +0000]]></pubDate>
<dc:creator />
<description><![CDATA[It seems that the "killer feature" of XCode 4.3, the new Storyboard editor, doesn't like VNC. An important feature of this is the ability to hold down control and then just drag objects around to form associations, but over VNC, nothing happens. It's also...]]></description>
<content:encoded><![CDATA[<p>It seems that the "killer feature" of XCode 4.3, the new Storyboard editor, doesn't like VNC. An important feature of this is the ability to hold down control and then just drag objects around to form associations, but over VNC, nothing happens. It's also not possible to move objects around on the storyboard.</p>
<p>I tried this with Lion's "Screen Sharing", RealVNC and Vine Server, all with the same problem. Also tried it with several different VNC clients, all with the same result. I don't have an answer for it except to wait for an update to XCode, but at least knowing that it's not just you might help.</p>
<p>I have to admit that I did give in and buy a Startech KVM...</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[VNC onto MacOS Lion has no keyboard]]></title>
<link><![CDATA[https://www.lightroom-plugins.com/support/index.php?/Lightroom/Knowledgebase/Article/View/115]]></link>
<guid isPermaLink="false"><![CDATA[2b44928ae11fb9384c4cf38708677c48]]></guid>
<pubDate><![CDATA[Mon, 06 Aug 2012 18:21:00 +0000]]></pubDate>
<dc:creator />
<description><![CDATA[Trying to use a Mac Mini over VNC... last time I used it, it was fine. Tried today and got no keyboard response, even though the mouse was fine. Hadn't been restarted, hadn't had any patches applied.
Well, to cut a very long and tedious story short, it tu...]]></description>
<content:encoded><![CDATA[<p>Trying to use a Mac Mini over VNC... last time I used it, it was fine. Tried today and got no keyboard response, even though the mouse was fine. Hadn't been restarted, hadn't had any patches applied.</p>
<p>Well, to cut a very long and tedious story short, it turns out that if you have a non-standard keyboard configured then none of the available VNC servers for Lion accept any keyboard input. I tried with built-in Screen Sharing, Vine Server and RealVNC all with the same problem. Also tried all of Vine Server's various keyboard input methods in the "Advanced" tab with no luck, using several different VNC clients.</p>
<p>So, I've had to remove my "GB Windows Standard" keyboard layout on the Mac Mini and revert back to the "Blessed by St. Jobs" one instead. Do that, restart the VNC servers and hey presto, I can type over VNC again (although half the symbols I need for programming are in the wrong place).</p>]]></content:encoded>
</item>
</channel>
</rss>