256 colors, SVGA, TCP/IP, HTML 4, and a keyboard and mouse are essentially the only components of what is honestly today’s “standard foundation” for the web.

Yes, of course you can ‘assume’ that your end users have Flash, 1024×768+ resolution, a javascript enabled browser, decent enough display hardware, ram, and cpu to render CSS transitions and other dynamic content, and that their connection speed (as well as the application server’s bandwidth) is sufficient to provide a ‘usable’ experience…

But I think it’s time we got to work on building the next generation ‘virtual platform’ for computing devices- which would be able to output dynamic, high resolution, 3D accelerated page/application content (Like say, Google Earth) – Without developers having to build separate application front-ends for each different device/OS platform…

Hmmm

Dennis, memory IO reservations have nothing to do with Vista’s requirements and everything to do with hardware. These memory reservations are required by devices so that memory mapped IO can undertaken with the device in question. As such, the device is mapped into a region of the 32bit linear address space. Once the device is mapped into that space, nothing else, including physical memory, can be mapped at those same address locations.

So, if you have, say, a video card with a 256MB framebuffer, in order for the system to communicate with that framebuffer efficiently, it is mapped into the systems physical linear address space and subsequently maps out the physical memory that would otherwise be available at that location. Now, if no physical memory is actually present at that location, there is no issue, which is why on sub 4GB 32bit configurations, this wasn’t an issue – there was no collision between devices needing address space and physical memory.

Now, the way 64bit systems work around this is that they have a huge 40-44bit (depending on CPU type) physical address space currently available, so physical memory and memIO reservations need not overlap (though if you actually were to max out the 40-44 bits of physical memory support of a current generation of x64 CPU, you would indeed see that about 768MB of your 1TB of expected memory would be missing).

On 32bit server systems, we are able to enable something called PAE with remap support, which are 32bit physical address extensions, wherein we enable 3-level page translation to a 36bit physical address space. As with 64bit systems, once the physical address space has been expanded, we no longer need have the overlap situation, which is why you don’t see the problem on Server 2003/2008 32bit. Again, we don’t allow address space remap in the client 32bit SKU’s due to a history of problematic device drivers and physical hardware that didn’t always play nice in a remap scenario (e.g. older consumer hardware with firmware or drivers that expected an unmodified 32bit physical address map).

So if Vista needs to reserve 0.75GB for various purposes, how come when I only had 1GB of physical RAM was it not limiting me to 0.25GB usable!

I’d like to hear your thoughts on the MS OOXML specs and why all the loonix folks hate it

As for the first poster, an elevated prompt is sinply one which you launched by right clicking on the Command Prompt icon and selected “Run As Administrator”.

I’m a noob at this

BoOoMSt1cK

**Free PSP*