Jump to content

burd

Member
  • Posts

    811
  • Joined

  • Last visited

  • Days Won

    5
  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by burd

  1. 2 minutes ago, win32 said:

    Your Vista is UEFI? That changes everything. osloader.exe is a modified version of winload.exe which is intended only for MBR/BIOS systems, though you will be able to use the same ntkrnlmp as everyone else.

    So I checked out winload.efi and it's indeed very similar to the MBR version. So hopefully the patched osloader.efi works.

    So for UEFI users, just follow this instruction as opposed to the similar one for BIOS users:

    bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.efi

    Yea it is,do i need to rename osloader.exe to efi aswell? how does it work

  2. 52 minutes ago, win32 said:

    ntkrnlmp.exe is available again, as I have managed to make it work.

    1853645239_VistaNT6.1.png.10eb9eee1c8efa6d7b59ffe1d8e0d591.png

    What's different about it?

    -New section added at end of file

    -Export table moved to this section

    -Version number changed to 6.1.6002.19741

    What was breaking it in the first place? Rebuilding its PE Header. The same thing happens on XP x64. Just update the checksum and you'll be fine.

    Once again, I wonder how the version change will affect newer drivers.

    For brevity, here are the installation instructions:

    I will start patching it accordingly, and hope to bring ntdll in the fold soon. Both ntdll and kernel32 may also be bumped to version 6.1, as it appears that some Qt 5.10+ binaries like to not load after a version check.

    is there some missing step? My screen is just blank and doesnt load to the os

  3. On 8/21/2020 at 10:59 AM, asdf2345 said:

    The Oct 2nd, 2019 Steam build is pretty recent, so most games still work, but some games, like Rust, which require the Steam API v20 don't work with it. There are some file modifications that are required to get it working. It still works with the browser from the XP client, but mouse scroll is broken, and it doesn't work too well with the modern Steam site. This client also is the last client to come with version 72 of CEF, which can be used if you rename the Windows 7 x64 CEF folder to cef.winxp in Steam\bins\cef, then add -no-cef-sandbox to the Steam shortcut target. It does have some issues though, but they could possibly be fixed if it were possible to make Steam treat Vista x64 exactly like Windows 7 x64. If you know how to do this, let me know. One final issue with the client is that you can't sign out of friends, so you'll always appear as online.

     

    Tried this but i get a steamui.dll error everytime

  4. 2 hours ago, asdf2345 said:

     

    There is a DirectX 11 port to XP, but I haven't been able to get it to work for many games, because of a missing function in one of the dlls. Only time it has worked, for me, is with a DirectX 11 backport to Unreal Engine 1.

    For now, just focus on Vista, XP hasn't been that fast on my systems. I've gotten terrible performance with it, even on my 3770K and my 4720HQ laptop

    u mean DX10 right? DX11 for XP doesn't exist afaik.

    Edit : Upon searching i did find dx11 for XP though, weird.

  5. 1 minute ago, win32 said:

    I think bootmgr needs to be modified as well in order for it to work.

    But I've had a few other things happen in my life lately (for example, right now, most sounds, sound warped to me) so I haven't been able to do as much as I've wanted to do so. And then I'm still trying to work out ntdll and LoadLibraryExW.

    Hope you feel better soon , the other things can wait :)

  6. On 8/28/2020 at 11:57 PM, win32 said:

    File temporarily pulled due to quality control issues.

     

      Reveal hidden contents

     

    I have just uploaded two new files: osloader.exe (winload.exe) and ntkrnlmp.exe (ntoskrnl.exe).

    Two modifications have been made:

    -Code integrity checks have been disabled

    -Version number of ntkrnlmp.exe is 6.1.6002

    To use these files, copy them to your system32 folder (x64 only, of course!). Then enter CMD and do these commands:

    bcdedit /copy {current} /d "Windows Vista Unlocked"

    Keep note of the value you get in this form: {91274567-89ab-cdef-00ff-nca000ffffff}. Replace yours with whatever value you get.

    bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} nointegritychecks 1

    bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.exe

    bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} kernel ntkrnlmp.exe

    Installation media with these files replacing the existing MS ones may be capable of loading unsigned drivers, like USB 3.x drivers.

    The version change to 6.1 was done because I found out that some drivers react negatively to the "wrong" OS version number. For example, some NVIDIA XP drivers fail to load on pre-reset Longhorn builds because they're NT 6.0, AMD drivers seem to arbitrarily reject Windows 8 and new NVIDIA drivers do the same for early Windows 10 releases. I'd like to hear results from Ryzen and NVIDIA Pascal series GPU users.

     

     

    when will you re-release it , still awaiting it :)

  7. 3 hours ago, asdf2345 said:

    I have an idea about getting the 372.70 drivers fully working on Vista.

    I recently discovered a subreddit, r/XtremeG, and it's all about driver modding. The idea is someone makes a request for them to fix the issues with 372.70 with Vista, and other users from this forum upvote, or even comment on the post to make it seem like a popular idea.

    I think it would be a good idea to use these images in the post too

     

    well feel free to try but i doubt 10-20 people would push them to even try to do any modding

  8. 32 minutes ago, Windows 2000 said:

    In my honest opinion, I think that you should prioritize x64 work rather than x86, as x86 is first of all, harder to get stuff working on and secondly, less people use it by a long shot.

    but its needed for 32bit apps to run even on 64bit systems 

  9. Just now, asdf2345 said:

    I've gotten newer clients working without a browser, so only small mode works. Also, I only get the superior old chat UI.

    the newer clients work anyways in small mode like win32 and i have already investigated , but in broken form with big picture mode or small mode the only way to use it at the bare minimum. The main task is getting everything to work , you will need a working steamhelper aswell to get it to work.

×
×
  • Create New...