The only other real changes are Hybrid CrossFire support for the new HD 5450 graphics card, the option for an integrated gigabit ethernet MAC, and support for port multipliers with FIS-based switching in the new SB850 Southbridge. Most multi-drive eSATA enclosures/docks have built-in port multipliers that require support for FIS switching to allow all the drives inside to be accessible simultaneously through eSATA. Previously this feature was only available on more capable third party/add-on SATA controllers.
2) System configurationMotherboard: GIGABYTE 990XA-UD3, AM3+ socket, dual UEFI BIOS, AMDx chipset, HD AudioCPU: AMD FX-6300 6-coreRAM: 8GBGraphics card: ASUS Radeon HD 5450 1GB (EHA5450 SILENT/DI/1GB)System Disk: Kingston HYPERX FURY 120GB SSD
Multibeast Utility for post-installation configuration of the main installation (for installing specific kexts -drivers- for various hardware devices, like Ethernet adapter or Sound card, and configure the boot loader to use specific kernel switches) Multibeast Maverics
Also create a folder on the root of Installer USB and call it installer where you are going to place all your post-installation files, like Multibeast, kexts (drivers), VoodooHDA, kext wizard, etc
I Used Retail 10.6.8 with iBoot PCIRootUID=1 at start. I have a Radeon HIS 5830 HD. Before I got the video drivers installed for it I was not able to get it working without PCIRootUID=1. Also Sound does not work from motherboard.
(be careful not to install other drivers, otherwise the official one won't work. When the official one is installed, there may be problems if you try to change the WINS or DHCP ID: the Wireless Utility will quit right after started, and this can be solved only by reinstalling the OS afaik. The problem survives reboot and driver reinstallation.)
Leveraging the I/O protocols on a single transport enables engineers to innovate new system design configurations, allowing for standalone performance expansion technologies that use existing native device drivers. Thunderbolt technology also enables the introduction of thinner and lighter laptops without sacrificing I/O performance, and extends to reach other I/O technologies by using PCIe-based adapters, making gigabit Ethernet, FireWire*, or eSATA easy to create.
I think you should just test all of these drivers, one by one (starting from the newest ones), to check which one works If something goes wrong you can just boot into VGA mode and uninstall the faulty driver.
From the feedback I'm seeing, the likely answer is 'no' and my procedure was OK, and this anomaly was seen only because I incorrectly thought the alpha driver was the only choice for my card and Windows 2000. I suppose that's why it's called 'alpha' ...
The reason for the questions ... I thought I'd like to get 'all my ducks in a row' before going ahead, now for the third time, in the hope it will finally go to a satisfactory conclusion. Each time, I'm updating the partition's image, then completely cleaning out the old driver, including remaining Registry entries, then switching cards, etc. Then, when it fails, putting the image back so I can start from zero, again, on the next try. I don't want to 'mess up' the operating system installation, as can happen so easily with MS Windows, even though trying to keep it clean is a bit of a bother.
Let me know if you see anything wrong with what I have written above, and also let me know if you have any comments about the empty 'Models' box causing the driver installation to 'hang' (see the quoted post, just before this one).
By the way, blackwingcat, have you tried these drivers with PAE turned on I can't get any of them (ver. 9/10/11) to work if I turn PAE on. The system is Win2k Advanced Server. With PAE switched off they work fine (ver 9/10, ver 11.x is unstable). I've got integrated Radeon 3000 HD.
Your directions on how to populate the 'Models' box should let the installation run normally. I was suspicious that my home-made 'work-around' may have given me a defective driver installation. No worry about that, now.
Thanks for your patience! The last time I worked with the ATi drivers was some years ago when I installed Windows 2000, and by now I have completely forgotten what I did, and I know you have all these details fresh in your mind. So then, to summarize the only two questions that remained after reading your directions and then looking at the files:
Thanks, blackwingcat, for your good work! I am writing this update from Windows 2000 Professional, using the ASUS EAH5450 SILENT. The periodic driver crashes (in both Windows 2000 and Windows 7) that were plaguing the old Sapphire Radeon ATi X300 are gone now, in both operating systems. And, yes, I had recapped the old board, with little or no improvement.
I tried ati1011w2k (edited) and got two missing file errors during installation, went ahead anyway, and wound up with a driver that crashed immediately during boot. On the second time, I found the first missing file in a folder one level down, and the other in a folder in the ati11-07w2k subdirectory (from the other version). I was able to direct the installer to these files so it accepted them (these were ati2mtag.sy_ and ativvamv.dl_) and then completed without error.
For others who are using blackwingcat's drivers without success (I saw a few posts in that category) it may not be the driver but a defective installation. It took a few tries until I figured out how to do it successfully.
Put the card in the slot and boot. Windows will make the card (marginally) functional with the default VGA driver. Open the Device Manager and you will see two entries with yellow exclamation points, or perhaps question marks. One will be for the video card, the other for the high-definition audio function on the card.
Go into the Properties of one of these and click the option to Change the driver. After a few self-obvious steps, will be taken to a wizard that allows you to browse to blackwingcat's files. If you are working with the video driver, you'll want to select the CX*.inf file, and install. Now one of the error indicators in the Device Manager will have disappeared. In this case, the one that remains will be for the HD Audio. Follow the same procedure, but this time select the ATi*.inf file, and install. Now both yellow error indicators in the Device Manager should be gone.
Edit: The original board used for the above installation developed an intermittent, and was replaced with a more recent EAH5450. Upon verifying its specs (for both the CPU code name, and device ID) showed it had a Cedar, in place of an Evergreen, GPU. To avoid any problems, the following line was inserted into CX102499.inf:
I apologize to blackwingcat for contributing to pulling the thread he started, so far off topic. My problem has had so many posts, and has been resolved, so I hope anyone needing help with the BWC drivers would be starting a new thread, anyway ...
Whatever the future holds, the Mac Pro Cheesegraters are long-in-tooth, and the viability of using one as a daily driver is fading but with right upgrades has still life left. This guide is an ode to the best computer ever made, the classic Mac Pro an engineering marvel marking the high-water mark of performance, ease-of-use and user-serviceability.
EFI - Short for Extensible Firmware Interface, a specification designed by Intel to replace BIOS as the method to interface between an operating system and the platform firmware. This former isn't essential to understand beyond that it is a computer's firmware. Apple adopted EFI on Intel Macs, and this is the interface that allows selecting a boot drive before OS X begins booting (by holding down the option), among other pre-OS loading functionality. I use the term EFI slightly loosely as I'll refer to the boot screen as the EFI even though it isn't all that EFI provides for the Mac. It is also important to understand that the UEFI (Universal Extensible Firmware Interface), which is now industry standard for PCs, isn't the same as Apple's EFI on computers from 2013 before. They are similar, but Apple's implementation varies partly due to age (predating UEFI by a few years) and partly due to the closed nature of Mac OS. Apple has since begun adopting (at least portions of it) UEFI, so the implications are better for the 2019 Mac Pro and GPUs. In order for a GPU to display a pre-boot screen, need Universal Graphics Adapter Protocol (UGA) support on the GPU for the Mac Pro 1,1/5,1s. The more modern UEFI replaced UGA with Graphics Output Protocol (GOP), which is not used on the classic Mac Pros. Most aftermarket cards only support GOP and not UGA. This means without using OpenCore. Aftermarket GPU upgrades will not output video before the drivers are loaded. The lack of UEFI also has implications for other OSes like Windows, where MBR (Master Boot Record) needs to be used instead of UEFI if you are not using OpenCore.
Kext - With OS X, the architecture for drivers uses kernel extensions, called .kext files. Kexts are supremely powerful and the backbone for the Hackintosh community to enable unsupported hardware. However, Apple has deprecated kexts in 10.15 Catalina for security reasons, replacing them with EndpointSecurity and SystemExtensions, and DriverKit. How this affects unsupported hardware remains to be seen. Kexts are located within /System/Library/Extension and /Library/Extensions.
Metal - Previously, Apple's default graphics library for graphics acceleration was OpenGL (Open Graphics Library), used on iOS and Mac OS. Over time, OpenGL fell behind in performance and features when compared to a library like Microsoft's DirectX. Without an ideal candidate to replace it (OpenGL's successor, Vulkan, would not be released until 2016), Apple created it's own graphics library called Metal and shipped it in 2014 on iOS 8 first. Later, Apple ported Metal to OSX. Mac OS 10.14 Mojave uses Metal to now power Mac OS. The new API does not support many o