<?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>Proactive Discovery &#187; EnScript</title>
	<atom:link href="http://www.proactivediscovery.com/category/blog/enscript/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.proactivediscovery.com</link>
	<description></description>
	<lastBuildDate>Sun, 27 Jun 2010 06:10:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>EnScript :: Long File Path export</title>
		<link>http://www.proactivediscovery.com/2008/10/enscript-long-file-path-export/</link>
		<comments>http://www.proactivediscovery.com/2008/10/enscript-long-file-path-export/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 01:05:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[EnScript]]></category>

		<guid isPermaLink="false">http://www.proactivediscovery.com/?p=44</guid>
		<description><![CDATA[Hello everyone &#8211; I thought I share a little EnScript I wrote which deals with long file path export issues. The script I wrote basically does the following: This EnScript plug-in is used to identify and export entries which would exceed the path depths limitations of 245 characters during a normal export. The script will [...]]]></description>
			<content:encoded><![CDATA[<p>Hello everyone &#8211;</p>
<p>I thought I share a little EnScript I wrote which deals with long file path export issues. The script I wrote basically does the following:</p>
<p>This EnScript plug-in is used to identify and export entries which would exceed the path depths limitations of 245 characters during a normal export. The script will loop through entries that are blue-checked and exports entries which exceed the above limit based on the FullPath column and the specified export path.</p>
<p>The script will export entries that exceed the 245 character limit. Once exported it will also &#8220;uncheck&#8221; them. This should leave you with items you can safely export using the native EnCase Copy Folder&#8230; function.</p>
<p>The script will create a subdirectory called &#8220;pathdepth&#8221; inside the user specified export folder and export data using the Logical Size of an entry. In addition a log file is created which contains the reference to the original entry details.</p>
<p>Since the script generates a flat export, it renames the files with a prefix to guarantee uniqueness. This prefix is actually the MFT record number on NTFS volumes (File Identifier).</p>
<p>Please report any bugs or suggestions to <a title="EnScript Support" href="http://www.proactivediscovery.com/contact-us/enscript-support/" target="_self">EnScript Support</a><strong></strong></p>
<p style="text-align: center;"><span style="color: #ff6600;"><em>Developing, maintaining and hosting this content does take time and financial resources.  Your support is much appreciated.</em></span></p>
<div>
<form style="text-align: center;" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<input name="cmd" type="hidden" value="_s-xclick" />
<input name="hosted_button_id" type="hidden" value="1711200" />
<input name="submit" src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" type="image" /> <img src="https://www.paypal.com/en_US/i/scr/pixel.gif" border="0" alt="" width="1" height="1" /><br />
</form>
</div>
<p><span style="text-decoration: underline;"><strong>ver 1.0.31 : 22 September 2009</strong></span><br />
+ (fixed) total byte size of selected files keeps increasing if going back and forth with new destination path<br />
+ (fixed) split file type extension into own column in export log<br />
+ (fixed) exclude case name in path upon export<br />
+ (fixed) remove CaseName from path calculations<br />
+ (fixed) add original file name to export log<br />
+ (fixed) uniform export format: with MFT FileIdentifier available (file.ext_id.ext), without MFT FileIdentifier availabe (file.ext_hash.ext)</p>
<p>The EnScript can be downloaded here: <a href="http://www.proactivediscovery.com/wp-content/plugins/download-monitor/download.php?id=4" title="Downloaded 180 times">Long File Path Export (32.93 KB, 180 downloads), version: 1.0.31</a> (updated 09/22/09) (Requires EnCase 6.11.2)</p>
<p><span style="text-decoration: underline;"><strong>ver 1.0.9 : 10 October 2008</strong></span><br />
+ added MD5 hash value to the exported file name if no MFT file identifier is available.<br />
File Identifier is only available if the MFT is within the evidence file. In case of a LEF<br />
that doesn&#8217;t have the MFT, it shows a zero.<br />
+ added check if entry is folder. Folders are not considered for export.</p>
<p>This script was written and tested in EnCase v6.11.2. Please keep in mind that his is the first (beta) version.</p>
<p><span style="font-style: italic; font-weight: bold;">NOTE: No guarantee is made that this EnScript is error free. Please use at your own risk and validate your findings.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.proactivediscovery.com/2008/10/enscript-long-file-path-export/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
