I remember a thread earlier where everyone posted a screenshot of their Windows Server 2008 workstation desktops, but I haven't seen much for R2 recently. I thought it would be a good thread starter.

As a rule, DO NOT ATTACH your screenshot in the post. Use a photo sharing website such as Photobucket to embed your screenshot image into the forum that way we don't have to scroll from left to right in order to view your desktop! The size below is fine.

Here is mine:

Here's my ""beeast.""

Took a bit to get hud installed the .exe wouldnt work on serverR2
Thanks to every 1 for there hard work to bring us this fine release

...multiple clicky to embiggen...

This is my rather Spartan Server 2008R2 'Game Rig' desktop, that's more about what it isn't then what it is; ergo 'everything I need and nothing I don't' -- an approach applied to my Workstation and Netbook operating system installations as well. I prefer not to have anything in the way distracting me from the content (Taligent R&D inspired theme and colors) or detracting from performance (no 'features' or interface 'fluff').

· boots as fast as most console/appliance (less then three seconds)
· very low commit charge
· record setting software, game, and soft system i/o benchmarks (RegBench et al.)
· hardware benchmarks asymptotic with the ideal
· no event log errors or stability issues, ever

It never ceases to amaze me that while individual system tweaks may only turn marginal performance improvements, sometimes inside the margin of error, or below the threshold of measurement; when combined can turn a performance increase worth a substantial cost in euros/dollars if the same where to be purchased as an equivalent performing hardware upgrade.

My 2x4 Quadcore System, specs in my signature

here is my desktop......
only just installed again,so its a bit sparse
looks great with the moving background

ROB

Dude, I think I love you. I thought i was into girls but damn that machine is just sex.

steady fella!!


if you notice in the first picture.....6 of the cpu in device manager show as unknown.
i just uninstalled each of them and let windows redo them.seems ok now.would that be a problem with the instllation of 2008 r2 or just my computer in general?
i notice nearly everyone favouring the intel route.yes,agreed they are faster,but is that always the need.i have tried to get the best for the money and stability.it does what i want it to do
i had quite a laugh on the phone to HP the other day.....i enquired about the opteron 8439se chips.he said £2370.00 each cpu,but they could do me 4 for £8k if i wanted them tomorrow!!
i made my excuses and headed for e*ay and found 4 for the total of £540 posted.even with the £120 import tax(a-*oles)i still made a massive saving!!
this rig started life as a dual fx-74 'quadfather'......and it has just grown from there!

ROB

Price for performance is one thing. Functionality is another. I could go out and buy a $80k Nissan GTR if I wanted, which posts an impressive 0-100KPH of 2.7 seconds. Of course somebody else with more money than me could go out and buy a Bugatti and do it in 2.4. Is it faster? Yes. Do I care? No.

I'm an Intel man all the way but I'm not prejudice against AMD. I have owned two Athlon boards in the past before buying my Q6600 which has lasted me 5 years now. I'm looking to upgrade to hopefully an Ivy Bridge in the future.

A really REALLY good feature of your processor is that it supports nested page tables for paravirtualization.

What does this mean? Normally with older crapper Intel/AMD processors you cannot pass instructions from the CPU through the hypervisor into the virtual machine. In other words you normally cannot virtualize the hypervisor. On Server 2008 R2 this requires you to run Hyper-V on the physical machine which is a resource drag and slows down the physical machine a butt load. Your processor supports nested page tables which allows you to pass these instructions THROUGH the VM and make the requests on behalf of the VM. Now your hypervisor is virtualized! Essentially what you are doing is running a virtual machine, inside a virtual machine, INSIDE A VIRTUAL MACHINE!!! From a security perspective you are only poking a hole in the virtualized hypervisor which makes it much more secure. The concept is called nested virtualization look it up. Pretty neat stuff. The ability to test a new hypervisor without affecting the physical machine can be very useful. If it crashes the system it only crashes the VM hosting the hypervisor and not the entire machine!

Hi. I sent you a pm Hoak but i dont know if you got it so i will post here. Can you explain what application, skin are you using? i want to have my windows look like yours. Thank you.