Leaderboard

LOL, couldn't help drafting such a disclaimer novel ;-P "For any help, support and discussion of roytam1 browsers, the best place is here: (link to NewMoon topic in msfn) Attention: Do not under any circumstances bother the PaleMoon team, especially Moonchild and Matt A. Tobin, with anything related to this forked browser, to anything XP-related, or mention any of roytam1 browser builds in the Pale Moon forum. They intentionally removed all XP-support for their products a long time ago, and do NOT tolerate any longer to be bothered by people using forked builds, especially not forks with restored XP support. Only discussion of their own original builds is allowed there. They have very STRICTLY declared this multiple times, in their own forum and also in the MSFN forum. So, please, abide by their request and go to MSFN only for support."

You actually expect anyone here to take you seriously while you continue to maintain a condescending attitude toward roytam1 and everyone else in this community? You can't even speak of these things without lacing it with some ignorant derogatory language or FUD. Emphasis mine. I assume once again that users are intended to believe that "poor modification" is an acceptable definition of "restoring the pre-existing functionality that you intentionally chose to break?" Not one of us here cares one iota whether or not roytam1 has some useless eye-candy website or some fancy branding for his browser builds. What we care about is that they work and that he is very responsive to bug reports and quick to address other issues that may arise on the target platform(s). Yourself and "Moonchild Productions" could do with some lessons from what you find here. When the rest of the world leaves your precious Windows 7 and your "outdated" Mozilla forks, along with their "outdated" addons behind, where will you be? In the same boat with the rest of us. If you expect anyone here to take you seriously, you'd better learn to treat people here with respect whether you agree with them or not.

So much for the "more constructive approach." I had a feeling this was insincere. roytam1 has no control over the actions of those who decide to use his XP-compatible builds. Even if he were to change names, remove references, yada yada yada. there could still be "ignorant" users (or even troublemakers just trolling) who will keep going to the wrong places for support or to ask questions. How hard is it to say "I don't support those builds" and link them here? Much easier than ranting there, ranting here, and rewriting a bunch of code.

Title says it all. Thx @bigmuscle - now many of us can now install and test v1903. Starting this new thread for feedback and bug reports...

I decided to create a new thread for those wanting to test the portable "Blink" version of Microsoft Edge. New portable builds of the Canary channel are being issued on the Upload.EE site, and I'm fetching those as they become available. N-Sane Forums are supplying the update links: https://www.nsaneforums.com/topic/341437-microsoft-edge-canary-channel-updates/ And here are the three latest releases: https://www.upload.ee/files/9839860/MSEdgePortable_75.0.132.0.paf.exe.html https://www.upload.ee/files/9844163/MSEdgePortable_75.0.133.0.paf.exe.html https://www.upload.ee/files/9872797/MSEdgePortable_75.0.140.0.paf.exe.html ***** A major credit goes to user @jeff69dini for getting this going. *****

Thanks, @siria; that's a good start. But let me flesh things out a bit: for FF/PM/NM/Basilisk/Serpent, the preconfigured SSUAOs are found in <browser installation folder>\browser\omni.ja\defaults\preferences\<browser>-branding.js. The precise path is important because these browsers include two omni.ja archives, each of which contain too many paths to manually search. The branding file for FF 52.9 contains no SSUAOs, of course, since SSUAOs are disabled by default in FF 52.9. Oddly, the branding file for Serpent 55 is named firefox-branding.js, not basilisk-branding.js. I guess MCP dropped the Moebius branch before they got around to renaming the files. As with FF 52.9, Serpent 55 comes with no preconfigured SSUAOs.

@Dave-H: Good to here your system is stable with the 16-bits HDA driver. I still have no definitive opinion regarding stability issues, but I will do thourough testing with Virtualbox, no real risks involved (thanks to UCyborg)... Working with an unknown system was stimulating, especially with such a careful tester. Gave me some new insights and idea's too. As a sort of spinoff from this project I made three quasi-universal versions of HDAICOUT.HDA. Instructions which one to choose inside. Especially useful if there is the Sound of Silence after installation of the driver. Hdaicout.hda.000 Hdaicout.hda.100 Hdaicout.hda.200

@hfuria: Please search with Google the full filename "DP_w98_1.01.exe" (including quotationmarks), etc.

Hi Roffen. Best? Uninstall Winzip. Windows can pack and unpack .zip files without any additional software. For other archive files, install 7-zip instead. Press start button. then, start typing "This PC", or Norwegian translation of this term. This PC icon should appear. Run it. It will open traditional Disks view, something like "My Computer" on Windows XP.

[click to open Chrome 360's website] To download it, just click the button in the middle of the page.

@DrWho3000: you need to add the full domain to the override pref name, incl. ".com" or whatever a domain ends with, not just the first part. Subdomains in the beginning can be omitted though, e.g. "www." As others have written many times above, in clear examples. SITE USERAGENTS in general There are several possibilities where they can be defined (just like any other pref too): 1) A bunch of predefined site-UAs in original browser builds come inside omni.ja. If unzipped can be discovered hiding in a giant melting pot file with almost 2000 default prefs. File name goanna.js, or greprefs.js, all.js etc, depending on the browser version. Update (thanks Mathwiz in next post): ...or in newer browsers in file (browser installation folder)\browser\omni.ja\defaults\preferences\(browsername)-branding.js - or not at all in omni.ja anymore. Those default prefs can also be viewed and customized on about:config, unless overruled by 2) to 4) Omni.js is by far the most user-hostile place :( But at least it has the lowest priority. The prob is that just about no user is aware where those mysterious default site-UAs are coming from, and especially how to get rid of them when later becoming outdated. Would be much easier on users if fork-builders would define all their predefined site-UAs instead in a separate file, in place 2: 2) The best possibility to define user friendly default prefs: written in any file in folder ...firefox.../browser/defaults/preferences/.....js That place makes them "default" values too, and has priority over 1) In very old browsers the path is ...firefox.../defaults/pref/....js For easy maintenance users can simply create a new file there themselves, e.g. called myuseragents.js 3) the normal way for users: define personally customized site-UAs in the profile folder. By manually adding them in about:config, or by using an extension. Adding or changing them in about:config will automatically store the new values in file prefs.js in the profile folder. (except if now matching the default value again, then the browser will delete them from the profile, but that's another story) 4) very unusual but possible: users can store any prefs that are important to them in the profile in user.js. That will make them "startup prefs". Those can be changed during a session in about:config, but at next browser start the value from user.js will be imported again. 5) If an Addon is used for managing useragents, most of those seem to store settings instead in their own ways, in files in the profile, overruling Mozilla's pref system. (Tip for K-Meleon users: my macro useragents2018 manages only the 'normal' mozilla prefs, like the old traditional KM macro too, and leaves the handling itself to the engine) That depends. Have examined exactly this prob last year, and find it a huge prob that predefined ones are tossed nearly inaccessible for users inside omni.ja :( Yes, right-clicking in about:config and resetting a pref to default will delete all custom values. If a site UA has no default value at all, it will be deleted as expected, and afterwards the general override UA can kick in again. Catch: but if a site-UA does have a default value, defined in 1) or 2), resetting it in about:config will only reset it to that value again. The trick is: do not reset, but instead set it to a completely empty string. Now the general UA seems to work again.

added

Okay so basically it is not very safe to use. That was expected... but is there a way to maybe look at the source code of the browser or something like that and recompile it so that it works with 2000/XP/Vista but this time with the original Chrome 69?

Certainly does. And this way, the portable version gives me a clean way to install Edge. I just extract the program folder in to Program Files and run it manually. It creates a large \users\local folder, but that's it. Easy to remove whenever I want. If anyone comes up with a way to move tabs below the address bar, please let me know. This may be a real possibility should Firefox ESR v68 not be to my liking.

thanks, I was going to do the same but you beat me to it, lol.... yup running very stable, gives new life to good ole 8 eh? :P

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190427-697f102-uxp-3424afcca-xpmod.7z Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190427-697f102-uxp-3424afcca-xpmod.7z source patch (excluding UXP): https://o.rths.cf/boc-uxp/boc-uxp-src-xpmod-20190223.7z Official repo changes since my last build: - [PLATFORM] Update commit pointer (4ceb85d) - [PLATFORM] Update commit pointer (cda8bd8) - [NAVIGATOR] Fix about:sessionrestore (837c77d) - [NAVIGATOR] Revert about:logopage (fa2551f) - [COMM] get*pref has defaults now, use it (6a812b8) - [PLATFORM] Update commit pointer (e744c6c) - [PLATFORM] Update commit pointer (3fd3eeb) - Issue #78 - Add signon.startup.prompt to avoid Master Password races (697f102) For UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190427-3424afcca-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190427-3424afcca-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a2.win32-git-20190427-3424afcca-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a2.win64-git-20190427-3424afcca-xpmod.7z Official repo changes since my last build: - Issue #991 Part 1: Pale Moon (9a37ab727) - Issue #991 Part 2: Basilisk (759132691) - Issue #991 Part 3: Devtools (609a7215e) - Issue #991 Part 4: Network and URILoader (c7796280a) - Issue #991 Part 5: DOM and layout (1d0af8b59) - Issue #991 Part 6: Services (2d3b7717a) - Issue #991 Part 7: Toolkit Components (714e9c907) - Issue #991 Part 8: Toolkit everything else (8757548a3) - Pref try/catch block fixup. Tag #991. (40fc72376) - Merge branch 'master' into default-pref (af7e140d4) - Remove unused try/catch block. Tag #991. (21b4cb27c) - Remove unused parameter from call (b73287811) - Stop building /accessible unified and fix deprot. (32577bdb3) - Merge pull request #1041 from Ascrod/default-pref (e0116ac2b) - Handle URL token in a closer way to the CSS3 spec (d9137b4b7) - Remove geo-specific search engine default preferences. Tag #245. (c78cd6fb9) - Remove geoip lookup for search engine defaults. Tag #245. (60e283715) - Remove browser.search.region usage. Tag #245. (a3a34dad1) - Merge pull request #1047 from JustOff/PR_css3_url_token (550d87388) - Version bump (bccf86a10) - Fix variable used before being declared in UpdateUtils.jsm (bca1943ca) - [PHOENIX] Fix missing default from lastSync in browser-syncui.js in Pale Moon and replace the tryblock in Basilisk (5d02c2207) - Remove SecurityUI telemetry. (b10712de8) - Issue #1049 - Show sync status via label of sync-button (ccd86d8c0) - Merge pull request #1045 from ThosRTanner/patch-1 (864f1cfdb) - Update platform version to reflect major changes in platform. (33ebc885e) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (1d7664d3a) - Update Twemoji Mozilla COLR font to 0.4.0 (TweMoji v11.4.0) (7d61305b0) - Merge pull request #1051 from adeshkp/remove-telemetry-security_ui (8bd7da130) - Merge pull request #1048 from Ascrod/geodefaults (228e55129) - Remove tests from search service (0c84220a4) - Sort out search service (63295d008) - Issue #1053 - Drop support Android and remove Fennec - Part 1a: Remove mobile/android (abe80cc31) - Issue #1053 - Drop support Android and remove Fennec - Part 1b: Remove MOZ_FENNEC (325b204d2) - [minor] Fix a variable name in Basilisk error page (2e781c998) - Add application ID and widget toolkit placeholders to UpdateUtils.jsm (cb5d20deb) - Don't use UpdateChannel.jsm in nsBlocklistService.js (a9ae19957) - Use UpdateUtils in GMPInstallManager.jsm (c11a0b276) - Remove UpdateChannel.jsm (9cf2c92c3) - [PALEMOON] Remove errent extensions.blocklist.* from shared branding prefs (e86f0e555) - Remove useless assert. Resolves #1055. (51af3decb) - Merge pull request #1054 from adeshkp/patch-11 (ace7f20fa) - Capture delayed events and cancel as necessary. (3424afcca) My changes since my last build: - nss: go back to 3.43 release (b314cfa40) - a11y: fix build (2faa94fa0) * since MCP deleted lots of files, this might affect Serpent's functionality of updating WE extension. please test and report if there is any irregularities.

New regular/weekly KM-Goanna release: https://o.rths.cf/kmeleon/KM76.2-Goanna-20190427.7z Changelog: in-tree changes: - MozUtils: JS::Evaluate() don't use `globalJSObject` anymore as bug 1097987 is landed in goanna3 side. (17c38519) - bump version to 76.2 since goanna API is changed due to landing of bug 1097987 (a844f112) Out-of-tree changes: * update Goanna3 to git b68d61fda..a09f31062: - import change from rmottola/Arctic-Fox: - Bug 1097987 part 1. Change some JS shell function signatures to make it clearer that they are always working with globals, not arbitrary objects. (5f45873a2) - Bug 1097987 part 2. Change JS shell's Run to always compile/execute the script in global scope instead of using its this object. (807880f9e) - Bug 1097987 part 3. Change XPCShellEnvironment to only use JS_ExecuteScript in global scopes. (7cffe2855) - Bug 1097987 part 4. Change mozJSSubScriptLoader to use the scopechain version of JS_ExecuteScript as needed. (3abe5d5c9) - Bug 1097987 part 5. Change XPCShellImpl to use the scopechain version of JS_ExecuteScript as needed. (4642566c3) - Bug 1097987 part 6. Require callers of JS_ExecuteScript to either use the global as the scope or pass in an explicit scopechain. (c4a2a811f) - Bug 1097987 part 7. Require callers of JS::Evaluate to either use the global as the scope or pass in an explicit scopechain. (694c09eb3) - Bug 1143793 part 1. Remove the obj argument of JS_CompileScript. (929d8fd58) - Bug 1143793 part 2. Remove the obj argument of JS_CompileUCScript. (9c577f67c) - Bug 1143793 part 3. Stop passing null as the obj argument of JS::Compile. (86a715f63) - Bug 1143793 part 4. Stop supporting load.call(somerandomobj) in xpcshell. r=bholley (ed2bc21b4) - Bug 1143793 part 5. Release-assert that a script being executed against a non-global scopechain is not compileAndGo. (bcb9ae600) - Bug 1143793 part 6. Drop the obj argument of JS::Compile. This is technically a behavior change for the shell's disfile() function, but I really doubt anyone is doing disfile.call(someObj). (5f99a59bd) - pointer style (c02ff21de) - Bug 1135039: Apply swizzle type policy changes in Ion too (effc49369) - pointer style again (b47813875) (95ffc37ba) - nss: go back to 3.43 release (a09a17de6) - import change from rmottola/Arctic-Fox: - Bug 1128076 - Clean up naming around unboxed scalar MIR accesses (08ee23875) - more pointer style (f20c11717) - Bug 1139152 - IonMonkey: Add dynamic output type checks for LIRs that use redefine (286e5a552) - Bug 1135039: Throw on non-int32 or out-of-bounds lanes arguments to swizzle/shuffle (4a5e7078e) - Bug 1135039: Implement LVariadicInstruction (112d6f02c) - Bug 1135039: Generalize swizzle MIR node to SimdGeneralShuffle (076f75d26) - Bug 1135039: Generalize SimdGeneralShuffle codegen (e3deae006) - more style (23944c5fd) - Bug 1135039: Factor out LInstructionHelper/LVariadicInstruction code (e02b132ad) - update pointer style... (db3f11786) - Bug 1135042: Optimize SIMD.loadX/loadXY/loadXYZ in Ion (013bc896e) (a09f31062) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190427-a09f31062-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190427-a09f31062-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190427-a09f31062-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190427-a09f31062-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - Bug 1097987 part 1. Change some JS shell function signatures to make it clearer that they are always working with globals, not arbitrary objects. (5f45873a2) - Bug 1097987 part 2. Change JS shell's Run to always compile/execute the script in global scope instead of using its this object. (807880f9e) - Bug 1097987 part 3. Change XPCShellEnvironment to only use JS_ExecuteScript in global scopes. (7cffe2855) - Bug 1097987 part 4. Change mozJSSubScriptLoader to use the scopechain version of JS_ExecuteScript as needed. (3abe5d5c9) - Bug 1097987 part 5. Change XPCShellImpl to use the scopechain version of JS_ExecuteScript as needed. (4642566c3) - Bug 1097987 part 6. Require callers of JS_ExecuteScript to either use the global as the scope or pass in an explicit scopechain. (c4a2a811f) - Bug 1097987 part 7. Require callers of JS::Evaluate to either use the global as the scope or pass in an explicit scopechain. (694c09eb3) - Bug 1143793 part 1. Remove the obj argument of JS_CompileScript. (929d8fd58) - Bug 1143793 part 2. Remove the obj argument of JS_CompileUCScript. (9c577f67c) - Bug 1143793 part 3. Stop passing null as the obj argument of JS::Compile. (86a715f63) - Bug 1143793 part 4. Stop supporting load.call(somerandomobj) in xpcshell. r=bholley (ed2bc21b4) - Bug 1143793 part 5. Release-assert that a script being executed against a non-global scopechain is not compileAndGo. (bcb9ae600) - Bug 1143793 part 6. Drop the obj argument of JS::Compile. This is technically a behavior change for the shell's disfile() function, but I really doubt anyone is doing disfile.call(someObj). (5f99a59bd) - pointer style (c02ff21de) - Bug 1135039: Apply swizzle type policy changes in Ion too (effc49369) - pointer style again (b47813875) (95ffc37ba) - nss: go back to 3.43 release (a09a17de6) - import change from rmottola/Arctic-Fox: - Bug 1128076 - Clean up naming around unboxed scalar MIR accesses (08ee23875) - more pointer style (f20c11717) - Bug 1139152 - IonMonkey: Add dynamic output type checks for LIRs that use redefine (286e5a552) - Bug 1135039: Throw on non-int32 or out-of-bounds lanes arguments to swizzle/shuffle (4a5e7078e) - Bug 1135039: Implement LVariadicInstruction (112d6f02c) - Bug 1135039: Generalize swizzle MIR node to SimdGeneralShuffle (076f75d26) - Bug 1135039: Generalize SimdGeneralShuffle codegen (e3deae006) - more style (23944c5fd) - Bug 1135039: Factor out LInstructionHelper/LVariadicInstruction code (e02b132ad) - update pointer style... (db3f11786) - Bug 1135042: Optimize SIMD.loadX/loadXY/loadXYZ in Ion (013bc896e) (a09f31062)

I quote myself to give you a little update. It may look like as if we are doing nothing, but we're not. @someguy25 asked me about Chromium 74 and since I really love Chromium, we re-forked it once again and I tried to backport for the 5th time. Compiling it using v141_xp and targeting XP leads to nowhere as the new SDK does not compile, however commenting out the sandbox and some other parts of the code made it compile, however the code was unusable as 27 calls were missing (including - but not limited to - the kernel). By removing many unnecessary components and taking it to its very bone, I managed to lower the number down and by linking it to the @Dibya modified kernel we managed to get this number even lower. Right now, the only missing calls are QueryThreadCycleTime, SymGetSearchPathW, SymSetSearchPathW, SHGetKnownFolderPath, SetProcessDPIAware, however the SymGetSearch can be delayed and not loaded at start-time and SetProcessDPIAware can be faked to equal true all the time, so the only really meaningful kernel call that has to be implemented and backported is QueryThreadCycleTime, 'cause once we get that and we fake SetProcessDPIAware, we're gonna get Chromium74 open and display the UI, which would be totally positive sign. BOOL QueryThreadCycleTime( HANDLE ThreadHandle, PULONG64 CycleTime ); It refers to the realtimeapiset.h which works on Windows7 and greater only and it has two parameters: ThreadHandle, which has either the PROCESS_QUERY_INFORMATION or PROCESS_QUERY_LIMITED_INFORMATION access right and CycleTime which is the number of CPU clock cycles used by the thread and it includes cycles spent in both user mode and kernel mode. In order to avoid to try to use it, I tried to convert the Thread32 function and use the elapsed time, however I didn't manage to get positive results as it's important to know the exact clock cycles as it varies between CPUs, for instance some CPUs will vary the frequency of the timer when changing the frequency at which the CPU runs and others will leave it at a fixed rate, so asserting it will almost certainly lead to wrong results (which is what happened in my case). Unfortunately I don't have much time to dedicate at this, nor my "virtual XP colleagues" like Dibya, Samuel and Peter do as we're all very busy for a reason or another and we don't also wanna become blind by staring at "apparently meaningless" lines of code... I'm sorry that my fifth attempt to backport Chromium led to nowhere once again... Good night, Frank...

Microsoft Security Essentials Updater for download and update the definition. (for Windows XP x86/x64, Functionality not tested on other versions of Windows!) Download: here Download via Webproxy: here Password: P&n"y9j5V23Khb1%vA7vM9CreU3BYzI429TD$h6K§ Update V1.9 on 05/02/2019 Update V1.8 on 04/30/2019 Update V1.7 on 04/25/2019 Update V1.5 on 04/01/2017 Update V1.3 on 07/11/2016 Update V1.2 on 05/14/2016 Update V1.1 on 05/02/2016