Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/11/2022 in all areas

  1. I released a new extended kernel. "FirefoxFix" and "SuperVerFix" are removed from osver.ini. You can use BuildNumber=7600 for Firefox instead, and use the regular version spoofing in other places too where those options would have been used previously. CPU-Z (and other hardware verification software) works again, as does PCSX2 (x86 versions; the newer x64 native builds are still a ways to go, due to reliance on DX 11.3 runtime) and some newer compilers/linkers should work too. A new installer is also used, which lacks the path issues of the previous one. It has a built-in backup facility, and the installer can restore backups from another OS install or a PE environment by specifying the path of the Windows directory of your Vista install. It can be obtained through all the known channels.
    4 points
  2. Hello everyone. Today I have edited the installation of Audio KB888111 UAA UPDATES to be able to work with SP3. And I have changed the portcls.sys file to version 5.1.2600.5566 File Name : kb888111xpsp3_modPatchedInstaller.zip CRC-32: cf3dea73 SHA-1: 69cdc438d13fb56fa421212f0aeef4ea6f3345c5 SHA-256: af4d536b6aa852064a1134a741c12b1722f4fb61971e87e43e426be4243f6f0d https://drive.google.com/file/d/11vhm1K2Hgxg4A9LNDqbzBd8Yf-mfPfOO/view?usp=sharing
    2 points
  3. try another useragent in the loader.ini : --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.63 Safari/537.36" with this however it will not pass the ddos cloudflare protection on some sites.
    2 points
  4. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220611-3219d2d-uxp-fec5435ab-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220611-3219d2d-uxp-fec5435ab-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220611-3219d2d-uxp-fec5435ab-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220611-d849524bd-uxp-fec5435ab-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220611-d849524bd-uxp-fec5435ab-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220611-d849524bd-uxp-fec5435ab-xpmod.7z Official UXP changes picked since my last build: - Issue #1905 - Part 1 - Implement detection of Monterey (12.x), Intel emulation and fix required OS version check. (8cee7f2b1) - Issue #1905 - Part 2a - Build system fixes to allow use of SDK versioned 11.0 and higher. Also don't include code incompatible with SDK 10.15 and higher, when building with such a SDK. (45606ffa5) - Issue #1905 - Part 2b - Fix crash on startup due to inability to load system font with newer SDKs. Fix based on Mozilla Bug 1672842. (d18524ab7) - [MailNews] Allow shift-clicking on Edit As New to edit a message as plaintext. (6182744d9) - Revert "Issue #1909 - Guard against empty update manifest URL" (d8e6867da) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - Revert "Issue #1909 - Guard against empty update manifest URL" (8c7e1338c) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    2 points
  5. Dolphin, the GameCube emulator is dropping Windows 7 support. The current beta, released a month ago is the last to feature 7 support. Get it here: https://dl.dolphin-emu.org/builds/51/be/dolphin-master-5.0-16380-x64.7z
    2 points
  6. Looks for btnDumpPlatform.addEventListener in lib/main.js and make it like this: btnDumpPlatform.addEventListener("click", () => { const info = { "PolyfillService": toJSON(gService, "is"), "appInfo": toJSON(Services.appinfo), "addonData": toJSON(gAddonData), }; delete info["addonData"]["installPath"]; const dumpInfo = JSON.stringify(info, null, '\t'); try { const filePicker = Cc["@mozilla.org/filepicker;1"].createInstance(Ci.nsIFilePicker); filePicker.init(Services.wm.getMostRecentWindow("navigator:browser"), "Save platform information", Ci.nsIFilePicker.modeSave); filePicker.appendFilter("JSON file", "*.json"); filePicker.appendFilters(Ci.nsIFilePicker.filterAll); filePicker.defaultString = "PlatformInfo.json"; filePicker.defaultExtension = "json"; if (filePicker.show() != Ci.nsIFilePicker.returnCancel) { const fs = Cc["@mozilla.org/network/file-output-stream;1"].createInstance(Ci.nsIFileOutputStream); fs.init(filePicker.file, -1, -1, 0); fs.write(dumpInfo, dumpInfo.length); fs.close(); } } catch (e) { alert("Palefill", e.toString()); } console.log(dumpInfo); });
    1 point
  7. This can only work in cases where the site's code only ever sets up regex objects explicitly through RegExp(). Code like... const myRegex = /incompatible regex here/; ...won't work. Those aren't "polyfills", those are core language syntax constructs. You can't "polyfill" core language syntax constructs. It manipulates/replaces RegExp object among other things. So concluding the statement above, the answer is no. Learn C++, Windows API and their limitations on XP, fork old Chromium, backport to XP, modify the JS interpreter to understand nullish coalescing, optional-chaining operators and code your own GUI on top since you don't like the default one. That's possible with the right skills.
    1 point
  8. Try this - https://web.archive.org/web/20070127041529/http://download.microsoft.com:80/download/9/b/5/9b59baf0-d78e-448f-a409-2dcd8ff3baf6/WindowsServer2003.WindowsXP-KB901105-v3-x64-ENU.exe
    1 point
  9. @thomasxxx You mentioned you have the HDD drive inside a USB Caddy? if so then you're not using an AHCI driver but are using the USB Mass Storage driver instead.
    1 point
  10. @VistaLover - I am always amazed at how you can keep track of all of this "stuff". I always read these and can't for the life of me know "which" Serpent or New Moon to even "trust" anymore
    1 point
  11. Mrs. Pac-Man on a C64 emulator.
    1 point
  12. Seems to be possible indeed: https://stackoverflow.com/questions/23147087/how-to-detect-syntactical-features-of-javascript In general it seems useless but in this case this is the way to go. It would be the most practical thing indeed, I Just need too learn JavaScript at some point. However for the UXP platform there are very few builds anyway so a version based system should be fine.
    1 point
  13. Hi, I've tried your installer on Vmware and at first got this error (maybe because I'm running Polish language version): After removing software checking part of the setup.bat, I was able to proceed with the installation. On reboot(s) another error popped up: So after making sure that all extended kernel files are in system32 directory, I booted my virtual machine into a Vista installation image and launched automatic startup repair. The tool not only solved the problem (probably by removing the installer from autostart), but also retested all permissions for system file back to their defaults, so I didn't have to do it myself and in the end the extended kernel was working as intended. Good job @Bizzbob (no sarcasm) because it's definitely an improvement over the original installer, although it still need some tweaking. It's also highly possible that I'm getting all those errors just because I have Polish edition of Vista. I'll put a link to your post in the guide.
    1 point
  14. Hi all, I've decided to write my own batch installer for the extended kernel that automates a few steps. At the moment it should be able to: Automatically trigger UAC to run as administrator Check that you are installing on Vista x64 (but doesn't check that you have the required updates!) Back up existing system files as *.bak Replace system files at reboot to avoid 'access denied' problems Set file permissions for the replacement files Enable local DLL redirection automatically and fix problems with Windows Sidebar (by making it use the original ole32.dll) Create OSVER.ini Optionally install the Media Foundation Platform update (see below) Optionally set x64 Windows Media Player as default for all users (if installing Media Foundation Platform) Check for any errors in the process and safely roll back any changes if problems occur (obviously still a good idea to back up your system!) Create a log for troubleshooting The batch installer requires a different configuration file (attached) for each release of the extended kernel to be installed. These are named in the same date format as the zipped extended kernel .7z files. To use: Place SETUP*.bat in the same folder as the extended kernel installation files extracted from the .7z archive Copy the corresponding version of the .cfg configuration file into the same folder (and rename as SETUP.cfg if using installer versions older than SETUP3.bat) If installing the Media Foundation Platform, place the extracted MFPLATSETUP folder as a subfolder with the rest of the extended kernel files Run SETUP*.bat and hope that it works... The installer automatically creates a basic OSVER.ini (if none exists), but its contents can be customised in the config file (does not replace any existing OSVER.ini). If Vista behaves oddly post install (e.g. Firefox failing with RtlQueryPerformanceCounter not being found), a second reboot should fix it. This is a limitation of the way this installer replaces system files at reboot, as certain files are loaded into memory before replacement and remain until the next reboot. Update 31 Mar 2023: Updated installer SETUP3.bat Feb 2022 configuration info no longer embedded, but .cfg files no longer need to be renamed (as long as only one version is placed in its folder - can get confused if more than one .cfg file available!) Makes copies of MUI files for the March 2023 extended kernel release Added SETUP_03092023_x64.cfg and SETUP_03092023_x86.cfg for the March 2023 release / revision 1 Update 31 Oct 2022: Renamed SETUP_10192022_x32.cfg to SETUP_10192022_x86.cfg Update 28 Oct 2022: Updated installer SETUP2.bat (various minor bug fixes; no longer fails installation when running from read-only location; checks that file permissions are updated successfully) Added SETUP_10192022_x32.cfg and SETUP_10192022_x64.cfg for the October 2022 release (see note below) Download installer SETUP3.bat for all releases - this is overdue a re-write, really. But for now I have amended it to work with the newest March 2023 release. Unfortunately extremely busy at the moment so this has had very VERY limited testing - please back up and use with caution! setup3.bat SETUP2.bat for old releases up to and including October 2022, that has had a bit more testing (at least, no-one's told me they've had any major issues...): setup2.bat By default, SETUP2.bat works with the Feb 2022 release of the extended kernel, but can be made to work with newer/older versions using configuration files (attached below). Simply rename the version you need as SETUP.cfg and place in the same folder as the batch file. Configuration files Note: the October 2022 and March 2023 Extended Kernel releases include too many files for the batch installer to handle at present, so the configuration files have been split in two for now. I would recommend installing the x64 files before x86 (reboot required in between). On first reboot after installing the x64 files, you may get a BSOD or crash with the 'Windows did not shut down properly' screen, but Windows will start up again normally after this, and the x86 files can be installed normally. The March 2023 x86 configuration file should be used with SETUP3.bat to ensure MUI localisation files are copied. setup_03092023_x64.cfg setup_03092023_x86.cfg setup_10192022_x64.cfg setup_10192022_x86.cfg Configuration files for older releases: setup_07252022.cfg setup_06102022.cfg setup_02042022.cfg setup_10262021.cfg setup_05142021.cfg setup_02262021.cfg setup_12312020.cfg If your Vista was installed using the MSDN iso, you may need to place Win32's replacement EXPLORER.exe with the rest of the extended kernel files and remove the ; at the start of the relevant line in the file list in SETUP.cfg (not required from the Feb 2022 release onwards). Help for configuration files: Config info.txt
    1 point
×
×
  • Create New...