Absolutely I would be more than happy to share the process of what I do with you.
For M200 series, FirePro and M370X cards the process is somewhat more straightforward than for M300 series users as M300 cards use unique software device settings not found in official AMD drivers.
So anyway for the more straightforward process with the M200 series, FirePro and M370X cards you guys can try this out for your own cards if you enjoy tinkering with AMD's drivers. After downloading the latest driver from the AMD website and opening the .exe file which extracts the required files to Your PC -> AMD, the rest of what you need to do is as follows....
1) We need to make the installer actually be able to run in bootcamp with displaying an error, so we go into Config -> InstallManager.cfg and add the line 'EnableFalcon=true' as a separate line.
Most of the rest of the work now involves editing the .inf found in Packages - > Drivers - >WT6A_INF, normally starting with a 'C' (then an '0' for Windows 10 users e.g. 'C0308528').
2) Open this file up, and now we need to map your graphics card to the code. First, open up device manager then in the dropdown menu expand 'Display Adapters' and open the current AMD graphics adapter by double-clicking. Then in the window that open go to 'Details' and in the drop down menu select 'Hardware IDs'. Copy the first line into clipboard (for M295X it reads 'PCI\VEN_1002&DEV_6938&SUBSYS_013A106B&REV_00'.
3) You will notice the 'DEV_6938' bit which identifies the card by its architecture number. Control-F the number (i.e. 6938) in notepad in the .inf file until you get to the first mapping which should look something like this -> '"%AMD6938.1%" = ati2mtag_Tonga, PCI\VEN_1002&DEV_6938&REV_00'. Replace the 'PCI' and onwards bit with your copied PCI line obtained from device manager. So in the case of the M295X it now looks like this -> '"%AMD6938.1%" = ati2mtag_Tonga, PCI\VEN_1002&DEV_6938&SUBSYS_013A106B&REV_00'. For the M390X it should end up looking something like this -> '"%AMD6821.3%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&SUBSYS_0149106B&REV_83'
4) OK so now we need to remove any code that AMD has added to stop individual cards of a particular brand from installing, including mac graphics cards. To do this, Control-F the first portion of the line on the right after the equals sign e.g. for the M295X it's 'ati2mtag_Tonga' and search until you get to a section called '[ati2mtag_(insertarchitecturehere)]' e.g. '[ati2mtag_Tonga]' or '[ati2mtag_577]' in the case of the Macbook Pro with M370X. At the bottom of this section you will see 'ExcludeID=PCI...' with a list of graphics cards the installer will refuse to install the driver to. You will see it also includes the mac cards. Delete all these 'ExcludeID' lines at the bottom. Now the driver will no longer come up with the 'No supported AMD graphics card detected' error.
5) For Windows 10 users, we need to delete the Anniversary edition section as it causes an unnecessary amount of issues without adding any further compatibility or stability (from my own testing) for the anniversary edition. To do this, Control-F 'Manufacturer' in the .inf file in notepad, which should take you to the '[Manufacturer]' section. You then need to delete 'NTamd64.10.0...14310,' which represents Windows 10 Anniversary edition, leaving all the other ones after it intact which represent Windows 10, Windows 8.1, Windows 7 etc. Then, Control-F '[ATI.Mfg.NTamd64.10.0...14310]' and delete everything from that line onwards (including that initial line) to the end of the file, which you will see is an awful lot of code to delete but it is completely unnecessary even for Anniversary users as the standard W10 code works just fine too for them.
As I've said this process only works for the older cards, and I've noticed for FirePro users sometimes hard resets being reported using this process, but it is certainly stable for M200 series and M370X users. The process is the same across all versions of Windows, except for the removal of Anniversary code (see step 5) for Windows 10 as it is not needed.
For M300 users I strongly recommend you download my drivers instead of trying to get it working yourself @ bootcampdrivers.com
