Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.4.win32-git-20191109-4a0c734e1-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.4.win64-git-20191109-4a0c734e1-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.ml/palemoon/palemoon-28.8.0a1.win32-git-20191109-4a0c734e1-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.8.0a1.win64-git-20191109-4a0c734e1-xpmod.7z Official repo changes since my last build: - Issue #1064: Don't get certificate details synchronously. (3252e2200) - No issue: Clean up `exceptionDialog.js` (a63272b53) - MoonchildProductions#1251 - Part 1: Restore initial Solaris support, fixed up. (afc187cc3) - MoonchildProductions#1251 - Part 2: Make the mozconfig loader POSIX-compliant. (9d449ce61) - MoonchildProductions#1251 - Part 3: Finally end the long tradition of casting getpid() to int. (64e03d014) - MoonchildProductions#1251 - Part 4: Core build system changes, lots of libevent/IPC junk. (4105ebb6e) - MoonchildProductions#1251 - Part 5: Fix POSIX compliance issue in process_util.h. (f105b741e) - MoonchildProductions#1251 - Part 6: Solaris needs an audio implementation. (57bfda37a) - MoonchildProductions#1251 - Part 7: All the posix_m* memory-related stuff, gathered together. (3647f42c2) - MoonchildProductions#1251 - Part 8: Align pointer for char_16t. (c0d814c1d) - MoonchildProductions#1251 - Part 9: Look for hypot in the math library (libm). (cf75ede0d) - MoonchildProductions#1251 - Part 10: ipc_channel_posix.cc should use IOV_MAX. (52f2321cb) - MoonchildProductions#1251 - Part 11: libpng uses C89 now to avoid buffer overflows. (7966d22df) - MoonchildProductions#1251 - Part 12: Add Solaris/illumos support to WasmSignalHandlers. (76c55f747) - MoonchildProductions#1251 - Part 13: Redefining abort in C++ requires extern "C" (5c28f10c1) - MoonchildProductions#1251 - Part 14: libstagefright build should avoid _GLIBCXX_OS_DEFINES. (e3fb8bd24) - MoonchildProductions#1251 - Part 15: fdlibm should provide definition for u_int32_t and u_int64_t. (4f6639a1b) - MoonchildProductions#1251 - Part 16: Resolve namespace conflicts with dbm on Solaris. (fca7c45a6) - MoonchildProductions#1251 - Part 17: All the libffi and libxul.so issues, resolved. (beea314ff) - MoonchildProductions#1251 - Part 18: (Hopefully) final version of build system fixes. (7e5ff857e) - MoonchildProductions#1251 - Part 19: Make the unpreprocessed file script work on Solaris. (e51afbcc2) - MoonchildProductions#1251 - Part 20: Add atomic.h to system-headers. (db34ef993) - Fix a bunch of dumb typos and omissions. (575f51a27) - MoonchildProductions#1251 - Part 21: Fix Flash player and some extensions being incompatible. (5a4a4990c) - MoonchildProductions#1251 - Part 22: Remove some unused type declarations from IPC process_util. (7d65eb2b3) - MoonchildProductions#1251 - Part 23: Allow AMD64 build to work. (2f4488521) - MoonchildProductions#1251 - Part 24: Remove temporary GNU M4 workaround. (9cd92944e) - MoonchildProductions#1251 - Part 25: Fix link paths. (21146d0d5) - MoonchildProductions#1251 - Part 26: Oracle Solaris gsed/ICU fix. (e4f90cbb5) - MoonchildProductions#1251 - Part 27: Fix ifdef style. (687a798e6) - Fix nits. (a9dc528a4) - Merge pull request #1262 from athenian200/solaris-work (21b3f6247) - Issue #146 - Part 1: Draw each table's background on their own display list items. (145527207) - Issue #146 - Part 2: Remove custom table painting component. (0de40040f) - Issue #1265 - Expose sndio as a build option for any supporting system (873f2cf8c) - Issue #1267 - Part 1: Update libcubeb to a1200c34. (d162ecbaf) - Issue #1267 - Part 2: fix libcubeb bindings in dom (22b35fa8e) - Merge pull request #1270 from g4jc/libcubeb (b7c6c779e) - Merge pull request #1269 from g4jc/sndio (6ee3467a6) - Issue #146 - Part 3: Create nsDisplayTableFixedPosition to avoid display list collisions when processing the background image of a table. (db98e3eff) - Issue #146 - Part 3: Create nsDisplayTableBackgroundImage to avoid display list collisions when processing the background image of a table. (ee663e293) - Issue #146 - Part 4: Adjust tests for fixes. (f1b043af1) - Issue #146 - Part 5: Treat table row groups as containing blocks. (ce11d5cae) - Issue #146 - Part 6: Allow `position: sticky` on table elements. (5ab2da700) - Issue #146 - Part 7: Remove no longer relevant reftest. (76052e837) - Revert "Issue #1267 - Part 2: fix libcubeb bindings in dom" (732fe3624) - Revert "Issue #1267 - Part 1: Update libcubeb to a1200c34." (1960d6e08) - Bump Goanna version. (ee8c5d387) - Issue #1271 - Fix build failure in current in-tree libcubeb sndio module (ff0f4b11a) - Merge pull request #1272 from g4jc/libcubeb (22b410f31) - Merge branch 'table-sticky-work' (bbc2206a0) - Issue #1252 - Remove fragile fast path. (082670ecb) - Merge branch 'master' into certexception-work (c5c44d120) - Issue #1064 - Part 2: Fix shorthand and services module import. (5f37447ac) - Issue #1064 - Part 3: Fix notifyObservers() call. (6df8aa495) - Issue #1274 - Part 1: Adopt the cairo version as our own. (7efd71616) - Issue #1274 - Part 2: Update Windows prerequisite defines. (45f665b59) - Issue #1274 - Part 3: Update libpixman licensing (620fdbdf4) - Issue #1274 - Part 4: Remove some unnecessary checks for old Windows versions. (7b8a065ea) - Issue #1274 - Part 5: Misc fixes and version update. (5f80c286c) - Issue #1275 - Add pref to disable warning prompts for SuperfluousAuth and AutomaticAuth, and default to not prompting. (7f5d38150) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (aff468a48) - Issue #1263 - Part 1: Remove DiskSpaceWatcher (60c83971f) - Issue #1263 - Part 2: Remove DiskSpaceWatcher tests (eb35cd108) - Merge pull request #1214 from MoonchildProductions/certexception-work (8bb208397) - Merge pull request #1276 from MoonchildProductions/cairo-work (0f3635dc8) - Issue #1254 - Update SQLite to 3.30.1 (4a0c734e1) My changes since my last build: - Reverted Issue #1274 - Part 2: Update Windows prerequisite defines. - Reverted Issue #1274 - Part 4: Remove some unnecessary checks for old Windows versions. (7b8a065ea)

I also want my OS to stay current until October 2023 0 that's why I run Windows 8 ....lol

Yep, but I want my win7 to reach EOS in 2023

Whoah.... your stories are real drama! And the above sounds like you're not too aware what you're dealing with here, but it's not quite trivial. I think it's all described in detail on the first UOC page, and strongly recommend studying it. But it's been a while that I've read it myself, so just a few quick tips from my own understanding: What matters most, is to FIRST make a backup of your profile! Or at the very least of PREFS.JS and USER.JS (if existing). You will need those files again to restore your current settings if later you remove the patch again. You can find your current profile folder in a link on the about:support page. IIRC the enforcer file goes into that profile folder, contents to be added in user.js, but better read this in the instructions to be sure. The "normal" patch file creates different "default" values for the contained prefs. This file goes into your unzipped program folders, into subfolder ../defaults/pref/ or /defaults/preferences. You want new profiles? Regarding K-Meleon, if you use roytam's 7z build, those create the profiles inside the unzipped program folder. You can just delete that "profiles" folder and restart, but I recommand to keep the current profile and just create a second one: Menu Edit>Manage Profiles K-Meleon also has the specialty that some user settings are stored outside of the profile, especially when changing toolbars, but you don't sound like you customized very deeply. PS: your screenshot, is it really intentional that you have the file types hidden, the endings after the filenames?? Or only because it's that stupid MS default setting? At any rate that icon for UOC looks you did not unzip the patch yet, that means it simply got ignored. You must extract the contained files to do anything with them.

New regular/weekly KM-Goanna release: https://o.rths.ml/kmeleon/KM76.2-Goanna-20191109.7z Changelog: Out-of-tree changes: * update Goanna3 to git 13f9e7fee..df039285e: - bump versions (58723f645) - ported bug1200802 (ef47f9b55) - import changes from rmottola/Arctic-Fox: - Bug 968520 - Explicitly specify the allocator for nsTArray_base functions. r=froydnj (8e11c1a0c) - Bug 968520 - Add fallible variant of nsTArray::SetCapacity. r=froydnj (3a33bc53e) - Bug 968520 - Add fallible variants of nsTArray::InsertElementsAt. r=froydnj (d52030d81) - Bug 968520 - Add fallible variant of nsTArray::EnsureLengthAtLeast. r=froydnj (7f22637b6) - Bug 968520 - Add fallible variant of nsTArray::SetLength. r=froydnj (a6f43b1b0) - Bug 968520 - Add fallible variants of nsTArray::ReplaceElementsAt. r=froydnj (e17169b21) - Bug 968520 - Add fallible variants of nsTArray::InsertElementAt. r=froydnj (0ed62209a) - Bug 968520 - Add fallible variants of nsTArray::AppendElements. r=froydnj (c4f4d2a1e) - Bug 968520 - Add fallible variants of nsTArray::AppendElement. r=froydn (3fbf72f7a) - Bug 1165729 - Remove unnecessary template declaration for fallible nsTArray::AppendElement. r=froydnj (f72cc5efd) - Bug 968520 - Make nsTArray::InsertElementSorted support moves. r=froydnj (217178725) - Bug 968520 - Add fallible variants of nsTArray::InsertElementSorted. r=froydnj (f99e300b9) - Bug 968520 - Add more fallible variants of nsTArray::InsertElementsAt. r=froydnj (218d4f025) (19841f19a) - addendum to git rev 19841f19a1e0fc573b99c2b56f280109786a79db, fix moz_malloc/moz_realloc/moz_free for our tree (3b174064e) - import changes from rmottola/Arctic-Fox: - Bug 1140264 part 1 - Avoid expanding auto-hidden ruby annotations. r=dbaron (5b6ddba10) - Bug 1140264 part 2 - Move and merge line breaking code in rbc reflow to reduce useless computation and fix undesired break point. r=dbaron (0d3aaad79) - Bug 1140264 part 3 - Rename IsInlineDescendantOfRuby to ShouldSuppressLineBreak and exclude rbc/rtc from it. r=dbaron (e929b296b) - Bug 1140264 part 4 - Reftest for this bug. r=dbaron (3aa19d44e) - Bug 1141842 - Add LastOptionalBreakPriority to nsLineLayout to simplify some code. r=roc (81cc1dcd0) - Bug 1137875 - Have the SharedFrameMetricsData hold a copy of the layers id. r=nical (81c657510) - Bug 1133237 - When transitioning from a shadow layer tree that has plugins to a tree that does not, make sure the old plugins get hidden properly. r=roc (11ff16c17) - Bug 1137875 - Have the LayerTransactionChild hold a copy of the layers id. r=nical (f9a090aad) - Bug 1137875 - Clear shared frame metrics objects associated with a PLayerTransaction when it is destroyed. r=nical (c5037ee27) - Bug 1119878 Part 1: Change SandboxTarget to hold sandbox target services to provide functions. r=aklotz, r=glandium, r=cpearce (7378d13e4) - Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. r=billm, r=dvander, r=aklotz, r=cpearce (fa002f559) - Bug 1149971 Part 1: Follow-up to bug 1119878 to fix broken IPDL tests. r=dvander (76b843d43) and some lines of fix of toolkit/xre/nsEmbedFunctions.cpp after Bug 1119878 Part 2. (5ec13acbd) - import changes from rmottola/Arctic-Fox: - Revert Bug 1125848 - Consolidate PCompositor's creation-destruction logic because of 10.7 MacOS bustage (ceda5a133) - adapt assertion to be as introduced in Bug 1125848 (877071282) - Bug 1160190 followup. Make ServiceWorker actually disabled on mulet so we can reopen the CLOSED TREE. r=bkelly (1a03ee7c2) - Bug 1123846 - Restrict some activities to be provided by the system app r=ferjm (c7ca76805) - fix header include order (01b1289df) - Bug 1151644 - Don't disallow the basic compositor backend. r=jrmuizel (b70633afd) - Bug 1155823 - Properly shutdown the CompositorVsyncDispatcher. r=kats (a3dee13e8) - add gfxCrashReporterUtils as of 1180688 2015-07-13 (433fa6bdb) - Bug 1029673 - Correctly report OMTC compositing in crash reports - r=Bas (87fc22936) - Bug 1180688 - Detect whether the widget will be able to present frames with BasicCompositor on Mac. r=mstange (842ed309f) (eca52a3f8) - import changes from rmottola/Arctic-Fox: - Bug 1125848 - Consolidate PCompositor's creation-destruction logic. r=sotaro (bd9905d37) - Bug 1180688 - Reset the appropriate widget states if creating a compositor fails. r=mstange (461339a0c) - missing part of Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. (631e112dc) (df039285e) * 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 build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20191109-6b769f4-uxp-4a0c734e1-xpmod.7z Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20191109-6b769f4-uxp-4a0c734e1-xpmod.7z source patch (excluding UXP): https://o.rths.ml/boc-uxp/boc-uxp-src-xpmod-20190720.7z There are changes in upstream now, but unless his uxp branch goes into main branch(or unless I cherry-pick his branch's changes into my tree), I will do cherry-picks of his repo only. - cherry-picked "[Mail] Add changes to align with mailnews (096b6e0)" For UXP changes please see above.

One thing to watch out for: the file names are different (e.g., UOC_Patch_38.js vs. UOC_Patch_45.js). So besides copying the _38.js files, you also need to delete the *_45.js files you copied earlier; otherwise NM 27 will load both and the result will probably not be what you want!

Nothing new in this post; it's just a summary of what's been discovered so far about this issue. To play Instagram videos in your FF (or FF-derived) browser, you need three things: Most obviously, you need to be able to play MP4 videos. This won't be a problem with @roytam1's UXP forks (NM and Serpent) since he includes his MP4 video DLLs in the build. For FF 45 though 52 or SeaMonkey 2.49.5, you can install the Adobe Primetime CDM according to the instructions pinned atop this forum; either method works. (Those instructions were recently modified slightly to work with SeaMonkey.) You need to set your user agent to spoof FF 56 to instagram.com. You can either set the general.useragent.override preference in about:config to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 or use an Instagram-specific user agent. FF versions before 56 work too, down to a point, but basically nothing on Instagram works at all if you spoof any version newer than 56. If you're not using NM, Serpent 52, or SeaMonkey, you need the following code in file userContent.css in the "chrome" subfolder of your profile: Note that this code is changed somewhat from @mixit's original fix; Instagram changed some of their random class names, requiring an update. Instagram will probably change them again someday, and we'll have to get @mixit to update his fix yet again.

I have yet to go through stuff on what I think are his testing machines. I have plans for doing that mid next week though. I can use this info (knowing that there might be an RFDISK 3.1) to help me figure out if I'm looking at something more recent than what I am working off of.

@VistaLover I have a similar problem with GMail freezing the whole browser whenever I close a tab with it open. Even reported it here but was ignored, and no, sadly creating a new profile doesn't help in this case.

This is my workaround, together with Total Commander for Android (free!). Using an USB-drive with normal and with micro-USB-connection. BTW: not all smartphones can mount an USB-drive!

I think I'll have to set up one of his computers to find it. I have a feeling it isn't in the "active" set of stuff I'm looking at. Thanks! Uploading them without going through them would not be a good idea. Right off the bat, there is customer information scattered in there. I already seen some family photos in the mix and even some code that I know is not relevant. I wouldn't want to just throw it out there. I can hold my own in regards to programming knowledge so that isn't a concern. A repo can be made at any point and anyone here could do it if they felt inclined to do so. I can't offer support for it anyway - I just don't have the time. My option was to upload source without a build system or to not upload source. I would like to think you can see what the better option is. In any case, the logic in the code is more important for anyone to try to learn or extend his work. Regarding who my dad was, I'm uploading his resumes so you get an idea of what he felt was appropriate to say he did. He did a bit of consulting work for Aerospace Avionics (I think that is the name, I have a pile of hardware schematics from them but they were absorbed into another company) but pretty much was consulting for the last 30 years and living off investments and tax liens. My dad was phone phreaker in his youth and actually got arrested for it (I'm quite proud of him for that) and was forced to write a public apology to avoid jail time. He was also responsible for this article: http://explodingthephone.com/docs/dbx0431.pdf I'm pretty sure that I'm about the only person he would trust with this. Although, he would not be pleased that I'm just giving away his work and that is a point where we differed in opinion, I think it is the best option for me to preserve his legacy. I never got into Windows like my dad did but I do take after him quite a bit. I wish my dad followed more modern standards for organization and such but the major issue is that there is just a massive amount of data. I brought about 60TB of stuff back home with me and that might only be half of his recent stuff (last few years). He has tape archives going back at least 20 years but I am pretty confident that stuff isn't related to his Windows endeavors. HTML by hand fits my dad so well. But I'm thinking about using React for the long-term of the page. Newspaper Article for Rudy.pdf resume.txt RESUME.DOC

I think for me what was the final nail in the coffin was that older applications (I used an older but more reliable version of u Torrent) stopped loading and unloading reliably once I update Vista past March 2018. So either skipping Spectre and Meltdown patches, or whatever else, simply made Vista run much worse. At this point, if I were to ever go back to an older system, it seems that Windows XP x64 Edition works more reliably. The Roytam1 browser choices are pretty much equal. But in truth, a modified Windows 8 installation (Metro and Start Screen disabled, Classic Shell installed, and Server 2012 patches) runs RINGS around a Vista x64 installation, especially in terms of reliability and performance. I may have started the "Server 2008 Updates on Windows Vista Thread", but I got off the ship now. That's OK. We change. That's all part of growth.

I managed to install net framework 4.7.2 in Windows Vista correctly: https://msfn.org/board/topic/178673-tutorial-how-to-install-net-framework-472-on-windows-vista/ Other software more updated to the list of latest software compatible with vista. .NET 4.8 does not work due to lack of ordinals

Yes, I tried the final version of .NET 4.8 on Vista just now, and while it could be installed, it unfortunately displays the same behavior as 4.8 Preview: This means that .NET 4.7.2 is the final version that can be used on Windows Vista without these issues, seemingly I did just that, and here are some of the files I got: I then modified the .MSI file with Orca like @artomberus did, and received the same error message when attempting to run the program after installing it... However, this limitation is pretty easy to circumvent using @blackwingcat's PEMaker tool: After modifying and recompiling the .exe file using this tool, that eliminated the "not a valid win32 application" error but sadly, my success was short-lived: So it looks like Paint .NET is a no-go on Vista As far as SP1 goes, .NET Framework 4.7.2 does "require" this, but there is no mention of the Platform Update "requirement" on Microsoft's .NET OS compatibility chart here. Bearing this in mind, the software likely calls for functions introduced in Windows 7's Platform Update, which would explain why it doesn't work in Vista even with .NET Framework 4.7.2 installed... Sadly, no. Downloading the installer and attempting to run it does not work, and extracting it provides no .MSI installer to use/modify, nor are there any available elsewhere on the web, from what I've found: