maximum File Migration size ?

[JohnBox]

Is 95 GB? How can I go past that limit? When migrating entire HDD contents with FTK imager I would certainly need TBs of file migration size.

Thank you.

[Peter2150]

IF as I suspect this is a disk imaging program, trying to image from within the Sandbox probably at best won't work. At worst...???

[JohnBox]

http://www.accessdata.com/support/product-downloads FTK is a forensic toolkit with lots of options for working with damaged drives as well as making to the bit copies of drives or scanning drives without leaving traces from the host OS or actually without infecting the host OS etc etc. Lots of scenarios, can only recommend it, also for everyday use.. https://ad-pdf.s3.amazonaws.com/Imager%203_1_4_UG.pdf

Would it be possible to break this 95GB limit with direct access to let's say another external drive and just put the drive letter or drive letter and folder?

[Peter2150]

I think you missed my point. I gather you want to try and copy the whole disk into the sandbox. My point, is looking at this program itself, I suspect it won't work in the sandbox. You might need to take the approach of installing it, imaging your system with a standard program like Macrium Reflect, doing whatever it is you want to do, and then restoring back to the prior state.

Pete

[JohnBox]

I must have misunderstood you or not understood you, yes.

I managed to get FTK running in a sandbox fine. The other day I was looking at a 1TB external drive from inside the sandboxed FTK. FTK has the option to copy or make an image of certain selections of a disk or the whole disk and write that to any location really.

So what I was wondering is, when I run FTK sandboxed and I give direct access to an extrernal destination disk where I want the extracted data to be written to, will I need the File Migration setting at all?

I am not trying to write all the content from the scanned disk to sandboxed FTK. FTK also always asks you where to save the extracted data, so I could actually save it to an external destination drive that is sandboxed as well with the Force Folder option, no?

Like that I don't need to worry about File Migration size and the data that is written to the destination drive is also kept there and only there, would that work and does what I say make sense?

Thank you Peter

[Guest10]

If a program is installed outside of any sandbox, and is then Run Sandboxed, giving the program Direct Access to a folder will bypass the File Migration setting for writes that the program makes to that folder - because all writes to that folder will take place outside of the sandbox.

However, if the program is actually installed inside of a sandbox, then to get the same results you need to use a "Full Access" (OpenPipePath) setting instead of "Direct Access" (OpenFilePath).

In either case, use the "Add Program" button to specify the program's .exe name on the Direct Access or Full Access screen, so only that one .exe program can use the setting. Otherwise, any program using that sandbox can make use of the setting.

[JohnBox]

Ok thank you will use this method next time there is an HDD to image or to backup files from it with FTK.