AFAIK, the build code for the server2008r2 core of Home Server is "Vail", not "Phoenix".
Vail is the software on top of it. The core has different codenames.
The AMD processor driver is built into NT6 systems (Vista/Win7/Server2k8) so you should be covered out of the box. If not, a quick trip to Windows Update should solve this whole issue.
Indeed it is there and has been automatically installed during setup, however it displays the message posted in the first post as well as that broken device that was identified as a button or fan or ....
So let me get this straight, you're running a phantom "alpha" version of an OS on an old server whose company went out of business?
yup
If you can't get support from M$ who gave you this alpha-OS (you're authorized to run it right?)
Yup, i'm a beta tester and a Microsoft Student Partner. It's like 'this is the build, try to see whether you can get it to run on your server'. Anything non-MS driver related is not supported by MS. It's about their beta OS, not the drivers (and related blue screen) from a third party. So I am pretty much on a road to find drivers/patches for hardware that is pretty much impossible to identify because the companies behind do longer exist. Currently I got 29/31 hardware related problems solved.
or the company who made the hardware, then I guess you're out of luck because our magic wand doesn't stretch that far.
It was worth a try At least the driver packs got my mass controller to work. It doesn't do hot swapping yet but at least the drives get identified and Device Manager is a happy with it.