All Activity

It has been two years since @Humming Owl last visited here. You could try sending him a PM. This is, of course, off-topic, but I hope he's OK too.

I saw the news says that there was a earthquake in your country, are you ok?

@roytam1 OK, it's taken a lot longer than last time, but we're at page 200 again! Could you do your usual thing, and when the next set of builds is rolled out, start a new part 6 thread with them? Thanks.

Seems to be real, here is another source: https://blogs.windows.com/windowsexperience/2025/06/24/stay-secure-with-windows-11-copilot-pcs-and-windows-365-before-support-ends-for-windows-10/#:~:text=Editor’s note – June 25%2C 2026 Editor’s note – June 25, 2026 – This post has been updated to reflect that the Windows 10 Extended Security Updates (ESU) program for personal use devices is being provided for an additional year, with coverage now available through Oct. 12, 2027. This extension provides customers with more time to transition to a new Windows 11 PC while continuing to receive critical security updates.

I burned the 98SE boot disk iso onto a cd and booted it via internal optical drive ( sata in ide mode ) on the Hp probook 6460b. I have used this method on other computers without problem, of course, almost all of them were much older ( usually no newer than ich6 ) and usually the connection was pure ide, not sata in ide mode.

Users can find the information at Microsoft's webpage. However, there is no official announcement from MS, so I don't know the information is true or not. Maybe the webpage was hacked. https://www.microsoft.com/en-us/windows/extended-security-updates

Yep! Thanks for fixing!

I think there's maybe a few more members on MSFN that do still dl the ulz's, but yes it's not as high numbers like back in the day. And I also provide the update lists on the My Digital Life forum site, and there is more members that do dl them too. So good news I'm not stopping anytime soon. I understand if you're into hardware more than software, I like both and can assemble my own PC though not recently due to the high costs of components especially memory and storage. I have managed with the use of a extension installed in VS2022, to convert the code from C# to VB.NET, but I will be able to resume programming when the GitHub copilot limits reset on the 1st July, as I'm on the free tier. So it could be next month when the Beta version is released but that's not a guarantee.

Used where? You described only problem with install Windows 98 from CD. No mentions of attempt to boot from USB Drive for example. Do you understand what is boot floppy image and what its purpose in CD-ROM boot process? Your .ISO has UNTOUCHED floppy image. I assume it's time to read something, El Torito standard for example and to study some .ISO authoring/editing software.

Steven: I wish I could help you but i'm more of a hardware guy than software. I hate to say this and maybe i'm wrong but I might be the only one DL the updates? Plus from jan. to may every year I snowbird to Florida so I dont make iso's those 4 months. If I'm the only one making use of your talents then I understand if you have to shut it down. I guess I'll survive by just seeing what new updates my computer installs after every patch Tuesday and get them from microsoft catalog. more work but that's the only thing I can think of. But if you can update WUD it would be GREAT. thanks again for all the time and effort you are putting into this. ps.. I just tried dl kb5094126 with WUD and it doesn't DL. I've noticed this happening at least the last 3 months of using WUD. it seems the large cumulative msu doesn't DL anymore. I've been going to the catalog to get them. Maybe its my system, but I doubt it... regards...

Oh man...plz stop this kind of personal war...we all are very special individuals, please respect each other and his/her opinion and behavior! I find out this myself every f*cking day...and still have problems to come together with other people... ------------------------------------------- Thank you, I hope to be here again regularly. ------------------------------------------- Sorry, had some vacation at the Baltic Sea - so the latest update is online just now: The mirror of latest ArcticFox 44, BNavigator 0.9, Firefox 28/45ESR, IceApe 52, IceDove 52, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28, RetroZilla, RZ browser and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest BNavigator 0.9 20260620 build - added latest IceApe 52 20260620 build - added latest IceDove 52 20260620 build - added latest MailNews 52 20260620 build - added latest New Moon 28 20260620 builds - added latest Serpent 52 20260620 builds - added latest Serpent 55 20260620 builds To don't lose track of things I want to update too someday... todo: - add various flash player versions - add FlashFix for WinXP - add VLC 2.2.8 (WinXP non-SSE2) done! - add polyfill addons Kind regards soggi

No, i used various combinations in your "a20alwon" package, all of them produced the same messages i mentioned earlier. these were all with usb legacy checked in bios, and fast boot = off. i also re-tested your "2_1_PREFERRED" method with usb legacy unchecked, but no change. To isolate this better, can you perhaps upload an already made modified ms dos 7.1 boot disk iso for me to test so i can check whether i'm doing something wrong or not? I attached my original 98SE boot disk below ( expires in 1 week ). https://limewire.com/d/ow9JG#U7khgdkRPI

And what’s the situation on the Windows XP front?

Asking AI suggests there should not be a difference. But there really is! No clue why. I've been trying to track that down ever since 360Chrome did that first-launch-lag in XP x64. It really is a matter of FORTY SECONDS verus ONE SECOND. But again, no clue why, been trying to track that down for YEARS. I *was* willing to accept it being "just my hardware", but I have confirmed the same exact behavior on two different machines (10yr old Dell Latitude E5470 and 1.5yr old HP Ultra 7 265). Will perform on a 10yr old Dell XPS 8700 in the next week or so.

Definitely have to disagree. Sure, it was possible that my observation on one machine would not carry over to other hardware, ie, a statistical outlier. But I have now observed on TWO DIFFERENT machines (will perform on a THIRD within the next week or so) that Chrome/Chromium/Supermium/360Chrome *FIRST LAUNCH AFTER REBOOT* takes FORTY-PLUS seconds in LTSB 2016 but only takes ONE second in LTSB 2021. All things identical except from the OS. I acknowledge that this is "probably" only a Chrome/Chromium/Supermium/360Chrome issue, but it occurs in ALL OF THEM and behaves identically across the board all dependent on a 2016 OS versus a 2021 OS. For me, sorry, it is NOT tied to hardware. All hardware between both installs were on the same exact machine (two of them, a third in the queue).

Yesterday, as a test for my projects, I downloaded a subtitle separately from YouTube using @nicolaasjan's yt-dlp. It was the first time I’d had to solve JavaScript challenges. After a thorough analysis of the logs, I installed QuickJS and was then able to download the subtitle successfully. However, it was anything but straightforward or quick. I timed how long it took to solve the JavaScript challenges, and it was a staggering 30 seconds on my Windows XP machine. Yet another reason to condemn Google to hell. However, the JavaScript challenges are only triggered under certain conditions. My ytBATCH for Windows XP downloads YouTube videos with subtitles, metadata and thumbnails without any problems and very quickly. I also tested that yesterday. So, for the time being, there’s no reason for me to implement QuickJS in my ytBATCH for Windows XP. If Google is to sabotage that too and no reasonable solution exists, I will discontinue the projects in question. P.S.: QuickJS 2025-09-13 even took 45 seconds on my machine contrary to the 30 seconds using QuickJS 2026-06-04.

Of course you will get error. You try to use unpatched himem.sys -> Unpatched himem.sys locates on boot floppy image of Windows 98 Install CD. Replace it there by patched version.

Yes I had a change of heart after your post. Currently working on updating WUD so that it can download the huge updates that MS releases, but having to rely on GitHub Copilot in VS 2022 as I don't have a lot of experience in programming C#. Once a build has been successfully built, I will release as a new beta. There will also be UI changes as well.

steven: I thought it was over!! I just checked (late for me for June) and there they are ...6/23/26 UPDATES!! you're the best! VERY MUCH APPRECIATED! now I can make my June ISO. SOOO very helpful. Thank you, regards....

i thought i gave enough information. i dont know what else to do that would be feasible for me, but let me post some more info. as i was discussing back to chatgpt. they specifically mentioned to remove "umb" from the config.sys for the 98SE boot disk iso burned to cd, booted it on hp probook 6460b - selected - start computer with cd rom support, then: error - unable to control a20 line! xms driver not installed. loads a couple cd dos drivers, then ram drive - extended memory manager not present. warning - the high memory area (hma) is not available. additional low memory (below 640 KB) will be used instead. windows 98 startup disk could not create a temporary driver for the diagnostic tools. this may be because this computer has less than the minimum required extended memory. path not found - :\command.com, :\extract.exe, :\readme.txt, bad command or file name, the diagnostic tools were successfully loaded to drive . file not found. ------------------------------------------------------------------------------------------------------------------------------------------- i tried various combinations below in config.sys DEVICE=HIMEMX2.EXE /MAX=256M /METHOD:ALWAYSON /VERBOSE - didn't work with "umb" omitted from config.sys or device=HIMEMX2.EXE /MAX=256M /METHOD:PORT92 /VERBOSE - didn't work with "umb" omitted from config.sys or device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE - didn't work with "umb" omitted from config.sys an example file of config.sys i used: [menu] menuitem=CD, Start computer with CD-ROM support. menuitem=NOCD, Start computer without CD-ROM support. menuitem=HELP, View the Help file. menudefault=CD,30 menucolor=7,0 [CD] device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE device=oakcdrom.sys /D:mscd001 device=btdosm.sys device=flashpt.sys device=btcdrom.sys /D:mscd001 device=aspi2dos.sys device=aspi8dos.sys device=aspi4dos.sys device=aspi8u2.sys device=aspicd.sys /D:mscd001 [NOCD] device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE [HELP] device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE [COMMON] files=40 buffers=40 dos=high stacks=9,256 device=ramdrive.sys /E 2048 lastdrive=z ------------------------------------------------------------------------------------------------------------ i also used xmgr.sys with the following in config.sys: [menu] menuitem=CD, Start computer with CD-ROM support. menuitem=NOCD, Start computer without CD-ROM support. menuitem=HELP, View the Help file. menudefault=CD,30 menucolor=7,0 [CD] device=XMGR.SYS /R device=oakcdrom.sys /D:mscd001 device=btdosm.sys device=flashpt.sys device=btcdrom.sys /D:mscd001 device=aspi2dos.sys device=aspi8dos.sys device=aspi4dos.sys device=aspi8u2.sys device=aspicd.sys /D:mscd001 [NOCD] device=XMGR.SYS /R [HELP] device=XMGR.SYS /R [COMMON] files=40 buffers=40 dos=high stacks=9,256 device=ramdrive.sys /E 2048 lastdrive=z ------------------------------------------------------------------------------------------------------------------------

Any clues people?

No clue from me. I technically never heard of "IoT" until this thread. I run LTSC (and LTSB, both from work) and it doesn't show "IoT" anywhere. The "IoT" shows it as in "Notification Mode", something else I've never heard of. It's just inside a VM for me, just for the sake of this thread. I'm not going to "activate" it out of fear even attempting to do so would "break" my company-provided activation (which also requires our company VPN). But I guess my thoughts would be this: if this "IoT" upgrade path is questionable (it probably is, no clue myself), it's probably no different than the "upgrade path" to XP's POSReady 2009. Something I myself see as ILLEGAL and never ran on any of my XP machines.

I wouldn't have recommended that upgrade path either and gone with a clean install. Windows 10 build 10586 (th2) is an internal pre-RTM build of Windows 10

I am curious about this "upgrade" mentioned, as I don't believe that IoT Enterprise LTSC has any upgrade path. It *is* true that it is possible, as I had taken about 3 months to figure out how to upgrade from Win7 to it but it is NOT designed to do that. 1809 version is the oldest I would use. I have that on my gaming computer and my old work notebook. I use 21H2 on my dev notebook. I previously had lag issues similar to what was mentioned on my gaming computer at various times but only when write operations were occuring, such as when a background process was running an update, Windows Update or Steam, etc. The culprit ended up being the SSD I was using having a write speed bottleneck. When I did my upgrade, I was using a Crucial SSD and upgraded on that, but then cloned it to a Sandisk SSD. The issue occured on the SanDisk SSD only. May not be relevant but it took me a lot of tooling around in the OS only to discover the OS wasn't the issue.

If you said about error in some software you had to describe exactly error in software, not behaviour of hardware. If you have error in himem.sys then take patched version (one of the two "preferred", of course) and just replace %windir%\HIMEM.SYS (or anywhere you want). >if you know whether "patcher9x" package includes all fixes from rloew's patchmem not all fixes, but all essential