AMD Readies Windows 7-Friendly Chipset:
By Andy Patrizio
AMD will begin shipping its newest chipset, the 785G, to OEM partners today. The 785G is the foundation chipset for AMD’s Windows 7 offerings, and is tuned to take advantage of some of the features in Microsoft’s forthcoming operating system.
This is AMD’s first integrated graphics processor (IGP) to support DirectX 10.1 (the latest version of Microsoft’s multimedia library), and is the first IGP with 10.1 support. nVidia has a 10.1 IGP in the form of its GeForce GTS 250M.
Intel, which has an overwhelming chunk of the IGP market, has yet to release a DirectX 10 IGP chipset. DirectX 10 was released in 2007 with Windows Vista.
“We look at the update of this chipset as not a huge evolutionary change in chipsets. We added in a couple of new features but primarily added in the graphics core and added in a couple of new features we wanted for Windows 7,” Brent Barry, desktop brand manager for AMD told InternetNews.com.
There is a newer version of the library called DirectX 11 that comes with Windows 7. Support for DirectX 11 will come via discrete graphics processors on add-in boards from both ATI and nVidia. There’s no great rush, however, as it will be some time before DirectX 11 games and other applications hit the market.
High performance graphics support & energy efficiency
Between the DirectX 10.1, HDMI 1.3, Stream and UVD 2 support, the IGP has a pretty good amount of high performance graphics support, allowing for faster video transcoding, high definition decoding, Blu-ray playback, all while reducing the power draw. It’s also the first AMD IGP to support DisplayPort.
The 785G uses a Radeon HD 4200 core, making it one whole generation above the last IGP set, the 790G. Combined with the new 45nm Athlon II and Phenom II processors, AMD is seeing power reductions by as much as 50 percent in certain applications, Barry said.
“There are more energy efficiency features native in Windows 7. The main thing is throttling and switching on and off the GPU when it’s not being used. Windows 7 is just a better operating system than Vista. It’s doing power management better, along with better memory management and thread management,” he said.
The chipset meets the spec for system builders seeking Energy Star 5.0 compliance, he added.
Microsoft is pleased to announce the release of System Center Operations Manager 2007 R2.
Extending monitoring support from Windows platforms to UNIX and Linux servers and workloads, detailed reporting on service levels, enhanced monitoring capabilities for systems and web applications, and more, the trial for Operations Manager 2007 R2 is now available.
I saw this error before in establishing many failover clusters , In the validation phase of the cluster nodes everything went fine except the IP configurations part.
I made sure that all network drivers are static and the binding is right. But the error keep appearing every time I validate the cluster.
I found that one of my network drivers has APIPA IP although I haven’t
I run ‘ipconfig /all’ from the command prompt. You might have noticed a few extra interfaces, but not really understand what they are. I suspected that those NICs are the problem so open the server manager to see what I get. I saw that there is many drivers under Network adaptors
There I found driver called Teredo tunneling pseudo-interface
Teredo is an IPv6 transition technology that provides address assignment and host-to-host automatic tunneling for unicast IPv6 traffic when IPv6/IPv4 hosts are located behind one or multiple IPv4 network address translators (NATs). To traverse IPv4 NATs, IPv6 packets are sent as IPv4-based User Datagram Protocol (UDP) messages. For more information check Microsoft network part here
Teredo is enabled by default in Windows Server 2008.
To pass the validation wizard just disable Teredo tunneling pseudo-interface on the cluster nodes
Some times when you try to log in to the domain from some computers you get that error “An unexpected network error occurred). Group Policy processing aborted. Even ID: 1054″
It’s a known issue with servers with AMD processors .
Go into the boot.ini file in the root system directory, add the following parameter:
Now Boot.ini should look like that
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”Windows Server 2003, Standard” /noexecute=optout /fastdetect /usepmtimer
Then restart your computer.