Jump to content

Brickedandroid

Member
  • Posts

    173
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Indonesia

Posts posted by Brickedandroid

  1. Wow, there may be some missing functions. Please repeat the analysis and re-send the screenshot but with selecting the dependency .sys file(s) marked with red box, sort the "PI" column, and scroll to the top or bottom, and you should see the red "C" box signs which represent the needed functions that aren't exist yet in NTOSKRNL8.sys or in other dependency files. Or please send those .sys files to me, and I will analyze them myself.

  2. On 6/30/2023 at 10:00 AM, Novek said:

    yes

     

    Capture3.JPG

    Capture.JPG

    Capture4.JPG

    Capture2.JPG

    Capture5.JPG

    Please download the dependency walker x64 here: https://www.dependencywalker.com/depends22_x64.zip

    Then put the .sys driver file in the same folder with ntoskrn8.sys, drop the .sys driver file to the Dependency Walker window, and send the screenshot to me.

    For the optional header, replace all the 000A's to 0006. Those are the major versions.

    Have you copied the ntoskrn8.sys to C:\Windows\System32\drivers\ folder? If don't, please copy the file and then restart the computer, and don't forget to press F8 and disable the driver signature enforcement.

  3. 7 hours ago, Novek said:

    I tried using that but it told me that the inf file wasn't compatible so I edited the file but I got a Code 39 and the only things that work are sound and my microphone

    Have you modified the .sys driver file using CFF Explorer, by modifying the minor versions in the optional header section and renaming ntoskrnl.exe to ntoskrn8.sys in the import directory? Also, don't forget to re-calculate the checksum after modifying.

    Or there might be some new missing functions that weren't added yet to the ntoskrn8.sys itself. Try checking that modified driver in the same folder with the ntoskrn8.sys using Dependency Walker x64.

  4. Use NTOSKRNL Emu_Extender.

    Newer Intel HD Graphics drivers (along with UHD and Iris) will only work partially in Windows Vista. You will not notice any problem from the Device Manager, but the driver breaks anything Direct3D 9 or earlier with problem signature BEX/BEX64. However, you still can use apps or games that use Direct3D 10, 11, Vulkan, and OpenGL API perfectly.

    You will also need to press F8 and Disable Driver Signature Enforcement every boot.

    For temporary solution (only to eliminate BEX crashes), just rename igdumdim64.dll in System32 and igdumdim32.dll in SysWOW64. But you will cannot:

    • Play games or use graphical designing/editing programs released in 2008 or earlier (unless using DirectX 10 or OpenGL API)
    • Play videos using Windows Media Player (if you want to play videos, look for the 3rd party media players like VLC, MPC-HC, KMPlayer, GOM Player, or Real Player)
    • Use Windows Aero theme
    • Use screensavers
    • 3D benchmarks (unless you can set or select the 3D rendering API manually)

    Or just use the discrete GPU (Nvidia/Radeon) for Direct3D 9 if your laptop also has it.

    The Intel Graphics Control Panel cannot be opened yet until you renamed those files. And you also can't adjust the resolution and refresh rate from the Intel Graphics control panel, so that you must adjust the resolution and refresh rate from the Windows Display settings.

  5. On 6/9/2023 at 3:11 PM, Waine Ammon. said:

    Windows Vista Extended Kernel Download For Windows Vista Business 32 Bit.

    I Would Like To Run Windows Vista In 2023 Again.

    Can You Help Me Please.

    Many Thanks

    Waine Ammon.

     

    Just download the 64-bit's Vista Extended Kernel build, but copy the wow64 files to System32 folder if you use the 32-bit Vista. I recommend the latest stable one (October 2022 build). And make sure you also have prepared some backups of the original files.

    March 2023 builds messed out the 32-bit things.

  6. 2 hours ago, winvispixp said:

    i would recommend going down to the october 2022 release as the newer ones break a lot of stuff, including wmp, experience index, cause general instability (java update scheduler always crashes when restarting or shutting down along side with some old asus monitoring program and audio driver)
    so if you don't need whatever newer versions can get you (someone wrote about discord and premier pro a while back) i suggest sticking with 10192022 release

    And March 2023 also breaks the 32-bit shell file dialogs and drag and drops

  7. 23 hours ago, mina7601 said:

    And how does that help answer winvispixp's question? He is asking how's the development of the extended kernel is going (like for example, would there be any new applications running in, new functions added in the next version, etc.), not what is the latest version of the extended kernel. Besides, this is wrong, the latest version of the extended kernel is March 9, 2023.

    March 9 is indeed latest but not stable. Instead, you may look for the March 6 build, which is the stable one.

  8. Yay! Finally I'm able again to run D3D9 games and programs in Windows Vista Extended Kernel using the newer version of the Intel HD Graphics 4000 driver!
    So, I used WineD3D to do this. I copied the WineD3D d3d8.dll, d3d9.dll, and wined3d.dll files to System32, replacing the original ones. I also renamed the igdumdim64.dll and igdumdim32.dll files in System32 and SysWOW64.
    WineD3D works by emulating Direct3D 8 and 9 into OpenGL. However, it is not perfect and there are still some crashes.

    What it can do:

    • Open the Intel HD Graphics control panel
    • Play video files using Windows Media Player
    • Play Chess Titans by running the chess.exe file located in the C:\Program Files\Microsoft Games\Chess folder
    • Use screen savers (except Ribbons, crashes with code 0xc00000fd)
    • Play D3D9 casual games
    • and other light 3D rendering activities that are done by the D3D9 API

    What it cannot do:

    • Use the Windows Aero theme
    • Run DxDiag
    • Perform D3D9 benchmarks
    • Open Games from the Start menu (this might be a bug)
    • Play D3D9 demanding games
    • and other heavy 3D rendering activities that are done by the D3D9 API

    Other bugs:

    • The video playback sometimes slowing down and not syncing with the audio in Windows Media Player if the video resolution is higher than 480p or if the Windows Media Player is maximized
    • Windows Explorer crashes upon closing the Windows Photo Viewer
    • Some fullscreen games don't revert the screen resolution when exiting fullscreen mode, going to desktop by pressing Windows logo key, or switching between windows. They only revert the screen resolution after quitting the game

    DXVK's D3D9 also most likely will work in Windows Vista Extended Kernel, even much better than WineD3D. However, DXVK only works on graphic cards with Vulkan API, and Intel HD Graphics 4000 doesn't support Vulkan.

    Proof:

    file.php?id=427&mode=view

    file.php?id=428&mode=view

     

    GTA San Andreas also works successfully on WineD3D. But if the Visual FX Quality is too high, the game will become very slow and unplayable, especially when in Red County. And the intro's FMV only plays the audio but still can be skipped. Unlike when using the native D3D9 which the game keep runs smoothly even with highest graphics quality on the same hardware and also can play the intro's FMV videos perfectly. Hope the DXVK's D3D9 will improve the performance so much and become faster and better graphics quality than the native D3D9.

    file.php?id=430&mode=view

    file.php?id=429&mode=view

     

  9. 6 hours ago, LostEntrepreneur439 said:

    Firefox 111 and later doesn't seem to be working for me. I'm currently using 110 without issue, if I try to use 111 or later, pretty much the second I double click on it I get the "Firefox has stopped working" message. I'm using the March 9 2023 build of the extended kernel on Windows Vista Ultimate SP2. Here's the details of the crash if they're relevant.

     

    Problem signature:
      Problem Event Name:    BEX64
      Application Name:    firefox.exe
      Application Version:    113.0.2.8542
      Application Timestamp:    646b8716
      Fault Module Name:    kernel32.dll
      Fault Module Version:    10.0.6004.4006
      Fault Module Timestamp:    64098adc
      Exception Offset:    0000000000000000
      Exception Code:    c0000005
      Exception Data:    0000000000000008
      OS Version:    6.1.7601.2.2.0.256.1
      Locale ID:    4105
      Additional Information 1:    10ba
      Additional Information 2:    44d65c4eeb6aca884fdc9b206a3a9706
      Additional Information 3:    5fb0
      Additional Information 4:    683c4139ddb44a06c8924dbeb362d749

     

    Have you installed the 2019 Quality Rollup (KB4493471) update? The main build number must be 6003 instead of 6002.

  10. 2 hours ago, Saswat2005 said:

    I followed @win32's instructions, then it works. Thanks @win32. But I can't update to March 2023 build as it is laggy sometimes. I will keep it on 2022 version.

    March 2023 has 2 builds. Please use the stable March 6 build instead of the buggy March 9 build.

    2 hours ago, Saswat2005 said:

    Hello, everyone. This is Saswat, a user here. If I use Windows Vista Extended Kernel, trying to have Google Chrome 104, trying to install from Google does not work at all. So I had a virtual machine on my previous laptop ( which has Windows 7 on it ) running Windows Vista, so I go to Program Files then move to Google, copy the folder called Google to Downloads folder and then make a zip file. Then I dragged the zip file to guest OS Windows Vista, and then it worked, by spoofing Windows 7 version, it gradually works. Even for Microsoft Edge too. So you know that thing.

    You can try spoofing to Windows 10 first before installing.

  11. On 4/29/2023 at 6:40 AM, sunryze said:

    i have quite a strange issue where after installing the latest extended kernel in a vmware VM, the mouse no longer works.

    HID-compliant mouse and PS/2 compatible mouse both say that windows was unable to load drivers for the device (code 37)

    Try the March 6 build. It's more stable than the March 9 build.

  12. Anyone knows which are the system files (DLLs or EXEs) that are used to render the fonts and unicode-related things from Windows 8.1? Because those might have some functions inside that also render the Segoe UI Emoji font colored, and I want to apply that on Windows 7 or earlier operating systems. But if I just install the Segoe UI Emoji ttf file obtained from Windows 10 or 11, the emojis are only colored inside Firefox, but are black and white outside Firefox!

  13. 7 hours ago, Sergiaws said:

    Tried that, nothing strange happened! Moreover, in my case Office 2003 which is only 32 bits can save documents and open documents without issues.

    Do you installed the March 2023 build?

    (Microsoft Office uses its own independent API, and please note that NOT ALL 32-bit programs have such issue.)

  14. On 4/16/2023 at 9:16 AM, Saswat Tech Center said:

    How did this happen?!

    Try running any 32-bit programs. For example, you can run Notepad from the SysWOW64 folder, and then try opening the file (Ctrl-O or File -> Open...), or write some characters and try saving to a file. Those will not work at all since the open/save dialog won't show anymore after March 2023 build.

  15. The March 2023 build breaks some 32-bit (x86) programs, especially the shell commands such as the load or save file dialogs, and shows "Failed to create empty document" error message when I drag a file to the 32-bit program's window.

    spacer.png

  16. 5 hours ago, Jakob99 said:

    Interesting. I don't think I have quite the expertise to do this, but I know someone who may. Would this also apply to post-Ivy Bridge Intel graphics drivers such as for Haswell and later?

    For now, I've tried it, but it's the newer version of Intel HD Graphics 4000 driver on my Ivy Bridge. It works partially, doesn't have any problems at all in Device Manager, but it breaks Direct3D 9 with BEX crash signature. But don't worry, Direct3D 10, 11, and OpenGL are unaffected and still worked perfectly just like normal. You only can't enjoy aero and playing videos using WMP, but you still can play games that use Direct3D 11 or higher (usually released beyond 2011).

×
×
  • Create New...