Skip to main content

A pound of directories from about the FAT?

Microsoft are crowing about having patented the FAT filesystem, but like ShysterShylock from The Merchant of Venice, who was allowed his “pound of flesh taken from about the heart” from his debtor Antonio, but (as Portia pointed out) was not allowed any blood along with it, the patents don’t actually cover FAT itself, they only cover FAT32 and VFAT.

FAT itself is derived directly from CP/M’s braindead filesystem. It even has a directory layout with scars from CP/M’s FCBs (File Control Blocks, the in-memory representation of an open file). Except for the fact that the FAT32 extension seems “novel” and “non-obvious” to some lame-brain in the USPTO, I would have said that FAT itself is essentially not patentable.

Microsoft claim that they developed FAT for a standalone BASIC in 1976, but with its obvious CP/M heritage, it was not noticeably different from all of the other random filesystems floating around at the time, and Seattle Computer Systems (of QDOS fame) evidently didn’t have a problem with having built their own version of it (the descendants of which are today’s FAT code, since Microsoft eventually bought QDOS and renamedre-engineered it as MS-DOS).

On top of this, the much younger VFAT extensions have unquestionable prior art in filesystems like UMSDOS and Rock Ridge, which operate in an essentially indistinguishable fashion to provide long filenames and ownership information on short-filenamed and essentially attribute-free underlying filesystems (FAT and ISO9660, respectively).

So what devices are covered by the patents?

Anything which uses the VFAT extensions (practically nothing in the way of digital cameras and such) or the 32-bit version of FAT (practically everything with a worthwhile amount of storage).

That shouldn’t be much of a problem outside of the USA, since relatively few other patent offices are stupid enough to award such obvious and pre-empted patents.

VFAT is easy to work around, too. Since it’s been designed to be backwards compatible with FAT, files on a VFAT partition can simply be read and written under their 8.3 “real name”. FAT32 is harder.

Where the fan gets turned into a sewage pump is in the area of licensing.

The GPL prohibits the distribution of patent-encumbered code. Where I live, a VFAT32 filesystem is not covered by patents, and if the local patent office ever tries to be that stupid, we’ll simply nuke ’em with a trust Rusty. However, they are so encumbered in the USA.

What consequences for the GPL?

If you’re prevented from distributing code because it’s patented somewhere, all Microsoft needs to do is “buy” some little island nation and patent everything under the sun there. However, if the solution were so simple, they would already have done it. It’ll be interesting watching the luminaries sort this one out.

Comments

Popular posts from this blog

An Open and Shut response to Darl McBride

Hi, Darl. I see you’re being dishonest again . It’d be really nice if you could shoot straight for a change, but I think Kerry’s Dad will be selling snowplows in Hell first. Three years ago, when I first joined The SCO Group, we focused the company on the area that was most profitable and provided the most benefit to customers, investors, resellers, developers and employees: UNIX No, you focused the company on suing people, which was most profitable to lawyers and provided some golden parachutes for your buddies. People thought we were crazy. They were right. But since SCO owns the UNIX operating system The SCO Group does not own UNIX® in any sense of the word. The Open Group owns the UNIX trademark, definition and other rights , The SCO Group does not. The SCO Group doesn’t even own the UnixWare® or OpenServer® code, the rights to those are held by Novell and TSG use them only by permission and under certain conditions — which they have violate...

5x7 text dot-matrix in five minutes...

This is a fairly primitive toy I threw together today for a specific purpose, published in case it’s any use to others... feed it a list of words as command arguments, which it will then display as a 5x7 ASCII dotmatrix with ‘#’ as a dot & ‘_’ as a blank. /* * display text using a 5x7 bitmap font in ASCII letters */ static unsigned char font [] [5] = { { 0x00,0x00,0x00,0x00,0x00 }, // 0x20 32 { 0x00,0x00,0x6f,0x00,0x00 }, // ! 0x21 33 { 0x00,0x07,0x00,0x07,0x00 }, // " 0x22 34 { 0x14,0x7f,0x14,0x7f,0x14 }, // # 0x23 35 { 0x00,0x07,0x04,0x1e,0x00 }, // $ 0x24 36 { 0x23,0x13,0x08,0x64,0x62 }, // % 0x25 37 { 0x36,0x49,0x56,0x20,0x50 }, // & 0x26 38 { 0x00,0x00,0x07,0x00,0x00 }, // ' 0x27 39 { 0x00,0x1c,0x22,0x41,0x00 }, // ( 0x28 40 { 0x00,0x41,0x22,0x1c,0x00 }, // ) 0x29 41 { 0x14,0x08,0x3e,0x08,0x14 }, // * 0x2a 42 { 0x08,0x08,0x3e,0x08,0x08 }, ...

Citizens Augmenting Government Waste

So here we have Microsoft-funded “ Citizens Against Government Waste ” (CAGW) heavily criticising Massachusetts’s switch to an internationally accepted and open document standard (not open source, open standard — but I seem to remember a large monopolist who frequently confuses the two when it suits them). I remember CAGW, they were the organisation who had dead people writing in to support Microsoft in court a few years ago — thanks to sbergman27 for the link — is this “the dead hand of CAGW” at work again? Let’s follow the money and find out. Who stands to lose the most money and control if Massachusetts switches to an unencumbered document format? Big surprise, it’s CAGW sponsor Microsoft, through their dominant MS-Office suite. Why did CAGW list Microsoft’s suite last, after two other much-less-dominant examples which are waning anyway? If you’re inclined to wallow in additional irony, consider that at leas...