Jump to content

win32

Member
  • Posts

    1,266
  • Joined

  • Last visited

  • Days Won

    79
  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by win32

  1. No. USP 5.1 is just an alternative to SP4 UR1. HFSLIP includes DX9.0c, IE6 SP1, post-EOS updates, XP embedded updates etc. And nLite is also an alternative to HFSLIP; they almost do the exact same things.
  2. That is the same thing as in the post above. While it does work somewhat, it stops working after returning from standby/hibernation. RMClock continues to work in such cases and works well on the T60, but is not an option for Westmere or newer.
  3. What are those functions? Not long ago, I found out that there is a Windows 7 Pro key under my workstation, and I might just use it. I know that user32.SetCoalescableTimer is needed to run Office 2019 setup (Office 2019 itself does run on Windows 7, with the help of a script from MDL), so I might work on something for that.
  4. Maybe DXVK would work. It does target Linux/WINE, but there has been success in using it for games on Windows 7: https://github.com/doitsujin/dxvk/releases download the tar.gz and extract the files in the x64 folder to your game folder. forget it. just realized there are no d3d12 binaries. Though I wonder what would happen if the DirectX graphics kernel was replaced with the one from W7 (dxgi.dll, dxgi.sys, etc.). I think if it works, then graphics drivers would work as on W7. Windows 10 beta/1507's files may also provide an opportunity.
  5. The 365.2064 was referring to whatever Office release would come out in 2064. While Office 2010 hasn't yielded any compatibility issues for me yet, it is a "when" and not an "if" based on previous experience. In fact, I printed a Word 2007 document with Office 365 in 2019 and there were several inexplicable spaces inserted into the document.
  6. VS 2019 can still specifically target Windows XP. Since it works on NT 5.1, 5.2 x64 is probably a pass since it has more API functions implemented than 5.1.
  7. Is it 32 or 64 bit? If the latter, then tell me what Dependency Walker says.
  8. You should be able to get them from a Windows 10 ISO (extract system32 from sources\install.wim in 7zip): https://www.microsoft.com/en-us/software-download/windows10ISO Select the appropriate options and it will give you an ISO. Those api-set-win-core-* files have hidden attributes though.
  9. NNN4NT5 doesn't work at all on NT6 OSes. Those api-ms-win-core-* files usually are quite portable. Try copying them over from a win8.1/10 install. It may also be included in the most recent VC++ 2019 runtime.
  10. no, I decided to remove them since the tutorial steps aren't a good way of doing things anymore, though I wanted to keep the text as it was originally written. The latest version 88 is now possible. But some file hosts haven't updated their files. If your kernel32/user32 files are from July and not October, PM me.
  11. yeah, that's the thing. I'm not aware of a script that will apply the post-UR1 updates all the way to April 2013 to an existing Windows 2000 install. You could cheat with IE6 SP1 + KB951748 + KB2817183 though like I have in the past. And KB919521 is this. I don't think they ever made an update package for it, though HFSLIP applies it along with enablebiglba: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\HAL] "14140000FFFFFFFF"=dword:00000010
  12. KB919521 (which is just a change to the registry) fixes whatever damage UR1 caused. But Windows 2000 always had issues in that area, but they don't manifest themselves until you standby/hibernate and return from those states. Running RMClock fixes that problem. You should really look into HFSLIP 2000 as well for a fully updated Windows 2000. Just avoid the .NET add-ons as they're buggy. And extra care is required if you run nLite after HFSLIP (but not before).
  13. https://en.wiktionary.org/wiki/err#English The third definition is the most fitting in this case, instead of going ahead and fulfilling the first definition by falsely claiming that this was the Milky Way's best source for Vista enhancements.
  14. Welcome to the world's leading source of Windows Vista news and enhancements! I thought about expanding this claim to the entire Milky Way, yet there are apparently Martians who already have DX18 and have it working on Vista. So I erred on the side of caution.
  15. Electron-based Discord? Sure, though not the official one at present due to being 32 bit, and I'm unaware of any circulating out there. Though this should work to make your own: https://github.com/jiahaog/nativefier ...and you will need the extended kernel of course!
  16. Which ones don't work? YouTube videos play OOB just like with the older Chromium browsers.
  17. Sorry, I thought the versioning for 365 had a year component to it. Turns out it's actually similar to Windows 10 versioning (currently they're on version 2009).
  18. I don't think we'd need source code anyway (which is for XP SP1/2003 RTM, which are quite different from the XP SP3/2003 SP2 that most people use nowadays). A good start would be to extract the Server 2008 SHA2 updates and look at the applicable files. Indeed I have done a hack that got marginally improved SHA256 support on Windows 2000 using POSReady crypto libs.
  19. Chromium 88.0.4091.0 x64 is working on Vista now. Themes install, but I still haven't figured out webextensions.
  20. igdumd64.dll is indeed part of the Intel graphics driver. Installing a different/newer version of the driver may help.
  21. Imagine. Someone extends Office 2010 in the future so it can properly render all documents made with Office 365.2064! And wrote plugins that incorporated all of that new version's features... Why didn't anyone do that with 2000/2003? OK there's the compatibility pack (wish it worked on Windows 95) but I've seen PPTXs that don't even work properly with 2007. I bought Office 2000 because I thought it would be the gateway to reading Office Open XML documents on Windows 95.
  22. Isn't that a web application (which worked well in roytam1's browsers last I checked, which means 2000/XP)? Or did they introduce a desktop client?
  23. Only ntoskrnl changes (and possibly some for ntext later on) require a modified winload file.
  24. You can also just change ntdll.dll to ntext.dll which has an implementation of RtlQueryPerformanceCounter. The next change to kernel32 should eliminate the need to change SubSystem versions in executables.
  25. Since I said that, I found that an x86 dll broke after renaming both a forwarded export and its pointer to the recipient function/dll. Simply changing the latter did not causes problems. I don't believe that this problem exists with PE32+. No, but I heard of it a long time ago. Didn't use it though considering the stability of exporttabletester with PE32+ and your statement that the regular ExpX corrupted one of your files. Though it seems pretty nice. Most of the work in kernel32 was done in late June and early July, almost immediately after gaining the bare minimum knowledge necessary to add functions to PEs. So horrific messes like that occurred because I kept running out of room in each new export table and didn't think of expanding the current one. Reason? CFF Explorer would never enlarge a section even if I had changed the virtual and raw sizes of it afterward. Now I know enough to make sure such a cluster.... never happens again.
×
×
  • Create New...