Microsoft to charge for FAT technology


Recommended Posts

from dp review, Dec 4, 2003

Microsoft will soon be charging manufacturers of flash memory card devices and those which use them $0.25 per unit or up to $250,000 to use the FAT filesystem. For those who are unaware the FAT file system was developed by Microsoft back in 1976 and has become the standard file system for all digital still cameras. Microsoft owns patents to the FAT File System but for many years hasn't even hinted that it may one day decide to charge for it. These new licenses appear to come into effect immediately and specifically make mention of 'compact flash memory cards' and 'portable digital still cameras'. What a great way for Microsoft to cash in on the most popular consumer products (as if they don't make enough money already).

I could understand M$ charging the camera manufacturers a fee, but charging the memory card manufacturers a fee is equivalent to charging floppy disk manufacturers the same kind of fee. The memory cards can be formatted in any format (I've formatted one HFS, and even NTFS before), but it is the CAMERA that is doing the formatting. If M$ chooses to do this, the simplest thing for card manufacturers to do is to simply ship the cards unformatted. Most cameras will offer to format them the first time they are inserted.

Here is a list of step Microsoft likes to use to make easy money....

1. Release something useful for the general public to use

2. Allow people to use this technology for free without any strings attached

3. Wait for this item to become an industry standard

4. Now attach some strings and make everybody pay money you for the use of this now industry standard technology

5. Watch the money roll in, or watch the industry standard switch

See how easy that is :D

i don't see the big deal.. first it is microsoft's technology to do with as they please... second, like stv said, it is only $0.25 per unit... *shrugs* then again, i do not own any of the affected pieces of equipment or the companies...

it's like GIF images before that expired

and in fact i don't think that MS have any claim on this 'FAT' technology because their 'FAT' technology was a filesystem that worked on hard drives, this is an implementation that resembles the same method of transfer as FAT, but because it's on flash memory, it physically is different

I own the following products that use the FAT file system technology:

- Lexar Media SD Card (64MB)

- SanDisk Cruzer Drive (128MB)

- SanDisk SD Card (256MB)

- FujiFilm FinePix A303 Camera (w/ 16MB xD-Picture Card)

I am not sure as to whether these products apply, but I would not mind paying the extra fee.

Please correct me if I am wrong, and also list any other products that might be affected.

Yeah, and the cap on this is $250,000 from what the post says. I don't really know that for sure, or if that is out of context, but usually there is a max cap so you don't have to pay like a billion dollars just because you mass produce products. $250,000 is nothing to these companies that manufacture the hardware.

it's like GIF images before that expired

and in fact i don't think that MS have any claim on this 'FAT' technology because their 'FAT' technology was a filesystem that worked on hard drives, this is an implementation that resembles the same method of transfer as FAT, but because it's on flash memory, it physically is different

a file system is a file system is a file system. It doesn't matter what media it is on, it's formatted the same way with FAT. That's why you can't read a disk or disc formatted for HFS in Windows. You can make your OS convert the information if you want, but that's a different story.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!