Microsoft has updated its Get Ready Web site to include the minimum system requirements to run Windows Vista. A Windows Vista Capable PC must include at least a CPU running at 800MHz, 512 MB of RAM, a DirectX 9 graphics card capable of at least 800x600, a CD-ROM drive and a 20 GB HDD with at least 15 GB free for the install. Of course, systems with bare minimum specifications will be unable to run Vista in the Aero interface.
In order a PC to be certified as “Windows Vista Premium Ready,” it must have at least a 1 GHz CPU, 1 GB of RAM, a DirectX 9 graphics with a WDDM driver, 128 MB of graphics memory, Pixel Shader 2.0, DVD-ROM drive, a sound card, internet access and 40 GB of hard drive capacity with 15 GB free space. For Windows XP, users who did not meet the minimal requirements for XP Home (300 MHz, 128 MB) were still able to install and run the operating system, albeit rather slowly. It remains to be seen if Windows Vista will allow installs on machines lesser than minimal specification.
News source: Daily Tech
Link to: Neowin Disscusion
In order a PC to be certified as “Windows Vista Premium Ready,” it must have at least a 1 GHz CPU, 1 GB of RAM, a DirectX 9 graphics with a WDDM driver, 128 MB of graphics memory, Pixel Shader 2.0, DVD-ROM drive, a sound card, internet access and 40 GB of hard drive capacity with 15 GB free space. For Windows XP, users who did not meet the minimal requirements for XP Home (300 MHz, 128 MB) were still able to install and run the operating system, albeit rather slowly. It remains to be seen if Windows Vista will allow installs on machines lesser than minimal specification.
















So it's so simple as that.
I used to work at a technical college where we had systems with lower specs than that running XP (some of them were the 800mhz machines I referenced in my first post), and we never had issues running CAD programs, SQL server, cartography programs, or any of the other specialized software we had to deal with. I would definitely go over your image and figure out what's chewing up that much memory, because that's NOT normal. I only have 512mb of ram on this rig (XP SP2)...running quite a few visual enhancement programs such as kapusles (which is using a massive 46mb) and objectdock...and I'm still only using 300mb. You may want to check your virtual memory settings as well
A log in shouldn't take 5 mins either...even on a laptop working of a wireless B connection. If you're talking low end P3 laptops then maybe, but not a p4 or pM laptop. I setup a "mobile" lab of 30 laptops loaded down with criminal justice apps (which are a pain to get working right I might ad), and I never had that kind of login lag any of the 1000 or so times I had to log on to each and every one after they'd get back.
I'm just trying to say that what you're seeing isn't normal. You might want to look into what's going on (image, login scripts, DCs, etc.) and see what's causing the login issues as well, because that ain't right.
A log in shouldn't take 5 mins either...even on a laptop working of a wireless B connection. If you're talking low end P3 laptops then maybe, but not a p4 or pM laptop. I setup a "mobile" lab of 30 laptops loaded down with criminal justice apps (which are a pain to get working right I might ad), and I never had that kind of login lag any of the 1000 or so times I had to log on to each and every one after they'd get back.
Actually, in a hefty windows environment (30 workstations or laptops is nothing...) with roaming profiles and domain authentication for everyone, logins in a Windows domain can very easily take 5-10 minutes, depending on what kinds of scripts and such you're forcing the clients to run @ logon.
People like the blame the problem on the workstations though - and in a case like this, the problem isn't with the workstation at all - it's somewhere else along the network, usually at your DC or server holding the profiles. SMB is notoriously slow with XP clients, and doesn't handle scaling well at all - those servers get bogged down with requests easily.
So it's possible - but yeah, blaming XP is completely incorrect. In this case, XP isn't the problem at all.
That being said - I ran XP with all the visual crap turned off on an old P2 laptop and it ran beautifully. It's all in the setup and configuration. I've run Vista on systems well below Microsoft's posted minimum specs with the same results. *shrugs*
I was able to load XP Home w/SP2 on his 10-gig hard drive. To make sure his CPU could run good I added a 64-Mb PCI graphics card and updated to 256Mb of PC2100 RAM.
With AVG and Ad-Aware running and a DVD-ROM drive installed this P2 was able to run rather smoothly and was very much able to run DVD Movies as well.
Yes I was amazed that this Slot I Pentium II w/MMX could run XP Home with no glitches. There still is life for those old PC's sitting on the shelves at Goodwill :o)
As for me, I'll just have to buy a new hard drive as my current one is almost overflowing ;-)
I think they make it up. I am typing this up fram a 3ghz machine with 1 gig of ram, and installed on a 20 gig partition and it runs actually faster then xp does on the same machine on a bigger partition.
Just don't go past 2gb of memory, at least for the x86 version. I ran into a nasty bug loading Vista where it won't recognize USB drives unless you either drop your memory to 2gb or lower, or drop your USB to 1.1. It crops up on nVidia motherboards, btw... not Intel systems.
Im running vista on a pentium M 1.73 ghz, 1gb ddr2 533mhz with only nod32 and windows defender loading and it feels kinda slow
I monitored my pagefile usage for a week and a half, and it barely even gets hit - even under a heavier than normal work load for me.
So those of you who gotten the 32bit version of windows vista... should have picked the 64bit version..
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.