<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   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/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
<channel>
    <title>Moblog - Comments</title>
    <link>http://moblog.wiredwings.com/</link>
    <description>Moblog - Moritz Bartl</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.5.2 - http://www.s9y.org/</generator>
    <pubDate>Thu, 18 Mar 2010 18:08:04 GMT</pubDate>

    <image>
        <url>http://moblog.wiredwings.com/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Moblog - Comments - Moblog - Moritz Bartl</title>
        <link>http://moblog.wiredwings.com/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Pasi Kärkkäinen: Lenny's Xen Kernel 2.6.26 Causes DomU Freezes</title>
    <link>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#c100</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=106</wfw:comment>

    

    <author>nospam@example.com (Pasi Kärkkäinen)</author>
    <content:encoded>
    Many people are seeing this bug, me included.&lt;br /&gt;
&lt;br /&gt;
Do you guys have a reliable/fast way to reproduce this? &lt;br /&gt;
&lt;br /&gt;
What should be done is to get a stack trace for each guest vcpu to see what&#039;s happening (going wrong), so it can be debugged and fixed.&lt;br /&gt;
&lt;br /&gt;
In dom0, like this:&lt;br /&gt;
/usr/lib/xen/bin/xenctx -s System.map-2.6.26-2-xen-686   &lt;br /&gt;
&lt;br /&gt;
Repeat that command for each guest vcpu.&lt;br /&gt;
The first vcpu is number 0, next is number 1 etc.&lt;br /&gt;
&lt;br /&gt;
If you have a 64bit dom0, xenctx might be under /usr/lib64/.&lt;br /&gt;
&lt;br /&gt;
The System.map file should be the actual correct System.map for the guest kernel. 
    </content:encoded>

    <pubDate>Fri, 05 Mar 2010 15:57:20 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100305/106.html#c100</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>nw: Disable Annoying &quot;Disk not formatted&quot; Dialog on Vista/Windows 7</title>
    <link>http://moblog.wiredwings.com/archives/20090903/Disable-Annoying-Disk-not-formatted-Dialog-on-VistaWindows-7.html#c99</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090903/Disable-Annoying-Disk-not-formatted-Dialog-on-VistaWindows-7.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=127</wfw:comment>

    

    <author>nospam@example.com (nw)</author>
    <content:encoded>
    many softwares which encrypt the whole drive require a drive letter, so deleting it is not the solution. this script works fine, it&#039;s the best solution i currently find:) 
    </content:encoded>

    <pubDate>Fri, 26 Feb 2010 01:16:25 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100226/127.html#c99</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Moritz: Disable Annoying &quot;Disk not formatted&quot; Dialog on Vista/Windows 7</title>
    <link>http://moblog.wiredwings.com/archives/20090903/Disable-Annoying-Disk-not-formatted-Dialog-on-VistaWindows-7.html#c98</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090903/Disable-Annoying-Disk-not-formatted-Dialog-on-VistaWindows-7.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=127</wfw:comment>

    

    <author>nospam@example.com (Moritz)</author>
    <content:encoded>
    Neat solution, thanks, didn&#039;t think about that. Of course it only works for known drives, and I&#039;m not sure it&#039;ll work for every partition encryption software (ie. that the drive letter is shown once the partition is decrypted). 
    </content:encoded>

    <pubDate>Fri, 19 Feb 2010 18:27:27 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100219/127.html#c98</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Jeff: Disable Annoying &quot;Disk not formatted&quot; Dialog on Vista/Windows 7</title>
    <link>http://moblog.wiredwings.com/archives/20090903/Disable-Annoying-Disk-not-formatted-Dialog-on-VistaWindows-7.html#c97</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090903/Disable-Annoying-Disk-not-formatted-Dialog-on-VistaWindows-7.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=127</wfw:comment>

    

    <author>nospam@example.com (Jeff)</author>
    <content:encoded>
    &gt;&gt;Other than disabling autorun completely, there is no official way to stop the &quot;You need to format the disk in drive X before you can use it&quot;&lt;br /&gt;
&lt;br /&gt;
FYI: This is wrong! The official way is to simply remove the drive letter from that specific partition in disk management... 
    </content:encoded>

    <pubDate>Fri, 19 Feb 2010 17:56:48 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100219/127.html#c97</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Moritz: Microsoft LifeCam Webcam - Drivers Only</title>
    <link>http://moblog.wiredwings.com/archives/20090303/Microsoft-LifeCam-Webcam-Drivers-Only.html#c96</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090303/Microsoft-LifeCam-Webcam-Drivers-Only.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=107</wfw:comment>

    

    <author>nospam@example.com (Moritz)</author>
    <content:encoded>
    There is one archive for Windows XP and one for Win7, each contains &lt;strong&gt;all&lt;/strong&gt; LifeCam drivers. 
    </content:encoded>

    <pubDate>Thu, 18 Feb 2010 19:56:47 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100218/107.html#c96</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>ali pali: Microsoft LifeCam Webcam - Drivers Only</title>
    <link>http://moblog.wiredwings.com/archives/20090303/Microsoft-LifeCam-Webcam-Drivers-Only.html#c95</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090303/Microsoft-LifeCam-Webcam-Drivers-Only.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=107</wfw:comment>

    

    <author>nospam@example.com (ali pali)</author>
    <content:encoded>
    im comfused! witch ones the one for lifecam VX-3000?&lt;br /&gt;
plz tall me 
    </content:encoded>

    <pubDate>Thu, 18 Feb 2010 19:53:11 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100218/107.html#c95</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Moritz: Vista: Windows Update Error 80070011 Semi-Automated Fix</title>
    <link>http://moblog.wiredwings.com/archives/20080301/Vista-Windows-Update-Error-80070011-Semi-Automated-Fix.html#c94</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20080301/Vista-Windows-Update-Error-80070011-Semi-Automated-Fix.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=25</wfw:comment>

    

    <author>nospam@example.com (Moritz)</author>
    <content:encoded>
    I cannot recommend to move winsxs and have no solution, sorry. After too much trouble I only move the profile data directory (&lt;a href=&quot;http://moblog.wiredwings.com/archives/20080729/Windows-Vista-Moving-Program-Files-and-User-Data,-Revisited.html&quot;  class=&quot;bb-url&quot;&gt;explained here&lt;/a&gt;) and leave the rest alone.&lt;br /&gt;
&lt;br /&gt;
It doesn&#039;t help to move winsxs, because all updates replace files on the system partition anyway. Files are NOT COPIED to their destination, but hardlinked, so keeping the winsxs directory on C won&#039;t take more space! I&#039;m not sure what happens if a later update changes the same files, I guess the previous update will stay, but maybe one could find a way to cleanup the directory, which is still better than move it completely.&lt;br /&gt;
So, a solution might be to scan for files inside winsxs that are linked only once, which means they are not in use by the system, and move/delete those files? 
    </content:encoded>

    <pubDate>Wed, 17 Feb 2010 20:56:57 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100217/25.html#c94</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Moritz: Windows Vista: Moving Program Files and User Data, Revisited</title>
    <link>http://moblog.wiredwings.com/archives/20080729/Windows-Vista-Moving-Program-Files-and-User-Data,-Revisited.html#c93</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20080729/Windows-Vista-Moving-Program-Files-and-User-Data,-Revisited.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=48</wfw:comment>

    

    <author>nospam@example.com (Moritz)</author>
    <content:encoded>
    I can confirm that this (method 1) still works very well using Windows 7. 
    </content:encoded>

    <pubDate>Wed, 17 Feb 2010 20:52:04 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100217/48.html#c93</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Ullrich Fischer: Vista: Windows Update Error 80070011 Semi-Automated Fix</title>
    <link>http://moblog.wiredwings.com/archives/20080301/Vista-Windows-Update-Error-80070011-Semi-Automated-Fix.html#c92</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20080301/Vista-Windows-Update-Error-80070011-Semi-Automated-Fix.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=25</wfw:comment>

    

    <author>nospam@example.com (Ullrich Fischer)</author>
    <content:encoded>
    I followed some detailed instructions to replace c:\windows\winsxs with a link to a folder on my e: drive so that I could free up some space on my SSD 60 GB C: drive.  Since then updates are failing.  I&#039;m wondering if updates have a problem copying themselves to of finding what is in the destination of that link.  Is there a registry setting somewhere that needs to be updated to take care of this?  I&#039;m getting error 80070011 for any update that I try to install. 
    </content:encoded>

    <pubDate>Wed, 17 Feb 2010 20:28:05 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100217/25.html#c92</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Aaron: Lenny's Xen Kernel 2.6.26 Causes DomU Freezes</title>
    <link>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#c88</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=106</wfw:comment>

    

    <author>nospam@example.com (Aaron)</author>
    <content:encoded>
    Yes, at first I tried limiting the Dom0 only - but that didn&#039;t solve it for me.&lt;br /&gt;
I got the idea from this bug report:&lt;br /&gt;
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524571&lt;br /&gt;
&lt;br /&gt;
I have the latest (official) packages for Debian Lenny installed - but I use the workaround for about 50 days now and don&#039;t have a problem with limiting each DomU to one CPU, so I didn&#039;t test if the bug is still there.&lt;br /&gt;
&lt;br /&gt;
And I agree, the second issue isn&#039;t really a problem &lt;img src=&quot;http://moblog.wiredwings.com/templates/default/img/emoticons/wink.png&quot; alt=&quot;;-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; 
    </content:encoded>

    <pubDate>Mon, 01 Feb 2010 14:24:23 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100201/106.html#c88</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Moritz: Evaluating Dropbox and Syncplicity: A First Comparison</title>
    <link>http://moblog.wiredwings.com/archives/20080728/Evaluating-Dropbox-and-Syncplicity-A-First-Comparison.html#c87</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20080728/Evaluating-Dropbox-and-Syncplicity-A-First-Comparison.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=47</wfw:comment>

    

    <author>nospam@example.com (Moritz)</author>
    <content:encoded>
    I&#039;ve been using Syncplicity to synchronize some of my files between my Laptop (WinXP) and desktop (Vista, now Win7). Sometimes it eats up my CPU and I have to kill it, but apart from that I&#039;m happy. But I don&#039;t need it for restore - for (network) backups, I use another app, Crashplan. You&#039;re right, restore on a file basis sucks. Dropbox supports that.&lt;br /&gt;
&lt;br /&gt;
Syncplicity &lt;a href=&quot;https://my.syncplicity.com/Forums/default.aspx?g=posts&amp;amp;t=3066&quot;  class=&quot;bb-url&quot;&gt;&quot;looks into adding this feature in a future release&quot;&lt;/a&gt;, until then, you can &lt;a href=&quot;http://manual.syncplicity.com/Restoration-Request&quot;  class=&quot;bb-url&quot;&gt;file a Restoration Request&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Mon, 01 Feb 2010 13:19:38 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100201/47.html#c87</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Moritz: Lenny's Xen Kernel 2.6.26 Causes DomU Freezes</title>
    <link>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#c86</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=106</wfw:comment>

    

    <author>nospam@example.com (Moritz)</author>
    <content:encoded>
    Thank you for your information. Unfortunately, I need multicores inside my DomUs. Did you try limiting the Dom0 only? Is that even possible?&lt;br /&gt;
&lt;br /&gt;
I guess you have tried the latest Xen+Lenny kernels? I cannot believe they still haven&#039;t fixed this.&lt;br /&gt;
&lt;br /&gt;
The second issue - problems with DomU shutdown - on the other hand isn&#039;t as bad, I never shut down DomU&#039;s. &lt;img src=&quot;http://moblog.wiredwings.com/templates/default/img/emoticons/wink.png&quot; alt=&quot;;-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; 
    </content:encoded>

    <pubDate>Mon, 01 Feb 2010 13:08:03 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100201/106.html#c86</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Aaron: Lenny's Xen Kernel 2.6.26 Causes DomU Freezes</title>
    <link>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#c85</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090227/Lennys-Xen-Kernel-2.6.26-Causes-DomU-Freezes.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=106</wfw:comment>

    

    <author>nospam@example.com (Aaron)</author>
    <content:encoded>
    Any update on this problem?&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know a fix, but I have a workaround - or at least in my case it works:&lt;br /&gt;
Limit the Dom0 to one cpu (&quot;(dom0-cpus 1)&quot;) and also every DomU (&quot;vcpus = 1&quot;). Until the kernel update yesterday I had an uptime of approx. 50 days and no problems.&lt;br /&gt;
But unfortunately there&#039;s another bug to consider if you want to use this workaround:&lt;br /&gt;
http://old.nabble.com/Domain-status-after-shutdown-command:----s---td15565767.html&lt;br /&gt;
&lt;br /&gt;
I just wanted to write this because the Etch kernel won&#039;t get security updates much longer. 
    </content:encoded>

    <pubDate>Mon, 01 Feb 2010 10:34:23 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100201/106.html#c85</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Patrick: Evaluating Dropbox and Syncplicity: A First Comparison</title>
    <link>http://moblog.wiredwings.com/archives/20080728/Evaluating-Dropbox-and-Syncplicity-A-First-Comparison.html#c84</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20080728/Evaluating-Dropbox-and-Syncplicity-A-First-Comparison.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=47</wfw:comment>

    

    <author>nospam@example.com (Patrick)</author>
    <content:encoded>
    I installed Syncplidiocy on my one PC and selected the dirs that it should back up. I let it back up everything, before I installed the program on my other PC.&lt;br /&gt;
&lt;br /&gt;
After installing on my other PC, I assigned the correct folders for it to sync with on the new PC, and it started inital sync.&lt;br /&gt;
&lt;br /&gt;
When I returned about 6 hours later, it had reached 11 % and had stalled. After a while I exited the app and started it again. It now started working again.&lt;br /&gt;
&lt;br /&gt;
It looked like it was downloading files, but the time left got smaller and smaller, and the amount of files suddenly dropped. I wondered how it could download so fast, and after 15 minutes it had downloaded the whole 1.5 GB.&lt;br /&gt;
&lt;br /&gt;
So I went to check, and of course only some of the files was there. But that wasn&#039;t the worst part. The worst part was, that now Syncplidocy had DELETED the files on my original computer, meaning that ALL MY DATA IS LOST!!!&lt;br /&gt;
&lt;br /&gt;
So I went in help, but they offer no form of contact with the free edition - even though having DELETED MY FILES!!! The manual said to use the recycle bin, but this only offers restoration on a SINGLE FILE BASIS! So does it expect that I sit and click &quot;restore&quot; 10.000 times????&lt;br /&gt;
&lt;br /&gt;
I am appalled! Luckily I took a backup a few days ago before starting out with apps like this, and lucky for me. But days of work is lost! 
    </content:encoded>

    <pubDate>Sun, 31 Jan 2010 23:31:38 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100131/47.html#c84</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>
<item>
    <title>Fritzybabe: Microsoft LifeCam Webcam - Drivers Only</title>
    <link>http://moblog.wiredwings.com/archives/20090303/Microsoft-LifeCam-Webcam-Drivers-Only.html#c83</link>
            <category></category>
    
    <comments>http://moblog.wiredwings.com/archives/20090303/Microsoft-LifeCam-Webcam-Drivers-Only.html#comments</comments>
    <wfw:comment>http://moblog.wiredwings.com/wfwcomment.php?cid=107</wfw:comment>

    

    <author>nospam@example.com (Fritzybabe)</author>
    <content:encoded>
    What a hero!!!! You&#039;ll never get a job for Microsoft - you&#039;re too helpful!&lt;br /&gt;
By the way the Windows 7 and vista 64 bit works for XP64 as well unlike any of the Microsoft packages. 
    </content:encoded>

    <pubDate>Thu, 28 Jan 2010 13:04:59 +0100</pubDate>
    <guid isPermaLink="false">http://moblog.wiredwings.com/archives/20100128/107.html#c83</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
</item>

</channel>
</rss>