[DPlettner]

Glad to hear it is working for you.

It seems like DViCo could fix this easily by only using the good USB code. Of course, that would require the TViX to do a full boot when the cable is disconnected, but that is a lot better than data corruption.

-Dave

[erikreut]

Had a busy weekend, so didnt get to test transfers before now

I also concur with the findings... Having the USB cable connected at boot works like a charm! Noticed something weird, here's the 3 tests I performed:

1) Connect USB cable -> boot -> Transfer files = No problems!

2) boot -> Connect USB cable -> Transfer files = Bad! (-36 I/O errors on my Mac)

3) Connect USB cable -> boot -> Transfer files -> Disconnect USB -> boot finishes to menu -> Connect USB cable -> Transfer files = No problems - both transfers!

I was surprised by the result of my 3. test. Seems like the Tvix continues with the "good code" if you decide to transfer some more files after boot.

This was all done with the 2.0.8 firmware.

Yeay! Can finally use 2.0.8!

[DPlettner]

Originally Posted by erikreut 3) Connect USB cable -> boot -> Transfer files -> Disconnect USB -> boot finishes to menu -> Connect USB cable -> Transfer files = No problems - both transfers! I was surprised by the result of my 3. test. Seems like the Tvix continues with the "good code" if you decide to transfer some more files after boot.

I am surprised by number 3 too!

For your second transfer, did the VFD say "USB On" or something like "USB Connected"?

Another possibility is that the the "good code" does some type of hardware initialization that is missed by the "bad code", such as properly enabling error checking and correction at the USB port.

-Dave

[erikreut]

Originally Posted by DPlettner I am surprised by number 3 too! For your second transfer, did the VFD say "USB On" or something like "USB Connected"? Another possibility is that the the "good code" does some type of hardware initialization that is missed by the "bad code", such as properly enabling error checking and correction at the USB port. -Dave

Well, I was pretty sceptical about the 3rd test too, so I did it again - this time it failed. All 3 tests was done with a set of 26 files, app. 15GB data in all. This is the set I've been able to get it to fail consistently, guess I was lucky that one time with the 3rd test

Test 1 works every time, though - thumbs up for that!

I did notice too, that the storage device changes name from "Linux File-Stor Gadget Media" at boot to "USB Mass Storage Dev Media" when booted. This leads me to believe you're absolutely right Dave - they're using different code-paths depending on when you connect your USB cable.

I still recommend the 1.9.9 firmware for those who liked the gloomy-jet-black menu with nice errorfree transfers, than that of the fairy-white feng shui menu of the 2.x series As for me, I'm staying at 2.0.8!

Erik

[Exter]

Thats good news.

im glad you found a workaround for this problem as i didnt notice this before.

Its good to know im not the only one with this problem and hope they fix this in future releases

Good work !!

[Kei Clark]

Originally Posted by erikreut I still recommend the 1.9.9 firmware for those who liked the gloomy-jet-black menu with nice errorfree transfers, than that of the fairy-white feng shui menu of the 2.x series As for me, I'm staying at 2.0.8! Erik

I know this is an old post, but since you have a drive installed, have you tried just moving the jet-black menu art files to the drive so that you can use that UI with the latest firmware?