Leaderboard

Click this https://imgur.com/beta/disable

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200912-72c45cb-uxp-b55d425b3-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200912-72c45cb-uxp-b55d425b3-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200912-72c45cb-uxp-b55d425b3-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win32-git-20200912-2771b99fc-uxp-b55d425b3-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20200912-2771b99fc-uxp-b55d425b3-xpmod.7z Official UXP changes since my last build: - Issue #618 - Add JS API to associate scripts with DOM elements after compilation (22f300f7c) - Issue #618 - Implement preloading of module scripts. (92ef20627) - Revert "Issue #618 - Add JS API to associate scripts with DOM elements after compilation" (e4fb3f48a) - Issue #1644 - Remove plugin checking code leftovers (9440be0ae) - Issue #1639 - Implement object.fromEntries() (1154e4884) - Issue #618 - Make ES6 modules work for resource: URIs (8e5d9da5e) - Issue #618 - Clear the module map when changing a Document's global and add release build assertions for mismatching compartments. (df55ce903) - Merge branch 'es-modules-work' (b55d425b3) Official Basilisk changes since my last build: - Update back-end branch pointer. (72c45cb) Official Pale-Moon changes since my last build: - Issue MoonchildProductions/UXP#1644 - Remove plugin check leftovers (front-end) (24a06c474) - Issue #1717 - Add distinct mixed-mode indicator and logic for display. (2771b99fc)

abbodi on mdl has managed to restore WU functionality with working SHA-2 apparently and can get both Vista and Sever 2008 Updates (even ESU) and possibly even Windows defender updates?

One year ago today... Rudy, you are sorely missed!

So I hope you guys know about some of the interesting things about Windows Me, at MSFN in fact, I found all this info in bits and pieces scattered over many threads so I am posting it in a single post. Also, there are many people here who already know it or are much smarter so ignore, I am only posting it for those still playing with this ancient OS in a VM or real old hardware. Hope it's not a problem: 1. Only the OEM version of Windows Me has hibernation support, retail doesn't. Also, OEM Windows Me CD is bootable. 2. It is common knowledge that Windows Me was patched to restore MS-DOS real mode. Io.sys, Command.com and Regenv.exe can be patched so it processes Config.sys and Autoexec.bat. That is old news. But this way of patching has a downside - you lose the nice white Windows Me boot logo (logo.sys that's inside Io.sys) because it takes the Io.sys/Winboot file from the EBD (Emergency Boot Disk). But instead what I recently learned (sure seasoned members and experts know it already) is after using the Me2Dos patch to modify Io.sys, command.com and regenv.exe or patching it yourself with a hex editor, if you take the Io.sys from Windows Me's Bootable CD (after it boots to DOS for Setup) or from the OEM Preinstallation Kit (OPK) that's there in tools\nettools\fac -> DTA files (which are actually CAB files on the CD) and overwrite the one in C:\ drive's root with this one, then this OEM Io.sys does have the nice boot screen and you can still boot to DOS if you want due to the patched Command.com and Regenv.exe. In fact you get the full set of startup options like 95/98 except "Previous version of MS-DOS". So, after you have patched Windows Me with the famous Me2DOS patch to boot like 95/98, you can replace Io.sys with the non-patched Io.sys from Me OPK or Bootable Me ISO, and you get the best of both worlds - boot screen as well as boot to DOS/startup files no longer ignored. 3. Another advantage of Io.sys from OEM CD vs EBD patch is Expanded Memory is available in Windows Me for DOS programs. 4. Finally, you need to make a few changes to startup files after the Me2Dos patch and replacing Io.sys from OEM CD, so that "Command prompt only" option works like 95/98 and also you don't get boot errors at startup when booting Windows Me with the "Normal" option. I'll explain why you need to modify files again after the Me2Dos patch. With this unpatched Io.sys from OEM CD Boot image/OPK, it always loads Windows Me even if you choose the "Command prompt only" option. This is because the Command interpreter line in startup files lacks the /P (permanent) switch. You just need to add the /P switch to config.sys. After you install the Me2Dos patch, it modifies Config.sys to add this line: shell=c:\command.com e:32768. Just modify it as stated below so you don't get a "File creation error" when booting. Like this: shell=c:\command.com c: /p /e:32768 (Note the correct use of /p switch in Config.sys is to list dir where command interpreter resides before it so you must add: c: before /p) Also this Io.sys will automatically load Ifshlp.sys so you can comment out the line in config.sys added by Me2Dos patch by a semicolon and lastly remove the line from Autoexec.bat: C:\WINDOWS\win.com as with the non-patched Io.sys from Bootable OEM CD, it will load Windows Me anyway when "Normal" startup is used. So you get all options working exactly like Windows 95/98: Normal, Logged, Safe Mode, Step-by-Step Confirmation, Command Prompt only (which does process your Config.sys and Autoexec.bat but boots to DOS only) and Safe mode command prompt only which bypasses them. 5. Another fun thing I recently learned is with the ORIGINAL Io.sys that Windows Me officially installs (not the patched one from Me2Dos/EBD patch and not the one from OEM Me CD), Windows Me does not actually need Win.com to boot! It is there only for compatibility but Win.com then loads vmm32.vxd which is the main file that switches from real-mode to protected mode. So you can do fun trick (not that there is any use of it): - Rename C:\Windows\Win.com to WinMe.com so Windows doesn't find it automatically - Rename C:\Windows\system\vmm32.vxd to vmm32.com. - Take Command.com from tools\nettools\fac -> DTA files and rename it to C:\Windows\system\vmm32.vxd Now when your PC boots with original unpatched Io.sys, it will only load Command.com Also you can directly load Windows Me by running: C:\Windows\system\vmm32.com. Or create a batch file in C:\ called Win.bat which points to C:\Windows\system\vmm32.com. That way it loads command.com. If you type, Win, it loads Windows Me. Note that I find this trick (#5) useless as original Io.sys bypasses startup files so there is no advantage of booting to DOS. Also if you use any different Io.sys, then vmm32.com will fail to load Windows Me directly. Let me know what you guys think. I think having access to MS-DOS almost like Windows 98 is awesome. The only thing that is still missing is Restart to MS-DOS Mode option but you can always dual boot between some version of DOS and Windows Me/DOS if you don't like "Command Prompt only" (Windows Me DOS 8.0).

I think that falls under “NM27 is too old.”

You must be referring to https://forums.mydigitallife.net/threads/windows-vista-bypass-eol-with-windows-update.81026/page-2#post-1617010. It sounds like a Server 2008 license would be required. For mere mortals, it might be a lot easier to just switch to Server 2008.

I assume this amount is for them to actively recover the data for you, not just for some recovery software? Is the price contingent upon them successfully recovering everything? Of course it also depends on just how "irreplaceable" the data is; or how hard it would be to "recreate" the lost items... If you have PayPal, some of us might be able to contribute a few dollars toward helping you... (for reference, if the conversion I'm getting is right this amounts to approximately $400 to $900 USD; seems a very wide price margin!)

@max-h this installs 7.6.7600.256 for XP and Vista http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x64.exe http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe

Microsoft cut a few days (or hours) ago I don't know precisely, the self-update of windows update agent. This means that WUMT will display "class not registered" until we manually update the agent. It's really the end this time. Fortunately, I found version 7.4.7600.226 as standalone package : https://support.microsoft.com/en-us/help/946928/information-for-network-administrators-about-how-to-obtain-the-latest As indicated, there is no standalone package for version 7.6.7600.256 but 7.4 works well.

Lots of news. I managed to work around ntdll somewhat. My ntext (ntdll with a new section and updated checksum) was successfully hooked by kernel32 through forwarded functions. But programs that call ntdll directly didn't go as well. Firefox would crash or pseudo-load hogging up several CPU threads. So I think a completely new wrapper dll that forwards to ntdll is necessary. I was almost successful in getting the Windows 7 compatibility shimming framework to work (a modified aclayers.dll that fakes Windows 7 SP1 instead of RTM and acppage.dll in particular). But the latter calls registry-related functions from kernel32 instead of advapi32. So I added them to kernel32 forwarding to advapi32 but it didn't work as it would keep forgetting the compatibility options (those reg functions are slightly different on 7 than Vista but very difficult to implement). So it may be better to modify the Vista versions of the files, but it's not that clear cut to me, unless I were to replace one of the existing compatibility options (somehow I think no one really bothers with the 2003 SP1 option).

hard to tell. the changes between 20181222-ba81aaf07-xpmod and 20181229-83cd9661c-xpmod are minor: https://github.com/MoonchildProductions/UXP/compare/ba81aaf07...83cd9661c unless it is AV1 content (which is unlikely since AV1 decoding is super-heavy) since there was an update between these builds. not possible, because ffmpeg 3.4 knows only software decoding.

Thank you. I never heard about this service. I wonder if it save to log in there using google account? If i leave comments there would they appear on youtube or only stay on this site? I use now yewtu.be in dark version - nice speed. Even with 720p CPU is idling with Cool&Quiet ON. I also have questions to roytam1. I look different versions of NewMoon and notice that 28.3.0a1 (2018-12-21) is last where video playback is more smooth and take less CPU resources. With next version video play a little bit intermittent, fitful. But on 28.3.0a1 (2018-12-21) video playback is very smooth. What did you change after (2018-12-21) version? Did anybody else notice that? Because 28.3.0a1 (2018-12-21) version play video faster and smoother then next versions. Also i have dumb question to roytam1. MPC-HC (1.6.9.7503), MPC-BE(1.4.7), PotPlayer use HW acceleration of videocard to play AVC video in Windows XP. Did you ever looked to option to make NewMoon play AVC video with HW acceleration. Or it is totally not possible?

FWIW, I got all the XP-X64 EXE files and double-checked that no more updates just after/around MS clobbered support. Done in a HyperVM (whatever) on one my other PC's (Srv2k8R2). Maybe an upload to Web Archive is in order?

I use that in spring and summer and until recently it worked, but not anymore. Nope. That didn't work to. What interesting that with default string - Firefox/42.0 PaleMoon/28.3.0a1 it can load non polymer design if in Bookmarks link is with ?disable_polymer=1 Like this: https://www.youtube.com/user/TheYoungTurks/videos?disable_polymer=1 But videos itself is only with polymer regardless of what in string. So i often use PotPlayer to watch videos from YouTube (i just copying URL and then push CTRL+V in Pot Player so i watch YouTube online with HW acceleration in XP) because page loading is so long now and video playback are not smooth. On other sites even 1080p can ran smooth but with polymer even 480p go badly. And in 2017 when they kill flash (flash was running h264 with HW acceleration) i was thinking that new interface was slow, but this polymer2 is like PCCB - (Porsche Carbon Ceramic Brakes) - it slow you down very efficiently.

Is there is still a way to make Old YouTube design work while playing video in New Moon 28?

there is no "release" schedule since all "releases" are just actually "pre-release". and no, I don't want to make any point-release builds for continuing develop product. 45ESR builds are different as upstream only drops few commits per month for bug-fixing.