Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/10/2025 in all areas

  1. I removed in all batch files the PowerShell commands for downloading and extracting the yt-dlp, youtube-dl and ffmpeg archive files. As a replacement, I added wget.exe for downloading your releases respectively @Reino's release and 7z.exe for extracting the downloaded archive files. Then, I rewrote the corresponding code in different batch files. Now, all batch files for updating work again under Windows XP. The yt-dlp, youtube-dl and ffmpeg archive files are downloaded, extracted and then removed including all unwanted files. So, your yt-dlp can be checked by the -U option at any time. After checking for updates, I added an option to decide whether an update of the yt-dlp file or the youtube-dl file should be carried out or not. Now, everything is running the way I wanted it to. Project finished.
    5 points
  2. 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.
    4 points
  3. ESR 128.8 is out, as is r3dFox 135 https://github.com/Eclipse-Community/r3dfox/releases/tag/v128.8.0-hotfix
    3 points
  4. I removed in all batch files the PowerShell commands for downloading and extracting the yt-dlp, youtube-dl and ffmpeg archive files. As a replacement, I added wget.exe for downloading your releases respectively @Reino's release and 7z.exe for extracting the downloaded archive files. Then, I rewrote the corresponding code in different batch files. Now, all batch files for updating work again under Windows XP. The yt-dlp, youtube-dl and ffmpeg archive files are downloaded, extracted and then removed including all unwanted files. So, your yt-dlp or youtube-dl can be checked by the -U option at any time.
    3 points
  5. 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.
    2 points
  6. What makes you think so? It's September - golden season! People are on vacation, nothing unusual. How did it run 360Explorer? I guess it was a nightmare?
    2 points
  7. Yes they did, I predicted about Win 7 (which is the topic here!) and 8, 8.1 (which is the topic's subject in the thread I made my predictions).
    2 points
  8. @Tihiy Thanks for Fixing the previous bug with touch Input. I found another bug, when I change the orientation of my x380 yoga the taskbar symbols getting wider and they stay like that until I reboot or login again. Best regards
    1 point
  9. Starting with 2012, probably not. The only real issue would be in regards to hardware or software capability. And it depends on what you mean by a daily driver. If you mean just using the internet, then no issue will be had. If you want to play games, that may be an issue with certain aspects if they (or the video/sound card) do not support the Server version. I think around 2012 to now, Windows Server is less transparent vs client, meaning most programs don't know any difference. But also in regards to using an old Server OS like 2008 R2, you are going to run into the same issues as equivalent client OS in regards to security certificates and TLS.
    1 point
  10. Indeed so, but if an 'experimental' feature is actually breaking sites, I do hope that gets addressed!
    1 point
  11. Why do I report here in terms of my ytBatch for Windows XP mod? I have decided to make my mod available for all users. Since YouTube Downloaders compatible with Windows XP are rather rare and ytBatch is simply great, everyone should be able to download YouTube video or audio files in Windows XP. Especially when such great releases are made available by @nicolaasjan. Everything can be set in ytBatch for a very individualised media download. And ytBatch is very light in consuming resources and very fast. When my test phase is finished, I will publish ytBatch for Windows XP here in this thread. Greetings from Germany, AstroSkipper
    1 point
  12. It's bigger than that! The "problem" is that the author set a flag to ENABLE EXPERIMENTAL features to make v126 compatible with web sites requiring v13x. But then KEPT that EXPERIMENTAL flag ENABLED in v132 (enabling EXPERIMENTAL features that will not become stable/vetted/good until v135, or v138, or v140, etc). THIS IS A PROBLEM for folks thinking their browser is "secure" because these EXPERIMENTAL features are designated as EXPERIMENTAL for a reason!
    1 point
  13. How do you do let it check for a new version? The XP version is a zipped exe, so it can't be updated with `-U` from within yt-dlp... (I guess I could provide a plain exe file, but then all the links that are already floating around on the web will be broken. )
    1 point
  14. 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!).
    1 point
  15. On GitHub, I found a nice Batch Script for downloading Audio and Video using yt-dlp or youtube-dl and ffmpeg. It is called ytBATCH. I have already configured it to my needs, and it works great under Windows XP. Whatever yt-dlp option is needed can be easily added to a config file. All preferences which have been set inside ytBatch are stored in config files. Once, all has been adjusted, you only need to insert the YT-link and to select V for Video or A for Audio. Then the file will be immediately downloaded. I use the script with @nicolaasjan's yt-dlp/youtube-dl releases and @Reino's last ffmpeg release. Now, my downloaded video and audio files also contain a thumbnail and metadata.
    1 point
  16. Keyword is "suggested". VistaLover would have to stop back in and tell us if he is or is not enabling/disabling. Until then, we should not be "guessing" VistaLover's configuration. As a test, we could revert the flag and add this polyfill. At the very least rule out one of the flag features. https://glitch.com/edit/#!/close-watcher-demo?path=polyfill.js
    1 point
  17. So, which is the culprit here? I guess whichever it is, it's in version 132 as well. As an aside, double negatives always annoy me because they can so easily cause confusion. Having a flag which has to be enabled to disable something for instance!
    1 point
  18. For British Gas try setting Disable Experimental Web Platform features to enabled.
    1 point
  19. Hi. Is there a possibility you reconsider and use an ISO with SP2 already integrated? Nlite doesn't want to be friendly with the 64bit version, it's to be expected.
    1 point
  20. I'm sure it's a good decision, we'll see how far it will help. I remember it all went downhill very quickly after 110 (which can be ported to windows 7 and Vista). I think things will get real ugly after or even in 120. I don't want this to be a prediction, there are people who are obviously not that happy when my predictions become true. By that time, I hope you will make a new topic about the "Future of Chrome on Windows 10".
    1 point
  21. jaclaz, I'm afraid I have to disagree about the term "generic", some time ago I was asked a specific question, I clearly predicted it about the memory function. Not just , "hey, guys, I know Chrome will soon not work". I think you're confusing me with someone else. Regards, Dixel.
    1 point
  22. Good to know! But for how long? From what I observe, the development (of adding bloat) is at the speed of light lately. Opera added AI since 101, and so on.
    1 point
  23. I once had a problem with a bad USB3.0 cable, it was wobbly and very thin (WD Elementals 8TB plastic box), I replaced it, and all works fine since. The error was similar, Windows told me: small files couldn't be deleted (protected).
    1 point
  24. I already predicted it would have happened (link), I'm not surprised, even though folks wrote their chrome still worked on the old Win 10 at that time. So looks like now 1809 is the new bare minimum, link. And like I said before. the whole memory function would have to be replaced to be able to run on such old versions, link. This would explain the delays with the Chinese forks of Chrome for Win 7. Each new release will be harder and harder to port, so build from scratch is the only method left. As you all see, I could be the new clairvoyant, in addition to @D.Draker, I think I don't even have to mention, @jaclaz's half-functional (maintenance mode?) crystal ball is already mine.
    1 point
×
×
  • Create New...