[Bink]

If you have to ask, and if this is your workstation, use Vista.

[Bink]

Yes. I can do this without issue.

[Bink]

I had the same issue—and we’re not alone. Six pages of complaints may be found at http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/4e1c53f5-0400-4ca9-8819-f942c10881c1/#page:1. Ultimately, it appears to be related to compatibility issues with Hyper-V and video drivers—with the best solution being not to use Hyper-V 😥 .

[Bink]

Just to clarify what I said, enabling Physical Address Extensions (PAE) allows Windows to see the RAM beyond 4GB, and expose it to applications, but the only applications that will be able to use that extra RAM are those that are specifically written to leverage PAE, like Microsoft SQL Server—so most x86 applications will not be able to see that extra RAM. However, if you have or 4 or more GB of RAM, you will still benefit from PAE on x86, but x64 removes all the tricks required for PAE and gives your OS a lot more headroom. With the planned Windows 2008 R2 being x64-only, and no simple upgrade path from x86 to x64, unless you have reasons against setting up a new x64 server today, I’d consider x64 the standard.

[Bink]

I used a method similar to Arris’ and can confirm this works on x64. I also installed the Bluetooth stack and have this working in conjunction with my phone and Nokia PC Suite—and this works better on 2008 than it did on Vista, so go figure.

[Bink]

While x86 can see the 8GB of RAM, it and most applications will not be able to use most of it. As a result, you must install x64 to use all 8GB.

[Bink]

Thank you Arris! “powercfg -h on” did the trick!

[Bink]

Well, I found where the Client for NFS was hiding—it’s in the File Services role as Services for Network File System. With this addressed, anyone now know where the hibernate feature is hiding? Thanks.

[Author]

Posts