Tableau has identified a problem with the T8-R2 writeblocker which can result in data being written to certain devices if the T8-R2 is connected to the host system via USB. It is essential that you go to this page on the Tableau website and download the latest firmware and install it on your T8-R2 (http//
TFU v6.84 introduces a firmware fix to correct the issue.
Please note this is a critical firmware update. All T8-R2 users should update the T8-R2 firmware to TFU v6.84 immediately.
The T8-R2 is the sole model affected and only with a USB host connection. The problem doesn’t exist with a Firewire host connection.
If you have problems updating your T8-R2 with this latest firmware please call Bernie on 01296-621121 or email him at Bernie@dataduplication.co.uk.
What is worrying is that I had to learn of this from places other than Guidance or Tableau.
What is worrying is that I had to learn of this from places other than Guidance or Tableau.
Do you have this particular model?
If so, did you register at Tableau for software updates?
As far as I know, they (Tableau) are very keen on informing their users - I once attended a presentation by Robert Botchek who pointed out that situations like this one are exactly the reason why they need you to register using your email address.
I can imagine they focus their communications on customers who they know have this particular model - but not sure.
I have registered for software updates and don't have this model - so I assume that's why I didn't hear anything.
Agree with Jelle here. Tableau have handled this reasonably well - I got my email update on this issue from Data Duplication at 1005 this morning, though the quickest way Tableau could've informed the maximum amount of people would be through their Twitter feed http//
No hardware or software is fool-proof. This is probably a timely reminder of why tool verification by the end-user is necessary.
Actually something else worries me a bit more . . .
Why is a hardware write-blocker needs a software to fix a writing issue?
Actually something else worries me a bit more . . .
Why is a hardware write-blocker needs a software to fix a writing issue?
Sorry for stating the obvious - because there is software (/firmware) inside ) It's not some sort of diode.
Again, Robert Botchek's presentation on this at F3 was excellent and gave a good explanation on how these devices work - I'll see if it's available somewhere online (it might be on the F3 website).
[update]it's indeed on the F3 website - don't know if you are a member? If so, login and find it in the 'downloads' section[/update]
Jelle, thank you. You do not need to look the document up, as I know intimately how a write blocker works.
The question was rhetorical.
Jelle, thank you. You do not need to look the document up, as I know intimately how a write blocker works.
The question was rhetorical.
I'll pretend I noticed that and my answer was ironic 😉
Actually something else worries me a bit more . . .
Why is a hardware write-blocker needs a software to fix a writing issue?
Jelle, thank you. You do not need to look the document up, as I know intimately how a write blocker works.
The question was rhetorical.
Maybe not-so-loosely connected to the sad fact that nowadays a number of TV's run Linux 😯
JFYI wink
http//
jaclaz
IF the bug only relates to a very specific set of circumsatnces, than thise circumstances should be communicated staright away together with the update. Without this, how is anyone meant to know if they are required to back track and review any of their previous cases.
An email without these specific details but just stating that under some circumstances, the device does not block clearly plays into the hands of any assertive defence who want to use smoke and mirrors (or a genuine concern) and put an element of doubt into the juries mind. They just want to know whether the write blocker blocks or not. I know that we know that it's a complex question but e-mails like this do not help.