Slashdot Mirror


USB 2.0 for Linux Coming Soon

itwerx writes "There's an article on MSNBC about USB 2.0 support in Linux. Interesting to see that the open source community is less than a year behind the most powerful software company in the world in supporting it. Does that make us the second most powerful now? :)"

254 comments

  1. Linux being mentioned on MSNBC by Electrode · · Score: 2, Insightful

    Don't you find it a bit strange that MSNBC, which is at least half owned by Microsoft, is almost advocating Linux?

    Anyway, I'm glad to hear it. I look forward to replacing my USB 1.1 hard drive housing with a USB 2.0 one.

    1. Re:Linux being mentioned on MSNBC by WanderingGhost · · Score: 1
      Don't you find it a bit strange that MSNBC, which is at least half owned by Microsoft, is almost advocating Linux?

      Microsoft hasn't been bashing Linux so much anymore. It sees important opportunities there. What they really don't like is GPL-like licences.
      Anyway, they've been changing their atitude towards Linux and Open Source. I just don't know if it'll get better or worse...

    2. Re:Linux being mentioned on MSNBC by Amiga+Trombone · · Score: 1, Interesting

      Don't you find it a bit strange that MSNBC, which is at least half owned by Microsoft, is almost advocating Linux?

      How's this for a conspiracy theory - Bill Gates, being a geek at heart, is secretly a supporter of Linux. Unfortunately, a public endorsement would de-value the stock value of Microsoft, leaving him liable to lawsuits from Microsoft's shareholders.

      Hey, stranger things have happened!

    3. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Mod parent up!

      It's a much better troll then the great-grandparent, and the great-grandparent made the front page, therefore we should be interested in what parent has to say. (or something)

      Not to mention it makes hella sense, no one with an IQ over 150 who seriously uses a computer (geek serious, not lawyer serious etc) could in no way believe the watered down junk that windows is could possibly be better than a solid posix OS (yes I'm sure there are better, but I haven't found one that works better for me yet).

    4. Re:Linux being mentioned on MSNBC by Cryptosporidium · · Score: 4, Informative

      The article is from CNET. It has just been reported again by MSNBC.

    5. Re:Linux being mentioned on MSNBC by Monkelectric · · Score: 4, Funny
      Probably some reporter wants out of his contract :)

      Im just imagining this conversation between Stephen Shankland (the author) and his boss.

      boss, "Hi Steve, what did you want to see me about?" Steve, "Well, um, fox news offered me 2x what you're paying me, and they have neater graphics, neat DNB music between segueys, and gretta van sustren is kind of cute." boss, "Steve steve steve, do I have to remind you that you signed a 5 year contract?" Steve, "I know boss, I was hoping you'd let me go...(trails off)" boss, "fat chance!!" steve, "Fine then, we can do this the hard way!" boss, "Yea and what is that?" steve, "I'll start writing LINUX STORIES!" (just then the office goes dead silent and you hear the gasps and jaws dropping) boss, "You just try it buddy!"

      And this is the [speculative] story of how pro-linux articles appear on MSNBC. Actually, if you read the article praising linux for being only a year behind, REALLY ISN'T HIGH PRAISE. Second of all, there was a time when journalists were supposed to have *ethics*, independance, and a responsibility to the truth.... Hopefully someone at MSNBC still thinks like that.

      --

      Religion is a gateway psychosis. -- Dave Foley

    6. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      I have an IQ of 178 and I use Windows XP. Suck on that, biatch!

    7. Re:Linux being mentioned on MSNBC by Oculus+Habent · · Score: 3, Interesting

      Gates' own operating system design was to be UNIX-based. However, he has long since stopped coding and started managing.

      You should look less at MSNBC's article as a support of open-source, or a secret desire to support Linux, then as a desire to become a serious news source.

      Microsoft has been trying for years to show that they are serious about the things they decide to pursue.

      Messengers, game consoles, ISP. All these things are places Microsoft didn't have to go and people didn't expect from a software company. Microsoft is just trying to get away from people thinking "Windows" when they think of Microsoft, and nothing else.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    8. Re:Linux being mentioned on MSNBC by Oculus+Habent · · Score: 2

      You werew almost making sense... It didn't quite work out, though.

      I think you really lost credibility when you said "hella" and "IQ over 150" in the same sentance.

      --
      If you have something worthwhile to say, log in.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    9. Re:Linux being mentioned on MSNBC by EvanED · · Score: 1

      Parent companies tend to leave child news companies largely alone. If they get too involved and it becomes biased, the news source looses credibility and some people go elsewhere. If you'll remember, MSNBC also ran several articles about the anti-trust trail with a decidedly anti-MS tone.

    10. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Because /. editors have always been MSNBC's fans :)

    11. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Don't you mean [b]lose[/b]?

      Loose is the opposite of tight.
      Lose is the opposite of winning or gaining.

      Is english your second language?

    12. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 1

      Well, you got the first half of the thought that I had. You said:

      Don't you find it a bit strange that MSNBC, which is at least half owned by Microsoft, is almost advocating Linux?

      I agree. But I'd also like to theorize why:

      For sake of argument let's forget for a moment that it's MSNBC and think of it as just another unbiased news outlet. We could say:

      "Isn't it great that USB support under Linux is considered newsworthy by mainstream media. Linux must be approaching critical mass."

      Now let's be cynical and remember that it's MSNBC, not just another unbiased news outlet:

      We could say:

      "Isn't it possible that ( as suggested by slashdotter Keefa on Friday ) Microsoft is trying to make the case to the courts that it does have formidable competition. Wouldn't one of the ways that they would attempt to corroborate the assertion be to point to the number of Linux articles in the "mainstream" press?"

      Is there a new movement afoot (reverse astro-turfing)? Wherever MS is involved, I am very skeptical and look for the hidden agenda. They have time and again proven themselves more than worthy of suspicion.

    13. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 5, Insightful

      > Microsoft hasn't been bashing Linux so much anymore. It sees important opportunities there...

      > Anyway, they've been changing their atitude towards Linux and Open Source.

      That's the biggest BS I've ever heard. Gates and Ballmer still run the company, and they are no more honest now than in the past.

      It was just a few months ago that evidence came about that showed how Microsoft pressured Dell into dropping support for desktop Linux:

      http://www.theregister.co.uk/content/4/24478.html

      If Microsoft is being quieter now, it's because they want something -- something that requires less hostility from Linux developers.

      What Microsoft wants right now is for companies and developers to accept .Net, to develop for it, and to become dependent on it. That includes building ties to Palladium.

      This is consistent with Microsoft's earlier behaviour.

      For example, once Microsoft had their polluted J++ version of Java in place, their strategy became the following:

      > "At this point its [sic] not good to create MORE noise around our win32 java classes. Instead we should just quietly grow j++ share and assume that people will take advantage of our classes without ever realizing they are building win32-only java apps." http://java.sun.com/lawsuit/051498.unfair.html

      Microsoft tried a similar "keep quite and let everyone lock themselves in" strategy with Bristol's Wind/U (Windows APIs on Unix), which tended to lock Unix applications to Windows servers.

      So of course Microsoft would like things to quiet down right now. It's because they've already set the traps that they hope will capture Linux and the Internet.

      These traps include:

      - .Net
      - Palladium
      - Windows Media protocols over the Internet
      - Palladium support for Apache
      - MS Office lock-in on Linux (Crossover)
      - ActiveX lock-in on Linux (Crossover)
      - .Net support (lock-in) in Qt
      - ActiveX support (lock-in) in Konqueror
      - Windows Media lock-in on Linux (mplayer)
      - Hardware partnership with AMD (kept API details secret, making Linux unstable)
      - Hardware partnership with NVidia (closed source driver tied into Linux kernel)
      - Hardware lock-in through NVidia (their new graphics language compiler)
      - Attempted government-mandated IP-security-hardware lock-in

      Actually, now that I think about it, that last one is a killer. In order for Microsoft to get Congressmen and Senators on their side, it is very important to reduce the political risk, by making Microsoft seem more benign. Thus, if Microsoft can succeed in keeping the Linux supporters quiet, then more government officials will be willing to accept the payoffs, excuse me, campaign contributions that Microsoft has offered, in exchange for selling out the American people. It would be a pretty sweet deal for Microsoft to have a law that requires the use of Microsoft technology in every computing device.

    14. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Actually, i think it's good that MSNBM behaves in a non-biased way and covers stories like this. Just because they are owned by Micro$oft doesn't imply that news is pro-M$. This raises my opinion of MSNBC...

      The one to watch out for is FOXNEWS. Forget M$ for a moment, they try to "balance" the news, by rationalizing that all other news is already biased "liberal". The end result is a conservative news agency - which is bad, bad, bad. Sorry, off-topic, I know. Yes, conservative does mean bad.

    15. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Your mom was the opposite of tight, too.

    16. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Don't you find it a bit strange that MSNBC, which is at least half owned by Microsoft, is almost advocating Linux?

      Don't you find it a bit strange that MSNBC, which is at least half owned by Microsoft, is practicing responsible journalism?

      Oh, wait, this is slashdot.

    17. Re:Linux being mentioned on MSNBC by xtremex · · Score: 1

      I never saw Bil Gates as a geek. He's geeky LOOKING, but he's a salesman and a master Marketer. The same people ost of us geeks think are NOT geeks. What has he done to show his geekiness?

      --
      If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
    18. Re:Linux being mentioned on MSNBC by xtremex · · Score: 1

      Why is conservative bad? You'd INSTEAD believe that the LIBERAL communist media is good?

      --
      If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
    19. Re:Linux being mentioned on MSNBC by awfar · · Score: 1

      How would Microsoft look to the Government if they had no Competitor; real or imaginary?

      It is all about Appearances.

    20. Re:Linux being mentioned on MSNBC by EvanED · · Score: 1

      I made a typo. Sue me. You're not perfect either; "English" is capitalized, at least in American English. I can't vouch for British English.

    21. Re:Linux being mentioned on MSNBC by EvanED · · Score: 1

      Reading over my first post again, I'm now surprised you didn't say anything about the "anti-trust trail." "Where is it? I want to hike it." "Oh, it runs through Microsoft's campus. Right by the tennis courts."

    22. Re:Linux being mentioned on MSNBC by yog · · Score: 2

      You make a few good points but some of this sounds a bit paranoid.

      > So of course Microsoft would like things to quiet down right
      > now. It's because they've already set the traps that they hope will
      > capture Linux and the Internet.


      So far, so good.

      > These traps include:
      >
      > - .Net


      .NET is good technology. Look, if someone else had invented it, let's say Sun
      or IBM, would people be so upset about it? It's going to make web services
      easier to implement. Let J2EE have a little competition and we'll all benefit.

      > - Palladium

      The only credible benefit of Palladium to the consumer is spam blocking.
      Digital rights management is usually consumer-hostile and tends to be defeated.
      This one has little chance of success; too big brother-ish. Keep your
      congress-peops informed of your opinions. Meanwhile, there's a couple of
      products out that already do spam blocking in a similar way
      (ChoiceMail, Mail Washer), and more are coming.

      > - Windows Media protocols over the Internet

      WMP is a pretty good format. Let them pour money into improving this important
      technology, and we'll all benefit. Anyway, with crossover I can now run
      Windows Media in Linux, which is one less reason to run Windows--how does that
      help Microsoft? Remember, the media player is a free download.

      > - Palladium support for Apache

      As above.

      > - MS Office lock-in on Linux (Crossover)

      As above--it's a lock-in, yes, but it's an unlocking of the operating system.
      You don't need Windows to do "real" Office. However, this is almost a red
      herring because Star/Open Office, Abi Word, etc. have gotten so good. Anyway,
      the research to improve Crossover/Wine has a great side effect; it makes more
      Win32 binaries run properly in Linux.

      > - ActiveX lock-in on Linux (Crossover)

      Hmm. For online banking it's handy but best is to scream at the bank, as a
      customer, and demand platform independent banking or you'll move your accounts
      elsewhere. Money talks. However, as above, it's a liberation of the OS.

      > - .Net support (lock-in) in Qt
      > - ActiveX support (lock-in) in Konqueror
      > - Windows Media lock-in on Linux (mplayer)

      Understand your point but this stuff is redundant.

      > - Hardware partnership with AMD (kept API details secret, making Linux unstable)
      > - Hardware partnership with NVidia (closed source driver tied into Linux kernel)
      > - Hardware lock-in through NVidia (their new graphics language compiler)

      Don't know anything about these. Tying a BIOS chipset to a particular OS
      sounds dangerous and probably unworkable anyway. If it's that specific and
      that secret, it'll certainly break something out there. Dongles failed a long
      time ago and any attempt to revive them is a waste of time.

      > - Attempted government-mandated IP-security-hardware lock-in

      Palladium, in other words.

      I'm more optimistic than you, though I agree with your concerns. Anyway my
      strategy is to keep pushing for Linux wherever I work and certainly in my home
      office. But, if someone builds a better widget well, you know it's still a market system; let the best product win.

      Terry

      --
      it's = "it is"; its = possessive. E.g., it's flapping its wings.
    23. Re:Linux being mentioned on MSNBC by stor · · Score: 1

      Hi!

      Not a flame but I gotta pull you up on this one:

      "Remember, the media player is a free download."

      That may be true but IIRC (what a disclaimer!) the EULA explicity prohibits you to run the player on a non-MS OS. So you've broken their EULA.

      Practically that probably doesn't make much of a difference but it does give you a little insight into the way MS restrictively licence their software in order to retain control.

      And then there's this:

      http://slashdot.org/article.pl?sid=02/06/29/1254 23 0&mode=thread&tid=109

      I believe a bit of cynicism is justified.

      Cheers
      Andy

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
    24. Re:Linux being mentioned on MSNBC by kasperd · · Score: 1

      the EULA explicity prohibits you to run the player on a non-MS OS. So you've broken their EULA.

      It is doubtable whether this EULA has any legal validity. At least in my part of the world the law gives us certain rights that cannot be given up by an agreement.

      --

      Do you care about the security of your wireless mouse?
    25. Re:Linux being mentioned on MSNBC by tzanger · · Score: 2

      - .Net support (lock-in) in Qt

      Qt has .Net support?

    26. Re:Linux being mentioned on MSNBC by Anonymous Coward · · Score: 0

      Yes, there is Qt#, which is Qt bindings for C#. That allows Qt-based code to call .Net components.

      They claim that the purpose is to allow Qt applications to provide support for Mono, but I'm not sure that I believe them. I think Trolltech's just in it for them money, and could care less about whether they are helping Linux or Microsoft.

      See: http://developer.kde.org/language-bindings/qtcshar p/

    27. Re:Linux being mentioned on MSNBC by gmkeegan · · Score: 1

      It would be a pretty sweet deal for Microsoft to have a law that requires the use of Microsoft technology in every computing device.

      That is EXACTLY where they're going!!! The biggest threat to Windows, second maybe to the server market, is the embedded market. Right now Linux is ideal because it can be scaled and customized to fit whatever embedded device the designer has in mind. If proprietary DRM features are legally mandated, then the embedded Windows will be the only practical option out there.

      Bastards...

  2. do you guys think by flashark · · Score: 0

    we would be able to make such advancements if m$ did not exist? what are our biggest device support things that m$ didnt have first?

    1. Re:do you guys think by jimmy_dean · · Score: 4, Interesting

      We had AMD Hammer 64 bit processor support before Windows did.

      --
      -> Sometimes, you just gotta break free from the shackles of proprietary code.
    2. Re:do you guys think by Stonent1 · · Score: 0

      Itanium (anyone remember processor?) support as well.

    3. Re:do you guys think by Anonymous Coward · · Score: 0
      What's that supposed to mean?

      Support as in the way Microsoft supports Palladium right now?

      How can you have support for a non-existing CPU?!

    4. Re:do you guys think by Anonymous Coward · · Score: 0

      We had AMD Hammer 64 bit processor support before Windows did.

      But not before NetBSD.

      And who is this "we?" I doubt you were on the Hammer project.

    5. Re:do you guys think by Anonymous Coward · · Score: 0

      um, not really. Don't believe everything you read in the press - they don't always get it right - they were not on this story.

    6. Re:do you guys think by Anonymous Coward · · Score: 0

      Uhh, Linux runs on large IBM and other mainframes. Does that count?

      There is not much point in comparing apples and oranges. It depends on what you want to eat...

  3. This will help how by jstroebele · · Score: 2, Insightful

    Reading the MSNBC story one would think this would solve all driver issues, if the device is USB 2.0. Last time I checked you still need to install some type of software to get a device to work. If the manufatures don't support linux, you might as well have a PCI card.

    1. Re:This will help how by xant · · Score: 2

      Some type of software? Don't be so pessimistic, device drivers aren't the only things we know how to write. If the manufacturers don't help, we'll reverse-engineer it and do it anyway.

      --
      It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    2. Re:This will help how by Anonymous Coward · · Score: 0

      Who are "we" ..?

    3. Re:This will help how by martyn+s · · Score: 1

      We are Us.

    4. Re:This will help how by JoeBlows · · Score: 3, Informative

      the USB spec has generic drivers that are available to everyone. the drivers include talking to Opticle devices, talking to block devices, mice, and keyboards.

      --
      True capitalism = lots of similar companies = jobs for everyone who wants one.
    5. Re:This will help how by bryston2 · · Score: 1

      Come on now do we need to use a 400Mbit buss for a keyboard and mouse. No one can type and click that fast!

    6. Re:This will help how by yog · · Score: 2

      I wish there were a driver for my SIIG flashcard reader. SIIG told me they had no plans to support Linux. USB 2.0 is all very well but manufacturers still need to have a little openmindedness.

      --
      it's = "it is"; its = possessive. E.g., it's flapping its wings.
    7. Re:This will help how by Anonymous Coward · · Score: 0

      Huh?

      My plextor usb 2.0 cdrw drive works fine out of the box on 2.4.19rc3, with no additional sofware. And plextors "linux support" is a link to the cdrecord home page.

      Unless vendors go out of their way to NOT use the standardized transfer methods, you'll be fine.

    8. Re:This will help how by Anonymous Coward · · Score: 0

      So tell them to suck it and buy something that uses mass-storage instead. It will work on windows and linux will be able to mount it as any scsi device.

      Don't tolerate that crap, and let them know that you don't.

    9. Re:This will help how by JoeBlows · · Score: 1

      Sony Makiva Digital camera uses CD-RWs.

      --
      True capitalism = lots of similar companies = jobs for everyone who wants one.
  4. USB2 Support by MiniChaz · · Score: 0, Flamebait

    What about USB2 under Mac OS X?

    1. Re:USB2 Support by Anonymous Coward · · Score: 0

      There is already support, it just isn't on an ofthe MoBo's yet

    2. Re:USB2 Support by Anonymous Coward · · Score: 0

      Yes. It shows BSD leads, and Linux follows.

      http://www.orangemicro.com/updateusb2mac.html
      M ac OS X
      Documentation - Driver Installation

      DOWNLOAD SOFTWARE for Mac OS X USB 2.0 host controller drivers. This release of the driver requires Mac OS X v10.1 or newer. Check this web site for periodic updates.

      1.0.6 4/15/02

    3. Re:USB2 Support by lonely · · Score: 1


      Happily running USB 2.0 card on my Mac OS X machines as I write this. IBut for the life of me I can't remember what it is called. If you search version tracker you will find drivers for another card from a company called Orange.

  5. NetBSD by The+FooMiester · · Score: 5, Interesting

    NetBSD has had NetBSD support in current for quite some time. Does that make it number 2?

    --
    The previous has been a secret message to my comrades.
    1. Re:NetBSD by The+FooMiester · · Score: 4, Funny

      Not only have they had netbsd support in the kernel, they've had USB2 support too!

      That'll teach me to post on less than 2 pots of coffee.

      --
      The previous has been a secret message to my comrades.
    2. Re:NetBSD by imr · · Score: 1

      Maybe you had enough coffee and not enough water:
      coffee
      (I just put the link because it's a must-see for every coffee lover out there; the whole discussion is great.)

  6. 1 year behind? by rtnz · · Score: 3, Insightful

    >Interesting to see that the open source community is
    >less than a year behind the most powerful software
    >company in the world in supporting it.

    1 Year is interesting? Seems like maybe a couple months behind would be interesting.

    1. Re:1 year behind? by Anonymous Coward · · Score: 0

      Linux has supported for usb2 for MONTHS, its just not reached the stable branch.

    2. Re:1 year behind? by Anonymous Coward · · Score: 0

      well gee, Windows has only had it since early 2002.

      dipshit.

  7. Second? by ozbird · · Score: 4, Insightful

    Interesting to see that the open source community is less than a year behind the most powerful software company in the world in supporting it. Does that make us the second most powerful now?

    No, it makes us a year behind. That isn't necessarily bad given the limited number of USB 2.0 to support, but it does show where it rates in the Linux priorities. (As a comparison, consider that Linux supported Itanium very early on - and I've yet to see one in the wild...)

    1. Re:Second? by dvdeug · · Score: 2

      it does show where it rates in the Linux priorities. (As a comparison, consider that Linux supported Itanium very early on [...]

      That has nothing to do with priorities. It has to do with the fact that Intel and HP were throwing money at the problem and loaning out Itanium machines semi-permenantly to anyone who could really use one.

    2. Re:Second? by chillyjim · · Score: 1

      Okay maybe I'm missing somthing, but what part of usb2 doesn't linux support? I know my 24X USB2 cdr works just fine and is running close to 24x.

    3. Re:Second? by DLR · · Score: 1

      A year is an awfully long time in the computer industry. How many companies went broke or discontinued product lines because they were "only" a year behind? How many generations of processors are released in a year, 2 or 3?

      I am not dissin' Linux, merely trying to be a realist.

      --
      "Like fire and fusion, government is a dangerous servant and a terrible master."~RAH
    4. Re:Second? by Johannes · · Score: 5, Insightful

      Actually, it makes us less than a year behind. Why? Because this article is incorrectly assuming that the 2.4.19 final release is the first time anyone sees any Linux USB 2.0 support.

      There has been a stable USB 2.0 patch for well over a year, it has been in the 2.5 kernel since it forked and it's been in 2.4 for a while, albeit under the "Experimental" heading or waiting for the final 2.4.19 kernel to be released.

      Like you mentioned, the biggest problem with adding support for USB 2.0 was the lack of devices. The vast majority of development was done with one USB 2.0 controller and one USB 2.0 device. Both were prerelease versions with a whole slew of bugs to workaround.

      The reason why you see Itanium support being so mature was because of the priorities of Intel, not of the community. Intel (and HP) sunk a significant amount of money into getting Linux ported to Itanium. Why? Because it's a billion times harder than USB 2.0 support and much more fundamental and thusly important to have supported as early as possible.

    5. Re:Second? by brsmith4 · · Score: 1

      if yer running one of the distros in the article or you have patched your kernel and recompiled then you device probably works great. Check again.

    6. Re:Second? by Anonymous Coward · · Score: 0

      No, it has to do with priorities.

      Itanium is a server-oriented technology.

      USB is not.

    7. Re:Second? by dvdeug · · Score: 2

      No, it has to do with priorities.

      You think Redhat paused for a second to consider priorities when Intel shoved a big pile of cash at them to get Linux working on Itanium?

    8. Re:Second? by GrenDel+Fuego · · Score: 2

      There has been a stable USB 2.0 patch for well over a year, it has been in the 2.5 kernel since it forked and it's been in 2.4 for a while, albeit under the "Experimental" heading or waiting for the final 2.4.19 kernel to be released.

      It was not in 2.5 was 2.5 was forked. 2.5.0 was exactly like 2.4.15, which did not include usb 2.0. I don't even believe it was in 2.5.7 or 2.5.8.

      USB 2.0 in the 2.4 series has yet to be in an actual release kernel, although it was added in 2.4.19-pre2, which came out back in February.

  8. Good reporting shows both sides. by Mustang+Matt · · Score: 0, Flamebait

    Microsoft should be proud that their news source isn't super biased.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
    1. Re:Good reporting shows both sides. by Anonymous Coward · · Score: 0

      Nooooo! Micro$haft SUXXX0RZ!!!1

      LUNIX R00lZ!!!

    2. Re:Good reporting shows both sides. by Anonymous Coward · · Score: 0
      "Microsoft should be proud that their news source isn't super biased."

      Shame the same can't be said for Slashdot.

    3. Re:Good reporting shows both sides. by Sj0 · · Score: 2

      We covered the X-Box, didn't we?

      --
      It's been a long time.
    4. Re:Good reporting shows both sides. by Sivar · · Score: 2

      Agreed. MSNBC has printed quite a few stories about Linux and very few seemed to have any hint of anti-Linux bias. It seems every time MSNBC publishes a Linux story, people either look for the smallest negative connotation and scream "BIAS!!!" or find none and say that they are just trying to build a reputation as unbiased so they can cover up the real Microsoft evils.

      Oddly, MSNBC has also published quite a few articles that do not make Microsoft look all that appealing. Unless somebody has some hard evidence as to why MSNBC is biased, like, oh-I-don't-know one single clearly biased story, give them a break. Does everyone think that every honorable journalist was instantly corrupted by Microsoft's aura?

      --
      Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
  9. What does this mean? by Anonymous Coward · · Score: 0

    The new version won't instantly enable USB 2.0 to work with Linux-based devices[...]

    *Still* having trouble getting their heads around this Linux thing, I see.

  10. Next! by Spleen · · Score: 2, Insightful

    There is no controversy here, Pay Respect to those doing the work, *waves the jedi hand* Move Along.

    1. Re:Next! by Anonymous Coward · · Score: 0

      I'd pay respect if you weren't such a fucking loser.

    2. Re:Next! by Anonymous Coward · · Score: 0

      Amen brother

  11. What devices? by Anonymous Coward · · Score: 1

    What devices support USB 2.0 that linux users REALLY need at this point? Look at it this way, Apple doesn't suppost USB 2 yet (and OS X.2 doesn't look like it does either), MS is the only player in the field. I say firewire all the way.. firewire 2 is just around the corner and looks fantastic (will probably be supported pretty quickly too).

    USB is good for keyboards and mice... that's about all.

    1. Re:What devices? by Fragmented_Datagram · · Score: 1

      A USB 2.0 hard drive would be useful. I saw this one demoed at a tech expo recently.

    2. Re:What devices? by Wyatt+Earp · · Score: 1

      There is USB2.0 support in Mac OS X.

      Just not from Apple, but from third parties shipping the cards.

      http://www.orangemicro.com/OrangeUSBPCI.html

      USB 1.1 - Mac OS 8.6, 9.x or newer
      USB 2.0 - Mac OS X or newer

      "USB 2.0 Hi-Speed support is only available on Mac OS X at this time. When running on Mac OS X systems, USB 2.0 Hi-Speed will have a data transfer rate of up to 480 Mbits/s (Hi-Speed). When running on the Mac OS 8.6 and Mac OS 9.x USB will have data transfer rates of 12Mb/s (Full-Speed) and 1.5Mb/s (Low-Speed) peripherals."

    3. Re:What devices? by Anonymous Coward · · Score: 0

      Quiet! Don't let facts get in the way of the Linux Jihad!

    4. Re:What devices? by Anonymous Coward · · Score: 0

      USB 1 is good enough for keyboards and mice. But USB 2 has a transfer rate similar to firewire, and can be used for external hard drives, cd burners, digital cameras, and so on.

  12. Not necessarily Second by SpamJunkie · · Score: 1

    I wouldn't say you're second until it's actually released. Wild speculation about Apple's next Powermac release says USB 2 might be there as well.

  13. Excellent! by whereiswaldo · · Score: 1

    I had written a digital camera vendor about 3 months ago and asked about their software support for Linux.

    They basically said "USB on Linux is not there yet" but they had obviously looked at the possibility. I hope USB 2.0 will give them what they've been waiting for and in turn give consumers what we've been waiting for -- more bundled software that runs on Linux!

    1. Re:Excellent! by GigsVT · · Score: 1

      They were full of shit if they said that 3 months ago. Linux has had solid usb support for almost two years.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:Excellent! by whereiswaldo · · Score: 1

      I found the email. Here is Kodak's reply to me (dated May 2002):
      ------------
      Greetings _____,

      Thank you for your recent visit to the Kodak website and question about
      using the KODAK EASYSHARE DX4900 Zoom Digital Camera on a Linux
      computer.

      Thank you for visiting the Kodak web site and your inquiry regarding
      Kodak support for Linux OS in Kodak products. Our Kodak software
      engineers are aware of the Linux OS and we appreciate your interest in
      enabling Kodak products to work with it.

      Kodak continues to follow the Linux Operating system. We noted, as far
      back as March 30, 1999, that Linux announced support of a Linux-USB
      driver that only worked with UHCI controllers. Since UHCI controllers
      represent only a portion of the PC market, Linux-USB was very limited
      and was very preliminary even six months ago.

      We had the same situation in the past with preliminary Microsoft-USB
      drivers and now version 2 USB as well. Sometimes, the availability of
      these drivers simply does not match our product release dates. Even
      after the support is there, as is the case with Microsoft version 1, we
      still have to update our Kodak web site with the latest driver patches
      to keep in step with Microsoft-USB patches. In addition, Kodak has
      worked very closely with the USB IF Working Group on the USB standard
      participating in numerous USB "Plug Fests" where we test out our
      hardware and software on a variety of computers with various "chip
      sets".

      In the past, prior to the release of Microsoft Windows 98, Kodak worked
      intensely with the staff at the Windows Hardware Quality Labs (WHQL) to
      achieve "Windows Logo". This was no small feat with the USB technology
      forming the basis of the DVC323 and later products and the Windows 98
      operating system. As a result, the DVC323 passed all USB compliance
      testing with Windows 98. I am not sure that there is such a rigorous
      test standard for Linux-USB. If not, this has serious implications on
      our technical support staff and the cost for providing a Linux-USB
      driver.

      We understand the issue with devices based on the CPiA chip set and once
      again are faced with a problem with Linux-USB support in that
      isochronous transfer is not yet fully implemented. There is a distinct
      difference when a company claims "USB support" it does not always mean
      "full USB support". Kodak relies on full support for UHCI and OHCI host
      controllers as well as their corresponding USB transfer types. The
      support for this simply is not there yet.

      As Linux-USB becomes fully implemented and released with the Linux OS,
      Kodak may investigate the technical feasibility of developing Linux-USB
      drivers for future products. I am confident that our technical teams
      would be able to provide support once Kodak analyzed the business case
      for such support.

      If you require further assistance, please call our call center at
      1-800-235-6325 in USA or 1-800-465-6325 in Canada. One of our
      representatives would be able to help you with this issue. We are open
      Monday to Friday 9 AM to 8 PM Eastern Standard Time.

      Regards,

      Mandy G.
      Kodak Information and Technical Support
      --- eof ---

    3. Re:Excellent! by acceleriter · · Score: 1

      IOW, we aren't going to spend 50% of our development effort on 1% of our market share, but here's a palliative so you won't think we blew you off.

      --

      CEE5210S The signal SIGHUP was received.

    4. Re:Excellent! by GigsVT · · Score: 1

      If they would have just followed real standards and not worried about proprietary MS-USB (whatever that is), then it would just work on various platforms.

      At least they were somewhat responsive, and they have made a token effort for working toward Linux compatibility.

      The fallacy of market share is important though. Sure, the linux market is much smaller than Windows, but if you make the extra effort to be Linux friendly, you can totally dominate the whole Linux market, and in effect, face no competition in that market. This effect is more pronounced with server-type hardware, and you do see more manufacturer linux support there.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    5. Re:Excellent! by Anonymous Coward · · Score: 0

      You will be happy to know that Linux is a big thing at Kodak. There was actually a project at one time installing linux on one of the digital cameras and. So I would not be suprised if linux support is actually right around the corner, but they don't want to commit.

      - Kodak developer (not cameras though).

    6. Re:Excellent! by Anonymous Coward · · Score: 1, Informative

      Hopefully I don't get fired for this, but most (all?) of the Kodak DC and DX digital cameras connect to the USB device as any IDE device would. If you can plug a CF reader into a USB port on your OS and have it recognized, Kodak cameras will work too, WITHOUT ANY VENDOR SOFTWARE. Works brilliantly in Windows, MacOS, and FreeBSD (I detest Linux, and use FreeBSD exclusively except for on gaming machines...)

      Posting anonymously to protect my job... Sorry if that offends you.

    7. Re:Excellent! by ffsnjb · · Score: 2

      NetBSD runs on a DC265... :) But its much more fun to play Doom on it though.

      --
      "Why do you consent to live in ignorance and fear?" - Bad Religion
    8. Re:Excellent! by acceleriter · · Score: 1
      You're 100% right--I'm just paraphrasing what I thought Kodak would have said had they not been trying to sugar coat it a little. And sugar coating it as they did and making a token effort is a good deal more than other vendors will do when queried about Linux drivers/support, unfortunately.

      Hindsight being 20/20, the time to find out if something will work with Linux (or any other OS one might run) is before buying it--and with the information resources available today, that shouldn't be too hard.

      --

      CEE5210S The signal SIGHUP was received.

    9. Re:Excellent! by acceleriter · · Score: 1

      I'm glad someone modded that up. That's pretty much all I ever ask for from vendors. Thanks for posting.

      --

      CEE5210S The signal SIGHUP was received.

  14. Its supported! by Weffs11 · · Score: 2, Insightful

    Now all I have to do is wait for hardware that supports 2.0.

    1. Re:Its supported! by amns · · Score: 1

      hic puer est stultissimus omnium

    2. Re:Its supported! by Weffs11 · · Score: 1

      non plaudite. modo pecuniam jacite.

  15. What about firewire? by Anonymous Coward · · Score: 0

    I still can't plug my firewire CDRW into linux & have it work properly, out of the box. Nor does my firewire HD.

    How many years behind does that make linux? 3? 4?

  16. Firewire vs USB support in Linux by rtnz · · Score: 1

    I am still waiting for Firewire to fully be supported in linux on my laptop; looks like it might be better to wait for USB2 to kick in.

  17. Yeah... by Anonymous Coward · · Score: 0

    ...now how about some drivers for USB 2.0 hardware? Like the 1394 camera drivers we're probably never going to get, either?

  18. CNET Story with details. by nilstar · · Score: 3, Informative

    CNET ran this story before MSNBC. The story is Here.

    --
    ===> An eye for an eye makes everyone blind - MG
    1. Re:CNET Story with details. by Anonymous Coward · · Score: 0

      USB 2.0 support is one of the important things and Linux should and will support it (and it did, does and will support othre interfaces that will become popular as well). CNET and MSNBC pay too much weight and make it look like such a big deal ("support USB 2.0 are die"). It reveals more about the reporters' egos than about importance of USB 2.0 to Linux.

  19. wtf? by Anonymous Coward · · Score: 1, Informative

    I don't mean to be a troll, but USB 2.0 support was in the kernel (2.5) a WHILE ago.

    Next time you want to say what Linux will support, please do a search on lkml, if you even know what that is.

  20. I don't get it by npqff · · Score: 1

    I just don't get USB 2.0. What does this technology provide that "Firewire" hasn't already been providing for years?

    1. Re:I don't get it by Anonymous Coward · · Score: 0

      Its made by Intel and thus has a _very_ strong supporter. Thats basically all, but its still a lot...

    2. Re:I don't get it by Abreu · · Score: 2

      Firewire will stay on it's professional photo-video niche because of the extra expenses of fiber optics...

      USB uses copper, so devices built for USB 2.0 will eventually be substantially less expensive than the ones built for Firewire.

      --
      No sig for the moment.
    3. Re:I don't get it by Anonymous Coward · · Score: 0

      People keep missing the point here. Firewire is the better standard. That 80mbps extra that usb 2 offers is non-existant in real world conditions?

      Why? USB is too processor dependent, too much latency because it has to have the CPU do all the work.

      Firewire doesn't require the CPU to do anything! That's why you can do straight DV copies from Camcorder to Camcorder.

    4. Re:I don't get it by proj_2501 · · Score: 2

      FireWire uses copper as well. Perhaps you are thinking of Fibre Channel?

    5. Re:I don't get it by be-fan · · Score: 2

      Huh? Firewire is copper too! The real reason firewire didn't take over was (a) Apple and their evil patents, and (b) firewire chipsets are more complex. However, USB 2.0's EHCI standard also requires more complex chipsets, so the difference is not much smaller.

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:I don't get it by Grishnakh · · Score: 2

      Very simple: USB2.0 provides an interface that requires more CPU power than Firewire, and which also is not peer-to-peer, so that it requires a computer with an Intel processor. These are good because they help drive demand for Intel processors (and of course Intel was the main company behind USB).

    7. Re:I don't get it by Catbeller · · Score: 3, Informative

      No, Apple and their evil patents didn't sink Firewire. They let the license go for a dollar a box, then soon waived the fee altogether.

      INTEL HAS THE PATENTS ON USB, and they ain't shy about making money on it. And forcing Firewire OUT, and forcing their inferior product IN.

      As for complexity, that would not be expensive if the technology could get better economies of scale.

      But since Wintel does not want Apple to prosper, and also since Intel was mightily miffed about little Apple taking it's USB thunder away when Firewire came out, they have FUDDed, lied, blocked, inhibited, you name it, any attempt at getting Firewire into the mainstream.

      Firewire is an amazing success story -- Overachiever actually makes big despite determined opposition to Voldemor it in the crib.

      Expensive complexity in chipsets is nonsense. Much more complex circuitry exists for a song -- how much is an LCD desktop screen? A video card? A CPU, jeez! A Duron 1.3 is going for $54! I picked up my Shuttle FV-24 barebone PC with Firewire on the motherboard for $190! There is no reason why Firewire is not on the mobo other than cutthroat "free" marketers making damn sure crud gets sold to nuke the hated compeitor.

    8. Re:I don't get it by jchristopher · · Score: 1
      Overachiever actually makes big despite determined opposition to Voldemor it in the crib.

      You are a COMPLETE LOSER. Get a life, go outside occassionally, jeez!

    9. Re:I don't get it by Catbeller · · Score: 2

      That's the thrust of your argument? I was tryingto invent a verb.

      As for the get a life BS, as we say in the chatting biz,

      "If what I say indicates that I should get a life, what does that say about the imbecile who sits around reading what I said?"

      F&#k off.

    10. Re:I don't get it by ivan256 · · Score: 2

      Fibre Channel uses copper too. Perhaps you're thinking of something else?

  21. Coming? It's already here by fire-eyes · · Score: 5, Informative

    Coming? I'm using it right now, it's an experimental option in 2.4.18 (maybe earlier too).

    Flawless.

    --
    -- Note: If you don't agree with me, don't bother replying. I won't read it.
    1. Re:Coming? It's already here by Anonymous Coward · · Score: 0

      "Experimental" doesn't imply "it's already here"

    2. Re:Coming? It's already here by martyn+s · · Score: 1

      Yes, but does it imply otherwise? He is saying that it is here. The fact that it's labeled "experimental" is not his proof.

  22. hmmm by XO · · Score: 0, Troll

    I'm going to have to agree with most people so far - almost a year behind means "we" suck.

    I installed a USB 2.0 card in my machine, and the system recognizes it as a USB 1.0 device, but it operates a HELL of a lot faster in Windows, even with USB 1.0 devices. Then again, there are no Linux drivers for most of my USB hardware, so that point is irrelevant really.

    About the only thing I can do in Linux with USB is sync my iPaq. BUt there's nothign to sync it WITH. lol

    --
    "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  23. Linux IS the best by Anonymous Coward · · Score: 0, Redundant

    Does that make us the second most powerful now? :)"

    NO!!! Linux IS the best!!!

    Linux is #1 World wide

  24. Huh? by virtual_mps · · Score: 5, Informative

    I've been using USB2 on linux for a while now. Since the kernel has source available, it's possible to apply patches to add features without waiting on a vendor. It would be more accurate to say something like "mainstream usb2 support" or "usb2 in released 2.4 kernel".

    FWIW, I've found USB2 to be not as fast as firewire for things like hard drives, a conclusion that windows benchmarks have also shown. So it's not like the delay in releasing 2.4.19 is really hurting anything, especially since there aren't many usb2 devices or ports around anyway.

    1. Re:Huh? by Anonymous Coward · · Score: 0

      Here's a bandwidth chart so you can better visualize what various tech is capable of.

    2. Re:Huh? by Anonymous Coward · · Score: 0

      uhh... +5 _funny_ maybe...

    3. Re:Huh? by millette · · Score: 1

      What? This can't be! You're complaining about a headline? That's a big no-no on slashdot, haven't you learned already!

    4. Re:Huh? by virtual_mps · · Score: 1

      You're confusing theoretical and real-world transfer rates. I've got firewire enclosures and I have usb2 enclosures, and I find that the usb2 stuff is slower, given the same hard drive. It doesn't matter that it should be faster, it's just not. That could be driver immaturity, it could be firmware immaturity, or it could just be that usb2 isn't as good at utilizing its bandwidth as is firewire. Regardless of the reason, however, I find a firewire enclosure faster and more useful than a usb2 at this time.

    5. Re:Huh? by Anonymous Coward · · Score: 0

      USB2 seems to be slower than 1394 for HDDs because the chipset isn't utilising the full number of slots it has for transferring data. When the HW matures, then USB2 might be faster.

  25. Proud? by binarybum · · Score: 2, Insightful


    Being a year behind in this industry is not something to be proud of. Rather this is something to hang our heads about. MSNBC must have loved posting this article. They're notorious for innovation delays, yet they still kicked our butts by 12 months. If the Linux/OSS community hopes to be competitive in the desktop environment it needs to stop being satisfied with second best. Granted these accomplishments are noble in light of the skimpy development finances being poured into OSS, but funds are growing.
    Success will come when we start forming hardware protocal standards based on technology that we've accelerated beyond the point where M$ can have much of a say in the standards. People will run linux on their desktops when it can do really innovative cool stuff that other closed-source companies have only started circulating memos about developing.
    Linux can no longer live of the legacy of its stability. Say what you will, but the NT5 kernel is suprisingly stable and new versions will likely continue to improve now that M$ home users have been exposed to stable kernels. Linux still has an upperhand is security, but M$ is spending a lot of $ and time into matching us there too. Our frontier needs to be usability, flexibility (open source media formats not restricted by heavy licensing), and innovative feature implamentation. This combined with the corner stone of extremely low cost will drive linux/oss above and beyond.

    --
    ôó
    1. Re:Proud? by ealar+dlanvuli · · Score: 2

      wtf dude, go to best buy and ask to buy a USB2.0 device.

      Oh whats that, they don't exist?

      yeah, exactly

      Not to mention "earlier this year" (as in feburary) is NOT 1 year ago. All you trolls can go the away, thank you.

      --
      I live in a giant bucket.
    2. Re:Proud? by Anonymous Coward · · Score: 0

      leave it to me to forget to hit AC...

      oh well, I think I was up in the low 30's anyway, shouldn't hurt too much.

    3. Re:Proud? by kableh · · Score: 2

      I've had an external Firewire/USB2.0 chassis for my hard drive for about 6 months now. It uses an Oxford 911 chipset. EVERYONE needs to check their facts before spouting off =)

    4. Re:Proud? by Anonymous Coward · · Score: 0

      You can get USB 2.0 cd burners at Best Buy.

    5. Re:Proud? by Anonymous Coward · · Score: 0

      12?

      more like 7.

      go do something useful for once.

    6. Re:Proud? by iabervon · · Score: 3, Informative

      Linux developers have, in general, had better things to do, aside from the group of people working on it. Until there are devices that use it and machines that support it, there's no reason to have OS support. MicroSoft shipped support a while ago because they're pushing its adoption. Linux developers just want all the devices people have to work; they're generally not pushing particular hardware. Keeping on top of all of the standards which may or may not catch on is generally a waste of time which could be better spent working on any of the other things you mentioned.

    7. Re:Proud? by Anonymous Coward · · Score: 0

      Unless you actually bought a card, mobo's didn't even have usb2 until the past 3 months or so (except a very few models). I meant the chances that anyone needs usb2 is close to 0, firewire is a better solution for most situations, and if your buying a card instead of puluging into the mobo there is no reason to use usb2 over firewire.

      though your probably right, I'm the type of person who didn't even use usb1.0 because most controllers really ate cpu time if they were bandwidth intensive at all.

    8. Re:Proud? by madenosine · · Score: 1

      don't exist? almost every new usb device i have seen is made for usb 2.0. sure, they have support for 1.1, but who wants to use 1.1 after have paying for usb 2.0 ports and devices?

      i think you meant "go to best buy and ask to buy a device that exclusively uses usb 2.0"

    9. Re:Proud? by Anonymous Coward · · Score: 0

      STFU and code then and stop trolling slashdot.

      Plus Stop with the fudding yes win 95/98 is a buggy pos. NT5 er Windows 2000 is INCREDIBLY STABLE as a desktop machine. Face it's over. Linux might have had a chance before windows 2000 came out but now it's over. PLus all the GNU tools are available on Windows now so pfft to *nix.

    10. Re:Proud? by Anonymous Coward · · Score: 0

      Stupid ass hole kebler elf troll all USB burners are 2.0 at Best Buy get your facts straight and go return your computer to walmart.

    11. Re:Proud? by Anonymous Coward · · Score: 0

      SHUTUP ALREADY! I don't want to hear another fucking WORD about Linux on the desktop! JUST USE IT AND SHUTUP! Enjoy what works. If it don't work, SHUTUP! This is NOT A FUCKING COMPETITION WITH MICROSOFT! Ask the coders on Linux and they probably don't give a damn. MSNBC IS NOT MICROSOFT. Geez. Do you people not realize that having ownership in a company is not the same as RUNNING the company? Infact, about the only thing MS gets out of MSNBC is close to free advertising and the "MS" in the name. They might have a say in what PROGRAMS get cut, but I'm 100% sure they have no say in program content. They could sit there all day and tell how Linux was saving starving children in India or some bullshit. Just as long as they are turning a profit.

    12. Re:Proud? by iabervon · · Score: 2

      MicroSoft pushes forward. Linux pushes forward in a different direction. Sure, sometimes MicroSoft does things that turn out to be worthwhile, like supporting USB 2.0, but just as often, MicroSoft does things which turn out to be really bad ideas, and it's just as well Linux never tried them. And there are plenty of things you can do with Linux you can't do with Windows, and plenty of things where Linux supported it first.

  26. You mean Linux DOESN'T support USB 2.0? by Anonymous Coward · · Score: 0

    Open source software usually supports standards BEFORE the major commercial operating systems. I haven't played with Linux for a couple of years, but I always assumed it had support for USB 2.0 from the moment the standard was defined. Looks like OSS isn't what it used to be...

    1. Re:You mean Linux DOESN'T support USB 2.0? by Skapare · · Score: 3, Interesting

      OSS typically lags commercial software support, unless the hardware standards designers and hardware manufacturers work with Linux and/or Linux people right from the start. All too often, the first sample a Linux developer has to go on is bought retail the day a new product is released, and often with no hardware specs to go on. I once contacted a hardware standards group by telephone to inquire about getting a copy of the standard for development purposes. If I wasn't a member of their organization, then I'd have to pay $10,000 and sign a non-disclosure agreement. I was told membership was "very exclusive and expensive". That standard was eventually released when products came out. That was the I2O standard.

      --
      now we need to go OSS in diesel cars
    2. Re:You mean Linux DOESN'T support USB 2.0? by Arandir · · Score: 2

      It's too bad more people don't recognize this. I just can't understand these people crying in their beer because Linux is less than I year behind Microsoft. Geez!

      99% of drivers for Windows are written by device manufacturers. 99% of drivers for Linux are written by people working in their own spare time.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    3. Re:You mean Linux DOESN'T support USB 2.0? by Anonymous Coward · · Score: 0

      Spare time? So you want me to devote my misson critical servers to something people develop on in their free time?

      Fuck you and gimme Windows.

      In the end you get what you pay for is true.

    4. Re:You mean Linux DOESN'T support USB 2.0? by Skapare · · Score: 2

      Not only that, drivers written by hardware vendors tend to be buggier than drivers written by the OS people for the OS they will be used in. Bill Gates has even blamed much of the buggieness of Windows on this. The bugs tend to be in interfacing with the OS itself, In fact, I've even seen it myself, where selecting certain options in the HP printer driver property menu on NT would instantly blue-screen. Linux tends to have more of the latter since OS enthusiasts are doing most of the work.

      --
      now we need to go OSS in diesel cars
    5. Re:You mean Linux DOESN'T support USB 2.0? by Arandir · · Score: 1

      So you want me to devote my misson critical servers to something people develop on in their free time?

      Never seeing your servers, I couldn't answer that. But I do know that the people developing that software may be doing it on their spare time, but that doesn't meant that they aren't professional developers.

      As a professional developer, I can tell you software quality has nothing whatsoever to do with the the pay of the developers.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  27. What was a new USB architecture even needed? by Skapare · · Score: 2, Interesting

    If USB (the interface that hardware presents to core driver software) had been designed well in the first place, then speed would not matter, except for content of data elements that describe speeds (e.g. a value that says this is running at 12mbps or this is running at 480mbps, or the argument to a command that says force this to run at such and such a speed). Maybe they needed to add speed information and speed control, but that wouldn't be a whole change that needs a whole new software architecture (that's something that could have been added in an overnight coding session). What you'd get is data being transferred 40 times faster with 480 mbps.

    Without looking at the specs to see, it's rather obvious that the hardware people just redesigned the interface all over again. Can't someone teach those people some things about reusability and refactoring? And USB isn't the only place this happens. Of course you do need to occaisionally add something to an interface, so a tweaked driver will be needed to fully take advantage of new hardware ideas. But a whole redesign isn't called for ... unless the old design was a POS. But was it the hardware or the software that was a POS? Looks to me like it was the hardware. We'll see when the next speed step occurs. Surely, the Firewire people won't stay 80Mbps down for long. They'll probably aim for somewhere in the 800 to 1600 range next, I bet (if not already). Will the next generation be compatible while still running at the higher speed?

    --
    now we need to go OSS in diesel cars
    1. Re:What was a new USB architecture even needed? by be-fan · · Score: 3, Informative

      Without looking at the specs to see, it's rather obvious that the hardware people just redesigned the interface all over again.
      >>>>>>>>>
      Well, here are the specs so you don't have to make stuff up:
      USB 2.0
      USB 1.0
      The real difference is here:
      OHCI (USB 1.0 host controller, this is the better one)
      UHCI (USB 1.0 host controller, the sucky one)
      EHCI (USB 2.0 host controller spec, has more smarts like OHCI)

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:What was a new USB architecture even needed? by Skapare · · Score: 2

      So a whole new set of commands, just to be able to go faster?

      --
      now we need to go OSS in diesel cars
    3. Re:What was a new USB architecture even needed? by be-fan · · Score: 2

      Not just that. A lot of people complained that UHCI was (a) too hard to write drivers for cuz it was so low level and (b) a voracious devourer of CPU power (I'm streching ;) because it required the CPU to do work better left to the host controller. EHCI is just fixing up stuff that had to be fixed up. Its not all that different from previous standards. Besides, USB 2.0 is a complete specification and needs to talk about things (like signaling, cables, etc) that are *very* different when jumping from 12mbps to 480mbps.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:What was a new USB architecture even needed? by Skapare · · Score: 2

      So then maybe they made it too low level to begin with. It should have been a basic message passing in the buffer kind of thing. I have not looked at the spec and I think I don't even want to in order to avoid polluting my mind. But the best approach would have been a higher level message/packet kind of thing with a few parameters to give status, identify device, device specific parameters/status, and a chunk/window of data. Things like timing and signals should be handled by the controller.

      Part of the trouble is that because vendors can supply Windows drivers, they feel free to change hardware interfaces, and so, this becomes a major problem. There need to be standards in this realm, as well as other places like system calls, libraries, and protocols.

      --
      now we need to go OSS in diesel cars
  28. Prototypes and emulators by yerricde · · Score: 2, Informative

    How can you have support for a non-existing CPU?!

    Just because it hasn't showed up on pricewatch.com yet doesn't mean it doesn't exist. There are prototypes, and before that, there were emulators.

    --
    Will I retire or break 10K?
    1. Re:Prototypes and emulators by Anonymous Coward · · Score: 0

      And who really gives a shit then?? Not like you can buy the damn thing. Linux can also run on a 386, but who really gives a shit? Not like you're gonna use it any time soon.

  29. powerful?? USB?? by Gavitron_zero · · Score: 1, Flamebait

    Last I checked, IEEE 1394 (Firewire) completely kills USB. USB 2.0 only just catches up in speed, and the next version of the IEEE 1394 standard is on the way...and who had the first support for Firewire? Apple. I guess that makes MS number 2 and relegates linux to number 3 of this little artbitrary ranking system.

    1. Re:powerful?? USB?? by greysky · · Score: 1

      Apple was also the first to support USB 2.0. Go figure..

    2. Re:powerful?? USB?? by dnaumov · · Score: 2

      Idiot. Firewire already *IS* supported on Linux.

    3. Re:powerful?? USB?? by TeddyR · · Score: 2

      um...

      http://linux1394.sourceforge.net

      the royalty is only in the NAME and use of the Logo, thats why in Linux its ieee1394 with a different logo...

      --

      --
      Time is on my side
  30. USB 2.0 is 99% hardware interface changes by Johannes · · Score: 5, Informative

    From a high level software perspective, there wasn't that much to do.

    The biggest amount of work was developing the driver for the new EHCI host controller. A new host controller was necessary for the USB wire interface changes to support the faster speeds.

    The reason why development took a while for the EHCI controller was because of the lack of USB 2.0 devices. It's hard to test a driver when you have no hardware to test it against.

    That being said, the article is VERY misleading. Linux has had USB 2.0 support for well over a year now and before 2.5 was forked. It's just that it was backported for 2.4 now. Even that's misleading since it's been in the 2.4.19pre tree since it was forked months ago.

    1. Re:USB 2.0 is 99% hardware interface changes by Anonymous Coward · · Score: 1, Interesting

      In addition to the new EHCI driver, USB 1.1 compatibility through the USB 2.0 hubs is a lot of pain in the butt, and performance improvements may require significant amount of change. So whether you measure this software effort in LOC or man-months, it's much more than 1% by any measure.

      Regarding "Linux has had USB2.0 support for well over a year now", the article wasn't that misleading. It just uses Linux distributions as a (sensible) approximation of the Windows release vehicles -- and USB2.0 is not available in the distributions yet. Your comparison would be fair if we knew since when USB 2.0 support was in the development releases of Windows.

  31. USB root hub vs. USB devices by yerricde · · Score: 2

    > The new version won't instantly enable USB 2.0 to work with Linux-based devices

    *Still* having trouble getting their heads around this Linux thing

    I know exactly what that part of the article means. It means that Linux now supports USB 2 controllers and hubs but does not yet support any USB 2 devices connected to a USB 2 tree.

    --
    Will I retire or break 10K?
  32. I call bullshit by Johannes · · Score: 3, Informative

    You're seeing a couple of different things happening here.

    The host controller is the host side hardware which supports USB. For USB 1.1 (there was a 1.0 standard, but it's broken and hasn't been used in years) there was OHCI and UHCI.

    For USB 2.0, there's EHCI.

    You can't run USB 2.0 on an OHCI or EHCI HCD. You can't run USB 1.1 on an EHCI HCD.

    So how does backward and forward compatibility work? Simple. Your USB 2.0 card has both 1.1 and 2.0 HCD's on it. Most likely you have a couple of OHCI controllers and a couple of EHCI controllers on it.

    That's why Linux saw the 1.1 controllers, because they need to exist to support 1.1 devices plugged into the root hub. Windows will also see the 1.1 controllers for the same reason.

    Now, back to my subject. I call bullshit on devices working a hell of a lot faster in Windows. Why? Because the HCD is the bottleneck. If you plug a 1.1 device into your 2.0 card, it'll still be using the 1.1 controller that's on that card. The 1.1 controller is limited to 12Mbps.

    The testing I've done (as well as other people) shows that Linux is consistently faster than Windows on almost all devices. For those devices where Linux is slower, it's only slower by an insignificant amount. Hardly "a HELL of a lot".

    I won't even begin to explain the ignorance behind your assertion that there is nothing to sync your paln with under Linux.

    1. Re:I call bullshit by XO · · Score: 1

      My USB based camera used to get about 4 frames per second on my P3/600, with USB 1. Plugging it into USB 2.0, I achieve constant frame rates around 25fps at the same color depth and resolution.

      OK, sure, there's lots of software to sync the iPaq with. There's just nothing USEFUL to sync the iPaq with.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  33. What's this about Virtual LAN cards through USB2? by ahfoo · · Score: 2

    I read on some site that USB2.0 could be used to produce virtual NICs. Anybody know someone working on this? It sounds like an interesting way to network a set of boards together with direct connections to each board without using up all the PCI slots. Do you go through a hub of some sort?
    It sure sounds interesting to have something like that especially if this fabled memory pooling version of Mosix ever shows up.

  34. works fine for me, too by g4dget · · Score: 3, Interesting

    I've been using it with 2.4.18, and it's been working just fine (I have a USB 2.0 disk). The interface cards are cheap and the throughput is great. And it seems to be a simple extension of USB 1.0, so drivers like USB storage just seem to work. (Firewire, of course, works as well.)

  35. While Microsoft talks, Linux innovates by Anonymous Coward · · Score: 4, Insightful

    > do you guys think [Linux] would be able to make such advancements if m$ did not exist? what are our biggest device support things that m$ didnt have first?

    What the heck are you talking about?

    Microsoft doesn't make advancements -- the PC hardware developers do.

    Microsoft's primary role has been to hold the hardware developers back.

    Do you remember, in the early nineties, when we had hardware-based Virtual Machine capabilities on the PC? Remember when, because of virtual memory and multitasking innovations from companies like Qualcomm, we were able to run multiple copies of DOS, DR-DOS, and other OSes, in parallel? What happened? Microsoft wanted users to only be able to run one OS -- DOS/Windows -- on their PCs. Thus, Microsoft tied memory management into Windows, thereby destroying further developer on PC VM capabilities.

    Do you remember when the 386 came out, with its new memory protection capabilties? Do you remember how many years it took for Microsoft to provide support for those capabilities? Even Windows 95 still wasn't using it correctly. In fact, it was Linux that, while new, provided support for 386 memory protection -- long before Windows.

    Do you remember when Microsoft hired a group of VMS developers from Digital to develop a stable version of Windows? Remember when they succeeded with NT 3.51? Remember when Microsoft destroyed that stability by allowing video drivers to run in kernel mode, in NT 4.0? Microsoft's history is riddled with backward steps.

    Remember when, in 1990, everyone had a capable GUI, that is, eveyone but Microsoft? By the end of the eighties, we had the Macintosh, the Amiga, the Atari ST, and OS/2 and Geoworks for the PC. It wasn't until five years later that Microsoft came out with something even remotely similar, in Windows 95.

    Remember when there were simple standards for LANs (SMP), security (Kerberos), printers (PCL), and video (VGA)? Microsoft didn't want open standards, because that might help another OS to compete with Windows. Now, because of Microsoft, we have polluted protocols, and complex devices drivers, tied closely into Windows. Further development of interface standards for PC hardware has slowed to a crawl.

    Remember when Microsoft tried to sabotage the standards for Java and OpenGL? Remember the Halloween document where Microsoft stated their plans to "decommoditize" (i.e. destroy the openness of) Internet protocols? Have you noticed that Microsoft has been carrying through on that threat?

    Were you paying attention to how long it took for Microsoft to provide a 64-bit version of Windows? The DEC Alpha version of Windows was a joke, because it was just a 32-bit version of Windows, slightly modified to be able to run on 64-bit hardware. Even now, there is doubt about Microsoft's claim of being 64-bit-ready. Meanwhile, Linux has been running on 64-bit platforms for years.

    Have you noticed all of the hardware innovation that has been taking place with Linux? Just in the last few years, we have seen Linux based supercomputers, Linux-based clusters for movie graphics, Linux on IBM mainframes, Linux in car radios, Linux-based store kiosks, Linux-based digital video recorders, and so on. Many of those innovations could have taken place ten years ago, except for one thing -- they were being held back by Microsoft.

    If there is one thing that has stood out about Microsoft and Windows, it is their _lack_ of innovation. Linux and Open Source are easily outstripping Windows.

    1. Re:While Microsoft talks, Linux innovates by jbolden · · Score: 3, Informative

      I'm going to correct a few things. I'm not sure about this "do you remember" since it seems like you are quoting history you yourself didn't live through.

      > Microsoft doesn't make advancements -- the PC hardware developers do.

      Microsoft has never billed itself as an innovator until very recently. Microsoft's strategy was based on low price and high volume. In terms of volume sales, standardization, and low prices they most certainly have advanced the market as anyone who was around before their dominance will attest to. The biggest area of innovation was the Microsoft, Western Digital, Intel arrangement that led to the IBM PC not incorporating an open standard for hardware so that after Compaq cloned the IBM bios we had a multi-vendor market of compatible PCs. The reason you are running a PC today is because of that "innovation".

      > Do you remember, in the early nineties, when we had hardware-based Virtual Machine capabilities on the > PC? Remember when, because of virtual memory and multitasking innovations from companies like
      > Qualcomm, we were able to run multiple copies of DOS, DR-DOS, and other OSes, in parallel?

      The company was Quarterdeck. You didn't have virtual machines prior to the 386 since the 8088 and 286 didn't offer protected memory. Quarterdeck's 286 task sharing system (Desqview) was able to allow for genuine multi-tasking when the 386 came out. This was about the same time that Microsoft offered multi-tasking in windows. During the years of the 286 (the IBM AT) Microsoft however had a genuine multi-tasking operating system (OS/2) that they believed would be running on hardware sufficient to maintain multi copies of a dos program + heap + stack (i.e. ~ 4 megs of ram). It was only when OS/2 faltered that it became clear that people wanted to run multiple dos sessions and needed more reliability than the Windows 386 / 3.0 system provided. By Windows 3.1 Quarterdeck's products were only marginally better than what came with a generic windows installation.

      > What happened? Microsoft wanted users to only be able to run one OS -- DOS/Windows -- on their PCs. > Thus, Microsoft tied memory management into Windows, thereby destroying further developer on PC
      > VM capabilities.

      This is simply false. There was very little structural difference between QEMM, Quarterdeck's memory manager, and Microsoft's EMM (included in Dos 5.0), EMM had been purchased by a competitor of Quarterdeck's. QEMM was slightly superior but might have created much greater long term compatibility issues for Windows had it become the standard, getting 90% of the benefit for only 20% of the hassles wasn't a bad trade off for Microsoft. I certainly can't see distributing memory mangers free with the operating system as destroying the technology. In addition OS/2 2.0 (which was the last OS/2 that Microsoft had a contribution to) outperformed QEMM/Desqview by a long shot in terms of 386 memory management for virtual 8088s. People today don't run lots of "real mode" applications and thus don't need powerful memory mangers.

      > Do you remember when the 386 came out, with its new memory protection capabilties? Do you
      > remember how many years it took for Microsoft to provide support for those capabilities? Even Windows
      > 95 still wasn't using it correctly.

      None, they offered them in their commercial operating system OS/2 which was used in things like Microsoft LAN manager. They didn't offer it in Windows for the reason we were just discussing above such protection would have caused large numbers of the Dos applications to not function. Memory protection could only become part of the standard operating system when the standard applications didn't violate memory. Microsoft employed a middle ground of moderate protection and still this created enormous problems for a generation of software and software developers used to having dangling pointers all over their code.

      > In fact, it was Linux that, while new, provided support for 386 memory protection -- long before
      > Windows.

      Yes the 386s Unixes had it years before Windows since they didn't have to support Dos applications.

      > Do you remember when Microsoft hired a group of VMS developers from Digital to develop a stable
      > version of Windows? Remember when they succeeded with NT 3.51? Remember when Microsoft
      > destroyed that stability by allowing video drivers to run in kernel mode, in NT 4.0? Microsoft's history is
      > riddled with backward steps.

      I think backwards is too strong. Microsoft has competing interests, high compatibility vs. reliability. Originally they had planned on compatibility going with the windows line and reliability on OS/2. Once OS/2 failed they needed an NT product line. But 3.51 was seen as not compatible enough. Did they make the right choice in retrospect? Probably not, at the time though, and still today, direct mode video was being used by lots of windows apps. What Microsoft did was offered a semi safe solution with direct x.

      > Remember when, in 1990, everyone had a capable GUI, that is, eveyone but Microsoft? By the end of the > eighties, we had the Macintosh, the Amiga, the Atari ST, and OS/2 and Geoworks for the PC.

      For a very long time the business community rejected GUIs in favor of menu system which Microsoft did support via. ansi.sys quite well. In practice there had been GUIs long before the ones you mentioned (like the one for the Apple II), they just didn't take off. Macintosh offered the only successful GUI and GUIs were not a strong customer demand. At the time of OS/2, Geoworks, ... windows was Microsoft's GUI. Notice that Geoworks (similar to the Quarterdeck example above) was not scalable but rather was a niche product that filled a particular hardware gap in Microsoft's strategy existed for a short period of time and died. It was never meant to be a long range platform design in the same sense as MacOS or Windows or OS/2. Finally in terms of OS/2 the bulk of OS/2 applications were text mode. The GUI API wasn't really usable until 1.2 and people didn't mainly use the GUI OS till about 2.0. By that time Windows was in full swing.

      > It wasn't until five years later that Microsoft came out with something even remotely similar, in Windows
      > 95.

      Did the start menu rather than application groups make that much of a difference?

      > Remember when there were simple standards for LANs (SMP),

      Baloney. There were no used standards for LANs at all when NetBUI came out. There were a dozen different vendors all offering different and incompatible systems. Appletalk offered a standard but no way to use non Macs; Novell offered a standard but it cost a bundle, Unix offered a standard that required you run Unix, Lantastic offered a PC standard that didn't scale....

      > security (Kerberos),

      Again a Unix standard.

      > printers (PCL),

      Microsoft has never had any problems with PCL. I'm not even sure what you are talking about if anything Microsoft supported PCL. BTW the printer standard at the time you are talking about was PostScript. Microsoft did have a problem with PostScript believing that it was too expensive to implement for it to ever become truly a printer standard. So what they tried to do was offer the major advantage of PostScript (high quality fonts) for cheap printers by using the bitstream system (today called truetype). I can't say that didn't work out. BTW even today it still costs a lot to get PostScript support in a printer.

      > and video (VGA)?

      Again what did Microsoft ever do to hinder VGA? Dos supported open video drivers so any video card within reason would work fine.

      > Microsoft didn't want open standards, because that might help another OS to compete with Windows.
      > Now, because of Microsoft, we have polluted protocols, and complex devices drivers, tied closely into
      > Windows. Further development of interface standards for PC hardware has slowed to a crawl.

      Again compatibility vs. reliability. You want good quality hardware standards buy a Mac or a RS/6000 or any number of other vendors. Microsoft has been the champion of open hardware which makes standards difficult to say the least. No one benefit more from easy unified interfaces than Microsoft, but what they have refused to do is tie into particular vendors.

      > Remember when Microsoft tried to sabotage the standards for Java and OpenGL? Remember the
      > Halloween document where Microsoft stated their plans to "decommoditize" (i.e. destroy the openness
      > of) Internet protocols? Have you noticed that Microsoft has been carrying through on that threat?

      You are switching from crushing innovation to not being standards compliant. This is a different issue.

      > Were you paying attention to how long it took for Microsoft to provide a 64-bit version of Windows? The
      > DEC Alpha version of Windows was a joke, because it was just a 32-bit version of Windows, slightly
      > modified to be able to run on 64-bit hardware. Even now, there is doubt about Microsoft's claim of being
      > 64-bit-ready. Meanwhile, Linux has been running on 64-bit platforms for years.

      And how many 64 bit CPUs do Microsoft's customer's use? Again Microsoft supports customer demand.

      > If there is one thing that has stood out about Microsoft and Windows, it is their _lack_ of innovation.

      Its funny. Above you go on for standards. If there is one area that Microsoft has innovated in more than any other company its creating a standard base for applications and the creation of standard applications.

    2. Re:While Microsoft talks, Linux innovates by proj_2501 · · Score: 2

      During the years of the 286 (the IBM AT) Microsoft however had a genuine multi-tasking operating system (OS/2)

      HANG ON THERE! OS/2 was made by IBM, not Microsoft.
    3. Re:While Microsoft talks, Linux innovates by be-fan · · Score: 2

      Microsoft's primary role has been to hold the hardware developers back.
      >>>>>.
      I hate MS as much as the next guy, but this isn't really true. If it hadn't been for Microsoft making DirectX, game developers would still be writing their own drivers for the dozen different soundcard types on the market. Or, Creative Labs would have just gotten a monopoly on the market and Sound Blaster compatibility would still be important. Plus, MS keeps adding features to the API, and hardware manufacturers rush ahead to support them. That helps innovation, not hurts it.

      Thus, Microsoft tied memory management into Windows, thereby destroying further developer on PC VM capabilities.
      >>>>
      Do you remember how much DR-DOS sucked? Every modern OS has had built in virtual memory. Microsoft building it in was them following CS theory. And remember, the PC VM hardware is still there, and still works if you care to use it.

      Do you remember when the 386 came out, with its new memory protection capabilties?
      >>>>
      And do you realize that people are STILL bitching and moaning about Windows XP not running their DOS programs? Don't blame Microsoft, blame backwards compatibility. Or more aptly, closed-source software that can't be recompiled to be used when OSs evolve.

      Remember when Microsoft destroyed that stability by allowing video drivers to run in kernel mode, in NT 4.0? Microsoft's history is riddled with backward steps.
      >>>>>
      So MS decided that microkernels were out. Along with everybody else! As for video drivers, those aren't the real problem. The real problem was moving the GDI into the kernel.

      Remember when, in 1990, everyone had a capable GUI, that is, eveyone but Microsoft? By the end of the eighties, we had the Macintosh, the Amiga, the Atari ST, and OS/2 and Geoworks for the PC. It wasn't until five years later that Microsoft came out with something even remotely similar, in Windows 95.
      >>>>>
      This holds back hardware developers how?

      Remember when there were simple standards for LANs (SMP), security (Kerberos), printers (PCL), and video (VGA)? Microsoft didn't want open standards, because that might help another OS to compete with Windows. Now, because of Microsoft, we have polluted protocols, and complex devices drivers, tied closely into Windows.
      >>>>
      Windows 2000 uses TCP/IP for LANs, and supports Kerberos security. It fully supports Postscript printers, and the WinPrinters and WinModems came out because hardware developers were lazy, not Microsoft. As for the VGA bit, you're joking, right? (S)VGA is an anachronism that doesn't support linear memory, high-res/high-bandwidth modes, and most importantly, acceleration. And acceleration is hideosly complex, which is why graphics drivers are complex. As for open standards, VESA had the potential to be one, but they screwed themselves when they tried to charge for VBE/AF. Besides, hardware these days cannot keep the same programming interface. Just look at ATI. They've been unable to keep their drivers compatible across even two generations (R200 -> R300) of cards. The real problem is a lack of register specs from graphics manufacturers, not great Microsoft technologies like DirectX (their one positive contribution to computing).

      Further development of interface standards for PC hardware has slowed to a crawl.
      >>>
      Blame the HW manufacturers, who try to keep charge for even basic things like the PCI specs.

      Remember when Microsoft tried to sabotage the standards for Java and OpenGL? Remember the Halloween document where Microsoft stated their plans to "decommoditize" (i.e. destroy the openness of) Internet protocols? Have you noticed that Microsoft has been carrying through on that threat?
      >>>>
      And have you noticed that OpenGL is more important than ever? And Java never really took off client-side anyway?

      Were you paying attention to how long it took for Microsoft to provide a 64-bit version of Windows? The DEC Alpha version of Windows was a joke, because it was just a 32-bit version of Windows, slightly modified to be able to run on 64-bit hardware. Even now, there is doubt about Microsoft's claim of being 64-bit-ready. Meanwhile, Linux has been running on 64-bit platforms for years.
      >>>
      Yes, Linux runs on platforms nobody buys. Windows just runs on platforms people actually purchase. You can't blame them for being in a different business.

      Have you noticed all of the hardware innovation that has been taking place with Linux? Just in the last few years, we have seen Linux based supercomputers, Linux-based clusters for movie graphics, Linux on IBM mainframes, Linux in car radios, Linux-based store kiosks, Linux-based digital video recorders, and so on. Many of those innovations could have taken place ten years ago, except for one thing -- they were being held back by Microsoft.
      >>>>>
      I see how Linux helps driver hardware innovation because its a free, open source, embeddable soluation, but I fail to see how Microsoft hurt it. It's like blaming your car for not being a helicopter.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:While Microsoft talks, Linux innovates by jbolden · · Score: 1

      It was a joint project of IBM and Microsoft during the 286 era. IBM started independent development before the release of 2.0 (that is Microsoft code was all over 2.0) but all the changes from 2.0->2.1->3.0 were IBM's. For example that was why the windows API emulation in OS/2 was so good it used the source for the Windows API.

    5. Re:While Microsoft talks, Linux innovates by Anonymous Coward · · Score: 0

      > it seems like you are quoting history you yourself didn't live through.

      Wrong. I started developing on the IBM System 370 in 1976. I installed Windows 1.0 on a single-1.44-floppy Kaypro 2000 laptop (they claimed it was impossible -- it took six hours of switching floppy disks). I modified the HP Laserjet driver for Borland's Sprint text editor to work with my HP Deskjet 500. I used Software Carousel to run Gem Draw, Turbo Pascal, FFM (a shareware file manager), and a DOS prompt, in swappable sessions, all loaded into 1 MB of memory on a PC. I could go on, but suffice it to say that I was there, and I was paying attention.

      > Microsoft has never billed itself as an innovator until very recently.

      Microsoft still isn't an innovator. .Net is a combination of Java (the C# language), and cross-language capabilities that already exist on other platforms (e.g. IBM's Logical Environment for C, PL/1, and Cobol). Microsoft hired the main developer of Borland's Delphi to provide them with C#, and IIRC they bought a company that was already working on the cross-language capabilities.

      > Microsoft's strategy was based on low price and high volume.

      Microsoft's strategy has always been to sabotage the competition. They made a change in DOS 5 (IIRC) that broke Geoworks. They put a fake error message in Windows to make people afraid to use DR-DOS, then added secret API calls to Windows 95 to prevent it from running on DR-DOS. Microsoft lied to WordPerfect about supporting OS/2, then provided broken Windows API calls to WordPerfect while using secret calls in MS Word. Microsoft changed the function-key API to break AMI Pro, which, at the time, was the fastest growing word processor. Microsoft's efforts to sabotage Java ("grow the polluted Java market"), Netscape ("make the use of any other browser a jolting experience"), and Linux ("decommoditize protocols") are well documented.

      > > Do you remember, in the early nineties, when we had hardware-based Virtual Machine capabilities on the > PC? Remember when, because of virtual memory and multitasking innovations from companies like Qualcomm, we were able to run multiple copies of DOS, DR-DOS, and other OSes, in parallel?

      > The company was Quarterdeck. You didn't have virtual machines prior to the 386 since the 8088 and 286 didn't offer protected memory. Quarterdeck's 286 task sharing system (Desqview) was able to allow for genuine multi-tasking when the 386 came out. This was about the same time that Microsoft offered multi-tasking in windows.

      It would appear that you are the one who wasn't there at the time.

      Quarterdeck did indeed provide the software, Desqview, that allowed multitasking on the PC.

      However, Desqview provided multitasking capabilities even before the 386 arrived.

      Before the 386, Desqview provided multitasking by making use of hardware memory-management capabilities built into certain memory cards, which, if I recall correctly, were built by Qualcomm.

      At the time, there were two competing standards for taking PC memory beyond 1 MB, called extended and expanded memory (don't ask me which was which). The simpler, and less expensive option came from memory cards supplied by AST. Those cards did not have any multitasking capabilities. The more expensive memory cards came from Qualcomm (IIRC), and those were the cards that had the necessary hardware and protocols to allow Desqview to provide full multitasking on a PC.

      At that time, both companies, and everyone else, knew that having two different standards was holding everyone back. Thus, an industry consortium formed, that included both memory card manufacturers, and dozens of other major players. That consortium came up with a single memory, standard, which not only provided for multitasking and hardware-based virtual memory, but was also backward compatible with the two earlier standards -- all the old software would still run. I remember cheering out loud when I read about it.

      As soon as the consortium had announced its memory standard, however, Microsoft immediately announced that Windows would be using a different standard, one that tied memory management into Windows, and one that provided none of the memory protection and multitasking abilities of the consortium standard.

      Multitasking on the PC was already working before the 386 was even introduced. It was going to work even better. Microsoft destroyed it.

      And you are right that the 386 also makes virtual-machines possible. That's one of the reasons why Microsoft has worked so hard to tie hardware peripherals directly into Windows. Now, the only way to get VM capabilities on a PC is through a software layer, like VMware, that sits on top of an OS, or emulates the complex interaction between Windows and the PC hardware.

      > [Microsoft] didn't offer [386 memory protection] in Windows for the reason we were just discussing above such protection would have caused large numbers of the Dos applications to not function.

      That's BS. We have 386 memory protection today, and I can still run old DOS programs. I have it on Windows NT, I have it on Linux, and it's on OS/2. You can talk about what OS/2 may or may not have been doing years ago, but OS/2 today makes full use of the CPU and memory capabilities, and still has better DOS emulation than even Windows 3.1 did.

      > > Remember when, in 1990, everyone had a capable GUI, that is, eveyone but Microsoft? By the end of the > eighties, we had the Macintosh, the Amiga, the Atari ST, and OS/2 and Geoworks for the PC.

      > For a very long time the business community rejected GUIs in favor of menu system which Microsoft did support via. ansi.sys quite well.

      Nonesense. The industry chose the PC because it was cheaper. Just because Microsoft hadn't yet provided a GUI doesn't mean the industry didn't want one.

      > Notice that Geoworks was not scalable but rather was a niche product that filled a particular hardware gap in Microsoft's strategy existed for a short period of time and died.

      You are kidding, aren't you? Geoworks was intended to be, and in fact was, a full GUI layer running on top of the OS. Geoworks was one of the top selling pieces of PC software at the time, and came pre-loaded with a good percentage of PCs. And Microsoft sabotaged Geoworks by introducing an incompatibility into DOS. Geoworks soon provided a patch to get around the problem, which I ordered, but by then it was too late -- Geoworks had been killed.

      In order to prevent new competitors like DR-DOS and Geoworks, Microsoft tied the GUI layer into the OS. Note that Microsoft lied, and said that Windows was combined with DOS in Windows 95, but the DR-DOS lawsuit eventually proved that all Microsoft had done was add some secret API calls to make Windows incompatible with DR-DOS.

      > > It wasn't until five years later that Microsoft came out with something even remotely similar, in Windows 95.

      > Did the start menu rather than application groups make that much of a difference?

      That is a truly deceptive response. What happened to all of your PC knowledge all of a sudden?

      Geoworks and OS/2 (and the Amiga) were pre-emptive multitasking. Windows 3.1, on the other hand, used co-operative multitasking, which meant any badly-written application could prevent other applications from running. Windows 95 was more-or-less pre-emptive, though, because the GUI is tied into the OS, there are still far too many cases where Windows 95 will not let me switch tasks.

      > > Remember when there were simple standards for LANs (SMP),

      > Baloney. There were no used standards for LANs at all when NetBUI came out.

      That's true early on. But IBM introduced SMB, clean and simple, then Microsoft "embraced and extended" it. Now it's an undocumented mess.

      > > security (Kerberos),

      > Again a Unix standard.

      Which Microsoft has again adopted, and extended in proprietary, undocumented ways.

      The value of a standard like Kerberos is in its being open and shared. It is that value that Microsoft seeks to destroy. Cross-platform compatibility does not fit well with Microsoft's lock-in strategy.

      > > printers (PCL),
      > > and video (VGA)?
      > > Microsoft didn't want open standards,


      > Microsoft has never had any problems with PCL.
      > Again what did Microsoft ever do to hinder VGA?


      The point is that common interface standards were developing on their own, until Microsoft trumped the standards process. Microsoft began taking an active role in defining hardware standards for the PC.

      Microsoft has studiously resisted defining or improving standards at the points where they are simple, and can be shared. Instead, Microsoft set the "standard" at a complex interface between to driver and the OS, a point where, due to its complexity, hardware manufactures are unable to share. Thus, we now have a situation where there are no standards, and every printer manufacturer, and every video manufacturer, has their own unique driver.

      Thus, today, it is not enough for an OS like Linux to support a common set of video and printer interface standards. Now, Linux can't communicate with a hardware peripheral without having a complex driver to deal with that hardware's unique interface. Companies like NVidia are so married to this lock-in process, that their hardware interface is undocumented and secret.

      > Microsoft has been the champion of open hardware which makes standards difficult to say the least. No one benefit more from easy unified interfaces than Microsoft, but what they have refused to do is tie into particular vendors.

      Hahahahaha...please stop...I can't breath.

      The reason why Linux and OS/2 have so much trouble communicating with the various printers, and video hardware, is because there are no standards. That's the way Microsoft intended it to be.

      What Microsoft wanted, and achieved, was for each peripheral to have its own unique interface, with its own unique driver -- a driver that ties it to only Windows.

      Of course, Microsoft's strategy backfires somewhat. The same thing that makes it hard for Linux to interface with PC peripherals, also makes it hard for Windows NT and 2000. That's why the hardware support has been so poor in Windows NT, because, like Linux, there is no clear set of standards for Windows NT to support -- each peripheral needs its own unique driver, rewritten just for NT.

      > > Remember when Microsoft tried to sabotage the standards for Java and OpenGL? Remember the Halloween document where Microsoft stated their plans to "decommoditize" (i.e. destroy the openness of Internet protocols? Have you noticed that Microsoft has been carrying through on that threat?

      > You are switching from crushing innovation to not being standards compliant. This is a different issue.

      You don't consider it an innovation to be able to automatically download and run software in your browser, in complete safety and security?

      You don't consider it an innovation for the entire world be able to communicate, publish, and read information, using any platform?

      You don't consider it to be "crushing" innovation when Microsoft pollutes those common standards, thus sabotaging and destroying the capabilities they provide?

      > And how many 64 bit CPUs do Microsoft's customer's use? Again Microsoft supports customer demand.

      Haha, please, I asked you to stop with the jokes.

      Industry has been running 64-bit servers for a long time. If they could do so more cheaply, and just as well, with Windows, then they would. Microsoft tried to compete in that field, prompting articles that appointed Windows NT as the Unix killer. Microsoft failed because they weren't up to the challenge. Microsoft's rate of development -- their innovation if you will -- is too slow, and of too poor quality.

      > Above you go on for standards. If there is one area that Microsoft has innovated in more than any other company its creating a standard base for applications and the creation of standard applications.

      As I have said, the truth is the opposite of your claim.

      What standards exist have occurred despite Microsoft. Microsoft's "Embrace, Extend, Extinguish" strategy has destroyed simple standards, and replaced them with hoops that everyone has to jump through in order to run on a PC. Microsoft's "standards" are intentionally-complex interfaces, intended to tie hardware manufacturers to Windows, by making it too expensive to consider supporting more than one platform.

      But don't take my word for it. Microsoft described this process themselves, in the Halloween Document:

      > "OSS projects have been able to gain a foothold in many server applications because of the wide utility of highly commoditized, simple protocols. By extending these protocols and developing new protocols, we can deny OSS projects entry into the market."

      But Microsoft has been digging their own grave. There are few left who trust Microsoft and, with the growth of Linux, I expect things to change. Once the hardware manufacturers discover how much easier it is to interface with Linux, they are going to start to innovate again. Actually, as I pointed out in my earlier post, that process has already started.

    6. Re:While Microsoft talks, Linux innovates by jbolden · · Score: 1

      >> Microsoft's strategy was based on low price and high volume.

      > Microsoft's strategy has always been to sabotage the competition. [examples snipped]

      As someone who was also there I can tell you it wasn't sabotage. Let's take an example of office suites before moving onto the specifics. For a while you had 3 word processors: AMI Pro (which btw I used), WordPerfect and Word running about equal. Ami Pro offered the most features but was the slowest and the biggest resource hog. Word Perfect hadn't made huge changes since their WP for Dos 4.2 version and mainly was riding on past success (similar to Word today) by just slapping a windows GUI on top of the same product they had been selling for 5 years; consequently Word Perfect was starting to fall slightly behind but mainly it was hard to argue why to switch. Word offered the best integration with Windows. But in reality none of the 3 really stood out. However Microsoft offered the competitive upgrade at $129 (with such lose terms that this "upgrade" essentially amounted to a new list price) while the rest charged about $325 street ($495 retail) the result was that new users went to Word overwhelmingly.

      Similarly with Lotus, Quatro Pro, and Excel or Access, Paradox and FoxPro (which Microsoft ended up buying). Microsoft beat the competition on price more than anything else.
      IMHO AMI Pro was the best word processor, Quatro the best spread sheet and FoxPro the best database. But Word/Excel/Access was a winning combination. And further once "integration" was considered an important feature the only real choice was Word/Excel/Access since you could cut and paste between them.

      That got us to where we are today. I don't see sabotage I see offering a pretty good product at half the cost and then becoming the "standard".

      As for your examples most of them I remember and agree with. There was no question that Dr Dos was attacked by Windows and GeoWorks was attacked by Dos. As for WordPerfect nothing stopped them from using their market leading position to advance word processor technology bad API calls or not.

      > > The company was Quarterdeck. You didn't have virtual machines prior to the 386 since the 8088 and 286 didn't offer protected memory. Quarterdeck's 286 task sharing system (Desqview) was able to allow for genuine multi-tasking when the 386 came out. This was about the same time that Microsoft offered multi-tasking in windows.

      > It would appear that you are the one who wasn't there at the time.

      > Quarterdeck did indeed provide the software, Desqview, that allowed multitasking on the PC. However, Desqview provided multitasking capabilities even before the 386 arrived.

      On the 286 it provided task sharing as their own literature attested. I was a big fan of Desqview and used it all the time.

      > At the time, there were two competing standards for taking PC memory beyond 1 MB, called extended
      > and expanded memory (don't ask me which was which).

      Extended was memory on the mother board. Expanded was memory added on an expansion card attached to the bus.

      > The simpler, and less expensive option came from memory cards supplied by AST. Those cards did not
      > have any multitasking capabilities. The more expensive memory cards came from Qualcomm (IIRC), and
      > those were the cards that had the necessary hardware and protocols to allow Desqview to provide full
      > multitasking on a PC.

      OK what you mean is using about 1 meg in dos mode. Quaterdeck's 286 memory manager (never used it so I don't remember the name) + Desqview allowed you to task share multiple independent copies of Dos.

      > At that time, both companies, and everyone else, knew that having two different standards was holding
      > everyone back. Thus, an industry consortium formed, that included both memory card manufacturers, and
      > dozens of other major players. That consortium came up with a single memory, standard, which not only
      > provided for multitasking and hardware-based virtual memory, but was also backward compatible with
      > the two earlier standards -- all the old software would still run. I remember cheering out loud when I read
      > about it.

      Why? In retrospect you have to agree it was a short term work around. Within a year or two you had expanded memory right on the mother board and OSes supporting it. More importantly by getting people to finally break 8088 compatibility and run in "standard mode" we now had a 16 meg limit without all the weird paging.

      > As soon as the consortium had announced its memory standard, however, Microsoft immediately
      > announced that Windows would be using a different standard, one that tied memory management into
      > Windows, and one that provided none of the memory protection and multitasking abilities of the
      > consortium standard.

      Which was btw roughly the same as the one used on most 32 bit OSes at the time and has worked pretty well. That standard (modulo one more upgrade) is what we use today on every Intel based OS.

      > > [Microsoft] didn't offer [386 memory protection] in Windows for the reason we were just discussing above such protection would have caused large numbers of the Dos applications to not function.

      > That's BS. We have 386 memory protection today, and I can still run old DOS programs. I have it on
      > Windows NT, I have it on Linux, and it's on OS/2. You can talk about what OS/2 may or may not have
      > been doing years ago, but OS/2 today makes full use of the CPU and memory capabilities, and still has
      > better DOS emulation than even Windows 3.1 did.

      I agree 100% that OS/2 had better Dos emulation that Windows 3.1; no question IBM dropped the ball on that one. As I like to say Windows NT 4.0 was about as good as OS/2 2.1; and Windows 2000 about as good as OS/2 3.0.

      In any case I don't think its true at all you can run your old Dos games with loose memory on NT/2000. I've tried on a few and they don't run at all.

      >> > Remember when, in 1990, everyone had a capable GUI, that is, eveyone but Microsoft? By the end of the > eighties, we had the Macintosh, the Amiga, the Atari ST, and OS/2 and Geoworks for the PC.

      >> For a very long time the business community rejected GUIs in favor of menu system which Microsoft did support via. ansi.sys quite well.

      > Nonesense. The industry chose the PC because it was cheaper.

      Cheaper than what? PCs were more expensive than Macs in the early days. Certainly they were always more expensive than Amiga. PCs didn't really catch up in price with Macs until after the days of gray market hardware and by then they had already been the standard. Being cheaper (IMHO) had kept the PCs the standard for the last 15 years but if anything I think it was Lotus 1-2-3 and WordPerfect that made PCs the standard in spite of higher costs (and that's given that JAZZ was IMHO a much better Lotus spread sheet program than 1-2-3).

      > Just because Microsoft hadn't yet provided a GUI doesn't mean the industry didn't want one.

      I don't agree but this point will have to wait till others get resolved.

      >> Notice that Geoworks was not scalable but rather was a niche product that filled a particular hardware gap in Microsoft's strategy existed for a short period of time and died.

      > You are kidding, aren't you? Geoworks was intended to be, and in fact was, a full GUI layer running on
      > top of the OS. Geoworks was one of the top selling pieces of PC software at the time, and came pre-
      > loaded with a good percentage of PCs.

      Huh? IBM didn't preload it, Gateway didn't preload it, Dell didn't preload it, Compaq didn't preload it, Tandy didn't preload it, that generic company which sold in retail stores (can't remember the name) didn't preload it. What did it sell a couple hundred thousand copies a million over its lifetime tops?

      > > It wasn't until five years later that Microsoft came out with something even remotely similar, in Windows 95.

      > Did the start menu rather than application groups make that much of a difference?

      > That is a truly deceptive response. What happened to all of your PC knowledge all of a sudden?

      > Geoworks and OS/2 (and the Amiga) were pre-emptive multitasking.

      Geoworks was certainly not pre-emptive it was task sharing. This was one of the selling points it ran on low end hardware unlike the powerful multitasking systems "windows for the rest of us" kind of thing.

      > Windows 3.1, on the other hand, used co-operative multitasking, which meant any badly-written
      > application could prevent other applications from running. Windows 95 was more-or-less pre-emptive,
      > though, because the GUI is tied into the OS, there are still far too many cases where Windows 95 will not
      > let me switch tasks.

      I'm not sure I'd call Windows 98 genuinely preemptive. But in case going back even to the Windows 3.0 days "Enhanced mode" was preemptive by Windows 3.1 while "standard mode" was task sharing. I know that didn't change by 95 my wife still runs 98 I'd could write a quick app to test if it even changed by 98 but I doubt it given the types of application related crashes she still has.

      > Cross-platform compatibility does not fit well with Microsoft's lock-in strategy.

      I'd agree that where Microsoft was dominant it attempted lock-in-strategies similar to what IBM does on their mainframe or Digital did with VMS, or the Unix vendors did back in the 1980's. In all fairness I'd have to credit POSIX and GNU with trying to end lock-in but I don't think they've succeeded yet.

      > > printers (PCL),
      > > and video (VGA)?
      > > Microsoft didn't want open standards,

      > Microsoft has never had any problems with PCL.
      > Again what did Microsoft ever do to hinder VGA?

      > The point is that common interface standards were developing on their own, until Microsoft trumped the standards process. Microsoft began taking an active role in defining hardware standards for the PC.

      I still don't see what you are talking about. Microsoft has had very little impact on printer standards other than the fight against PostScript (see previous comment). As for VGA video standards were still being set by IBM with CGA, EGA, VGA, UVGA and XVGA... both before and after VGA. All Microsoft did was publish a simple interface for hardware to right drivers for their OS. It was only when people wanted both access within the GUI (I not following the "reboot to dos to play games") and also direct video writes that drivers become meaningful tied to Windows. As far as I know that was really being pushed by the gaming / video card market.

      > Microsoft has studiously resisted defining or improving standards at the points where they are simple, and > can be shared. Instead, Microsoft set the "standard" at a complex interface between to driver and the OS, > a point where, due to its complexity, hardware manufactures are unable to share. Thus, we now have a
      > situation where there are no standards, and every printer manufacturer, and every video manufacturer, has > their own unique driver.

      As for printers that's really not true. Most accept a "stdin" type access using a documented interface. Its only for reverse communication that they need OS hooks. Here we can use examples from non Microsoft since printers are used in more advanced ways by other operating systems. Take a look at the code for print symbionts in VMS I'd say they make a PC device driver look trivial comparatively. Look at the forms management hooks needed to support a printer under PFS again pretty trivial compared to Windows.

      Again the evidence shows that printer manufacturers would rather have unique features to their products which require complex OS specific interfaces then follow a standard. Printer languages are a lot like programming languages they offer different functionality and features. PCL (HP), MetaCode (Xerox), PostScript (Adobe), AFP (IBM), Epson escape sequences (Epson / Digital) existed before Microsoft had any influence and many of them existed before Microsoft (IPDS, 3211...).

      I don't know video nearly as well as print so its harder for me to be as specific. But as I mentioned above I'm not sure what reasonable standards have even been proposed that most hardware manufacturers would have agreed to.

      > Thus, today, it is not enough for an OS like Linux to support a common set of video and printer interface > standards. Now, Linux can't communicate with a hardware peripheral without having a complex driver to > deal with that hardware's unique interface. Companies like NVidia are so married to this lock-in process, > that their hardware interface is undocumented and secret.

      I'd agree. I'm just not sure how Microsoft is at fault for this. It seems like it evolved independently of them. Again I can speak more easily printers than video.

      > Microsoft has been the champion of open hardware which makes standards difficult to say the least. No one benefit more from easy unified interfaces than Microsoft, but what they have refused to do is tie into particular vendors.

      > Hahahahaha...please stop...I can't breath.

      > The reason why Linux and OS/2 have so much trouble communicating with the various printers, and video hardware, is because there are no standards. That's the way Microsoft intended it to be.

      > What Microsoft wanted, and achieved, was for each peripheral to have its own unique interface, with its own unique driver -- a driver that ties it to only Windows.

      > Of course, Microsoft's strategy backfires somewhat. The same thing that makes it hard for Linux to
      > interface with PC peripherals, also makes it hard for Windows NT and 2000. That's why the hardware
      > support has been so poor in Windows NT, because, like Linux, there is no clear set of standards for
      > Windows NT to support -- each peripheral needs its own unique driver, rewritten just for NT.

      What evidence do you have for this being Microsoft's intent rather than something that just occurred? Video standards seem much more unified today than they were 10 years ago (when IBM ruled) and every application had to ship with 3 dozen video modes for different cards. If a hardware manufacturer releases the spec its easy to write a driver just most of them consider this a trade secret.

      > > > Remember when Microsoft tried to sabotage the standards for Java and OpenGL? Remember the Halloween document where Microsoft stated their plans to "decommoditize" (i.e. destroy the openness of Internet protocols? Have you noticed that Microsoft has been carrying through on that threat?

      > > You are switching from crushing innovation to not being standards compliant. This is a different issue.

      > You don't consider it an innovation to be able to automatically download and run software in your browser, in complete safety and security?

      I don't know that Microsoft objects to that. The object to Sun controlling that process similar to their fight against PostScript as the PC standard. There is no question that Microsoft will fight any company that tries to establish control over some aspect of the PC (that is a standard not set by Microsoft).

      > You don't consider it an innovation for the entire world be able to communicate, publish, and read information, using any platform?

      They can today PDF works fine, which Microsoft opposed but didn't really do anything about since they aren't as worried about Adobe as they were 10 years ago.

      > You don't consider it to be "crushing" innovation when Microsoft pollutes those common standards, thus > sabotaging and destroying the capabilities they provide?

      No I don't. If Microsoft were to make their browser say Sun Java incompatible that would be "crushing innovation". I think Microsoft has as much right to release a different VM as Sun does. I happen to use Sun's with I.E. 6.0 and it works fine. It wouldn't if Microsoft didn't want me to be able to use Sun's VM.

      > And how many 64 bit CPUs do Microsoft's customer's use? Again Microsoft supports customer demand.

      > Haha, please, I asked you to stop with the jokes.

      > Industry has been running 64-bit servers for a long time. If they could do so more cheaply, and just as
      > well, with Windows, then they would. Microsoft tried to compete in that field, prompting articles that
      > appointed Windows NT as the Unix killer. Microsoft failed because they weren't up to the challenge.
      > Microsoft's rate of development -- their innovation if you will -- is too slow, and of too poor quality.

      I agree that Microsoft NT server has failed to gain the kind of dominance that NT workstation has. I certainly agree that NT server isn't designed for really high end hardware (and for that matter I don't think Unix is great for enterprise apps either, I think S/390 and VMS are vastly better but that's another thread). Microsoft has failed much more spectacularly in the embedded systems market. But failure is not crushing innovation its just losing.

      > > Above you go on for standards. If there is one area that Microsoft has innovated in more than any other company its creating a standard base for applications and the creation of standard applications.

      > As I have said, the truth is the opposite of your claim.

      > What standards exist have occurred despite Microsoft. Microsoft's "Embrace, Extend, Extinguish"
      > strategy has destroyed simple standards, and replaced them with hoops that everyone has to jump through > in order to run on a PC. Microsoft's "standards" are intentionally-complex interfaces, intended to tie
      > hardware manufacturers to Windows, by making it too expensive to consider supporting more than one
      > platform.

      The above referred to applications standards not hardware standards. That was the whole point. They have succeeded in absorbing the incredibly complex world of PC hardware into the OS.

      > But Microsoft has been digging their own grave. There are few left who trust Microsoft and, with the
      > growth of Linux, I expect things to change. Once the hardware manufacturers discover how much easier
      > it is to interface with Linux, they are going to start to innovate again. Actually, as I pointed out in my
      > earlier post, that process has already started.

      I'd agree that Linux offers a wonderful test bed for hardware manufacturers and it is quite likely that Linux's hardware support will be far better than Microsoft's in the near future. Again the point of this thread was about Microsoft crushing innovation.
      >> Microsoft's strategy was based on low price and high volume.

      > Microsoft's strategy has always been to sabotage the competition. [examples snipped]

      As someone who was also there I can tell you it wasn't sabotage. Let's take an example of office suites before moving onto the specifics. For a while you had 3 word processors: AMI Pro (which btw I used), WordPerfect and Word running about equal. Ami Pro offered the most features but was the slowest and the biggest resource hog. Word Perfect hadn't made huge changes since their WP for Dos 4.2 version and mainly was riding on past success (similar to Word today) by just slapping a windows GUI on top of the same product they had been selling for 5 years; consequently Word Perfect was starting to fall slightly behind but mainly it was hard to argue why to switch. Word offered the best integration with Windows. But in reality none of the 3 really stood out. However Microsoft offered the competitive upgrade at $129 (with such lose terms that this "upgrade" essentially amounted to a new list price) while the rest charged about $325 street ($495 retail) the result was that new users went to Word overwhelmingly.

      Similarly with Lotus, Quatro Pro, and Excel or Access, Paradox and FoxPro (which Microsoft ended up buying). Microsoft beat the competition on price more than anything else.
      IMHO AMI Pro was the best word processor, Quatro the best spread sheet and FoxPro the best database. But Word/Excel/Access was a winning combination. And further once "integration" was considered an important feature the only real choice was Word/Excel/Access since you could cut and paste between them.

      That got us to where we are today. I don't see sabotage I see offering a pretty good product at half the cost and then becoming the "standard".

      As for your examples most of them I remember and agree with. There was no question that Dr Dos was attacked by Windows and GeoWorks was attacked by Dos. As for WordPerfect nothing stopped them from using their market leading position to advance word processor technology bad API calls or not.

      > > The company was Quarterdeck. You didn't have virtual machines prior to the 386 since the 8088 and 286 didn't offer protected memory. Quarterdeck's 286 task sharing system (Desqview) was able to allow for genuine multi-tasking when the 386 came out. This was about the same time that Microsoft offered multi-tasking in windows.

      > It would appear that you are the one who wasn't there at the time.

      > Quarterdeck did indeed provide the software, Desqview, that allowed multitasking on the PC. However, Desqview provided multitasking capabilities even before the 386 arrived.

      On the 286 it provided task sharing as their own literature attested. I was a big fan of Desqview and used it all the time.

      > At the time, there were two competing standards for taking PC memory beyond 1 MB, called extended
      > and expanded memory (don't ask me which was which).

      Extended was memory on the mother board. Expanded was memory added on an expansion card attached to the bus.

      > The simpler, and less expensive option came from memory cards supplied by AST. Those cards did not
      > have any multitasking capabilities. The more expensive memory cards came from Qualcomm (IIRC), and
      > those were the cards that had the necessary hardware and protocols to allow Desqview to provide full
      > multitasking on a PC.

      OK what you mean is using about 1 meg in dos mode. Quaterdeck's 286 memory manager (never used it so I don't remember the name) + Desqview allowed you to task share multiple independent copies of Dos.

      > At that time, both companies, and everyone else, knew that having two different standards was holding
      > everyone back. Thus, an industry consortium formed, that included both memory card manufacturers, and
      > dozens of other major players. That consortium came up with a single memory, standard, which not only
      > provided for multitasking and hardware-based virtual memory, but was also backward compatible with
      > the two earlier standards -- all the old software would still run. I remember cheering out loud when I read
      > about it.

      Why? In retrospect you have to agree it was a short term work around. Within a year or two you had expanded memory right on the mother board and OSes supporting it. More importantly by getting people to finally break 8088 compatibility and run in "standard mode" we now had a 16 meg limit without all the weird paging.

      > As soon as the consortium had announced its memory standard, however, Microsoft immediately
      > announced that Windows would be using a different standard, one that tied memory management into
      > Windows, and one that provided none of the memory protection and multitasking abilities of the
      > consortium standard.

      Which was btw roughly the same as the one used on most 32 bit OSes at the time and has worked pretty well. That standard (modulo one more upgrade) is what we use today on every Intel based OS.

      > > [Microsoft] didn't offer [386 memory protection] in Windows for the reason we were just discussing above such protection would have caused large numbers of the Dos applications to not function.

      > That's BS. We have 386 memory protection today, and I can still run old DOS programs. I have it on
      > Windows NT, I have it on Linux, and it's on OS/2. You can talk about what OS/2 may or may not have
      > been doing years ago, but OS/2 today makes full use of the CPU and memory capabilities, and still has
      > better DOS emulation than even Windows 3.1 did.

      I agree 100% that OS/2 had better Dos emulation that Windows 3.1; no question IBM dropped the ball on that one. As I like to say Windows NT 4.0 was about as good as OS/2 2.1; and Windows 2000 about as good as OS/2 3.0.

      In any case I don't think its true at all you can run your old Dos games with loose memory on NT/2000. I've tried on a few and they don't run at all.

      >> > Remember when, in 1990, everyone had a capable GUI, that is, eveyone but Microsoft? By the end of the > eighties, we had the Macintosh, the Amiga, the Atari ST, and OS/2 and Geoworks for the PC.

      >> For a very long time the business community rejected GUIs in favor of menu system which Microsoft did support via. ansi.sys quite well.

      > Nonesense. The industry chose the PC because it was cheaper.

      Cheaper than what? PCs were more expensive than Macs in the early days. Certainly they were always more expensive than Amiga. PCs didn't really catch up in price with Macs until after the days of gray market hardware and by then they had already been the standard. Being cheaper (IMHO) had kept the PCs the standard for the last 15 years but if anything I think it was Lotus 1-2-3 and WordPerfect that made PCs the standard in spite of higher costs (and that's given that JAZZ was IMHO a much better Lotus spread sheet program than 1-2-3).

      > Just because Microsoft hadn't yet provided a GUI doesn't mean the industry didn't want one.

      I don't agree but this point will have to wait till others get resolved.

      >> Notice that Geoworks was not scalable but rather was a niche product that filled a particular hardware gap in Microsoft's strategy existed for a short period of time and died.

      > You are kidding, aren't you? Geoworks was intended to be, and in fact was, a full GUI layer running on
      > top of the OS. Geoworks was one of the top selling pieces of PC software at the time, and came pre-
      > loaded with a good percentage of PCs.

      Huh? IBM didn't preload it, Gateway didn't preload it, Dell didn't preload it, Compaq didn't preload it, Tandy didn't preload it, that generic company which sold in retail stores (can't remember the name) didn't preload it. What did it sell a couple hundred thousand copies a million over its lifetime tops?

      > > It wasn't until five years later that Microsoft came out with something even remotely similar, in Windows 95.

      > Did the start menu rather than application groups make that much of a difference?

      > That is a truly deceptive response. What happened to all of your PC knowledge all of a sudden?

      > Geoworks and OS/2 (and the Amiga) were pre-emptive multitasking.

      Geoworks was certainly not pre-emptive it was task sharing. This was one of the selling points it ran on low end hardware unlike the powerful multitasking systems "windows for the rest of us" kind of thing.

      > Windows 3.1, on the other hand, used co-operative multitasking, which meant any badly-written
      > application could prevent other applications from running. Windows 95 was more-or-less pre-emptive,
      > though, because the GUI is tied into the OS, there are still far too many cases where Windows 95 will not
      > let me switch tasks.

      I'm not sure I'd call Windows 98 genuinely preemptive. But in case going back even to the Windows 3.0 days "Enhanced mode" was preemptive by Windows 3.1 while "standard mode" was task sharing. I know that didn't change by 95 my wife still runs 98 I'd could write a quick app to test if it even changed by 98 but I doubt it given the types of application related crashes she still has.

      > Cross-platform compatibility does not fit well with Microsoft's lock-in strategy.

      I'd agree that where Microsoft was dominant it attempted lock-in-strategies similar to what IBM does on their mainframe or Digital did with VMS, or the Unix vendors did back in the 1980's. In all fairness I'd have to credit POSIX and GNU with trying to end lock-in but I don't think they've succeeded yet.

      > > printers (PCL),
      > > and video (VGA)?
      > > Microsoft didn't want open standards,

      > Microsoft has never had any problems with PCL.
      > Again what did Microsoft ever do to hinder VGA?

      > The point is that common interface standards were developing on their own, until Microsoft trumped the standards process. Microsoft began taking an active role in defining hardware standards for the PC.

      I still don't see what you are talking about. Microsoft has had very little impact on printer standards other than the fight against PostScript (see previous comment). As for VGA video standards were still being set by IBM with CGA, EGA, VGA, UVGA and XVGA... both before and after VGA. All Microsoft did was publish a simple interface for hardware to right drivers for their OS. It was only when people wanted both access within the GUI (I not following the "reboot to dos to play games") and also direct video writes that drivers become meaningful tied to Windows. As far as I know that was really being pushed by the gaming / video card market.

      > Microsoft has studiously resisted defining or improving standards at the points where they are simple, and > can be shared. Instead, Microsoft set the "standard" at a complex interface between to driver and the OS, > a point where, due to its complexity, hardware manufactures are unable to share. Thus, we now have a
      > situation where there are no standards, and every printer manufacturer, and every video manufacturer, has > their own unique driver.

      As for printers that's really not true. Most accept a "stdin" type access using a documented interface. Its only for reverse communication that they need OS hooks. Here we can use examples from non Microsoft since printers are used in more advanced ways by other operating systems. Take a look at the code for print symbionts in VMS I'd say they make a PC device driver look trivial comparatively. Look at the forms management hooks needed to support a printer under PFS again pretty trivial compared to Windows.

      Again the evidence shows that printer manufacturers would rather have unique features to their products which require complex OS specific interfaces then follow a standard. Printer languages are a lot like programming languages they offer different functionality and features. PCL (HP), MetaCode (Xerox), PostScript (Adobe), AFP (IBM), Epson escape sequences (Epson / Digital) existed before Microsoft had any influence and many of them existed before Microsoft (IPDS, 3211...).

      I don't know video nearly as well as print so its harder for me to be as specific. But as I mentioned above I'm not sure what reasonable standards have even been proposed that most hardware manufacturers would have agreed to.

      > Thus, today, it is not enough for an OS like Linux to support a common set of video and printer interface > standards. Now, Linux can't communicate with a hardware peripheral without having a complex driver to > deal with that hardware's unique interface. Companies like NVidia are so married to this lock-in process, > that their hardware interface is undocumented and secret.

      I'd agree. I'm just not sure how Microsoft is at fault for this. It seems like it evolved independently of them. Again I can speak more easily printers than video.

      > Microsoft has been the champion of open hardware which makes standards difficult to say the least. No one benefit more from easy unified interfaces than Microsoft, but what they have refused to do is tie into particular vendors.

      > Hahahahaha...please stop...I can't breath.

      > The reason why Linux and OS/2 have so much trouble communicating with the various printers, and video hardware, is because there are no standards. That's the way Microsoft intended it to be.

      > What Microsoft wanted, and achieved, was for each peripheral to have its own unique interface, with its own unique driver -- a driver that ties it to only Windows.

      > Of course, Microsoft's strategy backfires somewhat. The same thing that makes it hard for Linux to
      > interface with PC peripherals, also makes it hard for Windows NT and 2000. That's why the hardware
      > support has been so poor in Windows NT, because, like Linux, there is no clear set of standards for
      > Windows NT to support -- each peripheral needs its own unique driver, rewritten just for NT.

      What evidence do you have for this being Microsoft's intent rather than something that just occurred? Video standards seem much more unified today than they were 10 years ago (when IBM ruled) and every application had to ship with 3 dozen video modes for different cards. If a hardware manufacturer releases the spec its easy to write a driver just most of them consider this a trade secret.

      > > > Remember when Microsoft tried to sabotage the standards for Java and OpenGL? Remember the Halloween document where Microsoft stated their plans to "decommoditize" (i.e. destroy the openness of Internet protocols? Have you noticed that Microsoft has been carrying through on that threat?

      > > You are switching from crushing innovation to not being standards compliant. This is a different issue.

      > You don't consider it an innovation to be able to automatically download and run software in your browser, in complete safety and security?

      I don't know that Microsoft objects to that. The object to Sun controlling that process similar to their fight against PostScript as the PC standard. There is no question that Microsoft will fight any company that tries to establish control over some aspect of the PC (that is a standard not set by Microsoft).

      > You don't consider it an innovation for the entire world be able to communicate, publish, and read information, using any platform?

      They can today PDF works fine, which Microsoft opposed but didn't really do anything about since they aren't as worried about Adobe as they were 10 years ago.

      > You don't consider it to be "crushing" innovation when Microsoft pollutes those common standards, thus > sabotaging and destroying the capabilities they provide?

      No I don't. If Microsoft were to make their browser say Sun Java incompatible that would be "crushing innovation". I think Microsoft has as much right to release a different VM as Sun does. I happen to use Sun's with I.E. 6.0 and it works fine. It wouldn't if Microsoft didn't want me to be able to use Sun's VM.

      > And how many 64 bit CPUs do Microsoft's customer's use? Again Microsoft supports customer demand.

      > Haha, please, I asked you to stop with the jokes.

      > Industry has been running 64-bit servers for a long time. If they could do so more cheaply, and just as
      > well, with Windows, then they would. Microsoft tried to compete in that field, prompting articles that
      > appointed Windows NT as the Unix killer. Microsoft failed because they weren't up to the challenge.
      > Microsoft's rate of development -- their innovation if you will -- is too slow, and of too poor quality.

      I agree that Microsoft NT server has failed to gain the kind of dominance that NT workstation has. I certainly agree that NT server isn't designed for really high end hardware (and for that matter I don't think Unix is great for enterprise apps either, I think S/390 and VMS are vastly better but that's another thread). Microsoft has failed much more spectacularly in the embedded systems market. But failure is not crushing innovation its just losing.

      > > Above you go on for standards. If there is one area that Microsoft has innovated in more than any other company its creating a standard base for applications and the creation of standard applications.

      > As I have said, the truth is the opposite of your claim.

      > What standards exist have occurred despite Microsoft. Microsoft's "Embrace, Extend, Extinguish"
      > strategy has destroyed simple standards, and replaced them with hoops that everyone has to jump through > in order to run on a PC. Microsoft's "standards" are intentionally-complex interfaces, intended to tie
      > hardware manufacturers to Windows, by making it too expensive to consider supporting more than one
      > platform.

      The above referred to applications standards not hardware standards. That was the whole point. They have succeeded in absorbing the incredibly complex world of PC hardware into the OS.

      > But Microsoft has been digging their own grave. There are few left who trust Microsoft and, with the
      > growth of Linux, I expect things to change. Once the hardware manufacturers discover how much easier
      > it is to interface with Linux, they are going to start to innovate again. Actually, as I pointed out in my
      > earlier post, that process has already started.

      I'd agree that Linux offers a wonderful test bed for hardware manufacturers and it is quite likely that Linux's hardware support will be far better than Microsoft's in the near future. Again the point of this thread was about Microsoft crushing innovation.

    7. Re:While Microsoft talks, Linux innovates by Anonymous Coward · · Score: 0

      > If it hadn't been for Microsoft making DirectX, game developers would still be writing their own drivers for the dozen different soundcard types on the market.

      It's funny that the PC is the only platform where that was even a problem. The Apple, the Mac, the Commodore 64, the Amiga, the Atari ST, and so on, all had interfaces defined for sound and video, right from the start. But on the PC, the provider of the OS, Microsoft, did nothing about it for ten long years. Then just when the industry was in the process of filling that gap with a cross-platform standard, namely OpenGL, Microsoft jumped in with a standard that was tied to Windows. Amazing.

      > Or, Creative Labs would have just gotten a monopoly on the market and Sound Blaster compatibility would still be important.

      Actually, with Linux, I can interface with any sound hardware that is SoundBlaster-compatible. I thank SB for providing the standard.

      Now, can you provide the name, and a link to the document, for the Microsoft-supplied open interface standard for sound? Or is that mess called DirectX it?

      > Do you remember how much DR-DOS sucked?

      Clearly, you don't know what you are talking about. Everyone I knew at the time, who used a PC, had switched from MS-DOS to DR-DOS. Microsoft had allowed MS-DOS to stagnate for years. DR-DOS, on the other hand, introduced greatly improved memory management, and other new capabilities. But don't take my word for it. Let's see what Microsoft thought. This is from the evidence in the Caldera versus Microsoft case:

      > Bill Gates, November 29, 1989: "While DOS continues to be our most important and most profitable product over the last four years we have done very little with it technically."

      > Bill Gates, September 22, 1988: "You never sent me a response on the question of what things an app would do that would make it run with MSDOS and not run DR-DOS. Is there any version check or api they fail to have? Is ther feature they have that might get in our way? I am not looking for something they cant get around. I am looking for something their current binary fails on."

      > Phil Barrett's response to Gates: "Here follow the three "differences" (between DR and MS DOS) that Aaron has been able to find so far. Except for these differences, the two OSs behave similarly, including undocumented calls. The bottom line is that, given Aaron's current findings, an application can identify DR DOS. However, most apps usually have no business making the calls that will let them decide which DOS (MS or DR) they are running on."

      > Bill Gates, October 31, 1988: "DOS 4 is a mess to discuss -- bugs, too big, strange shell interface, who wrote it? DOS 4 has a terrible reputation."

      > Microsoft Product Support Services, June 13, 1991: "We're currently hearing from numerous callers (approx 150/day) who are experiencing severe incompatibilities with MS-DOS 5.00, to the point that PSS is unable to get the operating system to work successfully on their machines."

      So, according to Bill Gates and Microsoft, MS-DOS had been allowed to stagnate, and DR-DOS had achieved almost perfect compatibility, better, in fact, than Microsoft was able to achieve with MS-DOS 4 and 5.

      It gets worse...

      > MS-DOS product manager, Richard Freedman, March 26, 1993: "If they really release [DR-DOS 7.0] with all this junk in it, it will mean that for three ms-dos releases in a row (5, 6 and 7), DR will have had our key features in their product 12-18 months before us (kernel in HMA, compression, VxD/multitasking). given that track record, it's going to be impossible to shake this "MS as follower" image. it's been very difficult so far as it is."

      So, given that Microsoft could not keep up with DR-DOS technically, how did Microsoft manage to defeat DR-DOS?

      Microsoft added a warning about DR-DOS in Windows (which Microsoft knew to be a lie), spread FUD about DR-DOS in the media, had OEMs sign licenses for Windows which forbade them to pre-install DR-DOS (which got MS in trouble with the DOJ), and, when DR-DOS still wouldn't die, added secret calls into Windows 95 to make it refuse to run on DR-DOS. For example, regarding the Windows warning message:

      Microsoft's Brad Silverberg, February 10, 1992: "What the guy is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is dr-dos and then go out to buy ms-dos. or decide not to take the risk for all the other machines he has to buy for in the office."

      But let's get back to your post...

      > Every modern OS has had built in virtual memory. Microsoft building it in was them following CS theory.

      Wrong. Mainframes have hardware assists for virtual memory. They don't waste the CPU's time transferring bytes in and out of real memory.

      And it is just such a hardware assist that was built into the more expensive memory cards at the start of the nineties. Everyone who knew enough about it, knew that the new memory standard, which expanded on those hardware concepts, was taking the PC into the realm of mainframes. Microsoft also knew how good it was, when they destroyed it.

      > > Do you remember when the 386 came out, with its new memory protection capabilties?

      > And do you realize that people are STILL bitching and moaning about Windows XP not running their DOS programs? Don't blame Microsoft, blame backwards compatibility.

      Oh, please. Everyone else (e.g. OS/2, Linux) seems to be able to run DOS software without giving up on 386 memory protection. All you are telling me is that Microsoft is too incompetent to do it. In fact, look back to the earlier quotes, where DR-DOS was able to achieve near-perfect backward compatibility with MS-DOS, while Microsoft could not.

      > Windows 2000 uses TCP/IP for LANs, and supports Kerberos security.

      And Microsoft has added proprietary extensions to Kerberos, won't publist all the specs, and won't even let people publish the specs that have been released:

      http://dir.salon.com/tech/log/2000/05/11/slashdot_ censor/index.html

      > As for the VGA bit, you're joking, right? (S)VGA is an anachronism that doesn't support linear memory, high-res/high-bandwidth modes, and most importantly, acceleration.

      Nice try. Now let's talk about the point I actually made.

      (S)VGA was a standard. And you're right, it's out-of date. But that's exactly the point. If (S)VGA is out-of-date, then why isn't there a new standard to replace it? The answer is because Microsoft has sabotaged the standards process.

      Now, in place of video standards, we have unique, complex drivers for each video card. These drivers are tied so closely to the OS, that they even have to be rewritten to go from one version of Windows to the next. And for some versions of Windows, such as NT, a lot of drivers don't even get ported.

      > And have you noticed that OpenGL is more important than ever?

      So Microsoft only succeeded in slowing down the spread of OpenGL. It doesn't change the fact that they tried to kill it. Of course, Microsoft hasn't given up yet, as demonstrated by Microsoft's claim that their recently-purchased SGI patents gives them control over parts of OpenGL.

      > And Java never really took off client-side anyway?

      Oh, nonsense. Client-side Java was taking off big time. Companies from all over the industry were announcing plans to use it. Then Microsoft did this:

      > The "strategic objective" is to "kill cross-platform Java by grow[ing] the polluted Java market." http://java.sun.com/lawsuit/051498.unfair.html

      Microsoft also took other steps to ensure that web developers couldn't count on there being a working JVM in the browser. Through contract interference, and other illegal means, Microsoft worked to "cut off Netscape's air supply," which stopped further development on the Netscape JVM.

      But, just as with OpenGL, Microsoft has only succeeded in slowing Java down. Along with Mozilla, client-side Java is finding new life, and may yet become the standard for e-commerce (five years later than would have been the case without Microsoft's interference).

      > Yes, Linux runs on platforms nobody buys.

      You mean like Intel-based PCs, 64-bit PCs (already being used, with Linux, in supercomputer clusters), IBM mainframes, Macintoshes, Sun boxes, HP boxes, Tivos, IBM RS6000s, and so on? Those sorts of "platforms that nobody buys?"

      > Windows just runs on platforms people actually purchase. You can't blame them for being in a different business.

      Haha. You're funny guy. The fact is that Microsoft tried to make the move to 64-bit servers, and they failed! They failed miserably! They failed because they weren't good enough!

      > I fail to see how Microsoft hurt [hardware innovation]

      - If Microsoft hadn't taken steps to prevent it, we would now be running PCs with mainframe-style hardware-assisted virtual memory.

      - If Microsoft had made even a small attempt at defining a standard interface, video on Windows might have caught up to the Amiga ten years sooner. As it stands, we still don't have a proper standard.

      - If Windows had been able to support the new capabilities of the 386, Intel could have been selling it years sooner.

      - If Microsoft had been able to provide a stable-enough OS, then Intel and PC manufacturers could have been selling server hardware to compete with the Unix vendors.

      - And if anyone really believed that Windows was 64-bit ready, then Intel and PC manufacturers could be selling 64-bit servers (in fact, they are selling 64-bit servers, but running Linux).

    8. Re:While Microsoft talks, Linux innovates by be-fan · · Score: 2

      Then just when the industry was in the process of filling that gap with a cross-platform standard, namely OpenGL, Microsoft jumped in with a standard that was tied to Windows. Amazing.
      >>>>
      You don't seem to understand. Hardware that is constrained to a single register standard cannot evolve as well as hardware where the standardization lies at a higher level. You seem to pine for the days of VGA when a few simple register tricks would work on all chips. Well, in this day of vertex shaders and multi-sample anti-aliasing, a single HW level standard is far too constraining. Hell, even something high-level like DirectX (which is more than just Direct3D!) is getting constraining.

      Actually, with Linux, I can interface with any sound hardware that is SoundBlaster-compatible. I thank SB for providing the standard.
      >>>>>>>
      Wow. Boy do you live in the 80's. SB Compatibility is dead. Everyone and their mother has moved on to compatibility at the API level. HW manufacturers like it. End-users like it. Game developers like it. You can't seem to grok it.

      > Do you remember how much DR-DOS sucked?
      Point taken. I meant in comparison to modern OSs (like UNIX), not DOS itself.

      Wrong. Mainframes have hardware assists for virtual memory. They don't waste the CPU's time transferring bytes in and out of real memory.
      >>>>>>>
      Mainframes are also really anachronistic. They get the job done, but at the cost of a ton of hardware that could be better spent on more modern designs. Are you claiming that every single modern OS (Linux, Solaris, IRIX, etc) and every single modern CPU (MIPS, SPARC, Alpha) all of which use the traditional kernel-controlled on-CPU MMU virtual memory design somehow missed to boat when they didn't catch on to DOS EMS cards?

      Oh, please. Everyone else (e.g. OS/2, Linux) seems to be able to run DOS software without giving up on 386 memory protection.
      >>>>>>>
      Not like Win95 can. Try running programs that directly access certain hardware under Linux, and it *will* get killed. There is just no way around it. Win95 leaves that hardware open, so moldy old DOS programs still work.

      All you are telling me is that Microsoft is too incompetent to do it. In fact, look back to the earlier quotes, where DR-DOS was able to achieve near-perfect backward compatibility with MS-DOS, while Microsoft could not.
      >>>>>>>>
      And DR-DOS was a fully preemptive, multithreaded, 32-bit, protected mode OS?

      (S)VGA was a standard. And you're right, it's out-of date. But that's exactly the point. If (S)VGA is out-of-date, then why isn't there a new standard to replace it? The answer is because Microsoft has sabotaged the standards process.
      >>>>>
      The answer is because hardware vendors realized that grand-unified hardware standards had gone the way of the dinosaur. Newer chips were reaching the complexity of CPUs, and simply could not adhere to one register standard. Try reading a modern graphics card register-spec sometime (I suggest Matrox's, they're free online). Now tell me that these interfaces (which are several generations out of date with current HW mind you) would not be held back if they had to conform to something like a new VGA.

      Now, in place of video standards, we have unique, complex drivers for each video card. These drivers are tied so closely to the OS, that they even have to be rewritten to go from one version of Windows to the next. And for some versions of Windows, such as NT, a lot of drivers don't even get ported.
      >>>>>>>>.
      These drivers don't have to be tied closely with the OS. Take a look at NVIDIA's kernel driver wrapper code. It's quite OS independent. A graphics driver needs only a few basic functions (allocating memory, managing interrupts, etc) and has no need to interface to complex internal OS structures. What is needed is not a hardware standard, but something like XFree86's binary module mechanism. It specifies an abstraction layer for graphics drivers. Any OS that supports this abstraction layer can theoretically load XFree86 drivers, even in binary form.

      So Microsoft only succeeded in slowing down the spread of OpenGL. It doesn't change the fact that they tried to kill it. Of course, Microsoft hasn't given up yet, as demonstrated by Microsoft's claim that their recently-purchased SGI patents gives them control over parts of OpenGL.
      >>>>
      They're on the ARB, they have control anyway. To tell the truth, the ARB did more than anyone to hurt OpenGL. They stagnated it for so long that it really started looking pitiful next to Direct3D. Thank god 3DLabs had the balls to come forward with OpenGL 2.0

      > Yes, Linux runs on platforms nobody buys.

      You mean like Intel-based PCs, 64-bit PCs (already being used, with Linux, in supercomputer clusters), IBM mainframes, Macintoshes, Sun boxes, HP boxes, Tivos, IBM RS6000s, and so on? Those sorts of "platforms that nobody buys?"
      >>>>>>>>>
      Yes, compared to the millions upon millions of Windows-based PCs. Microsoft (until only recently) wasn't in that business. Who cares if their products weren't suited for it?

      Haha. You're funny guy. The fact is that Microsoft tried to make the move to 64-bit servers, and they failed! They failed miserably! They failed because they weren't good enough!
      >>>>>>>
      I highly doubt Microsoft lacks the technical skill to make a 64-bit OS. The Alpha, PPC, and MIPS ports of Windows were never really intended to be blockbuster products. I'm sure they had some plans to target that market, but it was more to show off the cool new design of Windows NT (back when portability, along with object orientation and microkernels, and multiple OS personalities was all the rage).

      - If Microsoft hadn't taken steps to prevent it, we would now be running PCs with mainframe-style hardware-assisted virtual memory.
      >>>>>>>
      Clarify this. As far as I can see, the virtual memory layout on my PC is (a) hardware assisted (the CPU takes care of reading the page tables for me) and (b) is the same style of virtual memory as in 64-proc Sun and SGI boxes. Now, if you're talking about multiple-OS images running in fixed partitions of memory, maybe you are right, but to beg the question, how useful is that? My current machine (1.5GHz Athlon XP) barely has enough horsepower to run Linux/KDE-3, much less both Linux and WinXP simultainiously. Plus, if its such a useful feature, why doesn't Sun or SGI have it?

      - If Windows had been able to support the new capabilities of the 386, Intel could have been selling it years sooner.
      >>>>>>>>
      If people hadn't bitched about backwards compatibility, Windows 95, Windows 98, Windows 98 SE, and Windows ME wouldn't have been necessary!

      - If Microsoft had been able to provide a stable-enough OS, then Intel and PC manufacturers could have been selling server hardware to compete with the Unix vendors.
      >>>>>
      Until recently (hell, even now) PC hardware is not enough to compete with real UNIX machines. MS provided a super-stable OS with NT 3.x. Why didn't PCs take the server market by storm? Cuz they weren't ready!

      --
      A deep unwavering belief is a sure sign you're missing something...
  36. No, it doesn't make it number 2 by Johannes · · Score: 1

    Linux has had support much longer than the article implies. Here's one post which is significantly before.

    In fact, this isn't the first since it mentions the USB 2.0 support that was in the 2.4 -ac kernel. It only mentions a patch for Linus' 2.4 kernel tree.

  37. For the wondering ones.... by unixmaster · · Score: 2, Informative

    You can read linux-usb news and reach linux-usb team at http://www.linux-usb.org

    --
    Never learn by your mistakes, if you do you may never dare to try again
  38. OH MY FUCKING GOD by Anonymous Coward · · Score: 0

    Oh, and here we have somthing supported for Windows and MAC for some time and GREAT! Linux is finally 'rounding the bend. Whoopee.

  39. Not Apple, Orange Micro by willy_me · · Score: 2

    Apple doesn't support USB 2.0 - as many other people have pointed out, Orange Micro (www.orangemicro.com) offers PCI cards and drivers for OSX.

    Having said that, one has to commend Apple for the architecture inside OSX. A third company wouldn't have been able to create drivers that quickly if OSX never had good plumming. I guess since it started getting designed around 98, they could see USB / Firewire becoming the standard for external IO and designed the OS to allow for easy integration of such devices. I once read the docs about the OSX driver architecture and was impressed - many well thought out layers of abstraction - but that was a long time ago.

  40. Re:I don't get it - it's not that hard, actually by Frodo420024 · · Score: 1
    Easy:
    You get a more open standard, compatibility with USB 1 devices, and significantly lower cost.

    USB2 will be integrated on all motherboards very soon, Firewire will remain an add-on option. USB will be king of the landscape, Firewire will live on like SCSI.

    --
    I'm in a Unix state of mind.
  41. Seriously? by Eric_Cartman_South_P · · Score: 1

    Very thoughtfull post, but when you say "Linux can no longer live of the legacy of its stability." I must disagree. That's the NUMBER ONE REASON why I run it for all my important stuff. Uptime, baby. If WinXP could stay up for a few months without swiss-cheese hole security, I'd run it. Stbility is king, and that is why Linux has entered the enterprise first, not the desktop. Enterprise wants stability, and Linux blows away Win2KSP2 in this regard (and many others as well). Just my 2 cents.

    1. Re:Seriously? by Anonymous Coward · · Score: 0

      LMAO! Another elitist fool in the OSS community. This is HILARIOUS! Get your facts straight, Windows 2000 has run for almost a year and a half on this box without freezing and the security is bullet proof. I go to all sorts of lame script kiddie channels on DAL and post my IP address. So far, no problems. This is with IIS, all patched; also. Don't give me your Linux-is-be-all-end-all-due-to-stability bullshit, please and thank you!

    2. Re:Seriously? by Anonymous Coward · · Score: 0
      I go to all sorts of lame script kiddie channels on DAL and post my IP address.

      Post it up, d00d.

      ~~~

    3. Re:Seriously? by foobar104 · · Score: 1, Troll

      Stbility is king, and that is why Linux has entered the enterprise first, not the desktop.

      Um... actually, Linux is used on servers more than on desktops because the Linux desktop experience is like having your fingernails pulled out. It's unbelievably awful. I don't like Windows at all, but I'd rather use Windows than Linux on my desktop. At least I can accomplish things with Windows.

    4. Re:Seriously? by Anonymous Coward · · Score: 0

      Um... actually, Linux is used on servers more than on desktops because the Linux desktop experience is like having your fingernails pulled out. It's unbelievably awful. I don't like Windows at all, but I'd rather use Windows than Linux on my desktop. At least I can accomplish things with Windows.

      Amen to that. Simple things like not having to press ^Shift+Alt+middle-click to do simple copy and paste operations go a long way in making a UI useful, or at least make it a consistant ^Shift+Alt+middle-click for every application if you don't believe in the well-established Shift+Insert...

  42. Re:I don't get it - it's not that hard, actually by Anonymous Coward · · Score: 0

    USB is an open standard? It's controlled by USB-IF which is very heavy with Intel people who created it. Only IEEE 1394 (FireWire) is an open standard.

  43. Re:What's this about Virtual LAN cards through USB by whovian · · Score: 2

    Would a LAN connected by USB2 be less expensive than gigabit ethernet (using a switch with all gigE ports)? Seeing as gigE switches are still relatively expensive, going USB2 might be a way to cut costs. However, my guess is that gigE latency would still be lower.

    --
    To-do List: Receive telemarketing call during a tornado warning. Check.
  44. Second Best by Anonymous Coward · · Score: 0

    is first loser. Being one year behind MS means you are one year behind the lamest OS company in the world. Is that something to be proud of? Stupid people only recognize accomplishmenst in light of what MS has done. Give it a rest.

  45. USB was designed not to be expandable by Anonymous Coward · · Score: 1, Interesting

    Look at the original spec. It specifically mentioned that it is designed never to go faster than 12mbs, because there are more appropriate interfaces for higher speeds (Firewire). Apparently Intel changed their minds.

    Firewire isn't actually slower anyway, due to inefficiencies in the USB 2.0 design, the throughput of USB 2.0 is approximately the same as Firewire and is usually significantly slower in practice.

    Finally, the new Firewire is protocol compatible with the old Firewire, they can exist on the same wire. In this way it is better than USB 2.0's compatibility. On the otherhand, Firewire 800/1600 require a whole new connector and so in my book actually has less real-world compatibility with previous standards than USB 2.0, or the same at best.

  46. Hardly the second best... by vorpal22 · · Score: 1

    I have a USB switchbox which shares USB Macally keyboard and my MS IntelliTrackball between my PowerMac G4 and my P3 550.

    Now, I've had no problems getting the peripherals to be properly recognized when switched over in the following operating systems: Windows 98, Windows ME, Windows 2000, Windows XP, Mac OS 9, Mac OS X, QNX RTOS, BeOS, and Solaris 8.

    However, Linux USB support is still entirely flaky. I've tried multiple Linux distros (Red Hat, SuSe, Mandrake, Slack), and about half the time, the peripherals are recognized when I switch them from my Mac to my P3. About half the time they're unrecognized, and then, at that point, no matter what I do, they will not be recognized until I perform a hard-reset.

    If even BeOS could handle this properly, I hardly see why Linux can't. I don't think my configuration is entirely unusual. Until this simple problem is dealt with, Linux will not be my idea of an advanced operating system.

  47. Actually, that's misleading as well by Johannes · · Score: 1

    The vast majority of changes for USB 2.0 were at a level below what the USB device drivers care about. As a result, most USB 2.0 devices will work with the old USB driver developed against USB 1.1 devices.

    Take for instance Mass Storage devices. The Linux USB 2.0 support was developed against a USB 2.0 Mass Storage device. 95% of the development was the EHCI host controll driver. 4% was in the core (to support some new USB 2.0 features) and 1% was in the Mass Storage driver.

    There are some new features that USB 2.0 introduced, but there aren't many and are well worth the additions.

  48. Are you kidding? by fmaxwell · · Score: 2

    USB is good for keyboards and mice... that's about all.

    USB 2.0 is faster than Firewire at 480mbps (vs. 400mbps for Firewire). Who needs 480mbps for a mouse? I put a 24X Yamaha cutter into a USB 2.0 enclosure and can burn CDs at the full 24X speed, so I'd say that it's good for external CD drives, too. It's also good for flatbed scanners, digital cameras, tape drives, printers, USB-to-Ethernet adapters, and just about any external peripheral which would benefit from a high speed, low cost, hot plug interface. That describes a lot of peripherals.

    MS is the only player in the field.

    Hardly. As this article states, Linux supports it and, as another poster pointed out, so does NetBSD.

    Another reason to support it is that it will soon be standard on every PC motherboard sold while getting Firewire ports will usually require the addition of a PCI card.

    Lastly, it uses inexpensive cables and is backwards compatible with USB 1.1 devices and cabling. If I have a USB hub on my desk, USB ports on the front of my computer, and a USB mouse, barcode scanner, and flatbed scanner, why would I want to start buying an incompatible Firewire peripherals? It already looks like there is a bald eagle nesting behind my computer, so I don't need yet another set of cables for Firewire.

    1. Re:Are you kidding? by capnjack41 · · Score: 1
      On the other hand...

      Though the majority of hardware supports USB (1 or 2) over firewire, some types of equipment went with IEEE early on and stuck with it, such as digital video cameras and tape decks. 400Mbps was enough to send high-quality NTSC video.

      Now we have USB2, which is slightly faster, but there's such a large base of IEEE video equipment, and so they may just stick with it instead of changing over all their hardware (DV cameras, capture cards, tape decks, etc.) to USB; IEEE's still good enough, and it's just not worth it for them to switch everything over.

    2. Re:Are you kidding? by fmaxwell · · Score: 3, Insightful

      Now we have USB2, which is slightly faster, but there's such a large base of IEEE video equipment

      I fully understand that. I deal with cards that have 1553 interfaces, GPIB interfaces, etc. in my work because we have equipment that needs those interfaces. But to claim that Linux should focus on the more specialized Firewire interface over the soon-to-be-ubiquitous USB 2.0 is almost as silly as claiming that USB is only good for mice and keyboards.

    3. Re:Are you kidding? by Anonymous Coward · · Score: 0

      USB 2.0 is faster than Firewire at 480mbps (vs. 400mbps for Firewire).

      Its faster in name only. Especially with as many devices as you have, as USB is a dumb bus and needs to be powered by the CPU, whereas Firewire is host independant.

    4. Re:Are you kidding? by fmaxwell · · Score: 2

      Its faster in name only. Especially with as many devices as you have, as USB is a dumb bus and needs to be powered by the CPU, whereas Firewire is host independant.

      I'll worry about that if I ever find myself simultaneously scanning images, burning CD-ROMS, scanning barcodes with the wand held in my teeth, and frantically typing with one hand while moving the trackball with the other. As to how involved the CPU is with the bus, I can't say. I seriously doubt that the Firewire bus has a direct connection to the computer's hard drive with no CPU intervention. All interfaces, whether USB, Ethernet, IDE, Firewire, or SCSI, impose some level of CPU loading.

      I would like to know why you believe that a modern Athlon XP or P4 would have trouble keeping up with the data transfer on USB 2.0.

      Dumb buses are becoming more prevalent as CPU horsepower gets cheaper. Not too many years ago, Hayes introduced a high-spped serial card that had 1K buffers and enough smarts to do the handshaking so that a normal PC could handle high-speed serial data at 230 kilobaud. In a modern system, such a card would be laughable.

    5. Re:Are you kidding? by Anonymous Coward · · Score: 0

      Digital video is a good example where dumb buses are bad. I often import video while doing other tasks such as applying a filter.

    6. Re:Are you kidding? by fmaxwell · · Score: 2

      Digital video is a good example where dumb buses are bad. I often import video while doing other tasks such as applying a filter.

      So do you not have enough CPU power to handle both simultaneously, or are you simply assuming that you would not? If you really do not (which I find hard to believe given the speed of modern CPUs), there will be a market for intelligent USB 2.0 controllers much as there is for intelligent drive controllers that have their own CPU, cache, etc. (You will note that, as CPU speeds have increased, the need for such cards has diminished.)

      Simply saying "dumb buses are bad" is dumb. Without considering the CPU speed, availability, and loading from the "dumb bus" at its rated speed, such a statement is meaningless.

      By the way, I programmed a "dumb" interface. It was a serial port that worked by toggling an I/O line connected to a 2N2222A transistor to create the bits. There was another bit that got read for the incoming data. Not even a UART. That was a "dumb" interface and I hardly think that's comparable to a modern USB 2.0 as interface as implemented in silicon today.

    7. Re:Are you kidding? by entrigant · · Score: 1

      Why settle for second best when you can have it all? Just because the cpu can handle it doesn't mean it must. In fact I'd rather it handle as little as possible. Give me sound cards with hardware mixing and 3d channels. Give me 2d/3d accelerated video cards. Give me hardware video/audio encoders/decoders. Give me a raid 5 card with onboard cpu and ram. Give me an ethernet card with it's own tcp/ip stack.

      Don't get me wrong I'm all for usb2... but I also think firewire is also cool. The better planned/newer motherboards and controller cards have both firewire and usb2 support. USB 2 is more of a "here's a chunk of bandwidth.. you guys can fight over it." Where is firewire is much more complex... there's a reason video equipment uses it... it's designed to provide gaurenteed bandwidth to the best of its ability.

      There's no reason to fight over thw two.. variety is the spice of life, and they are both rather different.

    8. Re:Are you kidding? by kasperd · · Score: 1

      Simply saying "dumb buses are bad" is dumb. Without considering the CPU speed, availability, and loading from the "dumb bus" at its rated speed, such a statement is meaningless.

      It is not that simple. You cannot say a piece of equipment is simply dumb or intelligent. There are variations from the very dumb through the little dumb and little intelligent up to the very intelligent equipment.

      In some cases a little dumb equipment is no problem to a fast CPU. But equipment can be so dumb that speeding up the CPU is no help at all.

      If communicating with the equipment requires the CPU to do busywaiting a fast CPU doesn't help. Maybe a fast CPU can poll the device 100 million times in a second where a slow CPU can only poll the device 10 million times in a second. But that doesn't make the device respond faster. So no matter how fast you poll, you are still wasting all your precious CPU time, a faster CPU will just increase the waste.

      Maybe hyperthreading can be a little help here, but you would still be wasting resources. And requiring so much from the CPU just to support very dumb equipment is not a good idea.

      So in fact a device can be so dumb that it is without doubt bad. I don't know if USB is this dumb, but I do know that a parallel port with an interlink cable is.

      --

      Do you care about the security of your wireless mouse?
    9. Re:Are you kidding? by Anonymous Coward · · Score: 0

      A USB 1.1 Steering wheel of Microsoft (;-)) takes a 30% impact in performance on this athlon 500 MHz machine with IDE disk and 256 MB of RAM playing Grand Prix 3 of Microprose.

      30% more than using a keyboard that is. Of course the steering wheel takes some and the game has more work still the overhead of USB could well be around 10-15%.

    10. Re:Are you kidding? by fmaxwell · · Score: 2

      In fact I'd rather it handle as little as possible. Give me sound cards with hardware mixing and 3d channels. Give me 2d/3d accelerated video cards. Give me hardware video/ audio encoders/decoders. Give me a raid 5 card with onboard cpu and ram. Give me an ethernet card with it's own tcp/ip stack.

      And give you liquid nitrogen to cool all of the CPUs in your system. Some of what you say makes great sense (3D accelerated audio and video), but things like RAID cards with their own CPUs and RAM, and Ethernet cards with their own TCP stacks, just drive up the cost of PCs for little gain. For example, RAID cards with their own cacheing do not often make sense. Money is better spent on more RAM for the computer which can be utilized by the OS for cache. It's a lot faster to get cached data out of local RAM than it is to get it across a PCI bus. TCP/IP stacks built into Ethernet cards limit what the system can do from a firewalling perspective.

      Where is firewire is much more complex... there's a reason video equipment uses it...

      The reason is that the vendors had no other choice at the time. USB 1.1 was only capable of 12mbps, so that was clearly not an alternative.

      I don't have some kind of hatred of Firewire and I would like to see it become something like a hard drive interface to replace SCSI, but USB 2.0 support in Linux is very valuable while Firewire is less so. I have noticed no small number of Firewire peripherals being closed out while USB 2.0 products are becoming more popular.

  49. Long Device Rant. by twitter · · Score: 4, Informative
    I hate USB. Born in 1993, USB I was about as fast and universal as the parallel port. While I can see my devices on USB I, I have no idea how to talk to them. I have all the respect in the world for people who heroically struggle to build interfaces to talk to old scanners, cameras and what not, in the face of OEM indifference and hostility. I'm afraid that USB II and the far superior IEEE 1394 (400 mbps currenet 800 mbps planned, can have multiple pc hosts, backported to 2.2 kernels already). might suffer the same fate. Someone tell me it's not so.

    So nice of M$ to draw attention to the mechanism that it keeps splintered. The article phrases the situation as a model for Linux device compatiblity as if there were no other options and Linux development will alsways be broken and lagging. This is true, if you are talking about chasing M$'s broken tail. CSS has demonstrated that any device can be made impossible to talk to, regardless of technical skill.

    My experience with M$ USB has been less than advertised. Windows 2000 has managed to make USB I not hot pluggable, and it manages to screw up one of my camera's flash card formating everytime I plug it in at work! At home, I tried to print out five plain text pages to a USB printer from win98. I got four pages, five error messages for lack of communications and one last message about "unknown system errors" requiring a reboot. Sometimes it works, sometimes it don't. That's what happens when you screw around with "standards" too much.

    On the other hand, pcmcia with a compact flash adaptor has worked very well. Compact flash registers itself as a new hard drive, /dev/hde in most cases, and this shows up in /var/log/messages when you plug it in. So long as your camera stores pictures unscrambled, you can get them without any silly interface software or device driver. Mount and coppy. Cannon S110 works great, Sipix has broken pictures. Yeah, pcmcia only goes 64 mbps, sigh. Too bad someone out there wants to make sure that:
    1. You must use a propriatory driver to talk to your devices. This will enable DRM of the pictures you take - eventually you will have to pay per play to view or print your own pictures. That's progress!
    2. That driver will not work forever and you will have to replace your device. Bitrot! more progress. My place of work is filled with old devices that stoped working due to "software upgrades". The vendors recomend, shocker, that we replace the devices.

    M$ will never support a "universal" device.

    --

    Friends don't help friends install M$ junk.

    1. Re:Long Device Rant. by foobar104 · · Score: 2

      It sounds like you don't hate USB so much as you hate USB on Windows.

      I use OS X. I a digital camera (a Nikon), and I upload the pictures to my Mac with a USB cable and iPhoto. No drivers required.

      I have a USB scanner and a USB printer, and with both of them the story is the same: just plug them in.

      There's nothing fundamentally wrong with USB. It sounds, from what you said, that you've ust had really bad experiences because you chose the wrong OS.

    2. Re:Long Device Rant. by SN74S181 · · Score: 1

      My place of work is filled with old devices that stoped working due to "software upgrades". The vendors recomend, shocker, that we replace the devices.

      I have a nice brand-name STB PCI graphics card. It has an S3 Trio64 chipset. It's deprecated in XFree86. I used to use it, back in the Linux 1.2 days as my main graphic card. About a year ago I got hollered at in a forum for complaining about it. People told me 'get a new card!'

    3. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      How about get a new card if you want XFree86 4.x support. Otherwise you can keep using 3.x. Why is this a problem? Is there some reason you want new X with old graphics card? The only real advantage in 4.x is the better 3d and AGP support, neither of which will do you any good. If you're feeling especially hackerly, you can always do the port yourself, since you have the source code.

    4. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      If the drivers exist in 3.x, why cannot just keep them in 4.x? Is it really going to be a problem to keep them? Is it going to affect the huge size of X significantly? Was there a reason to drop old driver other than they wanted to? It would be like dropping 386 support from linux...what is the point?

      Did windows 9x drop support for vanilla VGA or the plethora of older graphics cards? Sure, there is a point of no return beyond which some cards will not be supported, but 4.x seems to be a bit extreme in its handling of this.

    5. Re:Long Device Rant. by SN74S181 · · Score: 1

      How about get a new card if you want XFree86 4.x support.

      In my previous comment I was only using XFree86 as an example. My point is made.

    6. Re:Long Device Rant. by CounterZer0 · · Score: 0, Flamebait

      You sir, a total reject. I've been using USB printers, flash card readers for my digi cam, usb speakers..for years. In win2K, it's been nothing but flawless.
      Just because your ineptitude with Windows prevents you from using something 'like you think it should work' doesnt mean Microsoft won't support a 'universal' device. What about PCI? What about SCSI? Doesn't MS support those? Can't those hold anything?

    7. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      Nah, that's not rant, that's FUD.
      Not olnly they will take rights for your pictures, they will also drink beer in yer fridge and rape yer dog.
      MS does support plenty of universal devices (ide, scsi, usb mass torage device). They did not came up with "generic camera" support, that's too bad, but they don't owe you to do everythng, right?
      USB is working perfectly with me. I guess your problem is that you hate your machine and your machine hates you in exchange.

    8. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      >> There's nothing fundamentally wrong with USB.

      Yes, there is. There is no support for connecting a USB device to more than one host machine. With Firewire, you can have (for example) video streaming from the same camera to two different hosts.

    9. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      They didn't "drop" the driver. Porting video drivers to the new 4.x architecture is a massive effort, and the most popular chips/cards come first. The XF86 project doesn't exactly have the resources of MS who can afford to port the entire range of software drivers forward for each release.

      XF86 3.x isn't "deprecated" -- it is perfectly fine to use if you don't require 3D support or the new input layer. It is also much smaller and faster.

    10. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      WTF? This is "informative," "insightful," and most laughable "interesting?" It's just a "my computer doesn't work and it's all M$'s fault."

      Get a fucking life, people.

    11. Re:Long Device Rant. by mrbrown1602 · · Score: 1

      I'd say there's something wrong with your USB setup (controller, hubs, etc.) rather than Windows. I've had nothing but flawless experiences with USB and M$ Windows - even during the various M$ OS betas I've been on.

    12. Re:Long Device Rant. by quinto2000 · · Score: 1
      THink of it as Windows XP dropping support for older hardware. It comes from the fact that Xfree 4 has a completely new driver design. Each driver can't just remain, it needs to be rewritten for the newer X. It just isn't worth the effort in many cases, but AFAIK many of these older cards are being slowly added back into the supported category. They should certainly not be top priority.

      And the new driver design in X 4, which is modular, was certainly worth breaking backwards compatibility.

      --
      Ceci n'est pas un post
    13. Re:Long Device Rant. by Anonymous Coward · · Score: 0

      OH COME ON.

      Get a new card you cheapskate.

  50. Bzzt! by Anonymous Coward · · Score: 0

    Not quite fucktard, the royalties are something on the order of 25 cents per system, and that gets split up amongst the 1394 consortium (Apple, Sony, Compaq) and does not go straight to Cupertino.

    Even on a $50 motherboard, the royalties would amount to half a percent of the cost. Go do the world a favor and get a vasectomy before you have any children.

  51. USB 2.0 support has been around for a lot longer by compwiz · · Score: 2, Informative

    Leave it to MSNBC and CNET to print totally uneducated articles about something they have no basis for.
    From linux-usb.org:
    People have been using USB 2.0 with usb-storage devices from Linux hosts since June 2001, but it was only in early winter of that year (a short while before Linus created the 2.5 development branch) that other USB 2.0 devices (notably, hubs) began to be available. So while some changes for USB 2.0 were rolling into 2.4 kernels through the year 2001, most of the tricky stuff (the ehci-hcd driver) was separate until the 2.5 kernel branched. Recently, some Linux distributions have begun to include this support.

  52. nice try lair by Anonymous Coward · · Score: 0

    You have to reboot after you install an MS security patch, and new holes in IIS are found often enough to make claims of running a patched server for a year and a half without rebooting a pathetic lie.

  53. Idiots - yes, you too. by Anonymous Coward · · Score: 0

    Someone sets the agenda and we all dance to it? Linux supports and has supported all widely used "standards." It will survive even if it doesn't support USB 2.0, but it is common sense to support it. Some peabrained reporter idiot thinks it is "critical" and this is "news"?

  54. Shame on whoever modded me down. by Mustang+Matt · · Score: 2

    That post wasn't flamebait. I was commending a company for having employees that were doing the right thing. Give me a break.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  55. Not really by ToasterTester · · Score: 1

    Isn't the idea behind Open Source is with "100's of thousands of developers" you can stay on top new technologies unlike commericial software with smaller development teams. No this isn't a troll message, I'm saying think before you open your mouth. You had a positive message in support was now available, but you dimisnished it with your, only took a year longer we're #2 rubbish.

  56. some articles about Linux USB: imply non-existance by Locutus · · Score: 2

    I recently read an article about this on C/Net (IIRC) and it really read more like this:

    Hey, Linux will soon have USB 2.0 support and with all the vendors/devices supporting USB, it's a good thing Linux is eventually getting USB support.

    The average Joe is going to think you can't use your USB devices with Linux.

    So watch out when you read those articles because there can sometimes tell another story. The number one marketing company in the world isn't always doing in-your-face marketing. Actually, they very seldom do it that way. In that way, they are very unlike the Borg who are so arrogant and powerful they just keep coming( in the clear ) directly at their prey.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  57. Bill Gates is your savior by Anonymous Coward · · Score: 0, Troll

    I'm sorry to break this to you, but Linux sucks and is illegal. Now Windows XP, thats a REAL OS not like the FAKE LINUX OPERATING SYSTEM. Buy it or die plz.

  58. Pfft about time by Anonymous Coward · · Score: 0

    Linux sucks and slashdot will be soooooon dead bahahahah

  59. Nope. by supabeast! · · Score: 4, Insightful

    "Does that make us the second most powerful now? :)"

    No, it just validates Microsoft's FUD that Linux is a bad choice for a desktop OS because of poor hardware support.

  60. MOD PARENT UP! by Anonymous Coward · · Score: 0

    It's so true! I work for Microsoft so I should know!

  61. Not a year behind Win98SE... by Krokus · · Score: 1

    Never mind USB. Despite years of patches, fixes, and upgrades, I *still* have to tell Win98 that I'd like to remove a PCMCIA device, so it can then *allow* me to remove it.

    1. Re:Not a year behind Win98SE... by Magic5Ball · · Score: 1

      I *still* have to tell Win98 that I'd like to remove a PCMCIA device, so it can then *allow* me to remove it.

      To allow cached transactions to complete, close interfaces and make voltage conditions safe.

      Unless you want broken files, programs halting for lack of data and device damage.

      --
      There are 1.1... kinds of people.
    2. Re:Not a year behind Win98SE... by Brian_at_Work · · Score: 1

      And after all theese years I still have to tell all my *nix boxen that I want to unmount /dev/cdrom just to get my drive open :-) someday maybee they will get their act together.

    3. Re:Not a year behind Win98SE... by Anonymous Coward · · Score: 0


      So, you're not a year behind a 3yr old OS?

  62. Yes, but does MS support USB1.1? :-) by fidros · · Score: 2, Interesting

    True story, happend today - a friend of mind got a USB connected digital camera. He took some pictures and needed to send them pronto to be included in some newspapaer story (long story...).

    He plugs it in, XP crashes. Every time the camera goes in XP goes out the Windows...

    Friend remembers me saying that I think Linux can handles this easily and gives me a phone call. I'm away from my desk so friend decides to try on his own: He boots Linux, camera gets detected automatically, friend grabs photos easily and send newspaper.

    When I called him there was nothing for me to do but say: "So, Linux saved the day once again :-)"

    Gilad.

    --
    Gilad.
    1. Re:Yes, but does MS support USB1.1? :-) by Anonymous Coward · · Score: 0

      Y'know what - Windows 2000 has been doing that to me recently as well. It just spontaneously resets the computer. Plug in camera using USB -> suddenly I'm staring at the BIOS checks, not even a blue screen of death. (I have a Kodak DC280 by the way.)

  63. Second.... by neilb78 · · Score: 0

    >> Does that make us the second most powerful now? :)

    Nope. That's makes you the first loser!

    --
    © 2004 The SCO Group, Inc. All Rights Reserved.
  64. Being first? by jelle · · Score: 2

    Being first is not always being best.

    Actually, in software, the first version usually has the most bugs.

    Rush, Rush, and Rush. Debug later sell first.

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  65. Re:What's this about Virtual LAN cards through USB by scm · · Score: 1

    I don't think you can do this with USB. USB has 1 host (the computer) and one or more clients. You can't have more than one host on a chain, so you can't connect 2 computers. I guess someone could build a box that looked like a client to each computer that connected to it, and run a network over that, but I don't know how cheap it would be.

    But you could do this with FireWire. Windows and Linux both support it already, IIRC. Plus, from what I've heard, the current FireWire is faster than USB 2.0. And the next version of FireWire (due to start showing up pretty soon) is twice as fast.

  66. A U.S. Air Force General once said... by Napalmstrike · · Score: 1


    ..."the second best fighter jet is like the second best hand at poker. No damn good!"

    Wouldn't you agree it applies to software as well?

    DISCLAIMER
    Take this as a rallying call, and maybe you'll derive something good from it.
    Take this with your typical flame-happy slashdot troll attitude and maybe you'll piss off your neighbors with your ranting.

    --
    I'm bored, lets go break something.
  67. Re:What's this about Virtual LAN cards through USB by Anonymous Coward · · Score: 1, Informative

    You mean like this IOGear product announcement for a USB 2.0 host-to-host link? Many such devices are already supported under Linux with the usbnet driver, though currently only at USB 1.1 speeds. (It should be easy to tell that driver how to handle one more device ... :)

    I'd expect it to be 2-3 times as fast as a 100BaseT link, without too much trouble, even on early USB 2.0 implementations. Bridge it (Linux will do the spanning tree stuff for you!) and make it be a relatively cheap 480 MBit/sec Ethernet style LAN.

    That product might be based on the NetChip TurboConnect2 device. For USB 1.1 speeds there are a bunch of such custom devices, resold by many companies. I'd be rather surprised if that didn't happen with USB2.

  68. Mod this guy up. by Mustang+Matt · · Score: 1

    I'm glad someone here has a head properly fastened to his shoulders!

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  69. Has anyone? by Mullen · · Score: 2

    Has anyone pointed out that releasing a year behind is like a million in computer years?

    --
    Linux O Muerte!
  70. Nomenclature by Paul+the+Bold · · Score: 2

    This is a pet peeve of mine, but megabit and megabyte are not synonims. They differ by a factor of eight. Does the journalist really mean mbps means megabits per second? Am I being too picky? A byte as wordsize is obsolete these days anyway.

    My favorite quote of the article is "SuSE is thinking of providing software that lets customers upgrade to the 2.4.19 kernel..." Last time I installed SuSE, gcc and ftp were part of the standard installation.

    1. Re:Nomenclature by twinpot · · Score: 1

      This is a pet peeve of mine, but megabit and megabyte are not synonims. They differ by a factor of eight. Does the journalist really mean mbps means megabits per second?
      Hmm, and (m) milli differ from (M) megas by a rather large chunk too. I suspect a (M) mega wotsits per second would be more useful ;-)

  71. Re:What's this about Virtual LAN cards through USB by Anonymous Coward · · Score: 0

    Oh yeah, there's now a webpage for the usbnet driver.

    That basically tells how to do USB host-to-host networking over USB today. Special devices that talk to two different hosts, and switch between them. Sure, you could build switches that talk to even more, but this is where it starts ... :)

    When this all works with zeroconf IP it'll be easy to set up a peer-to-peer LAN with speeds of several hundred Mbit/sec. Until then, you've got to set the net up by hand ... :)

  72. Re:Second? [NO, FIRST ] by Anonymous Coward · · Score: 0

    The standard releases of Windows STILL (!!) do not come with USB 2.0 support. End users must add it themselves ... and so must OEMs.

    If we look at RedHat and SuSE as examples of Linux OEMs, we see that until now, Linux has been at the same stage as Windows in terms of distributing the software: in both cases, the integration was done by OEMs. In what sense is this "a year behind"?? Not device driver support, from what I've seen; few devices, no lack-of-driver problems. Maybe in testing, but Linux always relies on "real world testing" anyway.

    As of 2.4.19, Linux OEMs don't need to do this integration any more. But MSFT ones still need to do that integration. (Or if they don't, that's a very recent change, as of the last few months.) So: Linux may well be the FIRST OS to really bundle USB 2.0 support in its base distribution.

    Yes, I could count NetBSD, but they don't have a particularly complete implementation even in their latest CVS. There's a lot of basic stuff they don't seem to have yet; I seem to recall at least one high speed transaction type as unsupported, and no split transactions at all. (And split transactions start to add up to a lot of work...) Linux handles all of that, except for the "split isochronous" type needed to stream a dozen USB 1.1 webcams on one USB 2.0 bus.

  73. Re:What's this about Virtual LAN cards through USB by ahfoo · · Score: 2

    Ah, the ol' usbnet driver. Thanks for the tip. Of course getting a USB2.0 to ethernet setup working and creating virtual NICs would be two different issues. Is there such thing as a generic MAC addeess?
    I've seen some of USB1.0/Ethernet adaptors as well so the same thing with 2.0 didn't sound all that far fetched. It sounds quite intriguing, but I suppose there's quite a few details to be worked out. For one I don't think I've seen USB2.0/Ethernet adaptors yet. You'd probably need those to start. Oh wait, the MAC addess would be in those. Hmm, I see you'd need to buy these little adaptors --once you could find 2.0 versions of them-- and then switch them using a regular fast ethernet switch. Perhaps it's not as complicated as a I thought, nor quite as virtual as I had assumed at first. That doesn't mean it aint cool though. Those USB1.0/ethernet adaptors were right cheap as I recall.

  74. Re:What's this about Virtual LAN cards through USB by Anonymous Coward · · Score: 0

    Standard Ethernet addresses are pretty generic MAC addresses; IEEE standard in fact. That's what the "usbnet" driver uses.

    There is a USB 2.0 10/100BaseT Ethernet adapter announced, from D-Link I think, but then you're talking Ethernet, not a "Virtual LAN" technology (which is really IP-over-USB).

  75. What about the "universal" serial standard for USB by TeddyR · · Score: 2

    My biggest pet peeve about USB in ANY platform is that instead of doing what they did with the mice/keyboards/audio/parallel drivers and make a standardised spec. for a serial class, they waited too long so the manufacturers had to come out with thier OWN methods to communicate with their serial devices. This made it a nightmare to try and get a serial converter recongnised in linux.

    For windows, the manufacturers made some of the drivers avail for their serial converters. [but now even some of the early ones are no longer supported in XP like the enterga/xircom/intel ones and the intel based mct ones]

    The problem with USB is the need for a separate driver for MANY of the common devices.

    Getting everyone together to come out with UNIVERAL device specs that the manufacturers follow and an easy way to update the device IDs for the OS would greatly advance the use of USB on Linux.

    --

    --
    Time is on my side
  76. What if it was the other way around? by Launch · · Score: 1

    I wonder what the slashdot community would be saying if Linux supported USB 2.0 a full year before MS...

    It surely wouldn't be as casual as the "we are the second most powerfull" comment made in the writeup.

    --
    Your mammas flamebait.
  77. Linux has always been behind in USB. by OrangeTide · · Score: 1

    Linux was behind FreeBSD in it's USB 1.x support for the longest time. Now it's a little bit ahead (I say because the improved driver model for USB on linux is better than FreeBSD). It's not like USB is some trivial thing, SCSI and Ethernet are way easier to implement, which is why open source unix clones are ahead of windows in that. (Yes, Linux supports ethernet cards that windows does not. don't freak out over it).

    --
    “Common sense is not so common.” — Voltaire
  78. No USB 2.0 Yet?! by Anonymous Coward · · Score: 0

    You mean you guys don't have USB 2 yet?

    Holy fucking shit, why are you guys using Linux anyways? I find XP Home to be more stable than my Debian (on the same machine with no windows only hardware)... What's left in Linux that makes so many geeks use it?

  79. USB 2.0 Support in Mandrake out of the box by Luckster7 · · Score: 0

    I get about 14MB/s on read to an external USB2 maxtor 120MB drive according to hdparam. I had my hands on a 160MB Firewire maxtor drive and only got about 12MB/s. Both drives used ext3.

    I've been using the external USB2 drive for several months now, probably close to 1/2 a year and it has performed perfect, except when I plug it into my USB1 machine at work (way too slow).

    --
    Deuteronomy 13:06-9
  80. Complaining about Potterheads...? by Abreu · · Score: 1

    But you -did- get the reference, didnt you?

    --
    No sig for the moment.