Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190420-51722cd4f-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190420-51722cd4f-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.0a1.win32-git-20190420-51722cd4f-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190420-51722cd4f-xpmod.7z Official repo changes since my last build: - Stub out FxA context menu functions. (8e44bbb43) - Merge branch 'master' into Sync-weave (51b821b3f) - Merge pull request #998 from MoonchildProductions/master (bf0413359) - Remove CloudSync (4c4314864) - Remove some fxa tests. (aa1a39311) - Remove fxAccountsEnabled checks. (f999f544a) - Merge branch 'master' into Sync-weave (88083f8c6) - Merge branch 'master' into Sync-weave (473291f8f) - [BASILISK] Add configure option to disable sync (3e466a01e) - [BASILISK] Remove FxA Synced Tabs Sidebar (711c9cd6c) - [BASILISK] Remove FxA infected Sync - Part 1: Remove or condition CUI and Integration Points (349ceffd8) - [BASILISK] Remove FxA infected Sync - Part 2: Sync Client (3face1acf) - [BASILISK] Remove FxA infected Sync - Part 3: Remove about:accounts (12885d441) - [BASILISK] Remove FxA infected Sync - Part 3b: nsModule (757424eed) - [BASILISK] Port PM Sync Client - Part 0: Add PanelUI sync button static images (17a54a70d) - [BASILISK] Port PM Sync Client - Part 1: Initial transfer (f98cdab7a) - [BASILISK] Port PM Sync Client - Part 2: Basic Integration with glue and preferences (f6c16cff3) - Merge branch 'master' into Sync-weave (ce3979c72) - Merge branch 'master' into Sync-weave (015f385ec) - Merge branch 'master' into Sync-weave (6968a3e40) - [BASILISK] Fix merge induced error in base jar.mn (dc4c5d4c7) - Merge branch 'master' into Sync-weave (8e5056ce2) - [BASILISK] Restore Tabs from Other Devices history menu item and Add First Sync Progress (0ea4dabde) - Remove some BEOS 1st party code leftovers. (095ea5568) - Merge pull request #1 from MoonchildProductions/master (5a1843c9f) - Bug1408701: Ensure that we continue to show dark scrollbar thumbs on.. (577ca2cd6) - Merge branch 'master' into Sync-weave (dea594744) - [BASILISK] Port PM Sync Client - Part 4: Tools menu items (Set Up Sync/Sync Now) (519d0cf55) - Merge pull request #1042 from wicknix/master (07381c3ed) - [BASILISK] Port PM Sync Client - Part 5: Port the original sync toolbar button and create a synced tabs toolbar button (868c9b8d7) - Merge branch 'master' into Sync-weave (df0c78a8c) - [BASILISK] Port PM Sync Client - Part 6a: Obvious ifdef'ing and clean up (7008afd8e) - [BASILISK] Port PM Sync Client - Part 6b: Don't build the sync client ui when it is disabled, duh. (1e868fadf) - Merge branch 'Sync-weave' (3eb4310cd) - Remove FxAccounts front-end module references (8a6883251) - Remove various FxA tests (cdc962dca) - Remove Firefox Accounts service and tie-ins. (de75f133a) - Merge branch 'Sync-weave' (51722cd4f) My changes since my last build: - update Twemoji font to upstream 0.4.0. (6a07ab850) - nss: update nss to hg rev 2d6adc7d8bfc with vc2013 hackfix (0daf4d9cc) - update libaom to rev 76574b6c09515d6687ebfa9760319e521f5abeb3 (without moz.build and aom_ports/aom_once.h) (ef35212f8)

Today I make an update of the acpi.sys driver for Windows XP SP3 32 bit which should work on any compi. AMD, Intel, language does not matter Dietmar acpi.rar

This is a very interesting idea and it would be really nice to see this working. This is also a huge undertaking, so I wonder if it would possible to make this a collective effort. Surely this would benefit countless enthusiasts, would it not?

+1. Nice to have you around!

Thanks @mixit having to use a different browser to view Instagram videos was very irritating. So irritating that when I came across this thread and it mostly solved my problem I felt compelled to sign up to convey my thanks personally. I'm a regular on a forum where many interesting Instagram videos are embedded and up until recently all was fine. Then one day the embedded videos weren't playing and neither were the same vids on Instagram. They still won't play within the forum, unlike previously, but at least I can click on the video and it opens the original Instagram location in a new tab where they play fine.

Strange, I just tried again changing VolumeWidget=$0C and it worked! I don't know what I did wrong the first time, but it seems to be OK now, and I can control the level. BTW is the above graphic posted by @ABCDEFG on April 2nd actually correct? My testing indicated that it's the first four characters that control the left volume, and the last four that control the right volume, which is actually more what I would expect. The Windows Media Player volume control works fine. It was actually rather good to remind myself that I can play MP4 HD videos on Windows 98 with it, thanks to K-Lite, and they look and sound great, even in full screen! There's a bit of a delay with a series of pops from the speakers before anything plays, but I guess that's normal. So, the only outstanding anomaly is that the "HDA Sound" entry doesn't "stick" in the "Multimedia" Control Panel applet. When it's not there, I can't use the test facility on the "Sounds" applet, the test play button is greyed out, although the sound is actually working. The way to get it back, which is still very hit or miss, is to go to the "Devices" tab on the Multimedia applet, open up the HD audio entry, click on settings, and click OK in the settings box. This usually, but not always, returns the HDA Sound entry in the playback devices, after closing the applet and reopening it. Very strange! Anyway, I now have sound on Windows 98 with HD Audio hardware, and for that I'm extremely grateful. Yet again this forum has proved that what was thought to be impossible, is in fact completely possible!

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190420-b68d61fda-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190420-b68d61fda-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190420-b68d61fda-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190420-b68d61fda-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - dom: change `override` to `MOZ_OVERRIDE` to match ArcticFox (a5f7ce22e) - import change from rmottola/Arctic-Fox: - Bug 1141905 part 1. Make it possible to CreateScopeObjectsForScopeChain with a given non-global scope chain terminator. (f511987e7) - Bug 1141905 part 2. Make the 5-arg version of CreateScopeObjectsForScopeChain non-static so it can be called from multiple files, and move it to a possibly-saner location. (8eb583d35) - Bug 1141905 part 3. Use CreateScopeObjectsForScopeChain in DebuggerFrame_evalWithBindings. (00ccdc430) - Bug 1141905 part 4. Add some assertions about what enclosingScope can return for non-scope objects. (efcdac5da) - Bug 1137844 - Part 0 - Add docs for Debugger.Memory.prototype.onGarbageCollection (5db93db6c) - pointer style (c329881dc) - Bug 1137844 - Part 1: Make {get,set}HookImpl not rely on a Debugger instance in the 'this' slot (934d19578) - Bug 1137844 - Part 2: Add a Debugger.Memory.prototype.onGarbageCollection getter/setter pair. (4ea252a53) - Bug 1137844 - Part 3: Fire the Debugger.Memory.prototype.onGarbageCollection hook after GCs (3f549a594) - Bug 1137844 - Part 4: Test the Debugger.Memory.prototype.onGarbageCollection hook (1e82dc1ea) (9dcfc17d2) - import change from rmottola/Arctic-Fox: - Bug 1142311 part 1. Stop parenting self-hosted objects to the intrinsics holder. (3cb7980c4) - Bug 1142311 part 2. Rename the parent arg of NewScriptedFunction to enclosingDynamicScope, and make it optional. (27c00cbb2) - Bug 1142310 part 1. Stop parenting scripted functions created via the NewFunction APIs to non-globals. (46f6521fd) - Bug 1142310 part 2. Stop parenting scripted functions created via CloneFunctionObject to non-globals. (f164e8c49) - Bug 1136486 - Simplify the SVG text rendering callbacks by getting rid of NotifyBeforeSVGGlyphPainted and NotifyAfterSVGGlyphPainted. (fc76dffd1) - Bug 1142865. Remove the parent argument from NewObjectWithGroup. (211d191b7) - pointer style (c83032f78) - Bug 1142859. Don't parent the object created by JS_DefineObject to the object we're defining on. (7a91bf02a) - Bug 1135731 - fix encoding inconsistency in NS_NewXBLProtoImpl (9d5d99022) - pointer style (53f1a2cd1) - Bug 1142309. Remove the parent argument from NewObjectWithClassProto (472a00e66) (19f4294af) - import change from rmottola/Arctic-Fox: - pointer style (b6253e08b) - pointer style again (9a39bc621) - even more pointer style... (f28b6f2c4) - Bug 1066234 - Part 1: Parser support for 'extends' in ES6 Classes. (7782e671d) - Bug 1066234 - Part 2: Implement JSOP_CLASSHERITAGE. (d29afcf6d) - Bug 1066234 - Part 3: Refactor js::CloneFunctionObject to take a proto argument. (0cc6f6048) - Bug 1066234 - Part 4: Implement JSOP_FUNWITHPROTO. (2e0c04103) - Bug 1066234 - Part 5: Implement JSOP_OBJWITHPROTO. (2f3980885) - Bug 1066234 - Part 6: Emitter support for 'extends' in ES6 Classes. (361d75fb4) - Bug 1066234 - Tests. (c06dccce7) - Bug 1066238 - Part 1: Parser support for static class methods. (53315d021) - Bug 1066238 - Part 2: Emitter support for static class methods. (3dc069679) - Bug 1066238 - Tests. (78470ee78) - Bug 1142296. Remove the parent argument from NewObjectWithGivenProto (plus adaptations for Goanna) (918202ddd) - Bug 1142304. Remove the parent argument from NewObjectWithGivenTaggedProto. (036d97369) (81d2deb5a) - backout bug 1134280 for fixing yandex search "Read more" link (980f33dae) - Revert "backout bug 1134280 for fixing yandex search "Read more" link" (01ed5ad3a) - finally fixed yandex search "Read more" link issue. this seems to be an accidentally changed line in upstream(s) that is fixed in bug 1141455. (6a3c759b1) - ported mozilla changes: bug1143506, bug1143509, bug1144899, bug1145560, bug1162350, bug1189593, bug1124084 (ea571e456) - import change from rmottola/Arctic-Fox: - Bug 1142864. Remove the parent argument from NewObject. (2e4cce561) - Bug 1281596 - fix evutil_rand.c for clang/android builds clang apparently dislikes |return func(...)| in a function which returns void. Remove the return to make everybody happy. (beab9a4b3) - Bug 1282141 - compensate for arc4random_buf not being available on Android; (db344c525) - Bug 1181026 (part 1) - Reformat libevent's README.mozilla file. (2816f11ef) - Bug 1181026 (part 3) - Fix libevent constants for 32-bit Linux/Mac/BSD builds. (979920fdc) - Bug 1181026 (part 2) - Clean up libevent patch handling. Add a missing one to the docs, and move them from their current two locations into a new patches/ directory. (40911a1f5) - Bug 1259218 - don't use arc4random_addrandom on Android, since NDK r11 doesn't provide it (ab8a3fcdf) - Unbreak bundled libevent on FreeBSD 12 without upgrading it - hack of existing Bug 1259218 for Android. This patch needs to be reverted when livenet is upgraded and Bug 1497169 applied instead. (4a29b331d) (7f760bdaa) - nss: update nss to hg rev 2d6adc7d8bfc with vc2013 hackfix (a81b41088) - import change from rmottola/Arctic-Fox: - Bug 805052 part 1. Remove assertParentIs. (4c5d44eb8) - Bug 805052 part 2. Stop using the shape's parent to get the object's global. (6da3560dd) - pointer style (e2545c9a5) - Bug 805052 part 3. Remove parents from SpiderMonkey. (8ca3b3643) - Bug 1143706 - Allow BaseShape's global to be null when tracing (8e45cec9d) (b68d61fda)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190420-325e148-uxp-51722cd4f-xpmod.7z Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190420-325e148-uxp-51722cd4f-xpmod.7z source patch (excluding UXP): https://o.rths.cf/boc-uxp/boc-uxp-src-xpmod-20190223.7z No official repo changes since my last build.

Have a great Easter break, whatever you're doing!

Could you provide more details on the exact problem? Do you end up with IE 5 and DirectX 7 installed instead of the newer versions? Could you post screen shots? I have personally not experienced such a problem. In my new, fresh installation of Windows 2000 using the FullPack I have both IE 6 and DirectX 9 installed correctly. I have conducted a fresh installation using the FullPack and can confirm that the .NET programs indeed do not work correctly. I am guessing that it is HFSLIP unable to correctly integrate the .NET addons. I will try to do more testing and see if the issue is fixable, either in HFSLIP2000 or the .NET addon packages themselves.

Windows 2000 Server: 4 CPUs/threads Windows 2000 Advanced Server: 8 CPUs/threads Windows 2000 Datacenter Server: 32 CPUs/threads The theoretical limit is 2^16 CPUs/threads if the appropriate registry hack is made, with all editions of Windows 2000.

It was to be expected that the MS will shut down the update system. So I've created my own update rollups (DEU and ENU) to circumvent this problem. Following a list of the updates that are included in my rollups.

An interesting little change I noticed in the April 2019 update rollup: For those that didn't notice, since 2009 with the release of SP2, Windows Vista's build number has been 6.0.6002 (while SP1 was build 6001, and RTM 6000). However, with the new rollup, Vista's build number has been changed to build 6.0.6003. At first I wondered if this was an error/discrepancy on MS's part, but turns out the change was intentional, according to this article: https://support.microsoft.com/en-us/help/4495374/build-number-changing-to-6003-in-windows-server-2008 Just an interesting little thing I thought I'd point out This change doesn't seem to affect functionality of anything though (at least not that I'm aware of), which is good.

regsvr32 MSI.DLL regsvr32 MSIHND.DLL regsvr32 MSISIP.DLL

You guys give up too easily, is this the infamous XP lair of fanatics or not!? Fortunately there is (for time being, anyway) a pretty simple fix for this "video problem". (I use quotes because it has nothing to do with video as such.) You don't need to switch or recompile browsers either - at least not right now over this particular issue. Apparently ESR 52.9 handles CSS flex layout a bit differently, so with the current Instagram code the video and its surroundding elements kindly get the height of 0 pixels... This can be fixed by modifying a surrounding <div> container to use block display instead of flex. If you use uBlock Origin, you can add the following rule to your My filters: instagram.com##div.ZyFrc[role=dialog]:style(display: block !important) (Just make sure Filterlists > Parse and enforce cosmetic filters is checked and that Settings > Default behavior > Disable cosmetic filtering is not checked or is overridden per-site for instagram.com.) The same can presumably be done with other styling/tweaking extensions, only the syntax may be a little different. I don't use anything else, so can't give you the specifics. If you don't use any such extensions and don't want to install them, you can just add the following CSS snippet to your userContent.css file (it's located in the chrome subdirectory under your Firefox profile folder. Edit: as @Dave-H pointed out, the file may not exist yet, in which case just create a new text file, put this stuff in it, and rename the file to userContent.css.) @-moz-document domain(instagram.com) { div.ZyFrc[role="dialog"] { display: block !important; } } (In this case you'll have to restart the browser for this to take effect, only refreshing the page won't make a difference.) BTW, aside from div.ZyFrc[role="dialog"] , simply using div.ZyFrc or div[role="dialog"] also works. I'm just using the more specific condition to hopefully avoid accidentally breaking something else on Instagram (I'm not a frequent visitor there, so I wouldn't know). The mangled class name ZyFrc is pretty likely to change when they rebuild they code, and using the role-based version without a class name may survive that. Or it may not - as we know web devs need to constantly tweak their stuff, even when it's not broken... So this may need to be revisited. Edit: Forgot to give kudos to @Mathwiz for narrowing down the problem and linking to this change list with hints to flex layout being the problem. Edit 2: I tested this style fix on ESR 52.9.0, but I'd be surprised if 52.9.1 would be any different in this regard. ----------------------- In other news, if you're spoofing a more current version of Firefox on all sites with ESR 52.9, apparently you'll have to drop your spoofed version below 57 on instagram starting today, because they seem to have switched over to Quantum-specific code for newer versions and basically nothing works anymore. (If you're using the default 52.9 user agent, you shouldn't need to make any changes because of this - at least it seems to work for me.) It could mean, though, that they'll be dropping support for anything pre-Quantum sooner rather than later, which may also affect the various Pale Moon derivatives, depending on how up-to-date their CSS and JS support is.

This is fun! Regarding the missing backend stuff, can't one infer what it does by examining the frontend client stuff, and then re implement it somehow? How do the inner workings of v6 differ from v3/v4? Aside from cosmetics, I haven't noticed a huge difference in functionality, so maybe the v6 backend can be hacked for use with the v3/v4 UI? c