Leaderboard

Chrome at default would have a "default" setting for that flag. I'm pretty sure I saw Vistalover wrote many times about that flags and advised to try them. Something tells me Dave listened to VistaLover and turned that experimental flag on. Let's tag him, probably he's just shy or ignores. @VistaLover

The screengrab doesn't show the exact error. Check Unity DLLs with Dependency Walker.

If you can't click it, then it's broken ... That's the problem when total convenience has taken hold, knowledge does no longer exist and thinking is far too strenuous. And modern operating systems, which do everything for the user, including AI, are also responsible for users' ignorance.

If you try the option --config-locations "c:\\Portable\\3D Youtube Downloader\\yt-dlp\\config.txt" then there is no error about "unknown escape sequence" but I didn't get a thumbnail, either. You may report to the developer that the extra arguments do not have any effects.

Look's like CloudFlare nightmare soon may be over, Pale Moon community reach out to press and CloudFlare team apparently noticed they negative coverage in press: Moonchild wrote: The Register article title is hilarious: Cloudflare's bot bouncer blocks weirdo browsers We finally know what browsers we using - a weirdo browsers.

Yes, but you only sent one, you gotta research the huge script British Gas has in .js. Otherwise, how do you explain the site works for @VistaLover on the same version??? I know, VistaLover took steps to block them.

It does not require VxKex or other kernelex to work. Firefox https://github.com/e3kskoy7wqk/Firefox-for-windows-7/ https://github.com/e3kskoy7wqk/Firefox-for-windows-7/releases Chromium https://github.com/e3kskoy7wqk/Chromium-for-windows-7 https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases

For Integration into offline Windows 11/10 images only, not to be installed on a Running/functioning Windows 11/10 OS! I will provide updated defender cabs on the 1st, 2nd, 3rd and 4th week of the same month, always on a Tuesday. Updates will be available from this first post only. Credit goes to members on My Digital Life Forum:- abbodi1406 for signature blocks in the Windows Defender Integration Tool script. And for providing direct download links for the beta platform updates. Enthousiast for pointing out the missing files, letting me know about new platform updates and for testing the new defender cabs. AveYo for creating a verification tool that checks the digital signatures of files inside the cabs, to make sure they are valid and not tampered with. This script has been updated to support arm64. drew84, Stripakulina and Enthousiast For providing direct download links for the x64 beta platform updates. atplsx for providing the direct download links to pre-release platform updates. ---------------------------------------------------------------- To integrate the updated Platform and Anti-Malware definitions into your Windows 10/11 offline images, you can use the tools below:- 1. Windows NT 10.0 Updates Installer v10.53 - Tool created and maintained by abbodi1406 2. UUP to ISO Converter v114f - Tool created and maintained by abbodi1406 3. Defender files Verification Tool v2.1 - Tool created by AveYo, Updated by AveYo and steven4554 ------------------------------------------------------------------ Details Released: July 15th, 2025 Next Update: July 22nd, 2025 Defender: 5.6.2506.5 Engine: 1.1.25050.6 Platform: 4.18.25050.5 Version: 1.431.649.0 x64 File Size: 212.3MB / SHA-1: 13053A384B823502090BB87E7B18B309C62A28B5 arm64 File Size: 210.4MB / SHA-1: EF89CDCD935D5255081846C7E5DE2A05D38824C1 x86 - (This cab is for Windows 10 x86 only!) File Size: 206.8MB / SHA-1: F02B77F600C2165A2C308C38E8A5C021E61CF806 Defender cabs can be downloaded here: https://mega.nz/folder/S8xknZDK#heADKKYAv9w2HUQV6s8Ntw Download the previous two versions of supported defender cabs:- https://mega.nz/folder/C4h3TALT#sD9qhmluImsDV7YGhpBADg Please Note - Defender cabs (x64, arm64 and x86) will continue to be updated until end of the Windows 10 ESU programme. Users that are running both Enterprise editions of LTSC 2021, defender cabs will continue to be made for x64 until end of support of both SKU's. As for x86, I will continue making cabs until end of support date of the LTSC Enterprise 2021 version. Which is on January 12th, 2027!

I have 'normal' Chrome v122 and 'normal' Edge at work. Both of them display the identity page correctly. Unknown version of Edge (company IT updates it often). I can prevent company IT from updating my Chrome v122. I also can *not* run any Ungoogled at work. I can only run Official Chrome or Official Edge. But have more control over which version of Official Chrome. I've tried over a DOZEN different forks of Chrome/Chromium v126, ungoogled and normal, clienthints enabled/disabled, different useragents, comparing flags/command switches - this really is something that is *ONLY* happening in Supermium R6 and higher. It is not flag-related, it is not client hints, it is not user agent, it is something in Supermium R6 and higher that DOES NOT EXIST in any other v126. It would be one thing if a flag or command switch solved this in OTHER v126's also, but again, this is something that is happening *ONLY* in Supermium R6 and higher (requiring a flag to fix). Again, it would be one thing if Browser X v126 was effected and it required the flag *AND* Supermium R6 v126 was effected and it required the flag. THERE ARE NO OTHER v126's THAT NEED THIS FLAG TO RENDER THAT PAGE. NO OTHER CHROME FORKS ARE EFFECTED. NONE! Okay, none that I can find (there are a LOT of forks!), and I spent all weekend HUNTING. This is something *ISOLATED* to Supermium R6 and higher.

I also used the Open With extension in the past. It is indeed a nice extension. ytBATCH is not only one batch file but a couple of batch files. I changed the code of some batch files to avoid PowerShell commands which do not work under Windows XP. Now, ytBATCH is able to download the most recent versions of @nicolaasjan's yt-dlp and youtube-dl releases, and @Reino's last ffmpeg release, by itself. And here ytBatch's Preferences: And this is the main window where a command or the YouTube link has to be entered: This script collection is cool.

Supermium R6 and higher is BROKEN. Users should consider R5 as the most-recent working version of Supermium. Creator should be brought to this attention at GitHub (will not be by me!). Out of the box, no changes, R5 works (for cited web site) in XP and in 10. Out of the box, no changes, R6 does not work (for cited web site) in XP or in 10. R5 and R6 are both v126's and I cannot find any other Chrome/Chromium v126's to not work for the cited web site. This is a Supermium R6 and higher issue ONLY. It's not going to "go away" in new releases without the creator addressing whatever he introduced in R6 and is carrying over to everything newer. That's the best I can gather, at least. I really strongly and wholeheartedly feel this needs addressed at GitHub (again, will not be by me!).

PowerShell 7 on Windows Vista Extended Kernel done properly So here's how to install 64-bit PowerShell 7 on Windows Vista with Extended Kernel. You MUST use EXACLY version 7.2.2. If you want to know why is that, go to the section why 7.2.2?, but for now here's a Quick step-by-step guide: 1. Install Windows Vista Extended Kernel October 2022 x64 version if you haven't already (only x64 files are needed, less stable x86 ones not required) https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/ 2. Download zipped version of PowerShell 7.2.2 (PowerShell-7.2.2-win-x64.zip) from GitHub https://github.com/PowerShell/PowerShell/releases/tag/v7.2.2 3. Extract it somewhere, from now on this somewhere is assumed to be "C:\Program Files\PowerShell\7\" so that the path to the main executable is "C:\Program Files\PowerShell\7\pwsh.exe" 4. Add this to your osver.ini in C:\Windows (if it's not there create it) [C:\Program Files\PowerShell\7\pwsh.exe] Enabled=1 MinorVersion=1 5. Add "C:\Program Files\PowerShell\7" without quotes to your system Path. To do that go to ControlPanel -> System and Maintenance -> System -> System Properties -> Advanced (it's a tab) -> Environmental Variables. Look for the Path variable and add the aforementioned path to other things after a semicolon ( ; ), thats how things are separated there. 6. Download and unzip this special shortcut https://forum.legacydev.org/viewtopic.php?f=27&t=231 and put it in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell" so that it appears in the start menu next to the old-school WindowsPowerShell. You can also put it in "%appdata%\Microsoft\Internet Explorer\Quick Launch" to add it to quick launch. The 2 things that are special about the shortcut I've made are: It launches cmd to launch PowerShell, which is a workaround to a problem with 7.2.2 more in why 7.2.2? It behaves like a WindowsPowerShell window, so it has a range select feature and the iconic PowerShell blue color. 7. Enjoy Why 7.2.2? So you could just install 7.2.17, 7.2.24 or any other newer 7.2.x version, and it would work fine... mostly But sometimes those versions hang on startup and never launch staying in a non-functional state which even takes a few seconds when you decide close it. On some machines like 9/10 launch tries are successful on some almost none. There are even reports of this occurring on Windows 10: https://old.reddit.com/r/PowerShell/comments/v6arrr/powershell_72x_almost_always_hangs_when_launched/?rdt=40615 https://github.com/PowerShell/PowerShell/issues/17558 But I've managed to reproduce this issue only on Windows Vista machines and multiple ones. 7.2.3 and newer as well as newer 7.1.x like 7.1.7 are affected by this issue on Vista 7.2.1 and older as well as older 7.1 and 7.0 on the other hand just fail to launch at all showing a Failed to initialize properly ... smth error. So if it wasn't for 7.2.2 you would have to go back to PowerShell 6 to get a working version But 7.2.2 has it's own issue where it sometimes immediately closes after launching an exe. Fortunately it doesn't do this when launched from another command line tool, that's why it was necessary to make a shortcut that launches cmd first and pwsh next

default build is already SSE2-enabled build

Please don't beat me up for digging up this topic! I was messing around with Windows 2000 on an old PC and noticed there was no entry on the registry for running "welcome.exe" anywhere, and a Google search only shows this topic without an answer, so... I fired up Process Monitor v2.8 (requires SP4 and Update Rollup 1) to figure out what would change in the system when I unchecked "Show this screen at startup" on the welcome.exe window, and the answer to the 1st post is: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Tips: Show =1 launches welcome.exe, Show = 0 does not launch welcome.exe.

... Might be related: https://forum.palemoon.org/viewtopic.php?f=17&t=32150 ... or not ; FWIW, it works here right now, so you may need to resort to a Europe-based VPN node, if available of course ...

If the e-mail-address is still the same, then it's "3DYD Soft Support <support@3dyd.com>". A couple of times, from 2017 until 2020, I've had mail-contact with a guy named Nick for some issues and feature-requests.

I was always able to check spelling and had an option to check it before sending the message enabled. Now it just says that spelling is complete, even if there are misspelled words!

DreamMail Pro - Update information! DreamMail Pro has been updated again and is now available in version 6.7.1.8. It is still XP-compatible, and the development is ongoing! I have not been able to find a version history on their homepage. Therefore, I generated an official version history translated to English and provide it here: And here is the download link of DreamMail Pro 6.7.1.8: https://download.cy-email.cn/dmpro_setup6.7.1.8.exe To force the updated installer of DreamMail Pro 6.7.1.8 to use English instead of Chinese as the installer language, I updated again my small loader that does this when it calls up the setup program. It must be executed in the same directory in which the setup file is located with its original file name dmpro_setup6.7.1.8.exe. Here is the download link of my loader Force_En_Install_DM_Pro_6718.exe: https://www.mediafire.com/file/7qb6k0l2lohhse1/Force_En_Install_DM_Pro_6718.7z/file Although some virus scanners detect this file as malicious, it is just a false-positive as always. Use my loader to force an English install, only if you trust me, of course! Cheers, AstroSkipper

You're welcome. What I like about DreamMail Pro is that they still seem to maintain compatibility with Windows XP. This is rarely the case these days.

And what about that? Did you already try to insert your custom argument there? You can get there by clicking on Options in the main window.

Screengrab the error and post here. Unity can be made working without the need of that Kernel.

ClimetHints are requested via javascript from you, not sent from that side, lol.

It only confirms what I already explained. Supermium transmits a lot of sensitive info, including the OS, whereas in Chrome 360 ClientHints are switched off. In CentBrowser and CatXP, too. So no problems with them.

Windows going down since abandoning original Longhorn, but windows 11 is "Nightmare on the wings of the night".

No, it's not Finita. Just use torrents as i said before. I will send you links in PM. This is how i watched in 2017 - torrents. P.S. 720p is not low definition. It is HD resolution, also i admit that YouTube low bit rate and mediocre AVC Main Profile 3.1 encoding make it look bad.