I raised a support ticket for this. No answer. Mine has been running for 4 to 4 days now. I don't think it has a processor. I think it's got old valves. Seriously, I saw another thing that I haven't tried yet and that was a suggestion to use handbrake on a different machine. I don't know what effect interrupting the transcoding would have? I asked when I was asked to chkdsk my drive. No response yet.

It's 13855. I've taken the actions of the support engineer (Adam) and it's not helped resolve the problem. I guess it has hopefully ruled out the disk. I have noticed during transcoding, that the percentage complete goes way way beyond 100%. Perhaps thats a clue? In any case, I'd call it a bug.

Since you have seen fit to investigate with me, can I suggest you run a group of beta testers if you don't already. In that way, you could buffer yourself from a lot of grief. I used to run a new product introduction group, so I have experience in this area.

I do only have a few days to return my system to Firebox, so I have a vested interest in you figuring this one out asap. I'd really like to keep the device and my wife is upset as it was an anniversary present. She feels bad for getting me a duff present! I was going to distribute my sons wedding photos with all his friends for him. 100+ people were expecting to see this whizzy new device I was banging on about. Thats what I meant in an early post about bad news travelling faster.