<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cygwin on ads' corner</title><link>https://andreas.scherbaum.la/tags/cygwin/</link><description>Recent content in Cygwin on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 09 Sep 2013 16:08:37 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/cygwin/index.xml" rel="self" type="application/rss+xml"/><item><title>Cleanup and reuse unused Copy&amp;Paste disk space occupied by VMware</title><link>https://andreas.scherbaum.la/post/2013-09-09_cleanup-and-reuse-unused-copypaste-disk-space-occupied-by-vmware/</link><pubDate>Mon, 09 Sep 2013 16:08:37 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2013-09-09_cleanup-and-reuse-unused-copypaste-disk-space-occupied-by-vmware/</guid><description>&lt;p&gt;Whenever you &lt;em&gt;Copy&amp;amp;Paste&lt;/em&gt; (or &lt;em&gt;Cut&amp;amp;Paste&lt;/em&gt;) something into or from a &lt;em&gt;VMware&lt;/em&gt; instance, the software first copies the files into a temporary directory and later on sends the copy/move job to &lt;em&gt;Windows&lt;/em&gt;. Since the &lt;em&gt;Windows&lt;/em&gt; task is asynchronous, &lt;em&gt;VMware&lt;/em&gt; has no chance to find out when this actually finishes - so it is supposed to clean up this temporary directory at boot time.&lt;/p&gt;&#10;&lt;p&gt;However, waiting for the next reboot can clog up quite some disk space (when I develop something I often have to copy many files around between several virtual machines and the desktop) - despite that &lt;em&gt;Windows&lt;/em&gt; still likes to &lt;a href="https://en.wikipedia.org/wiki/Blue_screen_of_death"&gt;BSoD&lt;/a&gt; on me from time to time. And sometimes &lt;em&gt;VMware&lt;/em&gt; does not get the cleanup right at reboot and the files are still there.&lt;/p&gt;</description></item></channel></rss>