ATI FirePro V4800 in Windows 10?

<p>Hi all,<br>

I'm totally frustrated and could use some friendly help. I took the plunge and reluctantly "upgraded" from Windows 7 to Windows 10. The compatibility search utility detected no compatibility issues beforehand.</p>

<p>The driver for my ATI card no longer works. I tried reinstalling, but there seems to be a compatibility issue with Windows 10. I see Win 10 is not cited as a supported OS. When I search the Radeon/ATI site for available drivers, it says there are none. I also tried running the auto-detect driver installer available from Radeon. It correctly identifies the card and OS, but it says there is no driver.</p>

<p>A search for Windows 10 drivers for this card brings up a lot of hits, but they all seem to have web-of-trust profiles suggesting malware and such.</p>

<p>Any thoughts? Do I have to buy a new graphic card to take advantage of this "free upgrade" I didn't want?</p>

<p>Thanks for any leads or insights!<br>

Sarah</p>

<blockquote>

<p>The compatibility search utility detected no compatibility issues beforehand.</p>

</blockquote>

<p>Yes, unfortunately this utility is badly flawed and your pain has been shared by many. I am surprised that the expressed outrage has been as muted as it is. Microsoft, shame on you!</p>

<p>If it has been less than 30 days since your OS "updated" to win-10 you can revert back to the earlier OS (7 or 8). Google it.</p>

<p>I can't be of any help other than to ask if you are on Fb and if so, some of the Windows and PC Gamers groups are awesome for questions like this.</p>

<p>Not on FB...</p>

<p>I knew this would be a PITA when I started it. However, I don't want to be stuck with an OS without update support. It's a lonely and scary place to be.</p>

<p>With a bit more poking around, I found a link on SoftPedia to an AMD FirePro and FireMV Unified Driver. Not totally trusting SoftPedia, because none of these sites are completely trustworthy, I searched the AMD website for "FirePro Unified Driver" and found this link:</p>

<p>http://support.amd.com/en-us/download/workstation/multi-view?os=Windows+7+-+64</p>

<p>The release notes indicate the driver will drive my card under Windows 10. However, it warns, "Note that this driver has general support for Windows 10 for listed Workstations products. The driver is not recommended for full advanced workstation features (see more information in section <em>Workstation Features (Win10). We recommend NOT to upgrade to Win10 if you are using advanced workstation features.</em>)"</p>

<p>So the driver at least brings up my monitors. ColorMunki calibrations are hosed for now. It looks like I have to give up 10 bit color depth, which is not supported. Damn. It was hard to find an affordable monitor/card combo that would support 10 bit. But at least that gives me minimal functionality.</p>

<p>Any suggestions for a replacement graphic card to drive the NEC MultiSync PA241W in 10 bits per color channel (a.k.a. 30 bit)?</p>

<p>Thanks!<br>

Sarah</p>

<p>That's a pretty nice card and I'd actually wait for them to catch up to W10.</p>

<p>It IS a nice card! I guess I can call AMD and ask them when they expect to have a Win10 driver for it. I don't really need the 10 bits for most graphic work.</p>

<p>Factually, rollback depends on which version of Win 10 was installed. Up until a few weeks ago, there was version 1. Since that time, M$ introduced a totally new 'update' that replaces the majority of the original 10 'upgrade' with something quite different. Not so sure that there is a rollback from that if the first version was installed--documentation seems to indicate that there is not.</p>

<p>Welcome to 'software as a service.' Too bad your fine and functional peripherals and internals no longer work--or that the device makers lag or have no intention of writing new drivers. Upgrade to the latest iterations of the hardware. </p>

<p>Say, is that a vacuum nozzle stuck in my wallet?</p>

<p>Sarah, a contributor on Fb suggest to try the most recent unified firepro drivers through Dell or HP. They just added windows 10 support. h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=wk_152047_1&swEnvOid=4158<br /></p>

<blockquote>

<p> <br>

Too bad your fine and functional peripherals and internals no longer work--or that the device makers lag or have no intention of writing new drivers.<br /></p>

</blockquote>

<p><br />I bought a new ssd, installed W7 with my key, then installed W10, then onto my software and then I started plugging in old peripherals, like my Samsung color laser printer. And nothing happened. Usually when you plug a usb device into the back, something happens on the screen. Not this time and I rolled my eyes and cursed Windows. But I jumped the gun and prejudged Windows as lo and behold, the Samsung was just there in the print dialogue box. The same with my Epson printer...it magically just appeared in Ps print dialogue. I'm impressed. So in Windows defence, W10 is the first OS (Mac included) were my old stuff just worked without having to do a single thing. </p>

<p>Sarah, AMD redid their site and made a complete mess, but I think this should be what you're looking for: http://support.amd.com/en-us/download/workstation?os=Windows%2010%20-%2064#catalyst-pro (Win 10 64-bits, I assume you're not running the 32-bits version). These are the FirePro 3D drivers, and in the list of products is your specific model. There is also an ISV-driver, which is (I believe, not 100% sure) the version with garantueed compatibility with applications as SolidWorks, AutoCAD etc. - I don't know if you'd need that one.</p>

<p>As for compatibility woes - these complaints are always there, but for all I've seen (and looking at it is part of my job), Windows 10 did really quite well. Yes, some devices run into issues, and graphics drivers not upgrading smoothly is not unheard of. But little shame on Microsoft to release an update that supports a vast, vast, vast ecosystem of peripherals, mostly without issues (including my printer connected over wifi, which surprised me most). That doesn't mean it's not terribly annoying if you're facing an issue, but a statistical sample of 1 system with some issue among several 10s of millions without isn't exactly a reason to tell others to stay away from Win10.</p>

<p>Thanks so much, everyone!</p>

<p>Sadly, Wouter, the unified driver you link to is exactly the same one I installed -- ver. 15.201.2401, dated Dec 1, 2015. The one you link to, Eric, is an earlier version of the unified driver, dated July 16, 2015. The December 1 version, which I assume is the latest, still offers no 10 bit support. Moreover, I have some sort of installation issue, whereby the driver doesn't keep working. Win10 seems to shut it down, and then I have what appear to be 7 bit (or less) graphics, which look really gunchy. Then when the ColorMunki monitor profiles are applied, everything turns to a lavender and eggshell color scheme (should be light gray and white). I'll give AMD a call sometime in the next few days (really busy with other stuff) to see if they can figure out what is going on. (Maybe an ISV driver is what I need -- talks of 10 bit support.) Xrite (ColorMunki) might be my next call. And heck, I have a cousin who is a big-wig programmer with Microsoft. I might contact him too.</p>

<p>I have to agree with you, Wouter, that the transition to Win10 has been smoother than I expected. (I have yesterday's version of Win10, BTW. And yes, I'm running 64 bit.) My applications all seem to work, more or less, which is rather remarkable. I think there are some registry issues I'll need to track down and hopefully clean up -- maybe a dozen executables that can't be found. What I hate, though, is having to go through this painful process when I have absolutely no complaints nor feel any limitations with Windows 7 Pro. In fact I prefer 7 Pro to 10. (I've been running 10 on a laptop for a while now, so I'm already somewhat familiar with it.) I decided to work on the system yesterday while recovering from a colonoscopy, leading me to ponder which was worse -- the colonoscopy or the Windows 10 upgrade. I honestly can't decide. </p>

<p>Anyway, it's back to work today on a house we're renovating. I have a hardwood floor to lay. I'm not sure how long I'm going to be living with my new lavender and eggshell color scheme!</p>

<p>Well, I do hope the colonoscopy was worse, because it'll go over - windows 10 is supposed to stay a fair while! Get well soon :-)<br>

The ISV drivers are worth trying, probably.</p>

<p>As for preference - I can understand that. Personally, I've never warmed up much to Win7, I liked Win8.1 and Win10 does one thing quite right for me: I don't notice it's there. It just does its job, and let me do mine; I really don't know whether I like it, but I guess that means I do. It all boils down to habits and preferences, and little chance Microsoft, Apple and/or the Linux community / developers will ever get it right for all of us.</p>

<p>I have the same problem with my FirePro V5700. Whatever Win 10 install it works OK but I lose a lot of capapiblities I had with the right driver on Win7.</p>

<p>I'm already well, Wouter. I had a somewhat mopey day at home, but now I'm back to home renovation stuff. ;-)</p>

<p>I do like MS's representation that Win10 is an attempt to have a durable, infinitely upgradeable OS. We'll see how well it makes the transition to future computer architectures. Sad to retire Win7, though, because it has been very stable for me, and I've already paid for it.</p>

<p>Bebu, I feel your pain! I tried uninstalling and reinstalling the drivers. I got rid of the lavender and eggshell color scheme with funky graphics, but now my NEC monitor is completely offline again, and my other two monitors are uncalibrated (and conspicuously different from each other).</p>

If you were happy with it, why not go back to W7?