Slashdot Mirror


First Details of Windows 7 Emerge

Some small but significant details of the next major release of Windows have emerged via a presentation at the University of Illinois by Microsoft engineer Eric Traut. His presentation focuses on an internal project called "MinWin," designed to optimize the Windows kernel to a minimum footprint, and for which will be the basis for the Windows 7 kernel.

615 comments

  1. that sounds good but.. by Chris+whatever · · Score: 2, Interesting

    But what about all that legacy crap in the Bios motherboard, when can we expect that some company will actual create a board without 15 year old technology or other obscure settings that is no longer used by anyone except maybe a 386.

    The os might load fast with a bare minimum but what about the excess baggage of hardware?

    has mac done this or is it just that the OS on a linux bas system is just plain faster.

    now i know linux fans and mac fans will say that they already knew that but can someone provide hard facts

    1. Re:that sounds good but.. by Anonymous Coward · · Score: 0, Redundant

      OS X isn't linux based.

    2. Re:that sounds good but.. by Raineer · · Score: 1, Informative

      OS X isn't linux based. Need a smaller knife to split those hairs? I don't see where anyone mentioned it was, regardless. Unix ~= Linux.
    3. Re:that sounds good but.. by _merlin · · Score: 1, Offtopic

      It's called EFI boot. The Intel-based Macs are all EFI based - no legacy BIOS necessary.

    4. Re:that sounds good but.. by falcon5768 · · Score: 5, Insightful

      One of Apples biggest wins with controlling the hardware AND the software is this very fact... they have phased out legacy equipment and software every so many years.

      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

    5. Re:that sounds good but.. by Space+cowboy · · Score: 5, Informative

      "has mac done this or is it just that the OS on a linux bas system is just plain faster"

      The implication that the Mac might have got rid of the BIOS (and hence gained speed) is tied to "a linux-based system is just plain faster". You could easily read that as suggesting the Mac is Linux-based.

      FWIW, the Mac doesn't use a BIOS, it uses EFI (Extensible Firmware Interface) these days. And it's not Linux-based either.

      Simon.

      --
      Physicists get Hadrons!
    6. Re:that sounds good but.. by CSMatt · · Score: 2, Informative

      Ditching the BIOS will only save a few seconds at best. In my experience most of the time spent waiting for Windows to be usable is not waiting for the drivers to load but waiting for all of those (mostly unnecessary) background processes to start up after logging in. And in any case those few seconds are vital if someone wants to boot from a CD. The American Megatrends BIOS in my built computer literally loads the OS almost immediately after being turned on when the quick test is used instead of a full POST. I found this so annoying that I had to actually enable the full POST along with a custom boot image to slow it down enough to be able to get those precious seconds back, which was not an easy task since I had pretty much a half-second to enter the BIOS setup.

    7. Re:that sounds good but.. by phantomfive · · Score: 5, Funny

      This is essentially exactly the same as Windows Vista except instead of removing features as they get close to the deadline, they've started out with all the features already removed. When you don't meet your expectations, lower the expectations.

      --
      Qxe4
    8. Re:that sounds good but.. by Anonymous Coward · · Score: 1, Informative

      While the grandparent post is a non-sequitur, it is a true statement. Linux != UNIX != OS X, and that isn't splitting hairs. OS X has a UNIX-like layer on top of its kernel. The kernel, however, has nothing to do with (and is nothing like) Linux. OS X has attributes which resemble Linux, but it is definitely not based on Linux.

    9. Re:that sounds good but.. by Joe+The+Dragon · · Score: 1

      What about the on board software raid bios delays in to days motherboards?

      System with real raid cards can also have HD spin up slow downs and you do not want to be spin up a lot of disks all at the same time.

    10. Re:that sounds good but.. by Rolgar · · Score: 3, Interesting

      I know this is severely outdated, but once, when I needed to reinstall '98, I didn't install my sound driver, and I was getting a incredibly fast boot, something like 20 seconds on a 650 MHz system. When I later installed the driver, my boot time went up 50 seconds to around 70. I know that in the last 8 years, a lot of time has been spent reducing the amount of time it takes to boot Windows, but I'd be interested to see what happens if people disabled some of the non-critical hardware on their machines to see what it does do to their boot times.

    11. Re:that sounds good but.. by Rod+Beauvex · · Score: 1

      Did this by any chance happen to be an ISA (and specifically, Creative) souncard? I had a bizzare problem with one on a PIII 1GHz machine with 98. Using the wavetable MIDI would lock up the system, and took a long time to boot. I had thought maybe it was a BUS timing issue, but usually that only fucks with the FM synth for programs that directly talk to it, like Adlib Track II, or the old game Populous. It was an AMI BIOS based board.

    12. Re:that sounds good but.. by Nossie · · Score: 2, Interesting

      errrr did you just pull that out of your arse?

      the linux kernel was called so by those that supported Linus Torvalds

      Torvalds never named Linux after himself, his supporters named the kernel and then the OS after him much to RMS disgust.

      Osx was based on NeXT... Next was a variation of one of the Unixes (A BSD of some variety I think?)

      So you could say OSx has more connection to Windows than it ever could to Linux (since so many Windows programs are under the BSD license.

    13. Re:that sounds good but.. by Anonymous Coward · · Score: 0

      Does the bios legacy really matter? It's only a few seconds at boot time and crams into a basically negligable amount of space in the memory map, so it seems to me that keeping it is essentially harmless. So why rock the boat and waste $unknown redesigning the wheel? Especially when certain predatory might take the opportunity to cram god-only-knows-what incompatibility, bloat, drm etc. into the gap.

    14. Re:that sounds good but.. by McFadden · · Score: 5, Informative

      Linux != UNIX != OS X
      Actually, from next Friday... Leopard gets UNIX certification Mac OS X will be officially Unix.
    15. Re:that sounds good but.. by sumdumass · · Score: 4, Informative

      I used to have a program that analyzed the boot log file from a windows 98/ME machines and pointed to anything over a set time frame. It diplayed everything in the boot log but it let you filter it to specific times, failures and all that. Often the generic devices that used system memory and processing power took the most times to load. Taking the modem out and replacing the on board stuff with good full blown cards would decrease load times enormously.

      It is possible you had a sound card that just wasn't a full blown hardware sound and off loaded a bunch of stuff onto the system's processor and memory.

      Of course the different types of boot logs on NT machines didn't work so it cannot look at XPs boot logs. I haven't found anything like it for 2000/XP either. Which really sucks because often the boot log can show all sorts of problem areas that could lead to other glitches in the OS.

    16. Re:that sounds good but.. by Anonymous Coward · · Score: 0

      No, because you need to go BACK TO MYSPACE. That completely ignorant writing style scores you no friends here. This is Slashdot.

    17. Re:that sounds good but.. by toadlife · · Score: 1

      So you could say OSx has more connection to Windows than it ever could to Linux (since so many Windows programs are under the BSD license. There are about three or four minor network utilities in Windows that are derived from BSD. I would bet Linux has far more BSD code in it than Winodws.
      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    18. Re:that sounds good but.. by jaxtherat · · Score: 0, Redundant

      Uhm no, you are thinking of GNU is not Unix...

      Linux is not an backronym, but rather is meant to loosely mean 'Linus's Unix', in the tradition of putting an X on the end of anything Unix like.

      --
      http://www.zombieapocalypse.tv/
    19. Re:that sounds good but.. by Nossie · · Score: 2, Funny

      really? well I'm not a code jockey but I tainted myself reading the 2k source code and found a large amount of the utils across the board were licensed under BSD... but that's just my mileage

    20. Re:that sounds good but.. by Nossie · · Score: 1

      long live rEFIt :D - one of the best EFI tools on the net for dualbooting.

    21. Re:that sounds good but.. by MadnessASAP · · Score: 1

      Well as long as were splitting hairs "!=" is a conditional operator so that sentence expands "If Linux is not equal to UNIX and UNIX in not equal to OSX" which I'm pretty sure is not what you were going for. Next time you might want to try "Linux ! UNIX ! OS X" but even then since ! is a boolean operator you could interpret it as saying that Linux is equal to OS X but neither are equal to UNIX ( double negative )

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    22. Re:that sounds good but.. by absoluteflatness · · Score: 1

      I was pretty sure that the "linux" name came from the folder the source was placed in. I think it was one of Linus' co-workers that just sort of chose the name on his own.

      Also, why would Richard Stallman (unless you were talking about the root mean square) be disgusted at the name of a kernel being based on the name of its creator?

      Along with your comment about "so many Windows programs being under the BSD license", I'm not really sure about the intent of your post. On the other hand, we can agree that the Linux name definitely isn't yet another recursive acronym like the GP suggested.

    23. Re:that sounds good but.. by Nossie · · Score: 1

      "and then the OS after him much to RMS disgust" << this is more what I meant about Stallman

      Although quazi officially the OS is called GNU/Linux I'd like to see how many people actually call it that outside RMS most avid supporters. I'm not suggesting people shouldn't call it GNU/Linux but accepting the fact most people are lazy and Linux is simply more catchy.

      If you've had a look through the Windows 2k source code then you'll realise that a good portion of it is BSD licensed.

    24. Re:that sounds good but.. by InvalidError · · Score: 5, Informative

      What does a BIOS do? It does POST, lets the user customize some low-level system settings and puts the system in a known state before loading the OS's (boot-)loader.

      An x86-style legacy BIOS does the same fundamental things as an x86-style EFI BIOS, the only major differences being the BIOS APIs, how the boot process is structured and the fact that EFI is not backwards-compatible on its own. Other than that, a BIOS, by any other name, is still a BIOS. EFI simply has fewer kludges and ties to legacy x86 hardware.

      BTW, a few weeks ago, I read an article about some MoBo manufacturers considering adding 512MB-2GB of flash memory to boot an embedded Linux desktop from the BIOS for disk-less web-browsing and other stuff... a BIOS with embedded Linux does not seem that far-fetched, we only need 1GB firmware hubs to plug into Intel's chipsets and hope we will not need to flash our 1GB BIOS too often.

    25. Re:that sounds good but.. by HiggsBison · · Score: 1

      really? well I'm not a code jockey but I tainted myself reading the 2k source code and ...

      La la la la ... I can't here what you're saying ... la la la la ...

      --
      My other car is a 1984 Nark Avenger.
    26. Re:that sounds good but.. by miro+f · · Score: 5, Funny

      actually you'll find that conditional operators don't expand like that. The sentence is saying "the value of Linux != UNIX is not equal to OSX. In other words, (Linux != UNIX) != OSX or (true) != OSX.

      He is clearly attempting to say that UNIX is not true, whatever that means

      --
      being vague is almost as cool as doing that other thing...
    27. Re:that sounds good but.. by Nossie · · Score: 1

      lol is that not what you call 'reverse engineering' ? when you read someones code.... describe it to someone else... and they recode what you just described?

    28. Re:that sounds good but.. by absoluteflatness · · Score: 1

      Ah. He has always been a stickler on the Linux GNU/Linux issue. I also remember that Windows has BSD-licensed portions in it, but as I remember, that stuff was mostly in places like the TCP/IP stack and other places that have been heavily rewritten of late.

    29. Re:that sounds good but.. by Daengbo · · Score: 4, Interesting

      Just yesterday I was on some site (CNET, I think) and was going to flame someone who posted that "OSX is not LIKE Unix, it IS Unix." Sure, it has BSD wedged in there over Mach, I thought, but that's not Unix. It's POSIX compliant, but not Unix. It wasn't actually based on BSD.

      Then I went to check my facts. I found this visual history, and OSX was nowhere on there. Great, I thought. I just need one more link to cement my position. Then I found the Open Group's list, and damn, I was wrong again. OSX 10.5 is Unix 03. Sucks to be me.

    30. Re:that sounds good but.. by Johannes+Laire · · Score: 1
      > actually you'll find that conditional operators don't expand like that.
      > The sentence is saying "the value of Linux != UNIX is not equal to OSX.
      > In other words, (Linux != UNIX) != OSX or (true) != OSX.

      How can you know what language it was? You can do stuff like that in Perl 6. It's somewhere in the Synopses.

    31. Re:that sounds good but.. by XdevXnull · · Score: 1

      the only major differences being the BIOS APIs Actually, there's quite a bit of legacy crap in your average bios. If you ever studied assembly programming on an x86 processor, it becomes rather apparent rather quickly. I don't recall which interrupt it was, but as just one example, the original bios that IBM shipped had a bug in one of the routines. They forgot to code a final pop into the procedure, so users had to counter-intuitively manually pop the stack after the interrupt returned. But of course, they couldn't fix the problem, because then every piece of software that used this bios routine would suddenly break. Now, 30 years later, we still have to deal with this mess.
      --
      "I'm a Laver, not a Phyto[plankton]"
    32. Re:that sounds good but.. by toadlife · · Score: 1

      Like what? ping ftp finger and telnet?

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    33. Re:that sounds good but.. by cnettel · · Score: 1

      Yes, but a modern OS doesn't use that crap. It uses some space in the flash ROM, possibly mapped into some RAM, but no call should ever use it. Just about everything should be done by drivers, so the only thing affected is the first few seconds of the boot. Those are not irrelevant, but it doesn't define the performance of the whole OS.

    34. Re:that sounds good but.. by geekinaseat · · Score: 1

      We should just call it Lignux and forget this argument ever existed. It would save a bunch of storage on the slashdot servers if nothing else.

    35. Re:that sounds good but.. by crontabminusell · · Score: 0, Troll

      "!=" is just a CompSci bastardization of the mathematical symbol that looks like an equals sign with a line through it (≠ doesn't get interpreted properly here for some reason), which means that the expression on the left does not represent the same value as the expression on the right.

      http://en.wikipedia.org/wiki/Inequation

    36. Re:that sounds good but.. by yakumo.unr · · Score: 2, Informative

      Embedded linux is happening already with some boards like the new asus p5e3

    37. Re:that sounds good but.. by Anonymous Coward · · Score: 0

      There was never an "if" anywhere in there originally. Take out the "if" you added and that says exactly what he meant.

    38. Re:that sounds good but.. by rbanffy · · Score: 1

      "they have phased out legacy equipment and software every so many years."

      I can still use a fully patched 10.4 on a beige G3. It requires some hacking to install and some patience (because, of course, the G3 is not the fastest box around), but it kind of works.

      I can't imagine running XP on a PC built 10 years ago.

    39. Re:that sounds good but.. by Anonymous Coward · · Score: 0

      You keep using that operator. I do not think it means what you think it means.

    40. Re:that sounds good but.. by Fred_A · · Score: 1

      This is essentially exactly the same as Windows Vista except instead of removing features as they get close to the deadline, they've started out with all the features already removed. When you don't meet your expectations, lower the expectations. This doesn't make sense, by doing this they just won't have any features to remove when the deadline whooshes by in a few years.
      That team must be new there.
      --

      May contain traces of nut.
      Made from the freshest electrons.
    41. Re:that sounds good but.. by snilloc · · Score: 1
      Not so improbable. At a previous job (a crap job circa 2002) my machine was a P2@266, though with probably more RAM than would have been initially installed. When I started college in the fall of 1997 the rich kids had new Pentium2s @233 and 266.

      XP ran OK if you turned off all the preview stuff and GUI animations. (Progs used most were MSOffice 2000 and Harvard Graphics 98). Most importantly it crashed a heck of a lot less than Win98.

    42. Re:that sounds good but.. by zero_offset · · Score: 1

      Back around 2001, I ran Windows 2000 with SQL Server on a 90MHz Pentium.
      It ran fairly well in 96MB of RAM.

      The biggest problem XP would have with older machines is a lack of driver support.

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

    43. Re:that sounds good but.. by Gr8Apes · · Score: 1

      It's doable, and not even that bad. :)

      I have a 96 era PPro 180 w/ an upgraded 512MB of RAM and a 6 disk RAID array of a whopping 45GB. (9GB drives...still 7200 RPM).

      I did install Win2K on that bad puppy, and it ran relatively well. Since XP can be reduced to almost 2K status by removing services etc, it should run as well, although I've not tried it as I retired that box about 5 years ago.

      --
      The cesspool just got a check and balance.
    44. Re:that sounds good but.. by Wdomburg · · Score: 1

      BTW, a few weeks ago, I read an article about some MoBo manufacturers considering adding 512MB-2GB of flash memory to boot an embedded Linux desktop from the BIOS for disk-less web-browsing and other stuff...

      Considering? Done! In stock!

      a BIOS with embedded Linux does not seem that far-fetched, we only need 1GB firmware hubs to plug into Intel's chipsets and hope we will not need to flash our 1GB BIOS too often.

      People have been replacing the traditional BIOS with Linux for about eight years now, so yeah, I would say it's feasible. :) Would make more sense to just embed a flash drive for the userspace filesystem and just put the bootstrap and kernel in the firmware proper.

    45. Re:that sounds good but.. by InvalidError · · Score: 1
      I said:

      EFI simply has fewer kludges and ties to legacy x86 hardware. You said:

      Actually, there's quite a bit of legacy crap in your average bios. Obsolete BIOS services/interrupts sound like kludges to me... and I also did call them legacy-BIOS and EFI-BIOS so I obviously implied that the legacy-BIOS had more legacy stuff in it by definition.

      Getting rid of the legacy stuff in the BIOS is one thing... but there is a whole lot more of more complex legacy stuff (logic) embedded in x86 chipsets and CPUs. Dropping hardware support for legacy stuff/kludges (remember "dos=high,umb" and what made it possible?) from the pre-MMX era could considerably simplify chipset and CPU design. The desktop market could use a re-engineered, more orthogonal x86-inspired ISA on a clean platform: it would simplify things across the board (R&D, testing, instruction decoding, compilers, etc.), reduce die sizes, reduce pipeline length, improve frequency scaling, improve IPC, improve performance-per-watt, etc. Intel failed miserably across the line with its first attempt at going clean-slate but the potential benefits are still there.

      Had Intel's Itanium plans worked out as initially planned, we would all be running on IA64 desktop hardware by now... kinda sad but seeing how IPF has turned out so far, we are better off this way for now.
    46. Re:that sounds good but.. by rbanffy · · Score: 1

      I realize I failed on my analogy because XP is a 6 year-old operating system. The real question is, can you run a 2 year-old Microsoft OS on a 10 year-old PC? Because you _can_ run a 2 year-old MacOS acceptably on a 10 year-old Macintosh that had only its hard disk and memory upgraded.

      BTW, I am sure you can run a 2 year-old Linux or BSD on a 10 year-old PC. I bet you can even run a current Linux or BSD on a 10 year old PC without any upgrade beyond filling it up with memory.

    47. Re:that sounds good but.. by Ant+P. · · Score: 1

      Not surprising. My onboard sound needed a 30MB (?!?) download for XP - and on an OEM machine at that.

    48. Re:that sounds good but.. by tepples · · Score: 1

      And in any case those few seconds are vital if someone wants to boot from a CD. If you're talking about the reaction time between turning on the power switch and pressing the button to change the preferred boot device, Apple has long had a solution for that: hold the C key (or in some models Command+Option+C+D) while powering on the machine, and the machine will prefer the optical drive over the hard disk drive. Contrariwise, in the GameCube BIOS, if you want to turn off booting from the optical drive (say to arrange files on a memory card), hold the A button while powering on the system.
    49. Re:that sounds good but.. by glenstar · · Score: 1
      We should just call it Lignux and forget this argument ever existed.

      OR... we could just call it Linux and tell all of the pedantic fucktards to shut the fuck up. No one outside of a handful of GNU people give a flying fuck about the differences between a kernel, an OS, and a desktop environment. It's a moot point and on top of that it is really, really silly. 'Linux' is the name that people know, well, Linux by and nothing you do will change that.

    50. Re:that sounds good but.. by XdevXnull · · Score: 1

      I agree with this sentiment completely. I think our disagreement was a matter of mere semantics. Actually, you are saying what I myself have been saying for years, and I imagine thousands if not millions of geeks and engineers the world over have been echoing the same sentiment as well.

      I personally was very disappointed when Apple switched over to x86. I understand why they did it though. It was more a business decision than a technical one. IBM couldn't deliver, so they moved to someone who could. I think as a whole the consumer has benefited, but I can't help feeling the longterm implications will not be quite so rosy. Even barring the "obsolete" portions of legacy support in modern x86-64 platforms, they are still built around that original conception of what Intel thought a microprocessor should be 30 years ago.

      Apple (when it switched to PPC and hell, when it switched to Intel) and Transmetta (with their inovative processor line) have both proved that legacy support doesn't have to mean you are locked in to a particular hardware breed. If the x86 processor disappeared tomorrow and was replaced with something else engineered to be efficient from the ground up, I think we would all benefit tremendously. My understanding is that most of the x86 stuff is done with microcode now, and architecturally the modern chips are more RISC-like anyways. It's just a matter of when it happens and who will reap the benefits.

      --
      "I'm a Laver, not a Phyto[plankton]"
    51. Re:that sounds good but.. by nuzak · · Score: 1

      Linus originally named it 'Freax'. The admin that hosted it thought 'Linux' was a better name.

      > Next was a variation of one of the Unixes (A BSD of some variety I think?)

      Mach. NeXT won over a lot of people for its design, and programming it in ObjC was probably all right, but boy was it braindamaged as a Unix. OSX does a lot better with Mach, largely because it shoehorns an entire BSD kernel into it instead of forcing it to run as a "personality".

      I can't think of a single Windows app Microsoft has ever shipped that's under the BSD license. It has some BSD apps with it (like FTP.EXE) but those are binaries only, certainly not distributed under the same license. What's the freaking license have to do with it anyway?

      --
      Done with slashdot, done with nerds, getting a life.
    52. Re:that sounds good but.. by zero_offset · · Score: 1

      You might be surprised. Most of the Linux distros are apparently pretty intolerant of older hardware these days. Had a friend at work who was screwing around with some older machines. (And please don't pester me for details, I have no idea or interest, he just mentioned it recently after somebody else made a comment similar to yours.)

      I suppose my first question is, why bother? You can pick up a fairly decent machine for a couple hundred bucks (particularly in comparison to a 10 year old box). Why waste time with an old machine?

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

    53. Re:that sounds good but.. by nuzak · · Score: 1

      You haven't been around long enough to remember the GNULix troll, do you? Around the same time as the whole Natalie Portman thing, I believe.

      (my slashdot uid's a fairly fresh one, I've had other accounts)

      --
      Done with slashdot, done with nerds, getting a life.
    54. Re:that sounds good but.. by Anonymous Coward · · Score: 0

      "Mac OS X will be officially Unix"

      Joining every mainframe and minicomputer IBM O/S, OpenVMS, and a host of other O/S's that are not truly "Unix". The heart and soul of Unix is now open software, beginning with the BSD mods of original Unix, through Linux, FreeBSD, etc. Apple's mountain of highly proprietary, secret source code dumped on top of a small Unix core does not constitute true "Unix".

    55. Re:that sounds good but.. by InvalidError · · Score: 1

      I agree with this sentiment completely. I think our disagreement was a matter of mere semantics. Not really, I simply have a tendency to be more verbose than necessary and branch off in variously loosely related topics.

      Even barring the "obsolete" portions of legacy support in modern x86-64 platforms, they are still built around that original conception of what Intel thought a microprocessor should be 30 years ago. RISC have become more CISC-like, CISC has become more RISC-like to the point that there is no more clear differences between the two.

      The x86(_64) ISA is ok feature-wise: it has everything any other general-purpose ISA has. The problem with it is the highly non-uniform instruction format: ~30 years ago, bits were really expensive so Intel designed the x86 ISA to be as compact as they could practically make it... and back then, they had to design the necessary circuits by hand, drawing them transistor by transistors every step of the way to create their lithography masks, makes it hard to blame them for not implementing the most optimal solution conceivable at the time.

      If the x86 processor disappeared tomorrow and was replaced with something else engineered to be efficient from the ground up, I think we would all benefit tremendously. It would not need to be completely new... most of the legacy peripheral hardware have modern equivalents and the instruction set is mostly ok. As I said in my other post, a re-engineered x86-64 ISA with all the tack-ons cleanly integrated together and improved ISA orthogonality/regularity would go a long way towards improving the situation. And since that new ISA would be very x86-64-like, legacy emulation should be possible with a moderate performance penalty.

    56. Re:that sounds good but.. by CSMatt · · Score: 1

      Well most Apple devices have slot drives, while most PCs have tray drives. It takes longer to get the tray open, closed, and the CD or DVD recognized, combined with the temporary disabling of the eject key immediately after powering on, than to just slide it into a slot drive.

      I do wish Apple would put a real eject key on their drives though.

    57. Re:that sounds good but.. by tepples · · Score: 1

      It takes longer to get the tray open, closed, and the CD or DVD recognized, combined with the temporary disabling of the eject key immediately after powering on, than to just slide it into a slot drive. That's why you boot from the hard drive, insert the CD, then restart.
    58. Re:that sounds good but.. by toddestan · · Score: 1

      Well, a 2 year old Microsoft operating system is XP SP2 and that'll run, though slowly, on 10 year old hardware without much hassle (a 10 year old PC is going to be some kind of P2). XP will install on as little as a Pentium processor and 64MB of ram, and you could get that back in 1993 if you had the money. XP will even accept a Pentium overdrive processor, meaning you could (in theory) even run XP on an some kind of upgraded 486 machine from 1989 if you really wanted to.

      I'm not sure about the minimum Vista will accept. I know it will install on a P3 with enough memory, which means a 8.5 year old PC is within reach as that's the age of the oldest P3's out there. If it will install on a P2 system (plausible, as the P2 and P3 are very similar), then you could install Vista on a PC from 1996, but I'm not sure about that.

      So basically, if you're into hacking operating systems to run on old hardware*, you can go pretty far back on the PC side of things too.

      *10.3 won't install on a biege G3 without some trickery either.

    59. Re:that sounds good but.. by CSMatt · · Score: 1

      And what if your hard drive has a virus or is otherwise undesirable for booting? Then what?

    60. Re:that sounds good but.. by tepples · · Score: 1

      And what if your hard drive has a virus or is otherwise undesirable for booting? Two things:
      • Your argument, more generally, is that booting from the hard drive will have some sort of harmful side effect. How did you determine that this is the case? Couldn't you have put the CD in the moment you determined that this is the case? If your hard drive just doesn't have a valid operating system installed, it will say "Non-system disk or disk error". At this point, you have booted without side effects; put in the CD and restart.
      • You can open the tray while the computer is powered off by inserting a straightened paperclip into the hole on the front of the drive below the tray.
    61. Re:that sounds good but.. by CSMatt · · Score: 1
      • If there's no OS on the drive than I really couldn't care whether or not I beat the idle time to get the CD in. The concern for me is if there's a virus on the machine. I've only had to deal with two viruses in my life after they hit their payload, one ancient boot sector virus that just hogged memory and one nasty modern one that corrupted files nonstop, both on my family's computer at the time. After witnessing just how nasty the second payload was, my newly developed failsafe plan at the time was to immediately shut down the machine if I find that a virus is on it. I'd then yank out the hard drive, install it in another machine which will not boot from it, and use that machine's AV to scan and remove any threats on the drive that I just stuck in. The only variation to that plan today is that instead of going through the trouble of pulling out the hard drive, I'll just boot an alternative immune OS from a LiveCD and use that to scan my drive - preferably a LiveCD that is explicitly designed for such a purpose. I dare not boot an infected drive lest the virus be in the boot sequence and subsequently take the chance to infect or destroy other files, and I dare not use the AV on the infected drive because experience tells me that said AV will not be able to help me eradicate the virus if the virus in question is on the same drive as the AV, only find it (and it may not even do that given recent reports about modern virus and worm payloads attacking the AV directly). So far I have never had to do this so I have no idea how effective it would be. I have since kept updated definitions after the last payload (the lack of which was mostly due to my arrogant parents who refused to get an AV subscription on our family machine) and have identified 5-7 viruses before they hit payload and deleted them, and by my observations I haven't yet missed any. If this is an ineffective or excessive strategy tell me now. I now have my own laptop with which I primarily use Ubuntu and Firefox in addition to updated definitions from CalmAV but a number of my files are still on my family's Windows computer and despite my efforts to secure their machine with updated Windows patches and AV definitions I don't trust them to make wise security decisions.
      • Oh I'm well aware of that, but it's a pain in the ass do have to do so given the amount of times I boot from a CD. In my experience paper clips make poor poking rods because they are so flimsy and can't withstand the stress of having to manually push a motor that well. That's probably why often times a more sturdy rod is included with the retail purchase of an optical drive. These are much more efficient in getting that drive open, but not only do I find that I lose the things often (which is odd because I know that I always put them back in the same place so I'm assuming one of my idiot family members is doing this - if you know what they are called and where I can purchase them separately that would be very helpful) but I really don't see the efficiency of having to do this every time I want to boot from the CD drive. The few seconds of idleness is more efficient to me than inserting the CD and then killing the hard drive's boot process by hitting the reset button, assuming that I have the fortune to have a reset button at all. And back in the pre-journaling days this method could have caused drive corruption.
    62. Re:that sounds good but.. by andreyw · · Score: 1

      I ran XP fine on a 200Mhz PPro. Ran better than 2k on same box. So, FUD.

  2. Rinse, Repeat by orkysoft · · Score: 5, Interesting

    So Microsoft tells something about the next version of Windows not long after the people have noticed that their current version isn't all that it's made up to be?

    --

    I suffer from attention surplus disorder.
    1. Re:Rinse, Repeat by ozmanjusri · · Score: 5, Insightful
      Why is this modded troll?

      Microsoft are the kings of targeted vapourware.

      They spent most of the '90s poisoning the well for their competitors with this tactic. What makes you think they're not doing the same thing again?

      --
      "I've got more toys than Teruhisa Kitahara."
    2. Re:Rinse, Repeat by Anonymous Coward · · Score: 0

      Wow, an article with not one single example of the supposed behaviour cited. That's got to be believable!

    3. Re:Rinse, Repeat by ozmanjusri · · Score: 2, Informative
      --
      "I've got more toys than Teruhisa Kitahara."
    4. Re:Rinse, Repeat by Anonymous Coward · · Score: 0

      Actually, when you look at the timing, it's just a pathetic attempt to steal thunder from Ubuntu. Period.

    5. Re:Rinse, Repeat by heinousjay · · Score: 1

      That would be more like stealing a hand from a clap.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    6. Re:Rinse, Repeat by cyber-dragon.net · · Score: 1

      And oddly the week Apple announces Leopard?
      Sounds a lot like "No no... don't give up on Vista we will fix it in the next version we promise"
      Didn't we go through this with ME?

    7. Re:Rinse, Repeat by Anonymous Coward · · Score: 0

      Yea, smallest kernel possible, 5,000 bloatware MS apps on top of that, no way to customize by default install disk, windows lite makers go on, the cycle continues.

      MS wouldn't know how to produce unbloated software if they got paid to.

    8. Re:Rinse, Repeat by 2ms · · Score: 0, Flamebait

      And doing so as if Vista was even competitive with the first version of OS X from 6 years ago.

    9. Re:Rinse, Repeat by ozmanjusri · · Score: 2, Informative
      Yep. Business as usual...

      Cairo:
      1. Announced in 1991 to distract from the lack of anything dramatically new in Windows 3.0.
      2. Expected in 1994. Pushed to late 1995, pushed to late 1996, intended to debut in 1997. Changed to a vision.
      3. Core features dropped. Ended up as polish on the existing Windows 3.0: Windows 95.
      Longhorn:
      1. Announced in 2001 to distract from the lack of anything dramatically new in Windows XP.
      2. Expected in 2003. Pushed to 2004, 2005, pushed to late 2006, intended to debut in 2007.
      3. Core features dropped. Ends up as polish on the existing Windows XP: Windows Vista.
      Windows 7:
      1. Announced in 2008 to distract from the lack of anything dramatically new in Windows Vista.
      2. Expected in 2010. Pushed to 2014, 2015, pushed to late 2016, intended to debut in 2017.
      3. Core features dropped. Ends up as polish on the existing Windows Vista: Windows 7.

      Fraud as a Business Plan The magic of the Internet is helping to point out the tragic fallacy of believing in Microsoft's promises. Microsoft assures us that it won't ever slip half a decade between operating systems again, but what about the fact that that's all it has ever done? http://www.roughlydrafted.com/RD/Q4.06/4E2A8848-5738-45B1-A659-AD7473899D7D.html
      --
      "I've got more toys than Teruhisa Kitahara."
    10. Re:Rinse, Repeat by Daengbo · · Score: 1

      Ubuntu released today and OSX is releasing in about a week. The story seems to be timed quite well.

    11. Re:Rinse, Repeat by richie2000 · · Score: 1

      Didn't we go through this with ME? We went through this with fucking (job-related) DOS 1 point bloody (job-related) 0.
      --
      Money for nothing, pix for free
    12. Re:Rinse, Repeat by darthflo · · Score: 1

      1: "Core features dropped. Ends up as polish on the existing Windows XP: Windows Vista." Would you mind telling me exactly which Core features we're talking about? I recall WinFS being quoted rather often as a dropped feature, but if you actually understand what WinFS would've been all about (indexing, SQL-style add-on to NTFS in order to quicken up searching), you might have noticed Windows Desktop Search doing kindof everything that WinFS promised. 2: What is this lack of features in Windows XP you're talking about? IIRC it's considered to be (one of) the most enterprise-friendly and (if configured acceptably) rock solid OS. It was no 180 turn from anything before, but it did most everything right and introduced a lot of possibilities to Active Directory admins. 3: Reading and/or citing RoughlyDrafted does not make your post appear informed or unbiased in any way. Daniel Eran Dilger, the person responsible for that blog is one of the most well-known, fanatic Apple-fanboys out there. I'm pretty sure you won't be able to find a single post which isn't either glorifying Apple or attacking Microsoft (most posts actually are both).

    13. Re:Rinse, Repeat by Anonymous Coward · · Score: 1

      Steal the thunder from Ubuntu? If by 'steal' you mean 'completely drown out', and by 'ubuntus thunder' you mean 'damp wet farting sound', and by 'pathetic' you mean 'inevitable', and by 'timing' you mean 'by coincidence', then yes, you're probably right!

    14. Re:Rinse, Repeat by dhavleak · · Score: 3, Insightful

      Somebody was already kind enough to give us a link to the roughlydrafted article. Oh wait -- that was you!. Of course that article is still not worth the disk space it's saved on for very obvious reasons.

      But wait, we have more evidence here -- the infamous google test. Did you even read some of the nonsense that popped up? The second result from google was that roughly drafted nonsense. Plus, I just googled "slashdot africa" and got 5.4 million results back, which means.. well, I'm not sure what it means other than the fact that your google search is meaningless.

      And then you link to some article that uses some incredibly convoluted logic to claim that MS is one of the worst oppressors of the African American community?? Have you absolutely no conscience? How do you get to the point where your hatred blinds you to this extent? I'm really curious to know. I mean, there are wars going on that could have been avoided (Iraq springs to mind), pockets of racists getting away with just anything they want to (Jena 6), desperate poverty in the third world, and many more things that are worth this kind of passionate hatred. I'm really curious to know what MS did that pissed you off to this extent.

    15. Re:Rinse, Repeat by GPL+Apostate · · Score: 2, Funny

      Somebody probably threw a chair at him when he was a small child.

      That, or he feels Microsoft is a good example of the root cause of a lot of the problems the world faces.

      Your psychobabble ridicule method follows the pattern pioneered by the Stalinists, by the way. Address your opponents like they're mentally unstable, and their angst is a psychological problem (Stalin took it further by institutionalizing them- you don't have that power at the moment.)

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    16. Re:Rinse, Repeat by GPL+Apostate · · Score: 1

      Windows Desktop Search

      This is a little bit of a branching-off rant, but WTF is it with Microsoft's 'search' technology. I used to be able to hit and search a folder. Now it brings up a bunch of bullshit and nonsense about searching the fricking Web. Did the 'Google Competition' cause Microsoft to again completely lose direction in their technology, the way that Netscape did in the past, where Microsoft turned their whole product into a competitor with Netscape (i.e. Windows Explorer ceased to be about the PC and became 'one-big-web-browser')??

      I am talking about how the search used to pop up fast and be useful on your machine in Windows 2000 and earlier and how it turned into a processor-cycling kludge in XP and later, btw.

      (what's your salary at Microsoft, btw?)

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    17. Re:Rinse, Repeat by dhavleak · · Score: 1

      Somebody probably threw a chair at him when he was a small child. That's pretty funny :)

      That, or he feels Microsoft is a good example of the root cause of a lot of the problems the world faces. I really didn't see that kind of depth in his posts. That's an interesting thought though.

      Your psychobabble ridicule method follows the pattern pioneered by the Stalinists, by the way. Address your opponents like they're mentally unstable, and their angst is a psychological problem (Stalin took it further by institutionalizing them- you don't have that power at the moment.) Aw c'mon man -- did you see the links he had posted to? Alright, I'm still processing what you said here -- I guess that last paragraph was a bit unnecessary. It was not untrue, but did not necessarily add anything to the dialog.
    18. Re:Rinse, Repeat by darthflo · · Score: 1

      I used to be able to hit and search a folder.
      Heh. If you're using Office 2007 (especially Outlook), you might be screwed a bit. I think you can turn off the "Desktop search instead of normal folder search" somewhere, but luckily (:)) haven't got an XP box handy here. If you aren't using the Desktop search, uninstall it. You're reading Slashdot, so you ought to know how to uninstall a normal piece of software.
      Then there's this fucking Dog. Opening a Search Dialog, clicking "Change Preferences" and "Disable Dog" (aka "Without an Animated Screen Character") will help with that.

      (what's your salary at Microsoft, btw?)
      As far as I know most Microsofties are forced to use Vista machines. So I ain't gonna work there ;) (and by "work" I mean "be hired by", so no, I don't collect any MSFT paychecks, salaries or discounts)
    19. Re:Rinse, Repeat by ozmanjusri · · Score: 1
      Somebody was already kind enough to give us a link to the roughlydrafted article. Oh wait -- that was you!.

      Check the times. This was posted first, the one you're quoting second. I'm happy to recycle.

      But wait, we have more evidence here -- the infamous google test.

      I lived, worked and developed software through the era. I did the Google post to show the AC how dumb it was to try to revise history.

      I guess you're still trying. Good luck with that, 'cause theres plenty of us with memories intact.

      --
      "I've got more toys than Teruhisa Kitahara."
    20. Re:Rinse, Repeat by Anonymous Coward · · Score: 0

      but does it run on linux?

    21. Re:Rinse, Repeat by Anonymous Coward · · Score: 0

      What makes you think they're not doing the same thing again?

      Naive Optimism?

      They saw how much code it took write Vista, saw how it turned out, and had 'what alcoholics refer to as a moment of clarity'. A "Perhaps we should go in the opposite direction with the next one", moment. Smaller, efficient, ugh.... stable, codebase.

    22. Re:Rinse, Repeat by dhavleak · · Score: 1

      Check the times. This was posted first, the one you're quoting second. I'm happy to recycle. The order makes no difference. Roughly drafted is still an utterly pointless site with, lies, untruths, half-truths, revisions etc. on it. Linking to that article twice (or even once), is absolutely pointless.
       

      I lived, worked and developed software through the era. I did the Google post to show the AC how dumb it was to try to revise history. That's the point! The google post doesn't show anything. It comes up with stuff like the roughly drafted article, which means absolutely nothing. Seriously, if you lived and developed software through the era, you of all people should know that there is nothing that makes sense in that article.
       

      I guess you're still trying. Good luck with that, 'cause theres plenty of us with memories intact. It's the other way around. Honestly, I'm not even an MS supporter. There's plenty of areas where I'll give them crap. You won't catch me defending them when for, say, Zunes not being PlaysForSure compatible (just pulling out some example at random). But the way the conversation on /. constantly gets skewed and constantly degenerates to the same "microsoft sucks, windows is insecure, linux rules, apple rules" nonsense has frankly gotten really annoying. TFA was about information for Windows 7. I'm interested in reading what people have to say about that (positive or negative), but it's impossible to even find such comments when they constantly get drowned out by posts like yours. And seriously man -- roughly drafted? And the article accusing MS of being a main oppressor of African Americans?? Your original point might have had some merit (highlighting a bait-and-switch or vaporware strategy) but it got completely discredited with those links.
    23. Re:Rinse, Repeat by ozmanjusri · · Score: 1
      Honestly, I'm not even an MS supporter.

      Anyone who is inclined to believe this, please check dhavleak's posting history.

      --
      "I've got more toys than Teruhisa Kitahara."
    24. Re:Rinse, Repeat by dhavleak · · Score: 1

      Honestly, I'm not even an MS supporter.

      Anyone who is inclined to believe this, please check dhavleak's posting history. Yes, please do. In my entire posting history you won't find the kind of disinformation you posted in this thread alone. You can't defend your posts when I call BS on them so this is your response?
  3. Size matters by Skiron · · Score: 5, Funny

    "Windows kernel to a minimum footprint"

    It depends if you have size 24" feet (MS) or 8" feet like real normal OS's. No matter how big the foot, you can only reduce your footprint to the smallest size of the foot.

    So that, as far as I am concerned, is a nebulous comment intended to fool the press and others that still believe every MS 'press release' they spew out.

    1. Re:Size matters by Cozminsky · · Score: 1

      I was under the impression that they'd standardized the foot at 12".

    2. Re:Size matters by rasputin465 · · Score: 1

      well you know what they say about kernels with big feet....

  4. Lesson in MS Counting by Prien715 · · Score: 5, Funny

    Apparently it goes:

    2, 3, 95, 98, ME, XP, Vista, 7!

    No wonder kids have so much trouble at math....

    --
    -- Political fascism requires a Fuhrer.
    1. Re:Lesson in MS Counting by mblase · · Score: 1

      Apparently it goes: 2, 3, 95, 98, ME, XP, Vista, 7!
      I'm assuming that Win98 and WinME are considered updates of Win95, rather than upgrades. I know that's how I thought of them.
    2. Re:Lesson in MS Counting by Cowclops · · Score: 3, Informative

      3 = 3 9x = 4 2k/xp = 5 vista = 6 7 = 7 Nuff said.

    3. Re:Lesson in MS Counting by truthsearch · · Score: 5, Funny

      3 = 3 9x = 4 2k/xp = 5 vista = 6 7 = 7

      Nuff said.

      No, not really. That equation actually makes sense to you? Are you one of the Microsoft Excel developers?

    4. Re:Lesson in MS Counting by Anonymous Coward · · Score: 5, Informative

      Actually, the proper lineage is:
      Windows NT 4, Windows 2000 (NT 5), Windows XP (NT 5.1), Vista (NT 6), 'Windows 7' (NT 7)

    5. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0
      2, 3, 95, 98, ME, XP, Vista, 7!

      more like

      1 = 2

      2 = 3

      3 = 95

      4 = 98

      5 = ME

      6 = 2000, XP and Vista! I New it!!!

      7 = windows new

    6. Re:Lesson in MS Counting by luchaugh · · Score: 1

      Wasn't ME just 98 with a few cosmetic changes? Wouldn't Win2K be more appropriate between 98 and XP?

    7. Re:Lesson in MS Counting by guardian653dave · · Score: 1

      enjoy http://en.wikipedia.org/wiki/Comparison_of_Windows_versions

      Though honestly I remembered them all... honest :)

      --
      God's in his heaven-All's right with the world. Karma=Bad ? F*ck that
    8. Re:Lesson in MS Counting by jkrise · · Score: 5, Funny

      2, 3, 95, 98, ME, XP, Vista, 7

      Oh... it's worse in Excel 2007;

      65533, 65534, 65535, 100000, 100000, 65538, 65539.. and so on!

      Maybe there's some nice pattern too?

      --
      If you keep throwing chairs, one day you'll break windows....
    9. Re:Lesson in MS Counting by freakyfreak2 · · Score: 1

      The current Consumer windows is built from the Windows NT line, not the original Windows line.
      Since Windows 3.1 was all the rage at the time NT debuted as Windows NT 3.1. Then came 4, 2000(5), XP (6) and next will be 7

      http://en.wikipedia.org/wiki/Windows_NT#Releases

    10. Re:Lesson in MS Counting by imemyself · · Score: 1

      The first version of the Windows NT kernel was 3.1 (or 3.5, I don't remember). It started there instead of 1 because the non-NT OS's versions numbers were around there at the time (Windows 3.1). Windows NT 4 was the next major version of the NT kernel. Windows 2000 came with the NT 5.0 kernel. XP was 5.1, and Windows 2003 Server was 5.2. Windows Vista is 6.0 and I *think* that Windows Server 2008 is 6.1. So, other than starting it at 3.1 instead of 1, it is fairly straight-forward. They increment .1 for minor releases (as far as the actual kernel is concerned) and 1 for major releases/changes. Windows 1, 2, 3/3.11, and Windows 95/98/Me are an entirely separate line than the NT based OS's. They do not have the same kernel. Windows 95/98/Me had version numbers of four point something IIRC.

      --
      Every time you post an article on Slashdot, I kill a server. Think of the servers!
    11. Re:Lesson in MS Counting by Enlightenment · · Score: 1

      No, I'm pretty sure they're saying 1, 2, 3, NT, XP, Vista.

    12. Re:Lesson in MS Counting by sconeu · · Score: 1

      Close.

      1 2 3 3.1 3.5 4 2000 XP (= 5.1) Vista 7

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    13. Re:Lesson in MS Counting by Enlightenment · · Score: 1

      That's what TFA says anyway. (Or rather the video embedded in TFA says that.)

    14. Re:Lesson in MS Counting by cyfer2000 · · Score: 1

      2->2
      3->3
      95->4
      98->4.1
      ME->4.9
      2000->5
      XP->5.1
      2003->5.2
      Vista->6

      --
      There is a spark in every single flame bait point.
    15. Re:Lesson in MS Counting by sconeu · · Score: 1

      XP was 5.1. Vista is 6.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    16. Re:Lesson in MS Counting by fractoid · · Score: 3, Interesting

      If you're going to mod one of these posts up, pick this one.

      Also, notice that (with consumer releases), Windows seems to be following the even-odd rule? 3.1, meh. '95, good. '98, meh. '98SE, good. ME, ai f'thangan! 2k/XP, excellent. Vista? Pfft. Windows7? Good things to come. ;)

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    17. Re:Lesson in MS Counting by dedazo · · Score: 1

      The first version of the Windows NT kernel was 3.1

      Technically 3.0 was "Windows OS/2 3.0" or whatever they were calling it back then, though the first proper "Windows NT" release was 3.1.

      The first really usable version was 3.5.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    18. Re:Lesson in MS Counting by Annymouse+Cowherd · · Score: 1

      For those of you that dont understand the parent, Windows has kept a numerical version inside it the whole time
      To see the number, you can type ver in a console

    19. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      No, not really. That equation actually makes sense to you? Are you one of the Microsoft Excel developers?

      Actually, I think his job is to count and report Vista sales.

    20. Re:Lesson in MS Counting by Wonko+the+Sane · · Score: 1

      Win2K was part of a different product line. It was Windows NT version 4. With XP, the product lines were merged.

    21. Re:Lesson in MS Counting by TheDreadSlashdotterD · · Score: 1

      ME wasn't an OS, it was a virus.

      --
      I have nothing to say.
    22. Re:Lesson in MS Counting by magus_melchior · · Score: 4, Funny

      Apologies to fans of a certain British comedy group...

      "Me shalt thou not count, neither count thou 2, excepting that thou then proceed to 7. Vista is RIGHT OUT!"

      --
      "We are Microsoft. You shall be assimilated. Competition is futile."
    23. Re:Lesson in MS Counting by Anonymous Coward · · Score: 1, Funny

      To see the number, you can type ver in a console
      True, someone with Vista please check to see if they are at version 6.66 yet.
    24. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      No, NT4 was called NT4. Win2K was "NT 5." XP is effectively NT 5.1.

    25. Re:Lesson in MS Counting by Soiden · · Score: 1

      2->2 3->3 3.1->3.1 3.11->3.11 95->4 98->4.1 98SE->4.2 ME->4.9 2000->5 2000Pro->5.01 2000Server->5.02 2000AdvanceServer->5.021 2000DatacenterServer->5.22 XP->5.1 XPStarter->5.0999999999 XPPro->5.11 XPCorporate->5.12 XPMediaCenter->5.13 2003->5.2 VistaStarter->5.99999999 Vista->6 VistaHomePremium->6.01 VistaBusiness->6.02 VistaEnterprise->6.03 VistaUltimate->6.04 2008Server->6.5? 7->7

      --
      Minti: What's that huge shuriken in your back?! Kin: It's the instrument of my victory.
    26. Re:Lesson in MS Counting by DJ+Rubbie · · Score: 1

      Nope. Windows 2000 is NT 5.0, and Windows NT 4.0 was an earlier release made in 1996, and it actually replaced (not merged) with the legacy Windows 95/98/ME that really wasn't all that good.

      Running a web server can help with identifying these version numbers. Or check out wikipedia:

      http://en.wikipedia.org/wiki/Windows_NT

      --
      Please direct all bug reports to /dev/null
    27. Re:Lesson in MS Counting by CSMatt · · Score: 1

      I've actually found that 3.1 was more stable for me than 95, especially once I found out that the majority of my 3.1 headaches were actually caused by a faulty CD-ROM drive on the 3.1 machine. This machine also had 95 on it, and suffered from the same CD-ROM woes, but 95 on this machine also had trouble with programs that were strictly on the hard disk.

    28. Re:Lesson in MS Counting by suv4x4 · · Score: 4, Funny

      Apparently it goes:

      2, 3, 95, 98, ME, XP, Vista, 7!


      I'm more curious what will Apple name their next major release, if ever.

      OSX, OSXI, OSXII, OSXIV...?

      Of course, once they reach 10.9, they have the option of pissing in the face of basic number representation and call the next version 10.10, then 10.11 ...

    29. Re:Lesson in MS Counting by hyeh · · Score: 5, Informative

      Actually there are 2 Windows lines...

      MS-DOS Based
      1.x, 2.x (Windows/286, Windows/386), 3.x, 4.0 (95), 4.1 (98), 4.9 (Me)

      NT Based
      3.1, 3.5, 4.0, 5.0 (2000), 5.1 (XP), 6.0 (Vista), 7

    30. Re:Lesson in MS Counting by Repton · · Score: 3, Funny

      Ok, it made sense to me, but I had to reread it 3 times. Let's try again, with formatting:

      1. Windows 1
      2. Windows 2
      3. Windows 3.x
      4. Windows 95, 98
      5. Windows 2000, Windows XP
      6. Windows Vista
      7. Windows 7

      No mention of Windows ME, but perhaps that's as it should be...

      --
      Repton.
      They say that only an experienced wizard can do the tengu shuffle.
    31. Re:Lesson in MS Counting by CSMatt · · Score: 1

      ME also removed a lot of legacy DOS stuff save for the DOS parts in the kernel that were absolutely necessary. It makes more since to say that XP was 2000 with Luna, product activation, a 9x compatibility layer, and much more resource consumption (although I imagine that the last one might just be a consequence of the first three).

    32. Re:Lesson in MS Counting by suv4x4 · · Score: 1

      3 = 3 9x = 4 2k/xp = 5 vista = 6 7 = 7 Nuff said.

      Similar thing happened to Flash versioning:

      (1), 2, 3, 4, 5, MX, MX2004, 8, 9, 10

      Branding gone awry.

    33. Re:Lesson in MS Counting by niteice · · Score: 3, Insightful

      Of course, once they reach 10.9, they have the option of pissing in the face of basic number representation and call the next version 10.10, then 10.11 ...
      You mean like *nix (especially OSS) has been doing for 20 years?
      --
      ROMANES EUNT DOMUS
    34. Re:Lesson in MS Counting by clarkn0va · · Score: 1

      No wonder kids have so much trouble at math
      Kid's have trouble with math.

      MS's OS numbering scheme is senseless.

      Therefore, MS's OS numbering scheme was written by children.

      I know, logically this conclusion is invalid, however I think it's a step closer to the truth than what the parent was suggesting.

      db

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    35. Re:Lesson in MS Counting by Sparky+McGruff · · Score: 3, Funny

      Microsoft Windows [Version 6.0.6000] is what I have on my machine. I'm not upgrading to 6.66 until after Halloween. This version is frightening enough.

    36. Re:Lesson in MS Counting by GaryPatterson · · Score: 1

      Everyone forgets Windows 1.0 these days.

      Hmm.... after reading the Wikipedia page I see why!

    37. Re:Lesson in MS Counting by cheater512 · · Score: 3, Funny

      They used a beta of Excel 2009 to figure out the numbers.

    38. Re:Lesson in MS Counting by ZachPruckowski · · Score: 1

      Incorrect. 95/98/ME were not a part of the Windows NT family. It had been the workstation/server/professional Windows until the release of Windows 2000. NT started at version 3.1 to have version number parity with Windows 3.1.

      Windows 2000 was NT 5.0
      Windows XP was NT 5.1
      Windows Server 2003 was NT 5.2
      Vista is NT 6.0
      Windows Server 2k8 and Vista SP1 will be like NT 6.1 or something.

      Therefore the next Windows is NT 7.

    39. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Though by the same token, there shouldn't be any mention of Vista, either.

    40. Re:Lesson in MS Counting by devman · · Score: 1

      This guy got it right, mod parent up.

    41. Re:Lesson in MS Counting by epiphani · · Score: 1

      We'll get this right eventually.

      Replace "Windows 95, 98" with "Windows NT 4", and you're on the right track. 95,98 and ME were different code bases that were eventually tossed.

      --
      .
    42. Re:Lesson in MS Counting by Kreigaffe · · Score: 1

      You didn't get the memo?

      MS models their releases after Star Trek movies. This pattern is to be expected.

      --
      ... still waiting for this free-as-in-beer free beer I keep hearing about. :|
    43. Re:Lesson in MS Counting by Trogre · · Score: 1

      Maybe they'll pull a Knuth and make it asymptotically approach a number:
      7,8,9,10,10.1, ... 10.8, 10.9, 10.91, 10.92, ... 10.991, 10.992, ... 10.99999999

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    44. Re:Lesson in MS Counting by TheSkyIsPurple · · Score: 1

      What about Windows NT 3.1?

    45. Re:Lesson in MS Counting by Lord+Ender · · Score: 4, Informative

      No! The Win9x line is dead. 2000, XP, 2003, and Vista are the Windows NT line.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    46. Re:Lesson in MS Counting by NockPoint · · Score: 1

      You forgot MicroSoft Bob. Better than Windows ME.

    47. Re:Lesson in MS Counting by ConanG · · Score: 1

      File ME under number 4 along with 95 and 98.

    48. Re:Lesson in MS Counting by Wordsmith · · Score: 1

      So do two progressions that merge into one

      win 3.0/3.1 / nt 3.1 ===== 3
      95/98/me / nt 4.0 ===== 4
      2000/xp (one product line now) ===== 5
      Vista ==== 6
      7 ==== 7

    49. Re:Lesson in MS Counting by swordfishBob · · Score: 2, Informative

      Where's NT 3.1, NT3.5 ?

      --
      -- All your bass are below two Hz
    50. Re:Lesson in MS Counting by jamesh · · Score: 1

      Reminds me of trying to get my kids to do something when i'm too tired to get off the couch...

      "1... 2... 3... 4... 4+1/2... 4+3/4.... 4+4/5".

      Oh well... at least they're learning about fractions :)

    51. Re:Lesson in MS Counting by AikonMGB · · Score: 1

      Mac OS X11.. now that would be cool to see =P

      Aikon-

    52. Re:Lesson in MS Counting by twistah · · Score: 2, Informative

      Don't forget NT 5.2, which encompassed the ever-popular Windows 2003 Server, as well as several 64-bit releases of XP. NT6.0 also encompasses Windows Server 2008.

    53. Re:Lesson in MS Counting by rs79 · · Score: 1

      "7,8,9,10,10.1, ... 10.8, 10.9, 10.91, 10.92, ... 10.991, 10.992, ... 10.99999999 "

      If it were really Knuth it would be:

      1, 2, 3, 4, 10 I'll do the rest later.

      --
      Need Mercedes parts ?
    54. Re:Lesson in MS Counting by bigstrat2003 · · Score: 1

      That's not really true. 3.1 was good, not meh, in my opinion. Vista is also good, in my opinion. Now, 98 and ME... I feel sorry for anyone who upgraded to 98 (not that it was bad, it just was a pretty minor thing to call a "new version"), or used ME at all. So it's kind of like Star Trek movies, where you see the releases following the rule to an extent, but also releases which completely break the rule (3.1, Vista, ST 3, ST Generations), making it hard to generalize.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    55. Re:Lesson in MS Counting by fractoid · · Score: 1

      Well, fair enough, I actually thought Windows 3.1 wasn't bad given the time. I haven't used Vista enough to familiarise myself with it past the 'gaargh its different' phase, either, so I may be giving it an unfair rap. Also, don't lump 98SE in with 98 (which I'm not sure you did, but anyway...) 98SE was awesome, many people stayed with it until well after XP was established. I may have bent some of the ratings somewhat to make them conform with star trek... :P

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    56. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Of course, once they reach 10.9, they have the option of pissing in the face of basic number representation and call the next version 10.10, then 10.11 ... They've already done this. For the current Mac OS X 10.4 "Tiger" series, they started at 10.4.0, then updated to 10.4.1, etc. They're currently at 10.4.10 and there's rumours of 10.4.11.
    57. Re:Lesson in MS Counting by cheater512 · · Score: 1

      I think Windows 7 will break that theory. :P

      Also you seem to have lumped 2k and XP together.

    58. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Kid's what has problem with math?

      Or are you saying you have a problem with apostrophes and grammar?

    59. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Or this:
            1. Windows 1
            2. Windows 2
            3. Windows 3.x
            4. Windows 95, 98
            5. Windows 2000, Windows XP, Vista
            6. Windows 7

    60. Re:Lesson in MS Counting by Tumbleweed · · Score: 1

      Where's NT 3.1, NT3.5 ?

      They came right after OS/2 1.0, 1.1, 1.2, and 1.3. :)

      They skipped 2 because IBM took over then, so MS went with 3.1 (because 3.0 was bad luck). Simple.

    61. Re:Lesson in MS Counting by darthflo · · Score: 1

      Actually, the Product lines were merged. XP was clearly marketed as a consumer and professional/business type OS and did incorporate lots of Multimedia-related features that weren't too readily available on what were it's predecessors in the NT line. The code base of 9x, however, was largely if not completely dumped in favor of NT/2000's.

    62. Re:Lesson in MS Counting by darthflo · · Score: 2, Funny

      Viri tend to be rather stable, fast and actually working. If you are claiming ME provided any of these criteria, you must be new here (or in Soviet Russia where Windows crashes you).

    63. Re:Lesson in MS Counting by Yetihehe · · Score: 1

      Just like in SL, when there was version 1.9 everybody was like "Cool, now will be 2.0 with havok 2.0 and stability and everything". And then came 1.10. And rage ensued.

      --
      Extreme Programming - Redundant Array of Inexpensive Developers
    64. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Sigh. See http://en.wikipedia.org/wiki/Windows_NT for Windows KERNEL version numbers.

    65. Re:Lesson in MS Counting by steampoweredlawngnom · · Score: 2, Interesting

      NT-OS/2 actually.
      The way I understand it, the progression is as follows:

      1.x (on DOS kernel) -> 1.01, 1.02, 1.03, 1.04
      2.x (on DOS kernel) -> 2.03, 2.1 (Windows/286), 2.11 (Windows/386)
      3.x (on DOS kernel) -> 3.0, 3.1, WFW 3.1, 3.11, WFW 3.11
      3.x (new kernel, based on code originally slated to be OS/2 rewrite - known internally as NT-OS/2 for much of it's life, later simply WindowsNT) -> 3.1, 3.5, 3.51
      4.x (on DOS kernel) -> 4.0 (Windows95), 4.1 (Windows98), 4.9 (WindowsME)
      4.x (NT kernel) -> 4.0
      5.x (NT kernel) -> 5.0 (Windows2000) 5.1 (WindowsXP)
      6.x (NT kernel) -> Vista
      7.x (presumably NT kernel) -> Windows7 (whatever it's final name is)

      The story of Me is semi-interesting (actually not so much interesting as it is tedious). Basically, MS had intended NT 5.0 to be what XP actually became; they planned on merging the consumer and business platforms to a unified (NT) codebase (codenamed Neptune). NT 5.0's codebase was not finished with time enough to add all the features consumers needed, like compatability with 4.x and 3.x applications. The reason for naming NT 5.0 Windows2000 was to create a clear naming scheme for home users to upgrade, but by the time it became clear that 2000 would not be for home users, the name had already caught on. To prevent confusion, they revamped 98, adding Windows2000's icon set and interface enhancements, as well as a few odds and ends such as UPnP, to call it Millenium Edition, or Me.
      Me really should never have existed, and it was quickly slapped together to avoid a marketing catastrophe. Unfortunately for Microsoft, Me is their Pinto. OTOH, it made XP that much more appealing.

      Side note: NT starting at version 3 was a multi-reason decision, slightly influenced by it's relationship to OS/2, but much more due to marketing. NT started at version 3.1 because that was the version Windows was currently sitting at. Also, MS didn't want customers to think NT was less mature than OS/2 (then at version 2.1). NT got its name from the fact that they totally rewrote the OS/2 kernel, opting for a microkernel that was designed from the start to be portable and adaptable, with multiple "personalities" sitting on top of it e.g. a Unix personality, an OS/2 personality (IIRC there were even plans for a NeXT personality as well as a few others, though those never happened), etc. The concept was fairly new at the time, hence the name New Technology. NT 3.x included a 16-bit OS/2 "personality" and a basic POSIX "personality" both to ease migration to the new platform, but also to showcase NT's capabilities.

      I'm an OS/2 fanboy turned Linux fanboy, and I've never seen the NT sourcecode, but from what I've read the NT kernel itself is a marvel of software engineering. It's the userland crap piled on it that makes Windows the lumbering beast we all love to hate.

    66. Re:Lesson in MS Counting by joeytmann · · Score: 1

      you forgot NT 4.0 and Win 2000(aka Win 5.0). Oh and XP is 5.1 and Vista is Windows 6. The only real odd balls are 95/98/ME, which are probably considered by MS to be early versions of 2000.

      --
      Insert funny smart-ass comment here.
    67. Re:Lesson in MS Counting by Bert64 · · Score: 1

      They at least can count...
      If you assume MX to be 6, and MX2004 to be 7 then it all fits, i'm sure the internal version numbers are visible in an about box or something.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    68. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Sorry, but the real list is rather like this :

      OS/2, OS/2NT, NT3.51, NT4, NT2000, NTXP,NTVISTA, NT7

    69. Re:Lesson in MS Counting by Bert64 · · Score: 1

      Or you could take the cynical view that...
      NT5 (2000) failed to appeal to consumers because for most people 98se was sufficient and performed better, so they created an intentionally nobbled ME for the sole intention of making XP more appealing to consumers.

      As to the NT kernel, yes the base design was very good, and you are right that the lumbering clunky userland on top of it is what brings it down, a need to maintain compatibility with all the cruft built up around dos based windows, and the fact that the NT kernel was designed and written by experienced OS developers, while the dos based windows was cobbled together by people not experienced enough, and then hacked to add more functionality as needed instead of having an extensible design up front.

      It's not just the userland tho, microsoft have included a lot of cruft into the NT kernel itself, such that it's not at all the clean microkernel architecture it was intended to be... Some of the lead developers quit over the decision to put video drivers into the kernel for NT4 for instance, and a good proportion of windows crashes can be attributed to bad video drivers.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    70. Re:Lesson in MS Counting by Bert64 · · Score: 1

      ME didn't remove the dos stuff, it just hid it from the user... You could still drop out of windows and get to a dos prompt if you wanted to.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    71. Re:Lesson in MS Counting by dfgchgfxrjtdhgh.jjhv · · Score: 1

      nt 4 was 4, 2000 was 5, xp was 5.1

    72. Re:Lesson in MS Counting by steampoweredlawngnom · · Score: 1

      Fair enough, though XP really was enough of an improvement over 98se to stand on its own merit, PlaySkool interface notwithstanding. It didn't need Me to make it seem that much better.

    73. Re:Lesson in MS Counting by clickclickdrone · · Score: 2, Funny

      >I'm more curious what will Apple name their next major release, if ever.
      OS-Xe (e for enhanced)
      Now say it - OS Sexy - geddit?

      --
      I want a list of atrocities done in your name - Recoil
    74. Re:Lesson in MS Counting by doktor-hladnjak · · Score: 1

      Remember, "Windows 7" is just a code name like Longhorn (Vista/Server 2008), Whistler (XP/Server 2003), Millennium (ME), Memphis (98), Chicago (95). Marketing will probably call it something else by the time it's released. Still, some speculate that the return to numeric code names signifies something larger with the recent leadership change, mainly the moving of Steven Sinofsky from Office (where code names have always been numbered) to Windows.

    75. Re:Lesson in MS Counting by dhavleak · · Score: 1

      Jokes aside, I don't think the final version will be called Windows 7 -- that's just the development name they are using. Just like there will be no product called Longhorn (Vista and Windows Server 2008).. I doubt the folks at MS know what they're gonna call it yet..

    76. Re:Lesson in MS Counting by os2fan · · Score: 1
      The lineage for Windows is

      DOS based: 1.x, 2.x, 3.0, 3.1, 3.11 relies on previously installed DOS

      DOS 7+ based: relies on inbuilt DOS, but this can be replaced: dos 7.0: win 95, dos 7.1 win 95 OSR2.x win 98, win98se. dos 8.0 winme. You can to varying degrees replace the DOS in these windows with similar or higher versions.

      VMS/OS2 based: Windows NT 3.10, 3.50, 3.51 (1057), 4.0 (1381), Win2K 5.0 (2195), WinXP 5.1 (2600), Win2k3 5.2 (3790), and vista 6.0 (6000). In side branches lies Neptune 5.0 (5000, 5111) = Win2k home beta.

      If Windows for DOS is a 'thing on a thing', then so is Windows NT. Neither the character-mode installs or recovery consoles for DOS or Windows NT will run Win32 apps, or even a subset. Unlike, say OS/2 or linux, the WinNT character-boot will not run programs that run in the console, and the DOS proggies are just that: dos programs running in a VM, like they do in OS/2 or DosEMU.

      --
      OS/2 - because choice is a terrible thing to waste.
    77. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      I'm more curious what will Apple name their next major release, if ever.

      OSX, OSXI, OSXII, OSXIV...?
      Oh, sexy!
    78. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Of course, once they reach 10.9, they have the option of pissing in the face of basic number representation and call the next version 10.10, then 10.11 ...
      They can call them that without pissing in the face of anything; the period isn't a decimal point, it's there to separate the major and minor revision numbers. On the other hand, their supply of big cats is running out fast.
    79. Re:Lesson in MS Counting by Anonymous Coward · · Score: 2, Informative

      You missed out NT 3.51, NT 5.2 (2003) and the upcoming NT 6.? (2008).

      I must be in the sweetspot; everyone else here is too young to remember or so old they've started to forget.

    80. Re:Lesson in MS Counting by siride · · Score: 1

      Actually, Windows 3.x basically used MS-DOS as a bootloader and occasionally for drivers. It already had a preemptive multitasking kernel using 386 virtual memory and paging. Unfortunately, all Windows programs ran in a single task, but each DOS program ran in a separate kernel task since that was the only way to multitask DOS applications.

    81. Re:Lesson in MS Counting by dakameleon · · Score: 1

      They've got Cougar and Lion to go before they have to start going to "snow leopard" and the like.

      --
      Man who leaps off cliff jumps to conclusion.
    82. Re:Lesson in MS Counting by Corporate+Troll · · Score: 2, Interesting

      No, he's right and you're wrong. DOS was the underlying architecture and loaded before Windows 9x. Many (older) drivers needed to be loaded there (often soundcards) and Antivirus programs always embedded them in that part. The only thing that was different with WfW 3.11 was that you didn't need "win.exe" in the autoexec.bat.

      However, that was easy to change and you could make Win9x boot in CLI by adapting a config file, I just don't remember which one. Also creating a bootdisk with 9x, gave you a 9x bootdisk that went straight to CLI and typing VER didn't say aynthing about DOS, it talked about Windows 95 but for all intents and purposes it was DOS. Heck it even said "Starting Windows 95" as first text upon bootup.

    83. Re:Lesson in MS Counting by spiderbitendeath · · Score: 1

      you forgot NT 5.2 (Windows 2003)

      --
      Sometimes when I'm working on projects things disappear, I suspect gremlins.
    84. Re:Lesson in MS Counting by Pharmboy · · Score: 1

      Windows for Workgroups 3.11 was actually a great piece of software, and even had wins32 to run Photoshop and such. Not perfect, but perfectly minimalistic and fast enough, and you could fine tune a fair amount of settings (time slices, etc). I still like multitasking better, but it was as good as you can expect for a non-multitasking OS desktop.

      Personally I would rather see an EASIER option to run computers with the standard win95 interface. Every boxen we install has to be changed over in 15 ways to make it 'look' like win95, just for the speed. We only keep the shadows under the desktop icons which is pretty nice. Everything else is swapped to 'classic' mode, including disabling all the crapping zooming windows. I can't be the only one that uses their computer fast enough to find all this eyecandy incredibly irritating. I have already said that if our office tries to switch to Vista, I'm gone. (small shop, I _am_ the IT dept, among other things, so it's not likely.) Even the Linux desktop is getting bloated with too much eyecandy.

      Attention GUI writers: some of use the computer to do things. Simply running the computer to run the computer is not why we have them. Quit making our new computers boot up and start programs slower than a Mac Plus.

      --
      Tequila: It's not just for breakfast anymore!
    85. Re:Lesson in MS Counting by xhrit · · Score: 1

      win98 code base is still alive as windows CE/mobile.

    86. Re:Lesson in MS Counting by trifish · · Score: 1

      Wrong. MS-DOS was NOT the underlying architecture, kernel or anything. It migh have served as boot loader or kickstart. Do you really think that the MS-DOS "kernel" was Windows 9x kernel? Nope.

    87. Re:Lesson in MS Counting by Corporate+Troll · · Score: 1

      Yeah, sure DOS was a "bootloader" but the 9x "kernel" couldn't live without it. It still was essentially a GUI on top of DOS providing an extensive API, and nothing much more. The whole underlying DOS was there at all times, otherwhise "old drivers" wouldn't be able to function, and I already said that old drivers could and had to be loaded (again sound cards and anti-virus progs were guilty of this)

      You still have to load HIMEM.SYS and EMM386.EXE in the config.sys and not doing so would seriously make problems during 9x usage. Don't take my word for it, go ahead and install that piece of crap again.

      So, it was a "bootloader" providing essential functions for daily operation. Imagine you'd need grub to load your sound modules, well that was what 9x did. It was too intertwined to consider DOS separate from 9x.

      Besides, you remember Win32S. How do you explain that? It was a part of NT that was ported to Wfw311, not exactly a kernel, but enough for many programs to run. It's all in the APIs.

    88. Re:Lesson in MS Counting by poot_rootbeer · · Score: 1

      once they reach 10.9, they have the option of pissing in the face of basic number representation and call the next version 10.10, then 10.11 ...

      But those figures have a data type of "release", not "number". The dot is not as a decimal point, but rather a separator between major and minor release number.

      If they were plain numbers, then major.minor.fix representations like 10.2.15 would not be possible.

    89. Re:Lesson in MS Counting by xouumalperxe · · Score: 1

      Actually, 95/98/Me are not in the same lineage as 2K/XP/Vista. So you have (...) 4 - NT4 5 - 2000 5.1 - XP 6 - Vista 7 - ?

    90. Re:Lesson in MS Counting by Daimanta · · Score: 4, Funny

      3 = 3 9x = 4 2k/xp = 5 vista = 6 7 = 7 9x = 4
      x = 4/9

      2k/xp = 5

      k = 1000

      2000 / xp = 5
      x = 4/9

      4500p = 5

      p = 1/900

      Windows == Solved!

      --
      Knowledge is power. Knowledge shared is power lost.
    91. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Would that be "7 of 9"?

    92. Re:Lesson in MS Counting by trifish · · Score: 1

      MS-DOS and Win32 are two different things. Windows 9x had native support for MS-DOS apps, but that was only a PORTION of the OS. The rest was Win32.

    93. Re:Lesson in MS Counting by Corporate+Troll · · Score: 1

      that was only a PORTION of the OS

      You finally agreed with me.... Good boy...

    94. Re:Lesson in MS Counting by dargaud · · Score: 1

      The Win9x line is dead. Are you absolutely, positively sure of that ? We wouldn't want the risk to see it rise from its grave, right ? A wooden stake in the heart and a whole lot of flaming jet fuel maybe ?!?

      Seen too many cheap horror movies.

      --
      Non-Linux Penguins ?
    95. Re:Lesson in MS Counting by niteice · · Score: 1

      Suppose they start below 1...
       
      0.9, 0.99, 1!

      --
      ROMANES EUNT DOMUS
    96. Re:Lesson in MS Counting by trifish · · Score: 0, Flamebait

      that was only a PORTION of the OS

      You finally agreed with me.... Good boy...


      Are you an idiot? I didn't agree with you. You stated that Windows 9x was BASED ON MS-DOS. That is utter nonsense. The system only has portions that allow legacy code to run. Otherwise it is a completely new kernel.

    97. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      You mean people actually play second life? I'm always reading articles about the people that play, but I've never EVER EVER heard of any actual person that does.....

    98. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      And when they run out of those, they'll start using strange hybrids, "tiger-husky", "poodle-panther", "kanga-leopard", and the like.

    99. Re:Lesson in MS Counting by edwdig · · Score: 1

      Check the Caldera vs Microsoft antitrust case. Caldera was claiming that MS-DOS 7 and Windows 95 were really separate products, combined only to get around the legal restrictions placed on Microsoft bundling DOS and Windows together.

      Caldera Win95 and/or DR-DOS so that Win95 would think that DR-DOS was MS-DOS 7 (the version included with Win95). They added in code to log calls to DOS functionality and found that Win95 was making calls to DOS far more often than even they expected.

    100. Re:Lesson in MS Counting by Anonymous Coward · · Score: 0

      Hmmm, Corporate Troll is not trolling here, but you are. Win 9x ran on top of DOS. You could start the computer just in DOS mode (hitting F8 during startup), muck around in DOS for half an hour, and then type win.com to load Windows. And then, when you were done in Windows, there was an option to shutdown to a DOS prompt, essentially unloading the windows program.

      You're pretty much wrong here. Suck it up and go read a bit. Then come back when you're better.

    101. Re:Lesson in MS Counting by swordfishBob · · Score: 1
      > Where's NT 3.1, NT3.5 ?
      They came right after OS/2 1.0, 1.1, 1.2, and 1.3. :)

      OS/2 2.0 preceded NT 3.1

      For a while there was talk of NT being OS/2 v3.

      --
      -- All your bass are below two Hz
    102. Re:Lesson in MS Counting by GPL+Apostate · · Score: 1

      The real 'kink' in the works is that the first version of Windows NT was version 3.1. And the numbering for Windows 2000 and on is based on the versioning of the NT line, not the old 16 bit mess.

      I have Windows 1.03 (complete package including retail box, manuals, etc.) but have never heard of anybody having Windows 1.0. PC-DOS 1.0 is a weird thing, too.

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    103. Re:Lesson in MS Counting by CSMatt · · Score: 1

      My mistake. I've never had the misfortune of having to use ME so I didn't know for sure.

    104. Re:Lesson in MS Counting by toddestan · · Score: 1

      Windows 95 and 98 are what Windows 1.0-3.11 eventually grew into. Really, there are two Windows lines, the first one is what I call the "dos-based" ones that started with Windows 1.0 and ended with Windows ME. Then there is the "NT-line" which starts with NT 3.1 (you could also call it the "OS/based" line) and currently sits with Vista and will eventually evolve into Windows 7, apparently.

    105. Re:Lesson in MS Counting by toddestan · · Score: 1

      Windows 3.1 was actually pretty decent. It predated things like the registry, which was the big downfall of Windows 95 in my opinion. The registry was hard to understand, tended to accumulate cruft, and seemed to like to randomly corrupt itself for no reason back in the '95 days, which killed more than a few of my Windows 95 installs. Windows 3.1, on the other hand, used text-based configuration files which made it much easier to troubleshoot and more resilent to corruption and cruft. Windows 3.1 was also very snappy and fast on as little as a 486DX/33 with 4MB of ram, which is not the case with 95.

    106. Re:Lesson in MS Counting by CSMatt · · Score: 1

      I've never noticed that much "under the hood" difference between 2000 and XP other than XP's completely unnecessary bloat due to all of the extra crud Microsoft threw in "for the desktop user."

    107. Re:Lesson in MS Counting by trifish · · Score: 1

      MS-DOS 7 (the version included with Win95)

      You correctly used the word "included". That's correct. It was only included as legacy component, it was not based on it. Win32 and MS-DOS are like apples and oranges. Similarly, Win32 and Win3 are like apples and oranges.

    108. Re:Lesson in MS Counting by trifish · · Score: 1

      Hmmm, Corporate Troll is not trolling here, but you are.

      Actually, neither me, nor Corporate Troll, but you are trolling here (as an Anonymous Coward). Check the definition of trolling. I pointed out that he was wrong when he said that Windows 9x is based on MS-DOS. That is not trolling, moron.

    109. Re:Lesson in MS Counting by The+One+and+Only · · Score: 1

      Actually, Cougar is equivalent to Puma (which they've already done), not that it'll stop them. There's also Ocelot, Margay, Bobcat, Lynx...

      --
      In Repressive Burma, it's not just your connection that dies. slashdot.org/comments.pl?sid=314547&cid=20819199
    110. Re:Lesson in MS Counting by dakameleon · · Score: 1

      I'm going on Wikipedia here, but a Panther is "a black specimen (a melanistic variant) of any of the big cats.", and all of the main big cats are in the genus 'Panthera' anyway, so Leopard is a 'repeat' already. Ocelot, Lynx et al aren't technically 'big cats' - you might as well start going "Cheshire" or "Persian short hair" :P

      --
      Man who leaps off cliff jumps to conclusion.
  5. Good intentions by _merlin · · Score: 5, Insightful

    I'm sure Microsoft developers have good intentions and big dreams for Windows 7. I'm sure they did for Vista at the beginning of the project. But they'll have to cut corners, meet dates, add legacy support, and all the things a behemoth like Microsoft always thinks they have to do. For all their failings, you've gotta give Apple credit for having guts to change things - the Mac has gone through three CPU architectures, and two completely different operating system kernels.

    1. Re:Good intentions by mblase · · Score: 4, Insightful

      But they'll have to cut corners, meet dates, add legacy support, and all the things a behemoth like Microsoft always thinks they have to do.
      Legacy support is important to many business Windows customers; some of them are still using 16-years-old custom software that needs to run on whatever desktop OS their employees are running.
    2. Re:Good intentions by larry+bagina · · Score: 3, Insightful

      They did switch from the DOS-based (1, 2, 3, 95, 98, Me) to NT based kernel. And NT 3 was written for i860 and MIPS, then ported to x86, alpha, and powerpc.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    3. Re:Good intentions by Anonymous Coward · · Score: 0

      One word: virtualization.

      There's no excuse for having a system bogged down with backwards compatibility. Run old stuff in a vm (like OS X does for OS 9) or pull a Wine.

    4. Re:Good intentions by ColdWetDog · · Score: 1

      Legacy support is important to many business Windows customers; some of them are still using 16-years-old custom software that needs to run on whatever desktop OS their employees are running.

      True, but that what Virtual Machines are for. Run VMware with a Win 98 image for the next century if need be. Just let the Rest of Us move along...

      --
      Faster! Faster! Faster would be better!
    5. Re:Good intentions by suv4x4 · · Score: 3, Insightful

      For all their failings, you've gotta give Apple credit for having guts to change things - the Mac has gone through three CPU architectures, and two completely different operating system kernels.

      Comparing the situation of Apple and Microsoft is dangerously wrong. Microsoft would most likely bankrupt if they did what Apple did with the three CPU architectures.

      I agree with you MS have good intentions and think big. Where I don't agree is that having a product after 5 years of development is just some "things a behemoth like Microsoft always thinks they have to do".

      What else are they supposed to do? Sit on it?

      They made mistakes with Vista. First mistake was they started developing Vista on post-XP beta code. It created a huge mess, so they dropped it, took the more modular Windows 2003 codebase, further analyzed it, modularized it, and in the span of 2 years, ported their old code over to end with what's Vista.

      They just thought they'd be done too soon. The vision of Vista is great, but they had to carry it out in 2-3 quicker releases, each with lesser more incremental upgrades.

      What Microsoft learned from Vista is they need to get their code in order. The new kernel design is part of this effort. I think they're on a good track, I pray like hell they take their time with it, and finish it properly, versus rush it like Vista.

    6. Re:Good intentions by Joe+The+Dragon · · Score: 1

      Vm's add overhead and make more work for IT.

    7. Re:Good intentions by iocat · · Score: 3, Funny

      And this is a problem for readers of slashdot how? More work = more work.

      --

      Dude, I think I can see my house from here.

    8. Re:Good intentions by Joe+The+Dragon · · Score: 1

      more work on top of the work need for a new windows system as well as the added hardware load.

    9. Re:Good intentions by fireslack · · Score: 1

      Then don't upgrade. Problem solved.

      --
      This sig only exists because you are observing it.
    10. Re:Good intentions by dhasenan · · Score: 4, Insightful

      If you can't handle it, port the application to a more recent version of Windows.

      If the application is sixteen years old, it should have system requirements that would be considered trivial by today's standards, so virtualization or emulation shouldn't cause as much of a performance hit. Instead, the application would perform as if it had been written today.

    11. Re:Good intentions by Ender77 · · Score: 1

      The best solution is virtual machines(which is what it looks like Microsoft is heading for). Totally recreate the OS from scratch and get rid of the slush of legacy support, people can just install a VM of their favorite OS. I really love VM's, the only gripe is the no hardware sharing(video card access for games for example).

    12. Re:Good intentions by AndrewNeo · · Score: 1

      Why even upgrade, if they have to use such old software? Surely it won't run much faster on newer machines?

    13. Re:Good intentions by Spy+Hunter · · Score: 1

      VMs add practically zero overhead if they are implemented with cooperation from the OS being virtualized. A new OS that has the explicit goal of virtualizing legacy Windows could do a near-perfect job, ensuring compatibility while allowing Microsoft to end work on the giant legacy codebase that even they admit has become a nightmare.

      This approach would be similar to what Apple did with the Classic environment in OS X, but with advanced features similar to Parallels to make the virtualization seamless. If Microsoft's Windows unit has any sense, Windows 7 will work this way, with a new kernel based on some of the great work coming out of Microsoft Research (I'm not holding my breath).

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    14. Re:Good intentions by Coward+Anonymous · · Score: 1

      And yet you firmly believe that these same business customers who are relying on a 16-years-old software really need to upgrade to the latest and greatest Windows OS?!
      No, the customers with the 16-years-old software will not change anything in their configuration and that includes the OS. Unless of course, MS makes it impossible for them to do.

    15. Re:Good intentions by Anonymous Coward · · Score: 0

      "you've gotta give Apple credit for having guts to change things"

      not really 'guts', just an advantage of having about 2% market penetration at the time. if MS changed their os architecture and stopped supporting older hardware/software i'm sure everyone's arms would go up and lawsuits would probably fly. with even the small (but grown users of macs since osx came out), apple would have a really hard time doing what they did again. imagine if with the next release of OsXI (?) none of your currently purchased software would run? of course most mac users are very non-savy and purchase each and every new version of the hardware...

    16. Re:Good intentions by aztektum · · Score: 1

      Minesweeper and Solitaire?

      --
      :: aztek ::
      No sig for you!!
    17. Re:Good intentions by evil9000 · · Score: 1


      They made mistakes with Vista. First mistake was they started developing Vista on post-XP beta code. It created a huge mess, so they dropped it, took the more modular Windows 2003 codebase, further analyzed it, modularized it, and in the span of 2 years, ported their old code over to end with what's Vista.


      They always use 1 branch of code. They never use multiple branches of code. Having started writing on post-xp beta code is meaningless, they always use the latest generation of the nt line of code, and in this example it would be win2k3 code.

      You talk like they have 2 seperate development trees of code, but they always have 1 tree with many branches.

    18. Re:Good intentions by Anonymous Coward · · Score: 0

      16 year old legacy applications are precisely what a built-in VM would be good at. (Although I doubt they're customers for a computer running Windows 7, but a program that old would have been designed to run in the DOS/Win 3.1 era, for crying out loud. You could fit the memory space for an application like that in a modern CPU cache.)

      The real problem will probably be games coded X years ago by the time 7 comes out, where X is a small number. They'll probably be coded for Vista, the Win32 API, and will probably need enough CPU umph that they won't be trivial to virtualize. In which case, you still need to do all that work to maintain the Win32 API, so what's the point in abandoning it in favor of an isolated VM implementation?

      Unless the game industry abruptly disappears for several years, there won't be a transition from the Win32 API. Ever.

    19. Re:Good intentions by Kris_J · · Score: 4, Informative

      Actually, VMs can reduce overhead for IT. For each legacy app, build a VM image and then just deploy that image to any of the PCs that needs it. Much more reliable than trying to run it directly through some dodgy legacy support.

    20. Re:Good intentions by Chabil+Ha' · · Score: 1

      Sounds like MS needs Rosetta-like interface for emulating legacy win32 system calls. Or hell, businesses can run their legacy code on a friggin' VM...There's no reason to not to stop the past 20 years of insanity. They've got blinkin' lava flow on their hands! They already of a software platform (.NET anyone?) that abstracts the newer code from the OS, c'mon!

      --
      We're all hypocrites. We all have hidden parts, it's the contrast between them that make us more a hypocrite than others
    21. Re:Good intentions by Das+Modell · · Score: 1

      I don't really understand why they'd want to optimize the kernel. Aren't they constantly just making Windows use more and more resources? I'm not exactly sure why they do that, but that's what they're doing.

    22. Re:Good intentions by ColdWetDog · · Score: 1

      Yeah, and maybe, just maybe it would even come with documentation. Unlike APIs from some large PC OS developer whose name starts with an "M".

      --
      Faster! Faster! Faster would be better!
    23. Re:Good intentions by suv4x4 · · Score: 1

      They always use 1 branch of code. They never use multiple branches of code. [...] they always have 1 tree with many branches.

      Oook.. you know, they gotta be pretty quick to be able to completely reverse their source code base organization from the time you started writing your post to the time you ended it.

    24. Re:Good intentions by phantomcircuit · · Score: 1

      Virtualization seems like it is the solution, but there are certain technologies that virtual machines simply do not support. An example being EMS, Expanded Memory Specification for MS-DOS.

    25. Re:Good intentions by Almahtar · · Score: 1

      Then they should keep selling the old OS's.

    26. Re:Good intentions by ottffssent · · Score: 2, Insightful

      Legacy support is important to many business Windows customers; some of them are still using 16-years-old custom software that needs to run on whatever desktop OS their employees are running.


      Bullshit.

      Slap it in an DOS VM and be done with it. Hell, that's basically what NT does anyway. Backwards compatibility is a great excuse for a crummy security model and a requirement of the marketing department which can't really give a satisfactory answer to "...but why shouldn't I run my DOS VM on Linux and save $200?" It's not actually a technical requirement. In a world where you can buy a quad-core CPU for a couple hundred bucks, with each core as fast as the fastest x86 chip you could buy a couple years ago, there's really no reason not to cordon off all that nasty old Windows code in a VM or two and let it munch on one of the cores.
    27. Re:Good intentions by andreyw · · Score: 1

      In fact, the Mac has gone through a lot more than TWO kernels... Geez.

    28. Re:Good intentions by happyemoticon · · Score: 1

      Well then, why not sell Windows 7: Crufty Old Apps Business Edition and Windows 7: No Bullshit Legacy Crap Home Edition? They're so into selling different versions of their OS, they might as well have something to differentiate them besides windowdressing. I don't see a rational case for the needs of people who still use Cardfile imposing unwanted, non-optional, security-compromising, bloat-inducing features on little ol' me.

    29. Re:Good intentions by Tim+C · · Score: 1

      But they'll have to... meet dates... and all the things a behemoth like Microsoft always thinks they have to do.

      Given the absolute roasting we've given them for how long it took them to get Vista out the door, do you really believe that MS only "thinks" they have to meet dates?

    30. Re:Good intentions by shmlco · · Score: 1

      Forget Rosetta, think Parallels and Coherence mode, run "antique" applications in a VM that appears fully integrated into the desktop. Build all of your new applications in .NET where feasible, or as binaries making new, secure system calls when not.

      Want to use the new XYZ features in 7? Then rebuild/recompile your applications. Otherwise you're VM'ed.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    31. Re:Good intentions by Anonymous Coward · · Score: 0

      Doesn't Windows virtualize legacy support already? I think they call it WoW or Windows on Windows. It's how the 32-bit NT kernel runs 16-bit apps, and how 64-bit windows will be running older 32-bit windows apps.

    32. Re:Good intentions by mjorkerina · · Score: 1

      No it's not virtualization, it's THE ACTUAL 32 BITS LIBS installed inside a 64 bits system.

      Like under linux with a multilib system.

    33. Re:Good intentions by darthflo · · Score: 1

      Right. It's more work to support one physical computer, one installed app (VMware) and a few files (VMs) per person than it's to support three computers running wholly different OS versions of which at least some won't participate in your network. Right.

    34. Re:Good intentions by darthflo · · Score: 1

      Microsoft's usual product lifespan is something in the region of 5 years. Even if you're on a secure network, you don't want to be running an OS that's been unpatched for the past eleven years. Paying MSFT to continue providing updates to you is an option, but I am quite sure that rewriting or at least fixing the Apps incompatibilities would be cheaper. A lot.

    35. Re:Good intentions by darthflo · · Score: 1

      That would mean two entirely different code bases. Since the No Bullshit Legacy Crap Home Edition would, as the name suggests, be targeted at personal and the Crufty Old Apps Business Edition at business users, the Windows line would split back up into 9x and NT style product lines. In the long run this would very probably mean worse hardware support ("Why should a high end graphics accelerator work in Windows Business? Why would you want a professional-grade RAID controller in your Home Edition?"), a security and management-wise impared product line ("You ain't running an Active Directory at home and logging in with passwords and stuff really seems too businessy") and similar problems.

    36. Re:Good intentions by adamofgreyskull · · Score: 3, Funny

      Trivial system requirements...like being able to copy 16,384 files without rebooting. :o)

    37. Re:Good intentions by AaronLawrence · · Score: 1

      And does that work when the application uses custom or older hardware for which there are no drivers for newer versions of Windows?

      --
      For every expert, there is an equal and opposite expert. - Arthur C. Clarke
    38. Re:Good intentions by Bert64 · · Score: 1

      Backwards compatibility is about the only thing keeping microsoft alive right now... Companies are stuck with a lot of old legacy apps that run on nothing else, and the cost of replacing those apps is prohibitive so they stick with windows...
      If they were forced to update everything anyway, then the migration costs that discourage people from migrating to something like linux would also apply to whatever microsoft were putting out. Making the savings from moving away from microsoft even higher, as well as a strong desire to not be stuck having to migrate from a deprecated proprietary product again.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    39. Re:Good intentions by Bert64 · · Score: 1

      That assumes you still have, or can obtain 98 licenses to install on your VM...
      If all you have are OEM licenses, you can't move them off the machines they came with, and when those machines physically fail due to old age your stuck.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    40. Re:Good intentions by Bert64 · · Score: 1

      If you have the source code you can port it... But if you have the source, you could also port it to something other than windows too.

      However most of these apps people are stuck with are proprietary and closed source, which locks the customers into whatever system they're tied to.
      People really need to learn from their mistakes, and not get stuck with proprietary lock in again...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    41. Re:Good intentions by Bert64 · · Score: 1

      The move from dos caused problems for gamers (many games required all the base memory they could get, and didnt work with windows running) and the move to nt-based windows caused further problems...
      Also, wine seems to perform fairly well, and ibm managed very good windows 3.x compatibility with os/2... Surely with the source code microsoft could manage a very good wine-like system, and what slight performance hit it might cause would be offset by faster hardware.

      Ofcourse they will never do this, because it would mean a clean break from their legacy cruft, and a lot of people only stick with windows because they need old applications which are tied to it.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    42. Re:Good intentions by eyeye · · Score: 1

      Vm's add overhead and make more work for IT.


      Rubbish, they actually solve many of the problems that IT has had.
      --
      Bush and Blair ate my sig!
    43. Re:Good intentions by Phoobarnvaz · · Score: 1

      Legacy support is important to many business Windows customers; some of them are still using 16-years-old custom software that needs to run on whatever desktop OS their employees are running.

      The thing I am still amazed about is the OS/2 1.X layer still being integrated into versions of the NT kernal. The only companies I've seen still running any OS/2 1+ was the DMV & a call center I helped setup for a move of their PC's from one office to another.

      For myself...if the Linux designers would make a easy PVR software that didn't require more than running Apt or Yum or whatever...would drop XP in a heartbeat. Would even run my old DOS games under DOSBox under Linux.

      --
      Don't worry about the world coming to an end today. It's already tomorrow in Australia. - Charles M. Schulz
    44. Re:Good intentions by Bert64 · · Score: 1

      Fixing the issues becomes even cheaper still if you have the capability to upgrade parts of the OS but not the whole, and strip out things you don't need...
      To give an example, there is a company that runs a radius server for authentication of various things including custom written apps, dialup users etc... The radius server is heavily modified such that a standard implementation couldn't be a drop in replacement.
      This server runs on a very old linux system, using a 1.x kernel and on hardware which is archaic by todays standards.
      The server has one setuid binary (sudo), 2 network listening services (radius, sshd) and 1 other background daemon (cron)... The version of SSH has been updated many times, as has crond, and the radiusd is pretty much custom.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    45. Re:Good intentions by Anonymous Coward · · Score: 0

      VMs create more work? Rubbish. They simplify. If it breaks, replace it with a fresh copy. What could be simpler?

    46. Re:Good intentions by 0100010001010011 · · Score: 1

      Sandbox it. Apple's done it pretty well with Rosetta and Classic before that and 68k emulation before that. Parallels does an awesome job with XP, I don't even know I'm running windows other than the taskbar is visible. I can double click a *.exe file from anywhere and it just launches in XP and runs right next to my OS X windows. Drag, Drop, Copy & Paste all work seamlessly. The Only problem I have is key commands. Control- in Windows and Command-* in OS X. And this is a 3rd party company that doesn't have access to all the APIs.

      Make it a 'free' download (after you're declared "Authentic") or include it as a package.
      [X] Windows XP Compatibility mode
      [ ] Windows 98 Compatibility mode
      [ ] DOS Compatibility mode

      With multi-core processors showing up this should be trivial to do.

    47. Re:Good intentions by JPEWdev · · Score: 1

      I work in Academia tech support, and I've come to find that a most of the time, it is the hardware, not the software that requires the legacy support. For example, we have several gas spectrograph (or something like that) in our building. The hardware works just as well as it did when they bought it, but the manufacturer hasn't bothered to keep updating the software to run on anything newer than Windows NT 4. Thus, we are required to keep these old machines around and support them since the department doesn't want to drop however many tens of thousands of dollars on new equipment when the old stuff works just fine (which I comletely understand). Also, in cases like this a VM would likely be far more hassle than it is worth, due to propritary interface cards used to connect the computer to the spectrograph. Not necessarly to say that this problem is unique to Windows or even non open-source software, it just tends to be more pronounced and occur sooner. The point is, you can't always just port the application to the newest version of the OS and continue with life.

    48. Re:Good intentions by poot_rootbeer · · Score: 1

      Legacy support is important to many business Windows customers; some of them are still using 16-years-old custom software that needs to run on whatever desktop OS their employees are running.

      Then let them have a "Microsoft Windows 7 Legacy Regressive Edition" that contains all the cruft needed for them to continue running their old MS-DOS applications, and let the rest of us have a clean, modern version of Windows optimized for people who live in the present.

      I shouldn't have to suffer just because some suit in 1993 assumed that 16-bit Windows APIs would be around forever.

    49. Re:Good intentions by foniksonik · · Score: 1

      There are plenty of desktop publishing houses that still have old Powermacs running Mac OS9 6 years later, just so they can run some version of Quark Xpress that they need for old files. SO what? Apple added in support for running OS9 as a virtual machine in OS X as a migration stop gap solution.

      Why can't MS do the same using Virtual PC?

      If they were smart about it they could provide the option of installing a compatibility layer using Intel Hypervisor and something like Parallels Coherence mode (where just the application window is displayed, instead of the entire desktop environment) and 'easily' provide support for legacy software while updating the main distribution to be non-backwards compatible.

      Another option would be to provide discounted services to help those companies port their legacy code. It can't be all that hard to do. Most of those old programs do relatively simple things and the majority of the complexity is in getting the old OS to display it properly (ie: if you separate the business logic from the presentation you'll find that it isn't all that complex).

      --
      A fool throws a stone into a well and a thousand sages can not remove it.
    50. Re:Good intentions by space_biker · · Score: 1

      If you're going to port it, why not rewrite it for Linux? or cross-platform in Java?

      If you can't rewrite it, run it under wine or in a VM.

      And if they absolutely have to upgrade, upgrade to a real OS.

    51. Re:Good intentions by Anonymous Coward · · Score: 0

      that's said a lot, but how many people are doing that ? Very few. and even if they are they don't need to upgrade.
      Either keep running the same version and it works well, or VMware it on a newer box if you have to.
      Or re-write it for .NET etc. etc.

    52. Re:Good intentions by edxwelch · · Score: 1

      I'd say most of the problem was MS development process, which seems totally disorganised.
      According to one of the developers working on the Vista shutdown dialog a team of 43 people were working on the feature for a year without ever getting close to finishing it:

      http://moishelettvin.blogspot.com/2006/11/windows-shutdown-crapfest.html

  6. Here we go again... by Anonymous Coward · · Score: 0

    Much more information will be available next Friday...

  7. I wonder... by larry+bagina · · Score: 5, Interesting

    I can't help but wonder if this is a reaction to OS X being used on iPhone and iTouch(mySelf). Maybe they're trying to consolidate windows/windows CE. Or maybe this is just another feature that will be cut in favor of demanding a DNA sample before allowing you to access the internet.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

    1. Re:I wonder... by Anonymous Coward · · Score: 0

      Considering the habits of the average user, I would think that most end up leaving a "DNA sample" during their web surfing.

    2. Re:I wonder... by Anonymous Coward · · Score: 0

      Or maybe this is just another feature that will be cut in favor of demanding a DNA sample before allowing you to access the internet. Most people supply the DNA sample shortly after logging onto the internet.
    3. Re:I wonder... by Anonymous Coward · · Score: 0

      It looks to me from the outside that Microsoft thinks of phones and computers as separate products. Eventually this won't be the case and home computing will be taken over by phones that connect everywhere. Maybe docking stations for fixed point use, small phone screens for mobile use, possibly laptop docs for intermediate use, and lots of other potential interfaces - TV, car stereo). At that point, the same software has to run on your ultra mobile phone as on a home PC today. And SW vendors are going to want to only release one version.

      Of course MS might be making a mistake again. By the time Windows 7 gets out the door, phones will probably be powerful enough to run Vista and all this work minimizing the kernel will be useless (ha!)

    4. Re:I wonder... by samkass · · Score: 1

      It wouldn't be a bad idea for them to re-sync WinCE, XBoxOS and Vista a bit before going too far forward. I have no insider info, but my understanding from reading Ars and such is that the XBox is a branch of NT3 (with the XBox360 continuing the branch) and WinCE is more or less from scratch with the APIs bolted on. Approaching development like Apple does with one kernel and a host of drivers and user-space options targeted at embedded, desktop, and server configurations seems like it would be a more sustainable model.

      --
      E pluribus unum
    5. Re:I wonder... by Anonymous Coward · · Score: 0

      Is iTouch(myself) Apple's response to the porn market? :-P

    6. Re:I wonder... by suv4x4 · · Score: 1

      I can't help but wonder if this is a reaction to OS X being used on iPhone and iTouch(mySelf). Maybe they're trying to consolidate windows/windows CE. Or maybe this is just another feature that will be cut in favor of demanding a DNA sample before allowing you to access the internet.

      Not really, since this has been in the works for over 3 years now.

      It's a reaction to them coding mess upon mess for years and not knowing what their own source does as a result. Technically it's still the Windows code, but major refactoring is happening. It's a good thing.

      Compatibility with the Win32 API will be preserved, but some oddities which software out there relies on will be gone.

    7. Re:I wonder... by Anonymous Coward · · Score: 0

      "
      Of course MS might be making a mistake again. By the time Windows 7 gets out the door, phones will probably be powerful enough to run Vista and all this work minimizing the kernel will be useless (ha!)"

      This is exactly the problem with Microsoft. They are neve thinking long-term enough.

      Apple after the newton didn't think to return to the small computer market until it was powerful enough to run a full fledged OS. Well now the iPhone runs OS X itself.

      Microsoft is doing all the optimization mumbo jumbo but they're going to be less full-featured than non-optimized competitors that were smart enough to know the hardware is progressing.

    8. Re:I wonder... by Anonymous Coward · · Score: 0

      what the fuck ever fanboi. iphone fags are running in record number to get away from it. not since the first gen razors have we seen so many fanbois running in fear.

    9. Re:I wonder... by dave420 · · Score: 1

      That's not OS X running on the iPhone and iPod Touch - it's a seperate OS they decided to call OS X for marketing purposes. Don't fall for the hype :)

  8. microkernel? by nagashi · · Score: 1

    Microsoft has 'invented' the Microkernel? Sounds good to me, but seriously. The major reason for going with a microkernel I've always read was protection from drivers with memory leaks and such. I use windows at work and linux at home, and I haven't blue-screened in about 6 years. Still, a simpler design may be safer as well, ne? Fewer exploits via buggy syscalls?

    1. Re:microkernel? by Sparky+McGruff · · Score: 1

      You haven't blue screened in 6 years? I'm impressed. I bought a windows Vista laptop about 6 months ago. It only gets light use, mostly web surfing and some microsoft word. I have a Mac at work that does most of the heavy lifting, and it works pretty flawlessly, even though it is several years old and way overworked.

      I just went back and checked the "problem reports"; I've had 26 blue screens (Windows shut down unexpectedly) in the "windows" column. It has gotten better after a few updates here and there, but it is not by any stretch "crash free". I certainly have to reboot often, if I don't want it to crash.

    2. Re:microkernel? by mdmkolbe · · Score: 2, Informative

      Sorry to disappoint you, but this is not a microkernel. This is just slimming down on what is packaged with the OS.

      Think more along the lines of sliming Red Hat Linux down to the size of Damn Small Linux, except right now Windows has the shell, X11, Gnome, etc. all running in kernel mode.

      The continuum looks something like this:

      1. Everything (shell, graphics system, window manager, etc.) in the kernel. (This is Windows as it is now.)
      2. Modularization to the level where different configurations can be distributed. (This is what it sounds like Windows 7 is going for.)
      3. Major subsystems (shell, etc.) moved into userspace, but still with a lot of stuff in kernel space (drivers, filesystems, etc.). (This is what Linux is now.)
      4. Everything moved into userspace that possibly can (Usually only threads, IPC and address spaces are left in kernel space). (This is a true microkernel.)
    3. Re:microkernel? by Lisandro · · Score: 3, Informative

      The nice thing about microkernels is that the kernel itself it's completely isolated from the rest of the software running on it - even device drivers, which can (and are) a breaking point in common monolithic kernels. Instead of doing direct calls to the kernel, the software now uses a system of messages.

      This, of course, works just fine and it makes the kernel rock solid, but makes system calls slower. I'm guessing that when Win7 is released hardware will be fast enough that this will be a non-issue (hell, it might even not be one now), but the point is, a "regular" kernel will almost always outperform it on the same hardware.

    4. Re:microkernel? by drsmithy · · Score: 1

      Everything (shell, graphics system, window manager, etc.) in the kernel. (This is Windows as it is now.)

      No, it's not.

    5. Re:microkernel? by TheNetAvenger · · Score: 1

      You act like this is a 'new' or abstract concept to Windows NT.

      I suggest you go look up the NT kernel architecture. It already bridges the best of both worlds of mono and micro designs and why NT is described as a hybrid kernel or a client/server kernel.

      Everyone acts like the Win 7 stuff is 'new' to Microsoft, but don't seem to realize that the kernel technology in NT is on par or even more advanced than other kernel technologies in every other OS out there, including OS X, Linux, etc.

      The Win 7 and other kernel concepts being thrown around at MS are the 'next' generation in kernel designs that are ahead of the rest of the industry, even though it is unpopular to state this on SlashDot.

      When NT was developed, it took the best Kernel concepts of the time, many of which were only 'theory' and adapted them into a new technology that didn't have the weight or shortcomings that other kernel implementations of the time did. This is why the kernel and HAL in Vista is not a massive change from the original designs in 1992. It was made to take the best of the time so that it would last for 15-20 years, which was a stated design goal of the time, and they succeeded.

      Win 7 stuff will be the next generation, and sadly MS is taking the lead in moving 'theory' into actual practice once again, and unless the OSS world is paying attention MS will leapfrop the industry, just as NT was a major jump of the kernel technologies of 1992.

      PS the calls do NOT have to be slower, see the internal structure of the NT kernel that already is subsystem 'virtual' based. (Hence why Win32/Win64/BDS all run on the NT kernel in abstract subsystem layers that don't talk directly to the kernel already.)

  9. Interesting by JK_the_Slacker · · Score: 1

    I'm curious as to just how long Microsoft has had somebody trying to minimize the kernel footprint. It would seem, from mere observation, that their trend has been to make a kernel that's feature-oriented at the expense of performance. It's really sad that developers no longer seem to care much about optimization. After all, the end user can just slap another gig of memory or higher-spec video card right in, can't they?

    --
    I'm waiting for a "-1 somepeoplejustshouldn'tgetmodprivileges" meta-moderation.
    1. Re:Interesting by wwahammy · · Score: 1

      Actually the kernel is simpler in Vista because graphics drivers run primarily in userspace. That's why nvidia and AMD had to make new drivers.

    2. Re:Interesting by smash · · Score: 1
      It's not that developers don't care - well, maybe some don't, it's about controlling software development and maintenance costs.

      Programming/debugging/maintaining stuff written in assembler is expensive. Easiest way to go about it is to write in a higher level language, optimise the hot-spots and wear the memory footprint. Memory is cheap.... programmer time is not.

      Wasteful? Sure. But if we were still writing everything in hand optimised assembler, we wouldn't be using the internet, downloading ISOs and building home media centres, etc - on free software. We'd more likely have the open-source equivalent of Windows 3.1 for the cost of vista ultimate...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    3. Re:Interesting by ZenShadow · · Score: 1

      Who said anything about hand-optimized assembler?

      Code in any language can be optimized. Case in point: I once wrote a trivial little systray app in MSVC++ using MFC. The thing was 7MB at runtime. Rewrote the same thing going straight to the Win32 API, and it was 16KB - and easier to understand, at that.

      --S

      --
      -- sigs cause cancer.
    4. Re:Interesting by Daengbo · · Score: 1

      Menuet is an operating system written entirely in assembly. It's free. You can't quite call it Open Source, though.

  10. Vista will be renamed to MaxWin by z-j-y · · Score: 0

    too boost the sale

  11. What about those fancy new effects/tech? by Zantetsuken · · Score: 1

    I would think that might be kinda hard, since they *just* introduced Vista with all of its new GUI effects and background services. To pull those out would make it look like they made a mistake with Vista. On the other hand, he said "optimizing the *kernel*" not all the other crap that bogs it down. Even if they made a brand new kernel that could run everything a "modern" kernel/core OS is expected to have, they'd somehow find unnecessary system services to bog it down...

  12. Can I get a little insight, please? by Jon.Laslow · · Score: 1

    I'm a Windows user (no jokes, please), and have occasionally dipped in to a Linux distribution, but I've never looked at Kernel Memory Usage. What is the standard memory usage for a Linux Kernel, just so I have something to compare with the numbers mentioned in TFA?

    1. Re:Can I get a little insight, please? by jlarocco · · Score: 2, Interesting

      At one point I had full XFCE desktop and latest (at the time) 2.6.xx kernel running in under 35 MB. That was a few months ago.

      But I'll be the first to admit that it wasn't a typical install. I was going more for speed, but I compiled the kernel with exactly the set of drivers/modules I needed; and compiled X, XFCE, and most "important" system libraries myself. Base distro was Slackware.

      I'm running a fairly standard Debian install right now, and with no apps running it'll use about 150 MB with X, Fluxbox, and some fairly "standard" background services.

      I'll also point out that the 35 MB Slackware was running on a 32-bit Pentium 4, and this Debian install is running on AMD64. Doesn't make much difference, but enough that I thought I should point it out.

    2. Re:Can I get a little insight, please? by cheater512 · · Score: 1

      Your standard Linux kernel only uses a meg or two at most.
      Its completely insignificant.

      On embedded devices it goes down even more.

    3. Re:Can I get a little insight, please? by baldass_newbie · · Score: 1

      The video had this 'MinWin' install going at 40 meg...with no graphics, only a web server.
      I snickered and stopped watching.
      It's bloated DSL, as far as I'm concerned.

      --
      The opposite of progress is congress
    4. Re:Can I get a little insight, please? by ozmanjusri · · Score: 2, Informative
      What is the standard memory usage for a Linux Kernel

      Download sizes;
      Version 1.0 * Current: 1.0.9, 16-Apr-1994 * Size: 1.3 KB(bz2)
      Version 2.6 * Current: 2.6.23, 09-Oct-2007 * Size: 5.8 MB(bz2)
      http://www.linuxhq.com/kernel/

      In use;
      Linux kernel 2.6.23, 1.8M on disk and 2.3M in RAM.

      I don't have a copy of the 1.0 kernel to compare with, sorry.

      --
      "I've got more toys than Teruhisa Kitahara."
    5. Re:Can I get a little insight, please? by ozmanjusri · · Score: 1
      I'm a Windows user (no jokes, please)

      Sorry, can't help myself.

      *Sob* Poor Laslow. The finest mind of your generation, and you're using **Windows**?

      --
      "I've got more toys than Teruhisa Kitahara."
    6. Re:Can I get a little insight, please? by William-Ely · · Score: 1

      Is that a reference to Real Genius?

      --
      Mod me down with all of your hatred, and your journey towards the dark side will be complete!
    7. Re:Can I get a little insight, please? by ozmanjusri · · Score: 1

      No, Casablanca, via Half-Life 2.

      --
      "I've got more toys than Teruhisa Kitahara."
    8. Re:Can I get a little insight, please? by SL+Baur · · Score: 1

      At one point I had full XFCE desktop and latest (at the time) 2.6.xx kernel running in under 35 MB. That was a few months ago. Good job. Long, long ago I made a 2 1.44MB floppy boot/root-fs system (with networking & NFS) for rescue & installation which worked just fine.

      I suppose this is the wrong article to point out that not only what you did is possible, but you can sell it afterwards thanks to Open Source licensing.

      Mod me down Microsoft Fan Boys. Bury the truth.
    9. Re:Can I get a little insight, please? by cnettel · · Score: 1

      Yeah, because the code size is the most relevant metric, right?

    10. Re:Can I get a little insight, please? by aliquis · · Score: 1

      Look at NetBSD-kernel instead ;)

      Or QNX Neutrino ;)

    11. Re:Can I get a little insight, please? by Anonymous Coward · · Score: 0

      In my experience, the *file* the kernel is stored in on the files system is about 6-10MB in Linux, +/-, depending on your config.

      Of course, this is also for a fairly standard instally, you could configure it to many more MB of bloat, or less than 1MB, if you know what you are doing.

      C:\Windows\System32\kernel32.dll -> 961kb

      My guess: That's not the whole kernel. I'd expect at least 5 MB for MS, min.

    12. Re:Can I get a little insight, please? by mqduck · · Score: 1

      Mod me down Microsoft Fan Boys. Bury the truth. You must be new here.
      --
      Property is theft.
    13. Re:Can I get a little insight, please? by ozmanjusri · · Score: 1
      because the code size is the most relevant metric

      It's what the OP asked for.

      Why are you complaining?

      --
      "I've got more toys than Teruhisa Kitahara."
    14. Re:Can I get a little insight, please? by cnettel · · Score: 1

      No, he asked for memory usage. You just gave the numbers for the code pages in RAM.

    15. Re:Can I get a little insight, please? by GPL+Apostate · · Score: 1

      That's the standard 'classic' Slackware install set. A boot diskette, a root diskette, an ethernet card in the box, and you install over an NFS share from a server somewhere on your network. Good times and Slackware in the 90's, building a network of 386sx machines all hovering around my big 486 box with all 16 megs of ram in it, with thin ethernet and ancient 3-Com cards I bought at a surplus store for $2 a pound.

      Ah, the memories.

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    16. Re:Can I get a little insight, please? by GPL+Apostate · · Score: 1

      If you compile the kernel with just the keyboard, basic console, IDE hard drive, no SCSI and no networking, a 1.0 or 1.2 kernel can be pretty small.

      But it will never 'beat' Minix in that game, cuz Minix you can run on an 8088 machine.

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
  13. Seems to coincide with patents by Anonymous Coward · · Score: 5, Interesting

    This seems to coincide directly with some recent patents filed by Microsoft. It seems what they're truly after is an al-la-carte style OS where DRM is used to control the subscription of such "base OS" additions. Read more on the patent here, http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PG01&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.html&r=1&f=G&l=50&s1=%2220060282899%22.PGNR.&OS=DN/20060282899&RS=DN/20060282899

    Basically, you purchase the base-system and tack-on additional subscription based modules. My concerns are how the subscription model will function, the subscription pricing, and the potential for removal of prior features such as 3D acceleration on the 'base' system.

    It also appears that DRM will be used extensively in this model and will not be solely limited to music/video as previously thought.

    Honesty, and I'm not trolling here, but this looks pretty scary. This reminds me of driver-signing gone awry. I don't see the potential for open-source/free modules due to item #3. Arbitrary application, memory, CPU, and process limits are also concerning.

    The whole "add-on" 3D support as well as "don't limit my desktop to 5 open applications/processes" seems incredible. I imagine the base system will be usable to about 3% of the population and the subscription-based add-on modules may be pricey. I can't imagine a DRM style approach for 3D gaming/enthusiasts being acceptable. Imagine having to pay $20/mo for 3D + multiple core CPU + 2G RAM and the minute you stop paying all those modules expire and are no longer active until you resume payment; like Napster and other DRM based music models work.

    -evilghost

    1. Re:Seems to coincide with patents by visgoth · · Score: 1
      "The more you tighten your grip, Tarkin, the more star systems will slip through your fingers. "

      There's a limit to how much you can abuse the rectums of even the dumbest of customers, and I think Microsoft is headed squarely toward that limit.

      --
      My patience is infinite, my time is not.
    2. Re:Seems to coincide with patents by failedlogic · · Score: 1

      People have been saying gaming in arcades has been dead for years. Could we see our PCs recycling the use of the quarter coin collectors?

    3. Re:Seems to coincide with patents by suv4x4 · · Score: 1

      Honesty, and I'm not trolling here, but this looks pretty scary. This reminds me of driver-signing gone awry. I don't see the potential for open-source/free modules due to item #3. Arbitrary application, memory, CPU, and process limits are also concerning.

      Don't worry, companies patent lots of things they don't use.

      In the case of this module subscription, it won't be implemented for the base features of the OS, such as 3D acceleration, since the market won't allow them. Apple is picking speed, Linux is picking some speed.

      By the time 7 is out, Microsoft will already be feeling the heat of those two emerging competitors and not playing with fire a lot.

      They may implement it for some optional extra features, but that's not that big of a deal, or anything new for that matter.

    4. Re:Seems to coincide with patents by Anonymous Coward · · Score: 0

      Basically, you purchase the base-system and tack-on additional subscription based modules. My concerns are how the subscription model will function, the subscription pricing, and the potential for removal of prior features such as 3D acceleration on the 'base' system.

      I have no concerns, as I would never purchase an operating system where a company in Redmond can decide to turn off features willy-nilly over the Internet, just because I'm not paid up on my subscription. No matter what the terms are. I select an operating system to, you know, operate my computer. If the computer is effectively bricked, the operating system sorta isn't doing its job.

      (Unless these subscription features would be things I'm not going to use anyway, like an integrated client that requires a subscription to some Microsoft service. Then it's just business as usual from Microsoft, which has always been looking to sell people services through bundling with Windows. Observe various incarnations of MSN, and now Windows Live. But if it's core OS functionality, forget it.

      Unfortunately, I'm not confident enough that the marketing department at Microsoft doesn't actually realize what a horrible idea this is. Just look at how excessive WGA has become. Piracy of Windows may be a problem--most people consider it pretty much free because it comes with their computers, and you can't do without it--but it's hardly a problem worth inflicting WGA on their customers over.)
    5. Re:Seems to coincide with patents by Synonymous+Bosch · · Score: 3, Interesting

      people always have such extreme overreactions to any microsoft articles or announcements.

      the component oriented model seems like it could be a smart move - business users may not want fancy 3d or even sound functionality, a barebones os may be perfect for them, especially for terminal services clients.

      this kind of model could also make them immune to their ongoing legal disputes regarding bundled software.

      it could also address user complaints about OS bloat, and fears the next version of windows will come on 2 dvds ;)

      it could also reduce the confusion between the different versions of windows as seen with vista

      as for the price, i expect each module is going to be a lot cheaper than a world of warcraft subscription :) microsoft make a lot of mistakes, but as far as making dollars goes, they seem to have a lot of smarts. i'm sure they'll figure something out which might even strike people as acceptable.

      there's a lot of coulds in here, but hey, we still really don't have any useful information - and besides, microsoft could completely screw it up and make a shemozzle of the whole thing.

      alternatively, they could set a new standard which is quickly adopted by their competitors, apple included.

      maybe i'm new here, i'm not prepared to write off anything i don't know anything about out of knee jerk predjudice :)

    6. Re:Seems to coincide with patents by Anonymous Coward · · Score: 0

      No way Microsoft can get away with it on the desktop. That's when everyone goes Ubuntu + Wine = done (full disclosure: I use Debian). Seriously. The only way Super Windows will be appealing is if they can actually make it a compelling embedded platform with this reduced kernel. We have resources to spare on the desktop so we don't have to put up with this shit. And Linux has much more forward momentum than Windows technologically. It will be at parity by the time Windows 7 comes around.

      Yes, I realize embedded Linux is all that and a box of chocolates. But if Microsoft can create an XNA for embedded devices that works well, the improved toolkit over Linux pain would be totally worth it to custom device developers. It has done wonders in the Xbox 360 vs PS3 battle.

      Linux needs to make its developer tools friendlier. We've got the old EMACS + C/C++ crowd. Then the VI + scripting language crowd. And finally the Eclipse + kitchen sink crowd. None of these are really as magical as Visual Studio. I'm not saying the aforementioned tools are bad. No, they are like finely honed scalpels in the hands of master surgeons. But we need some idiot developer tools for Linux. For those self-taught, don't-really-understand-programming people who don't want to take the time to learn all that stuff just to make a simple application with a few buttons.

      You know. Shit just needs to work. You should be able to stumble your way into an application (web or fat) with a button, a text box, and an event handler without having to read a giant tutorial or do a 10 step wizard.

    7. Re:Seems to coincide with patents by networkassault · · Score: 1

      Man, that's a scary patent. It says in the patent itself in language plain enough for every one to see that Microsoft reserves the right to establish expiration dates for modules to the OS. Basically, if they want to kill off Windows 7 immediately when Windows 8 comes out, all they have to do is to kill off all your modules. I thought Vista took too much of the ownership of my computer away from me. This is an outrage! There's never been a better reason to switch to an alternate OS. They basically control your computer with this scheme. I hope they realize, though, how ridiculously hard a modular OS will be for them to make. I mean, Microsoft is the one that couldn't make Me work well. Vista's no walk in the park either. I was afraid of Microsoft before. Now, I'm more afraid of Microsoft than I am of death itself. Don't let MS get away with this! Frankly, I'm surprised how open that patent is. Most patents are intentionally vague. This one clearly defines Microsoft's strategy if they're technically able to do this.

      --
      "I'm glad I'm going to die because, when I do, the world's gonna go to the dogs." -Me on aging and the next generation.
    8. Re:Seems to coincide with patents by Richard+W.M.+Jones · · Score: 1

      Basically, you purchase the base-system and tack-on additional subscription based modules. My concerns are how the subscription model will function, the subscription pricing, and the potential for removal of prior features such as 3D acceleration on the 'base' system.

      What's quite interesting is that this is how commercial Unix died. The vendors started charging extra for the C compiler, the text tools, X support, &c. in exactly this a-la-carte mode. It was deeply confusing for the customers are one (of many other) reasons why everyone shifted to Linux.

      Perhaps ReactOS will have their day yet ...

      Rich.

    9. Re:Seems to coincide with patents by Walter+Carver · · Score: 1

      as for the price, i expect each module is going to be a lot cheaper than a world of warcraft subscription :) I don't. When you are monopoly you don't care about the price.
  14. Call me in 2012..... by edwardpickman · · Score: 4, Funny

    when its at least in beta.

    1. Re:Call me in 2012..... by istartedi · · Score: 4, Funny

      No thanks, I'll be waiting for Hurd to be production-ready.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    2. Re:Call me in 2012..... by Anonymous Coward · · Score: 0

      According to the Mayan calendar, any version released after december 21, 2012 will be pretty much useless...

    3. Re:Call me in 2012..... by Trogre · · Score: 1

      Why, won't the new version cope with an extra ring in the calendar?

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  15. This time will be different! by Wylfing · · Score: 4, Funny

    It's going to have a database file system! It's going to be secure! No more rebooting! It will have a really good command line!

    --
    Our intelligent designer has never created an animal that we couldn't improve by strapping a bomb to it.
    1. Re:This time will be different! by AmigaMMC · · Score: 1

      Hmm funny! Database File System (which was announced for Vista months after Amiga Inc. announced the Ortogonal Persistence File System for AmigaOS5 = same thing) was pushed back so much because M$ had/has no idea on how to implementet and that's their reason for the first delays in shipping Vista (we know better now), then they announced that it would be part of a major upgrade (under payment) of Vista, now it's moving to the next edition? Yeah right! Luca

    2. Re:This time will be different! by Frosty+Piss · · Score: 2, Insightful

      Rethink the Registry? Please?

      --
      If you want news from today, you have to come back tomorrow.
    3. Re:This time will be different! by toddhunter · · Score: 1

      Don't forget that under windows 7, music will sound better.

    4. Re:This time will be different! by Anonymous Coward · · Score: 0

      MS has been pushing the DBFS idea since, oh, around the time that Be Inc. actually delivered on it. Look at the marketing hype for Cairo.

    5. Re:This time will be different! by Anonymous Coward · · Score: 0

      It's really implausible to speculate, I mean the code for win 7 isn't really even written yet, they're mostly just doing design review now. However, MS is also starting to practice what SWI preaches with SDL and such, and they already have people on-site doing design review and pen-testing what little code there is, this will continue on for the majority of the next year. The upside of all of this is quite simply that the security people will have been involved nearly from day one, which should end up in a pretty secure product.

      For all the bashing everyone likes to give it, the security of vista actually is *a lot* better, heck even apple agrees, go through what they've announced in regards to security enhancements for the next version of osx and count how many of them already exist in vista; that speaks volumes.

    6. Re:This time will be different! by Anonymous Coward · · Score: 0

      It's going to be secure! No more rebooting! It will have a really good command line!
      Then, why not call it Linux Kernel 2.4.1?
      In other news, DRMs are still not working under Linux .. guess which system i'll keep on using ??

      It's going to have a database file system
      What will it be named ? ReiserFS, VxFS, XFS, Fuse, ... or Filesystem Metadata ??
    7. Re:This time will be different! by IdeaMan · · Score: 1

      Really good command line? They're working on PowerShell

      No I am NOT an MS fanboy. I'm posting this so that bash will be better than this by the time it rolls out (well you can download it for vista, but since I'll never run Vista I can't tell you first hand if it's any good.

      --
      They ARE out to get you simply because They are in it for themselves and they don't care about you.
  16. where are the details? by networkzombie · · Score: 1

    He is describing Windows v6. Where are the details of Windows 7? I've played with the beta of 2008 Core, and it is fun and all, but that's exactly what he seems to be talking about. As a matter of fact he does talk about it, yet he gives no details of Windows v7 past the ASCII boot screen. Did I miss something? Is that the big change? They save HDD space by using ASCII graphics?

    1. Re:where are the details? by Anonymous Coward · · Score: 3, Funny

      As a matter of fact he does talk about it, yet he gives no details of Windows v7 past the ASCII boot screen. Did I miss something? Is that the big change? They save HDD space by using ASCII graphics?

      That IS Windows 7! It's the return of the CLI! Everything old is new again! Reviewers are already writing accolades for the new interface. It's been called "Bold" "Clean" and "Unobtrusive".

      The perfect OS for people new to computers, no longer is there a rash of icons to confuse them, the OS is "simple" for those not technically inclined.

      Enterprise customers love the lack of superfluous eye candy. Windows 7 screams "business" and "just the facts" and with a lack of translucency and 3D effects it runs much faster on businesses' hardware. Upgrade cycles can now be extended another 5 years and save millions in hardware costs by not having to buy higher end processors, memory, and GPUs to get basic work done.

      Gamers will also appreciate more of their system's horsepower being put to use on their favorite titles. "It's like playing Doom on DOS 6 again!" raved one user.

      Yup, Windows 7, it's not outdated, it's VINTAGE CHIC!
  17. So what? by foo+fighter · · Score: 4, Insightful

    The kernel hasn't been Windows's problem since NT 4.

    The real problem is the middle-management clusterfuck. The direct result of which is the bizarro world of Windows the platform and its zillion libraries and APIs that have subtle (and not so subtle, but probably undocumented) incompatibilities.

    Microsoft's own devs can't figure that shit out and they've been trying since XP. It has only become worse since they shoved all the digital restrictions management into the system.

    --
    obviously no deficiencies vs. no obvious deficiencies
    1. Re:So what? by midnighttoadstool · · Score: 1

      Actually the Kernel has only been good since Vista. Before Vista multi-threaded synchronization used 'events', which are very hard to get right and the result has been a lot of subtle bugs.

      Since Vista we now have condition variables which the rest of the sane world has had for a while now. It is not entirely MS's fault: they were threading pioneers, and condition variables weren't an option at the time.

      Still to be addressed is least privilege access control: but that isn't entirely a Kernel problem.

    2. Re:So what? by moosesocks · · Score: 3, Interesting

      I should probably go one step further to point out that NT is probably the best (and most modern) general-use kernel in widespread use today. I'm no kernel developer, although after talking to people 'in the know', I get the general concensus that NT was one of the few things Microsoft got right and nailed on the head.

      Although there's nothing fundamentally wrong with the Linux Monolithic Kernel (especially since it's behaving more and more like a microkernel these days), Linus has admitted that were he to start from scratch, it wouldn't be monolithic.

      I don't know too many specifics of the OS X (Mach) kernel, although from what I understand, there are some fundamental performance and latency issues holding the entire system back that have existed in Mach since the beginning.

      Although the software on top of NT is often less than stellar (ruined by the businesses execs, and trashed by the requirement for backward-compatibility), the NT kernel is generally regarded as being the most solid part of the operating system.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    3. Re:So what? by ettlz · · Score: 3, Informative

      Although there's nothing fundamentally wrong with the Linux Monolithic Kernel (especially since it's behaving more and more like a microkernel these days)
      Exporting the odd service or two (like FUSE) does not a microkernel make. And modern NT is not a microkernel by any stretch. Read what AST has to say. If anything, NT's gigantic Executive makes it even more monolithic than Linux. Anyway, the best solutions often borrow ideas from all over the shop.

      Linus has admitted that were he to start from scratch, it wouldn't be monolithic.
      Citation, please.
    4. Re:So what? by Anonymous Coward · · Score: 0

      Linus has admitted that were he to start from scratch, it wouldn't be monolithic.

      We all know that Windows and other micro kernels are modern and much more suitable for the desktop. UNIX is obsolete shit designed in the 60's for mainframes. Dump the legacy shit already. Jeez.

    5. Re:So what? by Blakey+Rat · · Score: 1

      NTFS is a pretty damned slick filesystem too. Not that anybody here on Slashdot, yourself excepted, would ever admit anything coming from Microsoft to be any good at all.

    6. Re:So what? by Anonymous Coward · · Score: 0

      NTFS is a pretty damned slick filesystem too. If by "slick" you mean "slow", you may have a point! Try unpacking some large tar archives or do something like that, and watch it take 3 times as long as on ext3.

  18. ah! just in time by boxlight · · Score: 4, Insightful
    ah! news of a new version of windows -- just in time for the release of Leopard.


    looks like Mistersoftie is up to their old hype the vaporware tricks to dissuade buyers from going with attractive alternatives.

  19. Windows 7 preview by Kurt+Gray · · Score: 5, Funny

    You turn on the computer. You are greeted by an angelic chime that gets progressively louder until your speakers shake. You attempt to adjust the volume but it only gets louder still. A full screen Window icon ripples across the screen then all goes black. The product activation screen prompts you to enter your activation keys, printed on 27 pages of holographic alloy glue to the inside of the aluminum DVD case. For the next 3 hours you enter the activation key, taking breaks to use the bathroom, eat, and make phone calls.

    After entering the correct activation keys, a dialog appears prompting you to select your social login profile group. You have no idea what that is so you click "Other Networks" The next dialog says "Connecting to networks..." for the next 5 minutes. A message apears saying "New Hardware Found" but it can't find the driver. Another popup appears "No networks found". Then your desktop appears. The wallpaper is stunning. The Internet Explorer icon appears to majestically float above the screen. You click it. A message appears warning you that the Internet can harm your computer, do you want to continue? You click "Yes". You are prompted to enter your administrator key. This key is on the sticker on the inside of your PC case. You shutdown the PC, get a screwdriver, open the case, write down the 18 digit administrator code, put the case back together and reboot.

    After rebooting, blocking your ears during the chime assault, and oggling the amazing wallpaper, ignoring the "live folders server not found" error, you try Internet Explorer again. You dutifully enter the administrator key. You are asked if you want to save this key to your "universal keyring" You click OK. You are warned that the universal keyring is encrypted and your sending encrypted information. You click OK. After 3 minutes you get an error saying "No key server found" ... and so on...

    You never do get to see the Internet. But the wallpaper is amazing.

    1. Re:Windows 7 preview by wizardforce · · Score: 1

      well at least windows would be secure, and look there's clippy to great you at boot up :)

      --
      Sigs are too short to say anything truly profound so read the above post instead.
    2. Re:Windows 7 preview by Anonymous Coward · · Score: 0

      You turn on the computer. You are greeted by an angelic chime that gets progressively louder until your speakers shake. You attempt to adjust the volume but it only gets louder still. A full screen Window icon ripples across the screen then all goes black. The product activation screen prompts you to enter your activation keys, printed on 27 pages of holographic alloy glue to the inside of the aluminum DVD case. For the next 3 hours you enter the activation key, taking breaks to use the bathroom, eat, and make phone calls. After entering the correct activation keys, a dialog appears prompting you to select your social login profile group. You have no idea what that is so you click "Other Networks" The next dialog says "Connecting to networks..." for the next 5 minutes. A message apears saying "New Hardware Found" but it can't find the driver. Another popup appears "No networks found". Then your desktop appears. The wallpaper is stunning. The Internet Explorer icon appears to majestically float above the screen. You click it. A message appears warning you that the Internet can harm your computer, do you want to continue? You click "Yes". You are prompted to enter your administrator key. This key is on the sticker on the inside of your PC case. You shutdown the PC, get a screwdriver, open the case, write down the 18 digit administrator code, put the case back together and reboot. After rebooting, blocking your ears during the chime assault, and oggling the amazing wallpaper, ignoring the "live folders server not found" error, you try Internet Explorer again. You dutifully enter the administrator key. You are asked if you want to save this key to your "universal keyring" You click OK. You are warned that the universal keyring is encrypted and your sending encrypted information. You click OK. After 3 minutes you get an error saying "No key server found" ... and so on... You never do get to see the Internet. But the wallpaper is amazing.
      But good sir, these are all features not bugs or errors.
    3. Re:Windows 7 preview by failedlogic · · Score: 2, Interesting

      This is modded funny, but how about 'Reality'?

      I honestly wonder if some of these posts aren't printed and used internally at Microsoft as either: cubicle decorations, motivation to make better code or ammunition to convince managers to improve the development process.

    4. Re:Windows 7 preview by langelgjm · · Score: 1

      You are prompted to enter your administrator key. This key is on the sticker on the inside of your PC case. You shutdown the PC, get a screwdriver, open the case, write down the 18 digit administrator code, put the case back together and reboot.

      Please. No self-respecting geek shuts down the computer before taking it apart...

      I once knocked a PCI card out of a running machine. That was amusing.

      --
      "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
    5. Re:Windows 7 preview by Saint+Aardvark · · Score: 1

      Thank you for that...I haven't laughed that hard all week.

    6. Re:Windows 7 preview by mrbluze · · Score: 1

      Will they let you buy a cheap upgrade from vista? I'm just at the partition manager for my Gutsy Ubuntu installer wondering should i wipe vista or keep.



      Allow or Deny?

      --
      Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
    7. Re:Windows 7 preview by gardyloo · · Score: 1

      It is pitch black. You are likely to be eaten by a grue.

    8. Re:Windows 7 preview by smash · · Score: 1

      I've accidentally rebooted a running machine with liquified compressed air before :D

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    9. Re:Windows 7 preview by Jugalator · · Score: 2, Funny

      Hmm, I'm now convinced Windows 7 is not its real codename, but it's actually called Project Zombo over at Redmond.

      --
      Beware: In C++, your friends can see your privates!
    10. Re:Windows 7 preview by AttillaTheNun · · Score: 1

      I see that George Lucas is on board to develop the Windows 7 wallpaper.

    11. Re:Windows 7 preview by jonasj · · Score: 1

      HA! HAHA! HAHAHAHAHAHAHA!

      Oh, THANK YOU for that. It boosted my mood in just the way I needed right now.

      --
      You know, Microsoft's street address also says a lot about their mentality.
    12. Re:Windows 7 preview by Anonymous Coward · · Score: 0

      ...so your post made me oddly depressed...

    13. Re:Windows 7 preview by Frozen+Void · · Score: 1

      This= +7 Funny material.

    14. Re:Windows 7 preview by Anonymous Coward · · Score: 0

      Ummm...you forgot the classic "The case has been opened...please enter the BIOS password:", when you broke the seal and opened the case to get the administrator key. Hence, you will have to take out the battery, unseat the BIOS chip, reseat it, wait three days, replace the battery, and THEN reboot.

    15. Re:Windows 7 preview by The+One+and+Only · · Score: 1

      You turn on the computer. You are greeted by an angelic chime that gets progressively louder until your speakers shake. You attempt to adjust the volume but it only gets louder still.

      Windows 7 is going to be THX certified?

      --
      In Repressive Burma, it's not just your connection that dies. slashdot.org/comments.pl?sid=314547&cid=20819199
    16. Re:Windows 7 preview by El_Oscuro · · Score: 1

      I once unplugged an IDE CD-ROM drive from a running machine. Instant BSOD. Standard reload from scratch Windows repair.

      --
      "Be grateful for what you have. You may never know when you may lose it."
    17. Re:Windows 7 preview by stefanlasiewski · · Score: 1

      and make phone calls.

      The computer IS my phone, you insensitive clod. Convergence ahoy!

      --
      "Can of worms? The can is open... the worms are everywhere."
  20. Huh? by Anonymous Coward · · Score: 0

    Why bother coming up with a new list when 75% of Vista's original feature list never got implemented?

  21. Singularity Anyone? by filesiteguy · · Score: 1

    I wonder how much (if anything) the Singularity (http://research.microsoft.com/os/singularity/) project will influence the next gen Wintendo. I was talking to an MS engineer today (to whom I gave a SUSE 10.2 DVD) who is installing AD at our location.

    He showed me that they apparently already have a VM of Singularity internally. (Of course, I couldn't get a copy...)

    1. Re:Singularity Anyone? by Eli+Gottlieb · · Score: 1

      Could you please not compare Nintendo to Microsoft?

    2. Re:Singularity Anyone? by filesiteguy · · Score: 1

      LOL! - Wintendo is a derisive term intended at the people who use Microsoft products for their ability to play games. Nothing to do with MS == Nintendo. (Though my son does play NESTicle on my wife's Win2K computer.)

  22. Windows 7??? by QuietLagoon · · Score: 1

    Microsoft doesn't even have Windows Vista working yet.

    1. Re:Windows 7??? by Fourier404 · · Score: 0

      "Screw it, let's just cut our losses and move on."

    2. Re:Windows 7??? by SeaFox · · Score: 1

      "Screw it, let's just cut our losses and move on."

      Probably not that far from the truth the way things are going.
      Vista truly is the new ME.
  23. What about the hardware vendors? by pilbender · · Score: 2, Insightful

    Hardware suppliers have always counted on Microsoft to force people into buying a new system. If they design something that's optimized and competitive, they will lose their advantage and preferrential treatment by those vendors.

    In other words, they have backed themselves into a corner. They must either continue down the path of slowness for their "partners" benefit or they must respond to the newer, faster systems that Apple and Linux offer people. More bang for the buck is what customers will want.

    They have a real uphill battle because their two main market drivers were the variety applications that were available and the control of hardware vendors, which includes drivers, discounts, or whatever other "agreements" they have.

    With Vista, there are driver and application compatibility issues just like there are with Linux (which is *much* less of an issue today). They are trying to toss away XP ecosystem and it puts them on a level playing field with other competitors. Suddenly, all the reasons for choosing Windows over Mac or Linux have disappeared!

    These are interesting times. Microsoft is having to compete with themselves as well as others :-D

    --
    Fresh horses and more whiskey for my men.
    1. Re:What about the hardware vendors? by Almahtar · · Score: 1

      Hardware suppliers have always counted on Microsoft to force people into buying a new system. If they design something that's optimized and competitive, they will lose their advantage and preferrential treatment by those vendors. Don't worry about that - it won't happen. The "microkernel" they're talking about takes 40 MB of ram just to boot to a text interface and run a minimalist web server. Damn Small Linux can boot to a gui with just 8. They never even mentioned whether or not they cut out the hardware detection and drivers for anything but VirtualPC on that model either.

      This system isn't optimized, it's just a small fraction of what makes up a full Windows install (no gui included in this one). If they hype how streamlined they are and back it up with 'demos' people will feel less comfortable accusing their software of being bloated. They're just trying to get a press pass to keep doing what they've been doing.
    2. Re:What about the hardware vendors? by pilbender · · Score: 1

      Yep. I know. I wholly agree with you. I'm a Slackware user so I'm pretty familiar with speed and efficiency. I'm using Opera too. I like things neat, clean, effiecient and fast.

      I'm not worried about anything Microsoft does anymore. I just don't care. It doesn't affect me. I would like to see a decrease in bot nets and spam tough. So, however slow and kludgy their next greatest system is, I hope it doesn't clog the internet with garbage because it's insecure.

      --
      Fresh horses and more whiskey for my men.
    3. Re:What about the hardware vendors? by smash · · Score: 1
      Back in the days of 386s this was the case.

      These days, modern hardware seems to die after 3 years or so anyway. no warranty = people need to re-purchase new hardware anyway.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    4. Re:What about the hardware vendors? by pilbender · · Score: 1

      You have a point to be sure. But that would mean that hardware vendors are no longer dependent on a Microsoft operating system release to drive sales. This is historically different than what we've seen in the past. Because of the long release cycle between XP and Vista I would say we probably have seen more people wear out their hardware than ever before.

      I personally have lots of hand me down systems that I use as far back as Pentiums. I generally use my stuff until it breaks and even then I still normally replace the component that went out. Alas, I realize I may be in the minority, but too often I hear people say, "I need a new computer because it's slow." People often think the reason is because it's old, but the real reason is they need to do a fresh install, clean our viruses, or delete programs that stay resident in memory for faster loading times.

      I can't tell you how many people I've convinced to clean up their systems, rather than buy a new one. Invariably they are gratefull too. Many people I know are keeping their systems longer than ever before and they are not tech people!

      --
      Fresh horses and more whiskey for my men.
  24. That's just sooo not gonna fly by melted · · Score: 4, Interesting

    Take it from a former Microserf - this "internal project" will be taken to the nearest corner and shot (and maybe also mutilated and spat on). When you have a huge turd of a codebase dating back 15 years in some places, the last thing you want to do is dramatically rehash it. Projects like this are DOA at Microsoft after the WinFS fiasco.

    1. Re:That's just sooo not gonna fly by suv4x4 · · Score: 3, Interesting

      Take it from a former Microserf - this "internal project" will be taken to the nearest corner and shot (and maybe also mutilated and spat on). When you have a huge turd of a codebase dating back 15 years in some places, the last thing you want to do is dramatically rehash it. Projects like this are DOA at Microsoft after the WinFS fiasco.

      I guess you didn't understand what they mean by internal. They won't commercialize the kernel itself. They have planned to, are, and WILL use this project to build Window 7 on.

      Unless you've missed that Microsoft has hit some hard limits in the way it managed its codebase and for 2-3 years now is spending heavily on analyzing the source code, separating the code in layers, modules, and removing dependencies between the modules.

      There's no other way forward.

    2. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      Yes, because Microsoft (or managers in general) always make the correct technical decisions.

      That project will be shot down by middle management at MS in a heartbeat. Here's an old Steve Jobs quote, which apart from the Sculley and Apple references, describes MS pretty well at the moment:

      "John Sculley ruined Apple and he ruined it by bringing a set of values to the top of Apple which were corrupt and corrupted some of the top people who were there, drove out some of the ones who were not corruptible, and brought in more corrupt ones and paid themselves collectively tens of millions of dollars and cared more about their own glory and wealth than they did about what built Apple in the first place -- which was making great computers for people to use."

      If version 1.0 worked perfectly, why buy version 2?

    3. Re:That's just sooo not gonna fly by melted · · Score: 3, Interesting

      You don't understand. This is not a way "forward". No one will approve anything that breaks backward compat. The guy who's in charge of Windows now is legendary for building a huge org (Office) one of the primary areas of excellence of which was work avoidance. They spend nine months "planning" to do three months of coding. At Microsoft getting Office to do anything for you is about as easy as getting a bear to ride a bicycle.

      Besides, what are you going to do with the code that's already built on top of the old kernel? Rewrite it? Deprecate it? Do you even begin to comprehend how difficult it is to do at this point if you want solid app compat (which I assure you is a top priority for Microsoft - they don't want to push folks towards Linux by making apps incompatible with the new OS).

      The only way forward now is to start over and do something other than same old NT and support NT as a subsystem a-la POSIX NT subsystem.

      Einstein said "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." This applies to Windows in its current state very well, and they are at the limits of their ability as it is. It's a heck of a lot easier to tangle something than untangle it.

    4. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0
      But you see this is all part of MS's plan. People are saying Vista is big, bloated and slow. So Microsoft claims the new (vaporware) Windows version will be tiny and fast.

      People think "Microsoft will fix my problems." They're wrong.

    5. Re:That's just sooo not gonna fly by Bryan+Ischo · · Score: 5, Insightful

      But Microsoft has soooooo much money. How can they not be able to do this?

      The thing that always amazes me about Windows is not how half-assed it is, but how half-assed it is given the amount of resources that Microsoft has to throw at the problem. You'd think that they'd have the money to fund tons of cool pieces of software to go with a Windows installation. I mean Windows Paint is a pathetic application that does almost nothing, a team of open source developers could better it in a week. But Microsoft doesn't improve it, or any of the utilities that come with Windows, nor does it ever add any really good or useful ones.

      That's just the start. Why didn't Microsoft implement some really awesome tools to assist with driver and hardware management? What they have is so basic! They have BILLIONS upon BILLIONS of dollars and this is the best that they can do?

      Honestly, Windows XP isn't terrible as an operating system; if you stick to simple stuff and don't expect too much, it can serve you well. But in terms of bang-for-the-buck, it must be the worst piece of software *ever*. Because if it's the best that a company can do with more money than most countries, well that just says that the company in question is pathetic.

      With the amount of money they have, I would think they could afford to fund 10 separate teams in parallel, each developing the next generation of Windows from scratch, and pick the best of the 10 when they're done. And yet they can't even muster enough skill to produce *one* decent next-generation product? What a bunch of losers!

    6. Re:That's just sooo not gonna fly by suv4x4 · · Score: 1

      Windows Vista broke some back-compat with old apps, Windows 7 is even a bigger departure. They do know it'll cause back compat issues.

      Code will need to be cleaned up and adapted. Either this, or they could instead ship 30 GB monstrocity with 40 years of collected garbage kept inside for back compat.

      And they know the time when this could possibly work ended with the release of Vista.

    7. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      Antitrust(or threats) from: (Not in any particular order)

      1. Adobe 2. Netscape (Because MS released a *gasp* better browser than the slow Netscape 3.x and the POS known as Netscape 4) 3. Norton/Mcfee 4. Lotus

    8. Re:That's just sooo not gonna fly by cyphercell · · Score: 1

      I see your point, but if I worked for Bill Gates, knowing what I know about software, I would expect more money than anywhere else. Personally, I blame microsoft at least in large part, for consumerism. The idea that you can foist worthless crap on people and if they have no other options, they will suck it right up.

      --
      Under the influence of Post-Cyberpunk Gonzo Journalism
    9. Re:That's just sooo not gonna fly by cliffski · · Score: 1

      If microsoft are a bunch of losers, I want to lose too, that way I can retire and buy my own island.
      You think their priority should be a new version of paint?
      I'm GLAD they aren't cluttering up the O/S with even more features. the idea of a stripped down low footprint O/S which lets you pick your own apps for stuff such as image processing is way better than a huge monolithic mess. They already have too much in the way of such crap as it is.

      --
      DRM-free indie games for the PC and Mac: Positech Games
    10. Re:That's just sooo not gonna fly by Aereus · · Score: 2, Interesting

      I personally love how XP and 2003 Server are still completely unhelpful in identifying what exactly you are supposed to be installing a driver for. I still have like 5 things that say "Unknown" under my Hardware manager that I have no idea what they are. They don't find any compatible drivers from any of my driver CDs or updates from their associated websites, and "Unknown" is patently unhelpful in discerning what they are.

    11. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      If MS wrote an amazing graphics app and packaged it with Windows, people would complain they were using their monopoly to squeeze Photoshop out of the market.

    12. Re:That's just sooo not gonna fly by Bryan+Ischo · · Score: 4, Interesting

      They aren't losers in the sense of making money, but they are losers in the sense of being poor engineers.

      No, I don't think the priority should be a new version of paint. You are completely missing the point. I am saying that with the resources Microsoft has, they should be able to produce a very, very good operating system, cutting edge and advanced in almost every way, and STILL have enough money left over to do things like update Paint. And after all that, still have $billions of dollars in the bank.

      If MS Windows came with a good image manipulation program, there still wouldn't be anything preventing you from buying a better one if you wanted to. And, if Microsoft didn't suck at writing operating systems so badly, it would be a very easy to set option to decide at install time what features you wanted and what you didn't.

      Are you saying that having NO choice is better than having SOME choice? Or that Microsoft's productivity *isn't* pathetic given their resources?

    13. Re:That's just sooo not gonna fly by skaet · · Score: 3, Interesting

      Yeah. That was the most mature comment I've read in a while.... "Throw all your money at it, Microsoft, the problem will fix itself!" Right.

      The thing here is not whether they have the resources to make a fantastic product (they have made some decent products when all things considered) but whether they have the management. You contradicted yourself when you said "... Windows Paint is a pathetic application that does almost nothing, a team of open source developers could better it in a week."

      So if OSS devs were to recreate MS Paint, assuming a minimal to non-existent budget, the obvious conclusion is that their product will blow since they put hardly any money into it at all... Notice the flaw there?

      Microsoft doesn't need "BILLIONS and BILLIONS of dollars" to reverse their history of bloated, buggy, unsupported, incompatible, insecure, closed-source code. They need management to care more about the product they are creating and direct the developers to stick to a standard and enforce it. Worst ever scenario is to cause a "Them and Us" mentality within the company and would be more disastrous for us - the consumer - in the end. Look where that ideal got Apple in the late '80s/early '90s...

      --
      There is no knowledge that is not power.
    14. Re:That's just sooo not gonna fly by fyoder · · Score: 1

      With the amount of money they have, I would think they could afford to fund 10 separate teams in parallel, each developing the next generation of Windows from scratch, and pick the best of the 10 when they're done. And yet they can't even muster enough skill to produce *one* decent next-generation product? What a bunch of losers!

      Not really. What they are is a corporation, and what they are primarily trying to produce is profit. And they've done very well at achieving their primary objective. What you are proposing is unnecessarily expensive, given that they can continue as they have been doing while raking it in. Better still, from their perspective, would be if they could halve the number of developers on the payroll while continuing to turn out the same shite. Multiplying the number of developers by ten would be just insane from the perspective of maximizing profits and minimizing expenses.

      --
      Loose lips lose spit.
    15. Re:That's just sooo not gonna fly by fwarren · · Score: 4, Insightful

      If one woman can make a baby in 9 months, surely 9 women can make a baby in one month?

      Even if an organization is flat. And everybody had their shit together and really knew their code.

      2 people have 1 path of communication
      3 people have 3 paths of communication
      4 people have 6 paths of communication
      5 people have 10 paths of communication

      Every person you have that needs to be in the know, adds to the complexity of communicating. Soon there is so much overhead nothing gets done but trying to stay up to date.

      Every "group" at Microsoft has this problem. The vista start button had one programmer working on it. This programmer had a beta tester, meetings with his manager. The manager had meetings with the UI manager, who had to share and work with his staff about how the button looked. The mananger also met with the systems manager, because his team actually had to plug the "shutdown" button into the code that did the shutdown, or hibernate. When it was all said and done. The programmer would make a change, and it would have to go through like 9 or 13 other people before it could be Ok'ed.

      All we are talking about here is ONE LITTLE BUTTON on a menu.

      Parkinson's Law "Work Expands To Fill The Time Available To Complete It"

      Parkinson correctly predicted that the British Navy would have more Admirals one day than they had ships. Due to people being promoted to fill all available space.

      Microsoft is so big. It can't trim back down to being lean and mean. Everything is done to much by committee to get anything important of quality done in a timely matter.

      As someone once said "God so loved the world, that he did not send a committee"

      Microsoft is it's own biggest competitor (Windows 2000 and XP competing against Vista and 7)

      Microsoft is it's own biggest enemy (death by committee)

      --
      vi + /etc over regedit any day of the week.
    16. Re:That's just sooo not gonna fly by Eighty7 · · Score: 1

      So if OSS devs were to recreate MS Paint, assuming a minimal to non-existent budget, the obvious conclusion is that their product will blow since they put hardly any money into it at all... Notice the flaw there?
      What? No, that doesn't follow at all. He only argued money should make a good product. He didn't say it's the only way to make a good product. Lack of it might or might not affect development - he didn't specify & you're putting words into his mouth.
    17. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      I have often wondered why Microsoft doesn't take a "throw money at it" approach to Windows development. An embarrassing surplus of money can even help in fixing bad management! For example, here is a strategy I think would work well: Fund 10 separate, completely independent teams to develop the next version of Windows. They all start with the current release but can take completely different approaches to technical decisions, development practices, management techniques, whatever. Then when it's time to release, do a bunch of testing, pick the best version, and ship it. Give everyone on the successful team a year's salary bonus. Throw the failed ones in the trash, mix up the failed teams and repeat.

      Yeah, it would cost a lot of money, but it's hard to put a price on maintaining a near-monopoly position in the desktop OS market. Furthermore, I believe this strategy would be effective enough that the individual teams would not have to be as large as the current development effort.

    18. Re:That's just sooo not gonna fly by nikanj · · Score: 1

      Three hundred permatemps with brushes will never reach the same level of art that one Michaelangelo does.
      And for some odd reason, the Michaelangelos don't want to work for Microsoft..

    19. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 1, Insightful

      Nope I doubt that will happen because of the broken system think about it-

      They update paint to be very good almost as much features as paint shop pro or even photoshop, and it comes free with windows. What do you think Adobe will say? I bet it goes along the lines of 'OH NO THEY ARE BUNDLING SOFTWARE! ANTICOMPETITIVE!'

      You can already see it, built in Anti Virus - nope Norton cries foul. Built in Media player - courts cry foul. Built in Internet browser - Netscape and everyone (even slashdot, cries foul).

      Microsoft is in between a rock and a hard place, if they add productivity software into windows someone out there is going to cry foul, and if they don't someone will criticize them.

      The thing is, if Microsoft adds more software to windows someone out there will cry foul and anticompetitive and the consumers suffer.

    20. Re:That's just sooo not gonna fly by Weedlekin · · Score: 1

      "Windows Vista broke some back-compat with old apps"

      It breaks far less stuff than XP did when it came out. The Win9X series ran most old software dating back to the DOS days, including drivers and stuff that wrote directly to the screen, because it had a version of DOS underneath that could bypass Windows completely when necessary. Compatibility with software and drivers written for 16 bit versions of Windows (e.g. Win 2.X, Win3.x) was also _much_ better than XP, which can be notably finicky (or downright impossible even after downloading Microsoft app compatibility toolkit) with software written for 9X and NT 3/4, let alone older Windows versions or DOS. Service Pack 2 also broke applications that ran fine under "vanilla" X or SP1 (including several Microsoft programs), thereby adding to the already impressive list of stuff that either didn't work at all or ran unreliably under XP.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    21. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      Speaking as a Microsoft engineer who doesn't work on Windows (on Office though)...

      Sure, I'm biased but the fundamental problem is not that there are poor engineers working on Windows. Having worked on smaller products in smaller companies in the past, it's easy to think it's just a question of financial or human resources. It's not though at this scale. After a certain point, the main problem becomes managing and coordinating all those resources.

      Productivity does not scale linearly (or even necessarily coordinate positively) with resources, particularly in terms of the number of people working on product. I don't think most people outside of Microsoft understand what it's like to work on a massively large team like Windows or Office. A huge amount of your time is spent coordinating with other engineers, planning and otherwise trying not to break something as opposed to just writing code.

      I don't know the exact numbers, but the Windows client organization has something like 2,000 developers alone. That doesn't even include all the program managers, testers, designers and a myriad of other people. That's 2,000 people writing new features, checking in bug fixes, etc. For example, on a small product in a small company, everybody typically works in the same source repository in the same branch. I've even worked at companies (crazy, naive startups) that had no formal source repository! With something like Windows, a dev breaking the build once every 2 years would have an excellent record considering he'd have about 2,000 other people checking in potentially conflicting changes all the time. However, with 2,000 people causing breaks at that rate, the build would be broken in several ways pretty much every day, which would means nobody could actually get any work done. This is not to say that's what actually happens. There are layers of process laid down to manage all of this--certain features done in branches that are integrated periodically, code review, lots of planning, triage meetings where decisions are made on which changes can be accepted. That process is time consuming though.

      That doesn't even include other coordination that needs to be done such as just deciding how features should interoperate, which features should even be done by whom, and so forth.

    22. Re:That's just sooo not gonna fly by doktor-hladnjak · · Score: 1

      Besides the obvious financial implications of this (try convincing your stockholders), this would be a huge morale killer. Who wants to work where there's a 90% chance your work will never see the light of day even if there's a 10% chance of a big payoff? Also, who decides which of the 10 is "the best"? The politics would be horrendous!

    23. Re:That's just sooo not gonna fly by Ash-Fox · · Score: 1

      If MS wrote an amazing graphics app and packaged it with Windows, people would complain they were using their monopoly to squeeze Photoshop out of the market
      I doubt the majority of people would complain. Also since when did complaining stop Microsoft?

      I remember when the European Union forced Microsoft to sell a version of Windows XP without Windows Media Player. The version of Windows XP that came without WMP costs more and nobody buys it.
      --
      Change is certain; progress is not obligatory.
    24. Re:That's just sooo not gonna fly by bjourne · · Score: 2, Insightful

      The thing that always amazes me about Windows is not how half-assed it is, but how half-assed it is given the amount of resources that Microsoft has to throw at the problem. You'd think that they'd have the money to fund tons of cool pieces of software to go with a Windows installation. I mean Windows Paint is a pathetic application that does almost nothing, MS Paint is a horrible example as that is one of the nicest tools Windows has. It is lean and cold starts up in less than a second. It is easy, you don't have to fiddle with layers just to draw a rectangle or some text. Notepad is the same, perfect if you want to paste some random junk och just check out a small text file. There is nothing quite like those tools on Linux, it seems like all utility programs just must have a Python scripting interface, modular toolbars, splash screens... Application startup suffers. But all image programs apparently just have to be the next Photoshop killer and all editors just have to have more features than Emacs.
    25. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      It's not really helpful, but the proper information is still there, but well hidden. In the properties of the device, under Details, there should be string like PCI\VEN_1234&DEV_5678... those are the PCI Vendor and Device IDs, you can look those up e.g. at www.pcidatabase.com.

    26. Re:That's just sooo not gonna fly by cliffski · · Score: 1, Insightful

      writing an O/S isn't exactly a simple task. writing an O/s with backwards compatibility for 5 or 6 other versions that go back over many generations of hardware, and supporting plug and play and doing all this when your system is the #1 target for malicious code writers has to be pure hell.
      I'm amazed that windows is as stable as it is, i can't remember the last time I saw a BSOD or similar.

      Its easy to criticise microsoft. unless you have developed a similar scale O/S with similar features, you are really in no position to judge. Its like me sitting in my chair at home moaning that NASA are idiots because their shuttles keep breaking. I haven't designed many reusable space vehicles, so I really have no perspective on the challenges involved.

      --
      DRM-free indie games for the PC and Mac: Positech Games
    27. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      My operating system history:

      First computer, in 7th grade: Apple IIe
      DOS 2.11
      DOS 3
      DOS 5
      Windows 98/Me (blah, yuck, pah...)
      Windows 2000
      Windows XP
      and this year: Mac OS X 10.4.10

    28. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      You have absolutely no idea what you're talking about. Microsoft is in a terrible position for a software development company. They can't do any of the things you suggest because of the disastrous consequences it would have.

      Don't expect super amazing MS Paint anytime soon because as soon as they release that they'll be sued like crazy. The same goes for any of their utilities. I'm fairly certain the only reason most of these utilities still exist is for compatibility reasons.

      They can't significantly change the way drivers are handled either. Just look at the amount of bitching going on regarding the minor changes made in Vista. It's been almost a year since it was RTM and hardware manufacturers still don't have their act together.

    29. Re:That's just sooo not gonna fly by Daengbo · · Score: 1

      Project management is a tough skill, and getting a bunch of geniuses with extremely high egos to all go in the same direction is even worse, but let's look at this objectively. Why would MS have 2000 developers working on the same codebase? That's the problem right there. The code is obviously not modular enough with well-enough defined APIs to break the development up.

      OSX is pretty similar to Windows in size and scope, yet Apple has few problems developing.

      The Linux kernel guys don't even communicate with the X.org, Mozilla, or Apache guys as far as I can tell. Everyone in that camp moves forward pretty much however they want to, just sticking to the API.

      Microsoft has the money and the intrigue to get the best project managers in the world working for them. I just don't think they have the culture to do it.

    30. Re:That's just sooo not gonna fly by nine-times · · Score: 1

      Throwing money at problems doesn't bring solutions. Lack of resources can prevent solutions from being developed, but excessive resources doesn't necessarily mean solutions will be developed.

      You can have thousands of developers working on a problem, but the problem won't be solved if those developers aren't managed properly. In fact, even if some small team of developers *do* solve the problem, the solution won't be implemented unless the management is smart enough to choose that good solution as their approved solution.

      Microsoft's problems have all the hallmarks of poor management, and most reports I've read of the internal workings of Microsoft confirms this.

    31. Re:That's just sooo not gonna fly by Anonymous Coward · · Score: 0

      The tradeoff to separating products into more modular parts is looser integration. Much of Windows' strength as a commercial product has to do with having tightly integrated features. It's both a strength in the marketplace and a weakness in the development process. One of the major reasons Vista took so long was due to delays caused by too many interdependencies. If Team A and Team B depend on each other, one falls behind when the other slips, which then causes the other to slip and so forth. Now, imagine that with dozens of teams with dependencies on each other.

      The problem is that Microsoft has backed itself into a specific business model that relies on complex products with lots of tightly integrated features. It's difficult to change that now and all but impossible on a monolithic suite like Office.

      Having good project managers is not necessarily the answer though either. In the end, you have get all the development staff on board to get the product done. I'm convinced as a Microsoft employee that a cultural change would be necessary to achieve that.

    32. Re:That's just sooo not gonna fly by nuzak · · Score: 1

      The thing that always amazes me about Windows is not how half-assed it is, but how half-assed it is given the amount of resources that Microsoft has to throw at the problem.

      Actually, it's not surprising. It's probably some kind of corollary to Brooks' Law, but at a certain point, more resources don't help, and in fact make it worse.

      MS actually does have some pretty nice command-line tools for dealing with drivers, like DevCon. It'd sure be nice if it came with Windows, but truth is that for the average userbase, it'd be like handing chainsaws to paraplegics.

      I do find it odd how they just refuse to update things like paint or notepad. You know that's gotta be a frequent request from customers.

      --
      Done with slashdot, done with nerds, getting a life.
    33. Re:That's just sooo not gonna fly by Daengbo · · Score: 1

      I agree with your last line. That's part of what MY last line was about. MS has huge amounts of talent at their campuses. I know some people here like to insinuate that the developers there don't know what they're doing, but I never think that at all. They've got some super minds there (though more and more, the smartest are working for others like Google).

      Never having worked at MS and only having listened to insiders talking about it, I get the feeling the culture just doesn't support agile development. By agile, I mean it in the generic sense, not in the development model sense. They'll have to make a change eventually. They have tons of money and time, so that change could take a while and still not kill them, though.

    34. Re:That's just sooo not gonna fly by Bryan+Ischo · · Score: 1

      Those are very good points, and very well presented.

      However, although I did not mention this explicitly:

      a) I am a software developer and am intimiately familiar with the problems you are talking about
      b) I already took all of that in consideration in my rant

      Yes, what you say would be a big problem for Microsoft. But even given that, they still do a pretty piss-poor job given what they have to work with.

  25. This is step one. by thatskinnyguy · · Score: 3, Interesting

    Good. Small kernel is a good start. Now make it open source and let me install whatever the hell I want for a desktop manager and applications on top of it.

    I've been saying it for years now. Windows should either be an open standard for operating systems to be built or be a desktop manager built on a Linux kernel. Of course, then what would the diehards bitch about on slashdot?

    --
    The game.
    1. Re:This is step one. by Joaz+Banbeck · · Score: 2, Funny

      ...then what would the diehards bitch about on slashdot? The editors, of course.
    2. Re:This is step one. by Nicolay77 · · Score: 1

      Food and rent should be free wherever I go.

      I've been saying it for years now. Of course, then what whould the bums ditch about on... mmm... some public park?

      --
      We are Turing O-Machines. The Oracle is out there.
    3. Re:This is step one. by r_jensen11 · · Score: 1

      We don't need another DE! We have enough flame wars as it is. What, with *box, Enlightenment, Gnome, KDE, and those damn bastards who claim command line is superior.

    4. Re:This is step one. by systemBuilder · · Score: 1
      == I've been saying it for years now. Windows should either be an open standard for operating systems to be built or be a desktop manager built on a Linux kernel. ==

      This is rather hilarious. Are you saying that Linux is something other than an open standard for operating systems ?? I personally think Linux is an open standard - like a garbage disposal - and the way you win at Linux (the MIT way, actually) is to write the largest piece of software you can and do not document it according to any particular standard. In fact, every manpage for Linux should follow a slightly different format, and it does ...

      Remember, it's coherence that lets light reflect off of a surface and lets me see it.
      Coherence is not something that linux developers ever have to worry about!

    5. Re:This is step one. by gardyloo · · Score: 1

      Remember, it's coherence that lets light reflect off of a surface and lets me see it. No. No it's not. If light were monochromatic, you might (I stress *might*) have a point. But sunlight (e.g.) isn't, and you don't.
    6. Re:This is step one. by moosesocks · · Score: 1

      Um. No. The NT kernel is generally regarded as being extremely solid. You'd be an absolute idiot to run the Win32 shell on top of the Linux kernel. The NT kernel is at the top of a very small list of the the few things Microsoft's done right. It's also one of the most recently developed kernels in widespread use. (OS X/Mach and Linux, though both innovative are evolutionary updates to a very old system)

      However, I do like the idea of open-sourcing bits of the OS to any paid and licensed end-user. RMS's whining about a free-as-in-speech kernel are impractical and counterproductive. Getting a peek inside the NT kernel would be extremely enlightening, and would allow developers to better tune their applications to the OS, and find security flaws (to be fair, most of those occur far above the kernel level).

      Likewise, Internet Explorer and the explorer.exe shell should both *definitely* be open-sourced, as they've both been extremely buggy for the entirety of their existence. At the moment, all of the desktop shells leave much to be desired -- Explorer is insecure, and prone to crashing -- it peaked around Win2k, and has been going downhill since, which is a shame because it's generally very *fast*. X11 is rapidly improving and evolving into something modern and desirable (and about time!), but KDE and GNOME still have a ways to go in terms of Usability -- I absolutely adore XFCE, but realize that it's not for everyone. The OS X shell is stable, fast, and secure, but suffers from somewhat poor latency, and the Finder needs to be completely revamped (and properly multithreaded!!!).

      Vista had some fantastic features going for it. If WinFS were the first to market, they could have gained a enormous competitive edge. Instead, that got cut out in favor of a myriad of features that the market has demonstrated that it doesn't want.

      Microsoft needs to rewind the past 7 years (kind of like our Government, but I digress...), Open-Source the Explorer shell, keep it simple, but gradually build it up. Make absolute sure that IE goes open-source, and let the community have input into it. Like so many other things MS does, IE7 was a big improvement in many ways, but also misses the mark completely in terms of the user experience (which is the general concensus I get from everyone who's used it). Firefox *is* the better product, and Microsoft needs to distinguish itself from it in a positive manner.

      Once you've got a fast, modern, lightweight shell, start emphasizing new and unique features within the core operating system, especially with regard to the Filesystem; Metadata is the future, and the first OS to properly implement it will be wildly successful. I'd even wager that Windows would be particularly well-suited to the task. Heck... if we're going to be audacious, consider implementing ZFS, with Time-Machine-Esque functionality built in.

      Hopefully, they'll learn from their mistakes. I love my Linux Box, and I love my Powerbook. However, it's great to see some competition.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    7. Re:This is step one. by doshell · · Score: 1

      And yet again someone misses the difference between free as in beer and free as in freedom...

      (P.S. I'm not saying I agree with the GP; but he was talking about freedom, not beer.)

      --
      Score: i, Imaginary
    8. Re:This is step one. by Nicolay77 · · Score: 1

      Don't be silly. In this case that difference doesn't matter at all.

      I'm talking about getting the richest company in the world to lose a huge part of its assets, and in consequence a big chunk of its money.

      If you think that's possible, good luck talking to Ballmer.

      --
      We are Turing O-Machines. The Oracle is out there.
  26. MS doesn't control the hardware by Anonymous Coward · · Score: 0

    If they did control the hardware with Apple's rigidity, you'd be running a very stable and safe version of Windows right now. You'd be paying a little premium (as you do with Apple) for the hardware, and the experience would [likely] be similar.

    The problem is that Microsoft puts out software that accommodates everything from generic video cards to 16-bit legacy programs. They try to please everyone, and succeed in pleasing very few people.

  27. die !!! by unity100 · · Score: 0

    you bastard !!! knocked me off the chair in the dead of the night.

    worth losing some karma

  28. Ouch. Don't do it. by russellh · · Score: 3, Insightful

    Until the next great advance in OS technology, the kernel, the core OS is a solved problem by modern standards. Microsoft should build windows around the linux kernel and be done with it. they could refocus their huge resources toward all the great stuff they have cut out in the past. Even the massive wealth of Microsoft can barely compete with their proprietary system against open source developers. Why waste so much time on security issues when the answer is just there for the taking? Of course, they will never do it without a massive shakeup. it's just too threatening. This is their downfall, eventually, at least insofar as platform domination goes. they still have shifting proprietary file formats and forced upgrades, though, at least. what a business.

    --
    must... stay... awake...
    1. Re:Ouch. Don't do it. by Anonymous Coward · · Score: 0

      ... the kernel, the core OS is a solved problem by modern standards.

      You might want to inform Linus and friends of that. It would save them much work, I'm sure.

    2. Re:Ouch. Don't do it. by Chili-71 · · Score: 1

      russellh wrote on Thursday October 18
      Microsoft should build windows around the linux kernel and be done with it.
      There are a lot of really neat ideas posted on /. and find this one to be one of the best. Microsoft could do a lot for the compute world by using a Linux kernel. But alas, the problem then becomes one of protecting (hording) their applications so they won't run on other Linux distros. For example, they have time and resources to develop a really knockout app that everyone needs/wants only to find that it is easily converted to run on SuSE or Ubuntu - oops, sales of the app take a nosedive and they can't recover their R&D.

      Fantastic idea, but in Microsoft's eyes, not viable. They need a convoluted, obscure operating system that their apps will only run on.
  29. Hmmm new Windows Hasta La Vista! by AmigaMMC · · Score: 1

    I wonder what the new features are going to be... New GUI, more security (meaning asking user confirmation every time the user presses a key), Installation on 6 Blue-Ray Double Layer and an 8 core Processor 4Ghz, 16GB RAM minimum requirement... Microsoft should stick to making Xboxes only, that's the only thing they do right.

    1. Re:Hmmm new Windows Hasta La Vista! by deftcoder · · Score: 1

      that's the only thing they do right.
      You consider 33% of a company's produced systems being defective to be "doing it right"?!
      --
      Peace sells, but who's buying?
    2. Re:Hmmm new Windows Hasta La Vista! by AmigaMMC · · Score: 1

      well, when you compare it to 100% of their OS doing it wrong I'd say 33% is damn close to being right :) (...and I'm not a Mac user, before I get flamed for flaming Win)

  30. Virtualised Legacy by Kenshin · · Score: 5, Insightful

    Legacy support can easily be virtualised. That's how Apple managed the jump from OS9 to OSX (the "Classic" environment was launched on-demand), and that's how Windows 7 should be built.

    Sure, legacy apps will run marginally slower, but new apps will be free of the built-up cruft.

    --

    Does it make you happy you're so strange?

    1. Re:Virtualised Legacy by batkiwi · · Score: 1

      Third party vendors already have enterprise solutions for this, it's only a matter of time until the same thing is available for individual PCs.

    2. Re:Virtualised Legacy by Anonymous Coward · · Score: 0

      "Legacy support can easily be virtualised."

      Yes. Writing Classic was a piece of cake.

    3. Re:Virtualised Legacy by Anonymous Coward · · Score: 0

      No, it doesn't.

    4. Re:Virtualised Legacy by Anonymous Coward · · Score: 0

      First of all, Apple can do whatever the hell they please. Since they're a cult, their followers will do whatever Apple tells them to do. Second of all, there are precious few mission-critical enterprise apps running on OS9. Third, Apple is the only company that can make Macs. All they had to do is stop making computers and peripherals that were capable of booting OS9, and people had to stop using it. There's no way MS can force computer manufacturers to stop making computers that will boot old versions of Windows.

      No, full OS virtualization works fine for a whole legacy server, but is only a last-ditch effort to make legacy apps usable. In real life that doesn't work because apps lose their ability to integrate with the rest of the system.

      How does my legacy browser plugin work with the fancy new browser? It can't.
      How does my legacy command line app pipe output to my fancy new app? It can't.
      How does my legacy scripting language create fancy new processes? It can't.
      How does my legacy app use devices that don't have drivers in the VM? It can't.
      How does my legacy app share memory and semaphores with my fancy new app? It can't.
      How does my fancy new screen scraper control my legacy app? It can't.
      How does my fancy new web server run legacy CGI scripts? It can't.

      Of course, you don't have to virtualize the whole OS, you could virtualize just the API. This is how DOS and Win16 apps run on Windows now, and is why your Win32 command line apps can pipe output to DOS apps, Win16 apps can send messages to Win32 apps, and so forth. This is certainly the ideal way to do things, but it doesn't eliminate legacy cruft from the modern codebase.

      For example, let's say the window manager always sends messages W, X, Y, and Z (in that order) to new windows, regardless of whether those messages really apply to all windows. You may decide that message W is not always needed, and can sometimes be left out as an optimization in the new streamlined window manager. Unfortunately you will find that stupid programmers have noticed that they always get W before any other message, so they put initialization code in the W message handler, causing the mission-critical legacy app to fail when running under the new streamlined window manager. The solution to this is to have the window manager check to see if the new window is running under the legacy VM and send the messages in the correct order if it is. Great! Now we're *adding* cruft in our attempt to eliminate cruft!

      dom

    5. Re:Virtualised Legacy by Anonymous Coward · · Score: 0

      The absolute worst thing MS could do would be allowing all apps to run virtualised. What if Ubuntu 7.10 or Mac could run any native Windows app in a nice little virtual environment that Microsoft gets running for their next version??
      Once windows creates a nice abstraction layer above all their hooks (like .Net is supposed to be) any program should be able to run on any compatible hardware.

    6. Re:Virtualised Legacy by Anonymous Coward · · Score: 1, Insightful

      i'm sorry, but have you ever tried supporting some legacy systems? When a systems been around for 16 years, it's been so for a reason, and a damn good one. I've seen:

      - Legacy systems requiring serial dongles as a means of copy protection which for some reason isnt working during virtualization. This was for a fire maintenance company (the software was modified from a boat maintenance company). The original installer charged them 10 grand to retrofit and setup the initial software. They've built 10 years of customer records on it. Legacy support is thier lifeblood.

      - I've seen legacy systems which control hardware devices that use proprietary cards which interop in ways that baffle me. Think ISA cards....virtualization just isn't possible.

      - Networking systems running proprietary protocols over token ring. Maybe this can be worked around, thing sure weren't looking good though..

      If you're in a software only world, then sure, the guy using access 97 or whatnot can be virtualized and move on. But I've seen some pretty hairy setups. Whenever you see 'decades old systems', think about everything else thats probably not had IT budget to get updated...printers, networks, even scanners.

      I'm not saying any of this is smart/dumb/right/wrong. Just providing some insight to the greater problem at hand. Of course, any customer that's been on these systems that long is probably not caring about what windows 7 brings, so I kinda mod this entire post as -1 offtopic :)

    7. Re:Virtualised Legacy by Burnhard · · Score: 1

      Legacy support with virtualisation will only be slower if you are running the new environment on the same old hardware (in theory).

    8. Re:Virtualised Legacy by Bert64 · · Score: 2, Informative

      There are even some companies with legacy systems tied to Amiga hardware... Using the proprietary Zorro bus. When these machines die, there are no replacements, not even any compatible replacements.

      The companies who originally chose these systems, the Amiga based devices, and the customer records database you talked about, made a huge mistake in selecting proprietary technology, and are now paying the price. You'd think enough time has passed for the industry to mature, but people are still choosing proprietary tools with no thought for the risks in the future.

      Luckily proprietary hardware is all but dead, and hopefully software will go the same way.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    9. Re:Virtualised Legacy by Anonymous Coward · · Score: 0

      Not to mention OSX PPC to OSX Intel with Rosetta.

  31. Small kernel, only for now by unity100 · · Score: 1, Troll

    Its to be inflated with drm crap later. 2 years of Riaa lobbying should be able to get it to 5 Gb ram requirement level. Of course, it will need a cluster of 2 pcs for cpu power - for the new "On Live Demand DRM®" feature.

    1. Re:Small kernel, only for now by smash · · Score: 3, Insightful
      Seriously, just how big do you think the DRM subsystem is in terms of code?

      Given that all it does is check encryption keys and decrypt data - i would wager it could be done in the equivalent of 1-2 lines of Perl. I've noticed no real speed difference between XP and vista on an old 2.4ghz non-ht PC. That machine is 5 years old.

      The "bloat" in windows is things like:

      • compatibility with 16 bit windows apps
      • window toolkit
      • activeX object library
      • .net runtime environment
      • directX
      • etc

      I like linux/bsd as much as the next guy, but you'll notice that as they begin to get feature parity with windows, the "bloat" is going up in them as well.

      When putting out an OS you have a choice: do you provide just the bare minimum of services (useful for embedded apps), or do you provide a complete OS including graphics libraries, 3d graphics libraries, various programming widgets, etc?

      Is Windows bloat free? Of course not. However, when RAM costs I'd much rather be running FreeBSD full time, but it's not because of the bloat - it's because of the user environment - windows treats you like a fucking retard, and it's irritating... but for the apps most people want to run/develop, it's a fairly usable platform.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:Small kernel, only for now by smash · · Score: 1
      sigh...

      Is Windows bloat free? Of course not. However, when RAM costs I'd much rather be running FreeBSD full time, but it's not because of the bloat - it's because of the user environment - windows treats you like a fucking retard, and it's irritating... but for the apps most people want to run/develop, it's a fairly usable platform.

      What i meant to say was "when ram costs $100gb, disk costs $200/500gb, and cpu is cheap - what's the point" but it went missing...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    3. Re:Small kernel, only for now by unity100 · · Score: 1

      In case you noticed, its the cpu power need that is making a cluster necessary in my example.

    4. Re:Small kernel, only for now by GnarlyDoug · · Score: 1

      If we're talking performance, it's not always the amount of code, but the nature of the code. A couple of lines of code in the wrong place can reduce effeciency by magnitudes of order. I bet the DRM code is not large in terms of lines of code, but I bet it's placed in critical locations all over the place. Even the overhead of making function calls can dramatically impact high performance loops.

    5. Re:Small kernel, only for now by makomk · · Score: 1

      The amount of code required to check keys and decrypt data may be small. The real killer is the code to throw off reverse engineering attempts, detect debuggers/code modifications, prevent interception of the data, etc, etc... and remember that, for robust protection, this has to be done at every layer the data passes through.

    6. Re:Small kernel, only for now by smash · · Score: 1

      Agreed, but fact remains in real world performance terms, i have noticed no difference (XP vs vista, on hardware purchased since 2002), so the overhead of what actually gets run, unless you're dealing with DRM content, appears to me, to be minimal.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  32. why troll parent by unity100 · · Score: 2, Insightful

    This exactly coincides with the time major pc sellers started providing Xp again. please, use your mod points visely.

  33. There's no bloat... by suv4x4 · · Score: 1

    The demo shows the very kernel and command line of Windows is something like 25 MB, and takes 14 MB of RAM.

    Can't help but thing this doesn't fair well to Linux and BSD which have mostly the same features (or alternative).

    DamnSmallLinux is 50 MB but that goes together with the: graphics subsystem, deskop, media player, ftp client, email, spreadsheet, firefox, graphics editor... etc. etc.

    The demoed MinWin here can't display a picture to save its life (except in ASCII) and contained just a very basic HTTP server that spews the task list back to a browser.

    But those little things don't matter anymore on the desktop, and with Penryn and future advancements in the x86 platform, they won't matter on the mobile devices either. Just I hope they manage to componentize the entire Windows environment this way. It'll mean much higher quality code, easier back compat, and much more predictable behavior of future Windows releases.

    1. Re:There's no bloat... by Anonymous Coward · · Score: 0

      Just I hope they manage to componentize the entire Windows environment this way. It'll mean much higher quality code, easier back compat, and much more predictable behavior of future Windows releases. ...and subscription based components. Yes, I'd like to pay an additional $10/month for DirectX. Yes, I'd like to pay an additional $10/month for networking. Yes, I'd like to pay an additional $10/month for media playback. Yes, I'd like to pay an additional $10/month for support for removable storage. Yes, I'd like to pay an additional $10/month for dual-head and multiple workspaces. Please, take my money!
    2. Re:There's no bloat... by wellingj · · Score: 1

      At least it won't be as hard for MS to not bundle shit (like web browsers and media players) with the OS. Should make the EU happy.

    3. Re:There's no bloat... by Anonymous Coward · · Score: 0

      Wait a sec! If Linux and all kinds of apps fit in 50MB, why is Debian 3 freakin' DVDs?!?

      Oh, probably for the same reason that a minimal XPe install is 40MB, but Vista is a whole damn DVD.

      dom

    4. Re:There's no bloat... by Ash-Fox · · Score: 1

      Wait a sec! If Linux and all kinds of apps fit in 50MB, why is Debian 3 freakin' DVDs?!?
      Debian's FAQ explains that you don't need all the CDs, DVDs.

      Additionally, you don't need to grab multiple DVDs/CD images if you just want a single rare package... Debian's package managers let you download the software directly from the internet.

      Oh, probably for the same reason that a minimal XPe install is 40MB, but Vista is a whole damn DVD.
      I didn't see much software included with Vista. Not even a office suite or even a decent text editor.
      --
      Change is certain; progress is not obligatory.
    5. Re:There's no bloat... by crimperman · · Score: 1

      Nah they'd [let|make] the OEMs install time-limited versions[1]. So you get IE for 60 days and then start paying once you're "hooked" and if you've forgotten to download Firefox before the 60 days are up...?

      [1] You know, kinda like they do for Office 2007 now.

  34. Maybe... by noz · · Score: 2, Insightful

    Maybe then someone at Microsoft will know how their process scheduler works.

  35. Other MinWin by dhasenan · · Score: 1

    I take it they're not referring to this MinWin?

  36. I swear: by xactuary · · Score: 0

    When Windows 8.6 arrives... I'm outa here.

    --
    Say hello to my little sig.
  37. codename... by sjs132 · · Score: 1

    Smaller memory foot print... maximized kernel... I think the codename will be "linux"

    "dont worry Bill... we'll realease it under our new OSS license and we'll get money for other people writing the code. We just have to include a 5 DVD's of source with every purchase, and Piracy will drop to 0% and our support income stream will increase 500 fold."

    --
    --- Relax, that mass muderer is just trying to reduce our carbon footprint, one fetus at a time...
  38. New File System by Anonymous Coward · · Score: 0

    And it is going to have a brand new type of file system called WinFS that is really a database! It has never been done before! It's true. Microsoft has been trying since Cairo an has yet to actually do it.

  39. Link down? by TaeKwonDood · · Score: 1

    And I can't find a cached version of it anywhere.

    1. Re:Link down? by Anonymous Coward · · Score: 0

      And half of those '300' features are copied from Vista, you have quite a sense of humor.

    2. Re:Link down? by TaeKwonDood · · Score: 1

      Oh sure, exploit the newbie. But that's funny stuff.

  40. MS has a history of "skipping" for parity's sake by AlexPlooy · · Score: 1

    Iirc, NT started at version 3 (maybe even 3.5) to keep up with the numbering convention of "everyday" Windows at the time (Windows 3). They've employed that practice several times now. Case in point would be the Office apps: Word for Windows jumped from v2 to 6 to get "in front" of Word 5.1 (DOS and Mac); Excel skipped v6 entirely; Access went from v2 to 7... so whatever way you look at it, counting the MS way can always be a little unusual should they so desire. We could add to the confusion by mentioning the difference between Win16, Win32 and Win32s back in the day, but whatever.

    They're not the only company to do so, but historically they seemed to be one of the more regular offenders. :-)

    --
    Are you really sure a floor can't also be a ceiling? - M.C. Escher
  41. I thought this headline was about by nickrout · · Score: 3, Funny

    gentoo's portage system being ported to windows... emerge outlook

    1. Re:I thought this headline was about by Anonymous Coward · · Score: 4, Funny

      USE="clippy" yay!

    2. Re:I thought this headline was about by TeknoHog · · Score: 1

      emerge: there are no ebuilds to satisfy "=sys-kernel/windows-7".

      --
      Escher was the first MC and Giger invented the HR department.
  42. virtualization by saleenS281 · · Score: 1

    that's why we have virtualization. So we can cut those ties completely, and allow them to run it in a virtual server. With the power of hardware today, even virtualized, the apps should smoke the crap out of the speed it ran 16 years ago.

  43. Classic Oxymorons by DaveAtFraud · · Score: 3, Funny

    Jumbo shrimp
    Military intelligence
    A new classic
    Efficient bureaucracy
    Peace force
    ...
    MinWin

    Cheers,
    Dave

    --
    They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
    Ben
  44. Awesome! by swillden · · Score: 2, Funny

    Honesty, and I'm not trolling here, but this looks pretty scary. This reminds me of driver-signing gone awry. I don't see the potential for open-source/free modules due to item #3. Arbitrary application, memory, CPU, and process limits are also concerning.

    That rocks! Windows 7 will finally provide that last push needed to rocket Linux into the mainstream!

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  45. Can it be like Star Trek? by CleverScreenName · · Score: 4, Funny

    Every odd Windows Version being good?

    1) Windows 3.1?
    2) Windows 95
    3) Windows 98
    4) Windows Me
    5) Windows XP
    6) Vista
    7) First Contact?

    1. Re:Can it be like Star Trek? by ksm2552 · · Score: 1

      Forget about Win2000? Though I would give you that XP is basically Win2000 2nd Edition.

    2. Re:Can it be like Star Trek? by CleverScreenName · · Score: 1

      I did. At least I tried!

    3. Re:Can it be like Star Trek? by San-LC · · Score: 1

      Star Trek 7 was Generations. And ew.

    4. Re:Can it be like Star Trek? by Anonymous Coward · · Score: 0

      I don't know if anyone else recalls this, but the media hype codeword for Windows 95 was "The Next Generation."

  46. They oughta Apple it... by i.r.id10t · · Score: 1

    They should pull an Apple and take a BSD and use that as a base to start over....

    --
    Don't blame me, I voted for Kodos
    1. Re:They oughta Apple it... by deftcoder · · Score: 1

      Please make them stay away from OpenBSD! They can have NetBSD or one of the less popular ones.

      --
      Peace sells, but who's buying?
  47. How about they deliver Longhorn? by r_jensen11 · · Score: 1

    Let's start with that, since clearly Vista is in and of itself a beast completely independent of Longhorn.

  48. The Microsoft secret to success by jmorris42 · · Score: 5, Informative

    > So Microsoft tells something about the next version of Windows not long after the people
    > have noticed that their current version isn't all that it's made up to be?

    Duh. They have been doing this same bait and switch for the life of the company.

    Step One. Release wonderous New Version! It is THE must have thing.

    Step Two. Everyone realizes it sucks but their money is already in Bill's pocket. And everyone realizes they have no choice but to adopt the new product anyway because of the three year hardware replacement cycle and the illegal (as certified by a US court) bundling agreements with the OEMs that continue to this day. Especially in the case of their OS but to a lesser extent with Office and the other crap they peddle.

    Step Three. Microsoft begins hinting about the upcoming new version. It will fix all of the (not quite admitted) problems with current version AND add exciting new must have features. And it is coming Really Soon.

    Step Four. Have their minions in the trade press obsess about Upcoming new version. All complaints about Current version are answered with "But Upcoming version will be out soon and will fix that problem." After a year or two make sure to begin writing reviews for competitors products by comparing them to features that Upcoming version will be shipping "Any day now". By this point EVERYONE must be lamenting how crappy the shipping version is to help generate the NEED to upgrade when the new version ships.

    Step Five. As the death march to release continues and feaures get cut, spin it as a good thing. (We are focusing on the needs of our customers, blah, blah.) Now that there is beta (anyone else would rate it pre-alpha but.....) code get the drumbeat ramping up in the press with lots of articles and screenshots. Will your hardware be compatible? Can life as you know it continue without the exciting new features? Etc, blah blah.

    Step Six. The product finally releases... See Step One.

    --
    Democrat delenda est
    1. Re:The Microsoft secret to success by 2ms · · Score: 2

      Step Six occuring at bare minimum 3 Years later that originally claimed.

    2. Re:The Microsoft secret to success by W33B · · Score: 0

      Step Seven....Profit!

    3. Re:The Microsoft secret to success by davotoula · · Score: 1

      Step six IS step one...

    4. Re:The Microsoft secret to success by kaizokuace · · Score: 1

      You might have forgotten the "???" and "profit!!?" steps. ;p

      --
      Balderdash!
    5. Re:The Microsoft secret to success by Anonymous Coward · · Score: 0

      Wait a second! where's "STEP N: profit!!!"?

      Step Two. Everyone realizes it sucks but their money is already in Bill's pocket.


      ahhhh... here it is.

    6. Re:The Microsoft secret to success by Saint+Stephen · · Score: 1

      Step 1b: Guy writes post outlining steps 1-6, nothing changes.

    7. Re:The Microsoft secret to success by garatheus · · Score: 1

      You forgot step seven... PROFIT!!!

    8. Re:The Microsoft secret to success by fropenn · · Score: 1

      This sounds to me like the typical cycle for any product development process in any company in the world. Have you ever purchased a car only to see a "improved, better, faster" model come out the next year?
      I guess I don't see how Microsoft is different (other than near-monopoly status) than any other company or group that is out to make a profit.

    9. Re:The Microsoft secret to success by Anonymous Coward · · Score: 0

      of course! and what better place to begin the massive campaign of misinformation than a guest lecture in a college classroom. I agree - clearly a brilliant and complex tactic to mislead the public - ohhhh, how devious. Amazingly, they've released horrible products this way for more than a decade. Stupid consumers keep buying the products while only jmorris42 has managed to figure out the scam. Good work jmorris42!

  49. Eegah! by amccaf1 · · Score: 1

    "MinWin," designed to optimize the Windows kernel to a minimum footprint


    Why is it I get the feeling that Window's minimum footprint and Bigfoot will have something in common...?
    --
    "Flag on the moon. How did it get there?"
  50. Re:Better than vista? by Anonymous Coward · · Score: 0

    That story is either fake, or you tried clicking Vista's 'add printer' button with a baseball bat.

  51. Windows NT DID have a Microkernal by tjstork · · Score: 1

    Everything moved into userspace that possibly can (Usually only threads, IPC and address spaces are left in kernel space). (This is a true microkernel.).

    Windows NT 3.1 (the first version) was a fairly purish microkernal. Microkernals came from the CMU Mach Project, and, when David Cutler was tasked for first developing WNT, he turned around and got as many key mach players as he could to come work for him.

    Over time, MS has been shoving things into the kernel - this is because people complain about performance. For that, to this day, there is a crowd of people that says that WNT Daytona (3.51), was really the best Windows NT - as NT 4 moved GDI into the kernel. I think now, with the new driver model under Vista, a lot of stuff is being moved out of the kernel and back into user space, bringing Vista more back to its roots.

    --
    This is my sig.
    1. Re:Windows NT DID have a Microkernal by JonJ · · Score: 1

      Moving drivers to userspace does not a microkernel make. Or are you suggesting Linux is a microkernel? And even though Cutlers first goal was to make a microkernel, too much resides in kernel space, and ntoskrnl.exe links the kernel and the executive together anyway.

      --
      -- Linux user #369862
  52. Foot print.. by agendi · · Score: 1

    They are going to start using Gnome? ;)

    --
    I just can't be bothered.
  53. Necessity by IGnatius+T+Foobar · · Score: 2

    Seriously, this is really the only option for Windows at this point. Anyone who has seen the Windows source code has said that it's an unmaintainable jumble of subsystems that they're having a lot of difficulty continuing to wrap their heads around.

    Microsoft sees what the open source folks are doing -- building quality operating systems around loosely coupled modules with separate developer teams and clearly defined interfaces -- and has decided "oh yeah, Windows should do that too." Of course it's a good idea. Microsoft steals from the best. Ironically, they'll patent it too.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  54. Re:ah! just in time by GaryPatterson · · Score: 2, Informative

    Mod parent to +11 'insightful reference to history'

    It's a common tactic from Microsoft. When there's nothing to say and a competitor may get some PR from a tech media looking for something to write about, come out with something about a product that's on the drawing board, or is only marginally closer to release than the drawing board.

  55. Re:Virtualised Legacy - duh! by BlackSabbath · · Score: 1

    Please mod this guy up!
    With virtualisation tech going the way it is, taking this approach should be a no-brainer. There may be a performance hit but the potential for sandboxing that this approach offers may actually make running legacy apps in this way SAFER than using the original OS or building the same old cruft into the core of the new OS.

    I seem to recall that Microsoft Research was working on an OS based on similar sandboxing concepts - Singularity http://research.microsoft.com/os/singularity/

  56. If anyone can do it, it's Eric Traut by benmartz · · Score: 1

    Eric is one of the brightest engineers I've ever had the privilege to work with. Some of you may remember him from the Connectix days. If anyone can make this work, he can and this would be a very positive development for the platform.

  57. Makes sense to me by rmcd · · Score: 1

    The antitrust complaint about Microsoft has been that everything was bundled in Windows. Isn't this what the antitrust authorities want them to do? Isn't modularity one of the things that's great about Linux? An unbundled commercial OS would allow Microsoft to have a stripped down version to compete with OLPC, and home and business versions that charged by the feature. You don't want eye candy, you don't pay for eye candy. Not a gamer, you don't pay for DirectX. In theory it seems like a great way to tell developers what to work on (you'll see which features folks are willing to pay for) and a way to offer cheap versions of the OS for the folks that just want e-mail/browsing and expensive versions for those who want everything. You're thinking that they'll try to charge a lot, but really, how much worse could it be than what we have now? Most users pay microsoft a lot every few years.

    Now this may be a technical and end-user nightmare, I don't know, but trying to develop an a la carte OS makes a lot of sense to me as a business move.

    The same thing is starting to happen with cable more extensively than before: you don't want ESPN or the NFL, you shouldn't have to pay for them.

  58. A good way to enter setup on fastboot BIOS by RCSInfo · · Score: 1

    I don't know if this works across the board, but I've had luck with holding down several keys when powering on the system. This caused a POST keyboard error and gave me time to enter the bios setup.

    1. Re:A good way to enter setup on fastboot BIOS by CSMatt · · Score: 1

      Thanks for the tip, but I've already gotten it taken care of. :)

      I suppose I could have also unplugged the keyboard before turning the PC on so as to get the same error. Easier than pressing all those keys at the same time in my opinion, although that of course wouldn't have worked for a laptop.

  59. I would debate first bits.... by Groo+Wanderer · · Score: 1

    How about disk-free?
    http://www.theinquirer.net/gb/inquirer/news/2007/10/04/vista-details-emerge

                              -Charlie

  60. OS X.X? by Chas · · Score: 4, Funny

    Where they trade out command line and GUI for a full emoticon-based interface.

    --


    Chas - The one, the only.
    THANK GOD!!!
  61. Oh the humanity! by Anonymous Coward · · Score: 0

    And now instead of being able to pressure hardware vendors they can only rely on vendor lock-in.

    However will the company survive?

    1. Re:Oh the humanity! by pilbender · · Score: 1

      Explain please? I don't get it. Vendor lock-in? They can try all the vendor lock-in they want but that is a failing stategy. No one is moving towards that model. They're going to have to play ball. Users seem to be avoiding vendor lock in, I'm talking governements, nations, schools, etc. Even businesses are trying to avoid that risk. They cannot afford to do anything but minimal vendor lock-in if they are going to survive. The jig is up on vendor lock-in techniques and people aren't buying it anymore.

      Am I missing something here or is this simply a matter of differing opinion on the future movement of the tech industry?

      By the way, vendor lock-in is how they've gotten the where they are today. They can't seem to make their new system take off because they vendor locked themselves right out of their own market ;-)

      --
      Fresh horses and more whiskey for my men.
    2. Re:Oh the humanity! by Almahtar · · Score: 1

      I wish vendor lock in didn't work anymore. I routinely have clients that need to use outlook because they use exchange server, or demand their stuff run on MSSQL 2K5 and .NET because then Microsoft will be their 'partner' or well... you name it. About Half my clients insist on Microsoft stuff because they currently use other Microsoft stuff. I can only convince a few that it's not actually a necessity nor advantageous.

    3. Re:Oh the humanity! by pilbender · · Score: 1

      You're absolutely right about it still working. I don't deny that. I experience it myself daily.

      But it's becoming a less and less successful strategy. People like you and me are eroding this technique's affectiveness because we're tired of working around the inherent limitations it puts on our systems and the people around us. Vendor lock-in doesn't allow us to make the best decisions we can about a solution because it attempts to eliminate those solutions' viability for reasons other than quality and effectiveness.

      I don't sit by idly and let it go. As a developer and advocate of technology, I'm compelled to give the best advice I can about risks, limitations, or future viability of a solution. It's my job and I can't help but give the best advice I can on areas where I'm qualified. If I smell vendor lock-in I have to respond early before it's too late and causes negative consequences. I know I'm not alone in this as you illustrate in your post :-)

      --
      Fresh horses and more whiskey for my men.
  62. ME doesn't get it's own number by Rix · · Score: 1

    It was just 98 warmed over.

  63. The operating system family tree by renegadesx · · Score: 5, Funny

    OSX was loosly based on NeXT. It's kernel is Darwin which is based on NetBSD.

    Linux is loosly based on Minix only ditching the microkernel design and got support as the GNU kernel (another microkernel) was going nowhere.

    Minix and BSD are based on UNIX, anyone can make a UNIX System III derivative for free as the code is public domain. Just most of the code is obsolete so you are better off making a BSD or Linux derivative (or Minix 3 if you want a microkernel)

    So if you look at a family tree, Minix and Linux are brothers while OSX and Linux are more like cousins

    Windows is the annoying friend that spunges off you for handouts and crashes on your couch

    --
    Make SELinux enforcing again!
    1. Re:The operating system family tree by Nossie · · Score: 2, Insightful

      "OSX was loosly based on NeXT. It's kernel is Darwin which is based on NetBSD."

      I wouldnt have said loosly but I agree that they are not the same.. Is that why OSX has only now gained the true UNIX certification rather than always conforming?

      Saying OSX is loosly based on Next is like saying Windows 2000 is loosly based on Windows 98... I'd say that the comparison between 2k and XP would be more apt taking Rhapsody, Blue Box and Yellow Box into account.

      talking about pulling stuff out of your ass.... I'm going to quote wikipedia here and say:

      "Mach is an operating system microkernel developed at Carnegie Mellon University to support operating system research, primarily distributed and parallel computation. It is one of the earliest examples of a microkernel, and still the standard by which similar projects are measured.

      The project at Carnegie Mellon ran from 1985 to 1994, ending with Mach 3.0. A number of other efforts have continued Mach research, including the University of Utah's Mach 4. Mach was developed as a replacement for the kernel in the BSD version of Unix, so no new operating system would have to be designed around it. Today further experimental research on Mach appears ended, although Mach and its derivatives are in use in a number of commercial operating systems, such as NEXTSTEP and OPENSTEP, and most notably Mac OS X (using the XNU kernel). The Mach VM system was also adopted by the BSD developers at CSRG, and appears in modern BSD-derived UNIX systems, such as FreeBSD. Neither Mac OS X nor FreeBSD maintain the microkernel structure pioneered in Mach, although Mac OS X continues to offer microkernel Inter-Process Communication and control primitives for use directly by applications.

      Mach is the logical successor to Carnegie Mellon's Accent kernel. The lead developer on the Mach project, Richard Rashid, has been working at Microsoft since 1991 in various top-level positions revolving around the Microsoft Research division. Another of the original Mach developers, Avie Tevanian, was formerly head of software at NeXT, then Chief Software Technology Officer at Apple Computer until March 2006.[1]"

      I'll just grab my coat and leave now :D /OT

    2. Re:The operating system family tree by Nossie · · Score: 3, Insightful

      oh and just to catch up to modern times regarding Darwin...

      "Darwin is built around XNU, a hybrid kernel that combines the Mach 3 microkernel, various elements of FreeBSD 5 (including the process model, network stack, and virtual file system), and an object-oriented device driver API called I/O Kit.[1]

      Some of the benefits of this choice of kernel are the Mach-O binary format, which allows a single executable file (including the kernel itself) to support multiple CPU architectures, and the mature support for symmetric multiprocessing in Mach. The hybrid kernel design compromises between the flexibility of a microkernel and the performance of a monolithic kernel."

    3. Re:The operating system family tree by drsmithy · · Score: 3, Insightful

      OSX was loosly based on NeXT.

      Indeed. In the same way Windows Vista is "loosely" based on Windows 2000.

      It's kernel is Darwin which is based on NetBSD.

      Darwin is "based on" Mach, with a bunch of code welded in from the various BSD projects (mostly FreeBSD).

    4. Re:The operating system family tree by drsmithy · · Score: 1

      Saying OSX is loosly based on Next is like saying Windows 2000 is loosly based on Windows 98... I'd say that the comparison between 2k and XP would be more apt taking Rhapsody, Blue Box and Yellow Box into account.

      Windows 2000 (or XP) to Windows Vista would be the best analogy to NeXT -> OS X. The changes in both comparison of are much the same scope, magnitude and type (and the timeframes are roughly equivalent - although OS X has lagged a bit with the lower-level features, that's understandable since the codebase has not been under as intensive development as NT).

      (With that said, there are a lot of low-level features that will only appear for the first time in OS X 10.5, that Windows has already had for many years, in particular with regards to efficient use of multiple CPUs.)

    5. Re:The operating system family tree by Nossie · · Score: 1

      I might be missing something here but which part of Darwin is based on NetBSD?

      If CMU developed Accent and made Mach 0 - 4...
      Apple took Mach 3/XNU and added bits of FreeBSD to make Darwin

      where does NetBSD come into it?

    6. Re:The operating system family tree by maglor_83 · · Score: 1

      Windows is the annoying friend that spunges off you for handouts and crashes on your couch On your couch? Mine crashes under my desk.

    7. Re:The operating system family tree by hedwards · · Score: 1

      I might be missing something here but which part of Darwin is based on NetBSD?
      >
      where does NetBSD come into it? You aren't missing anything, NetBSD wasn't a major source of code. In fact this is the first time I've seen it mentioned in this context. Googling for it didn't really help either.

      If memory serves the code which FreeBSD uses to boot on macs is based largely upon code developed for NetBSD when it was ported to the Motorola and macs from then on. I don't know offhand though if any of that portion of the tree was brought into OSX, as it would probably have made more sense just to write it from scratch as Apple has far better information than was available to the NetBSD coders.
    8. Re:The operating system family tree by Anonymous Coward · · Score: 0

      OSX is *exactly* NextStep. It's kernel is the same old M.A.C.H.
      The "bsd" layer is just a personality running on top of MACH.
      The layer was simply updated (long overdue, since the NeXT era), and Jobs remarketed it as "bsd" in an attempt to surf the opensource wave.

    9. Re:The operating system family tree by petermgreen · · Score: 1

      I wouldnt have said loosly but I agree that they are not the same.. Is that why OSX has only now gained the true UNIX certification rather than always conforming?
      Afiact OS-X got the unix certification because apple decided the easiest way out of the mess they had got in by calling it unix without it being certified as such was to make whatever minor changes were required for compliance and get it certified.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    10. Re:The operating system family tree by rbanffy · · Score: 1

      "Windows 2000 (or XP) to Windows Vista would be the best analogy to NeXT -> OS X"

      I am not sure any Windows analogies would apply. 2K was never as elegant as OPENSTEP and OSX doesn't suck nearly as much as Vista. Some may say OSX doesn't suck at all while I can identify some suckiness here and there.

    11. Re:The operating system family tree by nine-times · · Score: 1

      I guess it depends on what you mean by "based on". I agree that there isn't much connection between OSX and Windows. The connection between OSX and Linux also isn't direct, but it's much closer.

      Linux was designed to be similar to Unix, while OSX was developed from a form of Unix. And, in fact, OSX *is* a form of Unix. The main things that set it apart from FreeBSD/NetBSD is that it uses a different kernel and runs a different GUI (with different APIs). Because of this similarity, OSX, Linux, and the BSDs have a lot in common, running a lot of the same tools and shells. Many applications that run on one system will run on another with minimal changes.

      So while OSX is not the same as NeXT, I'd call it a direct descendant. In turn, NeXT and OSX are like half-brothers of NetBSD and FreeBSD, while Linux is sort of an adopted brother. The genetic code is different, but they grew up together and have a lot in common. Windows is more like their next-door neighbor who sometimes tags along.

    12. Re:The operating system family tree by The+One+and+Only · · Score: 1

      OSX was loosly based on NeXT. It's kernel is Darwin which is based on NetBSD.

      No, Darwin is directly based on NeXTStep (with some adaptations from FreeBSD) while Mac OS X's Cocoa API is directly based on NeXT's OPENSTEP API, which pioneered on the NeXTStep OS. The Quartz graphics engine was new (due to licensing issues with Display PostScript, among others), Aqua was an adaptation of both the Mac OS and the NeXT UI, Classic was a VM for running Mac OS 9 within Mac OS X, and Carbon was an adaptation of the Copland API to run on Darwin.

      --
      In Repressive Burma, it's not just your connection that dies. slashdot.org/comments.pl?sid=314547&cid=20819199
  64. Wow? by Almahtar · · Score: 1, Insightful

    Ok, running on only 40 MB of ram (with 7 free) you can run a text interface and an http server. How is this streamlined? Check out Damn Small Linux - I can get full gui up on it using 8 megs of ram, 2 of which are the wallpaper. If I boot up without X I'm using around 4 megs of ram.

    Congratulations, you've booted Windows without a gui and a minimalist http server in only 33 megs of ram.

    1. Re:Wow? by Deimos24601 · · Score: 1

      How do you expect them to fit all that DRM code into 8MB of RAM?

    2. Re:Wow? by Almahtar · · Score: 1

      How do you expect them to fit all that DRM code into 8MB of RAM? I stand corrected.
    3. Re:Wow? by Anonymous Coward · · Score: 0

      8Mb of Ram? You should upgrade your hardware.
      I don't understand why people are still using such ancient equipment.

      My Pentium 166 MMX 24Mb laptop running Slackware will absolutely smoke your machine.
      Fluxbox, dillo, ssh, playing mp3s... it handles it all.
      Sometimes I even turn off the swap file so the hard drive can spin down to save power.
      Try pulling that stunt with your 8mb piece of junk.

    4. Re:Wow? by Almahtar · · Score: 1

      The machine has 96 MB, but only 8 was in use.

  65. True Story by laparel · · Score: 1

    I touched Vista for the first time today, because a friend wanted help installing a printer, and my cries of "I know nothing about windows!" fell on deaf ears. It took me 3 minutes from power on to bluescreening, and 2:30 of that was the time it took to boot...True story.

    Fixed.
  66. Wrong family line by ben+there... · · Score: 1

    3: NT 3.51 is where we'll start
    4: 2000
    5: XP
    6: Vista
    7: Win7

    95/98/ME are all a different code base with different versioning.

    1. Re:Wrong family line by pushing-robot · · Score: 4, Informative

      Consumer line:

      Windows 1.0
      Windows 2.0
      Windows 3.0
      Windows 3.1
      Windows 95 (v. 4.0)
      Windows 98 (v. 4.1)
      Windows ME (v. 4.9)
      Line killed off.

      Business line:

      Windows NT 3.5
      Windows NT 4.0
      Windows 2000 (v. 5.0)
      Windows XP (v. 5.1)
      Windows Vista (v. 6)
      Windows "7"

      There were no NT versions prior to 3.5 because the first NT was released after Windows 3.11, and Microsoft wanted their numbering to be consistent. NT 3.5 coexisted with Windows 3.x (and shared the same GUI design), NT 4.0 coexisted with Windows 4.x, and then MS killed off the "Consumer" Windows line, leaving the NT line to fill versions 5 and 6.

      --
      How can I believe you when you tell me what I don't want to hear?
    2. Re:Wrong family line by pushing-robot · · Score: 1

      Sorry - I just did a bit of looking on Wikipedia and realized that 3.5 wasn't the first NT. There was apparently a short-lived Windows NT 3.1, though I've never personally seen it. The rest of what I said is correct, though.

      Sorry for any confusion.

      --
      How can I believe you when you tell me what I don't want to hear?
    3. Re:Wrong family line by aproposofwhat · · Score: 2, Interesting
      3.1 was indeed short-lived, but long booted!

      We built an early 3.1 server soon after the release date, just to compare it with the Netware servers we used.

      Since the system took 10 minutes to get to the login prompt, and the file and print services were atrociously slow, we soon abandoned the exercise.

      It's not that long ago, though - only 15 years :P

      Get off my lawn, you damn kids!

      --
      One swallow does not a fellatrix make
    4. Re:Wrong family line by sr8outtalotech · · Score: 1
    5. Re:Wrong family line by downix · · Score: 1

      Untrue. I have a copy of Windows NT 3.1 sitting right here.

      http://en.wikipedia.org/wiki/Windows_NT

      And you could consider the previous name OS/2, which Microsoft had a part in until version 2. When MS and IBM had their falling out, they both has OS/2, which MS took and turned into NT and IBM evolved in it's own way.

      --
      Karma Whoring for Fun and Profit.
    6. Re:Wrong family line by petermgreen · · Score: 1

      95/98/ME are all a different code base with different versioning.
      For the most part the versionings are paralell, versions from the two lines with similar version numberings have a similar user interface and were released at a similar time. When you query for version number there are seperate values returned for the version number and whether the system is NT line or not.

      Your version numbers are also wrong.

      the following is how I understand the mapping of names to versions

      3.0->3.0
      3.1->3.1
      NT 3.1->NT 3.1
      3.11->3.11
      NT 3.51->NT 2.51
      95->4.0
      NT 4.0->NT 4.0
      98->4.1
      ME->4.2 (not sure on this one)
      2K->NT 5.0
      XP->NT 5.1
      Vista-> NT 6

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    7. Re:Wrong family line by TheNetAvenger · · Score: 1

      Sorry - I just did a bit of looking on Wikipedia and realized that 3.5 wasn't the first NT. There was apparently a short-lived Windows NT 3.1, though I've never personally seen it.

      Glad you checked, because the NT 3.1 CDs I have sure seem to be real. ;)

      Actually 3.1 of NT was around for a while, and it made the first moves in the server and workstation areas for MS. It also was the premiere OS for the new Alpha CPU line.

      Also anyone that attended the 1992 CES would easily be able to correct the 3.1 omission as NT 3.1 was freaking everywhere.

      You also didn't reference NT 3.51 which was more important than 3.5 as it brought the Win32 API in line with Win95, and the UI from NT 4.0 originally ran on NT 3.51, although the UI was never 'officially' released for 3.51.

      BTW Thanks for separating the Consumer and NT line of OSes... Too many people STILL confuse Win9X with current Windows OSes, and they are as different as System 9 and OS X is.

    8. Re:Wrong family line by TheNetAvenger · · Score: 2, Informative

      Since the system took 10 minutes to get to the login prompt

      You must of had some serious hardware issues. If you had 12mb of RAM, or 16mb of RAM NT 3.1 booted as fast as the DOS Win 3.1, and yes even the server version, as there was even less distinction between the workstation and server versions then.

      We moved all our development and tech employees and their respective servers to NT 3.1 in 1993, and trust me this would never of happened if it took 10 minutes to boot.

      Average system Specs: 486-33/66 12/16mb RAM...

      PS Compared to our Novell Servers, NT file operations (especially remote booting clients) was 2-4x as fast as Novell. Trust me, MS didn't 'dent' the Novell market because NT sucked. Not only was it faster, easier to manage for small business but was a great application server platform, something Novell 'never' got.

    9. Re:Wrong family line by BlackSnake112 · · Score: 1

      I always thought ME was 98 version 3? There was 98 and 98 version 2

    10. Re:Wrong family line by CastrTroy · · Score: 1

      Could that have possibly been windows 3.11 for workgroups?

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    11. Re:Wrong family line by aproposofwhat · · Score: 1
      Well, it was 1992, and running on a 386 :P

      Funny though - my testing (mostly on ~30MB CAD files) showed Netware 3.11 to be at least twice as fast, running on identical hardware.

      Added to which, at the time the fastest Intel platform for Oracle 6 was Netware - running at ring 0 really gave those queries a boost, so as an application server, Netware was far superior - it just lacked the developer base, which was a pity as NLMs werejust as easy to code as Windows binaries, without the Win32 API bloat.

      --
      One swallow does not a fellatrix make
    12. Re:Wrong family line by TheNetAvenger · · Score: 1

      Well, it was 1992, and running on a 386

      Well the 386 at that time would have been a major problem. Even 486SX chips of the time without a math-co in them suffered.

      NT was i386, but 486 optimized, and this includes the use of the RISC pipeline in the 486 and even the math-co-processor for OS level functions.

      On 386 platforms, Novell was faster than NT, but on a 486 server, and running as a server, it couldn't keep up with NT, which is what really blew consumers and even Novell away, as NT had an inherent GUI strapped on it which most assumed would consume both RAM and CPU cycles, even though the NT GUI model when not in use was very minimal on RAM and non-existent on CPU cycles breaking the 'GUI = slower' concept for servers.

    13. Re:Wrong family line by TheNetAvenger · · Score: 1

      Netware was far superior - it just lacked the developer base, which was a pity as NLMs werejust as easy to code as Windows binaries, without the Win32 API bloat.

      PS Windows binaries on NT that ran in the Win32 subsystem were always Win32 API applications. Almost nobody and nobody to this day can or do code directly to the NT level of the OS. Developers pretty much have to pick an architecture subsystem, whether it is Win32/POSIX/BSD/Win64 and code for the subsystem and the subsystem kernel that abstracts to the NT kernel layers.

      There really is no such thing as Windows binaries that are not Win32 or BSD or some other Subsystem based application API.

      Take Care...

    14. Re:Wrong family line by petermgreen · · Score: 1

      I don't think they changed the version number for 98 second edition though i'm not positive.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    15. Re:Wrong family line by pushing-robot · · Score: 1

      I was tempted, as 3.51 was the first NT I spent much time with. I guess I just missed 3.1 as I first got into real IT in '96 and don't remember seeing it in use (or maybe I just assumed it was 3.5)

      Anyway, I didn't put 3.51 on the chart because if I had, I'd have felt obligated to list all the other "revision" point upgrades, like Windows 1.0x, 2.0x, Windows 3.11, and 98 SE. Not that they weren't important upgrades, I just wanted to keep the list simple by only listing major/minor version changes.

      --
      How can I believe you when you tell me what I don't want to hear?
    16. Re:Wrong family line by GPL+Apostate · · Score: 1

      There was NT 3.1, 3.5, and 3.51.

      3.51 is probably the best version of NT that ever came out. 4.0 was something evil. 3.51 feels almost like they 'got it' as far as a Unix-like architecture in many ways, but then Windows 95 happened and everything had to be like 'that' from then on.

      The Fall 1992 first beta (alpha) version of NT didn't even have the applets (Notepad, Solitaire, etc.) working quite right. I specifically spent $600 on a Sound Blaster Pro and a 1x CD-ROM to install it. It installed, all right, but Creative didn't ever release NT drivers for the CD and sound card that I know of, so you... umm.. installed NT and it essentially bricked your sound card and CD that you just spent a bunch on.

      The good old days. Thank goodness Linux happened. Yggdrasil's first release ("LGX") with an 0.99 something kernel was 'plug and play' with that sound card/CD drive. It booted off the CD to a full system and played music at the login prompt.

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
  67. Oops, forgot NT 4.0 by ben+there... · · Score: 2, Informative

    Should be:

    3: NT 3.51
    4: NT 4.0
    5: 2000 (5.1: XP)
    6: Vista
    7: Win7

    Or just look at this. I should have google'd it first. It's all right there.

  68. MS should support Wine ;-) by ben+there... · · Score: 1

    That's how Apple managed the jump from OS9 to OSX (the "Classic" environment was launched on-demand), and that's how Windows 7 should be built. MS should just pull an apple, grab BSD with maybe some of NT's subsystems on top, then throw all their money into Wine. Can you imagine that? An MS supported Wine?

    Okay, I'll stop dreaming now.
    1. Re:MS should support Wine ;-) by Bert64 · · Score: 1

      And no vendor lockin, meaning MS have to compete on a level playing field with everyone else...
      As Bill Gates himself said, removing people's reliance on proprietary microsoft systems would be business suicide, microsoft would suffer greatly but everyone else would benefit.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  69. Re:Better than vista? by Anonymous Coward · · Score: 0

    I've been using vista since January, and it has *never* crashed or bluescreened. And my old printer was automatically detected and installed, and it works fine. Compare that with when I ran Ubuntu for a month: my USB flash drive would only auto-mount 10% of the time, sound completely stopped working one day and I could never get it back no matter what I did (including compiling a new version of the kernel--too bad we can't do that in Windows, huh), and getting the wireless on my laptop to work was such a huge headache that required using windows drivers in linux. I didn't even dare try to print in linux.

  70. Screw a smaller kernel footprint... by Khyber · · Score: 1

    How about giving us an OS in it's entirety with a small footprint? Minuet seems to do the job, though I can imagine assembler programming to be a bitch. Damn Small Linux can be fully functional with a 250 meg install, just like Windows 98 had.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  71. "minimal footprint."...hmmm by thatseattleguy · · Score: 1
    optimize the Windows kernel to a minimum footprint


    So it'll include nothing except DRM?

  72. So what *is* in it? by jayegirl · · Score: 1

    So, this is a completely stripped back to the bare bones version of Windows. And it eats 40MB (IIRC?) of runtime memory. What I want to know is, what, exactly *is* included in this 40MB of running binary footprint?

    Seems like a lot for a "minimal windows footprint", especially compared with, say, QNX...

  73. Oh God... by andreyw · · Score: 4, Insightful

    Oh God... I can't believe this actually made news. In. Such. A. Horribly. Skewed. Fashion. But this is /. You can watch the presentation HERE - http://www.acm.uiuc.edu/conference/2007/videos It was ONE of MANY presentations given as part of the ANNUAL UIUC ACM-hosted conference. Please actually watch the presentation and STFU. Please. All it shows is that Microsoft is working on fixing what it considers to be mistakes in the design of its NT system. That is it. It's work as part of Win7. It is _not_ Win7. Listen to the questions that students asked Eric about MinWin. Listen to the answers.

    1. Re:Oh God... by Anonymous Coward · · Score: 1, Funny

      Please actually watch the presentation and STFU. Please. PLEASE leave MinWin alone! PLEASE!
      How DARE anyone out there make fun of MinWin after all she's been through!
    2. Re:Oh God... by Anonymous Coward · · Score: 0

      Andrey. He made them high and lowly and ordered their estate; the rich man at his castle, the poor man at his gate. Get back to the gate, Andrey.

    3. Re:Oh God... by moosesocks · · Score: 2, Funny

      Oh God... I can't believe this actually made news. In. Such. A. Horribly. Skewed. Fashion. But this is /.


      William Shatner posts on slashdot?
      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    4. Re:Oh God... by everphilski · · Score: 1

      no, William Shatner's toupee.

  74. Please elaborate? by LaZZaR · · Score: 2, Interesting

    Please elaborate on the amusement?

    I once had a crazy friend who was upgrading his Pentium III era PC, and got fed up with getting certain peripherals to work, so he started yanking things out of the PC with the power on. We then found that the sound card was hot plugable, it would dissapear and reappear in device manager every time.

    --
    I lost me sig.
    1. Re:Please elaborate? by langelgjm · · Score: 1

      That's impressive. I think I must have knocked out a NIC or sound card of the same era machine. It completely locked up - the image on the screen stayed, but go no response from anything. After a reboot, it was fine. I was scared shitless for a few seconds, there, though.

      --
      "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
  75. Re:ah! just in time by happyemoticon · · Score: 1

    I liked this one: http://www.roughlydrafted.com/RD/Q4.06/4E2A8848-5738-45B1-A659-AD7473899D7D.html. The Windows 7 hype, however, probably has as much to do with the way people are fleeing from Vista like it's Mt. Vesuvius.

    It's not the same market nowadays, though, and I think people will be generally less inclined to fall prey to this kind of thing.

  76. In related news... by SandmanWAIX · · Score: 1

    In related news George Costanza is filing a lawsuit and claiming copyright on the name "7"

  77. How low can they go? by g051051 · · Score: 1

    Let's hope they get the Windows footprint down to zero!

  78. Way too much heat.... by ScottKin · · Score: 1

    ...generated with very little light.

    That's how I approach most of the comments in a way-too-easy target for the linux-o-philes here.

    While we're talking about footprint, and previous comments about 24" .vs 8" footprints and extending the previously-started metaphor/meme, we can be sure of two facts:

    1) If you're saying that the 24" footprint is the OS footprint of Windows, you can then be sure that what they say about shoe-size is true.

    2) At least I don't have to cobble my own shoes together to try a new pair every few years or having to replace my shoe's soles by myself, and I can still put on new shoelaces without worrying if they'll fit in the shoelace holes that came with my shoes without having to use a leather punch to make new holes.

    --ScottKin

    --
    I don't give a rat's behind about "karma" here or anywhere else. Don't like what I have to say here? Deal with it!
    1. Re:Way too much heat.... by Anonymous Coward · · Score: 0

      Thank you for this completely nonsensical post, pompous imbecile.

      Here's a hint: No one here gives a shit about what you think.

  79. if you succeed, do it again by m2943 · · Score: 1

    With Vista, Microsoft has succeeded at removing useful drivers, making the system harder to install and use, and increasing incompatibility. And with Windows 7, they will build on that solid foundation to improve Windows even further.

  80. Then Microsoft calls developers by Anonymous Coward · · Score: 0

    And says,
      If you add a cal to module 'Xyzzy' it will cost the user another $5/month. We'll pay you $2/month.

      Developer: But my product does not need to call that module.
      M$: Ok, $3 per copy per month
      Developer: Done.
      Click

      What I am saying is that could be pressure on M$ to get the main 3rd party application providers to include unnecessecary calles to addon modules just to the the system user(not owner) to have to fork out for these 'extras'. I smell huge number of RICO Lawyers sharpening their pencils as I write this.

    This model is open to a huge amount of abuse and is therefore fundamentally flawed at the outset.

  81. Clue to the developers by threaded · · Score: 1

    Just a little clue to the developers from someone who has written code for a long long time:

    The UI goes on top of the OS, g'damn it!

  82. Cruft is their business model by johannesg · · Score: 1

    Since people apparently still do not get it, let me state again: cruft is Microsofts business model. The constant eruption of new technologies from Redmond keeps the Microsofties on their toes, requiring them to always be learning the latest and greatest brainfart yet considered. Why? Two reasons:

    1. It takes time away from other activities. No time to learn about penguins, if you need to study the latest .NET 3.1.7 crypto/drawing/thingamabob API.

    2. Having invested so much in studying all that Microsoft crap, going to another system is a very unattractive proposition: suddenly all that hard-won knowledge loses its value, and all that time wasted.

    Without a constant barrage of new "technologies", API's, and other things to study, Microsoft would start losing brainshare very quickly.

  83. Here's what they need to do. by AbRASiON · · Score: 3, Interesting

    HIRE SOME FUCKING UI EXPERTS.

    Sorry to be shouting and all but I'm a Windows guy, I always have been a Windows guy, sure I have that slashdot bone in me, wanting OSS to be huge, great, free and out there for everyone to share and love but let's be realistic now, for some people it's not an option, myself included.

    Honestly I have been really quite satisfied with XP (after becoming accustomed to its own issues)
    However after having recently tried Vista (multiple times) it's a disgrace, PURELY from a look and feel perspective, it's like 500 people designed it around a board room table but consistency and ease of use just aren't even considered.

    I'm definately NOT an apple man by any means, yet having now used OSX for a week and an ipod for a year, they just get (most) stuff right, logical and simple - just how it should be.
    Vista is wrong, it looks wrong, some of you can whinge it sucks under the hood or perhaps DRM ate your babysitter, maybe it has poor performance copying files and playing MP3's (doesn't bother me) but that UI? Good lord if you can't make it better at least give us back the XP one as an option.

    It's time that MS made some RADICAL changes to the user interface, crazy out there stuff, which is actually USEFUL! rather than just re-hashing the same old thing, stapling on some stuff (poorly) and expecting us to enjoy it.

    1. Re:Here's what they need to do. by ykiwi · · Score: 1

      I'm definately NOT an apple man by any means, yet having now used OSX for a week and an ipod for a year, they just get (most) stuff right, logical and simple - just how it should be.


      Well you sure sounds like you are an Apple man now. Oh - and Apple's come with spell-check.

      Welcome to the light side.
  84. Re:ah! just in time by suv4x4 · · Score: 3, Interesting

    looks like Mistersoftie is up to their old hype the vaporware [wikipedia.org] tricks to dissuade buyers from going with attractive alternatives.

    Because, of course, you can't wait to have MinWin on your machine - the Windows that does only one single thing: publish your tasklist via HTTP.

    Hmmm, so much better than Leopard :P

    Come on, it's just a tech demonstration, Microsoft in fact closed themselves solid after the release of Vista. Management thinks part of the bad reception of Vista is because they were so open about the whole process for the entire 5 years.

    For some part they are right. We'd never know about the dropped features if they were never pre-announced. Most products plan various features that get dropped or deferred in the process of development.

    We'd also be surprised at the Aero Glass UI, and the new security features.

    What we'd be most surprised about though, is the lack of consistency in the UI and stability/performance issues. So I'm not sure Microsoft has the right strategy right now.

  85. Not Windows-2 by scsirob · · Score: 3, Funny

    Must be NT-based counting.

    0. CP/M
    1. VMS
    2. OS/2
    3. Windows-NT 3.1, 3.5, 3.51
    4. Windows-NT 4
    5. Windows 2000, Windows XP
    6. Windows Vista
    7. Windows 7
    8. Ubuntu Octal Overlord
    9. Plan-9
    10. OS-X

    Plenty of future, you see..

    --
    To Terminate, or not to Terminate, that's the question - SCSIROB
    1. Re:Not Windows-2 by ConceptJunkie · · Score: 2, Funny

      I for one welcome our new Octal Overlords.

      --
      You are in a maze of twisty little passages, all alike.
  86. Nice try but you guys are all wrong by commodoresloat · · Score: 4, Funny

    The numbering system has nothing to do with this. Microsoft named it "7" in order to announce that they are finally catching up to MacOS's revolutionary System 7, from 1991. I for one can't wait for Windows to finally get "Balloon Help"!

    1. Re:Nice try but you guys are all wrong by 3vi1 · · Score: 1

      I thought "7" was short for "7 of 9". Not only is that a name that will get geeks to buy it, but it also tells a small truth about how many versions they have in them before Desktop Linux is the obvious way to go for most people.

      -J

    2. Re:Nice try but you guys are all wrong by Anonymous Coward · · Score: 0

      Yeah, System 7 was Apple FINALLY adding color, years after every other computer in existence had it. Revolutionary indeed.

  87. Microkernel? by G-News.ch · · Score: 2, Funny

    So, basically they're saying they want to go back to DOS roots for Windows 7, right? 640k is enough for everyone, after all. :)

  88. Re:MS has a history of "skipping" for parity's sak by jrumney · · Score: 1

    NT started at version 3 (maybe even 3.5)

    It was 3.1, the same as the version of DOS based Windows that was current at the time. 3.5 came next, then 3.51, before the Windows 95 UI upgrade which was NT 4.

  89. A matter of degrees by fwarren · · Score: 1

    It is how much are they going to break?

    Win 95 broke some stuff. Win 98 did too. Windows XP broke stuff as well. Vista broke more stuff. But for the most part, making sure legacy code has a shot at working seems to be a priority at Microsoft.

    If 7 breaks nothing at all..it will really suck.

    If 7 breaks a little bit....it will still suck like Vista.

    If 7 breaks to much...people will move to linux or mac.

    --
    vi + /etc over regedit any day of the week.
    1. Re:A matter of degrees by Ash-Fox · · Score: 1

      If 7 breaks to much...people will move to linux or mac.
      I highly doubt that. You goto a computer store, the only computers being sold there are Windows machines - They have no choice.
      --
      Change is certain; progress is not obligatory.
    2. Re:A matter of degrees by fwarren · · Score: 1

      That is so 2007. Things may quite different by 2012.

      Having run Linux from 1999. I remember: Step 1 install it. Step 2 set up networking. Step 3 back to windows to find out how to fix networking. Step 4 download video driver stuff. Step 5 Compile video drivers. Step 6 stark hacking on X.

      While your millage may vary, we starting to get to the point where it does not matter if it is 32 bit or 64 bit. Linux is working more out of the box than Vista is. Dell, is putting enough force behind things that drivers are going to become less of an issue.

      The stink of vista is not going away. If Dells support of Linux continues to improve, even if only a little bit. I think you will be seeing Linux systems in stores.

      --
      vi + /etc over regedit any day of the week.
  90. Foot print by mistralol · · Score: 1

    Well moving everything outside the windows kernel into a device driver which at loaded at runtime does reduce the foot print. But only for booting.

    Its the Microsoft answer. Technically correct but absolutely useless.

    1. Re:Foot print by KillerBob · · Score: 1

      It's also the Linux and Apple answer... What those two systems have been using for years.

      Well... Linux does have the option to compile the drivers directly into the kernel rather than having them as loaded modules, but most distributions use a microkernel with loadable modules/firmware.

      It does more than reducing the footprint at boot time. It makes the system more resilient to driver crashes as it gives the system the option to unload a driver and reload it.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    2. Re:Foot print by mistralol · · Score: 1


      Yes but linux and apple can still measure footprint size in KBytes Window has been measuring it in MBytes for years

  91. Hmm, let's have a look by simong · · Score: 1

    c:\ ver
    Microsoft Windows [Version 5.7.1000]

    Ha! I knew it!

  92. Emerge? by Splod · · Score: 1

    Anyone else read that and wonder why the Gentoo maintainers had sold out so suddenly and so thoroughly?

  93. Meh. by vegiVamp · · Score: 1

    Can't $random_unix_vendor patent 'small kernel footprint, other stuff in loadable modules and various chainable tools' and sue ?

    --
    What a depressingly stupid machine.
    1. Re:Meh. by KillerBob · · Score: 1

      Prior art, at the hands of *many* vendors, notably Xerox and Apple. The idea is old enough that it's in the public domain and even these companies wouldn't be able to patent it.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
  94. AmigaOS 5 existed back in 1993? by Anonymous Coward · · Score: 0

    News to me, but then I've never understood the whole AmigaOS5 OS4 OS3 Workbench, AmigaDOS, Intuition or whatever they're calling the OS next naming game thing.

  95. You linked to a steaming pile of ... by dhavleak · · Score: 1
    The article is full of crap like:

    Rather than just bluffing its hand like other companies, Microsoft played the game with a set of cards in one hand, while waving the illusion of another set of cards in the other hand. The fake set of cards were highly distracting because they looked like a much better hand than anyone else could possibly have. and:

    Microsoft struggled with the complex reality of building its own operating system without IBM. and:

    Despite quaint stories about Bill Gates singlehandedly writing DOS on the back of a napkin, Microsoft had no real experience in building or designing operating systems at all. Throughout the second half of the 80s, it had relied on IBM to develop OS/2 as the replacement for DOS. And that's just from the first page or so of a roughly 7 to 10 page article. I want back the 5 minutes of my life that I wasted reading that crap. Twisted facts, shameless bias, bungled timelines is all there was in it. Jeez!
    1. Re:You linked to a steaming pile of ... by GPL+Apostate · · Score: 1

      Say hello to your cubicle neighbor darthflo.

      Or are you just two accounts from the same person?

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    2. Re:You linked to a steaming pile of ... by dhavleak · · Score: 1

      Say hello to your cubicle neighbor darthflo. Or are you just two accounts from the same person? ?

      I didn't get it.. did I say something offensive that someone else is famous for?
  96. Could be worse by JuanCarlosII · · Score: 1

    They could be following the Star Wars system. Windows Epidoe 1 anyone??

  97. Frak Windows 7... by Keeper+Of+Keys · · Score: 1

    What about IE8?

  98. New windows by Dunbal · · Score: 1

    Good, maybe they'll sell another dozen copies...

    --
    Seven puppies were harmed during the making of this post.
  99. The Best Way to Minimize Window's Footprint by sjaguar · · Score: 0, Troll

    is to not use it.

    --
    If at first you don't succeed, call it version 1.0.
  100. LOL by Anonymous Coward · · Score: 0

    And yet, that free OS can't seem to get it off the desktop, or the server, or the phone ... I predict you guys will chattering away at this when the next version of Windows is released the same way you did when 2000 was.

  101. The Linux secret to success by Anonymous Coward · · Score: 0

    "Step One. Release wonderous New Version! It is THE must have thing."

    That reminds me. When's the next Ubuntu out?

    "Step Two."

    But who will pay my bandwith bill?

    "Step Three. Microsoft begins hinting about the upcoming new version. It will fix all of the (not quite admitted) problems with current version AND add exciting new must have features. And it is coming Really Soon."

    So how's that Desktop Linux coming along?

    "Step Four. Have their minions in the trade press obsess about Upcoming new version."

    Gotta love slashdot.

    "All complaints about Current version are answered with "But Upcoming version will be out soon and will fix that problem." "

    I stopped RTFM and "don't complain, code it" a long time ago.

    "Step Five."

    Wobble my windows, baby!

    1. Re:The Linux secret to success by cloakable · · Score: 1

      "Step One. Release wonderous New Version! It is THE must have thing."

      That reminds me. When's the next Ubuntu out?


      Just under six months now. Gutsy came out yesterday, so Hardy is going to be here in six months - one day.

      "Step Two."

      But who will pay my bandwith bill?

      Or, you know, order a free cdrom from Canonical. Or switch to an ISP that just charges you for a connection, rather than connection + bandwith.

      "Step Three. Microsoft begins hinting about the upcoming new version. It will fix all of the (not quite admitted) problems with current version AND add exciting new must have features. And it is coming Really Soon."

      So how's that Desktop Linux coming along?

      Extremely well, as of Kubuntu 7.10. True, I'm confused at the inclusion of OpenOffice.org rather than the vastly better KOffice, but that's simple to fix.

      "Step Four. Have their minions in the trade press obsess about Upcoming new version."

      Gotta love slashdot.

      "All complaints about Current version are answered with "But Upcoming version will be out soon and will fix that problem." "

      I stopped RTFM and "don't complain, code it" a long time ago.

      See, if people DID rtfm, they'd save time. And 'don't complain, code it' is how OSS software improves.

      Unlike, say microsoft, where software is designed by market research.
      "Step Five."

      Wobble my windows, baby!

      Don't have that enabled. I do have the desktop cube, transparency, and a few other bits enabled. Mostly the productivity enhancing ones.

      --
      No tyrant thrives when every subject says no.
  102. GNU/Linux vs. uClinux by tepples · · Score: 2, Interesting

    Although quazi officially the OS is called GNU/Linux I'd like to see how many people actually call it that outside RMS most avid supporters. I use "GNU/Linux" especially to distinguish the PC operating system that includes Linux from the embedded operating system that includes Linux:
  103. but more interestingly... by mrwolf007 · · Score: 1

    ...will Leopard be certified Linux-compatible?

  104. Kudos to you. by Kickasso · · Score: 1

    However, this is not "case in point" by any stretch of imagination.

  105. Re:Lesson in MS Counting NITPICK! by Anonymous Coward · · Score: 0

    "NT Based
    3.1, 3.5, 4.0, 5.0 (2000), 5.1 (XP), 6.0 (Vista), 7"
    - by hyeh (89792) on Thursday October 18, @10:54PM (#21035679) You forgot NT 3.51, & 5.2 (Windows Server 2003)

    No biggie, you had the right point, but skipped a couple.

    APK

  106. wait wait wait... by twm1010 · · Score: 1

    let me get this straight, they're actually gonna strive to improve performance and reliability for once? holy shit. someone write this down!

    --
    If this post has multiple meanings, and one of those pisses you off, I meant the other one.
  107. MOD PARENT UP by Luscious868 · · Score: 1

    I couldn't have said it better myself.

  108. minWin? by mycroes · · Score: 1

    minwin == minix?

  109. Windows becoming shareware? by Chemisor · · Score: 1

    > The whole "add-on" 3D support as well as "don't limit my desktop to 5 open applications/processes" seems incredible.

    This is the very tactic that shareware apps have employed for years. Give away some crippled demo for nothing (as Windows is given away for nothing), and then charge big bucks to "register". Of course, then you have to enforce the registration, with, say, "what's the 5th word on line 14 of page 125 of the manual?", and constantly watching for registration codes for your software on pirate sites. I think that looking at the status of shareware today, we can infer how this new "Windows the Crip" version will fare.

  110. Small Footprint? by YetAnotherBob · · Score: 1

    Does this mean that they are going back to the microkernal design they inched away from to get added reliability? If so, the BSOD comes roaring back.

    OR

    Does this mean that they are redesigning the portable windows system (CE) yet again?

    We may have to wait through 3 more years of marketing to find out.

    --
    Everybody knows 3 people with my name.
  111. Same thing by YetAnotherBob · · Score: 1

    Nuff said

    --
    Everybody knows 3 people with my name.
  112. Agreed! by 0100010001010011 · · Score: 3, Interesting

    Apple: 15,810 Microsoft: 61,000 Microsoft has a little under 4 times the number of employees Apple has.

    They both do Hardware: xBox vs Apple Line (I think apple probably has more employees on their hardware than Microsoft.)
    They both do MP3: iPod vs Zune (It should be a wash in employee #'s)
    They both do Office Suite: iWork vs Office (Office has obviously more employees than iWork)
    They both do "Family" apps: iLife vs Microsoft Movie Maker, etc. (iLife probably has more)
    They both do an OS: OS X vs XP/Vista. (With out a doubt XP/Vista has more employees on it than OS X)

    You'd think that they'd be able to do something right. Heck AppleMaybe it's bureaucracy collapsing the whole thing. Maybe what Microsoft needs is a Steve, a dictator, someone that says what goes and no questions from above. Back in the day Apple wasn't run like this and we had Copeland and all other "Next OSes" there were some iffy products (OpenDoc). Then Apple bought NeXT. Steve came back and the rest is history. (And about 3000% in the stock market).

  113. Actually, Windows 7 is Windows NT version 5 by MCSEBear · · Score: 1

    You see, It goes like this....

    Windows NT 3.1 = Windows NT version 1
    Windows NT 3.51 = Windows NT version 1.5
    Windows NT 4 = Windows NT version 2
    Windows 2000 = Windows NT version 3
    Windows XP = Windows NT version 3.1
    Windows Vista = Windows NT version 4
    The thing MS is calling "Windows 7" = Windows NT version 5

    The Windows 3.1 and Windows 9x code trees were unrelated dead ends and were abandoned. When keeping up with which version number Windows has gotten up to, you should only pay attention to the NT based versions.

  114. It's quite true by cpt+kangarooski · · Score: 1

    The idea is that the kernel will have to shrink considerably in order to allow MS to cram in more DRM features -- both to keep people from pirating Windows, and as part of their ambitious program of colluding with the RIAA, MPAA, et al. There is not a guarantee that the smaller kernel will be able to do as much as at present, just more efficiently; it'll lose functionality. But they're betting that no one will notice since everything you do will have to be vetted by someone else who would generally prefer it if you didn't. (In order to reflect the long wait, the hourglass will change to a calendar)

    --
    -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  115. Windows is over! by Anonymous Coward · · Score: 0

    Aren't the days of huge new operating system releases over now that web aps are on the rise?

  116. Re:Size matters - Getting it right by Anonymous Coward · · Score: 0

    NO!
    This time they really 'got it'. Size IS everything. So if they are finally focussing on the most important aspect of an OS (from size comes speed, easier maintenance etc) this should be AWESOME.WSOME.SOME.OM....

    (This is a test. If you got exited by reading this you still have not ridden yourself from the 'eternalNextUpgradeBug' virus. Reduce your surfing NOW!)

  117. Seinfeld - The Seven! by guyfromindia · · Score: 1

    George and Susan, heading home from the restaurant. George is happy,

    smiling and whistling.

    GEORGE: I think they really went for that Soda.

    SUSAN: What, are you crazy? They hated it. They were just humouring

    you.

    GEORGE: Ah, alright. Believe me, that kid's gonna be called Soda.

    SUSAN: I can tell you, I would never name my child Soda.

    GEORGE: Oh, no no no. Course not. I got a great name for our kids. A

    Real original. You wanna hear what it is? Huh, you ready?

    SUSAN: Yeah.

    George uses his finger to draw a number 7 in the air, accompanying the

    Strokes of his digit with a two-tone whistle.

    SUSAN: What is that? Sign language?

    GEORGE: No, Seven.

    SUSAN: Seven Costanza? You're serious?

    GEORGE: Yeah. It's a beautiful name for a boy or a girl...

    Susan scoffs.

    GEORGE: ...especially a girl. Or a boy.

    SUSAN: I don't think so.

    GEORGE: What, you don't like the name?

    SUSAN: It's not a name. It's a number.

    GEORGE: I know. It's Mickey Mantle's number. So not only is it an all

    Around beautiful name, it is also a living tribute.

    SUSAN: It's awful. I hate it!

    GEORGE: (angry) Well, that's the name!

    SUSAN: (also angry) Oh no it is not! No child of mine is ever going to

    be named Seven!

    GEORGE: (yelling) Awright, let's just stay calm here! Don't get all

    crazy on me!

  118. Obligatory by Anomalyst · · Score: 1
    MS is attempting a stealth upgrade to v7.uh-oh
    Cancel or Panic?
    --
    There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
  119. Bull by TheVelvetFlamebait · · Score: 1

    He is clearly attempting to say that UNIX is not true, whatever that means
    Your assessment is simply !(Linux != Unix)
    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  120. Windows 7 of 9? by IchBinEinPenguin · · Score: 1

    1) I guess MS are "embracing and extending" the "borg" title :-)

    2) what happens after Windows 9?

  121. I think you've made two mistakes there. by argent · · Score: 1

    Does this mean that they are going back to the microkernal design they inched away from to get added reliability?

    First mistake: the NT kernel was never a microkernel. It has some features in common with one, but it's even less microkernel-like than Mach.

    Second mistake: the biggest reliability hit Windows NT had was when they moved GDI into the kernel in NT4. They didn't do that to improve reliability, they did it to reduce latency and improve performance, and it hurt reliability.

    Since they've decided that performance isn't that important any more (encrypting internal communication paths? Give me a break!) they could well be going towards a limited kernel and maybe even an actual microkernel design.

  122. Get the guys who did Pocket PC ... by argent · · Score: 1

    The palm-sized PC UI was a typical Windows 9x-derived 3d-style UI.

    Pocket PC rejected all that and went back to a flat 2d Windows-3 style for all the gadgets and window details, and it looked way more attractive and professional than the 3d look in any version of Windows or Windows CE.

    I don't know if the 3d look is the problem, but the Windows UI needs a lot of simplification. And I don't mean getting rid of menus or replacing control panel applets with "wizards" (which is what they seem to think 'simplification' means), I mean removing pure eye-candy UI elements.

  123. What it really would be by SnarfQuest · · Score: 0, Troll

    Ok, need smaller kernel. Grab a copy of Linux. Nobody will know because we don't let them see the souce code anyway. We'll do something stupid to hide all the boot messages behind a scroll bar.

    Next, graphical system. Swipe X.Open. Nobody will know because we don't let them see the souce code anyway.

    Now, we need a gui interface. Either gneme or kde will work for that since they both want to look exactly like Windows anyway. Just a couple of tweaks to the graphics to change the command button to "start", and nobody will know because we don't let them see the souce code anyway.

    Now, we need windows compatibility. Wine. What more needs to be said. ....

    --
    Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
  124. Only 7? by houghi · · Score: 2, Funny

    The next version of openSUSE will be 11. It will go to eleven!

    That means that the next version of openSUSE will be at least 4 better the Microsoft one. If the next version of Windows takes 7 years again, openSUSE will be at 14. So openSUSE will be TWICE as good.

    --
    Don't fight for your country, if your country does not fight for you.
  125. 250MB? by argent · · Score: 1

    It's pretty sad when 250 MB is considered a small install.

    Used to be that you could fit the OS on a floppy. Yes, including the GUI.

    1. Re:250MB? by Khyber · · Score: 1

      Did ya not see my mention of Minuet, which does fit and boot direct from a floppy? :) Pure Assembler.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    2. Re:250MB? by argent · · Score: 1

      Did ya not see my mention of Minuet, which does fit and boot direct from a floppy? :) Pure Assembler.

      Menuet, no?

      Not open source, though, and kind of funky. Reminds me a lot of '60s and '70s operating systems, and not in a good way.

      QNX boots off a floppy and it's actually UNIX. And it appears to be in C.

  126. Followup to smash hit Vista already in production by David+Gerard · · Score: 1

    SAN FRANCISCO, Redmond, Friday (UnGadget) — With Vista just out the door, Microsoft is drawing up plans to deliver its followup, Windows 7, codenamed Vienna, by the end of 2009. That would be a much faster turn-around than Vista, which shipped more than five years after Windows XP.

    Vista's uptake has been stupendous, with copies flying off the shelves and midnight queues on release day turning into major street riots, with police deploying water cannons and rubber bullets, to rival the release scenes for the PlayStation 3. It is expected to give a significant boost to the computer hardware industry, per the Mended Windows Theory of economics. But Vienna aims even higher.

    "We have a radical vision for Vienna," says Ben Dover, corporate vice-marketer for development. "It's definitely the one to wait for. You should avoid buying any other operating system or even looking at them until you see Vienna ... Except Vista, of course. That's pretty good. But Vienna is just so amazing. Wow! It's the most fantastic thing ever. Incredible. Mac OS 10.4 can't possibly hold a candle to it."

    So what will be the coolest new feature in Vienna? According to Dover, that's still being worked out. "We're going to look at a fundamental piece of enabling technology. Maybe it's hypervisors, or a new user interface paradigm for consumers, or rotating cubes like in XGL, or WinFS, which is definitely due to ship with Windows NT 4 in 1994. Or whatever Apple puts in Mac OS 10.6, really. Hell, I dunno. What's really shiny?"

    The much-derided Digital Rights Management system in Vista will be worked over. "We'll be including user-downloadable 'tilt bits,' which you can configure to your own liking. It'll require every user to supply a blood sample for DNA analysis, but of course that's only if you want to play premium content."

    Independent blogger Wiki Jellff was incontinent in his praise. "I am so excited about $NEXT_VERSION of Windows. It will surely go beyond just solving all of the problems with $CURRENT_VERSION, it will be an entirely new paradigm. Forget about security problems, that will be all fixed with $NEXT_VERSION. And they'll finally be ridding themselves of $ANCIENT_LEGACY_STUFF. Also there will be $DATABASE_FILESYSTEM. It'll be awesome! I wonder how $NEXT_VERSION will compare to $NEXT_NEXT_VERSION."

    "It's too early for me to talk about it," added Dover. "But over the next few months I think you're going to start hearing more and more."

    --
    http://rocknerd.co.uk
  127. Is it based on alien tech too? by edxwelch · · Score: 1

    There is a theory going around the internet that Vista was actually software recovered from the Roswell UFO crash site and reverse engineered. This explains the hardware compaitibly problems, the kernal was actually designed to interface with alien hardware.

  128. ReactOS as an NT replacement in WinGentoo? by tepples · · Score: 1

    emerge: there are no ebuilds to satisfy "=sys-kernel/windows-7". In your fictional NT-based Gentoo OS, why doesn't emerge suggest ReactOS as an alternative kernel to NT 7? Might the ebuild for Wine have a broken dependency list?
  129. It's the shoe that's 12 inches by tepples · · Score: 1

    I was under the impression that they'd standardized the foot at 12". While I was doing research for my homage to Miner's "Body Ritual Among the Nacirema", I discovered that it's the shoe over the foot that's standardized at 12 inches, where one inch is either (formerly) the average width of three men's thumbs or (now) 2.54 cm. "Foot" on Wikipedia has a plausible explanation:

    The average foot length is about 9.4 inches (240 mm) for current Europeans. [...] One attempt to "explain" the "missing" inches is that the measure did not refer to a naked foot, but to the length of footwear, which could theoretically add an inch or two to the naked foot's length. This is consistent with the measure being convenient for practical uses such as building sites. People almost always pace out lengths whilst wearing shoes or boots, rather than removing them and pacing barefoot.
  130. We need legacy software by pubwvj · · Score: 1

    Sadly, there is a tremendous amount of software out there that we still need. This is especially true of children's educational software but a great many small businesses have data in legacy programs with no options to upgrade. Apple should continue to support all the old legacy software. It really isn't that hard to do and it would make their system more appealing.

  131. yawn by wikinerd · · Score: 1

    apt-get install debian