Hi Duivels
I think it's pretty clear that there is a major problem in the Realtek SDK4 with it's NTFS file system drivers. Have you managed to get any info out of AC Ryan as to what they are doing about it?
I have noticed there seems to be a bit of a lack of information from them again - on this, firmware, the future support for HD / Mini 1 devices etc.
Andy

I regret to say that information is scarce, not to say completely absent. In many ways moderators are treated just like other clients.
I suppose that Realtek is the real culprit and that AC Ryan, Mede8er, Egreat and others cannot but wait (till eternity?).

The error can also be forced with the 4824 (SDK 3) firmware, so probably it has not originated with the SDK 4 firmware. The indexing (scanning) option of the SDK 4 firmware has presumably aggravated the problem in comparison to the SDK 3 firmware because of the increased number of file writes.

I think you have a good point there Duivels re r4824. Looking at some of the other forums the NTFS drivers for the linux O/S seem to be the culprit. I think I'll stick to my NAS.
Anmdy

Did not know that windows could recognize ext3 with a driver, thank you.
But I can say that until now the alternative firmware has worked without problems.
I also have an asus oplay air (Realtek??) and never gave me these problems.
But the oplay air dont have dlna, nas, and i buy the ac ryan becose of this and they all give problems.
I can put all these functions and more in my oplay air with moservice but i give preference to original firmware.
First time i see acryan was in moservices

If you are sure your alternative FW no write errors does, you can explain the Script sometimes.
Script here.
However, use an empty HDD.

With moservice it can his of the mistakes is not there. If comes on it, what was changed.
To do this I would have to look in the moservice FW. I know what it is and know how one changes it. At least the called Test-Script runs with me perfectly.

And here are a zitat from moservice (by Transmission, but the error is not only with Torrents):
"It was found: a multi-threaded write to NTFS in the kernel player realized the error, as I have written repeatedly. "Thank you" says the author NTFS, holding the protocols and Realtek who chooses to use this system.
The solution for the moment only similar rtorrent: use for download EXT3 partition and move the completed download to NTFS."



Greeting Steffen

This problem is reported and under investigation by the developers.

Yes, this is what we keep hearing. The developers apparently know this for some time now. But what is the current status? Discussions with Realtek? Do the developers think they can fix it? As the SDK seems to be flawed, can the developers do anything at all? And is there a more or less official statement concerning the use of NTFS drives on PlayOn devices from the staff or management? Just "reported and under investigation" will not cut it.

Why have I found the mistake and qualified developers do not create it?

They get not to use the testscript, but they say cannot reproduce the mistake.

You may not think that are silly the users. (I mean with it not you personally kraakie, but your informants.)


Greeting Steffen

Well the problem is not everyone experiences this problems

I have a hd2 and a dvr-hd and the last time i had a file problem is about 4 months ago.

And that was because my router crashed.

So this makes the problem not easier to resolve.

I copy gigabytes of data to the hd2 and dvr and from the dvr-hd and hd2 to pc over the network Without problems and usb hdd to the players works fine here

I dont use torrents etc because the player is not super stable with torrents