View Full Version : Tricaster Updates a little Slowww ....

10-05-2016, 06:19 AM
And this is not the first time. Twelve hours on a 20 mb/s fibre. Reminds me of the 1990s. :)

10-05-2016, 09:55 AM
Thankfully the update speed improved, only six hours to download the update. But ...

The Tricaster being updated is a 460 Educational (Standard Edition) device, which has never seen an update since purchasing in early 2015. Downloaded the ‘Standard Edition’ update, which by the way had a ‘ADV’ logo on the left hand side of the dialog box upon install. Curious. Absolutely the standard edition was downloaded.

Well the Tricaster is now DEAD. No boot, nil nothing, nada, zilch. The version is Standard Version: 2-5-160706. Is this update applicable for the educational version of the Standard Edition. Not a good way to finish a day. Any thoughts?

Zane Condren
10-05-2016, 10:07 AM
There is no software difference between an educational unit and a standard 460. I would suggest you pull the power cord for 2 minutes then hold down the power switch for 10 seconds to see if it comes up.

10-05-2016, 10:59 AM
Thanks Zane. All good on the educational unit. Had never updated a Tricaster with that branding before. Sadly, the Tricaster has booted with the message "A disk read error has occurred". Now that doesn't look good at all, considering the primary drive is an SSD. I'll check the internal hardware connections tomorrow. The hour is late ... very late. Cheers for now.

10-05-2016, 09:20 PM
The message "A disk read error has occurred" was not caused by all the usual suspects in this case. Diagnostics in Win2Go reported no problems with the drive or its content. Running Samsung Magician revealed lack lustre performance with the SSD. Hmm ... the SATA Port, the cable or the connection. As it turned out, SATA Port 0 is intermittent in its functioning, so repatched to SATA Port 2. All is now good with the world.

Surprised to see no over-provisioning on the Samsung SSD. Only 50% of the SSD drive space is used. This does not bode well for the future, as memory blocks fail as they do. Perhaps something to investigate in the near future, and a way to facilitate this feature (fault tolerance) in the next updates. Cheers.