<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Converting a Virtual PC  image to Parallels mac</title>
	<atom:link href="http://blog.notarus.net/2006/10/11/converting-a-virtual-pc-image-to-parallels-mac/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.notarus.net/2006/10/11/converting-a-virtual-pc-image-to-parallels-mac/</link>
	<description></description>
	<pubDate>Thu, 11 Mar 2010 10:13:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Gary</title>
		<link>http://blog.notarus.net/2006/10/11/converting-a-virtual-pc-image-to-parallels-mac/#comment-2213</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Sat, 16 Dec 2006 02:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notarus.net/2006/10/11/converting-a-virtual-pc-image-to-parallels-mac/#comment-2213</guid>
		<description>I've gotten the archive upload to work successfully, but when I attempt to import the image, I have to use the "new" Intel Mac's IP address to make the connection, and once the transfer is done, it still provides an error, saying that the archive length was not correct. I suspect either the transfer is not completing, or something is not being written correctly, since every image I have attempted to create from the VPC image has been roughly 3GB in size, while the data that is claimed to transfer (specified drive size) is 15GB.

Once complete, the machine attempts to boot in Parallels, but provides an error saying that there was a hardware error, and that the machine needs to reboot, but simply runs an endelss cycle, asking if I'd like to boot in Safe Mode (which provides the same error) or boot normally, continuing in an endless loop.

Any insights?

The method is ingenious, I would just really like to figure out why I'm so close to working, without actual success.

Thanks,
   Gary</description>
		<content:encoded><![CDATA[<p>I&#8217;ve gotten the archive upload to work successfully, but when I attempt to import the image, I have to use the &#8220;new&#8221; Intel Mac&#8217;s IP address to make the connection, and once the transfer is done, it still provides an error, saying that the archive length was not correct. I suspect either the transfer is not completing, or something is not being written correctly, since every image I have attempted to create from the VPC image has been roughly 3GB in size, while the data that is claimed to transfer (specified drive size) is 15GB.</p>
<p>Once complete, the machine attempts to boot in Parallels, but provides an error saying that there was a hardware error, and that the machine needs to reboot, but simply runs an endelss cycle, asking if I&#8217;d like to boot in Safe Mode (which provides the same error) or boot normally, continuing in an endless loop.</p>
<p>Any insights?</p>
<p>The method is ingenious, I would just really like to figure out why I&#8217;m so close to working, without actual success.</p>
<p>Thanks,<br />
   Gary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: djl</title>
		<link>http://blog.notarus.net/2006/10/11/converting-a-virtual-pc-image-to-parallels-mac/#comment-2189</link>
		<dc:creator>djl</dc:creator>
		<pubDate>Tue, 12 Dec 2006 13:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notarus.net/2006/10/11/converting-a-virtual-pc-image-to-parallels-mac/#comment-2189</guid>
		<description>Thanks for this - just copying over now.
It might be worth mentioning in your article that the PPC/old Mac needs to be connected via Ethernet for the FTP to work.
The Intel Mac is fine on Airport/WLAN though.
Cheers</description>
		<content:encoded><![CDATA[<p>Thanks for this - just copying over now.<br />
It might be worth mentioning in your article that the PPC/old Mac needs to be connected via Ethernet for the FTP to work.<br />
The Intel Mac is fine on Airport/WLAN though.<br />
Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
