<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Official Atola Technology Blog</title>
	<atom:link href="http://blog.atola.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.atola.com</link>
	<description>Hard disk drive technology and data recovery stuff</description>
	<lastBuildDate>Mon, 23 Apr 2012 12:56:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Interested on Forensics issue?</title>
		<link>http://blog.atola.com/interested-on-forensics-issue/</link>
		<comments>http://blog.atola.com/interested-on-forensics-issue/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 06:50:13 +0000</pubDate>
		<dc:creator>Alexandra Kalinichenko</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.atola.com/?p=338</guid>
		<description><![CDATA[I’m happy to inform you that we’ve started our cooperation with Hakin9, an IT-security magazine. In the article you will find our offers and recommendations, solutions and detail information on how our products are functional and efficient. All products belong to the category of advanced and smart technology, at the same time being easily accessible [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.atola.com/interested-on-forensics-issue/forensics-magazine/" rel="attachment wp-att-352"><img class="alignnone size-medium wp-image-352" title="Forensics-magazine" src="http://blog.atola.com/wp-content/uploads/2012/04/Forensics-magazine-203x300.jpg" alt="" width="203" height="300" /></a></p>
<p>I’m happy to inform you that we’ve started our cooperation with Hakin9, an IT-security magazine.</p>
<p>In the article you will find our offers and recommendations, solutions and detail information on how our products are functional and efficient. All products belong to the category of advanced and smart technology, at the same time being easily accessible and user-friendly. We treat our customers with the utmost care, so all tools are carefully designed with the use of the best existing technology.</p>
<p>Now you can solve even the most difficult problem in Forensics so easy – just choose an Atola product and start to use.</p>
<p>Want to learn more?</p>
<p>Please follow <a href="http://atola.com/files/pdf/Hakin9_Extra_4_2012.pdf">the link</a>.</p>
<p>If you want to read the full edition, please <a href="http://hakin9.org/wp-login.php?action=register&amp;a_aid=michalwisniewski&amp;a_bid=8f6377e8">register here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.atola.com/interested-on-forensics-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What&#8217;s new in Atola Insight 2.4</title>
		<link>http://blog.atola.com/whats-new-in-atola-insight-2-4/</link>
		<comments>http://blog.atola.com/whats-new-in-atola-insight-2-4/#comments</comments>
		<pubDate>Tue, 03 Jan 2012 15:59:23 +0000</pubDate>
		<dc:creator>Fedir Nepyivoda</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.atola.com/?p=324</guid>
		<description><![CDATA[Introducing Imaging Target Concept With the help of imaging targets, it is now possible to efficiently image a hard drive using multiple sessions. During each session, the Atola Insight only copies sectors that were not copied during any previous session. As the imaging process goes on, the operator can adjust the copy approach and change [...]]]></description>
			<content:encoded><![CDATA[<h4>Introducing Imaging Target Concept</h4>
<p>With the help of imaging targets, it is now possible to efficiently image a hard drive using multiple sessions. During each session, the Atola Insight only copies sectors that were not copied during any previous session.</p>
<p>As the imaging process goes on, the operator can adjust the copy approach and change various settings for each session in order to maximize data extraction.</p>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<td width='50%'><a href="http://blog.atola.com/wp-content/uploads/2012/01/img-targets.png"><img src="http://blog.atola.com/wp-content/uploads/2012/01/img-targets-300x217.png" alt="" title="Imaging targets" width="300" height="217" class="alignnone size-medium wp-image-331" /></a></td>
<td width='50%'><a href="http://blog.atola.com/wp-content/uploads/2012/01/img-sessions.png"><img src="http://blog.atola.com/wp-content/uploads/2012/01/img-sessions-300x217.png" alt="" title="Imaging Sessions" width="300" height="217" class="alignnone size-medium wp-image-332" /></a></td>
</table>
<p>Data from the multi-session imaging function is then used to aid the file recovery process. The Atola Insight pinpoints any files that are incomplete or contain bad sectors and report them to the user.</p>
<h4>Read without ECC Correction for all LBA48 Range</h4>
<p>Imaging can now copy sectors without ECC check for all hard drive sectors. This function enables Atola Insight users to read data from bad/unreadable sectors by ignoring ECC codes. When enabled, it is executed during the last imaging pass if all other read operations have failed.</p>
<p>The list of supported hard drives for this function has been expanded dramatically. 2TB drives and over are supported!</p>
<h4>Firmware and Password Recovery</h4>
<p>Improved support for firmware access and password recovery for latest Western Digital drives (including Raptor models).</p>
<h4>Improvements and Bug Fixes</h4>
<p>Various improvements were made to the software. Please refer to the <a href='http://atola.com/products/insight/changelog.html'>version log</a> for details.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.atola.com/whats-new-in-atola-insight-2-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Imaging using Read Long in Bandura</title>
		<link>http://blog.atola.com/imaging-using-read-long-in-bandura/</link>
		<comments>http://blog.atola.com/imaging-using-read-long-in-bandura/#comments</comments>
		<pubDate>Mon, 12 Dec 2011 07:42:07 +0000</pubDate>
		<dc:creator>Vitaliy Mokosiy</dc:creator>
				<category><![CDATA[Atola Bandura]]></category>
		<category><![CDATA[Bandura]]></category>
		<category><![CDATA[imaging]]></category>
		<category><![CDATA[read long]]></category>

		<guid isPermaLink="false">http://blog.atola.com/imaging-using-read-long-in-bandura/</guid>
		<description><![CDATA[Imaging is the main Atola Bandura feature. This is the reason why it has been unstoppably improved since the very first release. This time we added the new setting to the firmware update 1.1.5 allowing to apply Read Long command for reading bad sectors and getting some data from them on last pass. Every sector [...]]]></description>
			<content:encoded><![CDATA[<h3>
<div class='bandura_frame'><img title="Bandura: Imaging via Read Long" src="http://blog.atola.com/wp-content/uploads/2011/12/imaging-readlong-setting_thumb1_thumb.png" alt="Bandura: Imaging via Read Long" width="270" height="180" border="0" /></div>
</h3>
<p>Imaging is the main <a href="http://atola.com/products/bandura/specifications.html">Atola Bandura</a> feature. This is the reason why it has been unstoppably improved since the very first release. This time we added the new setting to the <a href="http://atola.com/products/bandura/update.html">firmware update 1.1.5</a> allowing to apply Read Long command for reading bad sectors and getting some data from them on last pass.</p>
<p>Every sector read by Read Long is marked in Imaging log with a corresponding message:</p>
<div class='bandura_frame'><img title="Read Long in Imaging log" src="http://blog.atola.com/wp-content/uploads/2011/12/imaging-readlong-log_thumb_thumb.png" alt="Read Long in Imaging log" width="270" height="180" /></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.atola.com/imaging-using-read-long-in-bandura/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wiping 2 disks simultaneously in Bandura</title>
		<link>http://blog.atola.com/wiping-2-disks-simultaneously-in-bandura/</link>
		<comments>http://blog.atola.com/wiping-2-disks-simultaneously-in-bandura/#comments</comments>
		<pubDate>Wed, 07 Dec 2011 07:58:22 +0000</pubDate>
		<dc:creator>Vitaliy Mokosiy</dc:creator>
				<category><![CDATA[Atola Bandura]]></category>
		<category><![CDATA[Bandura]]></category>
		<category><![CDATA[erase]]></category>
		<category><![CDATA[wipe]]></category>

		<guid isPermaLink="false">http://blog.atola.com/wiping-2-disks-simultaneously-in-bandura/</guid>
		<description><![CDATA[Atola Bandura contains many erasing algorithms including DoD 5220.22-M, NIST 800-88, Security Erase, Fill with Pattern/LBA. All of them can be used for simultaneous wiping of 2 disk added to firmware version 1.1.5 as a new feature. New Disks to use setting allows to select one of two variants: - Source &#38; Target (new!) - [...]]]></description>
			<content:encoded><![CDATA[<div class='bandura_frame'><img title="Wiping 2 disks simultaneously in Bandura" src="http://blog.atola.com/wp-content/uploads/2011/12/erasing-settings-disks_thumb3_thumb.png" alt="Wiping 2 disks simultaneously in Bandura" width="270" height="180" border="0" /></div>
<p><a href="http://atola.com/products/bandura/specifications.html">Atola Bandura</a> contains many erasing algorithms including DoD 5220.22-M, NIST 800-88, Security Erase, Fill with Pattern/LBA.<strong> </strong>All of them can be used for simultaneous wiping of 2 disk added to <a href="http://atola.com/products/bandura/update.html">firmware version 1.1.5</a> as a new feature.</p>
<p>New<strong> Disks to use</strong> setting allows to select one of two variants:</p>
<p>- Source &amp; Target (new!)</p>
<p>- Target</p>
<p>Selecting Source &amp; Target, you will be able to improve Bandura performance twice in case if you need to wipe several or many disks. This option helps to start erasing 2 disks simultaneously.</p>
<p align="left">It’s also important to understand that it somewhat breaks Bandura concept of write-protected source disk. Therefore an additional confirmative question will be shown each time you try to start wiping source and target disks together.</p>
<p><strong>Start button with updated text</strong></p>
<div class='bandura_frame'><img title="Start erasing 2 disks with Bandura" src="http://blog.atola.com/wp-content/uploads/2011/12/erase-panel-two-disks_thumb1_thumb.png" alt="Start erasing 2 disks with Bandura" width="270" height="180" border="0" /></div>
<p>&nbsp;</p>
<p><strong>Wiping source and target disks together</strong></p>
<div class='bandura_frame'><img title="Disks wiping in progress" src="http://blog.atola.com/wp-content/uploads/2011/12/erase-in-progress-two-disks_thumb1_thumb.png" alt="Disks wiping in progress" width="270" height="180" /></div>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.atola.com/wiping-2-disks-simultaneously-in-bandura/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HPA and DCO max address management</title>
		<link>http://blog.atola.com/hpa-and-dco-max-address-management/</link>
		<comments>http://blog.atola.com/hpa-and-dco-max-address-management/#comments</comments>
		<pubDate>Mon, 05 Dec 2011 08:16:36 +0000</pubDate>
		<dc:creator>Vitaliy Mokosiy</dc:creator>
				<category><![CDATA[Atola Bandura]]></category>
		<category><![CDATA[Bandura]]></category>
		<category><![CDATA[dco]]></category>
		<category><![CDATA[hpa]]></category>

		<guid isPermaLink="false">http://blog.atola.com/hpa-and-dco-max-address-management/</guid>
		<description><![CDATA[The Bandura (since firmware version 1.1.5) enables users to easily manage the HPA (Host Protected Area) and DCO (Device Configuration Overlay) settings in order to set the max address of a hard drive. The three below functions can be executed quickly and easily. 1. Set HPA address Establish HPA address restriction. After function is executed, [...]]]></description>
			<content:encoded><![CDATA[<div class='bandura_frame'><img src="http://blog.atola.com/wp-content/uploads/2011/12/hpadco-dco-set_thumb1_thumb.png" width="270" height="180" /></div>
<p>The Bandura (since <a href="http://atola.com/products/bandura/update.html">firmware version 1.1.5</a>) enables users to easily manage the <strong>HPA</strong> (Host Protected Area) and <strong>DCO</strong> (Device Configuration Overlay) settings in order to set the max address of a hard drive. The three below functions can be executed quickly and easily. </p>
<p><strong>1. Set HPA address</strong></p>
<p>Establish HPA address restriction. After function is executed, the ID sector will display any address set by the user (example: 500GB hard drive may be reduced to 250GB). </p>
<p><strong>2. Restore DCO</strong></p>
<p>Restores <b>all factory settings </b>of disk. If a max LBA address restriction is set, it will be removed and the ID sector will use the hard drive’s native max address.</p>
<p><strong>3. Restore HPA</strong></p>
<p>Removes HPA address restriction if it is set. After the function is executed, the ID sector will display the hard drive’s native max address. </p>
<p><strong></strong></p>
<p><strong>Bandura shows max LBA restricted in HPA and DCO </strong></p>
<div class='bandura_frame'><img src="http://blog.atola.com/wp-content/uploads/2011/12/hpadco-hpa-and-dco-set_thumb1_thumb.png" width="270" height="180" /></div>
<p>  <br/>
<p><strong>Changing HPA max address restriction</strong></p>
<div class='bandura_frame'><img border="0" alt="hpadco-set-native-max-address_thumb1" src="http://blog.atola.com/wp-content/uploads/2011/12/hpadco-set-native-max-address_thumb1_thumb.png" width="270" height="180" /></div>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.atola.com/hpa-and-dco-max-address-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

