<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Controversial Book Cover?</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 13:56:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Final Back Cover for MDAA V1</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23308</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Final Back Cover for MDAA V1</dc:creator>
		<pubDate>Mon, 14 Apr 2008 16:07:58 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23308</guid>
		<description>[...] Crash Dump Analysis Exploring Crash Dumps and Debugging Techniques on Windows Platforms      &#171; Controversial Book Cover? [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Crash Dump Analysis Exploring Crash Dumps and Debugging Techniques on Windows Platforms      &laquo; Controversial Book Cover? [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario Hewardt</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23306</link>
		<dc:creator>Mario Hewardt</dc:creator>
		<pubDate>Mon, 14 Apr 2008 15:38:53 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23306</guid>
		<description>This link may be useful:

http://www.microsoft.com/about/legal/permissions/default.mspx#E3C

At least in as far as screenshots of Microsoft products is concerned.</description>
		<content:encoded><![CDATA[<p>This link may be useful:</p>
<p><a href="http://www.microsoft.com/about/legal/permissions/default.mspx#E3C" rel="nofollow">http://www.microsoft.com/about/legal/permissions/default.mspx#E3C</a></p>
<p>At least in as far as screenshots of Microsoft products is concerned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23297</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 14 Apr 2008 14:05:38 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23297</guid>
		<description>I actually found that a user dump of one of my applications is much better and vivid picture to illustrate. So I'll replace the picture in the final book. To sleep better :-)</description>
		<content:encoded><![CDATA[<p>I actually found that a user dump of one of my applications is much better and vivid picture to illustrate. So I&#8217;ll replace the picture in the final book. To sleep better <img src='https://www.dumpanalysis.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23289</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 14 Apr 2008 12:13:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/13/controversial-book-cover/#comment-23289</guid>
		<description>Using my CRC example, there are many ways (different code and data) to get the same picture because it was first preprocessed and reduced from 16128x16128 to 2167x3254 format and further processed by JPEG algorithm. I would say that we have a different interpretation of the data if the original data is not possible to reconstruct or if there is ambiguity in data reconstruction. Also we will never get the same picture from different memory dumps even from the same system because memory contents and layout change with every CPU tick. How would I get exactly the same picture form a different code and data? Exactly the same way I can generate the same CRC! </description>
		<content:encoded><![CDATA[<p>Using my CRC example, there are many ways (different code and data) to get the same picture because it was first preprocessed and reduced from 16128&#215;16128 to 2167&#215;3254 format and further processed by JPEG algorithm. I would say that we have a different interpretation of the data if the original data is not possible to reconstruct or if there is ambiguity in data reconstruction. Also we will never get the same picture from different memory dumps even from the same system because memory contents and layout change with every CPU tick. How would I get exactly the same picture form a different code and data? Exactly the same way I can generate the same CRC!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
