Slashdot Mirror


32bit Win7 Vs. Vista Vs. XP

An anonymous reader writes "ZDNet's Adrian Kingsley-Hughes tested the latest Win7 build against XP and Vista and came to a surprising conclusion: Win7 performs better than the other 2 OSs in the vast majority of the 23 tasks tested. Even installation. 'Rather than publish a series of benchmark results for the three operating systems (something which Microsoft frowns upon for beta builds, not to mention the fact that the final numbers only really matter for the release candidate and RTM builds), I've decided to put Windows 7, Vista and XP head-to-head in a series of real-world tests...'" This review shows only a 1-2-3 ranking for each test, so there's no sense of the quantitative level of improvement.

105 of 641 comments (clear)

  1. I question the results. by Tubal-Cain · · Score: 4, Informative

    Take results with a grain of salt. He ranks Vista as better than XP on the AMD machine and as nearly equal on the Pentium machine.

    Of course, the AMD machine has 4 GB of RAM and the Pentium machine has 1 GB, so that could have something to do with it.

    1. Re:I question the results. by N!NJA · · Score: 4, Interesting

      WTH! if i had run those tests and come to the conclusion that Win7 installs faster than XP, i would have rushed to the basement, grabbed my Win3 floppies and performed a "3 vs 7 Install Death-Match"!

      that just sounds like a fisherman tale....

    2. Re:I question the results. by Ethanol-fueled · · Score: 3, Informative

      But the only number-one score for XP was on the Pentium machine - Move 100 MB files a quick glance through the results seemed to imply that XP usually came in second place for moving/opening smaller files, shutting down, and performance of few other tasks which would be attributed to a "stupider" computer. XP did come on second roughly half the time across both machines(from a quick glance, YMMV). It's nice that his charts are simple and straight-to-the-point instead of the usual spreading of the results across 10 pages, but I still find the results hard to believe.

      It's possible that the people who compiled the test results rated the OS's from 1 to 3 with 3 being the best ;) and Mr. Hughes confused the data when he wrote the article. And even if he didn't confuse the results, the 1-2-3 standings aren't very meaningful when the first-place OS opened the file in 1.255 seconds and the second place OS opened the same file in 1.26 seconds.

    3. Re:I question the results. by purpledinoz · · Score: 4, Insightful

      If he tested all 3 OSes on the exact same hardware configuration and compared those results, then the tests results are valid.

      My major problem with these test results is that he ranked them 1, 2, and 3. He should have put in the actual amount of time these tests took so we could see how much big of a difference it is. 1, 2, 3 tells me nothing. The difference between 1 and 2 could be 0.01% or 5000%.

    4. Re:I question the results. by Skal+Tura · · Score: 3, Informative

      i've found out that generally speaking ZDNet articles are total bullshit, with no relevance to the real world.

      This article and your example is just one example of that.

    5. Re:I question the results. by Firehed · · Score: 2, Interesting

      Partitioning the drive won't make the test any more fair. It may lessen fragmentation between each "chunk" of the drive than an OS would ordinarily take (if you decided to falsely assume that you can put more than one copy of Windows on a single partition without it blowing up).

      Hard drives are cheap, and quite re-usable. Get three identical ones. Do your testing, throw the results online, and then reformat the drives and throw them in the nearest fileserver.

      --
      How are sites slashdotted when nobody reads TFAs?
    6. Re:I question the results. by TheNetAvenger · · Score: 5, Informative

      Take results with a grain of salt. He ranks Vista as better than XP on the AMD machine and as nearly equal on the Pentium machine

      Sadly, as much as the SlashDot world not like to believe, this is accurate.

      If you have 1GB of RAM even on old hardware, Vista is as fast as XP, as the extra RAM offsets the Vista features overhead and Superfetch and other tricks of Vista help make up performance gains.

      With 2GB of RAM, Vista will be faster, even if you have a 800mzh PIII and a 1998 ATI video card.

      Vista or should we say the NT kernel in Vista is not slow or bloated, it is the extra features that Vista is doing that consumes RAM that offsets its performance gains over XP. (Search Engine, etc.)

      The CPU cycles for the Vista features are light, it is all about RAM. Just like with virtually every Windows and known OS update in history, they want more RAM for the features they add.

      - Even for Leopard to perform as fast as Tiger you need 1GB of RAM, which is funny considering Apple was making fun of Vista for the exact same reason.

      Here is how it works:

      512MB RAM - XP > Vista
      1GB RAM - XP = Vista
      1.5GB+ RAM - Vista > XP

      Windows7 so far is showing that even on 512MB is faster than XP in many cases, which is the result of the event based service manager, that unloads processes/services when not needed and saves RAM.

      An example on a running test system with 3Ghz P4 and 1GB RAM:
      Vista 41% - OS Consumed RAM
      Win7 20% - OS Consumed RAM

      See how that might help the Vista RAM overhead and put Win7 back in line with XP?

      PS And on this test system Vista is faster than XP - even in gaming with a Geforce 5600 video card.

    7. Re:I question the results. by je+ne+sais+quoi · · Score: 5, Interesting

      Take results with a grain of salt. He ranks Vista as better than XP on the AMD machine and as nearly equal on the Pentium machine

      Sadly, as much as the SlashDot world not like to believe, this is accurate.

      Here are some benchmarks right over at tomshardware that show that the "SlashDot world" in this case is accurate (amazing!).

      Conclusion: K.O. For Windows Vista? Windows Vista clearly is not a great new performer when it comes to executing single applications at maximum speed. Overall, applications performed as expected, or executed slightly slower than under Windows XP. There are some programs that showed deeply disappointing performance.

      This was on a system with 2 GB of RAM, so according to you Vista should have been faster, but it wasn't. So your idea that it's the RAM that's the problem is bollocks.

      Anecdotally, a colleague of mine was complaing her brand new lenovo thinkpad with Vista was slow compared to her imac -- she was kind of amazed that the they had the same processor and memory.

      --
      Gentlemen! You can't fight in here, this is the war room!
    8. Re:I question the results. by LVSlushdat · · Score: 2, Interesting

      I did that too, but only after making floppy disk images of all of them.. Never know when MSDOS 3.0-3.2 and 6 might be useful.. not to mention you don't even need to write the images to a floppy disk, you just boot from the floppy image in either vmware or vbox...

      --
      THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
    9. Re:I question the results. by TheNetAvenger · · Score: 4, Insightful

      Scheduler in Vista also performs worse than on XP (so MS had to resort to such hacks: http://blogs.technet.com/markrussinovich/archive/2007/08/27/1833290.aspx [technet.com] ).

      Saying this with the link you provide pretty much discredits anything you continue to say.

      You have no idea what you are talking about...

      Here:
      http://www.extremetech.com/article2/0,2845,2302499,00.asp

      Make sure you read the PCMark, then click Next to go to the Gaming Page. Vista outperforms XP in every test. (The only test it is a couple of points behind is the synthetic 3DMark.)

      And this is SP3 - the fastest XP compared to Vista.

      So go on again about how horrible the scheduler is in Vista, I am guessing you don't even know what a scheduler does and especially I know you don't know how it works in NT.

      If you want to put your hands over your ears and eyes and keep screaming, "Vista is slower", try clicking your heels together too, it is as likely to make it true and take you to Kansas.

      The Vista is slower myths need to stop and the idiocy behind them is really getting annoying.

    10. Re:I question the results. by Nutria · · Score: 5, Informative

      Unless you need the proprietary ATI or nVidia drivers, one reboot at the end of installation and it's done. And, if you do need to download those drivers, that's only one more reboot. Two at most, and you're done.

      Not true, even if you use [gxk]dm, you should be able to "activate" the new driver (after updating xorg.conf) by killing the dm. It'll auto-restart and thus load nvidia.ko.

      Of course, God only Smiles on you if you use startx.

      --
      "I don't know, therefore Aliens" Wafflebox1
    11. Re:I question the results. by WhatAmIDoingHere · · Score: 5, Informative

      The win7 beta EULA says no benchmarking. This is his way around that. If he could have posted times he would have.

      --
      Not a Twitter sockpuppet... but I wish I was.
    12. Re:I question the results. by Cyberax · · Score: 2, Informative

      What exactly discredits my words? Vista got so bad at audio performance that they had to hack around it by slowing down other parts of the system (by adding 'multimedia class scheduler'). It exactly mirrors my observations.

      I had to add a workaround to my application because waveOutGetDevCaps function became about 100x slower on Vista than on XP so it became impossible to use it in a single thread with interactive audio.

      Also, empirical observation: it became impossible to work with video on Vista in VMWare on my notebook. Even though it worked fine on XP.

      As for gaming benchmarks: I don't care about them. There are too many different parameters affecting them.

    13. Re:I question the results. by mrsteveman1 · · Score: 4, Funny

      Take results with a grain of salt

      Salt is forbidden by the EULA......and my doctor.

    14. Re:I question the results. by yoyhed · · Score: 3, Informative

      In my experience, as long as you weren't on a complete piece of shit of a computer, XP did start up faster than 2000, and also application startup times were noticeably faster.

      --
      WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
    15. Re:I question the results. by aliquis · · Score: 3, Insightful

      No need to if your Windows DVD happen to have all drivers either I guess, or atleast not many times.

      Do you still have to rebuild/reinstall modules for Linux for each version of the kernel? That's always awesome ..

      Atleast you don't have to reinstall every driver in Windows each time you've ran Windows update ...

      And before you moderate me flamebait, be sure to understand that it's NOT needed for all other oses.

    16. Re:I question the results. by aliquis · · Score: 2, Informative

      With a fresh partition he meant on a single clean 100% disk coverage partition before installation of the OS. As in not one partition for each OS. I know it looked weird but ..

    17. Re:I question the results. by Anpheus · · Score: 5, Funny

      And they say Linux isn't ready for regular users.

    18. Re:I question the results. by Score+Whore · · Score: 3, Insightful

      The problem is you just don't understand what the audio system in Vista does. It is by far the most advanced personal computer audio system available on any platform. Which is the reason that it needs a more consistent stream of data. Because adjusting the timing to the computer's various speakers so that the audio arrives at your head at the same time rather than leaves the speakers at the same time isn't free.

    19. Re:I question the results. by Jim4Prez · · Score: 2, Insightful

      Good point. However, I didn't see anything in TFA that said all operating systems were on one drive. Though it also did not say the contrary.

      This is NOT a benchmark or any kind. It is a paid-for-MS-Win-7 advert.

      Seriously, no real performance tester would grade results as 1,2,3. WTF?

      As others pointed out the diff of performance between Vista and Win7 could have been %0.001. or something negligible.

      The only thing I can think of is that this was given the olde "wink-wink" from MS to this "reporter".

      Great reporting work there Lou!

    20. Re:I question the results. by techno-vampire · · Score: 4, Informative
      Do you still have to rebuild/reinstall modules for Linux for each version of the kernel? That's always awesome ..

      That depends on which driver and how you install it in the first place. I use Fedora, so I can only use that for my example. If you use a different distro, YMMV. If you download the nVidia driver from the OEM site and install it, you will have to reinstall it every time you update the kernel, because of the way it works. Or, you can download kmod-nvidia and install that, because that gets updated whenever the kernel does. And, just in case there's a time gap, you can also install akmod-nvidia. That checks on boot to see if you have the latest kmod, and if it's out of date, builds another one on the fly.

      So, the answer is, yes, you do have to rebuild/reinstall modules, but the process can, and often is, done either by the distro maintainers, or on the fly without any user intervention.

      --
      Good, inexpensive web hosting
    21. Re:I question the results. by Anonymous Coward · · Score: 2, Informative

      Don't be coy. When you say MS had to resort to some sort of hack to make certain interactive processes more reliable, you have a certain connotation. Yet those "hacks" have been going int the Linux kernel for over a decade. Are all the different CPU schedulers and their ways of detecting which processes are interactive a "hack" in the same connotation as you refer to the NT Kernel?

      Come on...

      And on top of all this, you're complaining about audio performance in a VIRTUAL MACHINE. Surprise: VMWare drivers aren't as fast, as efficient as the real thing. Additionally, to support more features than they should, they often lie about their capabilities and end up overtasked. Many of the earlier virtual NIC drivers for many virtual machines would choke on gigabit traffic. Shocking, I know, that software emulation of a hardware interface can be slower.

      Try testing your interactive Windows code... in an actual Windows installation? Virtual machines add a whole layer of obfuscation to your already flimsy anecdote and, frankly, makes you Just Another Troll.

    22. Re:I question the results. by Cyberax · · Score: 2, Informative

      I quite understand what Vista audio system does (down to the driver level). For one thing, it doesn't use hardware acceleration (!!!) anymore and does everything in software.

      "It is by far the most advanced personal computer audio system available on any platform." - is a complete lie.

      JACK (http://jackaudio.org/) is probably the best personal high-quality audio system (it has a zero-latency design). It's followed by PulseAudio which is now not quite yet zero-latency but much more efficient.

      Adding some more latency into audiobuffers to adjust timing is a fairly trivial task. Also, a good implementation would just turn off this misfeature if the system uses only one sound sink.

    23. Re:I question the results. by Toonol · · Score: 2, Interesting

      He attached his name, you didn't. That means he may be lying, and you probably are lying.

      It's not pointless.

    24. Re:I question the results. by venuspcs · · Score: 3, Interesting

      I have been using Windows 7 Beta 1 (Build 7000) for 3 days and am utterly surprised. Here is a quick overview of the experience to date. On Wednesday I finished downloading the ISO and burned it to disc using Nero 9. Once burnt I removed the hard drive from my Toshiba Satellite A215-S5818 laptop and replaced it with a blank 120 GB SATA 4300 RPM drive with only 4MB Cache. I had previously upgraded my ram from 2 GB DDR2 to 4 GB DDR2 while using Vista and it had no discernible effect on performance. After installing the 120 GB hard drive I inserted the Windows 7 Beta 1 DVD and booted to it. The entire install (including initial setup and installing my Cellphone as a USB modem, setting up my internet connection and downloading newer Video Card Driver) took less than 30 minutes. I was blown away, especially considering the Internet Setup was 100% completely and totally different than under Vista, XP, 200, 98, etc. Then I went to restore my 40+GB of data from my external 1TB Buffalo DriveStation which was ridiculously slow (almost unuseable) in Vista. It took less than 20 minutes to restore all my data to the correct locations (even though I had to find some of them because they where in different places). After my data was restored I went to re-installing all my software (about 50 programs and games) which was all backed up to and restored from that same 1TB external drive. I was able to reinstall every single program in about 2 hours without a single reboot (until they where all installed). Office 2007 Professional installed in less than 5 minutes. Nero 9 took the longest at about 8 minutes. Firefox 3 less than 15 seconds. Google Chrome less than 10 seconds. Acrobat Reader 9 about 4 minutes. Adobe Photoshop CS3 about 7 minutes. All 10 of my games in less than 10 minutes. Once everything was reinstalled I started playing around with the OS. First thing I always try is to open several hundred Windows Explorer windows and see how many it takes to crash the system. Much to my surprise Windows 7 said "hell no you only need one and that is all we are giving you". Then I said well I will open a couple hundred pictures, again Windows 7 said "hell no your note" and kindly opened them all in 1 Preview Window. Then I said well let me open about 50 Word and Excel Documents at the same time and low and behold they all opened in less than 10 seconds (after I finished the First Run wizard) and didn't slow down the system AT ALL. SO while they where open I decided to open QuickMediaConvertor and convert a divx avi to vob. Once that was started I opened several different games (including Hardwood Solitaire IV, 3d Texas Holdem Poker, Freeciv and Mahjong Titans all at Maximum Graphics and Detail levels. Still my system hadn't blinked so I opened Google Picasa and selected a 1000+ pictures and applied the "I'm Feeling Lucky" filter. It was done in about 2 minutes. While I was waiting I went and played a game of Hardwood Solitaire IV with no noticeable slow down. Now thoroughly impressed I decided to crash it one way or another and opened every single thing I could find to open (about 100 programs) all running at the same time. Now the system finally slowed down as my processor (an AMD Turion X64 running at 2 Ghz with 2 cores) was almost maxed. Suprisingly my memory (3.5 GB usuable by Windows) was only using about 2.75 GB. System was still easily usable and probably faster still than a normal XP/Vista installation with normal programs running. Now that I have figured out I just can't make it crash I close all those programs. I was fully expecting CPU/Memory to stay up much higher than when I first booted. Much to my chagrin everything returned to roughly the same levels as a fresh boot. Then I started poking around and discovered some remarkable changes in Windows 7 that frankly I hadn't expected. Almost every single process is Sandboxed (Virtualized) by default. My older programs that are not Windows 7 compatible (every one I installed) was Automatically checked and if need be was run in Compatibility mode AUTOMATICALLY. In fact out of the 100

    25. Re:I question the results. by jhol13 · · Score: 2, Insightful

      If he tested all 3 OSes on the exact same hardware configuration and compared those results, then the tests results are valid.

      Kindly disagree. There are billion different ways to make or tune benchmarks so that your favourite (OS, language, whatever) will look better.

      The results shown are 100% meaningless.

    26. Re:I question the results. by Score+Whore · · Score: 2, Informative

      True. You have to calibrate it first. But once calibrated it delivers to the position you told it your head would be in.

    27. Re:I question the results. by je+ne+sais+quoi · · Score: 5, Interesting
      Fine. Here's some benchmarks from Vista SP1 vs. XP SP2 from ZDNet. Again, Vista is slower... despite the mighty passage of time:

      So, onto conclusions. Looking at the data there's only one conclusion that can be drawn - Windows XP SP2 is faster than Windows Vista SP1. End of story. Out of the fifteen tests carried out, XP SP2 beat Vista SP1 in eleven, Vista SP1 beat XP SP2 in two of the tests, and two of the tests resulted in a draw.

      Beyond that, I have yet to see any conclusive benchmarks posted by the defenders of Vista on this thread showing any proof that Vista is faster than XP, just empty assertions. What I do see is a bunch of Microsoft fanboys comforting themselves that their favorite brand released an OS that has turned out to be a flop.

      Let me qualify my positions here though. I have Vista installed on an old hard drive on a brand new PC -- my own conclusion is that Vista is not as bad as everyone makes out, but you all need to stop pretending that Vista is fast. It isn't. It's not terribly slow on nice hardware, and it looks very nice and it has some nice features, e.g., the DX10 features on new games, but it's not fast.

      --
      Gentlemen! You can't fight in here, this is the war room!
    28. Re:I question the results. by HappySmileMan · · Score: 3, Funny

      Of course it is, but the newbies have to suffer a reboot, only the elite get to keep their uptime even while updating graphics card drivers.

    29. Re:I question the results. by Score+Whore · · Score: 4, Interesting

      "It is by far the most advanced personal computer audio system available on any platform." - is a complete lie.

      True. I wasn't exactly clear. I'm talking OS audio subsystem for delivering audio from apps to the hardware. Not apps.

      JACK (http://jackaudio.org/) is probably the best personal high-quality audio system (it has a zero-latency design). It's followed by PulseAudio which is now not quite yet zero-latency but much more efficient.

      Right. Zero latency. Talk about lies. It establishes callbacks in the apps, writing into shared memory segments which are then mixed and delivered to the standard linux audio device. Yeah. Zero latency as long as you stay ahead of the playback. Just like pretty much every sound system since the days of the original Soundblaster Pro using DMA. Where's the signal processing layer in there? Oh, it's third party. Where's the channel synchronization? Can't find it. And awesome how it punts sample rate changes back to the apps. And it uses floats as the sample format? Talk about a really bad design decision. I mean you get three of four apps going in hi definition audio (96/24/7.1) and you're going to be seeing twenty or thirty percent of your system going down the shit hole just to do sample format conversions. And what is the upside? Nothing. For every 32 bits of sample data you get 24 bits of mantissa and a useless exponent. And shockingly enough it's all software. Where's that hardware acceleration you're so fond of?

      And what happens under load and the realtime scheduler can't quite keep up? Ah, I see, you get drop outs. What happens on Vista? Nothing, they hook into the scheduler to guarantee that their audio paths get time on the CPU.

      Adding some more latency into audiobuffers to adjust timing is a fairly trivial task. Also, a good implementation would just turn off this misfeature if the system uses only one sound sink.

      It's not a matter of delaying individual streams. It's a matter of delaying individual channels from the same stream. So that your rear speakers sitting against the far wall behind you play just a bit earlier.

    30. Re:I question the results. by ozmanjusri · · Score: 5, Informative
      If he could have posted times he would have.

      But he could have benchmarked Vista and XP, then given an above/below rating for Windows 7.

      And in fact, he HAS performed that test in the past and come to the conclusion that XP outperformed Vista.

      The fact that his results are reversed this time must throw serious doubt on his credibility.

      --
      "I've got more toys than Teruhisa Kitahara."
    31. Re:I question the results. by Daengbo · · Score: 5, Informative

      The test you link to used SP2, while the new tests use SP3. XP SP2 and SP3 aren't the same thing. In fact, most benchmarks put Vista SP1 ahead of XP SP3 or at least within spitting distance of each other.

      I'm not a big fan of Adrian, but he does hardware pretty seriously and lays out all his testing method well enough for you to duplicate it.

    32. Re:I question the results. by Daengbo · · Score: 2, Informative

      Adrian does an enormous amount of pro-Ubuntu writing on his blog. Considering his closing paragraph contains

      "And if youâ(TM)re put off by things such as activation and DRM, then Windows isnâ(TM)t the OS for you (good news is there are others to choose from)."

      I don't think MS is going to be paying him any money for his posts.

    33. Re:I question the results. by CommentThingSucks · · Score: 2, Insightful

      This guy -- an employee of ZDNet -- is running a pirate copy of Windows 7 (only 32-bit, the 64-bit version is not on the pirate sites). Why would a "EULA" matter.

      It's disgusting that ZDNet condones this.

    34. Re:I question the results. by Cyberax · · Score: 3, Informative

      "Right. Zero latency. Talk about lies. It establishes callbacks in the apps, writing into shared memory segments which are then mixed and delivered to the standard linux audio device."

      That's pretty much all I want from my audio system. Just give me a precise control over my audio stack and then you can build anything on top of it.

      XP does exactly this - there's a fast, efficient, hardware-friendly kernel streaming layer.

      Vista on the other hand forces you to use inferior-quality stack because MS couldn't figure out how to do protected audio path with kernel filters.

      "Yeah. Zero latency as long as you stay ahead of the playback. Just like pretty much every sound system since the days of the original Soundblaster Pro using DMA."

      DirectShow is famous for its imprecise timing control due to KMixer ;) My previous employer made a lot of $$$$$$ by making time-correcting kernel streaming filters.

      "Where's the signal processing layer in there? Oh, it's third party. Where's the channel synchronization? Can't find it."

      Everything is third-party. JACK only gives you a microsecond-precise information about audio system. You can do the rest yourself.

      "And shockingly enough it's all software. Where's that hardware acceleration you're so fond of?"

      It's possible to have hardware filters in JACK. The problem is that hardware filters are not that useful for professional-type audio systems. Look at OpenAL/EAX for hardware acceleration of spatial sound and other goodies.

      BTW, OpenAL Creative Drivers even work on Vista by bypassing all its audio stack.

      And.... SURPRISE! Windows Vista uses 32-bit floats as internal audio sample format ( http://blogs.msdn.com/larryosterman/archive/2007/04/03/volume-in-windows-vista-part-1-what-is-volume.aspx )!

      "And what happens under load and the realtime scheduler can't quite keep up? Ah, I see, you get drop outs. What happens on Vista? Nothing, they hook into the scheduler to guarantee that their audio paths get time on the CPU."

      Newsflash: if Vista scheduler can't quite keep up - you'll get sound drop-outs (I _do_ get them when I test my audio app on VMWare). There's no way around it. Realtime scheduler guarantees that your audio stack will get the highest priority, just like in Vista.

      "It's not a matter of delaying individual streams. It's a matter of delaying individual channels from the same stream. So that your rear speakers sitting against the far wall behind you play just a bit earlier."

      That doesn't matter. It's still not hard to do using kernel streaming.

      I can distinctly remember that nice '3d-room' settings on my Creative Audigy 2 back in 2003. All in hardware.

    35. Re:I question the results. by broeman · · Score: 2, Interesting

      I found out on my dads old crappy laptop (Windows XP preinstalled), that a clean XP install runs about right on his machine. After I install SP2 the laptop comes to a crawl (probably when it has to load all the new security applications). 10-15min from login to a fully working desktop, as on vanilla XP max. 2min.

      If I didn't have compatibility issues with Windows 2000, I would still be using it (for games, that is). It is the only Microsoft product I have ever been content with.

      --

      (yes this can be compared with sex)
    36. Re:I question the results. by dominious · · Score: 2, Insightful

      I've got one thing to say:

      for the love of god use <br>

    37. Re:I question the results. by Fred_A · · Score: 2, Informative

      Unless you need the proprietary ATI or nVidia drivers, one reboot at the end of installation and it's done. And, if you do need to download those drivers, that's only one more reboot. Two at most, and you're done.

      The only reason you'd ever need a reboot when installing Linux (apart from the obvous one to boot into your freshly installed system) would be if a new kernel had been released since your installation disk image had been issued and you have to upgrade. A kernel upgrade is the *only* case you have to restart a Linux (or pretty much any Unix nowadays for that matter) system (unless you managed to lock it up tight).

      Video drivers are merely kernel modules (loaded dynamically, so no reboot) and a X11 server, thus requiring only a restart of the X server. So in layman terms, log out, restart your X display manager (or press Ctrl-Alt-Backspace, it will restart by itself), log back in and you're done.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    38. Re:I question the results. by techno-vampire · · Score: 2, Insightful

      Granted. But to the average user, logging out and back in (with or without restarting the X server) is the same as rebooting. As far as Aunt Minnie is concerned, it takes at most two reboots to get her Linux box installed and running.

      --
      Good, inexpensive web hosting
    39. Re:I question the results. by nabsltd · · Score: 2, Informative

      Optical media starts at the inside (i.e., closest to the hub).

      Magnetic media starts at the outside.

    40. Re:I question the results. by Frools · · Score: 3, Interesting

      I know you were just making a joke but on Vista you can actually update graphics drivers without rebooting.
      The installer will tell you to reboot anyway, but the driver has been updated.
      This is possibly the best feature in Vista ;)

    41. Re:I question the results. by Score+Whore · · Score: 3, Insightful

      Everything is third-party. JACK only gives you a microsecond-precise information about audio system. You can do the rest yourself.

      So what you're saying then, if I got this right, is that the best audio system on the planet is the one that you have to write yourself? Awesome.

      That doesn't matter. It's still not hard to do using kernel streaming.

      Didn't say it was hard. Said no other OS is doing it. Your argument seems to be that it's possible to do something, therefore it's already been done. To go for the car analogy, you are saying that since you can melt a Honda Civic down and recycle the materials into some of the parts needed to custom build a super car, a Honda Civic is better than a Bentley Continental.

      Show me another OS that, out of the box, has the same feature set that Vista has. Any linux distro. Any kernel. And I'll concede that Vista doesn't have the most advanced audio system. Until them blather on, but you're still wrong.

    42. Re:I question the results. by prisoner-of-enigma · · Score: 2, Informative

      This is NOT a benchmark or any kind. It is a paid-for-MS-Win-7 advert. Seriously, no real performance tester would grade results as 1,2,3. WTF?

      If you'd get that enormous chip off your shoulder for just a microsecond, you'd realize that the Win7 Beta EULA specifically forbids benchmarking. If he'd posted actual times or scores, MS can and would sue to get his site taken down. He did the only thing he could, which was posting 1st/2nd/3rd scores.

      Instead of being so quick to scream "he's being paid by MS" (something, by the way, you have absolutely no basis for claiming), you'd appear less of an idiot if you bothered learning a bit about what you're frothing. I'll also remind you that Win7 is not available for purchase and won't be for another 6-12 months. Far from MS paying him to review Win7, they have a vested interest in not making people think they need to wait for Win7. Every person who sticks with XP while waiting for Win7 is a lost Vista sale.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    43. Re:I question the results. by anthonys_junk · · Score: 2, Informative

      Yeah, that's why you can 'short stroke' a magnetic HDD (mostly done in a RAID 0 setup) to only use the outside of the platter. It's not terribly effective but it may give you a small speed boost until frag kicks in.

      --
      Barbara Felden claims prior art on the flip phone, sues Motorola, Nokia.
  2. Still making 32 bit? by Dyinobal · · Score: 5, Interesting

    When are 32bit OSes going to start going away?

    1. Re:Still making 32 bit? by Tubal-Cain · · Score: 4, Informative

      I agree. Nobody is selling 32-bit processors anymore.

      Linux can handle 32-bit applications on 64-bit OSes. Surely MS can do the same?

    2. Re:Still making 32 bit? by vux984 · · Score: 4, Insightful

      Linux can handle 32-bit applications on 64-bit OSes. Surely MS can do the same?

      Of course they can, and do. Vista x64 runs 32 bit apps just fine.

      Unfortunately MS doesn't have the source for all the devices out there, and can't just recompile all of those to be 64-bit, and the 3rd party vendors that can do it, would rather not spend the effort -- hell, they kicked and screamed and did a half-assed job of updating their drivers to work with Vista in 32 bit (the main source of most real Vista woe).

    3. Re:Still making 32 bit? by Tubal-Cain · · Score: 4, Informative

      32bit or 64bit is essentially meaningless...

      Unless you have more than 3.5 GB of RAM

    4. Re:Still making 32 bit? by DigitAl56K · · Score: 3, Interesting

      What bothers me about Vista 64 is that Microsoft do not let you load unsigned drivers. Got a driver from a vendor that's not signed? You have to go through the trouble of signing it yourself and kicking your OS into test mode. The problem became worse with SP1 when MS made several known workarounds disappear.

      I understand they're trying to work against root kits but I'd rather be able to easily install any drivers I choose on my own system then have Microsoft protecting me against myself and causing me all kinds of grief. I've also never been hit by a root kit and I would guess that regular viruses are just as problematic and more common for nearly everyone.

    5. Re:Still making 32 bit? by Ethanol-fueled · · Score: 2, Funny

      I'm glad you brought that up, bro.

      It's like all the wackos out there want to stop using 8-bit and 16-bit processors and replace them with Pentiums. I'll upgrade my toaster when they pry it from my cold, dead hands!

    6. Re:Still making 32 bit? by 644bd346996 · · Score: 3, Insightful

      64bit x86 gives you 4 times the general purpose register space and twice as many vector registers, which is a huge benefit for an architecture that's so lacking in register space.

    7. Re:Still making 32 bit? by TheNetAvenger · · Score: 5, Informative

      lol. you've drunk the kool-aid, 32bit or 64bit is essentially meaningless

      There is kool-aid, but you need to check you own cup.

      If you are referring to the Apple marketing machine, they ya, 32bit and 64bit are not much different, just larger memory addressing. (Of course OS X is still a 32bit OS could be the reason they like to create this mis-perception.)

      On a real 64bit OS, there are 64bit registers and tons of other tricks and optimizations that happen, let alone full 64bit drivers that can shove data to devices oh like Video cards much faster.

      If you look at Vista x64 it performs 15% faster than Vista x32 if you have 2GB of RAM.

      This includes not only the OS's operation, but even 32bit applications running on the OS.

      You see when you have a 64bit memory addressing and can optimize for this in the memory manager you no longer have FS and pagefile lookkup tables for extended amounts of RAM.

      You also can do like Vista x64 does and shove two 32bit memory writes into on 64bit address space, so when it can, you get double the read/write performance out of the memory chip because you are pulling two 32bit chunks in one read cycle.

      And we could go on and on and on...

      Understand yet?

    8. Re:Still making 32 bit? by Cowmonaut · · Score: 2, Interesting

      FYI, a commonly overlooked issue into why some 32-bit applications didn't initially work on a 64-bit OS was the 16-bit installer program. Occasionally, you could just move file programs over from a 32-bit XP install to a 64-bit XP or Vista install and run it without too many issues. Granted this is largely an irrelevant issue now that 64-bit OSes are prevalent but still. I'm sure in a business environment more than a domestic its still an issue.

    9. Re:Still making 32 bit? by DA-MAN · · Score: 4, Interesting

      I agree. Nobody is selling 32-bit processors anymore.

      Intel's Atom processor is 32-bit.

      Linux can handle 32-bit applications on 64-bit OSes. Surely MS can do the same?

      It's the proprietary drivers that make it hard for MS to do the same. In Linux the vast majority of drivers are maintained in source, so this isn't as much of a problem.

      --
      Can I get an eye poke?
      Dog House Forum
    10. Re:Still making 32 bit? by 644bd346996 · · Score: 2, Informative

      While it may take a particularly clever compiler to use the extra width of the registers when operating on 32bit data, even the most basic compilers will be able to take advantage of the fact that there are twice as many general purpose registers.

    11. Re:Still making 32 bit? by DA-MAN · · Score: 3, Informative

      Unless you have more than 3.5 GB of RAM

      Unless you allocate more than 3.5 GB per process.

      PAE has gotten around the 4 gig limit a long time ago.

      --
      Can I get an eye poke?
      Dog House Forum
    12. Re:Still making 32 bit? by Just+because+I'm+an · · Score: 2, Insightful

      If you are referring to the Apple marketing machine, they ya, 32bit and 64bit are not much different, just larger memory addressing. (Of course OS X is still a 32bit OS could be the reason they like to create this mis-perception.)

      This is true(ish), I grant you, however at least there is a clear intent to redress this issue for the client OS within the next few months with the release of snow leopard and that will be the only OS Apple will distribute.

      Microsoft will undoubtedly have versions of Windows 7 in 32 and 64-bit and by default distribute the 32-bit version. I completely understand why they might do this, I might even be convinced it is in their interest to do that, but I think it holds back the development of the platform in general.

      Finally Leopard itself does support full 64-bitness, for example Apache on OS X Server is running as a proper 64-bit application. I don't mean to dispute your claims that it remains effectively a 32-bit OS, just that it's not as cut and dried as it might appear.

    13. Re:Still making 32 bit? by TheNetAvenger · · Score: 3, Insightful

      There are some good TechNet articles at Microsoft that would give you specific answers of what happens on Vistax64 with regard to 32bit memory allocation. (The SDK/DDKs will also give you some answers.)

      Also check out interviews with NT engineers at channel9.msdn.com.

      As for you questions regarding the compiler, yes. If you compile your application for 64bit, optimizations like you describe are handled unless you disable them in the compiler.

      However, the things I was talking about in reference to Vistax64 is that running 32bit code on the 64bit OS, gives the OS the ability to make decisions like this on the fly for upper level system RAM (not CPU level optimizations/etc). So on Vista x64, and running your 32bit code, it will execute faster on Vista x64 because the OS is running faster, but also if you are using large chunks of RAM, the 32bit application will get additional boosts by combining 32bit memory chunks into one read/write of 64bit space.

      Once you get what you need on what Windows x64 is doing, head over to AMD and read about CPU specific optimizations that happen in the register and cache levels of the CPUs when executing 32bit code.

      Even if you stick to 32bit development, your applications get benefits of Vista x64.

      ---

      Side Note for others:
      Anyone here that installs Windows for gaming, if you have 2GB of RAM, grab the 64bit version of Vista, you will easily get 15% more performance out of your games over Vista x32 and XP.

      And if you play MMOs, your zone and load times in either version of Vista will make you never want to touch XP again as it is often a 10x to 20x difference due to SuperFetch.

    14. Re:Still making 32 bit? by Metasquares · · Score: 4, Informative

      Despite supporting PAE, Vista-32 still limits addressable physical memory to 4 GB (Wikipedia). PAE will also run into problems at 64 GB, whereas 64-bit machines shouldn't reach another addressing limitation until they hit 16 EB.

      Transitioning to 64-bit is a better solution in the long term.

    15. Re:Still making 32 bit? by Cyberax · · Score: 2, Insightful

      Driver signing requirement is NOT for rootkit prevention.

      It's here to make pro-DRM studios happy. Plain and simple.

    16. Re:Still making 32 bit? by 644bd346996 · · Score: 3, Interesting

      And in practice extra x86-64 registers are not that great improvement because modern CPUs got very good at pipelining and data prefetching.

      Good point. However, those extra registers may matter quite a bit more for something like the 64-bit Atom processors, which deliberately forgo most speculative features that mitigate register pressure. It would be interesting to see whether it's a better use of silicon to make an out-of-order processor or a 64-bit in-order processor when you're operating under the power constraints of the Atom. The current existence of 64-bit in-order Atom processors suggests that the performance per watt impact of 64-bit is better than out-of-order execution. I suspect this is because 64-bit takes less silicon than OOE, in a similar manner to how useful a good implementation of simultaneous multithreading can be.

    17. Re:Still making 32 bit? by fuzzyfuzzyfungus · · Score: 2, Informative

      Umm, you do realize that Microsoft only supports 4 gigs of RAM, even with PAE, for most 32 bit Windows versions? The only 32 bit MS OSes that support more than 4 gigs of RAM are the Windows Server Enterprise and Datacenter editions(which are pretty much irrelevant to the home user). http://msdn.microsoft.com/en-us/library/aa366778.aspx

    18. Re:Still making 32 bit? by LenE · · Score: 2, Informative

      You need to check out how Snow Leopard is built a little better, as it will not be 100% 64bit. It will be 'more' of a hybrid, but still not a full 64bit OS.

      Actually, it will be a full 64-bit OS from kernel to user with legacy support for 32-bit carbon and cocoa. By your reasoning, XP 64 and Vista 64-bit aren't 100% either as both use the less-elegant WoW for 32-bit stuff and System32 for the 64-bit bits. This, in addition to the fact that Microsoft requires separate versions, rather than just shipping a product that covers both architectures. There's also that pesky problem that most programs for Windows are 32-bit apps, and many are very fragile on the 64-bit Windows platform. I'll stop now.

      Because it DOESN'T matter in the Windows world. 32bit applications get performance benefits on the 64bit OS.

      As it also happens with Snow Leopard, as the kernel goes full 64-bit (on Core 2 and newer machines). Current Leopard already gives the 64-bit benefits of increased registers and larger VM space to 64-bit programs, so there isn't a lot more to gain. These capabilities are not magically transferred to 32-bit apps under any OS, as the architecture is different, so there is no way that Vista-64 or Win7-64 will gift 32-bit apps with more than the 2GB of address space that they are currently allowed (vs. the full 4GB that OS X gives to 32-bit apps). Any speed increase comes from taking less time for register shuffles on 64-bit programs, giving more time to all processes.

      Also if developers want to provide a full 64bit version, it is a simple recompile, you don't have to re-write the application like a lot of people (Adobe for example) find they have to do on OS X. This is why if you want a 64bit version of Adobe software, you need Vistax64, as the development APIs Apple sold Adobe never got moved to 64bit as promised.

      Oh ho! What a canard. A simple re-compile was what has been hamstringing 64-bit graphics drivers and codecs for the last three years or so on XP-64 and Vista-64? Apple doesn't sell it's API's, it just publishes them. Adobe had 8 years of warning and opportunity to move it's cruft from Carbon to a cleaner, more modern API, and they decided to play chicken because Apple started eating their lunch with Final Cut Pro and Aperture. Being Carbon developers, they knew that it would not be an easy to clean up all of the legacy crap in the API without breaking backwards compatibility. Developing the iPhone was the final nail in Carbon's coffin.

      All MS API sets(development platforms) move to 64bit, even old 16bit applications can be recompiled as 64bit applications. (You can't do this with System 9 applications, nor even the whole early 32bit transition APIs Apple provided.)

      Yes, this is why Microsoft came up with thunking and the 16-bit \System folder and the 32-bit \System32 folder for Win32, which became the 32-bit \WoW and 64-bit \System32 folder. Brilliant. It isn't quite fair to drag System 9 applications into this mess. Do old Borland TurboPascal programs magically compile to 64-bit? Most System 9 programs were done as projects in Metrowerks Code Warrior with the PowerPlant framework, a system that was bought and buried by Motorola. Mac OS 9 was a cooperatively multi-tasked mix of PowerPC and 680x0 code, which used legacy system calls that needed Paschal syntax. OS X is basically a BSD Unix with no 680x0 code that uses GCC for compilation. Different architectures, compilers, system calls, hell the only things that are the same are the word "Mac" and "Apple". Up until the the Intel switch, you could run Mac OS 9 code, similar to WoW, without a re-compile. In most cases, the question is why would you want to.

      Do you remember the Apple ads talking about the FIRST 64bit Personal Computer? How ironic that this many years later it still isn't even running a native 64bit OS, where Windows has been doing 64bit versions s

    19. Re:Still making 32 bit? by joib · · Score: 2, Informative

      Unless you're playing tricks like storing other data into the upper bits of pointers, this shouldn't matter; from the application perspective addresses are 64-bit. With current hardware a bunch of bits is always zero, but allowing applications to use more memory should come transparently with newer hardware generations, with no recompilation necessary.

    20. Re:Still making 32 bit? by tkrotchko · · Score: 2, Interesting

      "Rootkits? You wish. Microsoft was trying to prevent people from doing sneaky things like rip DVDs and record the audio output from programs like Windows Media Player to "rip" DRMed files."

      Vista x64 does not prevent people from ripping audio streams, DVD disks or Blu-Ray disks. Almost all the tools that allow this on 32 bit windows work on 64 bit windows. Even the Slysoft people don't have a problem with 64 bit windows.

      --
      You were mistaken. Which is odd, since memory shouldn't be a problem for you
    21. Re:Still making 32 bit? by TheRaven64 · · Score: 2, Interesting

      PowerPC is freaking ancient and were supported for 7-8 years, which is all you can reasonably expect

      The last PowerPC Mac I bought was less than 8 years ago. They only started selling Intel Macs in 2006 - about three years ago from the launch of Snow Leopard - and they didn't transition all of their product lines until some time in 2007. Leopard was the only version of the OS to be released after the switch. Not supporting three-year-old hardware is pretty poor, even by Apple's standards.

      --
      I am TheRaven on Soylent News
    22. Re:Still making 32 bit? by TheRaven64 · · Score: 2, Insightful

      I don't often defend Microsoft, but in this case I think they are right. Running an unsigned driver is something that can totally compromise your system and only needs to be done by a small number of people. Making it difficult is exactly the right thing to do. UAC makes it far too easy to click 'allow' without reading the dialog for this kind of thing.

      --
      I am TheRaven on Soylent News
    23. Re:Still making 32 bit? by UnknowingFool · · Score: 2, Informative

      Since MS adopted the LLP64 model, there really isn't a need to recompile 32 bit code to make them run on a 64bit OS. This model maintains maximum backwards compatibility but sacrifices it for forward compatibility. A 64 bit program would have to be rewritten for a 32 bit OS in this model. So companies would have to write and maintain two different source code trees for separate compiled versions.

      Unix and Linux went with a LP64 model. Forward compatibility is stressed instead of backwards compatibility. In this model, companies would have to maintain two compiled versions but the source code would be the same but compiled differently.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    24. Re:Still making 32 bit? by vux984 · · Score: 2, Insightful

      I'm not sure what your point is.

      So proprietary code stifles the advancement of hardware....

      No, proprietary code stifles the support of legacy hardware.
      New hardware, conversely, tends to be supported by proprietary software first, and the FOSS comes later.

      And niche hardware tends to be exclusively supported by proprietary software, and FOSS never gets around to adding support. (Think medical instruments, etc...)

      Meanwhile, open source drivers for linux and bsd have been ported to 64bit hardware years ago.

      Yup, exactly. Your old 10 megabit network card will have 64-bit latest kernel support on OSS while the windows drivers haven't been updated since windows 98. But the latest nvidia graphics card? Proprietary drivers are way ahead of the OSS stuff, and it will be years before the OSS stuff catches up.

  3. Completely useless by beef3k · · Score: 2, Insightful

    This review shows only a 1-2-3 ranking for each test, so there's no sense of the quantitative level of improvement.

    In other words a totally subjective opinion with no numbers/statistics to back it up, also known as Totally And Utterly Useless.

    1. Re:Completely useless by bhpaddock · · Score: 5, Insightful

      It isn't useless. It isn't "subjective" since it's based on actual objective measurements. It conveys the indication that Windows 7 has *broad* performance improvements.

      It has been suggested that exact numbers were not given due to the beta's EULA clause that prohibits benchmarking against the pre-release build.

    2. Re:Completely useless by poetmatt · · Score: 3, Insightful

      You can dance all you want, but the truth is we have no evidence that they even performed testing since there are no numbers. That's not subjective, it's called an editorial/not factual.

      If there are numbers out there, other people can compare and go "hey, that isn't what I got using the exact same setup as you tested with", etc.

      The eula literally says "NO BENCHMARKING ALLOWED" so this means that this guy isn't even allowed to benchmark. It doesn't say "no posting of a benchmark", it says no benchmarking period. Therefore, he hasn't even done benchmarking. See how this works?

    3. Re:Completely useless by Shadow7789 · · Score: 5, Insightful
      No, you're wrong. Read the EULA.

      You may not disclose the results of any benchmark tests of the software to any third party without Microsoft's prior written approval.

      What the author did was within the bounds of the EULA since he didn't disclose the results (the numbers).

      What really frustrates me though is that you would suggest that the author is LYING. What gives you the right to make such accusations? Are you working on some kind of historical precedent? Do you know the author personally? Has he lied before? Or are you just being a douche? I can completely understand if you want to see the raw data, so do I. But really, I thought Slashdot attracted a smarter caliber of readers who don't have to result to personal attacks. Apparently, I was wrong.

      For the record though, the relative performances he gives us are a valuable indicator. Are you saying that a race scored based upon who crossed the finish line first instead of a stop watch is not a valid way to measure the performance of the athletes in it, because I can think of plenty of sports (even a few Olympic ones) that are scored this way. That makes no sense. Maybe next time, you should think before you post.

  4. win7 rocks by moniker127 · · Score: 2, Interesting

    I'm using build 7000 right now. And yes, it is clearly quicker than XP, and there arent as many point where it has the potential to stop. It feels very fluid. Its the best windows version yet but a fair margin.

    1. Re:win7 rocks by 3vi1 · · Score: 3, Funny

      A friend showed me build 7000 for the first time a few minutes ago.

      It blue screens in kl1.sys and reboots the whole system every time he tries to register the Kapersky AV it nagged him to install.

      I'm showing him Kubuntu 9.04 alpha 2 now, but I haven't found a way to show him a crash.

    2. Re:win7 rocks by DAldredge · · Score: 4, Insightful

      Installing kernel level software that isn't certified for the OS you are using isn't the smartest thing in the world to do.

    3. Re:win7 rocks by networkzombie · · Score: 2, Interesting

      His antivirus software doesn't work in a beta version of an unsupported OS? He should contact Kaspersky and complain. Maybe he can get his money back. I have b7000 running on a P4 2.8 (800MHz FSB) with 1 GB RAM and it performs pretty well. No crashes at all, but I'm throwing various hardware at it, not software. It really likes multiple video cards with multiple monitors on each card. The only slowdown I saw was opening the event log. The new event log is so bloated that it acts just like Vista. YMMV.

    4. Re:win7 rocks by 3vi1 · · Score: 3, Informative

      So, you're saying that when Win7 nags you and clicking the nag opens up http://www.microsoft.com/windows/antivirus-partners/windows-7.aspx, they're pointing you to uncertified software? BTW - I just went to his system and did the install again and didn't get any warning about installing uncertified software, so I'm guessing it's signed.

      Are you guys actively testing Win7, or just ragging on people that don't report the bestus experience ever?

    5. Re:win7 rocks by dreemernj · · Score: 4, Insightful

      Windows is working with them to develop security software. So, what actually happened is your friend installed a Beta test of an OS, and then installed a technical preview beta of antivirus software and on his hardware something goes wrong.

      As long as he reported the issues to MS, then it all seems like standard operating procedure for using test software running on a test OS.

      --
      1 (short ton / firkin) = 89.1432354 slugs / keg
  5. Two reasons for this by bhpaddock · · Score: 3, Insightful

    1) Netbooks. The Atom processors in most netbooks are 32-bit only. Also consider any other embedded scenario where 64-bit CPUs are not available, practical, or where 64-bit addressing is not necessary.

    2) Upgrades. Windows does not support upgrading from a 32-bit OS to a 64-bit OS (you have to choose the "clean install" option). If you want to sell upgrade discs to the vast majority of current customers, you need to sell 32-bit copies.

    1. Re:Two reasons for this by Belial6 · · Score: 4, Insightful

      There is no excuse for MS supporting any legacy code in Win7. None. Zero. Zip.

      If they were halfway competent, they would port VirtualPC to Win7, include a modified copy of XP that will only run 1 program at a time, and include drivers to share the clipboard between the host and the guest. A little configuration magic so that launching the virtual machine also launches the application instead of a desktop, and virtually 100% all current software would not only work, but could be sandboxed by default. If they really wanted to do things right, they would include images for every version of Windows and MS-DOS ever released. This would not only improve security, clean up the API DRAMATICALLY and keep only one code base which would be fully 64-bit but it would also make Win7 by far the MOST backward compatible version of Windows ever released. Hell, they could make even make it XBox 1 compatible and let all of their partners re-release all of their XBox 1 games as "XBox Classic".

      Of course, this would have the negative side effect of not letting them claim that backward compatibility was the reason for all of the crap in Windows.

    2. Re:Two reasons for this by cbhacking · · Score: 2, Interesting

      Cool idea. Now let's take a step back and look at the realities:

      Port VitrualPC to Win7: I suspect it'll already run on Win7, but even if it won't they'd do that anyhow.

      Drivers to share the clipboard: Sure. Of course, you'd also need drivers to handle OLE stuff (drag-and-drop, for example). I'm sure it could be done, but don't make the mistake of assuming it's trivial. It takes a bit of work (made utterly painless, but still required) just to allow near-seamless mouse movement in and out of the virtual window.

      Launching virtual machine now launches the application rather than the desktop: this is pretty easy. Of course, you still need to account for the bootup time of XP. Even with hardware virtualization, this is at least tens of seconds. I'd really rather not wait that long every time.

      Virtually 100% all current software would work: Except, you know, anything that needs 3d hardware acceleration. Or direct driver access. Or more than two COM ports (yes, such programs exist, and VPC's limitation to 2 COM ports is an issue for the one program we have that won't quite work right in Vista. The problem could be worked around, but it's indicative of the greater issue).

      Sandboxed by default. How sandboxed? Windows supports an incredible number of forms of inter-process communication. Some programs rely quite heavily on such things. You could allow the VPC to run one process and all the programs that it spawns, perhaps, but there would still be problems. Hell, this sort of excessive sandboxing is supposedly the reason the iPhone can't even handle simple cut/copy/paste!

      How much RAM do these virtual systems have? Each virtual machine would need a good chunk of RAM, especially with the overhead of running all those excess copies of Windows. However, they would also compete with native apps for physical RAM. What do you do when some process that runs on Windows 2000 starts demanding 2GB of working set? Is VPC supposed to automatically enlarge the physical RAM allocated to that machine? Is it supposed to use its own pagefile? Perhaps you'd like to somehow get it to use the global pagefile instead?

      I hope this is enough to help you realize that, noble though your end goal is, your method simply would not work.

      --
      There's no place I could be, since I've found Serenity...
    3. Re:Two reasons for this by Belial6 · · Score: 2, Interesting

      Drivers to share the clipboard: Sure. Of course, you'd also need drivers to handle OLE stuff (drag-and-drop, for example). I'm sure it could be done, but don't make the mistake of assuming it's trivial. It takes a bit of work (made utterly painless, but still required) just to allow near-seamless mouse movement in and out of the virtual window.

      This stuff is already done by their competitors. So, even if it isn't 'trivial', it is something they will have to do anyway.

      Virtually 100% all current software would work: Except, you know, anything that needs 3d hardware acceleration. Or direct driver access. Or more than two COM ports (yes, such programs exist, and VPC's limitation to 2 COM ports is an issue for the one program we have that won't quite work right in Vista. The problem could be worked around, but it's indicative of the greater issue).

      So, your saying that MS sucks too much and does not have the resources to bring their product up the match their competitors who are already on the market? I'm not buying it.

      Sandboxed by default. How sandboxed? Windows supports an incredible number of forms of inter-process communication. Some programs rely quite heavily on such things. You could allow the VPC to run one process and all the programs that it spawns, perhaps, but there would still be problems.

      MOST applications don't share data via inter-process with other applications beyond a simple clip board. But even for the ones that do, you would at least know what applications were trying to access what. Even if you had the simple choices of "No Access", "Clipboard Access", and "Full Access", you would be head and shoulders above what we have now because even if some users just always said "Full Access", they wouldn't be worse off, and anybody that has any concern for security isn't going to do that. I know that I would certainly click "No Access" when my freeware Falangy Counting software asked for access to Quicken.

      Hell, this sort of excessive sandboxing is supposedly the reason the iPhone can't even handle simple cut/copy/paste!

      That is total BS. Cut/Copy/Paste does not work because while the iPhone interface is neat, it has some serious problems, and Apple simply chose not to implement cut/copy/paste. Likely because they felt it would make the interface too complicated.

      How much RAM do these virtual systems have? Each virtual machine would need a good chunk of RAM, especially with the overhead of running all those excess copies of Windows. However, they would also compete with native apps for physical RAM. What do you do when some process that runs on Windows 2000 starts demanding 2GB of working set? Is VPC supposed to automatically enlarge the physical RAM allocated to that machine? Is it supposed to use its own pagefile? Perhaps you'd like to somehow get it to use the global pagefile instead?

      Memory actually gets BETTER if you had them running in a virtual machine. Currently an XP application can only access 3 gigs of ram, and anything beyond that must swap to a physical disk. You see, back in the days before dirt was invented and the memory that an OS would use could be counted in bytes, we had this thing called a "RAM Disk". It was a chunk of memory that the OS saw as a physical disk, even though it was in RAM. Since a 64-bit OS could access 16 exabytes of RAM, the RAM disk starts to make sense again. If the machine were virtualized over a 64 bit OS, the swap file could be set to run from the disk, or it could be set to run from a ram disk which would mean that you could get far more real memory to the 32 bit application virtualized than you could from running it natively on a 32-bit OS.

      I hope this is enough to help you realize that, noble though your end goal is, your method simply would not work.

      No, this does not help me realize that the method would not work. It just shows that you are being short sighted about OSes, and don't really understand how computers work. Or have just drank the "MS said so, so it must be true" Cool-Aid concerning backward compatibility.

    4. Re:Two reasons for this by heffrey · · Score: 2, Informative

      Lots of people seem to think that Win32 API is a weakness of Windows when in fact it is its greatest strength. The stability of Win32 allows developers to target a huge range of operating systems with a single codebase (95, 98, ME, NT4, 2000, XP, Vista, 7). These days you only really need to support 2000 or perhaps XP and above, but being able to do that with a single binary API is a huge boon.

      People are forever going on about how hard Win32 is to code against. Well, once you take the time to learn it it's not hard. Only if you aren't very talented would it be a problem. In reality most developers don't code directly against Win32, they code against a higher level wrapper (MFC, VCL, Qt, WinForms etc.) which makes it quite simple.

      As a developer of commercial closed source software for Windows in a very small software shop I for one an hugely grateful for the stable and reliable development platform that MS has provided it. Without it we wouldn't have the successful business that we currently enjoy.

  6. No 64bit test and a 4gb system? by Joe+The+Dragon · · Score: 2, Interesting

    Do a 64bit test as well as most system today with with 3-4gb ram + video ram and other system stuff go over the 4gb limit 32bit.

  7. My benchmarking scheme by Anonymous Coward · · Score: 3, Funny

    Windows Vista 3rd
    Windows XP 2nd
    Windows 7 1st

    Windows 7 wins... it uses the least number of letters.

  8. Microsoft has a good version of Vista! by tkrotchko · · Score: 3, Informative

    Their 64 bit version of Vista is actually the best consumer level OS they've done so far. It's the version that should become Windows 7. It's stable, fast (way faster than the 32 bit version on my machine), and its backwards compatible with almost every application that I've tried.

    If they made the default install 64 bits, they'd actually be pushing forward an improvement in their consumer OS. As it is, we'll be living with Vista mk. II.

    I'll bet the folks who work on the 64 bit version are scratching their heads wondering why they bother!

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
    1. Re:Microsoft has a good version of Vista! by Belial6 · · Score: 3, Interesting

      No, it isn't. What is a problem is that MS has not integrated VirtualPC into Windows, and included a virtual environment to run your 16-bit apps in a 16-bit environment. I know it may sound like splitting hairs, but it is long past the time that MS should be leaving bad code in new OSes just to claim 'Backward Compatibility' when it is totally unnecessary.

    2. Re:Microsoft has a good version of Vista! by Detritus · · Score: 2

      It's a program that I used to setup and offload data from a portable data acquisition device. I plug a special RS-232 serial cable into the computer and the data acquisition device, and then run the program to offload the collected data and set it up for another run. It also has some features that let me analyze and graph the data, and export it to other programs.

      --
      Mea navis aericumbens anguillis abundat
  9. How does it "feel"? by john.picard · · Score: 5, Insightful

    He tested things like moving files around, compression, decompression... This is all good and fine, but it's probably not the thing that most people "feel" when they use a computer. What I would like to know is how snappy or sluggish does the operating system "feel" when using it for every-day tasks? Does everything halt while the hard drive cranks away when you click a menu? Do the GUI animations help use the computer or do they simply slow you down? That's the sort of thing that matters to most users. How often do you really have to move 100 MB or 2.5 GB of files around?

    1. Re:How does it "feel"? by Jugalator · · Score: 3, Informative

      How often do you really have to move 100 MB or 2.5 GB of files around?

      A benchmark like this still probably matters though, as if it's fast on moving 100 MB (a size more easily measurable than 10 MB), it's likely faster at 10 MB too. And it's at these ranges it starts creeping into everyday use and the "feel" you're talking of.

      --
      Beware: In C++, your friends can see your privates!
  10. Judge it when it's done by Opportunist · · Score: 2, Insightful

    I've said the same when people complained about crappy Vista beta results, so I will say it again: Judge the system's speed when it is done. No nanosecond earlier.

    The reason is simple. First, it's plenty possible that there are still parts missing. Parts that can weigh the system down again. In Vista's case, we saw a pretty good improvement in handling, but this can work the other way 'round too if early results are promising (maybe too promising) and optimizing takes a back seat to other matters.

    From what I can see so far, Win7 still has some stability issues. Improving stability often comes at the price of speed. It is entirely possible that MS tried to get a system out for "beta report" tests that is as fast as possible to get these desired effects. Vista's resource hunger and its sluggish handling was one of the core gripes reviewers had, so it was likely the first tests Win7 will be put to will be about speed and handling. Vista had no really crippling stability issues (aside of driver problem which are arguably the hardware supplyer's problem), so this won't be one of the things reviewers will make a big fuss about.

    So what did they produce for a beta review? Exactly what we have here. A system that is as fast as it can be, everything else back to the corner there. Yes, it's maybe crashing from time to time, but it's beta, you know, and Vista already was stable, so they'll get that done by release, no worries. Now imagine it was the other way 'round, stable as a rock but sluggish. Yes, it's beta, so the speed issues could be ironed out, but reviewers would have had a field day with it.

    Bluntly, I don't give a flying fsck about a beta review of Win7. Wake me when it's ready for release. In other words, when SP1 arrives.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  11. Re:win7 performance by Z80xxc! · · Score: 3, Informative

    Who likes chairs anyway?

    Steve Ballmer, that's who.

  12. No extra garbage by arkham6 · · Score: 2, Insightful

    I'm sure the fact that this build of windows does not have tons of extra bells and whistles installed, thus leaving more system resources for doing benchmarking.

  13. Notebooks? by hack++slash · · Score: 2

    Has anyone tested it on an Asus Eee or the like in comparison with performance of XP on the same machine?

    I think that would be an important test what with vendors clinging onto selling XP with laptops/notebooks for as long as possible.

    --
    To do something right, you often have to roll up your sleeves and get busy.
  14. It could be by ShooterNeo · · Score: 4, Insightful

    The general feeling around here is that no-one WANTS to believe it is even possible that Windows 7 doesn't suck. Because if that were true, that would sort of devalue everything done to improve Linux the last few years. (because if Windows 7 is fast and stable and lets you play games, that doesn't leave any room for Linux on the desktop)

    It could actually be that Microsoft got it right. It may be that the core of Vista is not as terrible as we all think it is. I've seen posts discussing how Vista uses a completely refactored kernel, with more layers of abstraction and cleaning up of many of the quirks of win32.

    Then, on top of this decent foundation, they overloaded it with poorly thought out gimmicks in an attempt to compete with Apple. In addition, some of their rewrites introduced new bugs, such as the networking problems where Vista machines are unable to talk to shared file servers.

    It's possible that Windows 7 succeeded. If they fixed the bugs, and ripped out some of the bloated, inefficient Vista code then you might have a decent OS after. Microsoft might be a monopoly, but if they sat on their heels for too long, eventually (it might take 10 years) alternatives would overtake them.

    1. Re:It could be by Shados · · Score: 2, Funny

      UAC can be disabled (and in general, UAC only confirms things that would request confirmation in other OS, or at least priviledge elevation... yeah yeah i know, people say "but in Linux you only have to sudo ONCE!), you can do that in Windows too...just doesn't seem anyone realise you can elevate a Window or a terminal session instead of an operation...which is exactly how you'd do it elsewhere...)

      Changing the control panel back to basic is in plain view. You go to the control panel, and at the top left you see "Classic View". You click it. Poof. Ok, that was soooo hard (and is exactly how it was in XP. It didn't even change!)

      And Vista is pretty much as fast for games as XP, give or take very early driver issues. Fine, you lose 2 fps (if you have such a fast rig, you ARE using vsync, yes? So you don't lose anything anyhow?). But I'll still give you, it is slower... like 0.5%.

      For older machines, you're right. Not that XP was any different back then though.

      Lets face it: This time, the geeks wanted it to fail, regardless of how it was. If MS had released Windows 7 two years ago, the same misinformation barrage coupled with 2-3 legit issues would have happened... it just would have been like XP in the early 2000s...people would have had to be more creative in blasting it and would have had less actual anecdotal arguments.

  15. Re:win7 performance by MobileTatsu-NJG · · Score: 3, Insightful

    "Win7 performs better than the other 2 OSs" In other words, it only crashes once a month, instead of once a week.

    The article wasn't about Windows 2000 vs. 98 and 95.

    --

    "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

  16. Has nothing to do with linux, OS X, BSD, hurd ... by dbIII · · Score: 2, Insightful

    The general feeling around here is that no-one WANTS to believe it is even possible that Windows 7 doesn't suck. Because if that were true, that would sort of devalue everything done to improve Linux the last few years. (because if Windows 7 is fast and stable and lets you play games, that doesn't leave any room for Linux on the desktop)

    Now that is bullshit. If Microsoft got their act together and made somethign as fantastic as Longhorn was supposed to be it really doesn't have anything to do with linux, and many of us that use a variety of things would rejoice. Gnome, KDE etc might be furthur motivated to add new features and improve old ones at the desktop level. I use linux because I want a cheap unix - a vastly improved Microsoft operating system isn't going to change that, plus it fills so many niches that are completely unprofitable for Microsoft so they will never go there. So many of the improvements are in things that Microsoft just does not care about and why should they - such as embedded devices, NFS, decreasing boot speed etc etc.

    Since Vista even has problems networking with NT4 machines that some people still need for legacy apps I really am not as optimistic as you are. When something from Microsoft is not Microsoft compatable it is a sign that you have a product with problems.

    I'll hold my opinion until they implement things like the poorly integrated DRM that caused so many problems in Vista - if they have to have it (and I think they will decide they do), they should implement it in such a way that it doesn't cause a lot of other problems in the system. To be frank, they are the company that has a long list of very stupid mistakes the latest of which is forgetting leap years exist. I doubt that the 32 bit version of MS Windows 7 will even support Intels Pentium Pro from 1995 and be able to address more than 4GB.

  17. Re:Win7 and PerfTrack by ShooterNeo · · Score: 2, Insightful

    Yes, I read that article.

    Microsoft developers are actually TRYING. Remember, there are a LOT of these people : I know quantity isn't everything, but microsoft has thousands and thousands of these men and women. Also, while standards have gradually slipped as the company grew, they have always tried to hire degreed computer science graduates with the top grades. Meaning, on average, microsoft developers are at least competent.

    Sure, brilliance and freedom and various efficiencies (as well as IBM having a huge team of their own) have let Linux sort of keep up, but the evil empire of Microsoft does have a lot of firepower.

  18. The devil is in the details by westlake · · Score: 3, Funny
    I have 3GB of Ram. Vista is far slower than XP on my machine.

    Explain to me why this rates a +3 "Informative" mod when the poster tells us absolutely nothing more about his system, his applications, or how he uses his machine.

    1. Re:The devil is in the details by Khyber · · Score: 5, Informative

      How about this.

      HP DV9825NR
      1.83 GHz T5550 Intel
      4GB DDR-800
      320GB SATA
      512MB GeForce 8600M GS
      RealTek HD Audio

      I had to hack drivers to get the video card to be seen under XP.

      Used for audio production, I made a quick multi-tracked setup using CoolEdit under both Vista and XP, then tested mixdown/encoding from .WAV to MP3.

      XP beat Vista - 13 seconds in XP vs 28 seconds in Vista, for the same minute and a half of music.

      For gaming, even with my hacked driver to get the video card recognized, playing Fallout 3 in Vista at 1280x720, medium details, gives me an average of 32 FPS. In XP, same detail settings and resolution, I average 40, following the same path, same difficulty. In XP I also lose the stuttering issue in Fallout 3 that Vista users seem to be getting, which seems to be caused by the audio subsystem, as turning audio acceleration to Basic stops about 90% of the crashes, and fixes several noise loop issues.

      So, Vista SUCKS. My laptop is dual-booted with it and XP, and I only use the Vista partition for internet stuff, webcam, skype audio chat, etc. Games and any WORK gets done in XP.

      I want to try 7 on this laptop.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  19. Links Please. by spaceturtle · · Score: 3, Insightful

    full 64bit drivers that can shove data to devices oh like Video cards much faster

    How do 64bit drivers speed up DMA?

    This includes not only the OS's operation, but even 32bit applications running on the OS.

    My understanding is that 32bit application would run slightly slower if the CPU was in 64bit mode. Presumably 15% would be the overall system performance, including legacy 32-bit applications?

    You see when you have a 64bit memory addressing and can optimize for this in the memory manager you no longer have FS and pagefile lookkup tables for extended amounts of RAM.

    What is a FS (filesystem?) lookup table?

    You also can do like Vista x64 does and shove two 32bit memory writes into on 64bit address space, so when it can, you get double the read/write performance out of the memory chip because you are pulling two 32bit chunks in one read cycle.

    By "64 bit address space" I presume you mean 64 bit register (you fit 2^32 32bit address spaces in a 64bit address space). But even in 32bit mode Intel CPUs can access 128bit registers via SSE. Anyway, this presumably has more to do with your compiler than your OS, so I don't know what Vista has to do with this.

    Everything else being equal, 64bit software would run slower than 32 bit, because you need twice as many bits to represent a pointer. Essentially, unless you need an address space larger than 4GB, you are wasting 32bits on every pointer. This would waste memory, cache and memory bandwidth etc. The standard answer as to why 64bit software runs faster on Intel/AMD CPUs is that on these CPUs everything else is *not* equal.

    The biggest bonus to running in 64bit mode on Intel/AMD chips is that since 64bit is essentially a whole new arch, we can throw out all the backward compatibility. In 64bit mode we actually have a decent number of registers. Also since 64bit code won't run on old processors anyway, there is no point in compiling code to be backward compatible with the old i586.

    Understand yet?

    Not really. Not any better than I understand this paper anyway :P. Could you give links explaining your claims above?

  20. About rebuilds by DrYak · · Score: 4, Informative

    Do you still have to rebuild/reinstall modules for Linux for each version of the kernel?

    In addition to the other /.ers' reports :

    - openSUSE : No, you don't.
    if you install the drivers from an RPM (which is one single click on a web-page away, thanks to their 1-click-install feature) everything is taken care of by the package manager.
    if you install the drivers from an ATI/NVIDIA installer or something more esoteric that you compiled your self, the openSUSE kernel upgrade will attempt (successfully in all my occurence) to import automatically the previous .ko into the current modules collection.

    - Debian stable : no you don't.
    Everything including the kernel version, etc. stays the same across version updates, except for patched bugs. The previous modules keep working because the situation is exactly the same as before.

    Atleast you don't have to reinstall every driver in Windows each time you've ran Windows update...

    The fact that their whole OS stays exactly the same and doesn't improve a bit over the course of 5 years may have something to play in this situation.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  21. Just how badly does XP SP3 hurt performance? by Xenographic · · Score: 2, Interesting

    > The test you link to used SP2, while the new tests use SP3. XP SP2 and SP3 aren't the same thing. In fact, most benchmarks put Vista SP1 ahead of XP SP3 or at least within spitting distance of each other.

    I think that's pretty telling, actually, assuming it's the reason. Did Microsoft manage to destroy XP's performance with SP3 enough that it's now below Vista? Did their software department design that "upgrade" or did marketing? (Assuming the two departments haven't been unified this whole time...)

    Or do we have some bad benchmark data here?