Leaderboard

I understand where you're coming from with that, however I certainly don't believe it's too much to ask for them to keep their "unsolicited opinions" to themselves. I don't care if they "disapprove" or "dislike" what we're doing, I know they don't approve and I didn't ask them to agree with it. I only ask that they stop "disparaging" us with it. This is how "diplomacy" works. If they expect us to do something that they demand, then they can show good faith by ceasing their constant attacks. And, I hate to say it, but they have no right whatsoever to insinuate that someone is "stealing" code; that's not how "Open Source" works. If that is their attitude, then they're nothing but a bunch of hypocrites, because they owe their entire existence to Mozilla and Firefox, from which they "stole" code to begin with. If they want the "right" to claim people are "stealing" code, then let them go and start from scratch and build a closed-source copy of what they have now. I would estimate they might be back up and running in five years or so, if they're lucky... That is Mr. Tobin's interpretation of the licensing. That doesn't necessarily make it the correct, or most accepted interpretation. You will recall that I disagreed with him on this previously, and he had no direct response to the points that I made. It would be pretty senseless to be able to obtain source code that could not be "built" - this, to me, is a perfect example of "attempting to limit the user's rights in the Source Code" which the MPL prohibits, as I listed before. Based on previous behavior, which I also provided links to, it seems to me that Mr. Tobin and company prefer to just go around making threats and creating a toxic atmosphere for those whom they don't like building their code, hoping that they can "scare off" or bluff them all into submission, because whoever they're targeting simply doesn't want to deal with their constant attacks. Oh no, I have absolutely no intention of beating that dead horse again. It is dead, and should remain dead. The issues of licensing are wholly independent from the "rebranding" discussion. I knew that, however these "ramifications" (read "threats") or whether they can be enforced or not come down to licensing. I covered that specific aspect in my other post. You did ask for other input...

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)

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).

Hope you feel better soon , the other things can wait

I tracked down the Perl script that effectively automates the process of making wrapper DLLs, especially for DLLs like ntdll which exports over 1800 functions: http://web.archive.org/web/20070526114542/http://www.craigheffner.com/security/linkout.txt This will prove essential for Vista and any future work for 7. And maybe even more so for 8.x and 10. Though ActivePerl 5.26's installer errored out with this: (0x80004005) the specified application is not a valid application for this OS platform. Indeed, Windows Installer definitely knows it's "running" on 6.1.7601 SP1 based on the error log. I found the executable for the "state tool" and it had a subsystem version of 6.1, so that may have been the reason for the error, so perhaps I will follow BWC and disable the subsystem version testing like he did, after all (which will only work with system32 file replacement). And just use Strawberry Perl anyway; it seems to work far better with Vista. On another note, it appears that a new hack in my ntoskrnl (not released yet) to prevent it from changing CurrentVersion from NT 6.1 to 6.0 in the registry has fixed some OS functionality. When I added CoGetApartmentType to ole32.dll, I could no longer modify Sidebar widgets nor open folders with downloaded files through browsers. But I can do that with my modified ole32 once CurrentVersion is changed permanently. But not everything thinks it's on NT 6.1 yet (like RtlGetVersion), which is still a big problem that no one has solved since it arose in 2005. Windows compatibility mode will not solve it.

... 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!

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.

That's the problem: I wasn't stating my preference... what I was is called being ironic! Why is it almost no folks nowadays are able to even detect irony? And no, please, don't answer the above question: it's just a rethorical question. Now, what is literal is that the next post about renaming @roytam1's forked browsers in this will be deleted. That's way off-topic and totally pointless nowadays. So, please, stop. Do stop. Resist useless posting.

IIRR, @glnz actually *IS* a lawyer, so I'm hereby asking him to ping in and kindly provide us some advice, which sure'll be much appreciated!

Let me begin by thanking you for continuing to deliver updated builds of your browsers, despite the recent major hardware hardships... (pun intended! ) Starting with last weekend's New Moon 28 package (linked-to above) and including this weekend's latest NM28 offering, I've noticed that 3 compiled files, all previously associated with Serpent 52.9.0 builds, have somehow slipped into New Moon's main app directory; these files are: Accessible.tlb AccessibleMarshal.dll IA2Marshal.dll I browsed quickly your custom UXP branch and did not find any clues there as to why these 3 files now appear inside NM28's main appdir ; if it's any info, these 3 files also do not appear inside upstream official compilations of Pale Moon 28.13.0/29.0.0a6; but since our fork has deviated somewhat from upstream, that fact may or may not be relevant... Mentioned files, as pretty much expected, continue to reside inside Serpent 52.9.0's main appdir (as well as in upstream official Basilisk 52.9.2020.09.11 ) Now, as a test, I went along and deleted those 3 "errant" files and latest New Moon 28.10.2a1 32-bit (buildID=20200918232718) launches and runs fine here (Vista SP2 32-bit, build 6.0..6003) without them... It looks as if those files are generated via a first stage Serpent/UXP compilation and are then added, by mistake, with other compiled files that are common/shared with the New Moon 28/UXP compile/build (possibly to expedite compilation of both UXP browsers...); if that's by design (and may I note that this wasn't the case with the previous [now lost] building environment), perhaps it would be best to remove those 3 unneeded (for NM28) files post compilation and prior to packaging/uploading... https://github.com/MoonchildProductions/UXP/issues/1653 Clean up Windows widget code https://github.com/MoonchildProductions/UXP/commit/6f5cd8a [widget] Clean up Windows widget code some. Can you please elaborate a bit why upstream UXP#1653 was not merged? Would it have broken WinXP compatibility if it had? Being on Vista here (NT 6.0), could this have been handled slightly differently if it provides performance improvements on Vista+? (e.g. ifdef'd to load the code under Vista+ but not under XP?) Apologies if I'm asking something that can't be done... I'm really sorry to have to bring this up, but don't you expect "upstream" to hear about that? You are, at the end of the day, still building "unofficial" Pale Moon builds and upstream have modified that branding (which is their prerogative, it appears...). I won't pretend I understand fully the Open Source licensing schemes, but I smell (additional) trouble coming from upstream, this time from Moonchild himself With all said and done (and undone) in the past, I'd hate to witness any further escalation between "us" and "them", especially if it results in more restrictive action(s)/sanctions from upstream... What do others think on this? Finally, I don't use any of these forks myself, but out of pure (healthy) curiosity, what source do you actually use now to produce updated builds of? AFAIAA, upstream have moved to a private repository, so are you now just updating the platform (UXP) submodule/component, which is still public? Thanks for all your hard work and efforts , thanks in advance for any answers received... Best greetings

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200919-72c45cb-uxp-c1988898f-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200919-72c45cb-uxp-c1988898f-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-20200919-72c45cb-uxp-c1988898f-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-20200919-1c51f25e6-uxp-c1988898f-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20200919-1c51f25e6-uxp-c1988898f-xpmod.7z Official UXP changes since my last build: - Issue #1629 - Part 4: Ensure isExplicitlyEnabled is false upon sheet creation. (8f95bacca) - Issue #1629 - Part 5: Remove pointless local variables. (1f65f171a) - Issue #1280 - Remove hostname parameter to trust domain. (61ab2b98e) - Merge pull request #1648 from adeshkp/hpkp-hostname-cleanup (c779684b3) - Issue #1650 - Add null check. (9eb8b61b8) - Fix usage of a macro in a cocoa widget (#1649) (00e073391) - Merge pull request #1651 from athenian200/link_element_disabled (85f915543) - Issue #618 - Clear the module map - Debug Followup (766ceb5d9) - Merge pull request #1652 from g4jc/618 (71030ab33) - [widget] Clean up Windows widget code some. (6f5cd8a5e) - Issue #1643 - Part 1: Add GetNodeDepth() to nsContentUtils. (b4eda697c) - Issue #1643 - Part 2: Implement ResizeObserver API (1b7382416) - Issue #1643 - Part 3: Implement ResizeObserverController (a53a2a3a3) - Issue #1643 - Part 4: Hook up all the plumbing. (b6b868b1b) - Issue #1647 - Part 1: Implement percentage for CSS opacity keywords (51764ac72) - Issue #1653 - Part 1: Remove WinUtils::SHGetKnownFolderPath (8151bb2b0) - Issue #1653 - Part 2: Stop indirectly loading DWM functions through WinUtils. (a0cdf3287) - Issue #1647 - Part 2: Implement VARIANT_OPACITY to correctly serialize. (b5c9f8e24) - Issue #1224 - Remove constant expressions from /dom (6be15b96a) - Merge pull request #1654 from athenian200/opacity_percentage (c1988898f) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - [minor] spelling correction in a code comment (82285f8db) - Merge pull request #1836 from adeshkp/patch-6 (97c753619) - Update branding. (54aeb5482) - Restore DS store file required for Mac builds. (8a211f630) - Merge pull request #1837 from adeshkp/dsstore-mac-build (54084d6b3) - Fix vendor name in about dialog for unofficial builds. (695be0bac) - Merge pull request #1838 from adeshkp/unofficial-vendor-name (dbcb9cea4) - Back-end branch pointer update (unstable 2020-09-17) (1c51f25e6) My changes since last build: - skipped Issue #1653, rev 6f5cd8a5e and branding related commits - partly import change from tenfourfox: - #618: EV now from ESR78, update TLDs, pins, HSTS (cb0f39c2f) (48b96210d) - import change from tenfourfox: - fix overzealous assertion (M1531906) (af9a8236e) (1455a4fcb) - import certdata changes from NSS upstream: - Bug 1651211 - Remove EE Certification Centre Root CA root cert. r=KathleenWilson,jcj - Bug 1653092 - Disable server trust bit for OISTE WISeKey Global Root GA CA root cert. r=KathleenWilson,jcj - Bug 1656077 - Remove Taiwan Government Root Certification Authority root cert. r=KathleenWilson,jcj - Bug 1663049 - Add SecureTrust's Trustwave Global root certificates to NSS. r=KathleenWilson,jcj - Bug 1663049 - September 2020 batch of root changes, NSS_BUILTINS_LIBRARY_VERSION 2.44. r=jcj (06a2891ef) - fix error flow in preferences (5f548d297) - partly import changes from tenfourfox: - #622: M1660537 M1641487(modified) M1645492 (291688840) (64ccce7c2) - import changes from tenfourfox: - #622: update brotli to 1.0.9, woff2 to tip (7c24b77e7) - #622: actually add new brotli files (fc50954e6) (1bdcd4697)

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

OK so, in addition to MPC-HC and Pot Player via 3DYD YTS I am now also able to stream YouTube videos without 3DYD in older versions of MPV, VLC, Osmo4 (GPAC), QMPlay2 and current/latest Mplayer Sherpya build from right click in both Opera 12 and Gecko Browsers. I've also made a quite fancy and useful GUI for Youtube-dl as it turned out I couldn't find any working properly on 9x (not any good one anyway). Coming soon, probably next week, as part of the Youtube-dl 4 98SE-ME Megapack (500MB). Screenies of the GUI for now:

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.

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.

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.

Firefox 52 shipped with TLS 1.2 default with optional Draft 18 spec TLS 1.3 support. Even 52.9.0 ESR still only supports up to Draft 18 TLS 1.3. The first UXP browsers to support the RFC 8446 TLS 1.3 spec (final) by default are: Mypal 28.3.1 (Feodor2) Centaury 0.0.3 (Feodor2) New Moon 28.3.0a1 (2018-12-21) (RoyTam1) Serpent 2018.12.21 (RoyTam1)

I'll remind people here that I'm not actually an authority on Google Chrome and Chromium derived browsers, having been from the very start a Mozilla Firefox user, first (2005-2008) on a WinXP desktop and then (2008-2018?) on this Vista laptop... This is to clarify that I haven't followed closely Chromium's development during that era... I've learned quite a few things from XP users of Chrome 49, and it's true that specific [old] version (officially the EoS one for XP/Vista) does rely on OS resources/libraries for secure connections (which involve both available TLS protocols and available cypher suites). Contrary to what Google (the No.1 enemy of the Vista OS, by far ) believed, WinVista != WinXP, so having a fully updated Vista SP2 OS with TLS 1.2 support will grant you more accessible websites using Chrome 49 on Vista, thanks to Vista supporting more cypher suites by default and, on top of that, having SNI support that WinXP lacks... But all this is probably a moot point already, because Chrome 49's rendering engine is antiquated by now... To conclude, yes, Chromium 49 can only go up-to TLS v1.2 on an updated Vista system (with KBs targeting WS2008 originally ) At some point further down its development, Chromium disengaged to a degree from OS libs where TLS support is concerned, so that Chromium 57/58, upon which Yandex Browser (YB) 17.4/17.6 builds, comes with bundled/native support for the TLS protocol. I haven't used YB 17.6 (portable) here for many months, having long ago switched, first to 360EE v11 (Chromium 69 based), then to 360EE v12 (Chromium 78 based) and currently testing (beta channel of) 360EE v13 (Chromium 86 based). YB 17.x has other significant shortcomings by now, affecting Google Web Store (GWS) support , but that is part of a future post about YB 17.x ... By default, YB 17.6 supports TLS 1.0+1.1+1.2, provided by its own (Chromium) libs (i.e. non-dependent on OS TLS support, kinda like Firefox); but there is latent TLS 1.3 support, too, which can be enabled via a browser flag; The problem is that YB 17.6 was released at a time when TLS 1.3 hadn't been finalised yet, so it only supports a TLS 1.3 draft preceding the final one (i.e. RFC8446) Testing on dedicated TLS testing sites you get mixed results, depending on whether the test site detects pre-final TLS 1.3 drafts or not; SSL Labs client test picks up pre-final TLS 1.3: ... but Browserleaks ... and pinterjann DO NOT! As a closing note, if you want to disable lower, deemed currently insecure, versions of TLS, you can launch YB via a shortcut containing the following flag: --ssl-version-min=tls1.2 or --ssl-version-min=tls1.1 if you want to disable just TLS 1.0 ...

Well, technically we aren't using their branding anymore since they just abandoned what we're using now. We now have a different product to theirs with different branding, which is most of what they wanted. Though there may still be some sort of trademark attached to their old branding. And Serpent isn't resolved though I don't think they are too pleased about us brand leeches either way (either we piggyback on their current unofficial branding or simply seize/gift ourselves their old branding). And New Moon could still evoke memories of Pale Moon (for an unfortunate few anyway).

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.

Yes, in fact here is screenshot for proof https://ibb.co/kMh6cpw

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.

A small update on the repository. Thanks to the efforts of @Regele there are now EN-US version of IE9 and KB937286. I've also change the folders names in the Ultimate Extras to English.

Just finished testing my fully updated install of Vista Ultimate x64, including build 6003 updates from Aug 2020: It seems that Microsoft fixed the timer issue, as seen above. Unfortunately, there are still random issues, specially with UAC prompts: permissions are not properly granted. Even so, it's clearly much more stable.

Microsoft Update and Windows Update no longer work on XP or Vista. It is the SHA-2 problem. I can still connect to the MS Update website, but it immediately fails when scanning starts.

Patch applied. It works. @roytam1 Thank you very much!

I discovered that I was unable to load ntoskrnl even if I replaced the MS signature with a custom one. This method is used in a tutorial to reinstate proper PAE support in Vista x86. I think bootmgr needs to be modified as well in order for it to work. But I've had a few other things happen in my life lately (for example, right now, most sounds, sound warped to me) so I haven't been able to do as much as I've wanted to do so. And then I'm still trying to work out ntdll and LoadLibraryExW.

Only for the record : https://quoteinvestigator.com/2013/10/20/no-predict/ jaclaz

While I don't like the tone he took here at all and think there's no excuse for it, I kinda feel like I have to point out... he probably views himself as an artist. I had an artist lady named Lambda or something (not here, somewhere else) once get really angry at me because I just changed the colors on a logo she provided as a logo candidate for my website rather than asking her to do it. I thought I was just saving her some hassle, but she took it as an insult to her work and started talking about me behind my back and giving me the silent treatment. That's how I learned that artists can be very possessive of their work and not like others changing it without permission or anything they perceive to be a mockery of it. The original browser is named Borealis Navigator, so the new branding being "BNavigator," is, well... it's like saying "PMoon," "SMonkey," or "WFox," isn't it? Combine that with the fact that it's in perpetual beta, he isn't even providing builds of Borealis himself yet, and it's easy to see how, as an artist, he might feel like someone took an unfinished painting of his and did something with it that made him uncomfortable. Like how I made that lady uncomfortable when I modified the color scheme of a logo candidate she gave me, thinking I was saving her some work. In fairness to you though, I think the official branding directories probably should have been closed source (or a least in a separate repository to the open source portions of the program) to begin with if that was the way he felt about it. I mean, I get that to a lot of people this is just code, and the whole spirit of open source means sharing and decentralization, but if someone views a part of that as their own artwork and they take it seriously in that regard, well... I can see how they might feel mocked or bothered by such a name, and I can also see how they might feel a bit like the way an artist might feel upon seeing a cheap, slightly modified reproduction of an unfinished painting of theirs that somehow leaked out becoming semi-popular. At the same time, I can understand how using a name that's similar like that would feel like a way of honoring the original or the artist to the person who did it, and that that person might feel confused as to why the artist isn't flattered by it. But yeah, that's just my two cents on the subject of why people might not like that, and why the creativity and branding aspect of it might be so important to someone.

I can't believe it's been so long since the most logical desktop UI was released. Windows NT API functions + DOS/win16 compatibility, FAT32 and basic USB support are pretty important as well. I started using Windows 98 long before I started with 95, but when I got my PIII machine, 98 was flaky beyond belief. I asked for opinions and some said that the near constant crashes were due to overheating. Then I went outside the next day. A razor-thin object hit my forehead and cut it. Turned out to be a Windows 95 OSR 2.1 CD-ROM. Used my 98FE OEM CD-ROM to boot it. And it installed with no issues. So those crashes were likely not related to hardware. My only problem was that the system would fail to boot or even be broken completely if the USB supplement was installed. But replacing the S3 Savage4 with a GeForce FX 5700 LE fixed it. I'm still quite satisfied with Windows 95, After Dark 10th anniversary edition, Office 2000 Professional and RetroZilla 2.2 (until MSFN broke in it earlier this morning due to apparent change in encryption. nice coincidence. ). I never, ever swap with 128 MB of RAM! I'd love to go back 15 or 20 years so I could run 95/98 as a main OS dual booting with Windows 2000 and not have to worry about compatibility issues. Seriously, since I dumped the Savage4, win95 has never given a BSoD or even inexplicable crashes of system executables (98SE did that to me often).

I don't quite understand the necessity for connecting to a site such as Wikipedia securely at all, this is just a free online encyclopedia, not a bank or a shop, these people have lost their mind completely...