Page 1 of 1

There may be corruption with this update! PleaseDO NOT USE!

Posted: Sat Jan 07, 2012 12:57 am
by Sequenzzer
synthjoe wrote:Latest OS for the V3 (6 voice MOSS option) is 3.1.2 here.
After downloading this and upgrading from version 3.0.0 to this version,after reading all the nightmares concerning failures in upgrading and having interruption in power,I checked my disks THREE times to see that they would read properly.

Imagine my heart sinking in my chest when after throwing in the first disk I get the normal message "erasing rom" and it starts to install a file,then there is a disk error,could not read this file!!! I know the disks were ok since I checked them so many times before I started. Of course trinity now has a blank blue screen after I turn off and on. So now I am royally screwed as far as I am concerned. CHA CHING CHA CHING.....

But I on a panic whim and figure I can't hurt it any try and get version 3.1.1 which I do...How VERY HAPPY I am to report that upon resetting the trinity,it allowed me to boot from and install THIS version on the same EXACT disks I used for the update that failed,and that everything is back to normal,and I have a working trinity again on 3.1.1!!

Which leads me to believe that there is a problem with that os file on that link being corrupted somehow.

Can someone verify this?

Thx!

Re: There may be corruption with this update! PleaseDO NOT

Posted: Sun Jan 08, 2012 2:34 pm
by 3 fingers
Sequenzzer wrote:Can someone verify this?
I started by using my Trinity to format the disks required. Then I copied the update files to the disks using my PC. Then I installed the update to the Trinity. It worked flawlessly.

Re: There may be corruption with this update! PleaseDO NOT

Posted: Mon Jan 09, 2012 1:15 pm
by Sequenzzer
3 fingers wrote:
Sequenzzer wrote:Can someone verify this?
I started by using my Trinity to format the disks required. Then I copied the update files to the disks using my PC. Then I installed the update to the Trinity. It worked flawlessly.
Thanks,3 fingers! Don't know what the problem is,but from what I understand,3.1.2 is a minor update from 3.1.1 which worked for me,so it stays...

Thanks again for verifying this!