Slashdot Mirror


Microsoft Expands exFAT Multimedia Licensing

alphadogg writes "Microsoft Thursday announced a broadening of its licensing program around its exFAT file system, which is designed to handle large multimedia files. Microsoft hopes companies making devices such as cameras and smartphones will adopt the Extended File Allocation Table (exFAT) technology to support the sharing of audio and video files. The technology is available on Windows 7, Vista SP1, Windows Server 2008 and Windows Embedded CE."

10 of 181 comments (clear)

  1. Why? by Teun · · Score: 3, Interesting

    Why, when you can pick up ext2 for free?

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    1. Re:Why? by peppepz · · Score: 2, Interesting
      What about UDF? It's already supported out of the box on removable media by Windows Vista and higher.
      Open standard, tons of features, fast on flash media, broad adoption by existing operating systems and devices.

      They should use it instead of inventing yet another file system with less features. And closed, too (so much for Microsoft's commitment to interoperability and open standards).

    2. Re:Why? by oglueck · · Score: 2, Interesting

      Well, the CD-ROM standard they support is "Joliet". Which is their own extension.... I wonder how long until they are going with patents after others implementing it.

    3. Re:Why? by peppepz · · Score: 3, Interesting

      Of course! But starting from Vista, it's supported on all other media, too. So what's the need for exFat? I think UDF might cover all of exFat's use cases, with no patents pending and secret specifications involved.

    4. Re:Why? by Anonymous Coward · · Score: 1, Interesting

      There's nothing wrong with naming a directory "Family Photos 25.12.2009." - if Joliet didn't exist, we'd have to burn that to CD as "FAMILYPHOTOS25122009".

      Wrong. You COULD use rock ridge -- http://en.wikipedia.org/wiki/Rock_Ridge . Of course microsoft prefers to come up with its own thing.

  2. Re:I smell DRM by Anonymous Coward · · Score: 2, Interesting

    No, it's because everytime I come near a machine running windows, I lose around half of my nerves from all the

    -EULAs,
    -"Yes, please send all my personal data to Microsoft and/or McAffee, Delle, Evilcporp"-checkboxes,
    -"YOU ARE A THIEF UNLESS YOU PROVE OTHERWISE"-'advantage'-dialogs,
    -"Logging off"-Screens that stay on for 10 minutes before the computer shuts down
    -"There are important updates", "there are more updates, "are you sure you want to do this", "I have a message" "ballons"
    -"No you can't connect more than a single person via RDP, it's not allowed"
    -"what do you mean 'virtualize'? Do you have a license for that ?"
    -"Updating media player? Give us access to all your stuff"
    -"non-localized EULAs"
    -crashes
    - Start your computer? Wait 15 minutes to go through through some updates.
    - "Your Visual Studio 'forgot' how to display the search/replace dialog ? Why don't you reset all the personalizations you made, or start with a fresh profile?"

    At this point I decided that I that really valued my sanity, and quit my job developing for .NET.

    "Have some faith he" said...
    "what's wrong with licensing?" he said..

    "If we wanted Microsoft to 'donate' their software for 'free'" he asked.
    No. Not really, me personally I am trying not using their stuff, and I am successfull not even being anywhere near it atm.

    However I want Microsoft to 'donate' for 'free' dataformats they are using so that all of us could exchange data, and if we didn't like an application or one wasn't available for our platform that was using said format, we could write our own. And maybe if it was better than theirs they could say, "Hey look at what that bloke is doing, maybe if we would ask nicely, he would let us integrate parts of his functionality into our own application", and then I would say "Yes sure, I was also liking that one feature there, could I maybe also...? " and then they would say, "yes sure, why don't we invite this developer over there as well ?"
    And then we could develop the stuff we need together and get to do much more of the dataprocessing done that we actually want to do, instead of fighting over stupid licenses or writing complicated copyprotection-software that never works.

    A man can dream....

  3. Re:EEE by rtfa-troll · · Score: 5, Interesting

    EEE only applies to open standard Microsoft targets.

    It also applies to Microsoft partners. The multi-media product manufacturers (including cameras, media players etc. etc.) will be the long term target. Right now their functionality is being extended with the aim of Microsoft getting lock in. Microsoft is already one of them (with it's Windows Mobile phones and XBox at least). Later, when they need to expand their market, they will wipe out the multi-media companies that have become locked in.

    The thing is, and I know this from working in a potential victim company and discussing with the person who was negotiating with MS for media standards, that the extinguish is at least five years away. Almost nobody working in such a company cares about that far in the future.

    Only companies, like Oracle, which decide to fight Microsoft from the beginning as hard as they can, will ever survive long term in such a market.

    --
    =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  4. Re:Latest in a long line of suck by dargaud · · Score: 3, Interesting

    FAT looks like someone's half-baked science project.

    Quite so. I remember writing an experimental filesystem for 3" (not 3 1/2") floppies on the Oric in 1982, making up my own concepts as I had no experience in the matter. It didn't really work but it wsa good learning. Then a couple years later I looked at the details of FAT and was surprised by how simple, similar and limited it actually was.

    --
    Non-Linux Penguins ?
  5. Re:Microsoft and Making Money by vrmlguy · · Score: 2, Interesting

    Since exFAT apparently is referenced in the SD standard, people will be forced to use it, if they buy any consumer electronic device containing an SD slot. They can't choose not to use it. It's a hardware standard.

    So after exFAT, they won't be able to do what they do today, that is, freely exchange their media among their devices at their will. That's evil, and once again, it comes from Microsoft.

    Is there any reason why you can't use UDF on flash media? It's designed for media that wears out with too many writes, so it seems like a perfect fit. And recent (since ~2000) versions support Unicode, so you can use Tengwar Sindarin for your file names.

    --
    Nothing for 6-digit uids?
  6. Re:Microsoft and Making Money by Anonymous Coward · · Score: 4, Interesting

    > Unless Microsoft somehow coerced the association to select exFAT

    Of course they did.

    Microsoft do not support third-party file system drivers. It's certainly possible to write them, but documentation is scarce, there are few tools available, and it's intended for use only in embedded systems. It's not possible to provide the same level of integration as the Microsoft-provided drivers, since none of the disk management tools are extensible by anyone but Microsoft. The IFS drivers themselves are far more complicated than filesystem drivers in any other operating system, since they have to implement functionality that is normally provided by the operating system's VFS layer, and that functionality isn't well documented. Basically, all existing third-party IFS drivers suck.

    The SDXC committee needed the memory cards to be usable on Windows, ideally without installing any drivers, and without having to screw around to get it to work. NTFS is completely unsuitable for flash storage, and is far too complex to implement in an embedded device anyway (not that Microsoft actually license any part of NTFS out to third parties anyway).

    That leaves UDF, which can not be used on anything but optical discs in Windows XP, FAT16, which can't be used for drives larger than 2GB, and FAT32. FAT32 can actually scale well into the terabyte range, but Windows will refuse to format a disk as FAT32 if it's larger than 32GB.

    Microsoft's solution was exFAT. The selection of exFAT instead of FAT32 was forced by limitations on Windows' FAT32 support. These limitations were intentional - the idea was to get people to use NTFS instead of FAT32. The only party to benefit from this situation is Microsoft - they get to sell licenses for their (apparently) patented new filesystem, which they can't do with FAT32 (cameras never used the patented VFAT extensions). In addition, they get to kill off one of their own filesystems, which was being used as a common interchange filesystem between completely different systems, none of which needed to run Windows, or use any Microsoft technology.