Leaderboard

(Sorry, didn't have time to respond to this before.) I agree with your general point, but I'm not sure how much Google is to blame in this particular case. The thing is, programmers often tend to be pretty lazy when having to do maintenance tasks, because these aren't seen as "cool" and "innovative"... And this bug is a bit of a special case, because it takes almost 30 min to run a single test case, whether you're trying to track down where the regression originated, or trying to fix it. Let me give you a rough rundown of the process I went through with this (let's skip this long story for them normal people ; and this isn't about me looking for extra credit, honest! ) OK, so now consider that during virtually every step of this, you have to run a whole lot of 30 min (or longer) tests to make sure of your guesses or fixes. I am, of course, a great guy and all , but even with my highly vested hobbyist interest in solving this issue it took me several months to get through this all. Obviously not months of straight work on this alone, and obviously I didn't just sit around gaping at the screen every time I ran a test, but started the test and then did something else while it ran, but the whole thing still took time. Now, imagine I was an elite coder working at Mozilla , and generally supposed to work on some other stuff besides this. And, let's say you were my manager. Are you sure you'd let me spend all this time on this one, apparently (but really not) intermittent issue that seems to be affecting only a few people (really affecting all, but 99.99% of those people wouldn't put 2 and 2 together and notice the very specific interval and would instead write these freezes off as internet issues or whatever else) on a "legacy" OS that doesn't have that long to live anyway (or so you think, not knowing about POSReady, and MSFN )? And would I, an elite Mozilla engineer , want you to make me spend my precious time on something like this? I mean, even without the whole Windows driver dive and leak hunting thing they obviously wouldn't get into (the leak hadn't happened yet, either), it's a lot of work that isn't "cool", nor "innovative"! This is not to say that I excuse the fact that they don't even run tests for longer playback, etc., etc. We all know Mozilla has lots of problems with their attitude and policies, and there are many things they aren't doing that they should be doing (and vice versa). I definitely do blame them for letting this fall through the cracks and not doing more to fix this. But as far as Google goes, since they probably weren't using cubeb, maybe they themselves never ran into this bug (at least its more obvious, 2x:xx version), and since this isn't an issue specific to Youtube, I think I wouldn't blame them too much for this one. But there is Microsoft, who introduced this bug in the first place with that pretty dumb coding error...

I guess this is my cue to stop procrastinating and finally post the fix I made for this I've had a few people test it for 4 months now on all kinds of sites on both XP x86 and x64, and the jury says this indeed fixes the 2x:xx video stoppage issue and doesn't seem to introduce any new problems. I honestly didn't intend for the testing period to be quite this long, but summer heat can have a detrimental effect on one's brain and thus plans. Since my own browser builds are based on Centaury, but I still consider myself a (lurking) MSFN patriot and this is the home of @roytam1's Serpent, I'm just going to post the fixed media/libcubeb/src/cubeb_winmm.c on Pastebin to avoid playing favorites (and signing up on Github ) I'm not sure how often @feodor2 visits here these days, so maybe someone on Github could mention this in https://github.com/Feodor2/Mypal/issues/1 if he doesn't pick this up soon enough. What has been tested: MP4/VP9/VP8 (and plain audio MP3/etc) streaming/local chunked/single-file sped-up/slowed-down 27+ hrs long playback (see the technical details for why) Youtube/Twitter/Facebook/Instagram/TV station streams/etc/etc (nor did we forget p0rn/pirate sites, which of course are no different from a technical POV... ). Among other things, a 75-year old lady watched the entirety of Prince Philip's funeral with this fix in effect and had no complaints. What has NOT been tested: Pale Moon-based builds (as opposed to Basilisk), because I don't use NM or Mypal. Since this is a UXP platform level fix, the front-end should have no effect. I obviously don't have access to every sound card out there, but since the MS driver causing these problems should be common in all configurations, I'd expect the fix to work with pretty much every card. new-fangled formats like AV1 (I'd expect them work, though). DRM-ed streams, since no Widevine on XP (but again, this should work with those as well if DRM itself worked). @roytam1, @feodor2 I didn't create a preference for turning this fix off, because it turned out the normal pref system is no longer compatible with C code, and once it became evident enough that the fix was pretty solid, I didn't feel like hacking something together to make preffing work for a library-level change like this. You're welcome to pref it, of course, but based on the length of testing with no issues discovered, I dare claim it's safe to include without a pref. Here's a general overview of why this problem was happening (you may be surprised ): And, some more technical specifics, incl. about where the 2x:xx times come from (this is also included as a comment in the source code): EDIT: Writing this up amply reminded me how much I LOVE making long posts using this board's post editor... BBCode FTW!

LGTM will commit it in short period. EDIT: committed in goanna3 and 4 repo, other repos will be followed later. https://github.com/roytam1/UXP/commit/85149582f1000cd801350ebaa73151872c521d4f https://github.com/roytam1/palemoon27/commit/2d96070f5334a82b3cb3133c822b8ae5a372c411 https://github.com/roytam1/mozilla45esr/commit/bf2771bde24a18e3ab13ead251befca1ac630d7b https://github.com/roytam1/basilisk55/commit/6fd60b08fe3f33fc0c7245427a25251dd6008690 https://github.com/roytam1/palemoon26/commit/a66d2e44121f0684044f86abed116dc1d686d17f

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210731-f94c0da-uxp-620374316-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210731-f94c0da-uxp-620374316-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.8.win32-git-20210731-f94c0da-uxp-620374316-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.4a1.win32-git-20210731-61f3c7277-uxp-620374316-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.4a1.win32-git-20210731-61f3c7277-uxp-620374316-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.4a1.win64-git-20210731-61f3c7277-uxp-620374316-xpmod.7z Official UXP changes since my last build: - [no issue] Replace PurpleBlock with SegmentedVector to reduce indirect memory accesses when calling suspect (738448aa0) - Issue #1781 - Follow-up: fix debug assert in MergeMultiplicativeR() (620374316) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Issue #1875 - Rebrand Help menu item URI from FF to PM. (61f3c7277) My changes since my last build: - cubeb_winmm.c overflow fix by mixit@MSFN, Thanks! This should fix the famous 23m18s freeze bug for audio/video playback. (85149582f)

Fingers crossed. Honestly, unless they're hell-bent on flushing all memory of XP, I can't think of a good reason for why they wouldn't accept this fix. Let's hope Tobin won't have a heart attack if his so-called "MSFN hackers" manage to get official recognition. (Less name-calling, cussing, and paranoid lashing out at people who have been helping their project, and maybe they wouldn't need appeals like UXP development: it doesn't magically happen...) EDIT: If Tobin or someone else from PM reads this: sarcasm aside, I'm actually not saying this to fan the flames of conflict, the point is that it's painful to watch the upstream I believe most of us would ideally like to support and root for make that as hard as possible, and not just for MSFN members, but also a number of those in their own community.

... This is Windows XP SPx you're still talking about , official Mozilla Firefox builds NEVER supported natively the h264 proprietary decoder in HTML5 video; the decoder is patented and its native inclusion in a browser requires the browser authors pay a "handsome" fee to the patent owners (the MPEG4 consortium). Google are rich enough to afford that fee, so Google Chrome comes bundled with that decoder (AVC=h264) and hence it's capable of native h264 playback under Windows XP... When Adobe Flash Player was around, it itself came with bundled h264/aac decoders (again, because Adobe are rich), so MP4 video streams could be played, via that plugin, even in browsers (like Firefox) without that decoder built-in (and XP users, like yourself, were "happy"...). When many video sites abandoned Flash and instead started using HTML5 embedded web players, the lack of h264 decoder in Firefox rose to the surface, again for Windows XP users ONLY... Your favourite OS is deficient in this sector because the vendor, Microsoft, did not equip it originally with that patented decoder, nor a provision was made to add it in a later stage via an update... You see, Mozilla, instead of paying the h264 patent fee, decided to shift the "issue" to the OS itself, so that Firefox could make use of the h264 decoder already present in the OS (as Microsoft had already paid that fee themselves); unfortunately for you, h264 dec is only present in Vista SP2+Platform-Update-Supplement and higher - the way for Firefox to use it is through Microsoft's WMF (Windows Media Foundation) framework, so you can't bring h264 support to Firefox under XP via installing Codec Packs (these are used for DirectX media players, like WMP). The Adobe Primetime CDM (content decryption module) came with a bundled h264 decoder (patent fee paid by Adobe) and as a side-effect (its primary purpose was DRM) it can be used as an HTML5 h264 decoder in versions of Firefox that supported the CDM (off the top of my head, I think it was v47.0-51.0 officially, but v52.0 also works) - again, this is solely for XP... Regarding Roytam1 browsers: New Moon 27 doesn't support h264 natively (on any OS), but you can "install" such support by downloading an additional "package" (lav), extracting it and placing some DLLs adjacent to "palemoon.exe". The UXP-based browsers, like New Moon 28 and Serpent 52, come with a special "kludge", i.e. h264 decoding support is included in the ffvpx third party library (for XP's sake only, the UXP-based browsers can still use WMF's native decoder, if on Vista SP2 and up...). Lastly, HTML5 video decoding in a browser under XP is S/W only, so the video watching performance you get depends, among other things, on the video codec selected to begin with and your CPU; some codecs are taxing your CPU more heavily than others; the higher the resolution/bitrate/framerate, the more your CPU suffers; performance of the youtube webpage alone (which is a literal beast of JS and CSS code currently) depends on the browser engine, CPU, GPU, available bandwidth, CDN you are served from, content blockers, etc. so, while I find these "stats-for-nerds" logs to be of some substance, they have little statistical weight when compared between different setups... The Adobe Primetime CDM requires SP3 for Windows XP... His "log" mentions the av01 video codec, aka av1/AOM, do note AOM != AVC, official Firefox ESR 52 never supported that codec; the codec is, however, supported in UXP browsers via a pref: media.av1.enabled;true but decoding taxes heavily your CPU... PS: @UCyborg 's post appeared in the middle of writing this , he's right, of course, but my post expands on what he kindly posted...

Cool, thanks! And you even gave (ample!) proper credit and everything, quite unlike the "thieving hacker" image certain folks at MCP like to project of you, lol!

Let's see here... Looks like my latest Centaury build uses roughly 6.2 GB altogether, 1.4 GB for the source and 4.8 GB for the "object directory" with build results. This is a release build, debug would be somewhat larger - so let's say 7-8 GB in total. MozillaBuild is roughly 0.8 GB. The full DirectX SDK is 1.2 GB installed (although you really only need a few MB from it). For Windows 10 EWDK based builds (like @feodor2 does them) the EWDK .iso (that you can mount as-is) is 6-9 GB depending on version (getting bigger), but you don't have to install VS and the Windows SDK, so you can still save quite a bit that way. It was pretty funny to see Moonchild arrogantly lecture feodor2 that he didn't "understand how software in general works" because feodor2 didn't want to install all the extra bloat that comes with VS, whereas Mozilla have been using stripped down tools packages since well before Firefox 52.0 that UXP is based on (see the history of their toolchain packaging script). (OK, so they do the install once, but then package the components they actually need and use that package for subsequent builds.) If you did that (installed, repackaged, uninstalled) with the current official MCP requirements for Pale Moon/Basilisk, you'd end up with only 1.3 GB for all the required VS and SDK stuff, huge space savings! You're very welcome Since I don't plan on distributing my own builds publicly, I guess you'll have to wait until @roytam1 and/or @feodor2 merge this into their builds, so quite possibly only until this week-end for Serpent (although they'll likely want to spend a bit more time testing this on their own).

v13 build 2206 rebuild 2 file size == 90.0 MB v13 build 2206 rebuild 3 file size == 70.2 MB login resources have been removed (which also removed Avatar context menu [may bring it back in a later rebuild to use as dropdown for chrome URLs]) @Humming Owl's v12 modfications have been ported to v13 -- no more gstatic connection on First Run --- I have not tested for possible side effects but will report if I do find any all settings pages fit in one 1920x1080 viewport - it always bugged me that you could be three dialogs in, close that third dialog, and the second dialog defaulted itself back to the top and you have to find where you were at, just annoying so I fit all to one page https://dl.dropboxusercontent.com/s/qyyimm3h58r3963/360Chrome%202206%20rebuild%203%20-%20unran%20-%20MSFN.zip

PR submitted! https://github.com/mozilla/cubeb/pull/656

Thanks, man! Ran a quick test on both with MP4, seems to "work for me". Hopefully the same will be the case for everyone!

the change is caused by https://github.com/roytam1/UXP/commit/9e19d368129f7405c09fdddc75c06e1ba46ed10c to add dark-theme support. if you don't like this change and want previous look, you may manually editing <root folder>\omni.ja\chrome\toolkit\content\global\logopage.xhtml and change back the values using left side of commit above for the time being. maybe I can do something more for this. EDIT: a fix has been committed to custom tree. will become available in next build: https://github.com/roytam1/UXP/commit/d6a5a51430ca21c72debe8d7818c6da72969f56f

Most of the complaints I've seen have been on their support site though, not at Bugzilla where the devs would see them first hand. And there never seemed to be that many people joining in and confirming the bug. The point @grey_rat kindly reminded us about would also definitely play a role in this. In any case, far be it from me to absolve Mozilla from its responsibility, I've mostly just been meaning to point out that there have been interfering factors along the way that don't (in this case) necessarily involve full-on Google agents within Mozilla's ranks. Thanks! After I found that it didn't matter if I used an online stream or a local file, I just downloaded a a random longish file VP8 WEBM video from search results, which happened to be this one. As you said, you won't be able to stream it because FF 15.0 can't handle the current HTTPS ciphers, but you can play it locally. (I've got to say, by the time I was finally done with the fix, I was totally haunted by the faces of those debate participants! ) Sure thing, go for it , but maybe wait until people have had a chance to play with your builds? I'd thought of this too, but I didn't want to bring it up before it's been confirmed that the fix works well for everyone. But it'd definitely be a nice subversion to "side load" this XP-specific fix into the current Firefox code via their stand-alone cubeb lib, after they took great care to remove all traces of XP from their main tree! That's an excellent point! It's been a long time since I switched from Flash to the Primetime codec for H.264, so Mozilla's messing around with H.264 and especially its support on XP has faded from memory a bit. Yeah, those watching MP4/H.264 stuff using the Flash player wouldn't see this 2x:xx issue (I think - never tested for it specifically) and wouldn't have anything to report until maybe the last few XP-compatible Firefox versions, by which time Mozilla barely cared about XP any more. And VP8/9, which Firefox supported natively, were mostly available on Youtube, hence the strong association with the site for a long time.

So, won't you tell how it's done? The picture alone doesn't mean anything, this forum is mainly for helping.

That may be it. My version of Office 2010 (which came as an unexpected bonus CD when I bought a copy of Office XP on eBay) is different: Microsoft Office Home and Student 2010. Looks like several users on the linked thread have that version as well. From linked thread: No problem for XP users, of course, but it looks like Win 10 users unlucky enough to have this nag will still get nagged monthly after each update.

Sorry, it was another Firefox version... This is with Firefox ESR 52.9.0 on XP SP3:

Hi dencorso, Thank you for your donation of $25.00. We look forward to improving the forums and stay online with your donation. MSFN Team

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210731-45b8007f3-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210731-45b8007f3-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210731-45b8007f3-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210731-45b8007f3-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1190636 - Replace AutoStringVector with Rooted usage; r=njn (5d287ee81) - Bug 1190911 - Replace AutoIdValueVector with normal Rooted usage; r=jonco (b6c8ce668) (9ff3d301a) - ported cubeb_winmm.c overflow fix by mixit@MSFN, Thanks! This should fix the famous 23m18s freeze bug for audio/video playback. (2d96070f5) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1191529 - Remove JSIdArray and AutoIdArray and replace with Rooted<IdVector>; r=mccr8, r=jonco (9c0d645aa) - Bug 1083752 - Calling Map/Set/WeakMap (without new) should throw. r=Waldo (bd0b31a3d) - Bug 1142279 - DataView should require 'new'. - r=efaust (97ef8ba02) - Bug 1155838 - Fix a build warning on windows; r=till (f9af00bff) - Bug 1129313 - Part 2: self-host MapIteratorObject#next(). r=jandem (b30734a0b) (11b532c45) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1150717 - Test request with no params in the Network Monitor. r=brings (a60e9e8d9) - Bug 1168077 - Remove remaining spidermonkey js specific syntax from browser/devtools; r=miker (c98f20c30) - Bug 1168125 - Fix existing tests, r=jsantell (b1dfa101e) - Bug 1169439 - Pull out marker definitions into its own file, and move formatter and collapse functions into marker-utils. r=vp (17eb24ab3) - Bug 1173654 - Part 1: Add logging methods for SurfaceType and ImageFormat. r=Bas (22f2fa019) - Bug 1169125 - Part 1: Allow sending any DataSourceSurface-backed image over WebRTC and fix failure cases. r=bwc (1fb0def92) - Bug 1169125 - Part 2: Use UniquePtr for scoped delete of yuv data in MediaPipeline. r=bwc (cdb79e201) - Bug 1173654 - Part 2: Use namespaces in MediaPipeline.cpp. r=bwc (311696260) - Bug 1173654 - Part 3: Attempt to GetDataSurface() and convert if sending pure I420 fails. r=bwc, r=jesup (58520b820) - Bug 1173654 - Part 4: Add detailed logging and asserts to MediaPipeline::ProcessVideoChunk. r=bwc (ba08ae5bc) - Bug 1155089 - Part 1: Reset |TrackID| for MediaPipelineTransmit::PipelineListener on replaceTrack(). r=bwc (304fb8703) - adapted Bug 1142688 - Wait for actual audio data on remote side before checking audio sanity. r=jesup,padenot (479f6356c) - Bug 858927 - Move the mozilla::TimeStamp into mozglue. r=glandium (751938e09) - Bug 1166559 - Add documentation for ProfileTimelineMarkers from a dev tools perspective. r=fitzgen (ed1563dfb) - Bug 1141614 - Part 4: Expose cycle collection markers in the devtools frontend; r=jsantell (2eb830de7) (45b8007f3)

AFAIK, Firefox itself only ever used Windows Media Foundation (Vista+) for AVC, which is not available on XP, hence you need a plugin on that OS, but otherwise, Firefox 52.9 can do AVC without a plugin.

@we3fan Try setting media.webm.enabled to false in about:config page and see how it performs. Should only need a reload of the page to take effect if you had a video open before you've set it, YouTube's stats->Codecs will then say avc1. Edit: wait, if you insist on Firefox 52 and my memory is right, you need a plugin that will do the decoding of H.264 (AVC1) streams if you disable the above pref. Disabling it on its own will leave no codec to fallback on that FX will be able to decode.

Right-clink on the playing video, select "Stats for nerds" (or whatever it is called now), and compare between FF and Chrome. Maybe one browser uses H.264 while the other uses VP8/9?

When there was Firefox 15, the video was watched in flash-plugin No problem 23 minutes in VLC or WMP plugins Flash player on Youtube was disabled at the beginning of 50 versions Firefox https://wiki.mozilla.org/Release_Management/Calendar Firefox 52 - Release Date 2017-03-07 07.2017 - When Flash on Youtube was completely removed

would you mind if I submit your work to https://github.com/mozilla/cubeb (credit to you of course)?

Actually YouTube offers several format options for 720p. Format 22 is a single file. E.g. for this video (found formats with yt-dlp, using the following command): yt-dlp -F https://www.youtube.com/watch?v=I79CQUTO5II 22 mp4 1280x720 30 | 852k https | avc1.64001F 852k mp4a.40.2 0k 44100Hz 720p 136 mp4 1280x720 30 | 89.77MiB 723k https | avc1.4d401f 723k 720p (throttled), mp4_dash 247 webm 1280x720 30 | 88.94MiB 716k https | vp9 716k 720p (throttled), webm_dash 398 mp4 1280x720 60 | 108.10MiB 871k https | av01.0.08M.08 871k 720p60, mp4_dash 480p however has only Dash: 397 mp4 854x480 30 | 42.61MiB 343k https | av01.0.04M.08 343k 480p, mp4_dash 135 mp4 854x480 30 | 29.41MiB 236k https | avc1.4d401f 236k 480p, mp4_dash 244 webm 854x480 30 | 32.46MiB 261k https | vp9 261k 480p, webm_dash But note "throttled" in the above output. Maybe that can be the culprit? cc @we3fan

The good news is, there should be a solution for Flash. Seems Adobe is still updating it for the China market. The bad news is, Adobe cripples the Chinese version to only run in China. Plus it has all the government-mandated spyware.... But the other good news is, there's a GitHub project called Clean Flash that removes the region restrictions and spyware! It's all discussed in this thread (at the XP forum, but it applies to newer Windows versions too; I'm running Flash 34.0.0.164 under Win 7): Runs just fine in IE 11, as well as Chrome & Firefox (prior to the most recent few versions; see post for details). Edge appears to be hopeless though.

yes

He's using Persian (Iran) Region and Language format, which causes the detail to display like that.

I've said it earlier but I will say it again for the new people mfplat works without "installing it" you just have to make a folder inside the folder where firefox.exe is and name it firefox.exe.local and throw in there all the .dll files that are in the mfplat archive

There are approved names for different resolutions, and the resolution of 1280x720 is called "HD". Just Google has already got used to changing standards and impose their own. https://en.wikipedia.org/wiki/Graphics_display_resolution

@Hunterw, you can try my suggestion for your screen going off . You need a player that is called "Aiseesoft Bluray Player portable" . Just do not install it ! It's chinese , you've been warned , though I didn't notice anything bad . Block it the firewall , of course ! Also , you need to look for a portable version , then just open it and leave it be . It will prevent the screen saver and your monitor from going off while watching videos in 360 browser or even playing . It was the only solution that worked for me . I do not even use the player itself , I just open when I want my screen to remain on. The suggestion by the member @ArcticFoxie doesn't work for me , maybe because I'm on Vista , not XP. BTW , you're very lucky he didn't go caps-locking on you , lol.

Not much of a music person myself, but yes, though YouTube hasn't been the only source. My sound equipment is rather poor, onboard sound on an ASUS motherboard from 2008 that cost only 70€ and some relatively recent (cca. 2 years) Sony headphones that cost 30€. I also use Sound Blaster X-Fi MB3 on Windows and PulseEffects on Linux. I don't have an exact equal config, it's probably impossible since they're 2 different programs, but they seem to help making things sound better even without digging deep into the configuration. Here be the 3 memorable (for me at least) theme tracks from Doctor Who: 2005 revival theme Series 8 theme The one that started it all, the original, you might say

What kind of a s***-ty thing to say is that. If you don't know the answer then you need not reply.

@mixit. Finally a fix, that's been a problem for a long time. I just tested it again in XP and the usual buffering was around 25:12. No reason for Mozilla not to have resolved it, there were plenty of complaints so they had to know. Probably too busy messing with the UI to be bothered with real bugs and then they wonder why their user base keeps dwindling.

When you have an infinite number of tasks with higher priority, it's practically impossible to find time for polishing things like that so unless the bug is actively causing havoc on significant scale, it may take years before it's fixed, if ever, and in case of commercial software, you probably won't get the version with the fix for free. Mozilla also hasn't fixed slow WebGL in Firefox on XP and this is still an open issue on Linux, where there's also a problem (though technicalities differ).

... Continued here, as being OT for this thread...

Thanks for the detailed answer, @mixit I already have VS 2019 and DirectX SDK installed, part of the reason i'm left with less than 40GB space on the C: drive, lol. Hopefully using another drive won't mess things if/when i try building something bigger (like a browser) sometime in the far future. Still no clue what i'm doing in that damn IDE, especially when a project won't build as is, but needs some fixing first. A simple "make config / make install" or the Arduino IDE come a lot more easier. P.S. there is HttpDisk, which allows mounting iso and disk images over the internet, no need to download several GBs to extract only a few files.

In legacy it has to be imported, and shows 0 of 0 rules applied.

You'd need to rebuild the whole application, replacing media/libcubeb/src/cubeb_winmm.c in the source code. Unfortunately this is not something that can be applied "on-the-fly".

I also encountered a warning by Vista's firewall asking me if I want to block an incoming connection to 360chrome executable file , with v12. I want to note that I have another firewall installed (which is considered to be good) , but it didn't notice anything strange (!) , though it has almost paranoid level of settings. Vista's firewall is good ? I think so, yes. I knew about 360's incoming connections for a long time. I warned about this a long time ago , which could be found at my profile . I just thought they had disabled them already , but it seems no, they are still here.

chrome 92.0.4515.107 on windows vista Thanks:)))))

You should see the list in "Privacy". But as you may have read I have no way to verify with UBO Legacy.

1 - I don't know anything about v13. on "later OS" . The latest for me is Vista x64 and it doesn't have any problems , like I said . Perhaps it's because you're using another version ? Try 1106 "beta", it's good . 2- And what environment would that be ? (specs , OS) What do you mean by "newer OS" , is it Vista and up ? I'm sorry I thought you're on XP , right ? 3- Did you or did you not try to install that cert. pack . I remember I started to get cert. errors somewhere around May 2021 . I installed his pack (without SHA-2 updates) and all problems just vanished . I can't replicate your issues with any on these versions on Vista x64 , sorry. About youtbue , try to change your UA , perhaps your slownees is due to numerous scripts and bloat coming from youtube ? Do you have a good adblocker ? Try using mobile user agent from iphone , maybe ? Youtube will load less scripts/bloat if you're on iphone. Other things to consider , try using 344.xx or 347.xx drivers if you're on GTX.

@XPerceniol , yes , I already told you . I'll give it to you , in fact it's been prepared already . Just shoot me a message .< I'll reply. @ArcticFoxie , give me a chance to reply ! You're bombarding me with questions, I'm sorry , I have a job and/or personal needs , like sleeping. I understand you have lots of energy and plenty of free time , lol. I'll answer later. Thanks for the attention.

DVD quality (at least in the US but probably most places) is 720x480p. I've sometimes heard that referred to as "ED" ("Enhanced" Definition) as opposed to 704x480i, or SD (Standard Definition). 720p (actually 1280x720) is noticeably sharper, but it is pretty much the lower bound of what folks would consider HD.

It's said he got more and more paranoid, with time passing. Then again, he faced all but certain 30y prison time, if extradicted to the USA. IMO, under the circumstances, practicing autothanasia does seem a very racional way of escaping a lot of potential pain. May he RIP! I used his software back in the 90's... at that time it rocked.

I recently started a separate site with more details on the extended kernel. You can find it by searching "eclipse" and the TLD for Christmas Island. But yes, I am trying more invasive methods of version spoofing, which have worked for the .NET Core 5.0 installer, but make Steam think it's offline, while Office has yet to be tested.

The latest version of Seamonkey works with the extended kernel. You just need to extract the installer and modify the .exe with CFF explorer.

I will likely use Windows 8 until the late spring 2024. During that time (between October 2023 until I pull the plug), I hope that Edge is at least supported, so that some sort of current browser is used. Beyond that, my tentative plan is to migrate to an iPad Pro and Bluetooth keyboard combination. Major strides are taking hold in order to make tablets (well iPads) more productive as a PC replacement. I hope that in three to four years from now, those strides will appreciate and make the iPad a suitable make shift workstation. As time goes by, there is less that I need a dedicated workstation for. If I wanted to, I have an older Windows XP x64 workstation that I could use (disconnected from the Internet of course) as an audio editing workstation. That was my old HP xw8200 PC. Time will tell.

Perhaps worth a look, free editor with syntax highlighting etc.: 920 Text Editor https://android.izzysoft.de/repo/apk/com.jecelyin.editor.v2 https://play.google.com/store/apps/details?id=com.jecelyin.editor.v2 I see it's now 5MB, but when I installed mine four years ago it was just 1MB. That version runs quite well on my old 0.5gb phone.

Use Easy BCD and forget about to change anything manually.