Slashdot Mirror


Microsoft to Charge for FAT File System

pario writes "According to Microsoft, the Redmond company is going to charge a license fee for any product that is formatted in FAT by the manufacturer. Any manufacturer of compact flash memory cards or digital cameras may end up paying Microsoft as much as $250,000 for the use of the file format. The FAT File System is covered by several US patents."

8 of 1,424 comments (clear)

  1. Charging for their IP by mOoZik · · Score: 5, Informative

    I see nothing wrong with it. They own the patents, so they have the right to sell it to whoever pays. BTW, slashdot post is a bit misleading.

    "Pricing for this license is US$0.25 per unit with a cap on total royalties of $250,000 per licensee."

    The $250K is the cap; that means, that is the maximum amount they will charger per license holder for the use of the FAT. Just thought it came across incorrectly.

  2. Prior Art for all 4 patents by Richard+W.M.+Jones · · Score: 5, Informative
    It's possible there's prior art in GEOS. Search down the page for "VFAT":

    http://www.vcnet.com/bms/departments/innovation.ht ml

    Rich.

  3. Re:Dammit, more Linux impact by barzok · · Score: 5, Informative

    As I read the license options, this applies only to devices that come pre-formatted as FAT. No mention of software. Limiting the ability of others to write FAT-compatible software would be a bad strategic move on MS's part - anyone who currently has another OS interoperating with Windows via FAT may be just as likely to ditch Windows as they are the "other" OS.

  4. RTFA and be careful with the FUD by dreamchaser · · Score: 5, Informative
    From the webpage:
    Microsoft is offering to license its FAT file system specification and associated intellectual property. With this license, other companies have the opportunity to standardize the FAT file system implementation in their products, and to improve file system compatibility across a range of computing and consumer electronics devices.
    Reading this and the rest leads me to believe that they are NOT preventing people from reverse engineering FAT. Rather, they are selling their 'true' implementation of the filesystem. Nowhere does it say that companies providing their own 'clean room' implementation of the FAT filesystem will have to pay.

    That doesn't mean they won't go there, just that they haven't yet. Still, the typical knee-jerk reactions here are as yet unwarrented.

  5. Re:can someone look over the patent please by Psyx · · Score: 5, Informative

    The validity of one claim typically does not invalidate the others. My patent lawyers call this a layered approach, where the first claims are purposely broad in an attempt to grab as much IP ground as possible. Subsequent numbered claims in the patent are become more specific. They take this land grabbing approach essentially because they can.

  6. Dammit, would people stop saying this? by jamused · · Score: 5, Informative

    "Microsoft needs to defend this patent lest they lose it."

    You're confusing Trademark law with Patent law; Trademarks must be defended lest they be abandoned, patents can be enforced against some, all, or none of those infringing on the patent at the patent-holder's whim. The entire practice of "defensive patents" rests on this.

  7. Karma whoring? by vrmlguy · · Score: 5, Informative
    Here are the patents' abstracts. They all relate to long filename support, so if you were willing to limit yourself to 8.3 names, you don't need a license. This is easly done with dedicated devices, since you just implement your own index file on top of the 8.3 names; this was a common technique back in the old FAT16 days.

    U.S. Patent #5,579,517 Common name space for long and short filenames

    An operating system provides a common name space for both long filenames and short filenames. In this common namespace, a long filename and a short filename are provided for each file. Each file has a short filename directory entry and may have at least one long filename directory entry associated with it. The number of long filename directory entries that are associated with a file depends on the number of characters in the long filename of the file. The long filename directory entries are configured to minimize compatibility problems with existing installed program bases.

    U.S. Patent #5,745,902 Method and system for accessing a file using file names having different file name formats

    A multiple file name referencing system stores multiple file names in a file. These multiple file names include an operating system formatted file name and an application formatted file name. When an operating system formatted file name is created or renamed, the multiple file name referencing system automatically generates an application formatted file name having a potentially different format from, but preserving the extension of, the operating system formatted name. The multiple file name referencing system similarly generates an operating system formatted name upon creation or renaming of an application formatted name. A B-tree is provided which contains an operating system entry for the operating system formatted name and an application entry for the application formatted name, each entry containing the address of the same file to which both names refer. The multiple file name referencing system converts the operating system formatted file name to the application formatted file name by accessing the B-tree with reference to the operating system entry, and vice versa. As a result, either file name can be used to directly reference the file without requiring additional file name translation.

    U.S. Patent #5,758,352 Common name space for long and short filenames

    An operating system provides a common name space for both long filenames and short filenames. In this common namespace, a long filename and a short filename are provided for each file. Each file has a short filename directory entry and may have at least one long filename directory entry associated with it. The number of long filename directory entries that are associated with a file depends on the number of characters in the long filename of the file. The long filename directory entries are configured to minimize compatibility problems with existing installed program bases.

    U.S. Patent #6,286,013 Method and system for providing a common name space for long and short file names in an operating system

    An operating system provides a common name space for both long filenames and short

    --
    Nothing for 6-digit uids?
  8. Re:FAT and CP/M and DR DOS Prior Art by kyz · · Score: 5, Informative

    The GIF file format isn't patented. You can't have a patent on file formats, the order of fields in a sector, etc. There is nothing innovative in that.

    The hardware process of the LZW compression algorithm was what as patented. You can write GIF files without using compression (literal, clear dictionary, literal, clear dictionary ... instead of following the compression algorithm.

    Here, Microsoft's patents relate to algorithms for fitting long filenames onto a file system that only supports short filenames. They do NOT have a patent on the (V)FAT filing system. However, in working with those filing systems you may need to use algorithms which Microsoft managed to patent.

    --
    Does my bum look big in this?