Microsoft Developing Windows for Low-End Machines
Jeff writes "According to the Washington Post, Microsoft is developing a version of Windows to run on old machines that currently run 95 or 98. It would be very similar to XP, but run faster on the older hardware. The move is to appease businesses and universities that don't want to scrap the old hardware. This is likely aimed at preventing Linux from gaining market share where MS is currently alienating their customers."
Nice that at the end of TFA, the exec still told people to buy new computers.
According to the Washington Post, Microsoft is developing a version of Windows to run on old machines that currently run 95 or 98. It would be very similar to XP, but run faster on the older hardware.
Wait, since 95 and 98 barely ran on the old hardware, how is Microsoft going to make XP, a system that normally takes at least 4 times the hardware compared to the old systems, going to run at any workable speed in this scenario? Microsoft really only has two code bases for their systems (the 95/98/ME code base and the 2000/NT/XP/2003 code base), so this new system must be a pared down version of the XP code base, especially since (according to the article) service pack 2 fixes are in place for this future system. So, if they can do this for XP on old hardware, why can't they do it for modern hardware? Is it that Microsoft is simply admitting XP has a load of unnecessary crap in it?
The NSA: The only part of the US government that actually listens.
why not just make a 'faster windows' all around, that runs fast on both old and new hardware? /boggle
Puh-leaze. Yes, this announcement is obviously aimed at preventing adoption of Linux on low-end hardware. The real question is whether or not a product will ever emerge from the vapor. How many times has Longhorn slipped? And what kind of bleeding edge hardware specs does it have? Microsoft can't build an OS with a blank check for hardware specs, so how are they going to do it on a budget?
I am not your blowing wind, I am the lightning.
Lacking <sarcasm> tags,
If you have windows machines, and you are using VNC, then I pitty you. I have used VNC, and I often have VNC installed on machines so that I can remotely control the windows boxes when logged into linux (and because terminal services does not control the root console of a windows server like VNC does), but there is no comparison. VNC is nice solution when you have nothing better. Terminal Services/Remote desktop is a nice solution period. Its fast, easily an order of magnitude faster than even TightVNC.
I regularly use Terminal services to connect to my home server, and then use remote desktop from there to remotely control other machines on my network at home, even the ones connected only by 802.11b. VNC is sometimes acceptable for one connection. It is painful to piggyback.
Don't get me wrong folks, OSS is great, and I would love to see the beast from redmond defeated, but Terminal Services/Remote desktop is a solution done right, give credit where its due.