Slashdot Mirror


Why We Can't Just Get Along: The Bootloader

mccormi writes: "Byte has an article from the BeOS perspective on why we don't see more dual boot machines from vendors. Browser anticompetitive complaints are nothing compared to what's happening with the bootloaders since the majority of people using computers will never have the know-how or courage to make an OS change."

174 of 513 comments (clear)

  1. Read this article - Worths Gold by Eugenia+Loli · · Score: 5, Insightful

    Yes, before you start replying here, please READ that Byte article. It will show you what really happened with the Ms antitrust case in the issue of the "secret license", and it will explain one of the fundamendal and most important reasons why Be was driven out of business and BeOS never became mainstream.

    1. Re:Read this article - Worths Gold by connorbd · · Score: 2

      I don't think there's any question at all of that. Even the appeals court thought so, even though they tossed the remedies.

      /Brian

    2. Re:Read this article - Worths Gold by cruelworld · · Score: 2, Troll

      That's funny. I thought that BeOS died because it was buggy, ill-supported, took 10 years to come to market, switched focus every two years to alienate it's users and developers and had no applications.

      Man, I can't believe how Bill Gates fooled me.

    3. Re:Read this article - Worths Gold by be-fan · · Score: 5, Informative

      Real funny. There are parts of BeOS that aren't particularly stable (like net_server) but the guts have always been solid. Saying that it is buggy is just plain false.

      Second, BeOS is probably just as well supported as Linux. There is a great user community, and I have yet to see the Linux equivilent of betips.net. Granted, commercial support on Linux is probably better, but given that BeOS runs a great deal of GNU code (like the entire CLI environment, for example) support on the application level is probably about the same.

      As for taking a long time to come to market, that's false as well. BeOS had a solid journeling FS long before ReiserFS came out. BeOS had a great desktop environment (proudly based on the Mac GUI) before KDE and GNOME ever got their acts together. It had sub 3ms audio latencies when the low latency patches were just a gleam in Ingo Molnar's eye. BeOS had technology in 1997 that Linux is just getting today. In another year or two, one will be able to say that Linux is the greatest media OS on the planet. At its current pace of development, there is no doubt about that. However, that level of development will only compare to what BeOS was in 1998.

      Enough with the focus shift BS. There have been two focus shifts in Be's history. First, they switched from IAs to desktops. Then, 8 years later, they switched back to IAs. It was a last ditch effort to save the company, and it gave people hope for a few more months. The focus shift was just a symptom of the fact that Be was on its way out, not a cause.

      Yes, Be had a lack of applications. That's the problem that any alternative OS that doesn't use X must endure. OSS-types talk about freedom, but what about those who want to be free of the shackles of X?

      Linux types always get mean about BeOS. My theory is that BeOS is the only thing out there that could possibly challenge Linux for technological supremacy. The BSD folks have already settled for the server market, and if WinXP is any indication of the future, it looks like MS won't be any competition. No, BeOS was the only thing that could have foiled Linux on the desktop. Well, the cornoation can preceed as scheduled. There are no more troublesome pretenders to the OS throne...

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:Read this article - Worths Gold by Dwonis · · Score: 2

      Bah. X isn't that big. Take what top(1) reports, subtract your video memory, and the font cache, and the backing store (if applicable), and X isn't very big at all.

    5. Re:Read this article - Worths Gold by Adnans · · Score: 2

      ....... At its current pace of development, there is no doubt about that. However, that level of development will only compare to what BeOS was in 1998.

      Hahaha, and how is that going to help us? Be fans LOVE to point out the "superior" technology in their beloved BeOS (I was once such a person :). However, that's probably one of the reasons BeOS is gone today. Too much arrogance, too little substance!!

      Yes, Be had a lack of applications. That's the problem that any alternative OS that doesn't use X must endure. OSS-types talk about freedom, but what about those who want tYes, Be had a lack of applications. That's the problem that any alternative OS that doesn't use X must endure. OSS-types talk about freedom, but what about those who want to be free of the shackles of X?o be free of the shackles of X?

      Funny, X is still around after all these years, while BeOS is going down the toilet faster than a turd spinning counterclockwise in Australia. Why don't you port or rewrite the 'great' BeOS Interface Kit to X. You can get all features, including one thread per window on X today, no populair toolkit does this however. I know there is closed-source code out there that does exactly this. According to you people are probably begging for this functionality right now...So go on!

      BTW, if you read the osnews.com forums you'll see that there are several serious issues with the BeOS pervasively mulit-threaded interface.

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    6. Re:Read this article - Worths Gold by 4of12 · · Score: 2

      That's funny.

      Cut off any company's air supply and it is quite possible to produce comedic staggering antics that appear funny, rife with incompetent execution, incomplete plans, etc.


      I hope you never have to suffer the distinction of belonging to a company that has been choked in such a manner. But I'm guessing that you don't.

      --
      "Provided by the management for your protection."
    7. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Hahaha, and how is that going to help us? Be fans LOVE to point out the "superior" technology in their beloved BeOS (I was once such a person :). However, that's probably one of the reasons BeOS is gone today. Too much arrogance, too little substance!!
      >>>>>>>
      All OS afectionados love to brag. At least BeOS users can brag and not lie. I've laid out several reasons why (as a Media OS) BeOS beats Linux. If you'd care to refute any of these, be my guest.

      Funny, X is still around after all these years, while BeOS is going down the toilet faster than a turd spinning counterclockwise in Australia.
      >>>>
      So, the measure of a GUI's quality is how long its been around?

      Why don't you port or rewrite the 'great' BeOS Interface Kit to X.
      >>>>>>>>
      Because it would then just be another stupid X toolkit.

      You can get all features, including one thread per window on X today, no populair toolkit does this however.
      >>>>>>>
      Yes, that's because UNIX in general is loathe to enforce (or even promote) policy. Its all about huggy feely "you have the freedom to do whatever you want!" stuff. BeOS was designed to encourage highly multithreaded programs with fast GUIs. Aside from the window threading example you have so nicely pointed out, there is the fact that BeOS's API encourages developers to extensively use attributes. Again, you can do this on Linux too, but you don't see applications doing this prevasively, do you? Similarly, the messaging system encourages scriptable apps. While it is entirely possible in Linux, the system doesn't encourage that behavior, and thus you don't see a unified app scripting system in Linux. The media system is designed to encourage a modular, plug-in based approach with multiple programs sharing media streams. While this is also possible with Linux (well, on low latency patched kernels anyway) the lack of any central encouragement precludes large scale integration of media apps.

      I know there is closed-source code out there that does exactly this. According to you people are probably begging for this functionality right now...So go on!
      >>>>>
      I don't know about closed source code, but I do know that BeOS's system isn't really possible on Linux right now. Neither Qt nor GTK+ are very thread-safe in their present states, which is why neither GNOME nor KDE use threads extensively. This should theoretically change with GTK+ 2.0 and Qt 3.0.

      BTW, if you read the osnews.com forums you'll see that there are several serious issues with the BeOS pervasively mulit-threaded interface.
      >>>>>>>>
      Where? I looked through the entire BeOS board, couldn't find anything related to multithreading. Did searches for both "GUI" and "thread." "Thread" turned up on irrelevant hit, while "GUI" simply turned up some articles about improving the GUI. What posts are you referring to?

      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Doubtful. MS is regressing technologicially. Linux is continually moving forwards. I am the last person to talk about Linux's success (I'm extremely critical of it even now), but undoubtedly Linux will beat Microsoft. Its starts in the server room. Sheer product quality CAN eventually defeat Microsoft, its just a very time intensive process. No closed company has the resources to follow that processes, but Linux community is big enough that it can fight MS indefintely.

      --
      A deep unwavering belief is a sure sign you're missing something...
    9. Re:Read this article - Worths Gold by be-fan · · Score: 2

      MOSX really isn't in a position to challenge Linux, since the field of battle is x86, not PPC. The x86 regime is even more entrenched than Windows, Apple hardware still can't beat top-end x86 hardware, and its price/performance ratio sucks. Unless IBM and Motorola bring out some serious open PPC hardware at good prices (they won't neither company has the balls to go up against Intel) PPC will continue to be marginal.

      --
      A deep unwavering belief is a sure sign you're missing something...
    10. Re:Read this article - Worths Gold by be-fan · · Score: 2

      It depends on what you mean by support. Generally, I think of hardware support. And in that area BeOS has always lacked.
      >>>>>>>>>
      True.

      Well, that depends on what you want to do with it in terms of media. Capture and edit video? Linux is current the best of the two with more applications and more video capture card support.
      >>>>>>>
      Well, supporting the most capture cards doesn't make on OS the best media platform. Right now, the best Media OS is Windows 2000, both because of its good performance and board hardware support. If Linus can keep his promise that 2.5 will fix many of the latency problems of 2.4, maybe Linux can pull ahead. After that, Linux will have to work on getting a good media environment, something it may never be able to do because of the sheer number of projects trying to do the same thing.

      Unless you're talking about a CLI network application. If your lucky, you might be able to get it to compile. If your on God's good graces, you might be able to get it to run without bringing down the net server.
      >>>>>>>
      Yea, the net_server sucks. Acknowledged feature ;)

      And what shackles would that be? The shackles of anti-aliased fonts? The shackles of hardware accelerated 3D (something that BeOS has never really supported for more than the Voodoo cards through glide)?
      >>>>
      The shackles that make X slower and less responsive than even Win2K. The shackles that make the X codebase larger than the ENTIRE BeOS system. The shackles that make X fragmented and filled with competing, incompatible toolkits. Some people like the extra freedom. Some people are disgusted with the non-uniform waste of CPU and RAM that is the average Linux desktop. Many BeOS users happen to be the latter.

      Pretenders to the throne are a good thing... It means that there's competition which, in general, leads to better products. BeoOS had great potential, and could have been the next in line, but Be Inc. dropped the ball.
      >>>>>
      I was being sarcastic.

      --
      A deep unwavering belief is a sure sign you're missing something...
    11. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Maybe if you run FVWM. But we're talking about a full desktop (GNOME or KDE) which is what you need to run if you want to compare with BeOS or Win2K that have the DE and GUI integrated. Either way, the whole shebang is slower than Windows 2000, which is just silly bad.

      --
      A deep unwavering belief is a sure sign you're missing something...
    12. Re:Read this article - Worths Gold by be-fan · · Score: 2

      According to Opensources.com, XFree86 is over 1.5 million lines of code. That is larger than the whole BeOS source tree. I'd say that that's pretty big, top or not. Both BeOS's GUI and QNX's GUI are less than 2MB in size, and QNX's GUI has even more functionality. I don't give a damn WHAT 'top' reports, X is too large.

      --
      A deep unwavering belief is a sure sign you're missing something...
    13. Re:Read this article - Worths Gold by be-fan · · Score: 2

      KDE-2? KDE-1 lacks many features that Win2K has, which makes the comparison unfair. As for KDE-2, even with the obj-prelink extensions, Konqueror takes three or four times as long too start than IE. In fact, EVERY KDE-2 app takes three or four times longer than IE (or Visual Studio or even Word). And GNOME flickers a LOT more than Win2K. What kind of graphics card are you running? I'm using a RivaTNT with NVIDIA's drivers, so that's not the problem. (And yes, I've tried the renice -10 hack and the low latency patch and the HZ=1024 hack).

      --
      A deep unwavering belief is a sure sign you're missing something...
    14. Re:Read this article - Worths Gold by be-fan · · Score: 2

      XP is on the order of 20-30% slower than Windows 2000. If that's isn't regressing, I don't know what is. MS is so concerned with 1% features (ie. features which only 1% of the userbase will take advantage of) that it is rebloating their OS. Win2K was unusually good for an MS product, but it seems that it was just a fluke.

      As for product quality, just look at the numbers. Linux networking is faster and more stable than Windows. Almost every kernel operation is faster. The VM is more well tuned. The filesystems (XFS and ReiserFS) are faster and more stable. Basically anything in the kernel (except the server-oriented scheduler) is better. The GUI needs a lot of work, but compared to XP's, its actually snappy. The only thing Linux has left to do is to fix the toolkit mess and get X running faster (maybe twice as fast and it will compare to BeOS and Photon ;)

      --
      A deep unwavering belief is a sure sign you're missing something...
    15. Re:Read this article - Worths Gold by Adnans · · Score: 2

      All OS afectionados love to brag. At least BeOS users can brag and not lie. I've laid out several reasons why (as a Media OS) BeOS beats Linux. If you'd care to refute any of these, be my guest.

      Sure, list them. I happen to know a couple of people who are migrating their (BeOS) Media applications straight to Linux. No point in building your software/hardware on a dead/unsupported system. And from my own experience in porting BeOS software to Linux, I can say that Linux provides most everything that is needed and much more (e.g. progress).

      BeOS was designed to encourage highly multithreaded programs with fast GUIs.

      Sadly, this hasn't panned out too well. It takes quite long time to get threads right. Porting apps from other OSes took considerable effort and willpower. Be talked about the "tractor app" thingy since 1995. To date there hasn't been a single native tractor app for BeOS. So much for the highly multithreads programs with fast GUIs.

      ...there is the fact that BeOS's API encourages developers to extensively use attributes

      And in the process they pretty much lock themselves to BeOS' APIs. And we all know how large the BeOS installed base is :-)

      but you don't see applications doing this prevasively, do you?

      No, because well, there's no reason to do so, unless there's a broader standard, and clearly there isn't (look for ACL/extended attributes integration in the 2.5.x kernel tree). BeOS was ahead of the pack, but unfortunately for Be and its develoeprs that meant shit..

      the lack of any central encouragement precludes large scale integration of media apps.

      Again, this hasn't helped Be one bit. Why? Because the Media Kit is so full of bugs, not to mention horribly documented, it is practically impossible for anyone outside of Be to write any Media add-on more complex than an audio codec.

      ...which is why neither GNOME nor KDE use threads extensively

      The only apps that really benefit from threads are media applications and most, if not all of them do use threads. GTK+ 1.2.x is already thread safe. Qt 3.0 is too. But because developers are NOT FORCED to use threads you will most likely only encounter them when they actually make a difference! I do wish Mozilla used separate threads to manage each browser window. Anyway, threads have their place but don't glorify them too much (just watched over 3 hours of perfectly synced DVD, thanks to some clever threading :)

      Where? I looked through the entire BeOS board, couldn't find anything related to multithreading. Did searches for both "GUI" and "thread." "Thread" turned up on irrelevant hit, while "GUI" simply turned up some articles about improving the GUI. What posts are you referring to?

      This thread. Read the comments by JBQ.

      "Multithreading sounds cool, but it's an unnecessarily complex beast to master, and the fact that it's asynchronous by nature makes it fairly hard to debug, and creates some behaviors that vary a lot between machines. Plus, people learn and like to write synchronous code. "

      and

      "The problem with BeOS isn't the fact that the kernel allows for multiple threads. The problem is the fact that developers are forced to use multithreading under BeOS, that they are forced to use the BeOS locking mechanism, and that various bugs and limitations in BeOS make all that even harder than it should already be. Sure, a computationally intensive application might (and probably will) benefit from spawning an extra thread. Sure, a game that needs to send feedback to different output devices might benefit from putting the game engine in a separate thread. But in many cases, it's just overkill. "

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    16. Re:Read this article - Worths Gold by be-fan · · Score: 2

      No, from the Anandtech articles.

      --
      A deep unwavering belief is a sure sign you're missing something...
    17. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Yes, KDE2
      Maybe because IE is loaded by the OS when the computer starts? As for Word staring that quickly, that's total BS (at least on my machine).
      >>>>>>>>
      Even when you have started the app previously (which means that Linux will cache the image), all KDE-2 apps still take several seconds to load. I know that this isn't a problem with Linux, since most Athena apps of comparable functionality take much less time to load. As for Word, I don't know how your machine is configured, but mine is a nicely tweeked Win2K machine running on a PII-300 with 256MB of RAM. I have all the stupid graphical features turned off, I have harddrive indexing turned off, and I've done the standard little tweeks. Word (97, but 2000 isn't much slower, and Word 97 still beats KWord in functionality) starts up in a second or two. After having loaded it once, starting up is instantaneous.

      With both my GeForce II and Radeon (the Radeon generally locks up within 10 minutes or so under W2K, too).
      >>>>>>>>>
      Hmm, did you update the graphics drivers for both? Win2K is really finicky about bad drivers. Do you have DMA disabled? Win2K doesn't like the SiS 630's IDE controller. Do you have lots of things running in your system tray? Win2K is faster than KDE-2 for a whole lot of people, so its not just my config.

      --
      A deep unwavering belief is a sure sign you're missing something...
    18. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Well, if you can stand X, more power to you. Maybe your fast hardware masks it, or you just aren't as twitchy as I am ;)

      --
      A deep unwavering belief is a sure sign you're missing something...
    19. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Sure, list them.
      >>>>
      I already have, in my previous post.

      The next part of your arguement basically boils down to "ignore all the technical reasons, Be died so BeOS must have sucked," and "BeOS sucked because it wasn't easy to port to." I make no arguement that Be the company is pretty dead, but I'm not talking about success. I'm talking about the technical quality of the OS.

      The only apps that really benefit from threads are media applications and most, if not all of them do use threads.
      >>>>>>
      That's not really true. Many applications can benifet from threads, it just requires a different style of programming. People said the same thing about OO programming until they realized that the main problem was that too many people were too set in their procedural ways. I've programmed with threads ever since I left high school comp-sci, and it really isn't that hard. Its more difficult to debug, true, but not appreciably, if the app is coded in a multi-threaded way to begin with.

      GTK+ 1.2.x is already thread safe. Qt 3.0 is too.
      >>>>>>>
      GTK+ 1.2 is hardly thread safe. According to the GTK+ FAQ, there is a global lock on the whole system which negates any advantages of threading. As for Qt 3.0, it hasn't been released yet, so it is of no consequence at the moment.

      But because developers are NOT FORCED to use threads you will most likely only encounter them when they actually make a difference! I do wish Mozilla used separate threads to manage each browser window. Anyway, threads have their place but don't glorify them too much (just watched over 3 hours of perfectly synced DVD, thanks to some clever threading :)
      >>>>>>>>.
      The reason I say that GUI developers should be forced to use threads is because, all too often, developers try to use (comfortable) procedural techniques to do GUI programs, which ineherently lend themselves well to a messaging/multi-threading model. Plus, it is a big boon to those with SMP machines (getting more and more common) if an OS's application base is extensively threaded.

      That's wasn't in the forum, it was attached to a story. Anyway, JBQ makes a good point: it is hard to port non-threaded software to a threaded environment. But that's not the issue here. BeOS was designed to get rid of a lot of baggage, and unnecessarily single-threaded software was one of those pieces of luggage. I've been a BeOS user for several years, and the apps have been extremely stable, multi-threading or not. People who have developed native BeOS applications have pointed out that it is easy once you understand it. I'm not trying to claim that threading is a silver bullet that will solve everything. However, it is a technique that has many advantages, especially for SMP machines, that that technique is often ignored by software developers who are too scared to architecture their programs differently.

      --
      A deep unwavering belief is a sure sign you're missing something...
    20. Re:Read this article - Worths Gold by Adnans · · Score: 2

      I already have, in my previous post.

      Oh, I remember refuting many (all) of your points against Linux/X11 a couple of weeks/months ago. I will pick legacy, network transparant, X11, with Geforce2, full OpenGL, over BeOS Vesa 2.0 any day, thank you very much. It makes practical and technical sense...

      The next part of your arguement basically boils down to "ignore all the technical reasons, Be died so BeOS must have sucked," and "BeOS sucked because it wasn't easy to port to."

      If you want to read it that way, sure. I never said BeOS sucked, however it's faaar from being superior. I was into Be probably way before you even heard of them. I have a BeBox to prove it :) I spent countless hours coding neat stuff for BeOS (it wasn't even called BeOS back then). Hell, I ported one of the first MP3 players over to BeOS :-) I know all about its pervasively multithreading enviroment. Back then I was simply amazed at how easy it was to get graphics and sound mixed with threads. But it was always a toy. You could do neat stuff with it, but there were no real advantages over other OSes at the end of the day (with the exception of the journalled FS).

      GTK+ 1.2 is hardly thread safe. According to the GTK+ FAQ, there is a global lock on the whole system which negates any advantages of threading

      Oh really? I think you need to take some more classes on threading then. Since your videocard is not multi-threaded all drawing events gets serialized at some point. The global GTK+ is ugly, but very effective. And your applications still take advantage of threading, if you code them correctly. Heh, just a couple of days ago I hit a locking bug in my pet project. The whole GUI froze because I acquired a lock twice, yet the music kept playing on. It even jumped to the next song in the playlist. The GUI thread was deadlocked, yet my audio and disk thread continued like there was nothing wrong. Sure, gtk+ global locks negates any advantage of threading, NOT! You use threads to do CPU intensive work while still being able to process other events (like the GUI). You do not use threads to fight for the single 2D pipeline that most PC graphics cards have these days.

      As for Qt 3.0, it hasn't been released yet, so it is of no consequence at the moment.

      Oh dear, I should wipe my stolen copy quickly then!

      The reason I say that GUI developers should be forced to use threads is because, all too often, developers try to use (comfortable) procedural techniques to do GUI programs, which ineherently lend themselves well to a messaging/multi-threading model.

      With the risk of not taking into account the technical advantages this has I will say that this model hasn't helped BeOS one bit! The fact that any programmer that wanted to put a BWindow on the screen had to deal with threads and locking has IMHO stiffled application development a great deal. Just look at BeBits.. it's full of "Hello World" style apps. There are very few mature applications available.

      Anyway, JBQ makes a good point: it is hard to port non-threaded software to a threaded environment

      He also points out that there are fundamental problems with the way BeOS handles inter-thread messaging. These problems will probably not bite the average graphics viewer coder, or the mp3 player program, but they will bite once you start coding moderately complex tools.

      Threads are cool, I use them every day. But like you say, they are not the silver bullet. On a sidenote, my heavily multithreaded audio player has been churning through a 3000 entries long playlist for 2 straight days now, rock solid :) Oh, and it uses GTK+ for threading the scope windows. Yes, each scope window has it's own worker thread, just like BeOS. In this case, it is usefull to have multiple threads calculate and draw the scopes in offscreen bitmaps before blitting them to the screen. Bottom line: use threads where they're usefull, don't use them pervasively (perversely :), just because it's technically "cool".

      BTW, you should go back to the forum/discussion area I pointed out earlier. There's some more interesting notes from JBQ on the "pervasively multithreading" nature of BeOS (He mentions smoke and mirrors.... ugh :)

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    21. Re:Read this article - Worths Gold by Adnans · · Score: 2

      Sorry to have 2 replies but I was just very surprised when reading the following piece of text from JBQ:

      "Big surprises here : there's usually only one mouse, only one keyboard, such that cases where several applications have to respond to input events at the same time are marginal, unusual cases. As for redrawing, all the redrawing events are sent to the graphics chip, which can only deal with one acceleration at a time anyway. "

      And that's exactly what I was saying 2 minutes ago.... JBQ rocks :-)

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    22. Re:Read this article - Worths Gold by be-fan · · Score: 2

      I don't get your arguement that BeOS isn't superior to Linux for media. The default Linux kernel's audio latency still blows, and even the guys doing the low-latency patch still use BeOS as a benchmark for low latency. True, the low-latency kernels do get far lower latencies than BeOS these days, but they still aren't part of the main tree, and thus aren't available to many people. For example, if you want XFS and low latency in the same kernel, its a crap-shot if the two patches are in sync. And with Linus's kernel of the day syndrome, that situation won't get any better.

      Oh really? I think you need to take some more classes on threading then. Since your videocard is not multi-threaded all drawing events gets serialized at some point. The global GTK+ is ugly, but very effective. And your applications still take advantage of threading, if you code them correctly. Heh, just a couple of days ago I hit a locking bug in my pet project. The whole GUI froze because I acquired a lock twice, yet the music kept playing on. It even jumped to the next song in the playlist. The GUI thread was deadlocked, yet my audio and disk thread continued like there was nothing wrong. Sure, gtk+ global locks negates any advantage of threading, NOT! You use threads to do CPU intensive work while still being able to process other events (like the GUI). You do not use threads to fight for the single 2D pipeline that most PC graphics cards have these days.
      >>>>>>>>
      What about drawing to multiple views? If GTK has a single global lock, doing GTK+ operations on one window will lock out those doing operations in another window. Also, many operations don't use the graphics hardware anymore. GNOME's canvas uses LibArt heavily, and as far as I can see, it is 100% software.

      Oh dear, I should wipe my stolen copy quickly then!
      >>>>>
      That's not my point. My point is that it hasn't been released, it isn't in any distros, and is thus not really usable yet. Even after its release, it will be awhile before many apps take advantage of its features.

      With the risk of not taking into account the technical advantages this has I will say that this model hasn't helped BeOS one bit! The fact that any programmer that wanted to put a BWindow on the screen had to deal with threads and locking has IMHO stiffled application development a great deal. Just look at BeBits.. it's full of "Hello World" style apps. There are very few mature applications available.
      >>>>>>>
      I don't really think that its is really the multi-threaded nature of BeOS that stifled application development. Windows 2000 uses threads even more agressively than BeOS (right now, with 2 IE Windows, two explorer Windows, and MS Word running, I have 273 total threads, maybe 100 that don't sleep all the time), and it has a ton of mature software. MS word uses half a dozen threads with one document open. IE uses 32 threads for its two windows, and there are over 30 system threads running. And Win2K can hardly be called an unstable environment. And Word 97, Visual Studio, and IE-6 are all sold, mature, complex programs that are EXTREMELY responsive to the user. I'm not dumb enough to think that more threads are necessarily better, I'm just pointing out that complex multithreaded environments ARE possible and they CAN be stable.

      Anyway, JBQ makes a good point: it is hard to
      He also points out that there are fundamental problems with the way BeOS handles inter-thread messaging. These problems will probably not bite the average graphics viewer coder, or the mp3 player program, but they will bite once you start coding moderately complex tools.
      >>>>>>>
      Yes, this dropped message thing is troubling. But it has yet to pop up in actual usage and if BeOS development had continued it could presumably be fixed. QNX is totally message based, and I really doubt you'd trust a nuclear reactor to an inherently flawed model.

      Threads are cool, I use them every day. But like you say, they are not the silver bullet. On a sidenote, my heavily multithreaded audio player [alsaplayer.org] has been churning through a 3000 entries long playlist for 2 straight days now, rock solid :) Oh, and it uses GTK+ for threading the scope windows. Yes, each scope window has it's own worker thread, just like BeOS. In this case, it is usefull to have multiple threads calculate and draw the scopes in offscreen bitmaps before blitting them to the screen. Bottom line: use threads where they're usefull, don't use them pervasively (perversely :), just because it's technically "cool".
      >>>>>>>
      No, not just because it is technically cool. Because with Win2K getting more popular, WinXP coming into the home, and dual Duron systems costing chicken scratch, SMP machines will become very popular. Apple's multi-proc machines were of limited usefulness because so little Mac software is multithreaded. Systems that use threading agressively (and yes, it is possible to use it agressively and still correctly) won't have this problem.

      BTW, you should go back to the forum/discussion area I pointed out earlier. There's some more interesting notes from JBQ on the "pervasively multithreading" nature of BeOS (He mentions smoke and mirrors.... ugh :)
      >>>>>>>>
      Yea I read it.

      --
      A deep unwavering belief is a sure sign you're missing something...
    23. Re:Read this article - Worths Gold by Adnans · · Score: 2

      The default Linux kernel's audio latency still blows, and even the guys doing the low-latency patch still use BeOS as a benchmark for low latency

      Probably because BeOS made the biggest noise about low latency audio support.

      For example, if you want XFS and low latency in the same kernel, its a crap-shot if the two patches are in sync. And with Linus's kernel of the day syndrome, that situation won't get any better.

      Actually the people that really want or need this right now, this moment, can get their cake and eat it too. FYI, I have 2.4.10-pre1-xfs + low latency 2.4.9 patches running just fine :) Of course, all of this patching will not be necessary once these go into the main kernel tree, and the will go in. At least great things are happening. Can't say that for BeOS.

      What about drawing to multiple views?

      What about it? Your PC will never draw to multiple views simultaneously, not even on BeOS (and not even on an SMP box). That's because there's only one blitter engine on the graphics chip.

      Of course there can be multiple outstanding draw requests, but X and gtk+ in combination with the GDK_THREAD_ENTER/LEAVE calls take care of that very well. Oh, and you can always open multiple X server connections from a single application. You will get multiple X pipelines (that get serialized in the X server / graphics driver) but at the application level you will have the equavalent of multiple BWindows with their own BLooper. And since everything on a X screen is inside an X Window you can treat all elements as Views.

      If GTK has a single global lock, doing GTK+ operations on one window will lock out those doing operations in another window.

      You only ask for the lock when you change internal shared data structures or if you want to push a pixmap to the screen. It's the same as in BeOS. Offscreen drawing can be done inside a gdk pixmap, and you don't need to hold the lock to do this. Only when you are ready to blast the pixmap on the screen do you request the lock. That's exactly how things work in BeOS. The locking might take place on another level but in essence it's exactly the same. And not surprisingly, BeOS mutithreaded code runs at the same performance level in Linux/X (at least my applications do :-) See the screenshots on my homepage with 20 audio scopes running perfectly sync to the 3 audio files being played, simultaneously with gobs of CPU cycles to spare :)

      Also, many operations don't use the graphics hardware anymore. GNOME's canvas uses LibArt heavily, and as far as I can see, it is 100% software.

      The canvas is just an offscreen image. You can have multiple canvas widgets being modified by multiple threads without problems. That is if libArt is reentrant itself (I've never used it). In the end, the canvas images will have to be drawn in the framebuffer and that is done by a single hardware blitter device.

      About Win2000 using so many threads. It'd be interesting to know how many of those threads are created by the programmers explicitly, and how many are the result of just calling a function in win32.

      No, not just because it is technically cool. Because with Win2K getting more popular, WinXP coming into the home, and dual Duron systems costing chicken scratch, SMP machines will become very popular. Apple's multi-proc machines were of limited usefulness because so little Mac software is multithreaded. Systems that use threading agressively (and yes, it is possible to use it agressively and still correctly) won't have this problem.

      The average Linux installation, will benefit greatly by running on an SMP box. And this, out-of-the-box.
      I have 102 processes loaded, that's with 6 Konqueror windows, a bunch of deamons, 8 terminal windows and my audio player on screen. If I had multiple processors in my box, they would all be utilized fully...You don't need very fine grained threading for that (remember, processes are just glorified threads, or the other way around, depending on how you look at it)

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    24. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Probably because BeOS made the biggest noise about low latency audio support.
      >>>>
      But more likely because it has audio latencies a order of magnitude lower than stock Linux and Windows.

      Actually the people that really want or need this right now, this moment, can get their cake and eat it too. FYI, I have 2.4.10-pre1-xfs + low latency 2.4.9 patches running just fine :) Of course, all of this patching will not be necessary once these go into the main kernel tree, and the will go in. At least great things are happening. Can't say that for BeOS.
      >>>>>>>>
      Yes, right now it works. But I run a similar config, and XFS-Linux 2.4.7 broke the low-latency 2.4.6-pre2 patches. It took more than a week to get 2.4.7 patches up. That's why I said it was a crapshot. And I know that 2.5 is getting lots of latency work, that's why I stated in my original post that Linux WILL become the ultimate media OS. Its just not there right now.

      What about it? Your PC will never draw to multiple views simultaneously, not even on BeOS (and not even on an SMP box). That's because there's only one blitter engine on the graphics chip.
      >>>>>>>
      Only if all you're doing is shoving bitmaps at the screen. The actual drawing code CAN run in parallel. Let me explain this to you. Say you start drawing a line. The line algorithm steps along the line and starts writing the pixels to video RAM. Halfway through, you're thread gets preempted and another graphics thread starts running. If there is a global lock on the drawing code, then that thread will block until the first thread finishes drawing. On the other hand, if everything is correctly parallized, that second thread can keep on writing to memory without interfering with the other thread. Also, the blitter can be shared as well. True, there is one blitter, but it is one hellishly fast blitter. On my DirectX tests, the RivaTNT's blitter can blit more than 30,000 small bitmaps per second. Thus, it can blit a bitmap once every 33 usecs. Also, the blitter can queue up blits. That leads to the following scenario: say a process locks GDK, issues a series of blits, then unlocks it. During this process, it is preempted by another drawing thread. By the time the system has done a context switch, most of the blits will be done. If they aren't, the thread can still issue more blits to be queued. If there is a global lock, however, the second thread will sleep, and by the time the system gets around the scheduling the first thread again, all of the blits would have completed long ago. In a parallel system, the second thread's blits also would have been queued and completed. In a serial system, only the first thread's blits would have been finished. The idea of keeping the I/O hardware as busy as possible is an important one in OS design. Most modern OSs go through hoops to make sure that processes that are I/O bound get as many chances as possible to make requests for I/O. Thus, they can wait on the I/O while other threads use the CPU.

      Of course there can be multiple outstanding draw requests, but X and gtk+ in combination with the GDK_THREAD_ENTER/LEAVE calls take care of that very well. Oh, and you can always open multiple X server connections from a single application. You will get multiple X pipelines (that get serialized in the X server / graphics driver) but at the application level you will have the equavalent of multiple BWindows with their own BLooper. And since everything on a X screen is inside an X Window you can treat all elements as Views.
      >>>>>>>>>>
      Maybe. Setting up a separate connection for each view seems slow though, and might blow chunks if you actually use the networking features of X. But I'd have to look at performance data to be sure.

      --
      A deep unwavering belief is a sure sign you're missing something...
    25. Re:Read this article - Worths Gold by be-fan · · Score: 2

      Sorry for the two replies, but I had to point this out. I don't like Linux's tendency to use multiple processes instead of threads. Whenever you switch processes, you have to change memory maps, frag your TLB, blow some cache, and it just gets nasty in general. Heavly multi-processed code is almost exactly equivilent to multi-threaded code, so I don't know what the justification is for using one over the other. The only thing multiple-processes buys you is protection from your own threads. And Linux has some pretty good threading code, so its not lack of support in the platform.

      --
      A deep unwavering belief is a sure sign you're missing something...
    26. Re:Read this article - Worths Gold by Adnans · · Score: 2
      Yes, right now it works. But I run a similar config, and XFS-Linux 2.4.7 broke the low-latency 2.4.6-pre2 patches. It took more than a week to get 2.4.7 patches up

      So? Remember, you don't *have* to upgrade your kernel everytime a new patch comes out. I have a production machine with 2.4.3-XFS that has already logged over 130 days of uptime and still going strong. I will most likely start test-running 2.4.10-XFS once that comes out and if proven sufficiently stable will switch over.

      that's why I stated in my original post that Linux WILL become the ultimate media OS. Its just not there right now.

      Good, at least we can agree on that point :-)

      [explanation cut]... Most modern OSs go through hoops to make sure that processes that are I/O bound get as many chances as possible to make requests for I/O. Thus, they can wait on the I/O while other threads use the CPU.

      While this is true, implementations of multi-threaded X servers (to overcome the theoretical contention problem you describe) have proven that speed gains are only marginal. So in the real world you will have to choose between:
      • Marginally better throughput accompanied with exponential programming complexity increase (mandatory thread/locking management in your program).
      • Good throughput but without more complexity forced upon you then necessary (but with the option of using extra threads).

      Pick your poison. JBQ makes an excellent point when he states that BeOS forces developers "to handle asynchronous events through threading, such that the core services of the operating system only handle synchronous requests".

      Maybe. Setting up a separate connection for each view seems slow though, and might blow chunks if you actually use the networking features of X

      The performance and responsiveness of remote X apps is entirely determined by your network speed and latency (on my local LAN remote X window creation is practically instantaneous).

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    27. Re:Read this article - Worths Gold by Dwonis · · Score: 2
      Yes, and I'm sure all those lines of ATI Rage Pro support are being used for your Matrox card.

      X is large, but it's not THAT large. What makes X seem big is really your window manager / desktop environment. I run WindowMaker, and X is quite fast, actually.

  2. Isn't this trial material? by sllort · · Score: 4, Interesting

    You and I can't read the license because Microsoft classifies it as a "trade secret." The license specifies that any machine which includes a Microsoft operating system must not also offer a nonMicrosoft operating system as a boot option. In other words, a computer that offers to boot into Windows upon startup cannot also offer to boot into BeOS or Linux. The hardware vendor does not get to choose which OSes to install on the machines they sell -- Microsoft does.

    The obvious question here is: why didn't the DoJ use this as part of their anti-trust trial? Isn't this the most blatant example of monopoly leverage in existence?

    Most importantly, are there any copies of these "trade secret" OEM license agreements on file somewhere? Without some sort of public record, we pretty much have to take the author's word for it (not that I doubt him).

    As much as we'd like to create a technological circumvention for this, we can't. Because the people who are affected by this are the people who don't have enough computer knowledge to even know they have a choice. And Microsoft has, very intelligently, ensured that they never will.

    Innovation at it's finest.

    1. Re:Isn't this trial material? by Mr+Skreet+Nite · · Score: 2, Informative

      If you read the article the author explains quite clearly why this evidence wasn't used.

      "The burning question, of course, is why Boies and Klein didn't want Gassée to testify on the bootloader issue, especially when it could have substantially helped their case? The answer provided to Gassée was that the case was by then already too well established. Including the bootloader issue would have meant rewriting many of the arguments and calling in a new collection of witnesses. In other words, it wasn't convenient for the U.S. government to get to the meat of the matter.... In addition, no PC OEM was willing to testify on bootloader issues...... Finally, Be didn't have the brand recognition that Netscape did; Netscape made for a much better poster child. "

      "If it smells, it's Chemistry, if it moves, it's Biology, and if it doesn't work, it's Physics"

    2. Re:Isn't this trial material? by ortholattice · · Score: 3, Informative
      Most importantly, are there any copies of these "trade secret" OEM license agreements on file somewhere?

      I doubt you'll find an example of an OEM license. I imagine the NDA is truly onerous. But there are little hints (http://news.cnet.com/news/0,10000,0-1005-201-3233 68-0,00.html) here and there:

      "If you are willing to give Microsoft a clear written assurance that the above will be implemented on all Compaq Presario machines within sixty (60) days of the date of this letter, Microsoft will withdraw its Notice of Intent to Terminate letter addressed to David Cabello and dated May 30, 1996 once such written assurance is received by Microsoft."

  3. Revenge of the 800 lb Gorilla by Whyte+Wolf · · Score: 2

    The revelation that Microsoft would hold a gun to their OEM's heads doesn't suprise me. Microsoft may not be the 'Great Satan', but their business practices are somewhat sinister, cloak and dagger, and monopilist.

    What surprises me is that some of the major hardware vendors would put up with this. Compaq, Dell and IBM? Without them to pre-load windows (which would happen if MS pulled their license) half of Window's market share would evaporate. It's true--few people would install their own OS. If MS pulled their license, why doesn't IBM or Compaq just install Linux for free and say to hell with Redmond?

    Maybe there's more to this than just the license thing. maybe Bill Gates has several CEO's families held hostage in the basement of his Redmond Complex....

    --

    Beware the Whyte Wolf.

    With a gun barrel between your teeth, you speak only in vowels...

    1. Re:Revenge of the 800 lb Gorilla by Sloppy · · Score: 2

      If MS pulled their license, why doesn't IBM or Compaq just install Linux for free and say to hell with Redmond?

      I don't know why, but if IBM were even mildly interested in doing that, then OS/2 would still be a major player. Whatever the hell caused them to abandon that, is probably also still a factor in Linux-related decisions.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:Revenge of the 800 lb Gorilla by UM_Maverick · · Score: 2

      The OEMs won't drop Microsoft because everybody (/. company excluded) wants Windows. That's all they know. Go up to the typical 40-year old blue collar worker, and ask him what linux is...I tried it once, and the person told me that it was a type of China/silverware...

      If Dell says "no more windows", 95% of their customers are gonna jump ship. Both Dell and Microsoft know this...Microsoft may be evil, but they are definitely not stupid.

    3. Re:Revenge of the 800 lb Gorilla by Black+Parrot · · Score: 3

      > What surprises me is that some of the major hardware vendors would put up with this.

      A classic case of taking the short-term easy route without regard for the long-term consequences.

      They are now completely beholden to Microsoft, and would have trouble changing their business plan to change that fact, if they did decide that they wanted to.

      --
      Sheesh, evil *and* a jerk. -- Jade
    4. Re:Revenge of the 800 lb Gorilla by (void*) · · Score: 2
      OS/2 was an IBM/Microsoft collaborative effort to produce a good, modern OS after Windows 3.0. But Microsoft played a dastardly trick. They convinced developers to develop for Windows 3.1 while OS/2 was being developed, giving the reason that OS/2 would run Windows 3.1 applications. But half-way through, MS walked away from the collaboration. IBM's hopes of sharing the market with Microsoft evaporated, while Microsoft got a better kernel, which they slapped a GUI on and called it Windows NT. In time, this kernel became Windows2K, while the other kernel based off Win3.1 became Win95, then Win98 and finally WinME (and no more).


      So who says MS only wrote one OS?

  4. Linux is not free to ship on a system by tim_maroney · · Score: 3, Insightful

    Linux is free. And yet there are no commercially available dual-boot machines on the market.... There is no other way to explain this phenomenon other than as a repercussion of the confidential Windows License under which every hardware vendor must do business.

    No, Linux is not free to the vendor. It requires an extra configurator setting, more system testing, documentation and support cost, installer and boot-time software development, inclusion of CD-ROMs, and a few gigabytes off the hard disk. If there's not customer demand for the feature there's no point in the extra cost for the system vendor.

    Tim

    1. Re:Linux is not free to ship on a system by the+gnat · · Score: 3, Insightful

      But the license is free. Most of the Windows installations I've used have been quite heavily customized anyway by the PC maker. For most standard desktop PC hardware Linux is about as straightforward to set up as Windows, if you know what you're doing. Most of the PC hardware I've ever dealt with took less time to get working under Linux than under Windows. ( the rest, of course, took weeks. ah well.)

      Forgive me from bringing up TCO here, but this applies too. A company like IBM or Dell can afford to run their own distro- or just an enhanced RedHat/Debian/whatever- and finally they can control what software is preinstalled, what icons show up, etc. And there will be no fee to any OS manufacturer. Long term, this is probably quite a bit less expensive than the bulk OEM Windows licenses.

      On the other hand, the Dells I've seen with Linux preinstalled appear to have shipped with the standard version of RedHat, i.e. $50, so there's not too much savings. I don't know what RedHat's deals with OEMs are- perhaps it's still cheaper than Windows, perhaps not. However, I'd guess the costs involved in setting up dual Windows/RedHat for all machines wouldn't be worth it, given the number of people who'd actually use the second OS.

    2. Re:Linux is not free to ship on a system by tim_maroney · · Score: 2

      so explain to me why linux is free to all my friends

      I listed eight specific costs to a system vendor. Was there something you didn't understand?

      Tim

    3. Re:Linux is not free to ship on a system by Khalid · · Score: 2

      Come on !

      Yes it needs some setting and testing for a new category of material, but one it's done just create an image and load it automatically in your thousands if not millions similar machines.

      Can you say economy of scale ?

    4. Re:Linux is not free to ship on a system by Eloquence · · Score: 2
      extra configurator setting, more system testing

      Yes, Linux has to be installed and tested. This should not be a big problem for large manufacturers with standardized PC series, though.

      documentation and support cost

      These are not necessary, e.g. "Compaq machines come with Linux as a dual-boot option. A lot of documentation is included in the /usr/doc directories. However, we only give support for the Windows configuration of your machine. If you desire Linux support, we suggest you call Redhat and ask for the special-priced Compaq support package .."

      installer and boot-time software development

      This is part of the installation costs. These are short-term costs that reduce long-term installation costs.

      inclusion of CD-ROMs, and a few gigabytes off the hard disk.

      Irrelevant.

      If there's not customer demand

      There is no demand if there is no information. Marketing creates demands by spreading information, some false, some true. An OEM could theoretically market Linux as an additional feature, with the "no support" provision. But Microsoft's licensing coerces them into not doing it. These are practices of a monopoly that must be stopped.

    5. Re:Linux is not free to ship on a system by reverius · · Score: 2

      Umm... RedHat actually has a license?

      I was under the impression that it was legal to install a single bought copy of RedHat on 500,000 computers (or for that matter, borrow your friend's CD).

      How is selling computers with RedHat any different from just "putting RedHat on all those computers"?

      What I mean is... why would they have to pay for licenses at all? Even considering they bought a boxed set, aren't they allowed to just install that on all of their computers?

    6. Re:Linux is not free to ship on a system by the+gnat · · Score: 2

      Give me a fucking break.

      I meant on commodity hardware, fuckwit. Dell, Compaq, IBM, HP, etc., not your $400 chop-shop piece of shit with Bob's Wicked Video II or whatever. And I meant for the OEMs to set up, not Joe Sixpack.

      I've found 90% of users can't set up a Windows machine properly (or at all), so it's a moot point anyway. As a programmer, and user of 4 different OSes, Linux is by far the easiest for me to get working- and I assuredly know what I'm doing. Windows 98 worked so badly on my NEC laptop that I nuked the partition and added it to the RedHat system. I'm probably doing something wrong, but I don't care enough to find out what. Geeks, too, can be complacent and lazy.

      I don't expect the MSCEs at PC manufacturers to have an easier time setting up Linux than Windows. But for someone with proper training- which is really just a matter of messing around with the system- Linux can be a breeze to set up. At this point it's effortless for me, the same way it's effortless for you to install Windows. Got it?

    7. Re:Linux is not free to ship on a system by the+gnat · · Score: 2

      The boxed set of RedHat stuff comes with extra goodies like commercial software and *gasp* manuals. Most users consider this worthwhile. I'm honestly not sure if you're allowed to burn and resell copies of the commercial software CD, but the manuals are not free.

      I'm sure Stallman is pissing himself over that, but it looks like this business model might actually work. At any rate, if OEMs buy the full version from RedHat they can distribute the standard labelled CDs, the manuals, etc. Regardless of how useful much of this is, it adds credibility and marketability to their product.

      They could do this themselves, too- it's just often easier to "license" the extra goodies from RedHat. And if they actually pay a per-box license fee to RH, they're more likely to see their hardware supported better, etc.

  5. GAG by matek · · Score: 2, Informative


    The BEST bootloader available right now is GAG. Multiple OS's on multiple Primary partitions, the bootloader is able to fit into the bootsector itself, it fixes errors, it finds in bootsector etc. etc.

    1. Re:GAG by Syberghost · · Score: 2

      I know it supports a jillion OSes, but does it support English?

  6. Perhaps because few would want them? by interstellar_donkey · · Score: 2, Funny
    Before we get upset and assume that there is some sort of corporate conspiracy keeping multi-OS systems off the shelfs, it seems a more reasonable explination that most people simply would'nt want to deal with Two OSws.


    There are execptions, of course (for example, many of the readers here). But why would your average end user want to have to learn two (or more) seperate OSes?


    At best, out of the box multi-OS machines could satisfy a small niche market of hobbyists and power users, and I'm sure somewhere those would make up a large enough marketshare to support a couple of vendors.


    But me, personally, I'll keep BSD on my machine I made for BSD, and my Windows on my machine taylored for windows.

    --
    The Internet is generally stupid
    1. Re:Perhaps because few would want them? by Eloquence · · Score: 2
      Before we get upset and assume that there is some sort of corporate conspiracy keeping multi-OS systems off the shelfs


      Nice try. The OEM licenses are a well-established fact and not a conspiracy, but business-as-usual for Microsoft. Whether or not consumers want multiple OS is besides the point. The point is that Microsoft is clearly abusing its monopoly to gain a strong competitive advantage over other operating systems. This abuse must stop ASAP.

    2. Re:Perhaps because few would want them? by Tim+Doran · · Score: 3, Insightful

      This was adressed in the article. BeOS was free, at least for a while, to be dual-booted with Windows. It would be technically trivial to enable dual-boot.

      So you'd think vendors, who are straining for differentiation, would jump on the opportunity. This falls into the "can't hurt, could help" category.

      *That* is why this looks suspiciously like the result of Microsoft tactics.

    3. Re:Perhaps because few would want them? by Jeremi · · Score: 2
      What I will say is that MS, even *if they are a monopoly and we assume so, has done nothing to prevent you, the user, from getting an alternate operating system. You, the user, are free to install anything you want on your machine.


      True, assuming that you, the user, are comfortable enough with computers to know how to install your own operating system. But you and I both know that doing so isn't a realistic option for most people--you might as well ask them to replace the carbeurator in their car.


      Microsoft has made sure the public does not have the option of buying a computer that dual-boots Windows and a non-Microsoft operating system, and that's what counts, not the hypothetical possibilities of what people could do if they were all computer geeks, which they surely aren't.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    4. Re:Perhaps because few would want them? by Eloquence · · Score: 5, Insightful
      I dont feel like getting into a MS monopoly argument, so I am not going to say that MS isnt a monopoly, even though I believe they are not (and that the courts will eventually agree with me).

      What a nice way to make a statement without having the facts or arguments to support it. "I don't feel like saying the Earth is flat, so I am not going to say it is, even though I believe it is, and most serious scientists will eventually agree with me."

      What I will say is that MS, even *if* they are a monopoly and we assume so

      What is a monopoly by your definition? Are 90% of the marketshare enough? 95%?

      has done nothing to prevent you, the user

      *beep* Wrong line of argument. Monopolies are not about direct coercion. Monopolies, while they do have immense market power, are not governments, otherwise they would be called governments. Monopolies, through accumulation of capital and mindshare, may be able to create a market in which it is impossible or very hard for competitors to thrive, even though this may be in the best interest of the consumers. Microsoft is such a monopoly.

      "Freedom of choice" arguments sound nice and are exactly the kind of rhetoric you would expect a Microsoft-propagandist to employ -- however, they are fundamentally flawed in that they omit an essential factor that determines our decisions: information. By being a monopoly, Microsoft has the advantage (and, rarely, the disadvantage) of being the focus of all media attention. And they have loads of money to spend on propaganda, too. Your decision to use or not to use a Microsoft OS may be free of direct coercion, but it is certainly not free of manipulation. And because of the nature of an operating system, being the basis for all other software run on a computer, any program that is written exclusively for a Microsoft OS strengthens Microsoft's monopoly. Thus, any switchover can obviously only be gradual, with many people using two or more operating systems at the same time (which, incidentally, has been confirmed in a recent survey of 10000 Linux users, where only 38% used no other OS besides Linux -- even many professionals boot Windows NT or 2K together with Linux).

      Linux is now in a position where it can actually compete with Windows in most fields, even in spite of Microsoft's market domination (a fact which lends tremendous support to arguments for open, patent-free software development). But consumers know little about Linux because of Microsoft's media domination, and they can't give it a try easily because of Microsoft's coercive OEM licensing. These are clearly practices of a monopoly by any reasonable definition, and they make it hard for the little competition to gain market share. Whether such practices are illegal under US antitrust law, I cannot say -- I care more about morals than about law. On the basis of morals, I can see no reasonable argument why the kind of coercive OEM licensing Microsoft uses should be allowed.

    5. Re:Perhaps because few would want them? by be-fan · · Score: 2

      News flash.

      If you want the abuse to stop, then DONT USE MICROSOFT PRODUCTS. EVER. PERIOD. END OF STORY.
      >>>>>>>>
      If you don't like the Standard Oil monopoly, stop using petroleum! If you don't like AT&T, stop using phones! If you don't like US Steel, stop using pots and trains and cars and shovels.

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:Perhaps because few would want them? by (void*) · · Score: 2
      Are you sure exclusive contracts are legal when you are a monopoly? Are you a lawyer? Do you play one on TV?


      IBM was going head to head with Microsoft for a while, then they decided not to. So they worked together to write OS/2. But Microsoft played dirty by spreading the propaganda to developers, telling them to write for Windows, because OS/2, when done, would run Windows applications. Guess what? MS broke development halfway through on OS/2, and ran away with the developers who wrote for Windows, thinking it would be supported by the IBM/MS empire.
      IBM was left holding an OS with no market, and MS a with a better kernel than Windows. This better kernel eventually became Windows NT, and then W2K.


      This is but another example of MS's anticompetitive sleazy behaviour.

    7. Re:Perhaps because few would want them? by Have+Blue · · Score: 2

      Get a Mac, run the latest Virtual PC (for OS X, almost out). It can run multiple OSes, each in a seperate window.

    8. Re:Perhaps because few would want them? by (void*) · · Score: 2
      You miss the point. The point is whether Joe Consumer knowingly makes this choice, or does not. Microsoft's history has always been to decrease, minimize and de-emphasize the fact that an active choice in this matter has to be made.


      Two roads diverged upon the road, but most people took the well-travelled one, becuase they didn't know that that treacherous looking one was a road and a viable one!

    9. Re:Perhaps because few would want them? by (void*) · · Score: 2

      If you want the abuse to stop, then DONT USE MICROSOFT PRODUCTS. EVER. PERIOD. END OF STORY.
      MS can put anything they want in their software, and can install it any which way they want, with any conditions they want. If you don't like it, don't buy MS products.


      I wish it was that simple. I live MS free, but ever so often, university administrators send a Word document my way, asking me to sign something or approve it before it gets printed. So I get second-order coercion effects. Is there anything in your libertarian philosophy that talks about such effects? Or is that concept too complex for such a sophomoric view of the universe?

    10. Re:Perhaps because few would want them? by Spy+Hunter · · Score: 2
      [...] its not illegal! The Sherman Act doesn't regulate free trade, it regulates monopolies trying to use its monopoly power to expand into new markets. Period. This isnt a new market. This is the preservation of an existing market.

      The defense attorneys could have used this anyway in order to prove that Microsoft was in fact a monopoly. I guess they felt it wasn't necessary though. The guy in the article was wrong to be mad at the attorneys for not including this evidence, because they did indeed prove that Microsoft was a monopoly even without the help of this bootloader evidence. It would have been superfluous if they had included it, delaying the trial (which would be to Microsoft's advantage).

      Be, Inc. couldn't sue Microsoft over the matter either, as he suggests, since its not illegal. Basically, this guy is all wrong about what he is saying because he doesn't understand the legal issues. That's the problem with armchair lawyers.

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    11. Re:Perhaps because few would want them? by (void*) · · Score: 2
      You misunderstand me if you think I was attacking you. I am attacking your idea. The simple-minded suggestion that merely not using MS products is the solution to MS's continuing abuse and hegemony over their customers. For many people, this is simply not an option, because of second-order coercion effects!


      The presence of conversion programs is all well and good. They are all there, in spite of MS's attempts not to document their formats. Who was the first to publish their Word document formats? I was developing programs, and I made an extensive check back in 1991+. Third parties who reverse-engineered their document format supplied doucmentation, not MS. (MS Developer net was not on the internet then.)
      Even now, the conversion is not perfect. Not becuase it cannot be done, but becuase the MS document format was not designed to specifications, but specifications written to suit the code, which is hidden.


      There is every evidence of poor design in MS's products. Yet they persue an agenda to dominate the software market not by excellence, but by monopolist action.


      You see, you've turned the argument into a personal one. These things are solutions for me, but should they not be solutions for others too? Can one not turn that the second order coercion towards weaning consumers from inferior products? Or should merely apologizing for MS's monopolist actions be the order of the day?

    12. Re:Perhaps because few would want them? by (void*) · · Score: 2
      You miss the point yet again. To "choose to be ignorant" is not the same as "ignorant of choices". MS makes use of the people who are ignorant of choices, by marketing to them, taking their money and using that to encroach upon others who choose otherwise.


      For example: MS Word or Excel does not exist for Unix systems. If MS was only a software applications company, they would have seriously considered expanding their market. Even if they determined that the market was too insignificant for them there is an opportunity for them to license a port like Loki does of Civilization, for example. But they do not, which makes you wonder why they do not want the extra business.

    13. Re:Perhaps because few would want them? by Malcontent · · Score: 2

      It's not that MS won. It's that they were slimy, unethical and immoral in doing so. You apparently think all business people (well maybe the business people who win) are also slimy, unethical and immoral but I don't. I do think it's possible to be an ethical person and run a successful business.

      Nobody in MS feels the same way.

      --

      War is necrophilia.

    14. Re:Perhaps because few would want them? by Simon+Brooke · · Score: 2
      Before we get upset and assume that there is some sort of corporate conspiracy keeping multi-OS systems off the shelfs

      When I bought my Toshiba Libretto, it came preinstalled with two OSs. When first booted up, it offered a dialogue box which asked which of the two OSs you wanted to use, and then deleted the other.

      What were those OSs? MS Win95 and MS Win98. But that's really not the point. Toshiba had developed an installer which allowed the machine to be shipped to the customer with multiple OSs, and allow the user to choose which he wanted. It's not just technically possible, it was judged financially worth while.

      And it would have been nice if it had also shipped with Linux installed, because it's a real pain getting Linux onto one of those beaties first time. The additional cost of adding Linux would have been small, and it doesn't take much research to discover that quite a proportion of the ultra-small, ultra-geek-toy laptops run alternative OSs - just check out any geek conference you go to.

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    15. Re:Perhaps because few would want them? by sql*kitten · · Score: 2
      Microsoft has the advantage (and, rarely, the disadvantage) of being the focus of all media attention


      Nonsense. It's hard to imagine Linux getting more hype/publicity than it does. It is given away on coverdisks of mainstream PC magazines, it has IBM backing it, it has hight profile companies (LNUX, RHAT) based on it, and it's now they height of "cool" to praise Linux to the heavens.


      Your decision to use or not to use a Microsoft OS may be free of direct coercion, but it is certainly not free of manipulation.


      That's true of *any* product, why do you suppose so much is spent on advertising Coca Cola (not a monopoly), Nike (again, not a monopoly), Ford (see a pattern here?) et al.


      On the basis of morals, I can see no reasonable argument why the kind of coercive OEM licensing Microsoft uses should be allowed.


      The OEMs were willing enough to sign those agreements when it was to their economic advantage to do so.

    16. Re:Perhaps because few would want them? by Shimbo · · Score: 2
      As for going 'head to head with MS', Compaq and Dell and couldn't do this because THEY DON'T HAVE A FUCKING OS.

      Compaq could have done because they acquired the rights to VMS and Tru64 from Digital.

    17. Re:Perhaps because few would want them? by (void*) · · Score: 2
      I am sorry, but if competitive business practices causes harm to consumers and developers, then it cannot be justified on those grounds.


      In the OS/2 case, developers were looking at the IBM-MS collaboration, and planning a switch of platforms to OS/2. MS instead sold them on that inferior product which is Win3.1. We could have a good OS with properly pre-emptive multitasking. But we didn't.


      As for the assertion that Windows NT is not based on OS/2 but VMS, that is just wrong. Windows NT was definitely spun off from OS/2, the development of which was based on VMS. Those VMS engineers were from IBM!

    18. Re:Perhaps because few would want them? by (void*) · · Score: 2
      Maybe they waiting for even one other company to be long-term succesful with Linux?


      This is very funny. Long before MS was on the scene, DEC was selling Unix workstations. If MS actually wanted to do ports, there were planty of platforms to port to.


      MS's problem is that they only want to code for the x86 processor. Sure they considered PowerPC, and Alpha, but as a software company, they weren't in the game to establish their applications monopoly. Believe it or not, that would have benefitted both consumers and them, but they didn't.

    19. Re:Perhaps because few would want them? by (void*) · · Score: 2

      And no, I am not missing the point. You want to equivocate over whether "marketing" equals "forcing". It doesn't. I will restate for: any consumer who chooses to be informed with readily see that MS isn't the only show in town.


      Sorry, but that not what I am arguing about. Marketing may or may not include second order coercion effects. Coke marketing coke has no influence on what I drink. There is no such effect. For software, there is, becuase I have to exhchange files with friends (a transaction having nothing to do with MS, but MS, through anticompetitive practices, is trying to force me to switch to MS).


      I have plenty of examples of MS's sleazy business practices. Whether you consider them OK or not, is your business. They may even be legal. So what, those examples all show detriment to the consumer.
      Examples like the IBM-MS OS/2 breakup, the sneaky error message of incompatitbility with DRDOS, when there is no incompatibility, the use of IE as a pawn to get rid of Netscape. The Palm OS incident.

    20. Re:Perhaps because few would want them? by SurfsUp · · Score: 2
      It wasnt brought up because its not illegal! The Sherman Act doesn't regulate free trade, it regulates monopolies trying to use its monopoly power to expand into new markets. Period. This isnt a new market. This is the preservation of an existing market.

      Are you just clueless, or are you knowingly trying to spread disinformation? The Sherman act provides that the use of monopoly power either for the maintainance of a monopoly or the extension of the monopoly into a new market is illegal.

      This did nothing to stop competiton, except for one specific form of it.

      That's enough. Go to jail, do not pass go.

      --
      Life's a bitch but somebody's gotta do it.
    21. Re:Perhaps because few would want them? by SurfsUp · · Score: 2
      I dont feel like getting into a MS monopoly argument, so I am not going to say that MS isnt a monopoly, even though I believe they are not (and that the courts will eventually agree with me).

      Who the fuck cares what danheskett, anonymous astroturfer on Slashdot thinks? A federal court has already decided the issue and been upheld unanimously by the appeals court, en banc.

      --
      Life's a bitch but somebody's gotta do it.
    22. Re:Perhaps because few would want them? by be-fan · · Score: 2

      If you don't like the Standard Oil monopoly, stop using petroleum! If you don't like AT&T, stop using phones! If you don't like US Steel, stop using pots and trains and cars and shovels.

      Are you suggesting that the of a compture requires the use of Microsoft products?
      >>>>>>>>>>
      Yes. And every desktop computer maker seems to agree with me.

      --
      A deep unwavering belief is a sure sign you're missing something...
    23. Re:Perhaps because few would want them? by Malcontent · · Score: 2

      I could list you dozens but they are in my town and you wouldn't know them. I know for sure that every businessperson in the world is not a sleazebag like the Microsoft people are. I will grant you that a significant portion (but not a majority IMHO) of business people are bastards though. George Carlin has a very funny skit about that.

      --

      War is necrophilia.

  7. Casio by Ridge2001 · · Score: 2, Informative
    The author makes an interesting allegation, but does he have any proof of it? The license he talks about is still supposedly a "trade secret".

    The main evidence he presents is the absence of hardware vendors selling dual-boot systems. But there seems to be at least one counterexample.

  8. Fine, but define "Bootloader"? by torpor · · Score: 2

    DOS used to be a bootloader, for an operating system called Windows 3.1 (and, less obviously, some later versions too).

    If we're going to call for restrictions on operating system bundling practices, we must be prepared to draw a line in the sand and define at what point a bootloader itself is *not* an operating system, and at what point it is...

    Think about it. Is an OS something that allows a user to select from a number of different programs, each with their own storage/comm mechanisms, and have those programs run, successfully, managing resources as needed, to completion?

    On the one hand - sure, lets melt down our bootloaders to make weapons, but then again: what're we really doing?

    :)

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    1. Re:Fine, but define "Bootloader"? by Tim+Doran · · Score: 2

      uh... not to pick nits, but DOS is an OS. Windows 3.x (and, arguably, 9.x) is a GUI.

      And the issue isn't bootloaders. It's dual-boot capability. Half the ./ crowd could probably write a competent bootloader. Be's problem was that they couldn't get space on OEM machines' hard drives.

    2. Re:Fine, but define "Bootloader"? by torpor · · Score: 2

      True, DOS is an OS. I'm not saying it's not an OS - but that it served as a bootloader for Win3.1, another 'operating system'.

      You're missing my point, which is:

      What is an operating system, what is a bootloader, technically? At which point does a bootloader, legally, become an 'operating system'...

      This distinction may not be so clear to you right now, but there was a time when there was little distinction - and fighting on this front may not prove to be worth it, against Microsoft.

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    3. Re:Fine, but define "Bootloader"? by be-fan · · Score: 2

      Your statement makes no sense. On x86 systems, a boot loader is something that resides on the first sector of a disk partition. The purpose of the bootloader is to load an OS image and jump to it. DOS isn't a boot loader. That's like saying Linux is a bootloader for X. DOS *has* a boot loader, which is a separate entity entirely. GRUB blurs the lines slightly (because it has many OS-type features such as a shell), but it's still a program that is contained in the first sector, and its sole purpose is still to load an OS image and jump to its starting location. Interestingly, it could be stated that GRUB is actually an OS, but its bootloader still retains a seperate identity.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:Fine, but define "Bootloader"? by (void*) · · Score: 2
      Who says no one wanted it? Looking at the feature set, I am confident that had I seen BeOS then, I would have picked it up, along with Linux.


      It was too bad for BeOS, and for me, that we were not on each other's radar. And why not? Becuase BeOS had a huge barrier to surmount, to get into the market. That all the industry players were into talks with them indicates interest. But they all dropped the ball, indicating that other factors were at work. To all our detriment.


      Just think: by 1997, we could all have a multimedia capable OS with a journalling filesystem. But we could not because of the shortsightedness of the OEMs and the greed of Microsoft.

    5. Re:Fine, but define "Bootloader"? by Adnans · · Score: 2

      Who says no one wanted it? Looking at the feature set, I am confident that had I seen BeOS then, I would have picked it up, along with Linux.

      He was talking about OEMs. BeOS was offered free of charge to any OEM who wanted to pre-install it on their new PC. JLG made a big hoopla out of this. The only problem was that no OEM wanted it......

      But they all dropped the ball, indicating that other factors were at work. To all our detriment.

      Yeah, the biggest factor was that BeOS was never a drop-in replacement for Windows.

      Just think: by 1997, we could all have a multimedia capable OS

      I had a multimedia capable OS long before that. Oh, and in 1997 BeOS multimedia was in a sad state. The new media-kit hadn't arrived yet, and it didn't run on commodity x86 hardware yet, so you had to buy a ridiculously expensive Mac machine or a second hand BeBox to get it to run.

      with a journalling filesystem.

      Journalling is nice, journalling was also very immature on BeOS. I remember loosing 2 filesystem because they got full. Go figure :)

      -adnans

      --
      "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
    6. Re:Fine, but define "Bootloader"? by be-fan · · Score: 2

      Oh please, the whole first sector bit is just semantics. If "boot loader" is a reserved term for that sector then his argument holds for some other term. Grub isn't an OS anymore than the OS/2 boot manager or System Commander is an OS.
      >>>>>>>
      And why not? Many toy OS kernels have less functionality than does GRUB.

      Look at NetWare for example, where DOS is/was pretty much used exclusively as a 'bootloader' (Loads OS image, and jumps to it, then DOS is blown out of memory).
      >>>>>>>>
      Doesn't matter. Netware used the DOS bootloader. It might have used DOS to provide services to Netware (like reading the OS image from a filesystem), but the actual booting of the machine was done by DOS's bootloader. In that case the bootloader loaded an OS, which loaded a user program that wiped DOS out of memory and loaded another OS. In that case, there were two bootloaders, DOS's, and the user program that loaded Netware.

      --
      A deep unwavering belief is a sure sign you're missing something...
  9. Dual Booting??? What for? by fm6 · · Score: 2, Interesting
    Dual booting is just not a serious solution for most people. If you really need that app that only runs on Linux or BeOS or whatever, you don't have time to reboot your machine to get at it. You buy a second machine, you buy a software VM, or you find a substitute that runs under Windows.

    The last solution is the one most people choose. The substitute may not work as well as the non-Windows alternative, but unless you're a total fanatic, it's just not worth the hassle.

    1. Re:Dual Booting??? What for? by wfrp01 · · Score: 2

      If you really need that app that only runs on Linux or BeOS or whatever, you don't have time to reboot your machine to get at it.

      I think your statement contradicts itself. If you need that app, you'll do what it takes. Each OS has it's own unique repertoire of applications. Using the right app for the job will save a lot more time than it takes to reboot. It might even make the impossible possible. Not everyone can afford dedicated hardware for each OS.

      --

      --Lawrence Lessig for Congress!
  10. DOS attack? by slickwillie · · Score: 2

    Why can't M$FT be prosecuted for Denial of Service?

    If I install, let's say FreeBSD, then I install Windows, it will wipe out the FreeBSd boot manager (without asking), thus denying me the FreeBSD service. Why does M$ think they own my boot track?

    1. Re:DOS attack? by mandolin · · Score: 2
      Some os's do stupid things in the name of "convenience" that could be taken maliciously.

      Most people installing windows wouldn't know what the hell a bootsector even is. And I doubt you could explain it to them. "Detected an unknown bootsector. Maybe it's garbage. Or maybe it belongs to another operating system that needs it to boot. On the other hand we need it too. Abort, Ignore?"

      94% will be confused; of these 5% will flood tech support asking about "unknown operating systems". 4% (smart linux/bsd users) will know what you're talking about but the question is useless to them, since they have to work around it anyway. The last 2% (stupid linux/bsd users) will ignorantly click-thru, blow away their other os, and sue anyway.

    2. Re:DOS attack? by j7953 · · Score: 2

      Because booting Windows it's what 99% of users want when they install Windows. And because most of the users won't understand the question the installer would ask them, no matter how good it's written. Also note that many current Linux distributions will not only overwrite your boot track, they'll also kill your Windows partition (they ask, though) if there's no unpartitioned space.

      But the real reason is that the boot track / master boot record is a broken concept. AFAIK the installer has no option of finding out what is currently installed there, unless it knows all possible systems and can identify them. Obviously this doesn't work at least for those systems developed after the installer.

      If there were an industry standard "operating system table", OSs could just add themselves to that table on installation and everything would work fine. While we're at it, could we throw away the concept of partitions as well? (No I don't have a solution.)

      --
      Sig (appended to the end of comments I post, 54 chars)
  11. BeOS? by jeffy124 · · Score: 2

    I'm afriad I'm a victim of popularity here. I'm a Windows and Mandrake guy. I've heard of BeOS, but have not taken much time (actually none) to learn more about it. It appears from the article that BeOS had something to offer to consumers that made Compaq, Dell, and Hitachi wanted to sell it alongside Windows (until the lawyers noticed the fine print on the MS license).

    Given that, what is significant about BeOS? What is the hype about? etc etc.... ????

    --
    The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
  12. Re:Darwin on x86 by MrBlack · · Score: 2

    Because Office for Mac and IE for Mac would disappear.

  13. What a load of bull. by Rimbo · · Score: 3, Insightful

    This guy starts to make a good statement, and then trips and makes a fool of himself in the comment you quoted.

    Yes, it's a mistake to make a commercial OS, but not because people are complicit in accepting Windows. It's because Windows is the only OS that anyone will pay money for nowadays, and even that is beginning to change.

    The OS has become a commodity. What OS you use is becoming largely irrelevant for the most popular tasks people use their computer for. It's not that no one can compete with MS; it's that there's simply no money in it any more, and only sheer momentum is what allows Microsoft to charge for Windows. But even then, most people don't pay directly for it anyhow; they get it with their computer, and never see the costs.

    No, we're not complicit in supporting Microsoft; we're complicit in not going out and buying OSes of any kind.

    1. Re:What a load of bull. by baptiste · · Score: 2
      Windows is the only OS that anyone will pay money for nowadays

      Hardly anyone PAYs for an OS these days. The bulk of the OS licenses come from new hardware. All BeOS wanted was to allow OEMs to install BeOS on teh hard drive - didn't cost the OEMs anything. In fact it gave them somethign else to tell teh customer (Not only do you get WIndows, but you also get...) It got BeOS some exposure.

      Yes, the OS as a market in terms of buying the OS is a joke, but the cash cow (at least according to Gates) will be the services the OS offers. So again, we're still beholden to MS. If some other OS vendor develops and OS witha service fee centric architecture, they STILL can't compete in the new service market that is evolving.

    2. Re:What a load of bull. by baptiste · · Score: 2
      Be totally honest, would you have preferred to buy a computer with BeOS installed or without it? If you plan on using something other than Windows and/or BeOS, consider it a tossup...

      Personally, I think it would have been kinda cool - heck if I'd have had the money I probably would have bought a neXt cube way back. So yes, I probably would have purchased a PC with Windoze and BeOS (or Darwin if Apple ever got that brave) Back in 98, I'm not sure because drives still weren't that big. But good lord, PCs are shipping with 40-75GB hard drives! That is HUGE! So slicing off 5GB for each OS and using the other(s) for data would be sweet and I wouldn't have worried about the secondary OS using up a little space. Again, think about it. Joe 6-pack consumer doesn't have a clue. But if Dell sells a PC with just WIndows and Gateway sells an equivalent PC in HW and price with an extra OS, the customer would probably pick the Gateway EVEN if they had no plans of trying it. But hey - joe 6-pack is getting computer literate these days - there is no denying this. So one night he tries out BeOS for kicks - he likes what he sees and gives it a whirl. He may or may not think its worth it, but imagine if 1 in 10 or even 1 in 20 tried BeOS and LIKED it. They tell a friend who tells anothe rfriend, and the OS gains users. Heck - how do you think Linux spread (and even WWW serve software) Killer app or purpose served, folks try it out and more and more people try it out.

      So being totally honest, this DID hurt Be - they could have gotten some decent exposure through the OEMs - in teh end it may not have mattered - but there's no telling. Heck - Apples still slive - who'd have thought?

  14. Re:BeOS by jfunk · · Score: 2
    BTW, I know this will seem incredibly petty and shallow, but IMHO the real reason BeOS didn't take off was C++.


    Not only petty and shallow, but totally wrong as well.

    Are you trying to tell me that Microsoft doesn't use C++?

    Lemme guess, you're a GTK/GNOME zealot, right?

    Do you honestly think that Be would be in a better situation if they had used straight C? There are bigger things at work than the mere language of implementation.
  15. Re:But by that logic... by torpor · · Score: 2

    The point is, with competition made possible in the marketplace by this bootloader issue, those *costs of maintenance and support* would be reduced. People *will go* with the easiest to use and nicest looking operating systems around - given a *choice*.

    We'll never know. Microsoft is standing in the way.

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  16. Comment removed by account_deleted · · Score: 3, Interesting

    Comment removed based on user account deletion

  17. Re:BeOS by connorbd · · Score: 2

    BeOS was a half-assed (though excellently done, for the half an ass that was there) implementation of a great idea. What killed it in the end had a lot to do with Windows, but more I think to do with Jean-Louis Gassee's pigheadedness.

    Be was a Mac fan's toy in the beginning -- the BeBox was a PowerPC-based system that was aimed at the geek world and happened to fit into the Mac world because of PowerPC loyalty. Be was doing okay until Apple killed Mac cloning and forced Be onto the much more hostile Intel playing field (a field they didn't have to be on, IMHO -- rewriting part of the Be microkernel using Mach/MkLinux code would have been workable (if a bit shady, since it's a little tough to tell what the licensing on Mach is) and would have kept Be alive on its native platform), but Gassee &c. chose not to.

    I think Be could have made the whole thing work -- there was a Posix layer, after all, and the OS itself, though (as stated above) half-assed, was very elegant and well-implemented nevertheless. But as good a point as the bootloader issue is (and it's a damn good one -- day late and a dollar/euro/pound/yen short for bringing it up in 2001) it doesn't have much to do with Be's bright start fading slowly into obscurity.

    /Brian

  18. Re:Microsoft did everything right, and had money. by Tim+Doran · · Score: 2

    While I think you have some strong points, I've used BeOS and it was as good or better than anything I've seen from Microsoft.

    I'm afraid merit never came into play here. Their money allowed MS to develop their way into the server market with a decent product, for example, but the real advantage of their money was in strategy, not product innovation.

  19. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  20. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  21. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  22. Re:BeOS by connorbd · · Score: 2

    Simply to point out that C++ had nothing much to do with it -- the early Be community certainly didn't mind.

    /Brian

  23. Boies "technologically illiterate" by benedict · · Score: 2

    This article attacks David Boies in a footnote, saying that because he doesn't have an email address, he is "technologically illiterate".

    I heard that Boies is learning-disabled and does not read -- instead he has aides read relevant documents to him. He has an eidetic memory and doesn't forget what's dictated to him. (Interestingly, for that reason, he asks his coworkers never to tell him anything that they're not absolutely sure of.) So the comment I referenced is rather insensitive.

    --
    Ben "You have your mind on computers, it seems."
  24. Re:BeOS by baptiste · · Score: 2
    On a feature-by-feature list with Win2k, BeOS gives a very poor showing.

    So what? Its still anti-competitive. I don't care if all BeOS could do is print "Hello World" The bottom line is the hardware vendors are completely under Microsoft's thumb because of licensing issues. Think of all teh times you've heard of vendors paying BIG bucks becuase they said "Do this for us or we'll stop selling to you" I recall cases involving TOys R Us and others. This is the same cut and dried issue. Microcosft is telling OEMs they can't sell another OS alongside Windows - plain and simple. The fact that BeOS may or may not have been comparable to Windows is irrelevant. The HW OEMs are completely at Microsoft's mercy and cannot do anything Microsoft doesn't approve of.

  25. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  26. Write Judge Colleen Kollar-Kotelly by LordNimon · · Score: 5, Interesting
    According to my research, the web site for her office is http://www.dcd.uscourts.gov/. The address listed there is:

    Clerk's Office
    United States District Court for the District of Columbia
    333 Constitution Avenue, N.W.
    Washington, D.C. 20001

    I'm going to verify the address tomorrow, but in the meantime, I suggest that everyone write her a letter informing her of this issue. Tell her that any remedy she proposes for Microsoft must address the bootloader issue. Be sure to tell her, in simple terms, what this issue really is. Include the URL to the Byte article so that she can read more about it.

    --
    And the men who hold high places must be the ones who start
    To mold a new reality... closer to the heart
    1. Re:Write Judge Colleen Kollar-Kotelly by LordNimon · · Score: 2
      Ok, it's a little late, but here's my letter:

      District Court Judge Colleen Kollar-Kotelly
      United States District Court for the District of Columbia
      333 Constitution Avenue, N.W.
      Washington, D.C. 20001

      Judge Kollar-Kotelly:

      Congratulations on being appointed to the Microsoft case (United States of America v. Microsoft Corporation and State of New York, et al. v. Microsoft Corporation, Civil Action Nos. 98-1232 and 98-1233). This is a landmark case that will affect everyone who uses a personal computer.

      I have been a victim of Microsoft's illegal monopolistic practices for over ten years. In that time, Microsoft has made it very difficult for me to use alternatives to their products. In every other market, I have complete freedom of choice. Ford doesn't prevent me from buying a Honda automobile. Toshiba doesn't do anything to hinder my purchase of a Sony TV. Delta Airlines doesn't prevent Continental from flying to any airport. Yet after all this time, I still cannot purchase any IBM-compatible computer I want without Windows pre-installed.

      The Department of Justice claims that the tying of Internet Explorer (Microsoft's web browser) to Windows is the most egregious violation of their monopoly. I disagree. The real problem is the secret agreements between Microsoft and the computer vendors (e.g. Dell, Compaq, Gateway, etc.). Vendors enter into these agreements so that they can purchase Windows at a competitive price. Unfortunately, Microsoft includes special conditions in these agreements, and it is my opinion that these conditions are what make Microsoft an illegal monopoly.

      If you can, please pull up your web browser and go to

      http://www.byte.com/documents/s=1115/byt20010824s0 001/

      There, you can read an article about the boot loader issue. The boot loader is a piece of software that determines which operating system your computer loads when it is turned on. On most computers, only one operating system is installed, and the boot loader automatically and transparently loads it. However, it is possible to divide your computer's hard drive into two or more sections and have a different operating system installed in each section. In such cases, the boot loader will ask the user to choose which operating system he wants to load. This happens every time the computer is turned on.

      Microsoft's agreements with the vendors prevent them from selling a computer which provides this feature. As you can tell from the article, the company Be was willing to let vendors include their operating system, BeOS, free of charge. Computer vendors today are having a very difficult time competing against each other because their products are all very similar: IBM-compatible personal computers with the Windows operating system. Many vendors would like to ship a computer that has two operating systems, because this would help differentiate their products. A computer that had both Windows and BeOS (or Linux, which is another free operating system) would allow the customer to continue using Windows, but would also allow him to try BeOS, Linux, etc. Microsoft understands that this feature is a serious threat to their monopoly, which is why they disallow it.

      When a user purchases a copy of Windows or a computer with Windows installed, that user has to agree to a license. This license, known as an End User License Agreement (EULA), generally allows the purchaser to use his copy of Windows as he sees fit, provided he uses it only one one computer. I believe that this agreement is sufficient for the computer vendors as well, and that computer vendors should not be forced to accept more restrictive agreements just to get a lower price.

      I understand that your task in the Microsoft case is to find a remedy to their illegal monopolistic practices. Your remedy will be far more effective if it prohibits these secret agreements. The vendors should be allowed to install Windows however they see fit, with any additional software they want. They should also be allowed to remove whatever parts of Windows they don't want (such as Internet Explorer). This would put Windows (and hence Microsoft) on the same playing field as vendors of other operating systems.

      Sincerely,

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
  27. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  28. Re:To Trust or anti-Trust by Midnight+Thunder · · Score: 2

    Perhaps one of the punishments is that all contracts must be made public if so chosen by any signer?

    Or it should be that the contracts should be registered with the government and on supicion of monopoly they would be made public, with the help of a warrant.

    --
    Jumpstart the tartan drive.
  29. Re:Darwin on x86 by Midnight+Thunder · · Score: 2

    The Mac and Linux are probably the only platforms where a real competitor to MS could afford to release an Office suit. The only problem is that people have got so used the features of Office that it is hard to convince them to use an alternative. I use AppleWorks on a Mac and do miss some of the features of MS-Word - unfortunately it is true :(

    As to the Darwin issue, Apple would never consider commercialising it, because if they did they would have to support it and that's not where the want to put their resources.

    --
    Jumpstart the tartan drive.
  30. Misunderstanding economics by isomeme · · Score: 4, Insightful
    From the article:

    The only OS projects that stand a chance are open source, because they don't play by the rules of the economy.

    This is akin to saying "The only things that get off the ground are airplanes, because they don't play by the rules of gravity". Every human activity obeys the rules of economics; at its core, economics is the study of how human labor and available resources are allocated. If some people allocate their labor to produce 'free' (insert your favorite sense of that term here) software, that is an economic activity just like any other.


    A narrow view of economics which ignores volunteer labor, bartering of labor and resources, and value measures other than money will steadily diverge from the real world as this new century progresses. The net has finally allowed us to approximate the world of "perfect information" which allows the economy -- in all its many forms -- to operate at peak efficiency. To think that it will continue to do so within current market models is to profoundly miss the point.

    --
    When all you have is a hammer, everything looks like a skull.
    1. Re:Misunderstanding economics by Midnight+Thunder · · Score: 2

      True time is money which ever way you see it, unless you are a student with nothing else to do ;-)

      The one big difference is that if a company goes boom none of the software source is available for people to hack at and let live - it just disappears into the trash-heap of time. In the open source community, while you will have factions that get bored and go onto other things, you will always have someone willing to spend the time improving it, and the code will always be legally available somewhere to be improved upon.

      --
      Jumpstart the tartan drive.
    2. Re:Misunderstanding economics by (void*) · · Score: 2

      Every human activity obeys the rules of economics; at its core, economics is the study of how human labor and available resources are allocated.

      Yes, that is what economics claims as it's terrority. But that does not mean therefore that economics as it is currenly understood, explains market forces. Which economist predicted the tech stock bubble? (The bubble, not the bubble bursting. That even the man in the street knows).


      It was claimed by astrologists all over the world before that the movements of planets are absolutely important to predestigation. It turned out to be wrong.


      This is not to denigrate economists, it's much better than astrology. But the point remains - a reality check to the student of economics, to take the claims with a grain of salt. Not every piece of human behaviour is `rational' in economic terms. Is space exploration economic? If yes, why don't we do more of it? If not, why do it at all?

  31. Comment removed by account_deleted · · Score: 3, Flamebait

    Comment removed based on user account deletion

  32. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  33. support, not installation, the issue by Proud+Geek · · Score: 2

    Installing multiple OS's would be trivial. The difficulty is that they would all have to be tested and supported by the vendors. That takes time and money. The cost of putting BeOS on a machine would be much higher than the cost of an OEM license.

    Linux is much more popular than BeOS, yet Dell backed away from it on the desktop because it couldn't justify the expenses. The OEM's don't want it because it would hurt their bottom lines.

    --

    Even Slashdot wants to hide some things

  34. Responses miss the point largely! by aralin · · Score: 4, Insightful
    I read the article and its really excelent, go and read it NOW! What disappoints me is that most of the responses moded up are missing the point entirely!

    Its not about if anybody wants it, its about the possibility, the option!

    Now, lets give an example. One of things about communist countries was, that you could not travel to the western countries. Not that anybody would want to do it and after the iron curtain fell, nobody actually does since they have no money to do it, but thats not the point. Now people are FREE to do it. They have the OPTION and the RIGHT. Its about your freedoms. Microsoft restricts freedoms of the OEMs to use the competetive solutions! and thats why its bad. Its not about how many people would actually buy. You will never know when you never try. And you never try, because Microsoft said so!

    You don't give up your freedoms and your rights only because you just don't happen to have the need to exercise them!

    --
    If programs would be read like poetry, most programmers would be Vogons.
    1. Re:Responses miss the point largely! by Arandir · · Score: 2

      Microsoft restricts freedoms of the OEMs to use the competetive solutions!

      No they don't. They only offer their products at a cheaper price if you don't use a competitive solution. There was nothing whatsoever stopping any OEM from shipping dual boot Win/Be machines except those contracts that the OEM's signed with full foreknowledge of the consequences.

      "Mr. Auto Manufacturer, I will sell you these radial tires for $5 a piece if you agree not to use any other tires but mine."

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Responses miss the point largely! by aralin · · Score: 2

      Did they have any option not to sign them? Thats a question :)

      --
      If programs would be read like poetry, most programmers would be Vogons.
  35. I disagree.. by FallLine · · Score: 3, Interesting

    While I find article presents a compelling example of MS' all too common anticompetitive behavior, it does not really provide a credible explanation for BeOS' failure. BeOS may well be a superior OS, in and of itself, but that is not sufficient to attract customers. For instance, the lack of software and support can easily outweigh any benefit that any individual consumer could draw from increased stability and performance.

    In addition, I find it hard to believe that installing BeOS as a dual boot system is any greater an obstacle than the numerous other disincentives that present themselves -- especially when it is possible to design software for make the conversion riduculously simple. Dual booting means that you sacrifice useful HD space to both the partition and the OS files. You must learn how to use it. You must purchase much of the software, if it even exists, for BeOS, that you either already own or comes bundled with Windows (hardly an argument for MS), at least if you wish to use it in that capacity. You may have to contend with compatibility issues. The Cost of BeOS itself. And the lists goes on. Any one of these could be sufficient reasons NOT to use BeOS, or any other OS, without that particular form of monopolistic behavior.

    Although, MS has no reasonable excuse for its behavior, the writing was on the wall people. All Be's escapade has done is to demonstrate to some, those that believe BeOS to be a clearly superior OS, that a technically superior OS can fail. I do not understand how anyone familiar with the industry could not understand this. Certainly MS' monopoly position played a significant role in Be's demise, but moreso in other ways (e.g., the Applications && OS symbiotic relationsip--although much harder to quantify). Furthermore, even without MS' monopoly position, it is not necessarily impossible for a superior product (which is what Be is presumed to be) to fail.

  36. Possible, but not necessarily THE reason by FallLine · · Score: 2

    While I find article presents a compelling example of MS' all too common anticompetitive behavior, it does not really provide a credible explanation for BeOS' failure. BeOS may well be a superior OS, in and of itself, but that is not sufficient to attract customers. For instance, the lack of software and support can easily outweigh any benefit that any individual consumer could draw from increased stability and performance.

    In addition, I find it hard to believe that installing BeOS as a dual boot system is any greater an obstacle than the numerous other disincentives that present themselves -- especially when it is possible to design software for make the conversion riduculously simple. Dual booting means that you sacrifice useful HD space to both the partition and the OS files. You must learn how to use it. You must purchase much of the software, if it even exists, for BeOS, that you either already own or comes bundled with Windows (hardly an argument for MS), at least if you wish to use it in that capacity. You may have to contend with compatibility issues. The Cost of BeOS itself. And the lists goes on. Any one of these could be sufficient reasons NOT to use BeOS, or any other OS, without that particular form of monopolistic behavior.

    Although, MS has no reasonable excuse for its behavior, the writing was on the wall people. All Be's escapade has done is to demonstrate to some, those that believe BeOS to be a clearly superior OS, that a technically superior OS can fail. I do not understand how anyone familiar with the industry could not understand this. Certainly MS' monopoly position played a significant role in Be's demise, but moreso in other ways (e.g., the Applications && OS symbiotic relationsip--although much harder to quantify). Furthermore, even without MS' monopoly position, it is not necessarily impossible for a superior product (which is what Be is presumed to be) to fail.

  37. Why BeOS?Rter.fov120.com/gfxengine/panquake/quake1 by dvdeug · · Score: 2

    I once sat down and thought about what I was missing in Linux. BeOS had almost all of it.

    BeOS has great font support, and excellent Unicode support. It's very fast, with the main browser (NetPositive) being much faster than Netscape. It had a nice GUI and a 64-bit journaling filesystem years before Linux did. BeOS advocates always went on about how you can play 200 videos at once smoothly. It also has fairly decent POSIX support and includes BASH as the default shell.

    It was a very nice system, handicapped by a lack of applications, lack of hardware support and the other stuff that comes with being 4th in the OS market.

  38. Upgrade to BeOS for $1 by volpe · · Score: 3, Interesting

    Suppose an OEM wants to sell dual boot machines, but is afraid of Microsoft's wrath. What's to stop them from selling a computer with Windows-only pre-installed at time of sale, and offering to install BeOS afterwards for a nominal charge?

    1. Re:Upgrade to BeOS for $1 by Arandir · · Score: 2

      Actually, nothing whatsoever is stopping them from *shipping* dual boot systems at time of purchsase. Just don't sign on Microsoft's dotted line, pay a little more for Windows, then do whatever the hell you want.

      Why are we running Microsoft through the wringer on this one when it's the OEM's that voluntarily agreed in writing not to make dual boot systems? (yeah, yeah, don't answer, I know already - it's because it would all be perfectly legal if Microsoft wasn't Microsoft)

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Upgrade to BeOS for $1 by Arandir · · Score: 2

      The crux is even more basic than that. Just what is a monopoly? And how does one determine that without having to drag someone into court?

      Exclusive contracts would be legal for Microsoft if they had only 1% of the market. Legal if they had only 10%. Legal if they only had 49%.

      But would it be legal if they had 51%? 60%? 80%? 90%?

      The trouble with the antitrust laws as they are written today is that there is no objective guide as to what is a monopoly without going to court. A slap on the wrist ten years ago would have stopped Microsoft from being a monopoly today. But ten years ago their exclusive contracts weren't illegal.

      I'm not denying that Microsoft is a monopoly. I'm just pointing out that the checks we have today are woefully off base and out of touch with reality. Law that doesn't apply equally to everyone is bad law. If it's wrong for Microsoft to offer exclusive contracts, then it should be wrong for everyone else as well.

      Microsoft has done a lot of illegal things over the years. But the courts have never seen fit to do anything about them until very recently. They should have been slapped down hard for the theft of Stac code. They should have been slapped down hard for violating the Java license. They should have been slapped down hard for violating the Sporkin decree. They should have been slapped down hard every time their install deliberately overwrote another company's software. They should have been slapped down hard each and every time they reneged on an agreement with a supplier or customer. They should have been slapped down hard for consumer fraud. But no, we wait until there's no possible remedy other than disection and dissolution before we act.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  39. Re:Why the OEM agreement hasn't been leaked by (void*) · · Score: 2

    You point out a very interesting inequity in Microsoft's relation with the OEMs. If a this licensing is leaked by a disgruntled Microsoft employee, Microsoft could use this fact to punish that OEM unfairly. The OEM would be hard pressed to prove it was innocent.

  40. Be and intellectual property. by WasterDave · · Score: 3, Interesting

    There is something that runs a danger of being lost in all the noise here, indeed it probably will: Palm only purchased Be's IP assets, specifically leaving Be Inc intact and explicitly with the "rights to assert and bring certain claims and causes of action, including under antitrust laws".

    So, we could see Mr Gasee in court after all. Maybe a good time to buy Be stock :)

    Dave

    --
    I write a blog now, you should be afraid.
  41. Re:BeOS by baptiste · · Score: 2
    They aren't under Microsoft's thumb because of licensing issues. They are under the thumb of the licensing issues because their customers demand Windows. Any OEM could end their agreement at renewal time and start pumping out Linux systems alongside Windows systems (which would undoubtedly cost much more) and proceed to go out of business.

    The OEMs are at their customers' mercy, and that means no Linux machines.

    Bull - its obvious OEMs see some potential for non Windows OS as some have tried it (and yes some have stopped doing it *cough* Dell losers *cough* But custoemrs wanting Windows does NOT mean Microsoft has to forbid OEMs from giving customers a CHOICE! RIght now customers have NO CHOICE of OS so you say they demand Windows - I say they never had a choice. So Microsoft aims to keep it that way by preventing OEMs from dual booting alternate OSes just like they prevent OEMs from having non MS ISP icons without Microsoft's. Microsoft has a monopoly and they use that monopoly to threaten OEMs into doing what they want (Sure - try dual booting BeOS - We'll drop your license - you can't install WIndows and you'll go bakrupt) That, AC, is a Monopoly and its illegal for obvious reasons.

  42. Actually by A_Non_Moose · · Score: 2, Informative

    I've found windows to be very useful for all my dual booting needs...I have found it to be one of the best hardware detection utilities, ever.
    It helped me to get my slackware box setup and running just perfect.

    Moose.

    The above paragraph contains humor and sarcasm, which has been known in the state of California to cause confusion in certain readerships.

    --
    Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
  43. Double Plus Ungood by jdcook · · Score: 5, Informative
    "No, its not illegal! Even for a monopoly! Exclusive contracts are legal even for a monopoly!"

    Your use of the word "are" is misleading. It may be legal for a monopolist to enter into an exclusive contract. Then again, it may not. The question turns on specific facts. A monopoly, as the article points out, is not illegal in and of itself. However, a monopolist may not use its monopoly power to compete unfairly.

    "This did nothing to stop competiton, except for one specific form of it.

    Oh, well why didn't you say so? I hadn't realized that Microsoft's secret OEM licensing agreement didn't do anything except for the stuff that it did. I fell much better now.

    "It wasnt brought up because its not illegal! The Sherman Act doesn't regulate free trade, it regulates monopolies trying to use its monopoly power to expand into new markets. Period. This isnt a new market. This is the preservation of an existing market."

    The Sherman Act is the first piece of U.S. antitrust law. Not the only piece. It is supplemented by the Clayton Act amongst others. The Clayton Act says, in relevant part:

    "It shall be unlawful for any person engaged in commerce, in the course of such commerce, to lease or make a sale or contract for sale of goods, wares, merchandise, machinery, supplies, or other commodities, whether patented or unpatented, for use, consumption, or resale within the United States or any Territory thereof or the District of Columbia or any insular possession or other place under the jurisdiction of the United States, or fix a price charged therefor, or discount from, or rebate upon, such price, on the condition, agreement, or understanding that the lessee or purchaser thereof shall not use or deal in the goods, wares, merchandise, machinery, supplies, or other commodities of a competitor or competitors of the lessor or seller, where the effect of such lease, sale, or contract for sale or such condition, agreement, or understanding may be to substantially lessen competition or tend to create a monopoly in any line of commerce."

    "Unlawful" is typically considered synonymous with "illegal." Just an FYI since you don't seem to think that forcing hardware vendors to only use MS OS products in a box if they use any MS OS products in that box tends to create a monopoly in any line of commerce.

    In any event, a monopolist is not supposed to be able to use their power to preserve their monopoly. They are supposed to get the monopoly in the first place because the market rewarded their innovation or service or pricing or something. But they have to be able to lose that monopoly. That's what free trade is all about. It's not the monopolists freedom to shove some spray-painted turd down your throat. It's the customer's freedom to decide that today, I don't want to swallow a turd but would rather eat a nice apple fritter from Bob's Donuts in San Francisco. (mmmmmmmm . . . Bob's . . .)

    "Anyone of the large vendors could go head to head with MS any day of the week. IBM was prepared to do it, but chickened out at the last second. Compaq had at the time revenues easily topping that of MS. Dell is a freaking-gigantic monolith."

    You say that CPQ had revenues easilly topping those of MSFT at the time. What time? It matters. And revenues aren't profits. Look at telcos if you don't understand that. But if any of the big hardware companies could do it, and if it would have been advantageous to them to do it (which you don't say but I assume you agree with since you say that MSFT was protecting their market by using their monopoly power), why didn't they do it? What does your libertarian philosophy tell you about why a company doesn't do something that would give them advantages in the market? Maybe because they couldn't do it? Or are they all just commies?

    "They didnt go against MS for two reasons: first, it was easier not to, and the easy road is often the most attractive. Second, no one gives a shit about your alternate operating systems. MS had the hardware vendors by the balls because people didnt have any tolerance for other OS's. Ask Apple how the mid 1990's was for sales. People wanted Windows, Windows, Windows."

    If MSFT had the OEMs by the balls because nobody wanted an alternate OS, why does it require OEMs to enter into this "trade secret" license agreement? Maybe because consumer choice can only hurt it? You say that it was easier for the OEMs to not fight MS. But if your opponent is going to grab you by the balls and squeeze, how much "harder" is fighting? Unless your opponent will kill you instead. Hmmm.

    I agree with one thing, people do find the easy road attractive. Maybe that's why they parrot libertarian nonsense about how certain choices of certain classes of people are the ne plus ultra of freedom rather than actually thinking.

    --
    Q:How many libertarians does it take to stop a Panzer division? A:None. Obviously market forces will take care of it.
    1. Re:Double Plus Ungood by (void*) · · Score: 2

      Second, the question of whether MS is a monopoly. Ask yourself, is there more competition is desktop OS' today than ten years ago? How is that so if MS is a monopoly? Its not.


      Yes, there is more competition. From Linux (counting only x86 platforms). The point that the BeOS guy makes remains - technically superior OSes never had a chance to penetrate the market, all thanks to MS's anticompetitive practices.

    2. Re:Double Plus Ungood by Malcontent · · Score: 2

      "I can live with that statement so long as you can live with the fact that MS isnt a monopoly, and therefore thier anticompetitive tactics are legal."

      Wow man what planet do you live in. In my planet a trial was held and Microsoft was found to be a monopolist. They were also found to have abused that monopoly. MS appealed and an appelate court also found MS to be a monopoly and also found MS to have abused that monopoly and ordered the lower court to punish MS appropriately.

      How can pu possibly make the argument that MS is not a monopoly when they have over 90% of the computer market and they were judged to be so by the courts.
      Your sense of denial is stunning.

      --

      War is necrophilia.

    3. Re:Double Plus Ungood by Watts+Martin · · Score: 2

      While this is a late entry into this argument, you--and your opponents--seem to forget that Microsoft is not being targeted for being a monopoly, they are being targeted for anti-trust violations. Being a monopoly is legal. Using the power that being a monopoly gives you to strongarm your way into dominating other markets is not.

      Personally, I'm dubious about the idea that Microsoft is technically a monopoly to start with, but I certainly agree with Scot Hacker's contention that the bootloader is a more serious issue than browser integration. It isn't an anti-trust issue--it's a prior restraint of trade issue.

      Of course, I've been dubious for a while about whether the common supposition that "less regulation = more competition" always holds true. If it was illegal for a vendor to dictate the relationships OEMs have with other vendors, this provides more freedom for the OEMs. Is the vendor's freedom reduced by the inability to say "deal only with me or don't deal with anyone at all"? Sure--to the same degree that a street gang's freedom is reduced by the cops busting them for forcing "protection" on neighborhood businesses. I'm sorry, I just don't think Adam Smith would consider "my way or the highway" to be the Invisible Hand at work.

    4. Re:Double Plus Ungood by Znork · · Score: 2

      Discount Linux. Linux isnt competition in any ordinary market sense. Linux isnt bound by the restraints of actually having to work within an economic context, which any ordinary competitor would be. This, of course, is the only reason that Linux has not and never will go the same way as Be and OS/2. Linux is rather the proof that competition in the x86 market is dead and extinct. You can neither make money from nor finance development of an OS that competes with MS, so the only even remotely successful competition is Linux, which needs none of those factors for its survival.

      Can you secure financing to write a new proprietary OS to compete in the x86 market segment, enter the market and compete? No. No way, no how, ever. Not unless MS is severely restrained.

    5. Re:Double Plus Ungood by jdcook · · Score: 3, Informative
      "I was considering not responding to you, primarily due to the ad hoc attacks you insist on making to me."

      "Ad hoc" means "for this" in Latin and is most often used in conjunction with committees. "Ad hominem" means "to the person" and is presumably what you meant to say. I don't think I engae in any ad hominem attacks until the very end (though I get close to the edge a few times before that). But in general, you're right. Frankly, the things you write are often so extreme and wrong-headed that I have a visceral reaction to them.

      "First, the "trade secret" agreements MS made with hardware OEM's is legal, even if they are a monopoly. For more information this, please see the SCOTUS decision on "INTERNATIONAL BUSINESS MACHINES CORP. v. UNITED STATES, 298 U.S. 131 (1936)". It clearly defines the ability of monopolists to protect the exclusivity of distribution, even if it defeats some or all competitive efforts."

      Have you ever actually read this decision? It stands for almost the exact opposite proposition. In that case, IBM leased card reading machines. The lease contracts contained a provision that required the lessee to only use IBM-supplied punch cards. The U.S. government sued. The trial court found, ta da!, a violation of the same section of the Clayton Act as the one I mentioned before. IBM contended it had patents that, collectively, gave it a monopoly to manufacture, vend and use the cards. In its review, the Supreme Court thought the patent claim was weak but didn't rule against IBM on those grounds. Instead, the court said:

      "We rest it rather on the language of 3 of the Clayton Act which expressly makes tying clauses unlawful, whether the machine leased is "patented or unpatented." The section does not purport to curtail the patent monopoly of the lessor or to restrict its protection by suit for infringement. But it does in terms deny to the lessor of a patented, as well as of an unpatented machine, the benefit of any condition or agreement that the lessee shall not use the supplies of a competitor. The only purpose or effect of the tying clause, so far as it could be effectively applied to patented articles, is either to prevent the use, by a lessee, of the product of a competitor of the lessor, where the lessor's patent, prima facie, embraces that product, and thus avoid judicial review of the patent, or else to compel its examination in every suit brought to set aside the tying clause, although the suit could usually result in no binding adjudication as to the validity of the patent, since infringement would not be in issue. The phrase "whether patented or unpatented" would seem well chosen to foreclose the possibility of either alternative."

      The Court concluded:

      The Clayton Act names no exception to its prohibition of monopolistic tying clauses. Even if we are free to make an exception to its unambiguous command, we can perceive no tenable basis for an exception in favor of a condition whose substantial benefit to the lessor is the elimination of business competition and the creation of monopoly, rather than the protection of its good will, and where it does not appear that the latter can not be achieved by methods which do not tend to monopoly and are not otherwise unlawful.

      This case has not been reversed. Your analysis of it is simply wrong. I think you were trying an argumentum ab auctoritate, or argument from authority, and counting on people to not actually know.

      "Ask yourself, is there more competition is desktop OS' today than ten years ago? How is that so if MS is a monopoly? Its not."

      A better question would be: "Is there more or less competition in the desktop OS market today than there would have been if Microsoft had not used its dominant market position (~90%) to force OEMs to not sell dual-boot machines?" It has been repeatedly shown in court that a company can lose market share or prices can come down and still be violating the antitrust laws. If they are using monopoly power to slow the losses, that's illegal.

      "Third, why didnt hardware vendors challenge MS? Serveral reasons. First, people dont have any reason to not use Windows. Second, application vendors are cool to the idea of new platforms. Third, it is a risky proposition, where MS is a solid established equation. If they struck on their own they might make more, or they might lose big time. Sticking with MS was a measure of their faith in MS to deliver. Fourth, they are hardware vendors, and as Apple can clearly attest to, doing the "whole" package of hardware and software isn't easy by a long shot. Fifth, consumers by and large either (a) love MS software (not incredibly uncommon) or (b) dont hate it enough to ever switch."

      I think your position here boils down to the idea that people are generally sufficiently satisfied to not switch. And you may well be right. But that is irrelevant to this discussion. Be's concern is that people never even got the chance to decide. Assume, arguendo, that Be could and would have provided the OS to major OEMs at no cost as a way of getting market share. (You know, like Internet Explorer.) Further assume that they could satisfy whatever inegration and support concerns the OEMs had. In that world, where is the risk to the OEMs? The customer gets a choice on their first time boot:

      Do you want a Microsoft Windows Only machine or do you want Microsoft Windows and BeOS machine (takes an additional 70 megabytes)?

      The customer picks and that's that. Some people say yes, some say no. But they had the choice! Hooray! Maybe no one would choose it. Maybe no one would develop for it. But the OEMs didn't have to "strike out on their own." They could have offered both if Microsoft hadn't forced them to enter into an agreement that precluded them from doing so. Also, I don't understand the "whole package" thing. Do you mean that they wouldn't want to roll their own Linux disto? Maybe so. But I imagine they could reach a satisfactory agreement with Red Hat for instance. What I don't understand is why you appear to support actions that prevent the free market from working.

      "Just because most people don't dislike MS doesn't make them a monopoly."

      True. It's the ~90% share of the desktop OS market that makes them a monopoly. And it's using the power of that monopoly to force others to do things they wouldn't otherwise that is illegal.

      "That will conclude my remarks here right now. If you respond, try not to personally be rude or demeaning - it only hurts your position, which is actually rather strong.

      Well, like I said before, it's a visceral thing. Things you've said set me off. I'd suggest that you bone up a bit on antitrust law. I don't know a whole lot about it but you seem to lack a sufficient understanding of the statutes and case law to adequately support your position.

      --
      Q:How many libertarians does it take to stop a Panzer division? A:None. Obviously market forces will take care of it.
  44. Re:Microsoft did everything right, and had money. by Billly+Gates · · Score: 2

    First off linux is innovating faster then windows even though its still behind. Lets look at kde as an example. 2 years ago it equaled windows 2.0 and the browser resembled IE 1.0. 2 years later kde equals WindowsME and the browser is somewhere between IE 4.0 and 5.0 in terms of supported features.

    Second off innovation is dying thanks to microsoft's strangle on the wintel market. Microsoft did not invent the gui, they did not invent object oriented programing, or ide's, or the internet browser. They let other people invent them and used market forces and their monopoly to copy them and squeeze them out of the out of the market. For example for the price of one copy of visual basic, you could also get Visual C++, and foxpro, SQL server and Interdev in the form of the bundled Visual Studio. Brillant! Borland c++ is still technically ahead but because vb is popular, visual c is taking over.

    Great software is made by people and not by corporations or a group of marketers. Hiring more people can create more code but not innovation. You can hire great innovative people but usually they are told what to do by the marketing department( in the case of microsoft). Microsoft knows how to make money but not good innovative products. I believe the true innovators are college students, those who are privately funded and can do whatever they like, or those volunteering code. This is because they can be free and code whatever they like.

  45. Re:BeOS by baptiste · · Score: 2
    Not true. Many OEMs load Windows without the OEM discount (try your local PC shop, though many these days have OEM deals also).

    Right - and those are the only shops that ARE experimenting with dual-boot setups just like mentioned in teh article:

    Yes, you can get dual-boot machines at some of the smaller shops, but these are the ones that slip under Microsoft's radar, and there's no guarantee that Microsoft won't decide to take action against these vendors at some point.

    The bottom line is any large OEM cannot dual boot their systems because they will lose the OEM discount which will cost them millions of dollars in an already low margin business - thus Microsoft forces them to have ONLY single boot systems.

  46. The bootloader is not the issue by Skapare · · Score: 2

    The bootloader is not the issue. The issue is having more than one OS on the machine. And the partitions.

    First of all, who needs more than one OS? The answer is that some people do, and those reasons are generally for people who have the skills (or are learning) to install two or more systems on the same machine, and understand (or are learning) the issues they have to decide, like partitions.

    The majority of the computer using population does not need two operating systems on one machine. They just need applications that run. If we can offer them all the applications they need which run on Linux or BSD, then we can certainly suggest they run Linux or BSD instead of Windows. Then they don't need Windows. And if we make that suggestion before they buy Windows, we've saved them that money. And they can get a PC without Windows.

    Aside from the obvious market lock-in, there is another reason Microsoft would not want to have Windows co-exist with another OS. That reason is support. Who supports the software on a system when each can impact the other, not only during the installation, but also during regular operation? Support costs do go up, and the finger pointing ends up making everyone mad and no one happy. The only time dual OS systems work out is if you take responsibility for it yourself.

    Sure, I'd love it if more people knew they had a choice. But I'd never recommend to ordinary people to have a dual-OS system. It seems to be hard enough for lots of geeks to set up a multi-partition Linux system (preferring instead to have one swap partition and everything else on one big filesystem partition). And we would expect non-geeks to understand how to manage disk space between two co-resident operating systems? I think not. If someone not ready to do partitions wants to try Linux on a Windows machine, they should be using UMSDOS and LOADLIN.

    --
    now we need to go OSS in diesel cars
  47. Re:As interesting as this is... by frknfrk · · Score: 2

    I sat waiting for J2SE for 2 years. I'm still waiting. BeOS with J2SE would have been THE machine, if you added just a bit more hardware support.

    --
    The REAL sam_at_caveman_dot_org is user ID 13833.
  48. I doubt him... by sheldon · · Score: 2

    "we pretty much have to take the author's word for it (not that I doubt him). "

    Actually, I do doubt him. Can someone point to a trial transcript which claims the license is a Trade Secret?

    The DOJ clearly had access to the OEM license agreements as these were brought up in the trial with regards to modifying the OS to remove Internet Explorer.

    If this were the case, it would be evidence of exclusionary behavior that coincided with the previous consent decree preventing Microsoft from charging computer makers for DOS whether or not a computer shipped with it.

    So there I doubt him.

    Although I also agree that the DOJ lawyers were completely inept for bringing this case to trial the way they did. Browser? Oh good grief.

  49. Re:Trade secret license by (void*) · · Score: 2

    One thing MS could do, should this happen, is not to affirm that the released documents is indeed the true license. A few phone calls, and Bill could get Micheal to shut up too. Then all we would have is hearsay to go by.

  50. Re:Why oh why did they link to this drivel-story? by (void*) · · Score: 2

    It is true that the lack of response IN GENERAL is not a proof. But in many specific contexts, the lack of response make be suggestive circumstantial evidence. To only way to refute circumstantial evidence is to present real evidence, or disprove it soundly. Why is Microsoft not interested in doing so?

  51. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  52. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  53. Dual Booting == Having a mistress by Capt_Troy · · Score: 3, Funny

    My friend once told me...

    "Dual booting is like having a mistress, it's all great till they find out about one another."

    My experience (in dual booting, not mistress having) tends to agree with this.

    troy

  54. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  55. Not THAT evil. by Remote · · Score: 2

    Nothing prevents an OEM to ship computers with MS-Windows and some other OS. Now, if you want a few k OEM licenses (for wich you'd pay much less than if you bought them from a retailer) then terms are obviously different. This is business commom practice: you give someone some kind of favoured treatment and you demand some loyalty in return. Whats the point of an OEM license from an OS company viewpoint? Increase installed base, so as to make shifts to other OSs more expensive.

    MS could really make things hard for double booters. Someone correct me if I'm wrong, but this perception that a boot loader can fire up just any OS is wrong. The code in a partition boto record has to be boot loader-friendly, even if by accident. Think about this: MBR code doesn't need be interactive or offer options. One can write MBR code that leaves the processor in some funny state and write the OS partition boot code so as to count on that state or information, all 100% transparent to the user. If the user repartitions and installs a second OS and his generic boot loader of choice, this new loader has no way to know how to "deliver" the machine to this OS. Maybe one could write an "intelligent" generic boot loader that would mimick such behaviour upon detecton of the user choice, but then one would have to consider things like patents, reverse engineering, etc. Also, I'm not sure if it's possible to squeeze that much code in a MBR.

    I was told once, by a Marketing professor, that the tobacco industry considers one to be a non-smoker only 10 years after the person quits. In the meantime they call them inactive smokers. Be it true or not, I think this is why it's interesting for MS to have people *at least* double booting, as long as one partiton is Windows, for you never know...

  56. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  57. Microsoft = Nazis? In some ways, yes. by BigBlockMopar · · Score: 2, Troll

    You're being blinded by your /. drive anti-Microsoft thinking too much.

    Windows is absolutely the best desktop operating system out there. KDE and Gnome are great, but Windows is still more mature.

    There. I said it. I displayed reason. I even posted this from my Windows 2000 machine.

    However, you only need to follow the link in my .sig to see why it should be illegal to use Windows on a routable IP. And that's coming from a moderate Libertarian.

    The facts speak for themselves. Microsoft is a sick and dangerous company, like the Nazis were a sick and dangerous political entity. They're so convinced that what they're doing is the right thing for everyone that they fail to see their own shortcomings.

    Hitler thought that killing all the Jews would solve the world's problems. Bill thinks that being the only operating system will solve the world's problems. Neither one is/was anything more than obsessively convinced of the strength of a flawed vision.

    Hitler's birthday = April 20th. Gates = October 28th.

    Yahoo's Astrology section has some interesting insights into their romantic potential. Buy the happy couple some flowers. And please lace them with cyanide.

    --
    Fire and Meat. Yummy.
    1. Re:Microsoft = Nazis? In some ways, yes. by BigBlockMopar · · Score: 2

      Godwin's Law!

      Indeed.

      Heheh.

      --
      Fire and Meat. Yummy.
  58. Re:BeOS by tshak · · Score: 2

    You make good points. Although this bootloader thing is disconcerning, the reality is, I've triple booted Win2K/RHLinux/BeOS (R5), and the ease of install and hardware (especially video and sound) went from left to right - at least RH Linux PnP'd my 3COM 905c so I could attempt to download video and sound drivers. With BeOS, it was a bit of a PITA. And please don't say I'm an "idiot if I couldn't get it working." Please, the bottom line is, I stuck my win2K disk in, and

    OT: I know it's probably not the OS and more code related, but /. has had a lot more down time recently - not doing good for the whole Linux/MySQL/Perl movement :(.

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
  59. Why Be Really Died--and it Wasn't MS... by Chasing+Amy · · Score: 2

    > Second, BeOS is probably just as well supported as Linux.

    Well, the bigger issue isn't about user support, it's about hardware support. Or rather, the lack thereof.

    There was a period a couple years ago where I honestly considered going to BeOS. I started with computers in college on Macs, then my college switched to PCs, and when I graduated I wanted a Mac but even the used ones were too expensive. So I bought a used laptop running Windows 95. It died after six months and I decided to buy something new, with a warranty. Obviously it had to be a PC because new Macs, even today, are so much more expensive compared to equally-performing PCs in any given range.

    I found a local screwdriver shop with good warranty terms, but decided to buy it OS-less to save the $89 Windows license charge. I had three choices: use Linux, use Be, or pirate Windows.

    I tried Linux and at that point in time no fucking way was I going to use such a primitive interface. Remember that this was years ago, before the current KDE/GNOME/Nautilus/etc. advances. I looked at Be, and was beautiful. I liked everything I read about it and when I tried it out on a real machine it was great. But what I couldn't handle was the lack of hardware support.

    At that point in time there was exactly ONE sound card supported. There was a very short list of "fully supported" motherboards, with the lackluster assurance that motherboards from other vendors using the same chipsets "should" work but are not officially supported.

    I went ahead and borrowed a relative's shiny new Win98 CD. I knew it would work on any hardware. I knew it would support a lot of expansion over the coming years. And it has--I added a new video card and capture board, newer sound card, a DVD-ROM with a Hollywood+ hardware decoder, and other things, none of which would have been completely usable by BeOS if at all.

    Obviously things improved quite a bit over the last couple of years, but not that much compared to all the new hardware that's come out. Be never had enough developers to keep up, much less catch up. And that's important.

    It's important because, without all that nifty hardware and the software to support it, a PC is just a glorified typewriter and WebTV. Sure, not everyone uses the latest greatest video cards, or wants to interface an MP3 player or PDA, or a special sound board, or a certain DVD player, or buys a motherboard with a new chipset, or wants to use a video capture device that isn't supported by BeOS. But all you have to do is want one of those things, or one of several others, and all of a sudden the OS is not worth the trouble.

    And as everyone points out, the problem is magnified on the software side. People can buy any kind of software or game for an MS OS. They can go to Best Buy or Fry's or wherever, and know that the software will work on their PCs 99% of the time. With any alternative OS this is just not the case. But the problem is all the more immense when there's a fair chance your hardware's basic features won't even work, which was the case for a very long time with Be.

    > Enough with the focus shift BS. There have been two focus shifts in Be's history.

    Hmm...

    1) From an integrated hardware/software solution like Apple, to an alternative PPC OS vendor.

    2) From an alternative PPC OS vendor to a dual PPC/x86 alternative OS vendor.

    3) Dropping new PPC development entirely, and refocusing and redoubling x86 development. This was forced by Apple, but nonetheless happened.

    4) Let's give a basic OS away for free for home use, and offer a more complete edition for business and home users willing to pay. A small change in the codebase, but a huge shift in business strategy and, therefore, the company's focus.

    5) Roughly contemporaneously with 4 was the development of BeIA. The final focus change is the ascendance of BeIA over the desktop BeOS.

    Each of these changes required a big shift in both business strategy and/or in developer assignments and the future of the OS.

    At any rate, that's more than 2. And it's an awful lot of shifting for a very young company.

    And ultimately, BeOS wasn't doomed by Microsoft's OEM licensing. It was doomed by its inability to run a wide variety of hardware and software demanded by end users. Pointing to BeOS equivalent software isn't good enough since most end users buy their software in a real store, and that software is almost always going to run on either Windows or depending on the store Mac.

    If you really want to analyze the situation, Apple killed Be. Be never was prepared to support the wide variety of hardware commonly strewn together in the x86 market, and so while they did produce an x86 OS that ran beautifully on supported hardware, they did not have the hive full of Microsoftian development drones required to support nearly everything, or the similar army of Linux volunteers. Be made a wonderful PPC OS, and could have continued to thrive on that platform since hardware support is a far easier task. But Apple yanked the platfor out from under them by not releasing the specs.

    Of course, one has to wonder how Linux manages to run beautifully on new Macs even though Be swore it couldn't. Surely it would have been easier to develop for the new Macs, than to spread the developers thin enough to code all those new and varied x86 drivers? It does make one wonder if Apple's refusal to release their specs was more of a red herring than a real reason to make the x86 switch. I have to suspect that JLG just bit off more than he and his little company could handle, by moving to x86. They might be more alive today if they had devoted those resources to running on Macs, since as I said Linux manages just fine--not to mention *BSD, where the BSD license would have allowed wholesale lifting of code.

    So as far as I can see, either Apple killed Be by making them switch to a far more varied platform than they could support, or Be committed suicide by moving to the more varied platform when maybe they should have worked harder on continuing PPC work. Either way, it has nothing to do with Microsoft so much as it has to do with the fact that PC end users want their hardware to work with all its features enabled, and to run software they can get at the store. BGe never filled either requirement, so while elegant, it had no chance at all on the x86 desktop.

    --

    Chasing Amy
    (We all chase Amy...)
    "The more corrupt the state, the more numerous the laws"-Tacitus
  60. Re:BeOS by tshak · · Score: 2

    Speaking of down time, /. cut off my last sentance... to complete:
    ,br>

    Please, the bottom line is, I stuck my win2K disk in, and... it worked.

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
  61. Why not a bootable CD? by Dwonis · · Score: 3, Interesting
    Why doesn't an OEM make a bootable CD that resizes the FAT filesystem (which would be defragmented before shipping), install an OS image, and rewrite the boot sector? Since that would probably be 3rd party software (i.e. contract someone to develop it), and the *user* would be the one modifying the boot sequence, Microsoft would have to create a clause that states that you can't sell other operating systems at all, which is much too stupid for even Microsoft.

    <rant>
    OTOH, I don't know why the [GNU/]Linux distro vendors don't do this themselves. Parted seems to be ready - what are they waiting for?
    </rant>

    <rant more="more">
    I wonder if Debian would quit stalling my application (for almost 7 months now!) if I re-wrote the entire bloody installation system. If only I had the time...</rant>

    1. Re:Why not a bootable CD? by scrytch · · Score: 2

      Why doesn't an OEM make a bootable CD that resizes the FAT filesystem (which would be defragmented before shipping), install an OS image, and rewrite the boot sector?

      BeOS shipped with a copy of Partition Magic which did precisely that (PM moves the data itself, no need to defrag). It wouldn't matter if it ran off the CD the first time then magically off the HDD right after with no "installation" at all. People just didn't give a damn about BeOS, since it offered zero value proposition for them over their current OS.

      Microsoft would have to create a clause that states that you can't sell other operating systems at all, which is much too stupid for even Microsoft

      They had precisely such a clause, and it made them filthy rich. Well, the clause had to do with preinstallation, and no OEM wants to bother with providing an aftermarket OS for their own systems. Microsoft may be unethical, and they occasionally make bad decisions, but no one in their right mind calls them stupid.

      There are already distributions of Linux that install with just a double-click on an icon. It could be that there are other barriers to entry, and just possibly, not all wre put there by Microsoft.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  62. OS 9 and OS X by ttfkam · · Score: 2, Interesting

    To all of the folks that say that average Joe user can't deal with multiple operating systems on a system

    To all of the folks that say that average Joe user doesn't want some things from one OS and other things from a second (or third) OS

    To all of the folks that say that average Joe user would never reboot to use a different program

    I put forth some counter-examples.

    1) A pair of OSes, lauded on the fact that Joe sixpack and grandma can use them, have a dual boot option for the entire line of new computers on which they are shipped.

    2) Depending on their needs, some users spend all of their time in OS X and others spend all of their time in OS 9.x quite happily.

    -------------------

    When it comes down to it, people will accept *anything* if they don't realize that there is a choice. As soon as you are shown your choices, you will fight back when a choice is removed. Most of the people in the US do not complain because they never realized that there was a choice. Most users of Be, Linux, BSD, etc. have been shown the choice and fight back (or at least complain loudly ;-)) when one of those choices has been unfairly removed.

    Why is this so difficult to grasp? The easiest way to deprive someone of their rights is to convince them that they don't have rights in the first place. What do you think high school is for? ;-)

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  63. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  64. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  65. umm by nomadic · · Score: 2


    the know-how or courage to make an OS change.

    Courage is standing up to tanks in Tianenmen Square. Courage is entering a burning building to rescue a child. Courage is not installing a second operating system on your computer.

  66. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  67. Re:Why oh why did they link to this drivel-story? by Fred+Ferrigno · · Score: 2

    I read his book, read more than one of his articles, and actually talked with the man myself. He is a great guy. His work at BeTips was an invaluable service to the BeOS community. He's been a central figure in the BeOS community for years.

    Most of what Scot talks about in this article is not unfamiliar to the BeOS community. Nearly all of it was slowly leaked by Be employees and then later directly confirmed by Gassee. I suppose if you don't trust Be or Gassee to be honest about their negotiations, Scot's article could be seen as dubious. Truly, nearly all of it comes from Be. However, Scot openly acknowledges this and makes no bones about his own speculation.

    This isn't a news article. It's an editorial in which he offers his own opinion and explanation as to the downfall of Be and the severe lack of major OEMs shipping dual boot systems. To support this, he offers information from Be and Gassee, as well as public information from the Microsoft trial. No, he didn't get an exclusive interview from Gates. No, he doesn't have absolute support for some of his conclusions, but it's your job to evaluate those conclusions for yourself.

  68. Cost of installing Linux in bulk is minimal by Jeppe+Salvesen · · Score: 2

    All you need is to set up one system, and then make all systems a complete copy of that system. You can do this by cd-rom, network or physically copying from hard drive to hard drive.

    I would estimate that the cost of installing linux might be about 20 mins per PC - at definite most. If they streamline the operation, they would probably get down to about 5 mins per PC - boot, run install, reboot, boot from hd.

    Yes - it's that easy.

    --

    Stop the brainwash

  69. Re:Complicit? by unitron · · Score: 2

    It should have been "complicit in", not "complicit with".

    --

    I see even classic Slashdot is now pretty much unusable on dial up anymore.

  70. Would you care backup your assertions? by renoX · · Score: 2, Insightful

    >>Realistically, no hardware vendor could afford to do without Microsoft.
    > Thats bullshit as well! Anyone of the large vendors could go head to head with MS any day of the week.
    > IBM was prepared to do it, but chickened out at the last second.
    >Compaq had at the time revenues easily topping that of MS.
    >Dell is a freaking-gigantic monolith.

    Your assertion are pointless: there is a cutthroat competition between PC hardware makers!!
    The day one of those hardware makers make something which goes against Microsoft, his rebate on Microsoft software would be suppressed and instantly its PC sold with Microsoft software would be higher priced than those of its competitors: he would be dead in no time (or more likely he would have to do what Microsoft wants him to do to regain its rebate).

    So even if the revenues of the PC makers are above those of Microsoft, they are very vulnerable to Microsoft decisions because of
    1) the competition between PC makers
    2) the Microsoft monopoly
    3) the Microsoft rebates

    I really hope that Be will sue Microsoft, IMHO they have a really strong point so Be should win..

    But it's just my opinion of course, Microsoft have so much money and power that I suspect that there won't be any outcome of a trial: if they see that they will loose the trial, they would go for an out-of-court settlement..

  71. Re:BeOS by baptiste · · Score: 2
    The problem is that even if they decided to drop the Windows licensing altogether and provide only Linux (as an example of a 0 cost OS) systems, they would quickly find their profits disappear

    Again - nobody was saying OEMs wanted to just sell Linux. OEMs wanted to offer multiple operating systems on the hard drives. Windows - which customers expect and perhaps Linux or BeOS if they felt adventurous. But Microsoft forbids this. That is monopolistic. The OEMs shoudl be able to do WHATEVER they want with the hardware they build and sell. Talk about viral licensing! I have to admit that in the online services case, Microsoft has some right to dictate whats on the desktop of their OS since it IS their OS. But dual booting does NOT change the Microsoft OS ONE bit. So here you have an OS maker dictating what OEMs can and can't do with teh computers THEY pay for and build and sell. Again - THAT is monopolistic. Microsoft has no right to tell OEMs that they can't install another OS in a complete SEPARATE partition on a PC PEMs sell.

  72. Beginning of the article by Syberghost · · Score: 3, Troll

    The last 80% or so of the article has been done to death here, so I'd like to comment on the first part:

    Gee, BeOS users are stuck out in the cold, since their product is being discontinued?

    Can we revisit the claims you BeOS folks were making about it not being important that the Source be Open?

    This is why it's important, folks; no company can discontinue Linux. If RedHat dropped off the face of the Earth, my systems would continue to evolve and support new hardware.

    In two years it'll be hard for BeOS people to buy a new machine that functions properly under their OS, because the source is closed and one company can dictate whether or not it's updated.

  73. Re:Boot Loaders by tb3 · · Score: 2

    The PowerQuest stuff works great. I've had W2K, Win98, Linux (Redhat, Corel, Debian), and BeOS on my machine at the same time, and booted between them. Microsoft managed to break PartitionMagic with W2K (suprise!) so that I have to boot into Win98 to edit partitions, but apart from that there are no problems. Just keep your BootMagic Rescue disk around in case you accidentally write LILO to the wrong place :)

    --

    www.lucernesys.comHorizon: Calendar-based personal finance

  74. You are *ALL* missing the point by ch-chuck · · Score: 2

    The point isn't passionate OS flamewars, the point is that Msft claims that it won it's desktop monopoly by 'consumer choice' in the PR fluff, yet in reality it's 'trade secret' agreement with PC vendors does everything to stifle any possibility of consumers 'test driving' alternatives. I.e., what they are shouting in the courts and astroturf campaigns is, "We have a monopoly because the consumer chose the best product", but to their vendors in the backroom their lawyers are saying, "You load anything but Msft and you're history."

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  75. GRUB is easy by supabeast! · · Score: 2

    "Browser anticompetitive complaints are nothing compared to what's happening with the bootloaders since the majority of people using computers will never have the know-how or courage to make an OS change."

    If we can get people to give up on LILO and move to GRUB things will get better. Grub is incredibly easy to install and configure, and generally works better. Once all of the distros out there standardize on GRUB with LILO as the optional bootloader, multi OS machines will get much, much easier.

  76. Yes, it CAN be illegal to maintain a monopoly! by Dr.+Manhattan · · Score: 2, Informative
    The Sherman Act doesn't regulate free trade, it regulates monopolies trying to use its monopoly power to expand into new markets. Period.

    Actually, according to this primer on antitrust law, Section 2 of the Sherman Act makes it unlawful for a company to [...] maintain or acquire a monopoly position through unreasonable methods."

    The OEM contract certainly sounds unreasonable to me, but, of course, IANAL.

    --
    PHEM - party like it's 1997-2003!
  77. That's insightful? by mactari · · Score: 2, Interesting

    This is insightful? Looks like the typical "I can make any song into a song about bhang" Linuxcentric bias we're always getting fed on /.

    The article's not about Linux, nor is it about whether an OSS license would have increased the viability of BeOS. It's about an unfair, predatory license. Linux was every bit as important to this article as BeOS was in paragraph 49 of Jackson's Findings of Fact.* The article is, instead, about a predatory practice that the author, as a BeOS diehard, happened to see firsthand thanks to his relatively unique perspective -- that of a hardcore BeOS user.

    Not to say Syberghost doesn't have some insight here (he certainly does), but so does most anything written by Daisetz Teitaro Suzuki, and I don't think his works fit well in this thread either.

    In the immortal words of Walter Sobchak, "The OS isn't the issue here, Dude." Careful you don't miss the forest (MS's predatory license) for the trees (love of Linux).

    * Specifically, a blip that was tangenentially related to the issue only in that it made for a "value unladen" example to support one of the author's points.

    --

    It's all 0s and 1s. Or it's not.
  78. Re:Cretin Alert! by Pope · · Score: 2

    Be hasn't supported PPC for *years* so good luck even trying to find disk images of the last release.
    And all currently shipping Macs dual boot OS X and OS 9.2.

    --
    It doesn't mean much now, it's built for the future.
  79. It's called a "boot disk" by MadCow42 · · Score: 2
    Ok, so the boot loader doesn't give the user a choice to boot Windows or Linux. However, if you insert this neat floppy disk on boot, you get Linux instead of Windows.



    Alternatively, you could use a HD selection switch like the 'NickLock' shown here on Slashdot a few weeks back.



    There's more methods to dual boot a machine than using a single boot loader for both OS's (although that is the most convenient).


    MadCow.

    --
    I used to have a sig, but I set it free and it never came back.
  80. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  81. look at all the foolish pathetic "one-os'ers" by scrytch · · Score: 2

    ... the majority of people using computers will never have the know-how or courage
    or need
    to make an OS change.

    I can't begin to go into how insultingly patronizing this sentiment is. My father recently called and was bemoaning the state of his win98 box. Programs crashing, system utilities failing all over the place... I recommended win2k as an alternative. Nope, not Linux or BSD. He's a music freak, jazz mostly, and gets a lot of it with Morpheus. Also likes games, desktop toy stuff mostly, like simcity 3000. Frankly it wouldn't matter if Linux could run every last game and support every single soundcard in existence without hassle -- he just doesn't have a reason to run it. I've had all of one BSOD on win2k, less than the number of kernel panics I got with linux. Once you're into user application land, I see app after app after app on Linux crash with segfaults. And on the security front, I just tell him to get ZoneAlarm, something I still haven't seen anything like for Linux (maybe because the notion of user interaction with the firewall is considered heresy). All this goes double for BSD, I just don't see as many of that camp deluding themselves about viability on the desktop.

    Linux might be a workable solution for him if he had a full-time sysadmin to get basic stuff working for him. Guess it keeps families together at any rate...

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
  82. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  83. Re:Misunderstanding English by isomeme · · Score: 2

    "The economy" is the subject matter of economics. The article used the term in a sense limited to monetary valuations and capitalist exchange models, which is not the full extent of the economy, properly understood. I stand by my comments.

    --
    When all you have is a hammer, everything looks like a skull.
  84. I tend to wonder... by cr0sh · · Score: 2

    If the issue really isn't so much about the end-user not knowing how to repartition, reinstall, blah-blah - or if it really is about Microsoft keeping the users in the dark about this possibility. Let me give you an example to illustrate my point:

    When I first started using computers, I was 11 years old using a TRS-80 Color Computer 2, with a cassette drive. I learned how to program in BASIC (MS Basic, at that!) on that machine, using the manuals included. These manuals even had a full schematic in the back for the machine, showing every part used. The manuals assumed I knew nothing about computers, and took me step-by-step, into a world of programming and excitement.

    Later, when I was in Jr. High, I got a floppy drive - which gave me around 160K of room per floppy (double that if I made a "flippy"), but still no notion of a directory tree structure.

    In High School, I got a Color Computer 3, later upgraded it to 512K (I remember sitting at the kitchen table with my dad plugging in DRAMs, with a wire wrapped around the sink spigot and my arm as a grounding strap!). Still had the same floppy drive. I tried playing around with OS-9 (no, not the Mac stuff, slash kiddies, but the ultra cool multi-tasking, multi-user software for the 6809 8-bit (!!) CPU), but I couldn't grok it too well...

    Toward the end of my senior year, my parents bought me a Tandy 1400HD machine, which was a revelation in power, in a way - 768K of memory, 8MHz of speed, a 20MB hard drive - but a blue/grey screen, CGA graphics - but still nice to play with. Oh, and DOS 3.2...

    What happened was a culture shock, in regards to the file system - directories!!! It took me a little bit to get used to it, but after a few hours of reading the manual and playing, I found the flexibility great.

    Too great.

    You see, not more than a few hours after playing, I had created a sub-directory in a directory, then at the root level tried to do an 'rmdir' - well, it worked, sorta - the files were wiped, but the directory stayed! Some minutes of frantic flipping later revealed that you had to delete the files in the subdirectory first before removing the directory, otherwise you had a big problem! This was a limitation of the version of DOS that I was using...

    My heart sank - I thought I might have broke it. But I knew I didn't - everything was still working. But I didn't want that directory - in fact, I wanted things back the way they were. So I did what every budding geek who has just played with a large hard drive, a "real" OS (compared to what was on the Color Computer!), and a directory structure does - I decided to format and reinstall the OS!

    Mind you - I had never before attempted or done such a thing - EVER! But I read the manual carefully, followed the steps, inserted the floppies, formatted the hard drive, re-installed the OS and programs - and everything worked again...

    You know something? It wouldn't have been possible without having that manual. The same could be said when I first started with my Color Computers - I had a manual there.

    Today, it is a different world. You buy a computer, and you are lucky if you get a rescue CD-ROM, let alone individual CDs for the software, or a manual, or a schematic of the machine (ok, I know that last one would be impossible in today's world - and nearly useless to boot). A bunch of assumptions are made that these items would scare people off, when we know this is untrue - it didn't scare me off as a kid of 11, why would it scare an adult? Indeed, think of the manuals and such that came with 16-bit systems in the early to mid 80's - did this documentation scare off the managers and people who used these machine? NO!

    So why isn't it included in today's boxes? Even if it did "scare" some people, they would still come to view it as a resource to help them - something familiar to help them learn how to use the system, how it all fits together...

    But - it would not do Microsoft (or the clone makers, to a lesser extent) any good for the users to "gain a clue" - because it would give them a measure of power over the software and hardware distributors/manufacturers. It would give the user knowledge that would allow them to _truely_ make decisions about "where they wanted to go today".

    You know something - this is what many Linux distros offer today - and is something that I first noticed with my first real distro install of Redhat 5.2 - I got manuals again. They told how to do everything, how to install and maintain the system, and I got actual floppies and CDs with the system. I later moved to SuSE 6.3, now I used 7.2 - each one came with floppies, CDs and a manual - which is why I bought the distros - I knew what I would get.

    SuSE 7.2 does it best - the manuals for install and configuration of the system really show and help you to do it (though I did an upgrade, not a full install - it still went really smooth) - this is something that I think people would appreciate, and see what they are missing, if they really knew of the options available to them.

    Perhaps this fact is something that should be pushed in the marketing of Linux...

    --
    Reason is the Path to God - Anon
  85. Re:BeOS failed--predictably by be-fan · · Score: 2

    I agree with you 100% The problem with BeOS was never the quality of the OS, but the development model. BeOS defintely should have been open sourced, because that is the only way an OS can survive competition with Microsoft. There were several problems with BeOS later in its development, praticularly with the VM. While Linux got a VM overhaul in a couple of months, BeOS's VM didn't improve at all over the period of a year or more. If the community had had access to the source, BeOS would probably be in a very different position today, both technologically and in terms of its userbase.

    --
    A deep unwavering belief is a sure sign you're missing something...