D.Draker

Thanks, I finally got through by using a good VPN, now upon choosing a low definition 720p (.mp4) file, it redirects me to a page with an "app", but then it says the "app" doesn't work with Vista! Finita la comedia, I guess.

One can get tired of exporting one by one very quickly. Let's see, There we have often cases where pics and videos are stored at another website, so even if you export the main (root) website cert, the pics will show empty, the browser will prevent the off-site untrusted (un-certified) connections. Last but not least, many modern AV scanners use your cert store to check the sites and/or your browser's executable. As we see, Tripredacus uses official browsers, perhaps he uses such AV software, too.

This time I agree, the engine is too bloody old anyways. Don't waste time.

Tripredacus is on Win7 (most likely the reason this long abandoned OS is still stuck at the current MS products on MSFN board), the question is only about Win7. How XP is relevant? But I'll answer, for Firefox it doesn't matter which system you run since it has its own cert store. This became the case with newer Chrome, too. But Chrome can use the NT6.0+ local system cert, in addition to its own. Not sure how good this would work on XP. And XP usually fails because it simply doesn't support modern encryption. So you could install and over-install, it will still show no green padlock on XP.

In older Firefox they were also duplicated in your profile directory. Certificates were stored in cert8.db file. Their corresponding keys were stored in key3.db. Probably the case with the new versions, but I don't use FF.

How is this related to what Tripredacus asked? Certs can expire at any time, on some sites I get expired on a new, fully supported and updated browser. @Tripredacus, On Windows 7 and Vista they also have their own Windows Cert Store, which supposed to be updated automatically, but then again, you probably blocked the auto procedure, just like me.

And now for those who love to live by the book. https://support.mozilla.org/en-US/kb/setting-certificate-authorities-firefox

Why such over-complications. lol? Wouldn't it be simpler to just move the whole cert folder from the new Firefox version?

Good idea, but he needs to do it after he tests with 7 or Vista ISO.

None, those can't be trusted in testing your hardware. I had several cases where my RAM passed all tests with flying colours, running from there, then failed with booting Windows.

What exactly you didn't like in my reply? Why do you integrate USB3 into an ISO for a 20 years old DDR2 LGA775 machine? It doesn't have them! So, my advice is to take the original Vista or 7 ISO and try to install so you would be sure your disk is fine. BEFORE you proceed with XP.

You mean the one you stuffed with custom made drivers using the dreaded NLite? https://msfn.org/board/topic/186694-kaby-lake-sata-storage-drivers-for-windows-7/page/2/#findComment-1278071

Friend, in as much as I want to help you, I can't. Never encountered such problems with Vista. I don't have 8.1, and here we have only one true 8.1 fan @Jaguarek62, as far as I know. Did you try different drivers?

Didn't work for me, so I used the Gigabyte tool I mentioned earlier + the official Intel drivers, why would want to use un-official, if there we have Intel certified drivers? Are they faster? I'm just curious, nothing more. I'm trying to broaden my horizons.

Is this question somehow inconvenient? I'm just curious, nothing more. I'm trying to broaden my future browser path. One example, CatsXP supported XP up to Chrome 87 (or so), Chrome 87 is far more advanced than FF 68, yet CatsXP had a fully working sandbox under XP, how so? And CatsXP still has a working sandbox under Vista.

And the dude here wrote you globally disabled the sandbox. Why? https://sourceforge.net/projects/r3dfox/files/v133.0.4e/

Firefox has a sandbox even for the outdated, initially unsafe and poorly implemented garbage like Flash. Flash was supported with XP for like quarter of a century, what Windows 10 are you talking about? "Firefox has a sandbox for some plugins like Flash, and it has a sandbox for media decoding plugins and DRM plugins. These are all enabled by default." It's from a decade old article. https://support.mozilla.org/en-US/questions/1111998

Yes, I understand about one "not designed for single process". And what about the other 99.999999% of users that have at least a dual Pentium?

Terrible article. The main info is missing! In which version they started to force it?!! Not to mention the author's terrible English.

First, it's 5 years, not 1. The browser has a 2020 engine, it was released in 2020. Second, no, and I quote: "I WILL NOT BE MAKING IT PUBLIC". Source: https://msfn.org/board/topic/186346-i-moved-to-centbrowser-i-feel-happy-about-it/page/5/#findComment-1277544 My humble opinion about that: https://msfn.org/board/topic/186346-i-moved-to-centbrowser-i-feel-happy-about-it/page/6/#findComment-1277577

You want to say, in the original Firedox 68, sandbox doesn't work, too?

Installing and running Nvidia driven card helps certain browsers that would otherwise fail to run with sandbox.

https://www.ncesc.com/gaming-pedia/what-is-the-no-sandbox-command-in-chrome/ "The sandbox is a security feature that isolates web pages and applications, preventing them from affecting other parts of the system. Disabling the sandbox is sometimes necessary for development purposes, such as redirecting stdout to disk when the sandbox would otherwise prevent writing data to the disk. However, it is not recommended to disable the sandbox when surfing the web, as it can leave your system more vulnerable to security threats."

Wait, what? No sandbox!? Geez! And what if it runs on Nvidia driver? It doesn't work, even in this case? I'm just trying to figure out why no sandbox, the reason, as it's considered to be a serious security flaw.

It's what agendalists stuff in your brain, it's not your problem, ignore everything what is not your problem. They off-load their work on civilian population. EDIT. You need to fight the depression with fun, we talked about it.