Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

win32

Member
  • Posts

    1,073
  • Joined

  • Last visited

  • Days Won

    62
  • Donations

    $0.00 
  • Country

    Canada

Everything posted by win32

  1. 91 ESR is working with the hex patches I described earlier. 92 beta as well, but 93 developer also has issues for me. But remember that 93 developer is bleeding edge and instability should be anticipated. I would be concerned if the crashes stuck around to beta, however.
  2. Which GPU and driver are you using? I haven't encountered that issue on NVIDIA driver 342.00 using Quadro FX 3800.
  3. For those wanting to run Firefox 89+ on Vista, open xul.dll in a hex editor and search for the hex sequence FC 1C 01 00 00 C7 46 08 B0 1D 00 00 31 C9 BA 04 and change the bolded numbers to 72 17 and then again with 6B 2D 04 C7 47 FC 1C 01 00 00 C7 47 08 B0 1D 00 Notice how 1DB0 is hex for 7600 and 1772 is hex for 6002.
  4. I notice that the only publicly available 373.19 is from MSI. Perhaps it's part of a driver branch for OEMs and only MSI decided to make the driver they got publicly available? However, 372.93 and 373.06 are available from NVIDIA as reference drivers. The former for Windows 10 but the latter as an NT 6.x mobile driver: https://www.nvidia.com/download/driverResults.aspx/108323/en-us Also of note, NVIDIA's reference driver also calls memcpy_s.
  5. I later checked the drivers 372.90 and 375.63. The former does not contain the Vista block, although I don't have the NVIDIA hardware to drive anything past 342.00 (not here with me right now, anyway). I assume that 373.19 is a special case as it was intended for Vista, which would explain why it actually runs on Vista without needing memcpy_s in ntoskrnl? And has it been tested with Pascal cards, which are apparently worse off than Maxwell and earlier on Vista?
  6. ntoskrnl cannot be easily wrapped. Thus, I will only be able to provide one patched version of it. And another note, NVIDIA drivers after 372 fail to initialize if version 6.0 is detected and send the NTSTATUS REQUEST_NOT_SUPPORTED. NVIDIA had no problem providing barely-documented Windows 2000 support until late 2010 yet they have shifted to blocking operating systems, even those that are technically capable of using the drivers (Windows 8.1 with RTX 3xxx, early Windows 10 builds and soon Vista).
  7. In most cases, yes, but there may be issues with temp-folder based installers that are spawned from another installer. By the end of September. I have close to enough new features to justify a new release, but I think I can stuff some more in. And I also need to test. I have every K32 function implemented for both architectures, SetDefaultDllDirectories fixed on both archs, ResolveLocaleName (basic implementation) and soon some other things. I hope to get many basic x86 applications running. The kernel32 wrapper itself is probably more compatible than it was at another point in the extended kernel's existence, as it doesn't rely on the original kernel32 having SetDefaultDllDirectories (which was added to Vista in 2013). But that will soon not be the case, as it will call functions from my NTDLL wrapper, and that will need a modified ntoskrnl to work.
  8. The culprit for Firefox 89+ font issue has been found: something in ntoskrnl that has yet to be identified (although it should be not be difficult, as it was a bug fixed between Windows 7 RC and RTM). A few other extended kernel users helped identify the source of the bug by running Firefox 89 on Windows 7 builds 7100 to 7600. 7100 to 7264 (the RC) have this issue as well, then RTM runs it fine. We are blessed by the stability of Windows 7 beta builds as they have helped us identify various issues (6519 as lacking the "drift" issue) without letting the builds' inherent idiosyncrasies and shortcomings get in the way. Imagine if we had to work with Whistler or Longhorn builds? VMware Workstation 16 will take longer due to a lack of functions for the VMX driver, although later versions of 11 and 12 should run with the GetVersionEx spoofer.
  9. Yes, and fcwin2k (for specific applications). However, they don't manipulate the GetVersionEx* functions and just manipulate some registry values instead. This was good enough at the time, but isn't 100% effective like my method. And the registry value that win2k used to grab version numbers has been deprecated as of Vista.
  10. Work continues on the Vista extended kernel. With the next release, you will be able to spoof version numbers on-demand, for either a specific application or the entire system. The values will be set in osver.ini in the Windows folder. Because I had difficulty accessing high-performance, Vista-compatible hardware for the past few months, I was initially forced to test it on NT4.
  11. Yes. Just install the same required updates.
  12. I have yet to find a way, as 2019's x64 installer crashes early on (for now). And implementation of 32 bit functions for the x86 installers is forthcoming. There were no formal bundled updates until November, as things were just added in at will. So it will be impossible to do so for that period. Too busy for November to May. But now that the structure of the project is evolving, there should be one for the next release, likely in August or September.
  13. It does, as the Eclipse 2020-12 IDE does call win7 functions through its JRE. I believe it's using JRE 14 or 15. Worked perfect.
  14. The Extended Kernel project is still active, but the amount of time I have to work on it has dropped to new lows for various reasons. In fact, I was investigating the Firefox 89 font rendering breakage, and was planning on upgrading win32k to fix it (and upgrading win32k will help with gdi32 and DX components; plus, something in win32k bugchecks me when I close Waterfox G3 sometimes). But I am only near real Vista hardware for 2 out of every 14 days through late August. One side note: I have finally found something that surpasses Vista in performance on my HP Z600 workstation, while being from its lineage. 21996.1's averaged benchmarked results (in Cinebench R11.5) are slightly better than 2008 with 2019-04 updates and extended kernel, and perceived performance is identical or even better than Vista, which in turn is better than 7/1809. So some efforts may be redirected to that from Vista.
  15. I believe that VMware's drivers (like vmx86.sys) are missing functions at the moment, and some Windows 8 functions will be needed as well. There is also a version block that prevents VMs from launching starting with 11.0.23 and 12.0.1 that will also have to be defeated. I hope to accomplish this in a few months. It will be very ironic to have VMware 16 working on Vista hosts, considering that its guest additions don't support it!
  16. Some applications started demanding the SHA-2 rollup update KB4474419, which is obviously already installed, so that will become the minimum soon. Though there are currently two sets of ntoskrnl/winload; one works with April 2017 updates (soon to be discontinued), and the other only works with the (SHA-2) March 2019 update. They will not work with anything else.
  17. Yes. I tried debugging it, but I'm not sure if it's connected to directwrite, mediafoundation, or the non-presence of kernelbase.dll (which isn't needed by Vista, and is simply part of kernel32 broken out into a new file). Very hard with multi-process applications.
  18. Yes it would, though if you have the SHA-2 update, I would assume that it would have cached a 6003.20xxx HAL (which would be acceptable as I haven't released a HAL mod) instead of a 6002.18005 one.
  19. There are only two acceptable update levels, and two separate filesets for each; April 2017 (which is the standard for the update distribution), or March 2019 (which needs different variants of ntoskrnl and winload (exe/efi) that are not currently incorporated into the installer, though they will be with the next version); the latter is the SHA-2 update point. This was done to placate some applications that reportedly requested the presence of the SHA-2 update.
  20. They shouldn't have messed with the boot options, though they may have overwritten ci.dll and especially ntoskrnl.exe, which is now quite important.
  21. What is your update level? The addition of a custom ntoskrnl has/will make the flexibility of updating considerably lower than in the past, which means you will only be able to use the updates that correspond to the ntoskrnl/winload that I've made. So right now it's just April 2017 or March 2019, and soon it will be just March 2019.
  22. I recently started a separate site with more details on the extended kernel. You can find it by searching "eclipse" and the TLD for Christmas Island. But yes, I am trying more invasive methods of version spoofing, which have worked for the .NET Core 5.0 installer, but make Steam think it's offline, while Office has yet to be tested.
  23. That would be odd, as those updates are perfectly applicable to Vista. The only problem I could see is that the updates may be the wrong architecture (ia64 or x86). My installs use media with slipstreams built by DISM++, which means that I don't get an update list on new installs made with them, which means I have no particular idea.
  24. To get the best extended kernel experience, install from vistakernsetup_02262021.7z. It's a 7-zip archive that contains the extended kernel installer and the newest files. Widevine DRM components are not working for unspecified reasons. They worked back in July, though I think that it may have something to do with the extensions not recognizing locales. ntoskrnl changes the NT version in the registry back at every boot. I patched it once, but it did nothing to prevent version blocking, so I left it alone.
  25. Yes. EnumDisplayDevicesW seems faintly familiar, but it returns completely different info so it's likely not a suitable replacement. And more proof of crummy MS documentation. It lies to users about the function being in Vista! https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-displayconfiggetdeviceinfo

×
×
  • Create New...