View Single Post
  #41 (permalink)  
Old January 31st, 2007, 02:06 PM
traut traut is offline
Eager Mistic Beaver
 
Join Date: May 2006
Posts: 287
Quote:
Originally Posted by Step666 View Post
You have completed missed the point.


The point is not that any transfer protocol will work with any file system, the point is that the user should have some say in it all.
I guess I got the point before. I did not mind for a long time - but since this thread goes on for a while, always sailing under incorrect subject, I finally wanted to point out that UMS vs. MTP is not a question of asking for different file systems.

... and I agree that the user should have a choice. In fact I don't see the need for a choice, since UMS would be god enough for any needs (I don't see any benefit from MTP here) - but it is exactly the way the clix was planned and developed NOT to support UMS, but to offer a tight integration to WMP11 instead. Since MS now builds MP3 players of their own, ignoring their former own standarf of Play For Sure, this may be discussed again - even providing multiple protocols in parallel.

In fact I do not know by now what the actual file system is. I would mind, if it would make any difference to me - and it makes a major difference e.g. for external USB hard drives, where I may use fat32 both on Mac and Win, but it sucks everywhere. I may read but not write NTFS formatted disks on the Mac, while HFS+ is not supported on Win. There are some 3rd party extensions around, which are more or less integrated and up to date.

So I checked by now - the Disk Utility just named File System: Generic or File System : MS-DOS File System

The System Profiler said:
iriver U10:

Capacity: 1.9 GB
Removable Media: Yes
Detachable Drive: Yes
BSD Name: disk3
Vendor Name: iriver Limited
OS9 Drivers: No
Product ID: 4118 ($1016)
Speed: Up to 480 Mb/sec
Bus Power (mA): 500
Serial Number: 6C0F590E0000

So I don't know much about the FS used here, but I guess it's a rather simple fat32.

In fact I was surprised that it did handle file names with 8bit chars very well (maybe UTF-support is supported very well from Korean companies). I tried a filename wit Äöß.txt. But the internal representation of text sucks (I don't need to select from languages here, but from a range of used/supported charsets instead) and does not show the characters I expect.
Reply With Quote