Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Windows Operating Systems Software Government The Courts News

The "Vista-Capable" Debacle Spreads To Acer 133

N!NJA writes in with a Register story on a lawsuit filed against Acer for selling Windows Vista on an underpowered notebook. Of course anybody can sue for anything; it will be interesting to see if this action goes forward in the courts. "With a lawsuit filed Wednesday in San Francisco, California, two residents of Fostoria, Ohio seek damages and relief from the world's third-largest computer maker after purchasing a sub-$600 Aspire notebook that included Windows Vista Premium and a gigabyte of shared system and graphics memory. In its official "recommended system requirements," Microsoft recommends that an additional 128MB is required to run the Premium incarnation of its latest desktop operating system. ... Microsoft says that the Premium, Business, and Ultimate editions of Vista will run on 512MB systems — with certain OS features disabled. In the beginning, Redmond called these 'Vista Capable' machines, and it's facing a separate lawsuit over this potentially misleading moniker."
This discussion has been archived. No new comments can be posted.

The "Vista-Capable" Debacle Spreads To Acer

Comments Filter:
  • 512Meg? (Score:3, Informative)

    by jawtheshark ( 198669 ) * <{moc.krahsehtwaj} {ta} {todhsals}> on Saturday March 28, 2009 @02:36PM (#27371675) Homepage Journal

    Probably even with shared graphics memory, resulting in something like 448Meg usable? Windows XP SP0 and SP1 ran on 256Meg RAM, SP2 seems to need 512Meg RAM, SP3 seems to need a bit more (but I never tried taht one on low-memory machines). Vista on such a machine? Eeeuh.... I don't think so.

    That said, they seem to have paid quite a lot of money to get a RAM upgrade.

    Linux runs fine tough on such "low-memory" (I had harddisks smaller than that, like 20Meg!) machines.

  • Re:512Meg? (Score:5, Informative)

    by the_humeister ( 922869 ) on Saturday March 28, 2009 @02:45PM (#27371785)

    Linux runs fine tough on such "low-memory" (I had harddisks smaller than that, like 20Meg!) machines.

    It's a little disingenuous to say that "Linux" (aside from the fact that Linux is just a kernel and that the term "Linux" is now being used in the mainstream for almost any Unix-like OS; but that's another argument altogether) will run in low memory. While this is true, most people wouldn't use it like that. My WRT54g with 16 MB of RAM is running OpenWRT. I had a 386 that only had 12 MB of RAM and I had X running with twm, and it ran only slightly faster than Windows 95, which had a much better looking UI.

    So yes, you can run "Linux" on a low memory computer, but you're sure as hell not going to be running KDE or GNOME or some other good-looking interface with it.

  • Re:512Meg? (Score:4, Informative)

    by jawtheshark ( 198669 ) * <{moc.krahsehtwaj} {ta} {todhsals}> on Saturday March 28, 2009 @02:53PM (#27371881) Homepage Journal

    Yes, indeed... You are of course right. However, I implied (that wasn't perhaps clear) that a 512Meg machine runs a Full Linux-Based Desktop like Gnome just fine. On my Asus EEE PC 701 4G, I rarely exceed 300Meg used.

    But your points are well taken....

  • capable? sure. (Score:2, Informative)

    by Anonymous Coward on Saturday March 28, 2009 @02:54PM (#27371903)

    It works fine with 512... Its just incredibly slow!

  • by hechacker1 ( 1358761 ) on Saturday March 28, 2009 @03:35PM (#27372237) Homepage
    Aero offloads the GUI onto your graphics card if it is capable of DirectX 9. It provides a faster, tear free interface, and if you notice DWM.exe (Desktop Window Manager) uses only 0-1% of CPU during use.
    If you disable Aero and fall back to GDI, DWM.exe will disappear, and explorer.exe instead takes the load, usually using 1-5% of my CPU (at least on this machine).
    In general, you should get better performance if you have a decent video card. If you are using the desktop anyways, why not utilize the GPU?
    A couple of considerations:
    1. Vista uses more GPU ram with each window. If you have a shared memory GPU, it's conceivable that it would be too slow when you start opening many windows. Or if your GPU just doesn't have a lot of RAM.
    2. Maybe your GPU isn't as power efficient as using the CPU for rendering the windows. Battery life could be affected.
    3. Windows 7 with driver model 1.1 uses a constant amount of GPU ram for any amount of windows (steaming in textures instead of keeping them loaded). It also re-enables GDI 2D HW acceleration which was disabled in Vista, but available in XP. Windows 7 also accelerates Cleartype text.
  • Re:512Meg? (Score:2, Informative)

    by Anonymous Coward on Saturday March 28, 2009 @03:40PM (#27372279)

    Im running Kubuntu on my home built atom 330 box. It has two gigs, but right now it's only using 0.47 gigs according to the system monitor.

    And this is with KDE4, Kaffine playing a video, KTorrent pulling down ...distros...(cough) and of course firefox with a couple of slashdot tabs open.

    I think it's fair to say that a modern linux desktop is perfectly usable with only half a gig.

  • Re:512Meg? (Score:3, Informative)

    by Hognoxious ( 631665 ) on Saturday March 28, 2009 @05:01PM (#27372903) Homepage Journal

    In Soviet Russia, anybody is enough for 640k! So regarding your request, no.

  • by Anonymous Coward on Saturday March 28, 2009 @08:56PM (#27374781)

    Posting AC as I'm moderating.

    There's "use" and there's "use", and I'm not sure which one you meant. If you're normally a Linux user and used to the way it uses swap, or if you're a tech that's just not familiar with the swap strategy Windows uses, it can get confusing, but see the next paragraph. However, if you mean the machine isn't seeing all the RAM and therefore not using it at all, that's different. One cause of that may be a 32-bit machine with more than 3 gigs RAM, due to the PCI device address space normally found at the top of the 4-gig 32-bit address space. Less RAM than that, perhaps it's as others have mentioned elsewhere, that it's a shared memory machine and the graphics are using part of it.

    But as I mentioned, Windows has a much different swap strategy than Linux, but also one that confused me years ago before I ever switched to Linux, as it makes a sort of sense but isn't intuitive. On Windows, as long as swap is enabled, the OS will use it, preemptively preswapping, trying to keep a lot of stuff both in memory and in swap if it can, so if the memory taken by an app is needed by something else, the VMM can simply dump the physical memory copy since it's already in swap, instead of having to spend extra time swapping it out just when the user is waiting for whatever needs the memory to load. This means it's using swap long before it actually has to, to keep the extra copy there just in case. In fact, if swap is enabled, Windows at least /used/ (9x versions, whether it still does I haven't the foggiest) to break if it couldn't do this. I discovered this the hard way at one point when I installed a new CDROM that took the drive letter I /had/ been using for dedicated swap. Fortunately I knew enough about how the 9x versions worked that I was able to boot to DOS mode and mcedit the hidden msdos.sys or whatever file (it has been awhile, I'm no longer sure what file it was) and point the swap at a different device.

    The effect of this is somewhat unintuitive. On Windows (again, 9x, but I believe it still applies today), if swap is enabled at all, it must effectively be the size of the physical memory at LEAST, before you get any "extra" virtual memory at all. If you have a swap LESS than the size of your physical memory, Windows may not be able to use the full physical memory at all. Either swap must be made bigger, preferrably double RAM or larger, or on big memory machines that don't really need swap anyway, it should be disabled entirely.

    Linux (and presumably most OSs) work more intuitively and rather differently, but theoretically, maybe a bit slower when people are loading something new into physical meory. Swap is always additive. If you have a 2 gig physical memory and a half gig swap Linux machine, it'll let you use 2.5 gig, NOT the half-gig you might be stuck with on Windows. Also, it doesn't so aggressively pre-swap, tho adjusting the swappiness setting [1] can change that. Swappiness defaults to 60. Higher numbers cause it to favor swapping apps out to keep cache, lower numbers encourage it to favor keeping apps and flushing cache, once available memory is full of cache and apps.

    I'm running kernel/md RAID, here, 4-spindle, RAID-6 for my main system so two-way striped (with two-way parity), with a swap partition set on each of the four spindles as well, with all four set to the same priority, so swap effectively runs RAID-0. Thus, the 4-way swap is actually faster than (re)loading stuff off the effectively 2-way striped RAID-6 (the other two being parity stripes), so I set swappiness high, 100, thus encouraging the kernel to swap out apps and keep cache data, because swapping in the apps out of the 4-way data striped swap will be faster than rereading the cached data off the two-way data striped RAID-6 main system. That of course is rather the opposite behavior most users, on a no-RAID single-spindle disk, will likely want. They may prefer to set swappiness much lower, say 20, or even 0.

    ---
    [1] Swapp

  • Re:512Meg? (Score:3, Informative)

    by ion.simon.c ( 1183967 ) on Sunday March 29, 2009 @02:33AM (#27376971)

    ...will need the same or higher computer specs to run a configuration that gets close to what the Windows experience offers...

    Check out the SVN trunk version of KDE 4 some day. [0]
    When you combine that with an ATI card, the open source drivers, and OpenRC, you get a desktop experience that (IMO) blows the doors off of anything coming out of Redmond.
    With this configuration, I have a Linux machine that goes from GRUB bootloader to a usable [1] desktop in ~45 seconds. (Time spent typing username/password not included. Time spent starting X is included.) Server 2K3 on the same hardware (with nothing else happening on startup) takes nearly a minute and a half. [2]
    My Linux desktop gives me an OpenGL accelerated desktop. [3] (Hello translucent windows, zoomable desktop, and live preview of window contents on ALT-Tab [or the Expose knockoff]). I get a faster USB stack... faster USB mass storage device recognition, mount, and unmount times... transparent access to network (and other exotic) resources... [4] the Lancelot launcher... fine-grained control over users and applications with PolicyKit and grsecurity... network-transparent audio. The list goes on and on.

    It sounds like you haven't tried out a Linux distro in a while. You might wanna grab a couple of six-packs, and spend some afternoons over the next month checking out what's available these days.

    [0] SVN KDE 4 won't eat your data, but you might not wanna install the dev packages required to build it. So, you could also check out KDE 4.2 (or 4.3 when it is released.) What I've said here about KDE SVN also holds for KDE 4.2 and later.
    [1] By usable, I mean the time that ipv6.google.com comes up in Firefox and I can type a query into the search box. And no. I'm not restoring any previously saved FFox sessions.
    [2] Guess what? My Linux installation also brings up Postgres, mysql, apache, an svn server, the BOINC client, and the usual host of remote access daemons on startup. The Server 2k3 install does none of that... it doesn't even start IIS.
    [3] Do I get shader support? No. IIRC, we're waiting on the Gallium3D project to mature.
    [4] There's nothing quite like being able to mounting a network resource (or ISO image, or...) inside a directory in your filesystem and being able to use it just as if it were local data. No fussing with UNC path handling. No bitching from CMD.EXE about being unable to handle UNC working directories. Nothing like that. :)

Thus spake the master programmer: "Time for you to leave." -- Geoffrey James, "The Tao of Programming"

Working...