Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20210102-6d7bb9f-uxp-0bb464bfc-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20210102-6d7bb9f-uxp-0bb464bfc-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20210102-6d7bb9f-uxp-0bb464bfc-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20210102-ddf403cf3-uxp-0bb464bfc-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20210102-ddf403cf3-uxp-0bb464bfc-xpmod.7z Official UXP changes since my last build: - Issue #1053 - Part 1c: Remove references to mobile/android targets and paths (9f004841a) - Issue #1053 - Part 2a: Remove android from /layout (partial) (ae2a16034) - Issue #1053 - Part 3a: Remove Android conditionals from /gfx (8d4456c79) - Issue #1053 - Part 3b: Remove AndroidSurfaceTexture and Android media decoder interface. (e011a048e) - Issue #1053 - Part 2b: Remove android from /layout reftests (0bb464bfc) Official Basilisk changes since my last build: - update link to new repo (dec2340) - Merge pull request 'Update link to new repo' (#35) from micwoj92/Basilisk:master into master (6d7bb9f) Official Pale-Moon changes since my last build: - [SSUAO] Add netteller to UA overrides. (ddf403cf3)

a fix is pushed, you may wait for next build or you can edit <root-dir>\omni.ja\modules\commonjs\sdk\url.js manually for hotfixing. https://github.com/roytam1/palemoon27/commit/bb287cf73f1611dbad38e528238133d49df2f78f

Classic Shell appeared not long after Windows 7 was released and supported both 7 and Vista. No Start menu that came from Redmond is as customizable as newer versions of Classic Shell / Open Shell. I would've used it in place of Windows XP's menu as well.

Foreword: I am notoriously cheap (besides old and grumpy). The story: I was gifted a couple (first one and a few months later the second) of non-working ASUS EEE PC model 1201T. both machines, with very little signs on wear on the exterior, clearly not excessively used/abused. showed the same symptom, on power on five leds (more specifically the one of the on/off button on top right, the one of the touchpad on/off button on top left and three on the bottom right, i.e. power, disk and wi-fi) were on, solid blue, the fan spinned, you could hear/sense the hd spinning BUT completely blank/black screen and no video signal on external monitor from the VGA connector. When I got the first one I thought (from previous experience with older laptops) that the video card/GPU was fried and set it aside, intending to later maybe salvage the hard disk. When I got the second one, I grew suspicious, two identical machines with the exact same issue? A few quick searches provided not any confirmation about the video card/GPU issue being common, but a more accurate search led me to this video by a nice Brazilian guy (which I have to thank a lot , not only for the specific solution but also for the idea of wrapping the upper part of the laptop to avoid scratches and fingerprints, simple and effective) : so the whole issue is that if the CMOS battery is exhausted the computer won't boot to BIOS, easily (and cheaply) solved on both machines. Since the idea, now that the machines worked, was to make them as functional as possible, I got two SATA SSD's (Crucial BX500 240 GB, got them for around 35 Euro each). Here came the second issue, the original disk inside the machines is 250 GB in size (one had a WD, the other a Seagate), so I couldn't do a 1:1 clone, and had to delve a little deeper to understand how the stuff (F9 recovery partition and boot booster) worked. Half to three quarters (or more) of the information you can find online about these two features is either partial, incorrect or plainly wrong. The partition table contains 4 entries: #0 Normal type 0x07 NTFS partition, active, around 100 GB in size, let's call it "system and boot" #1 Normal type 0x07 NTFS partition, around 113 GB in size (the exact size of this partition was slightly different on the two disks), let's call it "data" #2 Hidden type 0x1B FAT 32 partition, 10 GB in size (this is the recovery partition, containing a WinRE wim and a couple other .wims). let's call it "recovery" #3 "Queer" type 0xEF partition 17.5 MB in size, let's call it boot booster after the fourth partition there were "a bunch" of unused sectors. The first two partitions are perfectly normal. The third one is also pretty much normal, set aside the "hidden" (obtained by adding 0x10 to the normal value) ID. The last one is "queer". The Windows (and most info on the Internet) calls it an "EFI partition", though this is completely wrong, it has nothing to do with EFI or UEFI, the good Asus guys simply used this "EF" id to leave on the disk some (17.5 MB in my case, but I have read about other models using different sizes) some "reserved" space to store the *whatever* data is used to "boost" the boot time. When you go into the BIOS, IF a partition with ID 0xEF is found, then an option to Enable or Disable Boot booster appears, if there is not this partition the option disappears. From what I understand in these 17.5 MB some info on the specific machine and possibly about its configuration are pre-saved so that they need not to be "discovered" during the BIOS POST, shaving off a few seconds in booting time, surely this info is recreated when you enable the boot booster. The instruction/manual says that you need to first make sure that Boot booster is disabled, and then you can use F9 at boot time to start the WinRE (and thus use the factory reset/recovery). It is clear (now) that most of the magic is done NOT in the MBR code (as it is the "standard" Windows 7 one), unlike other OEM's, like, as an example, HP, see: https://msfn.org/board/topic/131620-hp-notebook-the-recovery-partition-could-not-be-found/ And I found some small evidence (which I had no occasion to actually test) that the functionality of F9 can be restored by making the 0x01B partitition active and (possibly? ) not hidden (i.e. 0x0B) and then, when the WinRE boots and you are given the option to recovery or abort, even if you select abort the partitions are "reset", i.e. first one is made active and the third one is (possibly? ) changed to 0x1B: https://www.forum-des-portables-asus.fr/forums/threads/touche-f9-ne-permet-plus-dacceder-a-la-partition-recovery.5307/ https://www.forum-des-portables-asus.fr/forums/threads/touche-f9-ne-permet-plus-dacceder-a-la-partition-recovery.5307/page-2#post-43132 Anyway, "my" F9 was working on the original hard disk(s), so I simply made some calculation (with the exact size of my SSD's) so that I had: #0 a clean NTFS volume, active the same exact size as the original #1 a clean NTFS volume, the exact size depending on the following #2 a clone of the 10 GB recovery partitions with the "sectors before" adjusted to reflect the new position[1] #3 only the EF entry in the MBR for the same size (17.5 MB) as the original 1 (one) excess sector after. Inserted the new SSD, at next boot: 1) disabled Boot Booster 2) pressed F9 3) chose to recovery and everything was well. Then I had some troubles to update to SP1 and a few other packages in order to be able to use Windows Update (which took forever), but this is another story. Conclusion: I hope that someone in a same or similar situation can find something of use from this report. The moral of the story (if there is one ) is: NEVER, and I mean NEVER, give up! jaclaz [1] for the record, I had some initial isssues with the PBR (and its copy, FAT32 stores a copy on sector 6) as (in the original volume) they were different, evidently the good ASUS guys used some tools that changed something (Root Directory cluster) after the initial format without updating the bootsector backup, and my good, invaluable, DMDE noticed it, in the end I verified that the "main" PBR was good and cloned it on sector 6

Today, the official Adobe Flash Player "version check" page no longer shows up; it was still working yesterday, Jan 1st, 2021, successfully detecting the last release, v32.0.0.465 ... https://get.adobe.com/flashplayer/about/ => https://www.adobe.com/products/flashplayer/end-of-life.html ... And it's the very first time they're revealing details about the time-bomb (included in versions > 32.0.0.371) set to go off on 12/01/2021

Only to confirm your impression, but on the very opposite side of the spectrum (low power machines, where a comparison is more likely to show noticeable differences). I just got two extremely el-cheapo (and old but in themselves "good enough") netbooks, identical, Asus EEE PC 12.1" 1201T (a not-so-common model sporting an AMD MV-40 processor). These machines are (were) intended as "pure" netbooks, i.e. minimal browsing and "normal" everyday activities in a rather light and portable format with a several hours lasting battery. Put on them both the max RAM (2 GB) and new 240 GB SSD drives. On the first I restored (from recovery partition) the original OS (Windows 7 Home Premium 32 bit), which I then updated to SP1 and via Windows Update to an as much "current" situation as possible. On the second I experimented an install of Windows 10 home (last release 2020, directly from MS original iso). I won't detail the amount of troubles I had to actually install the stupid Windows 10, as it would become a rant, but trust me it wasn't easy (on the other hand in the Windows 7 one having to deal with Windows Update (non)response times has been as well really trying) Anyway, after having run them both a few hours and having let them "settle", I briefly tested the two PC's side by side (literally). Quick sum up: 1) booting times: Windows 7 is seemingly a tadbit slower to get to the desktop, but Windows 10 is "faking", if I count the time until the Start button responds, W7 is faster 2) CPU usage: Windows 7 uses far less CPU at rest (including running in the background some of the built-in ASUS tools), W10 has a sh**tload of processes eating CPU time 3) RAM usage; Windows 7 at rest is around 532 MB, W10 at rest is around 1.1 GB (more than double) Right now I am re-setting/re-installing the second netbook to Windows 7, and make it identical to the first one. jaclaz

Hi The latest version Arctic fox 27.11 doesn't work anymore on rutube, I confirm in my last post that the Arctic fox browser works with the rutube website but without its video player, because I use an external video player . A new Arctic fox 27.11 version is coming and hop ... for the new year 2021 Rutube disappears from the screens of the arctic fox browser as on the New moon browser 27.9.7 of Roytam1 . it's called an involution. You have to have a strong mind not to get paranoid... Happy New Year to everyone.

Extensions broken in previous build still don't work. Working palemoon-27.9.7.win32-git-20201212-cafd4d45b-xpmod-sse : 02.Jan.2021 04:19:26 Warning: ReferenceError: reference to undefined property Type.prototype Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/method/core.js Line: 174 ---------- 02.Jan.2021 04:19:27 Warning: ReferenceError: reference to undefined property state.badge Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/ui/button/action.js Line: 111 ---------- 02.Jan.2021 04:19:27 Warning: ReferenceError: reference to undefined property Type.prototype Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/method/core.js Line: 174 ---------- 02.Jan.2021 04:19:27 Warning: ReferenceError: reference to undefined property state.badge Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/ui/button/action.js Line: 111 ---------- 02.Jan.2021 04:19:27 Warning: ReferenceError: reference to undefined property internal(...).parentMenu Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/context-menu.js Line: 515 ---------- 02.Jan.2021 04:19:27 Warning: ReferenceError: reference to undefined property root.parentMenu Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/context-menu.js Line: 1126 ---------- 02.Jan.2021 04:19:27 Warning: ReferenceError: reference to undefined property Type.prototype Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/method/core.js Line: 174 ---------- 02.Jan.2021 04:19:28 Warning: ReferenceError: reference to undefined property state.badge Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/ui/button/action.js Line: 111 ---------- 02.Jan.2021 04:19:28 Warning: ReferenceError: reference to undefined property internal(...).parentMenu Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/context-menu.js Line: 515 ---------- 02.Jan.2021 04:19:28 Warning: ReferenceError: reference to undefined property root.parentMenu Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/context-menu.js Line: 1126 ---------- 02.Jan.2021 04:19:28 Warning: ReferenceError: reference to undefined property json._dataType Source file: resource://gre/components/nsSearchService.js Line: 3696 ---------- 02.Jan.2021 04:19:28 Warning: ReferenceError: reference to undefined property param.purpose Source file: resource://gre/components/nsSearchService.js Line: 1196 Not working palemoon-27.9.7.win32-git-20210102-1f141d568-xpmod-sse : 02.Jan.2021 04:11:25 Warning: ReferenceError: reference to undefined property frame.columnNumber Source file: resource://gre/modules/commonjs/toolkit/loader.js Line: 206 ---------- 02.Jan.2021 04:11:25 Warning: ReferenceError: reference to undefined property Type.prototype Source file: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/method/core.js Line: 174 These are the errors reported at start-up only when those extensions are enabled.

@Monroe I did use ZA up to 3-4 years ago if memory serves me right but due to updating screw ups ( ZA antivirus was trying to update even though was not installed thus disrupting my work every so often) I uninstalled and installed PC TOOLS firewall plus version 7.0.0.123 considered one of the best firewalls at Matouasec. It has been running flawlessly and I found it to be better than ZA. The software retired about 9 -10 years ago. It is firewall + HIPS.

new ArcticFox win32 test build is uploaded: http://o.rthost.win/gpc/files1.rt/arcticfox-27.11.0.win32-git-20210102.7z too many commits to be listed, even github can't show all of them. https://github.com/rmottola/Arctic-Fox/compare/112f75dbc913ad1052931b17df0617bcad06d5c6...63656f89c5456afcb2f2da68adafb6899e99cbc7

New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.3.1-Goanna-20210102.7z Changelog: Out-of-tree changes: * update Goanna3 to git 5e5396a2f..1f141d568: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1102048 (Part 20, imgLoader) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (0a8270ba4) - Bug 1102048 (Part 23, encoders) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (6625ca535) - Bug 1102048 (Part 39, decoders/icon) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (55956f847) - Bug 1102048 (Part 24, decoders) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (cf2b002a7) - Bug 1102048 (Part 04, ClippedImage) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (c9f1451ad) - Bug 1102048 (Part 30, imgTools) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (2e3378d34) - Bug 1082837 - Track insecure redirects on imgRequest. r=? (466a14e22) - Bug 1139225 (Part 3) - Make OnDataAvailable threadsafe. r=tn (d10208a8b) - Bug 1139225 (Part 1) - Remove unused imgRequest::mBlockingOnload flag. r=tn (c0d80facd) - Bug 1102048 (Part 11, imgRequest) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (63ee15eb8) - Bug 1102048 (Part 38, ShutdownTracker) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (a58d515ed) - Bug 1102048 (Part 37, ProgressTracker) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (04b07cb06) - Bug 1102048 (Part 14, NotificationObserver) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (ca32242a4) - Bug 1102048 (Part 13, RasterImage) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (8f3931f31) - Bug 1102048 (Part 10, imgFrame) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (2f2b22e70) - Bug 1102048 (Part 36, DynamicImage) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (2cce04d2b) - Bug 1102048 (Part 09, Image) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (2f3743d2e) - Bug 1102048 (Part 29, imgRequestProxy) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (bf2824c08) - Bug 1102048 (Part 31, SurfaceCache) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (c6849f4d9) - Bug 1102048 (Part 25, header guards) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (bde0a4979) - Bug 1102048 (Part 33, SVGDocument) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (71f5f960c) - Bug 1102048 (Part 05, Decoder) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (48b1d5a80) - Bug 1102048 (Part 34, Multipart) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (fb65aa069) - Bug 1102048 (Part 35, Downscaler) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (2eb0be1f7) - Bug 1102048 (Part 19, ImageMetadata) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (749305ddd) - Bug 1102048 (Part 32, FrameAnimator) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (1df4850d6) - Bug 1102048 (Part 26) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (52550fb88) - Bug 1102048 (Part 03) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (438e52a57) (6b6341f07) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1102048 (Part 16) - Make image/src files comply with the Mozilla Coding Style Guide. r=seth (de8eaaf9d) - Bug 915805 - Don't treat unbound names in Function() code as globals when the Function() code contains a direct eval or similarly-extensible scope. r=jorendorff (9d719f57e) - Remove workaround for bug 748219, which seems to have been fixed in the meantime. (72e4042f7) - Bug 1009776 - part 1, [css-grid] Implement line-based placement. r=dholbert (0b43d82fb) - Bug 1009776 - part 2, [css-grid] Add a method to inflate the implicit grid to include a given grid area. r=dholbert (b6ea6b48b) - Bug 1009776 - part 3, [css-grid] Store the grid item's grid area on a frame property. r=dholbert (52dafc67d) - Bug 1009776 - part 4, [css-grid] Add a cell map to keep track of which grid cells are occupied. r=dholbert (c4e963666) - Bug 1009776 - part 5, [css-grid] Fill the cell map if the grid area is definite. r=dholbert (6b87324a7) - Bug 1009776 - part 6, [css-grid] Update the spec reference in a comment. (fd7bf76fd) - Bug 1107778 - part 1, [css-grid] implement automatic grid item placement. r=dholbert (80b21d1d4) - Bug 1009776 - part 7, [css-grid] Some reftests for grid item placement with definite positions. (2a7c95e5f) - Bug 1107778 - part 2, [css-grid] Some reftests for grid item placement with auto positions. (c5b12b74c) - Bug 1107778 - Remove a couple of unused test files that landed accidentally. r=me (8f7c87715) (a1addd18d) - import changes from mozilla nss repo: - Bug 1682863 - Revert nssSlot_IsTokenPresent to 3.58 after ongoing Fx hangs with slow PKCS11 devices. r=bbeurdouche - Bug 1680400 - Fix memory leak in PK11_UnwrapPrivKey. r=bbeurdouche (e1d2d4080) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1139539 - part 1, [css-grid] Implement primitive grid track sizing. r=dholbert (498e8b04e) - Bug 1139539 - part 2, [css-grid] Implement grid item containing block calculations and reflow (initial version). r=dholbert (335925317) - Bug 1139539 - part 3, [css-grid] Fix a couple of typos in the CSS Grid tests. (278c82cf3) - Bug 1139539 - part 4, [css-grid] Tests for simple track sizing and grid item layout. (91390780d) - Bug 1107783 - part 1, [css-grid] Implement abs.pos. grid item placement and reflow. r=dholbert (2b36d051f) - Bug 1107783 - part 2, [css-grid] Reftest for basic placement and layout of abs.pos. grid items. (f2f7d4274) - Bug 1145968 - [css-grid] Make grid items paint as inline-blocks and create a stacking context when 'z-index' != 'auto'. r=dholbert (7449e1152) - Bug 1107786 - part 1, [css-grid] Implement layout and painting per the CSS 'order' property for normal flow grid items. r=dholbert (52fb3b578) - Bug 1107786 - part 2, [css-grid] Implement a DisplayList sorting function that sorts by CSS 'order'. r=dholbert (a6a62aa7e) - Bug 1107786 - part 3, [css-grid] Implement layout and painting per the CSS 'order' property for absolute positioned grid items. r=dholbert (f61148242) - Bug 1107786 - part 4, [css-grid] Reftests for the CSS 'order' property on grid items. (5ad3979b7) - Bug 1144905 - Clean up SortByZOrder code and comments since it now assumes the list is already in content document order. r=roc (d0aa7e94a) - Bug 1192689 - Add in classes to LIR-none. r=nbp (82ebd0990) - pointer style (04b610ab2) - Bug 1182203 - Part 0: Generalize reciprocal multiplication constant calculation. r=sunfish (b08497260) - Bug 1182203 - Part 1: Optimize unsigned division by constants. r=sunfish (ce662ddc4) - Bug 1187323 - Add some asserts to the assembler's linkJump/nextJump/setNextJump methods. r=nbp (829d43cdf) - Bug 1187323 - Use release asserts in assertValidJmpSrc and related methods. r=nbp (96510be4c) - Bug 1183060 - wrong code generated for x86 word operations. r=sunfish (b7835db20) - Bug 774364 - Part 2: Move architecture specific function from BaseAssembler-x86-shared.h to BaseAssembler-x86.h and BaseAssembler-x64.h. r=sstangl (71b6831dc) - Bug 986680 - Part 1/4 - Define AutoGenericRegisterScope. r=nbp (cbce9c1f1) - Bug 986680 - Part 2/4 - Define per-platform ScratchRegisterScope. r=nbp (16d769323) - Bug 1169214: IonMonkey - Part 1: Create Ion shared stub helpers, r=jandem (7f8903293) - Bug 1169214: IonMonkey - Part 2: Add the x86 shared stub helpers, r=jandem (49bb8e972) - Bug 1169214: IonMonkey - Part 3: Add the x64 shared stub helpers, r=jandem (fbf58cf75) - Bug 1169214 - Add the ARM64 shared stub helpers. r=h4writer (62321406f) - Bug 1197665- IonMonkey: MIPS32: Fix build failure caused by Bug 1169214. r=h4writer (e55c027a8) - pointer style (4feea2046) - Bug 986680 - Part 3/4 - Convert x64 to ScratchRegisterScope. r=nbp (264af9838) - Bug 1188650 - Part 1/2 - Rename LIR-Common.h to shared/LIR-shared.h. r=nbp (e440be5c6) - Bug 1191552 - Move some common LIR to shared code. r=nbp (83a109d24) - Bug 1169213 - SharedStubs: Introduce JitFrame_IonStub to allow vmcalls out of sharedstubs in IonMonkey, r=npb (faae6df66) - Bug 1182936 part 3 - Rename mips to mips32 in check_macroassembler_style.py. r=nbp (ed7335bcf) - Bug 1184959 part 0 - check_macroassembler_style: Remove default values from the signature. r=h4writer (1fbd0de16) - Bug 1184959 part 1 - check_macroassembler_style: Only add an inline prefix in the output, if the methods are inlined. r=h4writer (b59cb1197) - Bug 1184959 part 2 - ARM ABIArgGenerator: Add support for soft-fp. r=h4writer (9a819c917) - Bug 1184959 part 3 - ARM MoveEmitter: Add support for pairs of registers. r=h4writer (ba90a8464) - Bug 1184959 part 4 - MIPS MoveEmitter: Add support for pairs of registers. r=rankov (0b9261cb2) - pointer style (0c2bb27db) - Bug 1184959 part 5 - Move callWithABI functions to the generic MacroAssembler. r=bbouvier,sstangl,jandem,rankov,h4writer (036ff5fc5) - Bug 935932 - Make Ion addprop stubs support dynamic slots (re)allocation. r=bhackett (37528556b) - Bug 1190295 - Remove 'args' arguments from MacroAssembler::setupAlignedABIArgs and MacroAssembler::setupUnalignedABIArgs. r=bbouvier (79b4c704c) - revert some unidentified patches (a08984287) - Bug 986680 - Part 4/4 - Convert ARM to ScratchRegisterScope. r=nbp (3ffe64d10) - Bug 986680 - Follow-up: Make constructors explicit. r=me (4d2f97498) - Bug 1192786 - Hook ARM disassembler into IONFLAGS=codegen machinery. r=nbp (337c3706a) - Bug 1103108 part 1 - ARM: Remove unused ma_callJit. r=h4writer (85ba22666) - Bug 1103108 part 2 - MIPS32: Remove unused ma_callJit. r=rankov (49465da6f) - Bug 1103108 part 3 - ARM: Replace single use ma_callJitNoPush by its implementation. r=h4writer (dfa1fb98c) - Bug 1103108 part 4 - MIPS32: Remove unused ma_callJitNoPush. r=rankov (107f96c30) - Bug 1184965 part 1 - Factor MacroAssembler::callJit. r=bbouvier (b299ad8ef) - pointer style (82c3494ca) - Bug 1184965 part 2 - Factor MacroAssembler::makeFrameDescriptor. r=sstangl (0a8108767) - Bug 1184965 part 3 - Use RAII for redundant profilerPreCall and profilerPostReturn calls. r=djvj (87356250f) - Bug 1157934 - import v8's ARM disassembler. r=jandem (63656f89c) (1f141d568) * 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

install WUFUC. it sometimes pops up after reboot, but don't worry about it. https://github.com/zeffy/wufuc

From Belgium, hello @Ricardo95 and welcome to MSFN! I wish you enjoy the forums! Have a nice day. hpwamr

Without patching the operating system in a way that makes sfc /scannow fail? Enlighten us, please... The W10 PowerToys are useless IIRC. The XP ones were more useful. Well, I think I'd go mad if I didn't have OpenShell on W10 when I have to use it You're saying people should just use the default sorry excuse for a start menu? It looks more like what an 8x real start menu would have looked like but the point is functionality not look necessarily. Best solution: upgrade to Windows 7, and forget about Windows 10, if you can!

Ain't it just a corollary of Parkinson's Law?

I've seen google only mentioning windows 7. Windows 8.1 was not even mentioned. Important: We will continue to fully support Chrome on Windows 7® for a minimum of 24 months after Microsoft’s End of Life date, until at least January 15, 2022.

Screenshare works, but audio does not. In browser it works and when you use app verifier and spoof windows 10, audio works too. It is intentional

Well yes, I'm aware of that. But discord still list windows 7 as their os requirement. Since they still list windows 7 I think we should not add it yet. source: https://support.discord.com/hc/en-us/articles/213491697-What-are-the-OS-system-requirements-for-Discord-

So I temporarily downgraded my bios to 2017 one and vista installation gets little bit further. Now I get Windows is preparing to start for the first time (again rough translation) and after this finishes I get different bsod. this time it says this: Hal initialization failed