Jump to content

D.Draker

Member
 View Profile  See their activity

  • Posts

    3,846

  • Joined

  • Last visited

  • Days Won

    171

  • Donations

    0.00 USD 

  • Country

    France

 Content Type 

Everything posted by D.Draker

  1. D.Draker
    Unfortunately I don't own any rtx 20 series card so it would be impossible to test and see how it performs, even if I decided to mod them. I tried some of the 400 drivers with my Titan 12GB and I didn't like the result . The 400 series drivers are very evil. It's too much junk/crap in them . So like I said , they need at least several areas to be professionally removed/disabled. But looking at the drivers, it seems very possible . I remember many folks wrote it's impossible to go beyond the 372.54 , yet I did it . So I'd say it's possible to go up to 471.xx and then the Vista code was removed.
  2. D.Draker
    Very interesting ! Thanks! So I was able to install it . How ? I don't know! I reboot like a gazillion of times , moved to another USB slots and it somehow started the installation , but there's a new funny thing . It can't accept any updates ! It's always stuck at "stage 3" then says "reverting back" , then just a black screen with the cursor (after it reboots itself).
  3. D.Draker
    @win32 So I finally tested the 32 bit drivers on the same PC where the 64 bit worked perfectly . I get this Error message: "Stop error code 0x0000007e … just like on the jabylake. What I tried , adding the new root certs . All the same . Also tried to replace with another functions.
  4. D.Draker
    Why would I need anyones name ? lol . It's like in that famous Lynch's movie where the dude always says my name's Bob . Anyways , like I already wrote in the comment above. If he knows how to safely remove that portion , he is very welcome to create a proflle here and join the discussion. https://msfn.org/board/topic/183688-breakthrough-new-nvidia-drivers-ported-to-vista-tutorial/?do=findComment&comment=1221422 In the meantime , I suggest to use something like 376.99 or 377.43 or even 377.83 (this one needs a new tutorial though) , they all are very stable. (end of 2017 - early 2018) EDIT: If he wants , I can add what needs to be done with 377.83.
  5. D.Draker
    So found some time today and resulted in this. The same ISO works on Kabylake mobo no probs. https://msfn.org/board/topic/183730-32-bit-vista-installation-possibly-blocked-by-bios-how-to-unlock/
  6. D.Draker
    Hi all , so I've been trying to install windows Vista 32bit to test the modded video drivers and created a bootable (with rufus) USB . USB stick works fine and the ISO is good (original), I tested on a laptop. But on this desktop I got : winload.exe is missing or corrupted . Error code 0xC0000098 Please note , I can install the 64 bit Vista on it from the same USN stick, but NOT 32 . The mobo is pretty basic with a classic BIOS (12 y.o. or so) To recap: I removed all devices (BluRay reader , card reader, another 3 HDD, etc). Attached only a mouse and a USB KB. Resetting CMOS didn't help. Swapping HDD to another new one 160GB (from my storages) didn't help. Tried multiple USB media, all fail to install with the aforementioned errors All just like here and seems unsolved . Could it be locked by the BIOS ? I have the latest version. The PC came with Vista x64. https://social.technet.microsoft.com/Forums/en-US/f8ec6c8b-527b-4b3d-99c3-0e2f70f0956f/windows-7-install-error-winloadexe-0xc0000098-what-next
  7. D.Draker
    Good ! I could be a solid beta-tester since now I have these new modded nVidia drivers with a GPU that still makes sense and a kabylake CPU. Ideally wanted to run x64 Vista using my cool modded drivers with a simple startup fix. As of now, I'm forced to run it on a very old board and it bottlenecks CPU intensive games. I even ditched the famous Dixel's 373.19 'cause these are just so much faster. And the idiotic jabylake system just gathering dust without any use.
  8. D.Draker
    Actually it's should be the first thing to do. And of course there are . Try to replace them.
  9. D.Draker
    By the looks of it shouldn't be that hard to mod.
  10. D.Draker
    I'm happy you survived and finally here with us , your struggle is remarkable ! The best example among of all people who have their strong will to fight !
  11. D.Draker
    Advanced Micro Devices, Inc. - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.3 - AMD Radeon(TM) R4 Graphics Last Modified: 5/18/2015 https://catalog.s.download.windowsupdate.com/c/msdownload/update/driver/drvs/2015/12/20810175_500dd9596bb00f7c148003d934f878e32fc0e3b4.cab
  12. D.Draker
    Graphics Adapter WDDM1.3 - AMD Radeon(TM) R4 Graphics Last Modified: 1/27/2015 Size: 84.7 MB https://catalog.s.download.windowsupdate.com/d/msdownload/update/driver/drvs/2015/06/20711026_c0dacb8c2d5adfe27501b08e34fd6a1dc5927169.cab
  13. D.Draker
    My thoughts exactly ! Since win 7 and all the way to win 11.
  14. D.Draker
    @Tripredacusand all other fellow Americans , Happy 4th of July ! Let your wonderful country stay strong !
  15. D.Draker
    I use the author's MiniBrowser and it's cool.
  16. D.Draker
    Jakob , this whole idea is pretty far-fetched , just so you know. What I mean is your drivers might be too new , all I'm saying. AMD is quite outdated traditionally , so in this case might work for our benefit . That's what I hope for. EDIT : And don't forget to fully de-crapify them . This is a very important step. If the installer starts whining about missing files , just replace 'em with balnks. (emty txt with the same name and extension). So you gotta find what each file really does.
  17. D.Draker
    Thank you !
  18. D.Draker
    Weird , I didn't notice anything bad , even though I posted quite a lot recently.
  19. D.Draker
    Lemme guess , the problems are with firefox ?
  20. D.Draker
    I don't rely on the ex-krenel , all in my tutorial says so . One thing to note, you maybe be in need to update to 03.2019. Why ? Yes , I hate updates , but in this case your drivers are much newer than those I hacked (2018 vs 2020) . So expect the idiotic security theater . Yes , they like to add lots of "security" crap in the drivers' kernel.sys. For example , I had better results with the drivers from 2019 on a system with the updates to 2019 vs the original one.
  21. D.Draker
    So how do you know if can't launch the installer at all ? Did you install the driver manually ? Replace the procedure entry with just ChangeWindowMessageFilter. Without the Ex
  22. D.Draker
    Two times "etc, etc" in the title.
  23. D.Draker
    Fantastic news ! Would it mean the plans to fix the x64 Vista startup issue abandoned for now ?
  24. D.Draker
    You will achieve nothing then . You can read our lengthy discussion with win32 regarding this subject. Code 39 means Windows cannot load the device driver for this hardware . Why ? Take a guess . In the case of modded drivers it's usually because you did not disable driver signature enforcement.
  25. D.Draker
    Microsoft Application Verifier
×
×
  • Create New...