Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

greenhillmaniac

Member
  • Content Count

    449
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    $0.00 

Everything posted by greenhillmaniac

  1. Those drivers are dated December 2014... Unfortunatly, my card came out in June 2015, so I would need newer drivers. Thanks for the links, tho!
  2. Could you give me some links to those MB driver websites?
  3. Didn't know about the network traffic monitor on the Charms bar, and I used Windows 8.0 from release, up until the 8.1 upgrade Anyway, those are some tangible points. Thanks for posting. Also, just remembered of a few more plus points for Windows 8.0: - You can use the Release Preview theme as is, without mods - You can use the Windows 7 Explorer with a wrapper, eliminating the Metro portion of the OS entirely Keep em coming... I'm trying to use this thread to have some arguments, when I say that Windows 8.0 is a viable alternative to 8.1 and 7.
  4. While we're talking, here are some personal gripes I have with the latest Windows 10 AU (and Windows 10 in general): - When you don't have the default apps installed, new entries on the start menu freeze, and the only way to unfreeze them is to log off or restart Explorer - Im my OS language (Portuguese of Portugal) the Downloads folder is named "Transferências", as it was since Vista, but Edge changes the name of the folder to the English default "Downloads", messing up with the visual organization I have on Explorer (8.1, 8.0, 7 and Vista NEVER did this) - This: - Ap
  5. Is there any reason to choose Windows 8.0 in favor of 8.1, in terms of kernel, performance, tools and/or user experience? AFAIK Windows 8.1 introduced quite a few improvements to the Modern Start Screen and the /resetbase switch in Dism to better cleanup WinSxS. One point I found better in 8.0 is resource usage, where it had less processes running out of the box compared to 8.1... Other than that, I can't tell if any other things that are better. I've read that DWM performance is better??? Please, the members that know this kind of thing better, elaborate on what advantages does
  6. Like I said, I am your guinea pig. If you ever need to test those changes, I'm usually available. I still believe you should start by making the drivers work on Vista, seeing that it's much closer to 7, and wouldn't require too much reverse engineering, compared to XP.
  7. Yup, there is a way to make the Rx 300 series work on Vista! But it's super unstable, and shouldn't be used for a day to day basis. Here's how I did it: Got the Catalyst 15.6 beta drivers, added my HW ID to the INF file and moddified it to install on Vista, and voila! A few things to note: for some reason transitions, fades to black, UAC calls and screen resolution changes are super slow... Probably because the driver was meant to work on a R9 285 and is running on a R9 380... This means the R9 Fury series probably don't work with this mod. The Windows Experience Index Score crashed
  8. Well... you could try the most recent stable ones, the 16.7.3... You could check out my post on AMD driver versions, and start from there, too: http://www.msfn.org/board/topic/175825-about-amd-drivers-on-vista/?do=findComment&comment=1127335
  9. There are 2 ways to mod the drivers to make them work on XP. You can mod the OS to stub/support certain system calls the new Windows 7 drivers need, and work around XP's limitations, or mod the XP drivers themselves to support more graphics cards. The mod @Dibya provided does the later. As such it only works with the XP made drivers. Windows 7 and XP are way too different, unfortunately. And, as I've said, it did not work on my system. I tried different driver combinations, with no luck. Try asking @Dibya for the mod and see if it works on your system.
  10. Ok, just tested 2 AMD XP drivers, both original unmodded versions and with your file. Here are the results: - AMD Catalyst 14.4 unmodded - added all the necessary info of the R9 380 into the INF file, does not work. - AMD Catalyst 14.4 modded - added all the necessary info of the R9 380 into the INF file... The driver seemed to install correctly, and asked for a reboot, but after reboot it couldn't load drivers, error 39. - AMD iCafe unmodded - added all the necessary info of the R9 380 into the INF file... The driver seemed to install correctly, and the screen flashed black, bu
  11. Let me first test the driver on my PC (my guinea pig ) and then I'll add the necessary HW IDs. Could you tell me your card's name and HW ID BTW?
  12. Sure, I'd be ecstatic to! Send the drivers, please!!!
  13. Starting with Catalyst 14.4, AMD officially dropped Windows 8.0 support, and nobody really cared to make a proper guide on how to mod the drivers to work on NT 6.2. Well, I'm here to show you how you can install the full AMD package, complete with the Crimson Control Panel, HDMI audio, Vulkan, Mantle, ACP Audio (that thing AMD advertised way back when they announced GCN, TrueAudio)... you get the jist. 1. Download the drivers you need from the AMD website, Windows 7 version. Extract the exe files into a folder (I use 7-Zip) 2. The video drivers will install without any modification,
  14. Ok, just got back home, time to update the repository. This is an overhaul to the repository, as it no longer contains superseeded updates, has Internet Explorer 10, Flash Player and Kernel Mode Driver updates on the root directory, since those are updated every month and replace the previous versions, and (most importantly) X86 UPDATES FOR YOUR COMPUTING NEEDS! These come from Windows 8 Embedded Standard and work on Windows 8.0 (tested on my 12 inch laptop with a measly Intel Celeron Dual Core at 1.2 Ghz, from 2009). One thing to keep note of is that security updates for Media Cente
  15. Well, DirectX 11 also adds a bunch of effects that DirectX 9 can't render, like tesselation, that can take away a large chunk of performance... If you want to do an apples to apples comparision I would suggest comparing Windows 10 DirectX 9 vs Windows XP DirectX 9. Only then can you say that Windows 10 is slower.
  16. Where are the links? Also, any ETA for AMD drivers?
  17. I guess now Vista is the only sane Windows version left... Let's pray that the Redmond bafoons don't exclude Windows 8.0 from the monthly rollups. BTW, I just tested this on my laptop, and apparently Windows 8 Embedded Standard updates also work on Windows 8.0, which means x86 PCs can also have a fully updated client NT 6.2 OS. I would update the repository, but I'm currently on vacation, so only next Tuesday will I be available.
  18. Patch Tuesday has arrived!!! Brace your PC's, updates are coming... This is the first month in the year where the looming threat of Windows 10 isn't upon us. Not that it matters for Windows 8.0 anyway https://technet.microsoft.com/en-us/library/security/ms16-aug.aspx Awaiting reports...
  19. Don't forget that XP and Vista are two almost entirely different beasts. What might be crashing a lot on XP and require a lot of reverse engineering of system and driver files, will probably be a lot easier on Vista (given it's basically Windows 7, but a lot prettier and lighter ). NT 6.0 and NT 6.1 are a lot closer than NT 5.1 and NT 6.1. Who can blame ya! Vista is suffering a worse fate than XP, with drivers being made only for XP and 7+, and programs that abandon both XP and Vista, without even considering the latter. Unfortunatly I am even more illiterate when it comes to t
  20. There are dozens of us! We might not be many, but what we lack in numbers we make up for in passion. Does @smeezekitty go online often? I still think that atimdag.sys is the main file preventing the installation of the basic drivers (even if stubbing the missing fuctions is possible, other driver functionality might still be semi-incompatible, and require aditional dll files, like power management, or hardware encoding).
  21. Actually, the patch @smeezekitty did for the 14.12 drivers worked for all releases until the 15.6 drivers (the last ones to belong to the 14.500 branch). He did an extra patch for the 15.3 drivers, I think, but that's it. If you'd like to know, the Rx 300 series (released June last year) do not work on Windows Vista, because the only drivers working with the cards are from the 15.20 branch or newer, which introduced some extra dependencies that the OS doesn't have. No INF modding works this time. Some extra work is needed. That's why I oppened this thread.
  22. Nope, he just installs thems, reboots and hopes for the best But Server 2012 and Windows 8.0 are practically the same, and @JodyT has been installing updates successfully since February 2016, so we can make a good assumption they will keep working moving forward.
  23. I've decided to start a little investigation on recent AMD drivers and Windows Vista (mainly the ones that work with the Rx 300 series and newer), because those drivers won't install, giving error 31 when trying to do it on Device Manager (even with the appropiate INF modding), and I love Vista too much, to let my GPU be the only reason I can't have it installed . The earliest drivers I found, supporting the Rx 300 series, were located on the Gigabyte website, dated from April 2015, version 15.20 (link, in case you're curious: http://download.gigabyte.eu/FileList/Driver/vga_driver_amd_w7_
  24. Just updated the repository with this month's updates. Here's to 6 and a half more years BTW, a little bit off topic, but I was digging around about Windows Vista and Server 2008, and it turns out Server 2008 got Powershell v3.0, but Vista never got it! You'd think that both OSs being the same would make installing the update easy, but it blocks itself on Vista! (I've tried.) Windows 8.0 and Server 2012 might have the same thing with Powershell v5.0 (it says it's only compatible with Server.) Is there any way to remove the OS restriction on these kind of updates?
×
×
  • Create New...