@TetiSoft
Quote:
When the player doesnt contain important data and has
an option to format the medium in case he cant understand it,
I'd simply try to partition and format the medium from some
OS which knows how to create a valid MBR, e.g. Linux or Windows,
and not the builtin player firmware...
Ok, got some guts and repartitioned the Swimp3 drive (with fat16 as per manufacturer's recommendation).
Used linux for this (x86). Now fdisk doesn't wasrn about anything.
Plugged into A1 and it sees it (with either usb stack, final and july's).
Copied some files, relabeled the device, and it even plays the files afterwards
Huge thanks
Now the IRiver T10:
fdisk reports
aetpy:~> sudo fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 1045 MB, 1045430272 bytes
33 heads, 61 sectors/track, 1014 cylinders
Units = cylinders of 2013 * 512 = 1030656 bytes
Disk identifier: 0x6f20736b
usb.log:
I: [6FF6BEA0][hub.usbfd] | Hub port | Device found on hub port 2.
I: [6FF6BEA0][hub.usbfd] | Hub port | Device at port 2 is full-speed.
I: [6FF6BEA0][hub.usbfd] | Hub port | Device on hub port 2 succesfully added.
I: [6AFD8C90][USB Fkt Init] | Init Fkt | Fkt 0x6AEABCD0 is {Vendor: 0x0241, Product: 0x1310, Class: 00.00}
I: [6AFD8C90][USB Fkt Init] | Init Fkt | Fkt 0x6AEABCD0 initialized
I'm affraid partitioning it using mbr will prevent firmware reading it. Gone to try it anyway...
Edit:
Partitioning with MBR didn't help, the only setup the firmware accepts is as fat16 partition taking over the whole space (no MBR).
Anyway, freshly formatted (from linux) mbrless device still suffers from the same symptom.
Not even a blink in USBMassStorages commodity.
How do I manage to attach it to a usb device driver?
BTW: the product is reported as of same class as mbr-ed SWIMP3.
TIA
Jack
Edited by Jack on 2008/1/15 1:13:36
Edited by Jack on 2008/1/15 1:14:37
Edited by Jack on 2008/1/15 11:46:01