Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200912-72c45cb-uxp-b55d425b3-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200912-72c45cb-uxp-b55d425b3-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.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200912-72c45cb-uxp-b55d425b3-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.rths.ml/palemoon/palemoon-28.10.2a1.win32-git-20200912-2771b99fc-uxp-b55d425b3-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20200912-2771b99fc-uxp-b55d425b3-xpmod.7z Official UXP changes since my last build: - Issue #618 - Add JS API to associate scripts with DOM elements after compilation (22f300f7c) - Issue #618 - Implement preloading of module scripts. (92ef20627) - Revert "Issue #618 - Add JS API to associate scripts with DOM elements after compilation" (e4fb3f48a) - Issue #1644 - Remove plugin checking code leftovers (9440be0ae) - Issue #1639 - Implement object.fromEntries() (1154e4884) - Issue #618 - Make ES6 modules work for resource: URIs (8e5d9da5e) - Issue #618 - Clear the module map when changing a Document's global and add release build assertions for mismatching compartments. (df55ce903) - Merge branch 'es-modules-work' (b55d425b3) Official Basilisk changes since my last build: - Update back-end branch pointer. (72c45cb) Official Pale-Moon changes since my last build: - Issue MoonchildProductions/UXP#1644 - Remove plugin check leftovers (front-end) (24a06c474) - Issue #1717 - Add distinct mixed-mode indicator and logic for display. (2771b99fc)

Hope you feel better soon , the other things can wait

... Now you hush, "young" gentleman! Those people are already extremely p***ed that you, single-handedly, created the Vista Extended Kernel project, so much so that they fear their "support channels" will get overwhelmed by Vista users running their official builds: https://forum.palemoon.org/viewtopic.php?p=198116#p198116 As the saying goes, "No good deed goes unpunished" ...

One year ago today... Rudy, you are sorely missed!

Lots of news. I managed to work around ntdll somewhat. My ntext (ntdll with a new section and updated checksum) was successfully hooked by kernel32 through forwarded functions. But programs that call ntdll directly didn't go as well. Firefox would crash or pseudo-load hogging up several CPU threads. So I think a completely new wrapper dll that forwards to ntdll is necessary. I was almost successful in getting the Windows 7 compatibility shimming framework to work (a modified aclayers.dll that fakes Windows 7 SP1 instead of RTM and acppage.dll in particular). But the latter calls registry-related functions from kernel32 instead of advapi32. So I added them to kernel32 forwarding to advapi32 but it didn't work as it would keep forgetting the compatibility options (those reg functions are slightly different on 7 than Vista but very difficult to implement). So it may be better to modify the Vista versions of the files, but it's not that clear cut to me, unless I were to replace one of the existing compatibility options (somehow I think no one really bothers with the 2003 SP1 option).

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200829-57e81f0-uxp-5559674be-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200829-57e81f0-uxp-5559674be-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.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200829-57e81f0-uxp-5559674be-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.rths.ml/palemoon/palemoon-28.10.2a1.win32-git-20200829-0882134ff-uxp-5559674be-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20200829-0882134ff-uxp-5559674be-xpmod.7z Official UXP changes since my last build: - Issue #618 - Fix error events fired when loading JS module dependencies fail (786e34469) - Issue #618 - Align error handling for module scripts with the spec (again) (43e0632cd) - Issue #618 - Use a single slot for the module's environment object. (6e72707e0) - Issue #618 - Lazily initialise module binding maps (e94f9dcce) - Issue #618 - Record module dependency before starting fetch so that error handling works correctly (8447c4d8a) - Issue #618 - Remove eager instantiation - Debug follow up (007c54c80) - Issue #618 - Lazily initialise module binding maps - Debug follow up (609815070) - Issue #618 - Align error handling for module scripts with the spec - Debug follow up (c5b47eb66) - Merge pull request #1626 from g4jc/618 (501b29a5d) - Issue #618 - Simplify module map interface (7e673b1db) - Issue #618 - Keep track of which modules in a graph have been fetched using a visited set (15a7be79b) - Merge pull request #1627 from g4jc/618 (1c342a57e) - [js] Add some utility functions to get the current JS runtime. (c349f04f9) - Issue #618 - Simplify module resolve hook to be a function pointer (9b6252893) - [js] Try to catch bad pointers for GC and bail if not valid. (e1e535c1c) - Merge branch 'master' into es-modules-work (11285cd0d) - Issue #618: Ignore 'event' and 'for' attributes for module scripts. (4f0d9497f) - Issue #618: Pass down referrer and referrer policy when fetching modules. (86f128d41) - Merge branch 'master' into es-modules-work (c04befb93) - Issue #618 - Don't mute errors for module scripts because they always use CORS (073e914eb) - Issue #618 - Integrity for descendant module scripts should be the empty string (c8a701b64) - Issue #618 - Split handling of load errors out from OnStreamComplete. (090a48738) - Issue #618 - Split SRI verification out from OnStreamComplete. (cbbfd0f2d) - Issue #618 - Handle errors for inline module scripts and ensure we update the module map after fetch errors. (f0175ebc7) - Update old.configure for --enable-phoenix-extensions (f909e1a6c) - Issue #618 - Fix processing of non-parser-generated module scripts. (76e5f863a) - Issue #618 - Make document.currentScript null in modules. (c5ab17748) - Issue #618 - Rename some script load request flags to be more descriptive. (a0ef1c07d) - Issue #618 - (async) Split out function to add async request. (95e0f114e) - Issue #618 - (async, preload) Correctly pass info about async/defer to parser. (2ca1cbe2f) - Issue #618 - (async) Keep track of script modes in a single mode state. (8b397a63a) - Issue #618 - (async) Implement async attribute for inline module scripts. (b78f53ffb) - Issue #618 - Don't preload nomodule scripts when modules are enabled (38d13e277) - Issue #618 - Regenerate the HTML Parser code for nomodule changes (0f433fc7c) - Merge pull request #1637 from g4jc/618 (8924e4ddd) - Merge branch 'es-modules-work' (6eb0dd861) - [media] Only include source error details in debugging scenarios. (4358ff62a) - [DOM] Only construct JS-implemented objects if inner window is current. (226fea386) - [misc/mar] Don't use a signed type for a length parameter. (7407fe22f) - Issue #1587 followup - Improve resilience of AbortSignals. (5559674be) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Update back-end branch pointer (202766dec) - Add a configure option for Phoenix Extensions Dual-GUID System and set default off in confvars (f7a1deb67) - Update platform and version (Unstable 2020-08-27) (0882134ff)

Windows always used to be the OS where you could do whatever you liked, theme the crap out of it and customize it to your liking. It's starting to become more like macOS where you can't do much and everything is the way Apple wants it to be.

Ah yes, as usual it's always someone else's fault when Tobin goes on a rampage. And I love how MC tries to make it sound like there's some kind of "opening" for everyone to work together.. - what a load of rubbish. Anyone but a fool or the willfully ignorant can see the way they have behaved toward anything they don't approve of or consider to be beneath them. With them it's more like "conform and obey, or die." Who would want to "work with" such an arrogant, self important bunch of jerks? Love this. Yes, a dislike button would be a nice wake up call for a lot of people in today's society, methinks.

I just came to know about this guy's work. What a legend! Rest in peace. Some great work from this guy: ● AHCI CD DOS Driver ● AHCI for Windows 9x ● Full Disk encryption for Windows 9x ● PTCHCDFS - To correct displayed size of DVDs on Windows 9x ● Blu-Ray writing and reading support for Windows 9x ● >4GB file support for Windows 9x ● 48 bit LBA support for Windows 9x (HDD up to 2 TB) ● SATA support for Windows 9x ● >4GB RAM support for Windows 9x ● API Redirector for Windows 9x ● HDD Advanced Format support for Windows 9x ● SSD TRIM DOS program for DOS/Windows 9x on FAT32 file system ● 9x shell32 patch with newer functions ● Windows Driver Model (WDM) API Extender ● Update slipstreaming for Windows 9x ! Simply AMAZING! Thank you Rudolph Loew, you will not be forgotten.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200822-57e81f0-uxp-dd1ad91cb-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200822-57e81f0-uxp-dd1ad91cb-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.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200822-57e81f0-uxp-dd1ad91cb-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.rths.ml/palemoon/palemoon-28.10.2a1.win32-git-20200822-11ba7a43c-uxp-dd1ad91cb-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20200822-11ba7a43c-uxp-dd1ad91cb-xpmod.7z Official UXP changes since my last build: - Issue #1629 - Part 1: Implement basic logic in HTMLLinkElement. (a9f337ea7) - Issue #1629 - Part 2: Implement the Explicitly Enabled flag. (686232635) - Issue #1629 - Part 3: Implement behind preference. (931e8d29f) - Fix nits (2372e1902) - Issue #1620 - Intrinsic Aspect Ratio: Debug Follow up. (22c672813) - Merge pull request #1635 from g4jc/1620 (56f8262c8) - Merge pull request #1632 from athenian200/link_element_disabled (7ca7fe802) - [db] Update SQLite lib to 3.33.0 (9074e6928) - Issue #457 - Silence SQLite compiler warning (46595e390) - [js] Reinstate precise floating point model for all js sources. (1b14edc01) - Follow up to eb28b1f32 - Correct inputmethod build file by putting Keyboard.jsm back in EXTRA_JS_MODULES (dd1ad91cb) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Issue #1826 - Restore missing close icon on the undo prompt at the quick dial page (1227e3ce1) - Issue #1717 - Padlock Improvements (f746a96f7) - Issue #1717 - Low Cipher Changes (c3d5f8ae1) - Issue #1717 - 3DES Detection (78aac837d) - Issue #1717 - Localize Padlock Tooltip (9641725f6) - Issue #1717 - Whitespace Cleanup (1ff8522d7) - Issue #1717 - Revert 3DES Check to Original Method for Now (b81e1c204) - Issue #1717 - UXP Says Mixed Content is Broken (b76ba6161) - Issue #1717 - Differentiate DV & EV Mixed Content (ea7f0b6d6) - Issue #1717 - Total Level Rewrite (1f488302c) - Merge pull request #1828 from RealityRipple/master (30987e613) - Update platform and version (Unstable 2020-08-19) (0aa10d730) - Merge pull request #1827 from FranklinDM/quickdial-close-button-work (11ba7a43c)

The author would have to pack the extension separately for old Chrome versions and distribute that version outside of Chrome Store because CRX_VERSION_NUMBER_INVALID. Edit: file removed

not yet for the old data, but new build environment in new WD Black SSD works quite well. I almost get out from depression of regretting of not backing up data in time before old SSD died without obvious symptoms.

That would of course involve admitting that XP still exists, and that would never do!

OAuth2 + Yahoo authentication works with MailNews because I provided the code to Roytam1 and our developer applied this patch. A benefit for us all. You can find the code on the previous pages of this thread.

... Well, fortunately things aren't yet as dire as you pictured them , all thanks to web.archive.org The URL https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html has been captured 187 times in total, the last time "valuable" content was still in was on July 18th 2020 (https://web.archive.org/web/20200718192527/*) The last version of Adobe Flash Player without the 2021 timebomb was/is 32.0.0.371; WAO have actually captured the following URI https://fpdownload.macromedia.com/pub/flashplayer/installers/archive/fp_32.0.0.371_archive.zip 5 times, last one was on June 30th, 2020 (https://web.archive.org/web/20200630185943/*) ; the zip archive itself is at 388 MiB, so it'll take a while to come down from WAO... It contains all possible flavours of installers/packages, no need to search further... Don't make that mistake again...

... Do I get extra points for prophesying ? Try the above Direct Link now and you'll get the door slammed at your face : Access Denied You don't have permission to access "http://fpdownload.macromedia.com/pub/flashplayer/installers/archive/fp_32.0.0.371_archive.zip" on this server. Reference #18.c46656b8.1600036305.1ef6b01c

(Note: this text is written for and directed at Big Muscle. Just pointing it out in case that the "you"s looks a bit wierd to you (the person reading this text)) Let me first get the most important thing out of the way: You CAN make money with open source software. In many ways actually: You can charge for the convenicance of auto updates You can charge for direct support (for example, via email or via a private discord chat) You can charge for the convenicance of having an already compiled binary version (which is especially true on windows; on linux for example, you usually git clone the repo, cd into it and type `make && sudo make install` and that's it. On Windows though...) You can make (optional) donations Speaking of donations: what you offer on your website, those are NOT donations. Those are payments. It is NOT freeware. You just get a free demo version. A donation is something optional. The point of a donation is not to get something back from it (besides maybe the knowladge of having helped someone/-thing or maybe getting a "Thank you" mail from them), but purely to support someone/-thing. And I want to mention that that is the only reason why I actually paid 5 bucks for it: not because I care about the watermark (if that would be my only reason, I could have just used a cracked version, and yes, I DID have a working one back then, but I didn't use it), but because I want this project to stay alive. In other words: I am pretty shure that a lot of peole donated just for support, or at least partially. Anyways, I of course know that there are not only positive things about open sourceing this software, namely: You may not make the exact same amount of money from "donations"* You may unveal your secrets* However, both of these arguments are very weak. The first one I already talked about above. For the second one: opening this app would mean that a lot more developers could integrate it (as in making their app compatible with it, not as in stealing your code; the only app I know of that supports aero glass is Winstep Nexus, and that one only works when it really wants to, which, as a dev explained to me, is not their fault). It would allow other people to learn about windows from (because, as described on glass8.eu, it uses undocumented windows features). TL;DR both arguments are... bad. Now let's finally get to why I think it should be open sourced: You (Big Muscle) are not able to maintain this on your own, or at least not in a way that I would concider acceptable for a paid app. Often times, this app gets a fix about 1-2 months before the next major update comes out, which will break it again. And again. And again. This app would be accessable to a lot more people. It would improve the user experiance since it will allow updates to be completed much, much faster. You would not have to stem this project all on your own anymore, which, again, you're not able to. Almost the entire forum is just "It doesn't work" posts. As described previosly, third party compatibility could also be improved massively. A concern you may have is others missusing your code to make money on. This is actually not a problem. You can either use the GNU GPL (or similar), which will technically not prevent your code from being commericallized, but since every modification that is being made availably has to also be opensourced under the same license (or a newer version), it is very unrealistic to think that someone would actually do it, exept maybe in those ***** bundles. While some apps (like OpenOffice or 7-zip, see here ) do suffer from this problem, I, again, don't think that such a tool like AeroGlass would really suffer from this. Alternatively, you can also write your own license, for example like this (this is not legal advaise): Of course, the above mentiond "license" is only one of many ways it could be done (and, again, it is not legal advise). I hope that you will change your mind about this program and it's licensing and distribution, as it would gain both you and even more so it's community. Cheers.

So I hope you guys know about some of the interesting things about Windows Me, at MSFN in fact, I found all this info in bits and pieces scattered over many threads so I am posting it in a single post. Also, there are many people here who already know it or are much smarter so ignore, I am only posting it for those still playing with this ancient OS in a VM or real old hardware. Hope it's not a problem: 1. Only the OEM version of Windows Me has hibernation support, retail doesn't. Also, OEM Windows Me CD is bootable. 2. It is common knowledge that Windows Me was patched to restore MS-DOS real mode. Io.sys, Command.com and Regenv.exe can be patched so it processes Config.sys and Autoexec.bat. That is old news. But this way of patching has a downside - you lose the nice white Windows Me boot logo (logo.sys that's inside Io.sys) because it takes the Io.sys/Winboot file from the EBD (Emergency Boot Disk). But instead what I recently learned (sure seasoned members and experts know it already) is after using the Me2Dos patch to modify Io.sys, command.com and regenv.exe or patching it yourself with a hex editor, if you take the Io.sys from Windows Me's Bootable CD (after it boots to DOS for Setup) or from the OEM Preinstallation Kit (OPK) that's there in tools\nettools\fac -> DTA files (which are actually CAB files on the CD) and overwrite the one in C:\ drive's root with this one, then this OEM Io.sys does have the nice boot screen and you can still boot to DOS if you want due to the patched Command.com and Regenv.exe. In fact you get the full set of startup options like 95/98 except "Previous version of MS-DOS". So, after you have patched Windows Me with the famous Me2DOS patch to boot like 95/98, you can replace Io.sys with the non-patched Io.sys from Me OPK or Bootable Me ISO, and you get the best of both worlds - boot screen as well as boot to DOS/startup files no longer ignored. 3. Another advantage of Io.sys from OEM CD vs EBD patch is Expanded Memory is available in Windows Me for DOS programs. 4. Finally, you need to make a few changes to startup files after the Me2Dos patch and replacing Io.sys from OEM CD, so that "Command prompt only" option works like 95/98 and also you don't get boot errors at startup when booting Windows Me with the "Normal" option. I'll explain why you need to modify files again after the Me2Dos patch. With this unpatched Io.sys from OEM CD Boot image/OPK, it always loads Windows Me even if you choose the "Command prompt only" option. This is because the Command interpreter line in startup files lacks the /P (permanent) switch. You just need to add the /P switch to config.sys. After you install the Me2Dos patch, it modifies Config.sys to add this line: shell=c:\command.com e:32768. Just modify it as stated below so you don't get a "File creation error" when booting. Like this: shell=c:\command.com c: /p /e:32768 (Note the correct use of /p switch in Config.sys is to list dir where command interpreter resides before it so you must add: c: before /p) Also this Io.sys will automatically load Ifshlp.sys so you can comment out the line in config.sys added by Me2Dos patch by a semicolon and lastly remove the line from Autoexec.bat: C:\WINDOWS\win.com as with the non-patched Io.sys from Bootable OEM CD, it will load Windows Me anyway when "Normal" startup is used. So you get all options working exactly like Windows 95/98: Normal, Logged, Safe Mode, Step-by-Step Confirmation, Command Prompt only (which does process your Config.sys and Autoexec.bat but boots to DOS only) and Safe mode command prompt only which bypasses them. 5. Another fun thing I recently learned is with the ORIGINAL Io.sys that Windows Me officially installs (not the patched one from Me2Dos/EBD patch and not the one from OEM Me CD), Windows Me does not actually need Win.com to boot! It is there only for compatibility but Win.com then loads vmm32.vxd which is the main file that switches from real-mode to protected mode. So you can do fun trick (not that there is any use of it): - Rename C:\Windows\Win.com to WinMe.com so Windows doesn't find it automatically - Rename C:\Windows\system\vmm32.vxd to vmm32.com. - Take Command.com from tools\nettools\fac -> DTA files and rename it to C:\Windows\system\vmm32.vxd Now when your PC boots with original unpatched Io.sys, it will only load Command.com Also you can directly load Windows Me by running: C:\Windows\system\vmm32.com. Or create a batch file in C:\ called Win.bat which points to C:\Windows\system\vmm32.com. That way it loads command.com. If you type, Win, it loads Windows Me. Note that I find this trick (#5) useless as original Io.sys bypasses startup files so there is no advantage of booting to DOS. Also if you use any different Io.sys, then vmm32.com will fail to load Windows Me directly. Let me know what you guys think. I think having access to MS-DOS almost like Windows 98 is awesome. The only thing that is still missing is Restart to MS-DOS Mode option but you can always dual boot between some version of DOS and Windows Me/DOS if you don't like "Command Prompt only" (Windows Me DOS 8.0).

As much as I despise the look and feel (and performance downgrade) of every version of Windows 10, I found the Windows Blinds thing just didn't cut it for me. In fact, find all of Stardock's stuff is bloatware that isn't done well. Even Start10 is junk compared to StartIsBack, not to mention it is also overpriced. But, anyhoo, Window Blinds... I almost bought this piece of garbage a couple of weeks ago since it's not clear how much longer it will be until we have AeroGlass for Windoze OS X 2004, and OMG... so glad I did the trial first. It sucks. Removed it within a few hours after tinkering with it and hating it more the more I used it. And, then I tried Stardock Curtains and found it was equally a bloated and buggy piece of crap that make Windows 10 uglier-looking instead of better. There's just no substitute for AeroGlass and StartIsBack as far as I am concerned.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200905-57e81f0-uxp-6b3ef7160-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200905-57e81f0-uxp-6b3ef7160-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.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200905-57e81f0-uxp-6b3ef7160-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.rths.ml/palemoon/palemoon-28.10.2a1.win32-git-20200905-0882134ff-uxp-6b3ef7160-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20200905-0882134ff-uxp-6b3ef7160-xpmod.7z Official UXP changes since my last build: - [NSS] Prevent slotLock race in NSC_GetTokenInfo (58cc431b0) - [NSS] Version and build bump (59683edb8) - Clobber for NSS update (0ac50227e) - Issue #1641 - Implement CSS flow-root keyword (6b2c3b61b) - Merge pull request #1642 from athenian200/display_flow_root (0bf7cb907) - Clobber for CSS flow-root implementation (6b3ef7160) No official Basilisk changes since my last build. No official Pale-Moon changes since my last build. My changes since my last build: - update NSS as-of pm27 rev 7606140ee (8015bb700)

With all due respect, probably because the older software still performs perfectly and is licensed for life, while an upgrade would require a new and expensive license just for show purposes, since it adds nothing really needed. Do you think people are made of money? Moreover, you yourself told he's gotten his clinic renovated... for normal human beings, there's only so much money (more so in times of covid-19, on top of it)!

Chrome is trash. Firefox is now following said trash. Pale Moon is the last, best hope... (If only they weren't such an arrogant bunch...)

commits will have a look before landing to my tree, and if undesired changes were landed they will be reverted.

actually it does, there are changes that preventing it to work in XP: 1. mozilla removes large chunks of code for XP while adding non-XP compatible APIs usage 2. rust compiler can't produce XP compatible code

... Are you sure this is FULLY de-obfuscated? function displayContent() { if (X("0x3", "^Mn5") in navigator) { uaPrefix = navigator[X("0x10", "wOY$")] + "/5.0 (" + navigator[X("0x5", "&j9b")] + ";"; if (!navigator["userAgent"][X("0xf", "wkB!")](uaPrefix)) return; if (navigator[X("0x4", "G9*&")] && (navigator["oscpu"][X("0x8", "^Mn5")](X("0x9", "Puzb")) || navigator["oscpu"][X("0xe", "73(^")](X("0x11", "e6DU")) || navigator[X("0x0", "DLe0")][X("0x2", "fCh&")](X("0x6", "pseB")) || navigator["oscpu"][X("0xb", "k4n@")](X("0xc", "GBIt")))) return null } var ig = document["getElementById"](X("0x1", "6osW"))[X("0x7", "rMvY")][X("0x13", "czCY")](!![]); document[X("0x12", "&iPz")]["appendChild"](ig); document[X("0xa", "Y8yJ")]["id"] = X("0xd", "wOY$") } ... Though he doesn't acknowledge he had anything to do with their removal, Moonchild's account of things: https://forum.palemoon.org/viewtopic.php?p=198040#p198040 TL;DR 1. He pretty much (as expected) justifies M.A.T. because he was undeservedly banned from MSFN without notice, as being "a long-standing member with a good track record" () 2. Once again, fork users are being called "so selfish"... The whole affair boils down to two things, basically: 3. MONEY ; the addons infra is being maintained fiscally out of M.A.T.'s own pocket; supposedly, "freeloaders" such as the fork-users put a significant extra burden towards bandwidth consumption/server costs... Edit: Fork users, when using the default Search Engine, DDG, also contribute towards the official project by Moonchild, do they not? 4. Branding (and all related stuff discussed extensively elsewhere in these forums). NB: The term "out of spite" is never mentioned ... I must thank @siria for being the first person in these forums mentioning in the past this HIDDEN Firefox pref When SSUAOs for the add-on repos stopped working for me, but I could still access them in my sister's Win7 laptop inside the same WLAN, I became sure I smelled of fish ... I arrived to the conclusion he must be checking OS version by Javascript, so I remembered that pref and applied it independently on my own; I did not disclose this early on, fearing the involved person's unpredictability... general.oscpu.override changes the Javascript-detected OS version globally; you can read more about it here . However, I wanted something more elegant, that would only work on these two "affected" sites; since I have Greasemonkey for Pale Moon installed, I concocted the following userscript: // ==UserScript== // @name Fake 'navigator.oscpu' on PM & Bk add-on repos (25-08-2020) // @namespace VistaLover // @description Changes 'navigator.oscpu' on PM & Bk add-on repos // @include https://addons.palemoon.org/* // @include https://addons.basilisk-browser.org/* // @run-at document-start // @grant none // @version 1 // ==/UserScript== Object.defineProperty(navigator, 'oscpu', { value: 'Windows NT 6.3' }); Sharing it now for purely academic reasons, just in case... BTW, navigator.oscpu is a feature of only Firefox and friends, Chromium-based browsers don't (easily) divulge the OS version when queried by JS... So, one major crisis averted, I'm sure there'll be more coming...

It does not. MS never bothered to port DiagTrack to NT 6.0.

Ugh, now I feel even older. But aside from that, it's a weird coincidence but I had just been attempting to pick back up my 95 slipstream project from where it got left 4 years ago for various reasons. Never realized the significance of the date.. but it seems fitting now. I remember my second computer, a Windows 95 OSR2 machine circa 1997. I'd had an earlier DOS6/Win 3.1 system before, but the new Windows 95 machine was there when I first discovered the Internet and online gaming. When it died on me a few years later in high school it caused me to have to learn more about building computers and setting up software.. and forever put me on the path, lol. Also enjoyed your story about issues with 98 that didn't exist on 95 - 98FE was garbage. A friend of mine had a computer with virtually identical specs to my 95 OSR2 machine that came with 98FE. He was constantly battling weird problems that I never encountered. Eventually later on I had to use 98FE on a system for a while, and I experienced several flaky issues that didn't happen under 95 (or 98SE). At one point I decided I wanted a CD burner.. thought I would get one of those new fangled external ones. Went to Office Depot and bought a HP USB burner, since my machine was HP and had a USB port. When I got home and figured out that it would not work with Windows 95, I took it back to exchange it for a different model/brand that connected via parallel port. The guy at Office Depot acted like I was crazy, and kept asking "Why don't you upgrade your operating system?!?!?" The parallel burner worked very well.. still have it, but haven't used it in ages. Eventually I went on to build a new system, with a 3.06GHz P4 processor. My beloved 95 crashed, and I couldn't figure it out at the time. Had to move to 98SE. Years later here I would discover the solution through trial and error installing any and all updates I could lay my hands on until it suddenly worked. And, total vindication at last. With @rloew's help, eventually helped to create a USB Storage driver for 95 that would run that d@mn HP burner.. if I still had it!

Despite your arrogant attitude I have to say the UXP browser is very nice and so I guess we can separate the harsh personality (and that's putting it mildly) from the work. I finally got a newer model with much better processing and more ram and it blows me away how much better this is. On XP it is screaming fast, very impressive.

MT: Well possible some of us are not the brightest here when it comes to computer science, but the fault for this misunderstanding here is your's. Not indicating what you're talking about exactly, using dev-speak, and clearly talking to RT in first post. Especially not bothering to mention to normal users who are not clairvoyant that "ShellService" might have anything to do with "Set Default Browser". That's absolutely not obvious, just a chance for blind guessing. Then again, it probably was your intention, to get more opportunities for jerking around. RainyShadow said: > As a last resort, you can try to use Control Panel > Folder Options > File Types > and manually change the assotiations. When using that method, this great little tool is an easier alternative: https://www.nirsoft.net/utils/file_types_manager.html One possibility for example is to open it and search inside where the current default "iceape" is used, then copy those lines for another browser. Am no expert for that stuff either, but guess at least four entries should be set: For ".html" and ".htm" and "http" and "https"

Wouldn't the OS-level SHA-2 support be sufficient? And which Rust are you talking about? The programming language upon which newer Firefoxes are built, or the game? I'm trying. I'd really love to have Vista running stable on my Kaby Lake laptop as well. 2012R2 looks like Windows 1, and having Vista's UI would be a major improvement (I'm also going to work on getting graphics drivers like my Intel HD 620 ones working too). I had previously narrowed it down to the function LoadLibraryExW, and I recently installed Windows 7 build 6519 which has a very similar version of the function, and also doesn't have those bugs. But simply transplanting the function failed, as it resulted in a BSOD where "the system couldn't find the file specified (@98w9asoise590dj.dll [or similar nonsense file name])". But after trying a few more things, I think I've narrowed down the problems to one particular part of the function. But making a good patch will be very challenging. What also doesn't help is that this laptop has broken hinges, so I can't bring it to where I am half of the time.

yeah, thats not the same as right click -> page info -> permissions which has no problem. anyway, this is fixed in repo and next build should have this fix applied.

... and, then, some!

Plenty of other people thought exactly the same! https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-2004-optimizationdefrag-bug/4c5498b9-04fe-41c9-8535-ed10313b6f33 This is off-topic of course, in this forum section, letalone this thread, but what was really bad is that they apparently acknowledged and fixed the issue in an insider build, but then still let the fault get through to the release version of Windows 10 2004! What was really bad was not so much that the automatic optimisation of drives was not having its status remembered so it was running unnecessarily, but it was that it was also misidentifying drive types, resulting in it trying to TRIM conventional hard drives (impossible) and actually defragmenting SSD drives, which is definitely a no-no! It's fixed now anyway, but I do wonder how many people had the lives of their SSD drives unnecessarily shortened by this.

I saw that coming... While I do respect Pale Moon and its developers for maintaining possibly one of the last independent web browsers around (enough to have gifted the x64 versions of 28/likely 29 to Vista), I will also wear the Browser badge with pride. Most people use a webpage viewing application covered in Chrome, a few stragglers need an Explorer to guide them through the Internet, others live on the Edge, and some like roasted fox. But Browser is where I stand. It's just like the "no name" grocery brand, which does quite well here in Canada.

@Vistapocalypse : A teaser/taster for now:

Thunderbird 52.9.1 cannot work because the Yahoo + OAuth2 code was entered by Thunderbird 60. Also interesting is the use of the new version 5 of POP Peeper (email notifier) which allows OAuth2 authentication with your default browser. Pop Peeper 4.5.3 work with I.E.8. Yahoo authentication was possible. Because the Yahoo Mail web page can be reached with I.E.8. But other OAuth2 authentications, such as Gmail, are impossible because they don't work with I.E.8.

@roytam1 FYI: The new sept. 12 version of IceApe-uxp does not work on my two systems (XP and Win7) and return the dialog "Couldn´t load XPCom". Thank you for your hard work Edit: in the IceApe-uxp sept. 12 zip archive mozsqlite3.dll is missing. If copying the missing dll from a previous version into the iceape-uxp folder all works well

Microsoft cut a few days (or hours) ago I don't know precisely, the self-update of windows update agent. This means that WUMT will display "class not registered" until we manually update the agent. It's really the end this time. Fortunately, I found version 7.4.7600.226 as standalone package : https://support.microsoft.com/en-us/help/946928/information-for-network-administrators-about-how-to-obtain-the-latest As indicated, there is no standalone package for version 7.6.7600.256 but 7.4 works well.

hard to tell. the changes between 20181222-ba81aaf07-xpmod and 20181229-83cd9661c-xpmod are minor: https://github.com/MoonchildProductions/UXP/compare/ba81aaf07...83cd9661c unless it is AV1 content (which is unlikely since AV1 decoding is super-heavy) since there was an update between these builds. not possible, because ffmpeg 3.4 knows only software decoding.

I have resigned myself to declaring that ntdll on Vista and up is indeed off limits. I again went to XP x64 for some inspiration and installed (Vista-compatible) Blender 2.90 on it. Several functions were missing like InitializeCriticalSectionEx. That function imports RtlInitializeCriticalSectionEx from ntdll, which also was introduced in Vista. So that requires doing the near-impossible, import table expansion. Then I looked at One-Core-API. As @Ximonite pointed out, ntext helps extend ntdll. ntext is a layer between kernel32 and ntdll, and most of ntext is imports and forwards respectively from/to ntdll. No new imports unless we make our own binaries, but forwards are indeed exports from the file. The people designing the PE format certainly had some nice tricks up their sleeves! Though I was forwarding functions to ntdll from kernel32 in Windows 2000 back in June, so my memory is going I guess. So this ntext would be a copy of ntdll with new and upgraded functions. But what about programs that call ntdll directly (which is frowned upon for win32 applications as kernel32 is what they're supposed to call as an intermediary)? A patcher that changes import table references from ntdll to ntext in a particular program is needed. Preferably, I'd like to make the file that ntoskrnl loads and is integrity-checked a decoy named ntext (which would be the original ntdll), while everything else calls a modified ntdll (so no changes to import tables are necessary). But changing the reference to ntdll I found in ntoskrnl did nothing.

there is no "release" schedule since all "releases" are just actually "pre-release". and no, I don't want to make any point-release builds for continuing develop product. 45ESR builds are different as upstream only drops few commits per month for bug-fixing.

Nope, it needs functions in user32: SetGestureConfig, CloseGestureInfoHandle and GetGestureInfo. I have an extended x86 user32 somewhere but I don't have it here with me. Though it doesn't rely much on the outmoded ntdll functions so I think a release is in order soon. And it's hard to force an install using Application Verifier, as you need to trick the temp file it creates (seemingly), and its name changes every time it's created. But even a x86 kernel32 with a borked VerifyVersionInfoW changes nothing.

the patch seems to be applicable, lets see if it will work or not in next build

Serpant55 is actually kind-of Firefox 53/54-ish thingy. upstream ported some features from Firefox 55 alpha and tell people that's 55-based.

The first beta 13 version, based on 86 Chrome, periodically crashes, but in general it is more stable than the first beta 12 versions. Those wishing to test, Russian assembly from Cento8 (many additions have been added, for some reason obsolete): https://www.upload.ee/files/12191126/360Chrome_13.0.1000.7z

A good way for a Vista user using the Security Monthly Quality Rollups to determine whether they have telemetry, is to run netstat -b in Command Prompt/PowerShell as administrator with no programs running (especially web browsers). You get a few hits on a standard Windows 10 and Windows 7/8.x with telemetry, but not on Windows 7 without telemetry updates as well as Windows 10 LTSC with services like Diagnostic Policy Service disabled (in the latter case, simplewall may have been running with many system components blocked from making connections, but I don't remember).

@Matt A. Tobin Nobody is required to know everything about the crap some self-important jerk is doing over the internet. Now, would you, please, remove yourself from here until you fix your attitude! @TechnoRelic As a last resort, you can try to use Control Panel > Folder Options > File Types and manually change the assotiations. No clue if it will work though, if the stupid browser is broken, As a quick test try dragging a .html file over to bnavigator.exe and select "Open with".

There are two main schools of thought on the matter. 1) The one I follow (which is objectively more complex to realize) is that first thing "boot" and "system" volumes must be separated, in the case of a Windows NT OS, installing it in a volume inside Extended, and in a multiboot scenario a volume must have a same drive letter assigned in each and every OS that accesses it AND that all volumes should be accessible from all OSes installed. The caveat is that more than a few (poorly conceived) programs will insist on installing (or however using files) on C:\, and in some cases they are a nuisance, on the other hand a (very stupid) malware virus hardcoded with C: or blindly wiping the active partition in the MBR will be able to make much less damage. 2) Alternatively, nothing prevents you from having completely separated installs, with the partition(s)/volume(s) of the "other" OS hidden from the "current" one. This gives a number of advantages, i.e. the install of each OS will be more "standard" so you won't have any issue with programs hardcoded for C:. Both are valid approaches, what I recommend in the second is to NOT have normally the "other" drive/volume visible, the idea is that before or later one is booted in the "other" OS and makes something destructive on the "wrong" volume because of a same volume having different drive letters under different OS. Of course, even in this second situation, the "other" drive/volume in a dual boot can be made visible - in case of need - to repair/fix the "other" OS. Example for #1: 1) small, FAT32 partition primary active drive letter C: 2) NTFS volume (logical volume inside Extended) Vista drive letter D: 3) NTFS volume (logical volume inside Extended) Windows 8.1 drive letter E: 4) NTFS volume (logical volume inside Extended) Common Data/Storage drive letter F: Example for #2: 1) NTFS volume active[1] primary partition Vista drive letter C: (hidden when 8.1 is booted) 2) NTFS volume active[1] primary partition 8.1 drive letter C: (hidden when Vista is booted) 3) NTFS volume primary partition or logical volume inside Extended Common Data/Storage drive letter D: from BOTH OSes 1st example for a "mixed mode": 1) small, FAT32 partition primary active drive letter C: 2) NTFS volume primary partition or logical volume inside Extended Vista drive letter D: (hidden when 8.1 is booted) 3) NTFS volume primary partition or logical volume inside Extended 8.1 drive letter D: (hidden when Vista is booted) 4) NTFS volume primary partition or logical volume inside Extended Common Data/Storage drive letter E: from BOTH OSes Of course there are other possible setups, including having the small FAT32 partition have not a drive letter assigned normally, which is what more or less is already happening on UEFI/GPT disks, i.e.: 2nd example for a "mixed mode": 1) small, FAT32 partition primary active no drive letter assigned 2) NTFS volume primary partition or logical volume inside Extended Vista drive letter C: (hidden when 8.1 is booted) 3) NTFS volume primary partition or logical volume inside Extended 8.1 drive letter C: (hidden when Vista is booted) 4) NTFS volume primary partition or logical volume inside Extended Common Data/Storage drive letter D: from BOTH OSes jaclaz [1] this approach needs a bootmanager capable of changing the active status of the partition and hide the "other" one at boot time

Is it me, or lots of people think that WiFi == Internet?

@bigmuscle Yes, please consider this for the future development of Aero Glass. If you want to keep it paid, at least provide a bit more communication.