Guidance bought Tableau

Interesting…. I certainly think Guidance had fallen behind with their hardware and software imaging capabilities.

All it will take now is for AccessData to acquire Guidance and the industry will have eaten itself!

All it will take now is for AccessData to acquire Guidance and the industry will have eaten itself!

lol

I winder what will become of Wiebe Tech?

I am not sure if I am happy, that they get something good for their hardware, or worried how the market is consolidating…

I am not sure if I am happy, that they get something good for their hardware, or worried how the market is consolidating…

signed

Certainly harder to see the upside from the end users point of view

Considering I currently tend to use Tableau blockers with FTK Imager (although with TIM fixing the naming conventions, I may look at changing) so I'm hoping Guidance has the good sense to leave the hardware guys to themselves. On the other side, it would be nice if Guidance could have them make some of the OEM bridges more widely available. I have friends at Digital Intelligence, but them being the only shop with access to the "Ultrabay II" is a bit ridiculous.

My biggest concern is the future of TIM. I used v.1.0 even though you couldn't alter the image name at all. Thankfully, as Tony noted, v.1.1 changed that issue. The speed increase using TIM over FTK Imager was dramatic. The slowest speeds I've observed using TIM with firewire in and out is 2.2GB/min. Hopefully, Guidance will continue to develop TIM and not kill it off.

I use and love TIM everyday (and will at 5pm today for another two field collections). I really hope it does stay an independently developed product aimed at collections. The logging is great and I have to say I am a sucker for a pretty and easy to use GUI.

However, I am having one issue. I collect to different target volumes from case to case on the same systems. If, for example, I collect to E\cases\evidence\test1 on one case and then x\cases\evidence\test2 on another. Then transfer the evidence to the preservation, production archive or whatever and delete the "test1" and 'test2" folders. If I go back into TIM after those folders are removed - TIM recreates the folder structure. Not real problem but really annoying when I am opening and closing things and multi-tasking as it can be a bit confusing as to why case folders are showing where I don't expect them. I worked around this by removing the timjobs.xml and Timager.xml files from the C\Program Files (x86)\Tableau\Tableau Imager directory.