Dear thajyeeb and others
I have used the chkflsh method very successfully on some slim players but on my version of your player (depicted on home page) and the very similar "3 button" type they still report as 32 gb.
What may be relevant is that they both appear to present not only two drive letters to the o/s but that partitioning utilities regard them as two separate physical drives. The first drive is set as the faked 32gb, the second drive as zero size.
Using mydisktest I can get it to create the xbadsect directory and the o/s matches the remaining report (only 1.9 from 32 available, took ages).
Perhaps this is where I am going wrong, if I run the instructions as above (with only the default "bad blocks" option checked) then it just zips through saying all 32gb are fine. I think the instructions should be ammended to:
2A check "do full scan" and also "test if downgrade" options then press the main "test the drive button". Warning this will be very slow, several hours.
At the end of that test opt to lock out bad blocks. Warning this will be even slower, suggest leave running overnight.
[I went through exactly as per your instructions the first time and then as my version, no difference]
Either way Chkflsh opens up as expected (it also shows the null drive as a seperate pysical device rather than a simple second partition ), running the slider down below 1.9 gb on the hacked drive and proceeding as instructed has no effect.
Any ideas as how to proceed? I have some feeling that it is linked to the aspect of the "zero" drive but I cannot fathom how to eliminate it.
I wish I had been sent a version with as much as 4gb!
Does anybody have any experience of operating these with micro sd cards? Do they operate in a stable manner and as you would hope? Can they use any more than a 4gb card? the printed spec suggests 8gb but I'm sure I have read somewhere that the chipset used does not address more than 4gb.
|