All Activity

Don't the standalone Linux builds work (they have newer Python embedded)? yt-dlp_linux or (for 32bit) my yt-dlp_linux_x86.

For the latest version of yt-dlp (2025.10.23) i had to update even my oldstable Debian 11 system (from 3.9 to 3.12.5 - as described nicely here). A little bit complicated and CPU-intense, but it seems to work: yt videos now downloading again without the 403/permission error. Cordial thanks @nicolaasjan and all the other developers!

Yes, there is always at least 1 disk (the system disk) present in the BIOS (it's bootable). There might be something else besides it. I'll check it out.

Thanks, this is what I need. It works (and it's even EMM386 compatible). Amazing work! I haven't looked at GCDROM.SYS yet.

Are you getting the below "consent" dialog? Or have you at least gotten it in the past? If not, maybe this "consent" dialog is not working in New Moon so everything else is "Googleismed" as unreadable.

Is something else on this AHCI controller? Especially BIOS controlled drives.

What is going on on Euronews? I get a page full of unreadable plain "binary" text in New Moon. Is the website somehow appified and not HTML based anymore? https://www.euronews.com/my-europe/2025/10/22/european-parliament-rebels-against-simplified-sustainability-requirements

@VistaLover The Windows 7 builds are the only ones I had published until posting in this thread. I also have Vista specific builds locally as I still run Vista x64. If you are not looking for a shared build of the XP version, I may be able to put something together in a 32-bit shared configuration that targets Vista. If you are willing to test? This would be XP incompatible, so Vista and up.

I'll the Deno thing if there is a package for download that doesn't require much command-line wizardry. I can download sometimes today, but I don't know how to get the format number that always works. "96-12" only works sometimes. https://i.imgur.com/SWaCvoO.png

It appears to me, that the last Kxproject driver (outside of community efforts) is 3550. There are earlier versions that work on Win98se and newer. Has anyone tried, or had any luck, getting/fudging newer versions to work? The driver/utilities source is available, now; so I can play around, at my leisure. However, my aim will be to get some functionality in Win98FE. I may decide it isn't a good aim :) I thought I should ask "here" before digging around, too much.

You are no novice user, so I assume most common questions aren't needed. For the sake of any novice, reading this thread, if you type C:\EXIT nothing happens? What happens if you use ahciwrap.sys or GCDROM.SYS? That may help eliminate that the issue is specific to rloew's driver. I'm not a huge user of cd-roms "in any O.S." with that said, the error exposes that the driver's disc filesystem functionality is blocked/unavailable; or now unable to recognize the data it observes it. Maybe, it could be the use of an updated UDF filesystem or other updates/patches; perhaps to the bit access of the drives and their controllers. A change/patch, when Windows loads, may be keeping something persistent, at the hardware level, in so doing "maybe" preventing the media from being recognized; after returning to DOS. I do think my reply is a placeholder, until someone else comes along. But you never know, as you are a competent user, maybe something here will help trigger a thought of your own. Looking forward to seeing this pan out for you.

Yes, I had to figure this out on my PC recently also, as a taskbar on one of my monitors stopped hiding. Are you by chance also running DisplayFusion, like I am ?

In the case of ffmpeg, as I use for more purposes, I use upx to reduce the disk size to around 50% on each file. In terms of run time, it doesn't make to work slower. Give it a try: https://upx.github.io/ (Don't worry to use old versions, I use an old 3.x)

Also having this on both home and work machines with KB5065789 installed, the supposed fix in 3.5.16 seems to have only partially addressed it; the partial fix stopped it from happening permanently no matter how many monitors you had plugged in, but my 2nd/non-primary monitor always has the transparent taskbar until I hide then rehide again. Would love to provide any logs/dumps or test fixes if possible!

Many thanks, indeed ; my OS is actually Windows Vista SP2 32-bit, my CPU can go up to SSSE3 instruction set, iGPU; so, I have to make do with XP-targeting builds ... I see the linked files are hosted on VideoHelp.com and, after searching, found out you do have an account on: https://forum.videohelp.com/ Is there a specific FVH.com thread that you announce/publish your FFmpeg XP/Vista builds in? There's https://forum.videohelp.com/threads/414767-ffmpeg-7-0-1-and-Windows-7 but, as one would expect, the 32-bit compiles posted there do not run on Vista SP2 32-bit (as they target NT 6.1 +) ; I know it'd be a lot to ask already, but do you see yourself publishing shared FFmpeg_x86 builds compatible with Vista SP2 / XP SP3 ? yt-dlp actually wants BOTH the ffmpeg.exe+ffprobe.exe binaries for postprocessing; static builds of them have now exploded to ca. 110 MiB each, I find it too much to use 220 MiB of disk space just for remuxing purposes ... Thanks for your efforts so far, much appreciated ...

I just read the external JavaScript requirement and... I think I'll give up using it from here. They say that a headless browsers defeats the purpose of yt-dlp, but... an engine over a hundred MiB, a half of Firefox 115 installation doesn't? Come on... I might regret and come back to yt-dlp again, but I think I will switch to the nightmare slow downloads from web download helpers. It is more sane, from my point of view. I'm expectant for the upcoming events...

That'll be my next move. What you're saying is somewhat proven by what jumper pointed out to me at the beginning of the thread. I tend to think it's a good idea to update to the latest drivers because doing so in XP and Windows 7 always gave me better performance with no side effects. I think it would be safe to use drivers with release dates close to the OS's. Supposedly tests were done at that time and everything worked. So I think I'll have to look in that direction or settle for Windows 10 hoping this problem can be fixed. Having a stable 11 seems like a distant luxury.

Or maybe it's the firewall. When it failed using TinyWall I was happy to think I'd discovered the problem. With GlassWire -Windows firewall- everything seems more stable but now this is happening. I appreciate all the info. Maybe that's why so many people complain about 11 and speak highly of 10. I also had a more stable experience with 10, although the error also occurred when using TinyWall (the adapter connected but couldn't navigate). Perhaps, as beautiful as 11 looks, the jump is simply too large causing an insurmountable incompatibility issue. XP still feels like a reliable system for every day use. 10 doesn't feel exactly like that but close. 11 feels insecure as if it could fail at any moment. I've tried several Linux distros and liked them but there are still no drivers for some of my peripherals including this Wi-Fi adapter.

My wireless adapter drivers are all dated 2013 thru 2015. Once I find one that works, IT NEVER GETS UPDATED. I often intentionally attempt to track down OLDER and never newer.

It doesn't happen in my Win10's either! *ALL* (minus a garage laptop for tuning turbo engines) of my computers now run Win10. They *ALL* ran XP as recently as only two years ago. THEY ALL PERFORM LEAPS AND BOUNDS *BETTER* ON 10 THAN THEY DID ON XP !!! But a "debloated" 10, obviously. And I'm talking real quantifiable metrics, not some "gut feeling placebo effect". BUT they are *all* stuck at Win10 21H2. At least until the day I can "debloat" newer to also perform BETTER THAN XP. All (except one) of my computers are 15yrs old or older. Granted, that one exception is less than 2yrs old, but it too runs Win10 21H2 (and gets an ocassional Linux every once in a while, only to return to Win10).

Never learned how to use virtual machines and when I tried I found it too difficult. I also don't fully trust the virtual experience. People who use it always say that while some things may work others may not and vice versa, so I prefer to experiment directly. SSDs don't suffer as much wear and tear as mechanical drives so I prefer the real thing and create images so I can always go back to an acceptable point. What happens is that just when I'm downloading a big file at full speed and the adapter is really working, the connection fails (beyond the indicator on the tray). The connection completely drops and I'm forced to disable Wi-Fi and then re-enable it from the net system's settings. I find it inconvenient that Windows now manages all of this. Before, the driver came with a dedicated factory manager that did the fine work. Now you have to trust Windows and these things happen. It could be a thousand different things. This PC is from 2010. To be comfortable I have it overclocked. I know the limits and don't stress it out but maybe that's the problem. Or maybe it's using the latest driver. Or maybe these stripped-down versions are missing something that contributes to the stability of the connection. Perhaps some software introduces stuff causing incompatibility that's dropping my connection. I'd have to run a lot of tests to find out what it is... but this doesn't happen with XP. This adapter is able to broadcast/share Wi-Fi and since the signal here is weak -which is why I wanted a wall breaker- it's convenient for me to provide a signal to my cell phone from it and I've also noticed that when I activate it the connection drops after a few seconds. It's as if the adapter is too "sensitive" so when I push it a little it fails or Windows fails to manage it. Or maybe it's the overclocking.

I have this problem on both of my computers now. Might be related either to high contrast or high-DPI mode (or both, both machines are set up very similarly, with 3 displays, centre being primary).

Hello. I've encountered a problem where the CD-ROM works fine in early DOS (before WINDOWS starts), but stops working completely in late DOS (after exiting WINDOWS). Regardless of when MSCDEX is loaded, attempting to access the contents of the CD results in the following error: "CDR103: CDROM not High Sierra or ISO-9660 format reading drive J Abort, Retry, Fail?" I am using the AHCICD 1.1 driver (By Rudolph R. Loew) + MSCDEX 2.95 (By Microsoft Corp). In CONFIG.SYS: "DEVICEHIGH=AHCICD.SYS /D:OEMCD001", and to call MSCDEX the line is used "MSCDEX /D:OEMCD001 /L:J" (AUTOEXEC.BAT or other place). Have you already faced this problem, is it possible to fix it? Thank you.

NEW VERSION: Diffinity v0.9.5 (2025-08-25) is out at http://truehumandesign.se/s_diffinity.php Frontpage updated.

ps - what are your inidications that your wi-fi is dropping out? In newer Win10-and-newer, you can't "only" go by the wi-fi ICON next to the clock. I have witnessed situations where the ICON simply isn't "updating" but the wi-fi *IS* connected. In my situation, it was when "startup services" were DISABLED, so the icon didn't think it was connected. But then as soon as a web browser started doing anything, the icon would then update and properly indicate that the wi-fi was connected.