Slashdot Mirror


No Office For Linux, MS Patents Rejected

Bays Fil wrote to mention a ZDNet piece discussing the U.S. Patent Office's rejection of two Microsoft patents on the FAT file system. "There has been concern that if the FAT patents are upheld, Microsoft may claim that Linux infringes on Microsoft technology and will seek a royalty. Any monetary compensation could threaten the operating system, which under General Public License (GPL) terms may not be distributed if it contains patented technology that requires royalty payments." Relatedly, Dayrl writes "Microsoft reiterates its firm decision not to offer its Office Suite on Linux anytime soon. From the article: 'Microsoft is 100 percent focused on Windows: We have invested billions of dollars in it. We have created Office for the Mac but--and I thought I had been clear on this already when I said 'No'--we have no plans at this time to build Office on Linux,' Nick McGrath, Microsoft's head of platform strategy said.'

15 of 422 comments (clear)

  1. More media inaccuracies by operagost · · Score: 5, Informative
    It would be nice if a mass-media publication would just ONCE publish a 100% accurate article.
    Though developed for Windows, the FAT format has become a common means of storing files on all manner of computers
    FAT was developed for DOS 2.0. I suppose you could say it even existed in 1.0, but I know that filesystem lacked a hierarchy so it may not apply.
    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
    1. Re:More media inaccuracies by Waffle+Iron · · Score: 4, Informative

      Well, the VFAT with long filenames, which is the subject of these patents, was developed for Windows95.

  2. Re:what about WINE? by aphaenogaster · · Score: 3, Informative

    Been using crossover for years now. Works great, just a couple of little funky keyboard issues. I actually ssh -X my fedora wine session onto my Sun Workstation. Best of all three worlds.

  3. Re:the .doc format by ylikone · · Score: 2, Informative

    Microsoft has not given the right for OO to use doc format... and they are NOT using doc format. They are using something has been reversed engineered from doc! It is not fully compatible with Office doc format... it is not the same thing.

    --
    Meh.
  4. Re:why feed the competition? by tomstdenis · · Score: 2, Informative

    I think you'd find legit professionals would acquire copies legally. I wouldn't mind running it if it worked natively on my amd64 running gentoo ;-)

    To somehow suggest that as soon as it hits Linux everyone will pirate it, perhaps you think because all Linux users are criminals??? is just plain stupid.

    Tom

    --
    Someday, I'll have a real sig.
  5. Re:why feed the competition? by Catbeller · · Score: 5, Informative

    I've a longer memory than most here.

    Microsoft extended its contract with Apple to keep Office current on Macs NOT for the unit sales, but because, at the time, they were litigating the monolopy case in court. They needed Apple to stay alive to keep up the pretense that they were engaging an open market without recourse to any monopoly (which was nonsense - they lost). Bill also invested a bunch of cash in Apple at the same time for the same reason: Bill needed Apple alive, not crushed, so that Microsoft could make a case against a finding of monopoly.

    Now that Linus is around, Office's days on the Mac may be numbered. They aren't needed any more. But, I think Bill prefers the devil he knows to the devil which is free and open sourced. He'll keep Apple alive as long as he can, even though he lost the monopoly ruling, because the alternative is all Linux and OpenOffice.

  6. Re:Office for Linux by Anonymous Coward · · Score: 1, Informative

    Office for Mac lagging behind? You're kidding, right? Have you even used it. It is what Office2k4 for Winblows should be. It's responsive, intuitive and stable.

    Before you wag your tongue, open your eyes.

  7. Fat(32) is useful in linux by bigtrouble77 · · Score: 4, Informative

    There's only one reason I use fat32, and that's to format my 300gb ub2 hd. If I want cross compatibility between windows and linux, fat32 is the only way to do that. If I format to NTFS I cannot write to the drive and all my files are labeled read-only (which is really annoying when you have to copy over many files). If I format to Ext2, Ext3, microsoft will not read those partitions.

    Interesting thing is that micrsoft PURPOSELY BREAKS FAT32 in windows!!! I forget the exact size, but you can only format a fat32 partition up to 30gb in windows. Microsoft really wants you using their proprietary ntfs file system. As a result I have to format fat32 from linux to utilize the whole capacity of the drive.

    This is simply another case of microsoft trying to force proprietary software onto people that want nothing to do with their product.

    1. Re:Fat(32) is useful in linux by sagenumen · · Score: 2, Informative

      I have had some good experience with EXT2 IFS. It lets you mount EXT2 and EXT3 drives in Windows. Reading and writing both worked well.

    2. Re:Fat(32) is useful in linux by despisethesun · · Score: 2, Informative

      Here's a couple of suggestions for Ext2fs in Windows:
      http://e2fsprogs.sourceforge.net/ext2.html
      http://www.ext2fs-anywhere.com/

      These should let you use Ext2fs in Windows.

      My big problem with Fat32 is actually the 4GB file size limit. Kind of aggrivating but I hardly ever use Windows these days so it's not really a big deal.

      --
      This poo is cold.
    3. Re:Fat(32) is useful in linux by sabit666 · · Score: 2, Informative

      Reiserfs for Win32: http://rfsd.sourceforge.net/

  8. Re:No office for Linux? -- A big blunder for MS by Sigma+7 · · Score: 3, Informative
    If MS ported Office to Linux,


    Try "re-written".

    Linux and Windows are completely two different software archetectures - Linux is focused around client-server connections using terminals (some of which are incapable of instantly distinguishing ESC from some other keypress without looking ahead) and has "perfected" that system. On the other hand, Windows is focused on a local user interface and has "perfected" that system - you can do almost anything in Windows just by using the base API.

    Consider trying to write a truly portable C program - the advice given on news:comp.lang.c is to stick with the ANSI standard - which doesn't support any GUIs, mouse interfaces, networking, multi-threading or any other stuff that would make a modern operating system. Because of this, both MS, and POSIX either are or have different extensions to the operating system. Of these two, MS attempts to implement everything in their windowing system (including delay systems, timers, GDI, clipboard, and other stuff.), and POSIX extended networking, logon and file-system features.

    Both systems are not complete at one time - Windows 3.0 didn't have builtin TCP/IP support, and required installation of a special package that interfaced with a modem, and used IPC to allow other applications to use the internet. On the other hand, POSIX was extended by XWindows and other stuff.

    Right now, MS has merged various OS extensions into the main product (e.g. external WinSocks were replaced by an MS implementation.) However, I haven't seen much change in the basic Linux or POSIX API, aside from third party extensions (such as SDL.)
  9. Apps Define the OS? by chronicon · · Score: 5, Informative
    MS Office + IE are the desktop to many people in Corporate America. If you could run those on Linux, there would be almost no reason to run windows. Windows just acts as a carrier horse for that suite and "the internet"

    According to Frank's Corner you can run both MS Office and Internet Explorer on the Linux desktop. And...he shows you how.

    Implementing it corporate wide would be the real trick...

  10. Re:Hasn't the time limit expired? by ptbarnett · · Score: 3, Informative
    I think it's bad form to follow up to my own posting, but I did a bit more research. The patents in question were already granted, and are now being challenged in response to Microsoft's demand for licenses:

    http://www.microsoft.com/mscorp/ip/tech/fat.asp

    The patents listed in the above web page:

    5,579,517, filed 1995-4-24, granted 1996-11-26.
    5,758,352, filed 1996-9-5, granted 1998-5-26.
    6,286,013, filed 1997-1-28, granted 2001-9-4.

    All of these patents appear to be related to VFAT, i.e. mapping long filenames and the original 8+3 short filenames into a common name-space. Although the filing dates are different and the title for one is slightly different, the abstract for each appears to be exactly the same.

    I haven't examined the claims in each patent, so I don't know how these patents differ. It might be interesting to determine what is new in the 2nd and 3rd patents, since they were filed as long as 21 months after the 1st one. I wonder what wasn't in the original VFAT implementation? Bug fixes or features?

    But, these patents don't appear to cover the "old" FAT filesystem: they address the later addition of long filenames. Again, IANAL, but I think that someone that confines themselves to the original FAT format (without long filenames) would have no need to license it from Microsoft.

  11. Re:FAT patent harmful? by Mechcozmo · · Score: 2, Informative
    Under OS X Panther and Tiger (10.3 and 10.4) you don't need to either. It is built into the OS and not the file system. This allows frequently used files to be placed at the outer rim of the hard drive (where it spins the fastest) and less-frequently used files to be moved away from this "Hot File Cluster" area.

    The filesystem is just one part in preventing fragmentation.


    (Note to mods: this isn't damning ReiserFS, but informing others about other methods of preventing fragmentation. Don't kill me. Thanks)