nothing happens on asus oplay.
just the pen dont stop working and had to shut down by remote.
But inside it has 2 files, tray.sh and x.4730.
And no windows warning.
I did something wrong?

Check the x.4730 file with a text editor or Wordpad, it is an ordinary text file which should only contain lines:

this is some text 1
this is some text 2

and so on.

If it contains anything else than lines with "this is some text" followed by the number of the iteration, it has been corrupted.

ok, this was there.

*edit*
this is some text 3
.
.
this is some text 400

where are the lines with:
this is some text 0
this is some text 1
this is some text 2

chkdsk work better if the USB-Pen in the PC is connected and then you boot up Windows.

Is on your asus oplay original FW or moservice ?


Greeting Steffen

there is no
this is some text 0
this is some text 1
this is some text 2

in there

its asus oplay original FW.



Second time i tray.

However, these lines must be there. If not is a mistake.

And you cannot take cat filename directly. filename must be exchanged with the file names you under ls out has found. In your example cat x.4730

just as with kill prozessnr prozessnr the number is in your file behind x stands. In your example kill 4730

The numbers are always varied, so next time not simply cat x.4730 or kill 4730 use. Special provisions with ls Now look at how the name reads.


Greeting Steffen

The lines are not there.
And I'm just trying to help because I do not know anything about scripts, or linux.
All I know is press buttons

Then make your asus oplay also error. Just not quite that bad, and it then takes a little bit longer until files are affected by it.


Greeting Steffen

this happens if i tray again

Venus login: root
warning: cannot change to home directory


BusyBox v1.1.3 (2011.05.25-05:45+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ # mkdir /tmp/usbmounts/sda1/try
mkdir: Cannot create directory `/tmp/usbmounts/sda1/try': No such file or direct
ory
/ #
/ #

Never mind the Linux.

There is only one conclusion: your Asus contains the same bug, because the x.4730 file is corrupt, the first 3 lines are not there.

It does not take a little bit longer, it appears immediately after the script has started.

And if you want to try again:
After you have logged in, just after the / # prompt type:
/tmp/usbmounts/sda1/try/try.sh &

then , after you have stopped the process check the x.<number> file again. Disregard the x.<number>.tmp file, if that exists.