D AccessData announced the FTK3.0 this past week and I have to make this posting to the people who are wasting their time running FTK2.x and EnCase. AccessData has released a V3 Product which I think has the fastest processing engine available. I used EnCase for years in Private Industry from V3 until V5, and AccessData 1.x until now 3.x. I am here to tell you folks that if you need to cut your processing time by 2/3, then try this product,. AccessData V3 is 'Awesome'. My case processing time is cut at least by 2/3 with V3. There is a new processing engine that has speeded up the process. I finished (4) cases in the last five days. My average processing time for a 200gb HD including Indexing, decompressing compound files (.PSTs) is 4 hours. New options in the index search area parses out types of documents. When you key in an indexed search term, it will find the keywords and tell you if the keyword is in a document, spreadsheet, OS, Email (what-ever). Enough of my ranting….. go get AccessData V3,, check it out. If you are running V2, load v3,, it's worth it!
What type of specs in your Forensic machine running? Are you using the Oracle Booster?
how to run the Oracle Booster?
Go here for Oracle Adjuster walk-through. http//
In first column of webinars, Core Forensic Analysis, you'll see "Oracle Adjuster Utility and UI Performance Tips". That will walk you through using he utility.
You can download the Oradjuster utility from the support page http//
This just in…
Hey Mr.Cyberguy - welcome to FF.
1st post and an 'awesome' review of a new version of a product from a supplier whose release of their previous version was corporate suicide….
I'll try it out as I have belief that the good old days can come back. Thanks for the heads up.
I must agree, FTK v3 is outstanding. Access Data did lose some credibility with the release of a less than functional v2. Version 2.1 really helped….But v3 is great. Version 2 was not corporate suicide. V3 has more than made up for any loss. There's a reason most of the Guidance Software people "migrated" to Access Data.
Hey Mr.Cyberguy - welcome to FF.
1st post and an 'awesome' review of a new version of a product from a supplier whose release of their previous version was corporate suicide….
My thoughts too…and the post after yours is…well… similar.
I look forward to the opinions of some of the known posters on this and other boards on FTK3. Can't test it myself as yet due to Oracle non-compatibilty with Windows 7.
Call me a suspicious cynical old cop with 30 years experience as a detective but I find Mr Cyberguy's praise of FTK3 a little too fulsome.
I broke one of my cardinal rules of not installing new software until at least six months after release by installing FTK3 last week (something I hadn't done with FTK2 - waiting for 18 months).
Install went without errors but I tried to load an image into a new case and got the helpful error message "error loading image".
One of my team didn't get the error and managed to load the image and it started indexing, for ten minutes at least until it crashed and closed FTK3.
Another member of the team not yet advanced to FTK3 did a search in FTK2 and found that it returned hits in FTK's own metadata. It appears FTK creates metadata relating to items in the image and then indexes its own metadata. I'd like to think it was a good idea to index evidence not something that FTK makes up itself.
I am less impressed than Mr Cyberguy.
H
Another member of the team not yet advanced to FTK3 did a search in FTK2 and found that it returned hits in FTK's own metadata. It appears FTK creates metadata relating to items in the image and then indexes its own metadata.
I ve seen this before, I think I was trying in vain to validate the hit from FTK in EnCase. Im not sure if what I hit on was quite the same, but the raw hex view offered by FTK had its own internal html tags contained within it.
No comments on FTK3 from me, Im still on 1.81 after 2 locked me out of my Oraclel database. oops