Jump to content

SigmaTel71

Member
  • Posts

    76
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Russian Federation

Posts posted by SigmaTel71

  1. 5 hours ago, D.Draker said:

    nvgsyncdetours.dl_ (sync with nvidia servers?)

    NVIDIA G-SYNC is a technology for monitors with variable refresh rate that adjusts refresh rate on demand to avoid tearing.

    5 hours ago, D.Draker said:

    And some idiotic plugins that cause low fps.

    Those are framebuffer capturing libraries, I wouldn't touch that personally, as I use application streaming through NVIDIA GameStream sometimes.

    https://steamcommunity.com/groups/homestream/discussions/0/451850849186356998/?l=czech.

  2. So I've managed to install the the June 10 release of Extended kernel, and... everything goes wrong. First, I got kernelol.dll error. Is it supposed to be the old kernel32.dll hanging in System32 and SysWOW64 directories?

    unknown.png

    At least I can confirm that Vivaldi 4.0 installer is starting with some issues, if I set 6.1.7601 version in osver.ini to global section, it starts up correctly, but says that the installer's archive was damaged and the installation will be aborted. Anyway, the extracted one from the installer works fine. I have even reverted the changes made to osver.ini to have correct version showing in the properties.

    unknown.png

    Crash details of Vivaldi update notifier (it crashes twice at launch):

    Сигнатура проблемы:
      Имя события проблемы:    APPCRASH
      Имя приложения:    update_notifier.exe
      Версия приложения:    4.0.2312.36
      Штамп времени приложения:    60dcf375
      Имя модуля с ошибкой:    webservices.dll
      Версия модуля с ошибкой:    6.0.6002.19623
      Штамп времени модуля с ошибкой:    56ec4641
      Код исключения:    c0000135
      Смещение исключения:    00000000000b7e68
      Версия ОС:    6.1.7601.2.2.0.256.1
      Код языка:    1049
      Дополнительные сведения 1:    fa3e
      Дополнительные сведения 2:    ac0507478d1c5bd693cfc4fe3987e900
      Дополнительные сведения 3:    fa3e
      Дополнительные сведения 4:    ac0507478d1c5bd693cfc4fe3987e900

    Discord client installed through DiscordSetup crashes at startup.

    Сигнатура проблемы:
      Имя события проблемы:    BEX
      Имя приложения:    Discord.exe
      Версия приложения:    1.0.9005.0
      Штамп времени приложения:    6255d9bd
      Имя модуля с ошибкой:    StackHash_9c79
      Версия модуля с ошибкой:    0.0.0.0
      Штамп времени модуля с ошибкой:    00000000
      Смещение исключения:    0a56f176
      Код исключения:    c0000005
      Данные исключения:    badc0de1
      Версия ОС:    6.1.7601.2.2.0.256.1
      Код языка:    1049
      Дополнительные сведения 1:    9c79
      Дополнительные сведения 2:    18d391556384f03f39cb1810be4919d6
      Дополнительные сведения 3:    cbd8
      Дополнительные сведения 4:    7823eb2f440e23b0eb8dcc58dcf1c44e

    To what I've noticed is that almost every application had been crashing with BEX until I disabled DEP through bcdedit. Could the renamed kernel32.dll to kernelol.dll be the issue?

  3. 2 minutes ago, D.Draker said:

    There's no need , it's supported out of the box.

    Yes, 342.01 has native support both for Vista and 7, but there is a difference. In Windows 7 I can play modern World of Tanks versions while I can't in Windows Vista. The unmodified drivers package leads to this result. Let me grab my capture card, I'll show what happens in a while.

    6 minutes ago, D.Draker said:

    he may even get somewhat aggressive about that subject

    Almost all Kaspersky users (especially the paid ones) are like that, so, yeah, better to leave it be. :lol:

  4. 1 minute ago, D.Draker said:

    who uses the Kaspersky KGB virus and constantly has crashes and other problems with it

    Oh, I got the point. I got that piece of nuisance at my job on my workspace and it causes performance dips on regular basis. I don't have permission to switch as the machine is in the domain.

    Anyway, back on topic.

    GeForce Game Ready 342.01 driver is not eligible for patching as it doesn't have the required HEX sequence in nvlddmkm.sys, so we can throw away all videocards released before GeForce 400 series.

  5. @D.Draker, have a look to what I understand as a properly formatted instructions. :rolleyes:

     

    Many years passed and it seemed no one's going to port newer Nvidia drivers to Vista, I decided to do it myself. Also, I decided to do some contribution to MSFN and took some time to create this tutorial. As we know, the last officilaly supported driver was from the early May of 2016, while this one is from 2017! Some may say it's a miracle, you betcha! It took me several weeks to try and test everything and it works flawlessly! Had to emphasise a bit (due to some folks not seeing the main detalis).

    Something to know before posting weird questions:

    • these are Quadro drivers and it's not a mistake
    • it's not allowed to share modded copyrighted software, but step-by-step modification instructions
    • I tested it on GeForce 900 series Titan and I don't have information on GTX 10 series
    • extended kernel installation is optional (I have tested on original Vista with updates prior to March 2019)

    Prerequisites:

    How to prepare the driver for patching:

    1. Extract the drivers with Universal Extractor
    2. Go to the folder with extracted files and delete all folders but keep these ones
      • Display.Driver
      • HDAudio
      • NVI2
      • PhysX
    3. Delete these NVIDIA Telemetry libraries located in NVI2 folder:
      • NVTelemetry.dll
      • NVI2SystemService32.sys
      • NVI2SystemService64.sys
      • NVNetworkService.exe
      • NVNetworkServiceAPI.dll
      • presentations.cfg
      • presentations.dll
      • progress.htm
    4. Modify nv_dispwi.inf:
      • Replace NTamd64.6.1 with NTamd64.6.0
      • Replace [NVIDIA_Devices.NTamd64.6.0] with [NVIDIA_Devices.NTamd64.6.1]
    5. Go to Display.Driver folder and extract these files with Universal Extractor to another folder:
      • nvlddmkm.sy_
      • nvd3dum.dl_
      • nvd3dumx.dl_
      • nvwgf2um.dl_
      • nvwgf2umx.dl_

    Now over to patching:

    1. Open nvlddmkm.sys in the HEX editor, go to offset D571F0
      • Find FF84C0740AB8BB0000C0
      • Replace with FFEB24740AB8BB0000C0
    2. Save the file and open it in CFF Explorer
      1. Go to Import, look for kernel32
        • Find KeQueryLogicalProcessorRelationship
        • Replace with KeQueryMaximumProcessorCount
        • Find memcpy_s
        • Replace with memcpy
      2. Go to Rebuilder
        • Remove the checkmark from 'PE Header'
        • Select 'Update Checksum'
        • Click 'Rebuild' and save the file

    For the rest four of the files, do the following in CFF Explorer:

    • Replace K32EnumProcessModules with GetProcAddress
    • Replace K32GetModuleFileNameExA with GetModuleFileNameA
    • Remove the checkmark from 'PE Header'
    • Select 'Update Checksum'
    • Click 'Rebuild' and save the file

    Putting patched files into the installer:

    • Rename all five patched files to:
      • nvlddmkm.sy_
      • nvd3dum.dl_
      • nvd3dumx.dl_
      • nvwgf2um.dl_
      • nvwgf2umx.dl_
    • Copy them (with replace) to Display.Driver

    ———————

    DISCLAIMER
    Some users might not like the use of additional software that might (not) be flagged by their KGB/FSB antivirus. It's impossible to permanently disable driver signature signature enforcement since Windows Vista, so look for Driver Signature Enforcement Overrider v1.3b, and if you are going for it, I'm not responsible for consequences in any way!

    ———————

    Installing the modified driver:

    • Run Command Prompt (cmd.exe) as an Administrator
    • Execute the following commands
    bcdedit.exe /set loadoptions DDISABLE_INTEGRITY_CHECKS
    bcdedit.exe /set TESTSIGNING ON
    bcdedit.exe /set nointegritychecks on
    • Reboot the system
    • Install the driver, but do not restart now.
    • Run Signature Enforcement Overrider
      • Choose 'Sign a system driver' and sign the following three files:
    C:\Windows\System32\Drivers\nvlddmkm.sys
    C:\Windows\SysWOW64\nvd3dum.dll
    C:\Windows\System32\Drivers\nvd3dumx.dll
    • Reboot the system, and you're all ready to play!

    ———————

    Optionally, you may run RemoveWatermarkX64 to remove the 'Test Mode' watermark. Reboot after applying changes.

    ———————

    Special thanks to the advisor @win32, who pointed out the location of the version checks in the previous driver (376.11 on the pic.), which I finally decided not to use since I found a much better and newer driver 376.84 from the year 2017.

    376.png

    If you share this topic, don't forget to tag @D.Draker. Final thoughts: Vista lives!

  6. 7 minutes ago, D.Draker said:

    Unfortunately GTS250 is not supported , it's too old for this driver.

    Would be there any differences if I move Windows 7 counterpart to Windows Vista of 342.01 driver which seems to have both Vista and 7 sections?

     

    unknown.png

    In this case, I can swap it for GT 730 which is still supported through 'security driver', but the closest driver I could find is 378.78, not 378.84.

     

    image.png.157f2c044e79bb2eb78b1237b9fdea1a.png

     

  7. 22 hours ago, D.Draker said:

    I'm sorry man , I'm not into discussing the games in the ex-kernel topic.

    Sorry for that as well, but I wasn't disuccing games in particular but interesting in conditions you made things run. Don't you mind if I switch to PMs to continue on this topic?

  8. On 6/11/2022 at 6:48 AM, win32 said:

    I released a new extended kernel.

    Very nice! Is there a more detailed changelog against the previous release?

    On 6/11/2022 at 6:48 AM, win32 said:

    and some newer compilers/linkers should work too.

    IIRC, executables built with VC2015 linkers and compilers work perfectly, but some of them may not be working due to 'incompatible' PE header (if I got it right). Or have you meant the 2017+ ones?

     

    image.png.86197e1b07f77f0088547c2d5bf7b512.png

  9. 6 minutes ago, win32 said:

    But I haven't added memcpy_s to the publicly available ntoskrnl, because the GPU drivers tested with the ones that had the added functions had issues with DirectX. I wanted to fix that as well, and updating the DirectX kernel and watchdog.sys is required to update DirectX to Windows 7/8 level.

    DirectX 11.1 one?

  10. 3 minutes ago, win32 said:

    This was good enough at the time, but isn't 100% effective like my method.

    I wonder what applications could be manipulated by this method. Will such work on modern browser installers like Google Chrome or Vivaldi?
    ____
    Also, are there any plans on DXGI patches to bring DirectX 11.1 support in future or it's not related to extended kernel?

  11. 2 minutes ago, win32 said:

    With the next release, you will be able to spoof version numbers on-demand, for either a specific application or the entire system.

    Whoa! That's a very nice feature. Were you inspired by BlackWingCat's NNN4NT5 thing while making this possible?

×
×
  • Create New...