Leaderboard
Popular Content
Showing content with the highest reputation on 06/16/2026 in all areas
-
Possible. But I'll let somebody else undertake that endeavor. I prefer the WinReducer EX-100 route over the winntsetup route.1 point
-
I'll paste into a "spoiler tag" here and see if it works. It's part of my Phase 2 process so I'll post that shortly.1 point
-
That's not the portable version that I use. I don't have the source for mine at the moment. I'll compare the two one of these days. So far, I'm happy with the one that I am using. It too has an "updater" and it too uses "chrome++" (which has never really worked 100% in any Edge variant). And I'm not familiar with the "chrome-next-mini" enhancements that this one references. Personally, I generally "boycott" anything that a MARKETING department gave the name of "enhancements".1 point
-
A new version of Watler's Win3x HDA-driver already: HDADRV9Q Download from: https://watlersfiles.netlify.app/ New: software volume; possible to set volumewidgetmax in HDACFG.INI, section Volume (default is $007F007F); four HDA-controllers added with auto-setting of pcipatchB; pcipatchB should be supported in HDAICOUT.HDA too; Export of functions sglinf, setbvalue and strlog (API).1 point
-
if u got the proper scripts, which Virgus and I have written so far (a couple of years now) and can be further and better engineered by those who are cleverer than us, u can do a lot more with a lot less space than is occupied by ur systems, I am sure. wanna cooperate?1 point
-
Well done this is coming along great! Tested on 7 machines: Lenovo S20-30 Laptop, Realtek ALC280 - 8086_0F04 / 10EC_0280 - headphones/speaker interchange working - reboot required for volume control Lenovo S10-3 Laptop, Realtel ALC272 - 8086_27D8 / 10EC_0272 - headphones/speaker interchange working - no reboot required for volume control Lenovo E530 Laptop, Conexant CX20671 - 8086_1E20 / 14F1_506E - headphones/speaker interchange working - no reboot required for volume control HP 6550b Laptop, IDT 92HD75B3X5 - 8086_3B56 / 111D_7603 - headphones/speaker interchange working - no reboot required for volume control - needed to nudge volume control to get sound HP 6710b Laptop, Soundmax AD1981HD - 8086_ 284B / 11D4_1981 - headphones working only, speaker not working, audio stream stuttering - no reboot required for volume control (needs to route to NID$05 for speaker) HP NC8430 Laptop, Soundmax AD1981HD - 8086_27D8 / 11D4_1981 - headphones working only, speaker not working - no reboot required for volume control (needs to route to NID$05 for speaker) AMD K30BF_M32BF Desktop, Realtek ALC887 - 1022_780D / 10EC_0887 - front headphones & rear lineout working - headphone/lineout interchange not working - no reboot required for volume control1 point
-
I'm alive. I've simply got a heavy schedule with limited free time for the computer. I've read your suggestions and am implementing the majority of them. Will report back when "finished," with some results. May be a few days though. Thanks for taking the time to share all the info.1 point
-
As far as I know, Virtualisation/Sandbox Evasion is when an app (in most cases malware) tries to detect whether it's in a sandbox or not. The MITRE ATT&CK behaviour section of VxKex-NEXT only shows the Evasion, not the Escape. (As far as I know, Virtualisation/Sandbox Escape is when the app actually tries to escape the sandbox and interact with the host OS directly) I'm not sure why this is the case, although this Virtualisation/Sandbox Evasion technique alert could be triggered by driver checks, registry entries etc. However, as plausible as this could be, in my opinion, if VxKex (i486) doesn't flag this, then VxKex-NEXT (YuZhouRen86) should also theoretically have no reason to either. (and it flagged it twice!) I kind of doubt these kinds of flags can be excused or ignored as "false positives", but I'm not entirely sure.1 point
-
Released WDMHDA Version Alpha-021 which adds headphone jack detection and improves communication with the codec. https://github.com/andrew-hoffman/WDMHDA/releases1 point
-
VLC is also used to watch streams. And that means YouTube streams, too. Therefore, your request is totally on topic. Your observation in terms of the 3.0.8 version is interesting. I will try this version in my system the next days. One thing is clear. The latest versions aren’t always the best on older systems. They are no longer tested on older operating systems. I can confirm that regarding your BBC Radio 2 Live stream http://as-hls-ww-live.akamaized.net/pool_74208725/live/ww/bbc_radio_two/bbc_radio_two.isml/bbc_radio_two-audio=96000.m3u8 the 3.0.24 version from 29.05.2026 behaves very bad, but the 3.0.8 version perfectly. Even the 3.0.20 version is ok but the 3.0.8 version performs best. When it comes to my YouTube test video https://www.youtube.com/watch?v=ffcitRgiNDs however, I can't see any differences in CPU usage.1 point
-
I realise VLC specifically is NOT the topic of this thread, but could you be so kind as to actually pinpoint/link to that version? On https://artifacts.videolan.org/vlc-3.0/nightly-win32/ you can see that their server retention goes back to last December, ONLY, so I expect, in the future, that older "artifacts" will be forever purged ; perhaps this last, XP-compatible, build deserves to be archived for posterity ... All 3.0.23 versions are compatible with Windows XP. The last 3.0.23 version was releases on 12.05.2026. The last Windows XP compatible 3.0.24 version was from 29.05.2026.1 point
-
That should be MORE than enough FOR NOW, and only to GET YOU STARTED. There's MORE if you really truly want an OPTIMIZED bloat-free Win10.1 point
-
Probably too large of a script to post here, but I also remove "Get Started", "Windows Backup", and EVERYTHING pertaining to EDGE. Technically, I use Edge (as a third when-needed browser) but ONLY AS A PORTABLE, I DO NOT WANT IT "ENTANGLED" WITH THE OS, AND DO NOT WANT THE BACKGROUND UPDATE CRAP.1 point
-
1 point
-
I can help with that. I use Win 10 LTSC 2021 and it has been a GODSEND over XP (which I only finally ditched roughly a year ago [maybe two, but definitly not more). Even on a ten year old Dell Latitude E5470 with "only" an i5-6300U at 2.4 GHz and only 4GB RAM. I have to admit that I don't know the difference between mine and your "IoT" and whether or not there is more than a "2021" version. I *prefer* to use WINREDUCER EX-100 and cut MOST of the bloat *directly out of the install ISO* BEFORE ever installing and NONE of it ever lands on my hard drive !!! But... That approach has seemed too "complex" for the average MSFN user. That is not an indictment, just been down this road before and no "interest" was ever garnered from the MSFN Community. So here's what I'll do. I obtained this ISO from MSFN way back when I was still on XP: en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f That may not be the most recent, it's just the one that I have (my company IT shares these with me, I do not have the download link). I'll install into a VirtualBox VM and walk through how I debloat an "already installed" Win10. Again, that's not my PREFERRED route, but it is still effective (and even a WinReducer EX-100 approach still needs SOME of this still done after install). Will keep you posted...1 point
-
Every part of this project is one out of (almost) nine ways to run Windows 98se from an USB-drive. Two parts are about the Windows 98 Second Edition installation using the legacy USB-connection. The other parts are dependent on Grub4Dos. Each part gives needed changes in respect to the one before. All installations are possible in directory C:\WINDOWS: no drive-letter assignment needed; Part 8½ B is an exception however. Needed for the first eight parts: · Legacy BIOS must be USB-HDD compatible. · 512MB RAM (reasonable minimum). · 500MB USB-drive (reasonable minimum). · Partitioned USB-drive (USB-HDD). I am not sure if anything I did is new, but you will let me know. In retrospective everything is easygoing, although later parts and project extensions are more complicated. Except Grub4dos, everything is experimental and (almost) undocumented. The results of the project are divided into following parts: Part I: Quasi-universal Windows 98se on Legacy-USB 1.1 Part II: Quasi-universal Windows 98se on Grub4Dos Memdrive with full Legacy USB 1.1 access Part III: Windows 98se with PCI-devices (except USB) on legacy USB 1.1 Part IV: Windows 98se on Grub4Dos Memdrive with full USB 2.0 access Part V: Windows 98se on USB 2.0 with Grub4Dos Memdrive as bootchain Part VI: Windows 98se from a logical partition on Grub4Dos Memdrive Part VII: Installation of Windows 98se on a logical partition with Grub4Dos Part VIII: Windows 98se on other USB 2.0 partition with Grub4Dos Memdrive as bootchain Part 8½ A: Full installation of Windows 98se on an empty Grub4Dos Memdrive without rebooting Part 8½ B: Full installation of Windows 98se on a Rloew non-XMS Ramdrive without rebooting Concluding remarks DISCLAIMER: THIS PROJECT IS POTENTIALLY ADDICTIVE, I DON’T PAY FOR REHAB!1 point
-
Update Download: Make_WinPE_Trusted-97 - E = file Encrypted with pw=bootwimb - Cleanup of File_List files - Removal of duplicates in file entries - SMALL_Add_Install_Files_10.txt improved with extra 30 MB PE Size so that Desktop DPI Setting is working with DPIScalingMFCApp.exe It means in fact that SMALL = WinXShell Version and LARGE = Explorer Version have almost the same List of Added files from install.wim Advantage is a much better PE Desktop now also for the SMALL = WinXShell Version with adjustable DPI Setting Windows 11 24H2 requires additional extra files to get Desktop DPI Setting working with DPIScalingMFCApp.exe For the time being this is considered as the final version ..... But for sure new adjustments will be needed when New Windows ISO Versions arrive ...1 point