Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


greenhillmaniac

Member
  • Content Count

    397
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by greenhillmaniac

  1. Could you give me some links to those MB driver websites?
  2. 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.
  3. 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: - Apps don't completely replace the Win32 counterpart, making their existence useless and irritating (for me atleast). Example: Groove Music plays MP3 files, Windows Media Player plays everything Groove does plus midis and other weird formats. Why should I have Groove occupying space, when Media Player serves me better, and with no crashes? - Apps crash at random without any kind of warning. Win32 programs crash and then give you a log, or a message of sorts. - You are not given the option to uninstall OneDrive and remove it from the Explorer, even if you're using a local account - App defaults are usually changed to the ones Windows wants. I use SumatraPDF as my PDF reader, but Windows 10 thinks it's a malicious app, so it kindly restored the default to Edge... How nice of them! I'm not even including the privacy or other control downgrades, or I would be here all day. Case in point: Windows 8.1 is the best OS Microsoft has done (with tweaks)
  4. 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 8.0 have over 8.1. I'm interested in hearing them.
  5. 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.
  6. 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 the system when I tried to run the test. Like I said, this is a super unstable way to get the drivers working. Also, AMD External Events kept crashing at startup, don't know why. I applied all the fixes @smeezekitty made, so I dunno.
  7. 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
  8. 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.
  9. 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, but it gave error 10. - AMD iCafe modded - same as 14.4 modded. Error 39. I'm sorry to say this, but the modded files don't work . I copied the system files into System32 and System32\drivers as instructed.
  10. 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?
  11. Sure, I'd be ecstatic to! Send the drivers, please!!!
  12. 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, because the INF file only specifies NT 6.1 (although that does not mean you will be restricted to WDDM 1.1. More on that later), but the HDMI INF file has to be modded, because it has lines in there that block the install on anything that's not NT 6.1. Assuming you are already on the folder with the extracted drivers, go to Packages\Drivers\WDM\HDMI\W764A and open the INF file. In there delete the line that says: [AMD.NTamd64.6.2] and modify the line that has all the hardware IDs below it: [AMD.NTamd64.6.1] > [AMD.NTamd64.6.2] Save the INF file. 3. Now the drivers are ready for install. If you're running a 64 bit system you will need to follow the following steps: 3a. Go to the Charms bar, go to the cogwheel symbol and click on the power button, now keep pressing the Shift key and click Restart. This will bring up the Troubleshoot menu. Click Troubleshoot and go to Advanced Options. In there click Startup Settings, and let the system restart. Upon restart you will be greeted by a menu with a bunch of options. We want the Disable Driver signature enforcement. Press 7 or F7 on your keyboard, and you'll be able to install the modded drivers. 4. Right click on the exe on the main driver directory, click compatibility and choose Windows 7. This will fool the installer and prevent it from saying "Unsuported OS". Next install the driver as you normally would. The only difference is this little popup, where you will allow it to install (Yes, I was using Windows 10 for some screenshots) 5. After the install is done, reboot the system, and you should have the full suite of AMD drivers working on your NT 6.2 OS of choice. A few things to note: - If you try to uninstall the drivers normally, it will say "Unsuported OS" and quit. One workaround is keeping that window open, go to Task Manager, find the location of the exe and put it in compatibility mode for "Windows 7", and run the uninstaller again (the same thing we did for the setup file, basically) - The Video Tab of Crimson does not appear to be working... It appears as a blank page. I've seen it working, so I'm not sure if it appears after a few restarts, or if it depends on the way you install the drivers. I'll try to look into this. - Despite the drivers having NT 6.1 on the Card INF file, it fully works on WDDM 1.2 and not Windows 7's WDDM 1.1, which means all the advantages of NT 6.2's WDDM are present. Hope this helps anybody on Windows 8.0 with an AMD card, such as myself
  13. 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 Center will not be available for Windows 8.0, since the only NT 6.2 supported OSes, Server 2012 and 8 Embedded Standard, don't have this feature. Regardless, these updates only fix vulnerabilities when oppening .mcl files, so as long as you don't open those kind of files, you shouldn't worry too much Here's the new link: https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ BONUS: I'll also be starting a new thread, on how to install AMD drivers for Windows 8.0 (it's surprisingly easy, but still requires a few steps). EDIT: The AMD thread: http://www.msfn.org/board/topic/175966-amd-drivers-for-windows-80/
  14. 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.
  15. Where are the links? Also, any ETA for AMD drivers?
  16. 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.
  17. 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...
  18. 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 this kind of thing. I can't promise much help, but I can give a test system (since my card needs the latest drivers, I think it could be a perfect test subject ). Also, did some more research, and here are the driver versions AMD has developed up to this day, which might be useful, if you intend to do your research (in chronological order): - 14.50x - AMD Catalyst 14.12 up until Catalyst 15.6 beta. Based on the Catalyst Omega release, these drivers don't support the RX 300 series, but are the last known ones to support Vista. - 15.20 - only found these on the Gigabyte website, which leads me to believe these are an early version of the Catalyst 15.7? They are dated from April 2015, according to the files inside the exe, so they seem older than the AMD released 15.15, which are dated June 2015... (link: http://download.gigabyte.eu/FileList/Driver/vga_driver_amd_w7_w8_15.4.exe) - 15.15 - just found out about these on the AMD website. These are the first official drivers to support the RX 300 series, but seem to be newer than the 15.20 that I found on the Gigabyte website (which is weird, going by the build number). Haven't tested these on Vista, but I'm assuming they won't work, like all 15.xx drivers and later (link: http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-300-Series.aspx) - 15.20 - the first 15.xx drivers supporting all other cards from AMD's lineup, and made for Windows 10. Starts with Catalyst 15.7 up to Catalyst 15.11.1 beta - 15.30 - introduced with the Crimson UI overhaul of the drivers. Starts with Crimson 15.12 all the way to Crimson 16.2.1 beta - 16.101 - discovered by the good folks at Guru3D forums. The only drivers on the 16.xx line to support the non-GCN GPUs (link: http://forums.guru3d.com/showthread.php?t=408883) - 16.15 - Vulkan support and a few new AMD features. The first official 16.xx release. Starts on Crimson 16.3 and ends on Crimson 16.5.1 Hotfix - 16.20 - honestly, I don't know what these drivers brought to the table... Begins on Crimson 16.5.2 Hotfix and ended on Crimson 16.7.2 Hotfix - 16.30 - recently released with the Crimson 16.7.3, made for Windows 10 RS1. Still haven't tested these. Apparently this driver version reduces DX11 driver overhead, according to the Guru3D forum guys (great forum for AMD drivers BTW) I think this is everything. If you find anything new, tell me. This info should provide some ground work to get started. EDIT 1 - Corrected some info and added the missing driver entries, up until the most recent EDIT 2 - Added info on the 16.101 drivers.
  19. 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).
  20. 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.
  21. 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.
  22. 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_w8_15.4.exe). I do believe these are prior to the big driver revision of 15.7 (all of the drivers until 15.6 are revisions of the Omega drivers 14.12. I know this because in the INF file they all say version 14.50x). With Catalyst 15.7, the driver version bumped to 15.30. Starting with versions 15.20 and 15.30, a simple INF mod would not suffice to make the drivers work with Vista. As such, I started to dig around the .sys and .dll files of recent drivers with Dependency Walker on my Vista laptop, to see what kind of dependencies were introduced. I started by first comparing the 14.12 .sys files, with the drivers provided on Microsoft Update Catalog, dated 19-04-2016, version 16.150, and here's the difference (since it's too many images, I've compressed all the results to my Mega account): https://mega.nz/#F!ApB1hQZL!dsRHCNz9HPSyJUOYI2AZZA Basically, atimdag.sys introduced two dependencies on NTOSKRNL.EXE that Vista doesn't have, namely sprintf_s and RtlDowncaseUnicodeChar. All the other .sys files have the same group of missing dependencies, which I'm not sure matter, since, like I said, 14.12 installs just fine on Vista. In terms of .dlls, both versions seem to have the same kind of missing dependencies, that is, missing IESHIMS.DLL and a missing function in MFPLAT.DLL, MFCreateMFByteStreamOnStream (there are A LOT of dlls on AMD's drivers, so I only looked at the main ones, like amd_opencl64.dll, amdh264enc64.dll,...). Now I'm kind of stumped. I don't know where to go from here. What do I need to do? Mod the drivers? Mod the system files? How do I add calls to DLLs? I feel like there might not be too much work involved in making these drivers work on Vista, because certain basic parts of it work. What do I mean by this? Well, when trying to install the drivers through Device Manager and getting Error Code 31, if I go to change the display resolution, my monitor's resolutions appears, where it otherwise only listed 600x480, which means basic display detection might be working. So, can anyone help me/guide me to making the Rx 300 (and perhaps Rx 400) series work on Vista? Summoning @blackwingcat and others
  23. 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?
  24. Surely GURU. I need to stabilize some kernel modification otherwise it may cause too much bsods I have not added skylake hd graphics as it also has same issue. 15th/16th of this month i will provide few hundreds of mordern hardware driver You're doing God's work
×
×
  • Create New...