Jump to content

Jakob99

Member
  • Posts

    354
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Jakob99

  1. Unfortunately, simply changing the version from 6.1 to 6.0 within the .sys file and the .inf was not enough. I'm gonna open up the .sys within Dependency Walker and see what is up. And maybe @win32 has some advice here? Like D.Draker has said, these shouldn't be too hard to mod. It still is very weird that they left a 6.0 section in even though these drivers don't officially support Vista.
  2. I hope not. Thanks for digging these out. I'll take a look at these and see what is up.
  3. @D.Draker I think these two articles would be great reads: https://en.wikipedia.org/wiki/Excavator_(microarchitecture) and https://en.wikipedia.org/wiki/AMD_Accelerated_Processing_Unit#Excavator_architecture_(2016):_Bristol_Ridge_and_Stoney_Ridge Says the Stoney Ridge model debuted in 2015, which is the year AMD cut XP/Vista support. Unfortunately, I cannot seem to find the very first driver AMD released for this model in 2015, but I'll keep looking. If I can find this, it might do better at getting Vista (and possibly even XP) working on the Stoney Ridge platform, which was available until at least 2019, possibly until 2021.
  4. I opened the exe and it threw the error. I did. It threw the same Code39 error. Maybe an older version of the driver (like the first one for Stoney Ridge) will work better. Who knows.
  5. I disabled driver signature enforcement and same code 39 error. Opening the setup.exe produces a "The procedure entry point ChangeWindowMessageFilterEx could not be located in the dynamic link library USER32.dll" error. Not sure if Extended Kernel has that function.
  6. Ah. I'll try that and report back.
  7. Interesting. I will do that. I did try to install by changing 0006 and 0001 to 0006 and 0000 and by adding in the hardware/device ID's to the Vista section, but I got Code 39. I did not disable driver signature enforcement, but I do not think that would make a difference. I'll try Dependency Walker later to see what it picks up.
  8. In atihdw76.sys and amdlog.sys.
  9. I sure did! About to install Vista on the laptop so I can check it.
  10. I found it with CFF Explorer. I changed the references to 0006 and 0001 to 0006 and 0000. Gonna see what this does. If nothing, I'll check with Dependency Walker.
  11. Not yet, but I'll download CFF Explorer and check it out. The card works with Vista, but the drivers do not (despite the 6.0 section). You know how to find the version number (e.g. 6.1) in the driver .sys file via hex editor? I tried finding 01 76 and found it, but it wasn't right and I do not know how 6.1 would be interpreted in hex so any help on this would be greatly appreciated!
  12. Inspired by @D.Draker's success with getting newer Nvidia drivers to work with Windows Vista, I was wondering if it would be possible to get some newer AMD graphics drivers to work, say, the Radeon R4 98E4 Stoney Ridge and related cards that use the same driver. This has a 6.1 and a 6.3 section that is filled in of course, but at the very bottom, it has a blank 6.0 section. Given that is there, it can't be too much work to hack work it onto Vista, right? My AMD laptop that can run Vista is an Acer Aspire A315-21 with Radeon R4 Stoney Ridge 98E4 from 2019. You can find the graphics driver I use for it here: https://www.mediafire.com/file/os5w3p1fb3ali8o/Win7-Radeon-Software-Adrenalin-2020-Edition-20.4.2-May25.zip/file I know there is newer that still has the 6.0 section, but those invert the color in a game I play when the game is in full screen (non-full screen is fine) while these do not. It will be interesting to see if these can be leveraged to work on Vista. If so, it would open up the Vista compatibility door wide-open here. I should note the problems that plague Haswell+ and Ryzen do not happen here and I've recorded no problems from what I could gather in my test. If anyone testing Vista on this or related AMD Radeons like Stoney Ridge notices any problems I may have missed, please do post them here for me and other users. October 17th, 2022: BREAKING NEWS: We may be one step closer to getting newer AMD Radeon graphics drivers such as for Stoney Ridge working with Windows Vista under Extended Kernel. Please stay tuned for more information on this as it comes in. October 18th, 2022: BREAKING NEWS; A huge development has been reported! This just broke the Vista compatibility vault wide-opened! Unfortunately, it will be a bit before this is available to everybody. To learn more, go here: https://imgur.com/gallery/nGsYopn October 22nd, 2022: I'm refocusing this thread to just AMD Ryzen from here on out. I do not have one, so I won't be participating as much, if at all in this iteration of the thread. If you have a modern Ryzen and want to try to get its graphics driver to work with Vista, then be my guest. Keep in mind, Ryzen dos have issues with Vista. These are different from the Haswell+ issues and I believe are related to the USB drivers (feel free to correct if wrong). Here's my new thread linked to below.
  13. Try the steps here please: http://windowsenthusiasts1.epizy.com/Windows2000SandyBridge.html As for IDT Audio, I don't think the Realtek audio driver would work. Someone such as @blackwingcat would need to take a look at the IDT audio files for Windows XP and determine how to backport it to W2k (Maybe @win32 know something too).
  14. Sorry for bumping this, but outlook email addresses (e.g. someone@outlook.com) do not work. I tried to change my account email to an outlook email, but nothing came in, not even to my junk box. I switched back to Gmail and it came in instantly (trying to declutter my Gmail a bit by moving some mails to Outlook). Other activation mails from other forums came in fine. Thanks in advanced for your help!
  15. Oh, so even if I modify its .sys in a hex editor (to change the version from 7600 to 6003), it still wouldn't work? Seems weird AMD left a blank 6.0 section in the INF.
  16. Does anyone know if it is possible to get the AMD Radeon R4 Stoney Ridge to work with Vista? It does have a 6.0 section, so I was wondering if anyone knows of a way.
  17. Dolphin, the GameCube emulator is dropping Windows 7 support. The current beta, released a month ago is the last to feature 7 support. Get it here: https://dl.dolphin-emu.org/builds/51/be/dolphin-master-5.0-16380-x64.7z
  18. I'm grateful for the research into Nvidia drivers, but unfortunately, the newest Nvidia I have is from 2009 and has Vista support I would, however, be happy to test out any mods for Intel Skylake and AMD Radeon R4 Stoney Ridge. I just procured an Acer Spin 5 SP513-51 with it Tuesday. Only thing is I'm not sure if NVMe support was modded to Vista. I also have an 11th Gen Tiger Lake, but for whatever reason Windows 7 doesn't even load despite using an ACPI.sys patch designed for it that strangely allows Windows 8.0 to load. I also have a Celeron N3050, but I'd have to WindowsToGo Vista due to lack of eMMC driver support and all of the makers of the unofficial WindowsToGo feature such as Rufus and Aoemi do not support Vista.
  19. We could have a working fix if we can bakport it from Windows 7 Build 6519. I just procured an Acer Spin 5 with Skylake, so I'd be happy to test if a fix is found.
  20. Any update on getting Windows 7 drivers to work with Vista or are we still a long ways out from that?
  21. Try this: http://windowsenthusiasts1.epizy.com/Windows7UEFI.html
  22. Windows Vista will work, but you'll have many issues (these first started appearing with Haswell) aside from no HD 5500 Graphics support. Your best bet is to get an external PCI-E device for the PCI-E Expansion Slot and hook in an Nvidia or AMD Graphics card (I believe they supported Vista until that year). If this is a laptop, you're screwed as most don't come with a PCI-E Expansion Slot anymore (if they even did). Unless @win32 can get Windows 7 drivers working on Vista as well as solve the Haswell+ problems, you're currently SOL.
  23. If you guys are in need of an Nvidia Graphics driver for your late-2000's to early-2010's Nvidia hardware for Windows 2000, you can find it here: http://windowsenthusiasts1.epizy.com/Downloads.html I've rehosted the graphics drivers to Media Fire in case the links in the "Running Windows 2000 on modern motherboards - USB Issues" thread die out (and the one for 258.96 has while the 257.21 has not, but may. 258.96 I was able to find through Internet Archive thankfully so it allowed me to download it to rehost it). The files are unzipped. If running the exe doesn't work, you'll have to mod the INF to include your Nvidia device. After doing so, it will warn that it did not pass WHQL testing, but you can safely ignore this. If, for some reason, it still does not work, you can Have Disk install this. After installing this, the boot time significantly increases during "Preparing Network Connections". This can be solved by disabling the NVIDIA display driver helper service, located in Control Panel->Administrator Tools->Services->NVIDIA display driver helper. After this is turned off, boot time will return to nearly normal speeds. Thanks to @win32 for this helpful tip (You can also find it in the aforementioned thread). There is also a new README included (alongside the original) that basically rehashes most of this info. I hope this helps someone out. Enjoy!
  24. Unfortunately, these did not appear to work. I am not sure the reason. After I put them into the boot.wim file using DISM and the Forceunsigned command and went to unmount the image, it told me that it could only be partially unmounted. Nothing remained in the mount folder and I was able to move the wim out of the root folder. I rebuilt the ISO and booted it up. Since this Windows 7 ISO uses Windows 8's WinPE, it detected the drives right away (probably a mistake to use a 7 ISO with 8's PE as 7's PE would have told me if the drivers were detected) and I installed, but upon reboot I was greeted with 0x07b BSOD. I then tried to point the Windows Installer to the files, but it told me that no signed drivers could be found. Either the integration got botched (it told me it could only be partially unmounted), or the unsigned nature of the drivers is to blame. I'm gonna go about trying to sign these to see what happens. Another thing is my device may not be in the driver. Gonna load up 8.1, grab that info, put it in, and then sign the drivers.
  25. You would need the Nvme hotfix plus an Nvme driver. Win-raid should have you covered for that. As for USB 3, the ones from Intel most likely won't work anymore, so you would need to find custom-made drivers. If you search Google, you might even be able to find an ISO that is updated to 2020 and has all this built-in. This would save you a whole bunch of time as all you would have to do is burn it to the USB drive using Rufus and install away.
×
×
  • Create New...