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,079
  • Joined

  • Last visited

  • Days Won

    62
  • Donations

    $0.00 
  • Country

    Canada

win32 last won the day on September 3

win32 had the most liked content!

About win32

  • Birthday 05/24/2001

Profile Information

  • OS
    Vista Ultimate x64

Recent Profile Visitors

12,454 profile views

win32's Achievements

739

Reputation

  1. I installed these drivers on a terrible HP laptop. Not much information provided by HP on it. Also, I just recalled that there was another set of unsigned generic USB 3 drivers that also worked.
  2. Yes, I did get one digitally signed set working at USB 3 speeds. I don't believe they are posted in the forum however. I will send them if needed.
  3. It now appears that the partial fix for the Haswell TSC drift issue was in a update released between 2017 and 2019. While this issue only seems to have appeared with the Haswell CPUs, fixes for the issue do date back to build 6519 (released in December 2007), as I have tested on my Kaby Lake laptop. In a series of reboots, all services started and there were no issues with application execution.
  4. Firefox 91-based Waterfox continues to run on Vista, and my extended kernel's implementation of Windows 8 API is still minimal. But it is not enough for Steel Bank Common Lisp, so both Vista and 7 users are out of luck due to the non-presence of CancelWaitableTimer: https://sourceforge.net/projects/sbcl/files/
  5. About that, the experimental extended kernel version was able to install Office 2019 and almost run it. I've yet to try Office 2013 or 16, as the current version spoofer works for 2019 but not 2013/16 for a few possible reasons. Most of the others are a little iffy, if only because they are first-party software, and it tends to be harder to get newer versions running of those than third-party ones (which is also true of Windows 2000; struggles with parts of Office 2007 while it can run every version of LibreOffice and OpenOffice that XP can). I think a couple of those are x86 native electron apps while iTunes is win7-compatible with a Windows 10-tailored version block (I do have a likely solution for it). So the former will be available when x86 matures (the kernel32 functions are plentiful for those now, but I haven't started on the other dlls) while the latter will be attempted very soon.
  6. 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.
  7. Which GPU and driver are you using? I haven't encountered that issue on NVIDIA driver 342.00 using Quadro FX 3800.
  8. 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.
  9. 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.
  10. 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?
  11. 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).
  12. 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.
  13. 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.
  14. 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.

×
×
  • Create New...