Leaderboard

Hi RoyTam1, tested your Serpent 52 Non-SSE2 test build, It's working beautifully on my Pentium III 1.4GHz. Once I finish tweaking it I expect it to run even better. But even as of now, discord web (which, if you aren't familiar, is very bloated and slow, even a bit sluggish on my Core Duo ThinkPad) is quite usable on the PIII using that browser. It's truly amazing. I'd imagine you may find more optimizations to make, as the build is in it's infancy. Keep up the good work, dude!

you can get the experiment build here. Disclaimer: I'm not responsible for any crash/damage caused by this build. You should always test such builds on its own profile.

......................or the OP is not using a registered Windows 7 installation. Not casting any aspersions on Raheem Jamali but it is a possibility. There is, or should be, no trouble using the Win 7 Convenience Rollup Package with a genuine Win7 SP1 installation. I've used it without problems to update two different newly set up Windows 7 PCs but after that still had to install all the updates since then. There are a great deal. It is 4 months since I last used the Convenience Rollup Package. I think I may have even slip-streamed the rollup into the OS installer using a tool I found - installed via USB flash drive. I know I did something fancy thanks to information from here and elsewhere. But once done and only done once you tend to forget what it is you did or maybe it is just my age.

Roger that. I have tested the build and it works wonderfully on the RDD. I still haven't UOC'ed the browser yet, but I will once the new rewrite for 45 ESR SSE is done. If the Patch works as it should and if the extensions I use don't bog Serpent down, I think I might have found a replacement web browser for the RDD... 😏

I have found a solution: Windows Update Mini Tool. You can use it in Online Mode or even in Offline Mode. All POSReady updates are supported until 2019-Apr-05 (KB4500331 from May is missing). 1) The utility can copy KB file names to the clipboard using the same format as Microsoft Update Catalog. You need to click the button marked in blue at the screenshot below: This way you will get a text file similar to this one: [ Security Update for Windows XP (KB956572) ] http://download.windowsupdate.com/msdownload/update/software/secu/2009/03/windowsxp-kb956572-x86-enu_a2463f484318332e8319dd931c87b27cf747b2de.exe [ Security Update for Windows XP (KB952004) ] http://download.windowsupdate.com/msdownload/update/software/secu/2008/11/windowsxp-kb952004-x86-enu_28e11ce4e9083f84c7b9903716904a94dc6b7280.exe http://download.windowsupdate.com/msdownload/update/software/secu/2008/11/windowsxp-kb952004-x86-enu_09e9035221a8d945e27f97508213436068aca018.psf http://download.windowsupdate.com/msdownload/update/software/secu/2008/11/windowsxp-kb952004-x86-express-enu_bb1028e1f5de91ab2a0466a8f0903d43f141a323.cab I couldn't get Linux sed command to work to clean it up. grep command is another option. It's on to-do list for now. The idea is to have a final file, without any empty lines or comments, named e.g. download.txt: http://download.windowsupdate.com/msdownload/update/software/secu/2009/04/windowsxp-kb923561-x86-enu_b8aac16b07ca89c7dde4d724c808ff88faa456ec.exe http://download.windowsupdate.com/msdownload/update/software/secu/2009/03/windowsxp-kb956572-x86-enu_a2463f484318332e8319dd931c87b27cf747b2de.exe http://download.windowsupdate.com/msdownload/update/software/secu/2008/11/windowsxp-kb952004-x86-enu_28e11ce4e9083f84c7b9903716904a94dc6b7280.exe Now you can use wget in Linux to download all the files straight from the server. On my slow DSL connection it took just over five minutes to get 214 files (228 MB) with all updates for the base POSR 2009 installation: wget -i download.txt There might be some commands in XP's native CLI to do all this, Powershell is probably not needed for that. 2) WUMT also has an option (the button marked in red on the screenshot above) to download KB files to: C:\Windows\SoftwareDistribution\Download However in that case you get cryptic file names in the WU format. 3) Another interesting feature of WUMT is Offline Mode, which allows checking which updates are missing on a machine without internet connection. Offline Mode will be useful once XP's update servers get shut down. I have run it on a fresh installation of POSReady 2009 without any network driver and it works like a charm. To get Offline Mode working you need to get file "wsusscn2.cab" from Microsoft and place it in the same directory as WUMT file: // Any directory wumt_x86.exe wsusscn2.cab Offline Mode only allows getting a list of missing updates, there is no way to download any files. As long as WU servers are working Online Mode might be a better choice as it seems to offer more optional updates. I have tested all the above in Windows Embedded POSReady 2009 so it should work in XP with POSR updates enabled as well. 4) WUMT can be downloaded straight from the developer or from Major Geeks: https://forums.mydigitallife.net/threads/windows-update-minitool.64939/ https://www.majorgeeks.com/files/details/windows_update_minitool.html File wsusscn2.cab is available here: https://docs.microsoft.com/en-us/windows/win32/wua_sdk/using-wua-to-scan-for-updates-offline Some more information can be found here: https://support.microsoft.com/en-us/help/926464/a-new-version-of-the-windows-update-offline-scan-file-wsusscn2-cab-is https://win10.guru/toolkit-item-windows-update-minitool-wumt/

@roytam1 That is F A N T A S T I C! I really hope you can fix it and can be made to work on SSE only systems... I would love to try it on the RDD, especially since FF45 ESR SSE is giving me many problems lately... It scrolls fine for a while and then stutters badly, to the point of being unusable. Installing any add-on makes things worse, and not even experimental versions of the UOC Patch I have been compiling have managed to fix that... the issue is much much more mitigated in New Moon 27 and non existent in K-Meleon Goanna...

All the new releases of the UOC Patch have been cancelled. I haven't noticed any improvement in the latest experimental release I was working on and that was planned to be released. So, I might probably need to rewrite the entire Patch from scratch once again and see if I can finally get over the issues I stumbled upon during development and make another step forward. Until then, N2L will be the current version available, maybe for a long while, until I finally can make a significant achievement.

some little experiment: tried to build non-SSE2 build of UXP, binary built but it doesn't run (not crashing but quits without showing any UI/console window and no error messages) on my Mobile Celeron 650MHz. EDIT: it seems to be chromium's zlib doesn't like non-SSE2 environment, reverting it back to stock in its branch. EDIT2: commits pushed to its branch. (Notice: even it is pushed to its own branch, no regular builds will be created as whole thing is actually walking a tightrope and anything can be happened)

Well, SM 2.49.5 (last for XP) doesn't, anyway. You either have to install Adobe Primetime or copy some DLL's from one of @roytam1 browsers. We had a bit of an adventure trying to figure this out in the original (now closed) thread, but we eventually did figure it out, and we now have two ways to play HTML5 videos in SM 2.49.5. Note: That only applies to Windows XP. On newer Windows versions SM 2.49.5 can use WMF to play HTML5 videos, but XP lacks WMF.

Random thoughts from my scattered brain on Windows 98, registries, software installs, etc based on recent experiences. Back in the day DOS purists probably detested the new and improved Windows registry. Personally i think it's all good. For the most part Windows 98 does a decent job of backing it up and compressing it at boot. The registry should be safeguarded, a key to avoiding system failure. Not sure if any OS is better than another, to me Windows 98 remains a strong contender. Pure DOS is elegant and simple, no registry, hard to get into trouble but limited for modern computing. In Windows 9x the registry adds complication but is simple to maintain, although the OS is showing it's age. With limited experience of later Windows iterations, other than Windows XP, registry maintenance is still reasonable but these systems are overly complicated for most home computing, no longer have true DOS fallback and have issues with activation. Although GNU/Linux doesn't use a registry, it has it's own complications. Compared to most DOS applications, Linux and Windows typically use high scatter software installation methods. New software files go everywhere and generate during runtime. In Windows 98 files may get written to Program Files, My Documents, C:, C:\WINDOWS, C:\WINDOWS\Application Data, C:\WINDOWS\TEMP plus registry entries. In Linux files go to various /bin directories, /etc, /lib, /usr, /tmp, $HOME, etc. IMHO managing software gone awry, mixing and matching software versions, pinning back and holding old versions can be a bigger mess in Linux, unless using rollback software, a modular distribution or compiling your own programs. If available updates are not installed en mass, version conflicts may cause issues. If updates cause regressions, it's not always easy to roll back. As Windows 98 receives no more updates, once the initial install is done and any desired manual patches applied the system is stable. Windows 98 also makes it easy to remove newer software in favour of installing older versions, as needed or desired. In Windows 98 a software install gone bad is usually a simple fix, even when encountering un-installer issues. Just manually delete the files, clean and/or restore the registry. In GNU/Linux removing software is generally not an issue but a user needs to be wary of removing a meta-package, in Debian-based systems anyway, which may flag and remove other critical software. Both Windows and GNU/Linux still leave cruft behind after uninstalls, which requires an OCD user to perform some manual cleanup. With proper management the need for a re-install of any of these OS' is rare, usually only due to hardware failure. As GNU/Linux configures most hardware at boot, it probably holds the advantage for rebooting after catastrophic hardware issues, even motherboard swaps, without an OS re-install. Like a kid with a new toy i run registry cleaners and occasionally optimize the registry manually. Without benchmarking, uncertain if there is an appreciable performance improvement, probably only if the registry wasn't 'cleaned' for a long time. Whatever registry maintenance software is used, configure it to create backups before deletion. It's best to avoid using more than one registry cleaner or running more than one cleaning cycle per boot. This minimizes breakage and makes it easy to find the culprit and restore an accidental registry deletion. Consider running this in COMMAND.COM, especially before installing software of questionable origin: scanreg /backup /comment="RunningWellBeforeXYZ" It's also a good idea to run the above command before manually tinkering with REGEDIT. Using REGEDIT, the registry can also be backed up and restored by selecting Registry -> Import or Export Registry File. Registry keys can be deleted manually after searching (Ctrl-F) for keywords, like the software vendor's name, but exercise caution, reboot and check for issues. Registry backups only take a few seconds and can save lots of grief. I've never restored using REGEDIT and prefer the DOS commands, as REGEDIT will not be available if Windows fails to start. In case of emergency, reboot to DOS, select and restore the registry that contains your comment tag: scanreg /restore Run scanreg /? to view usage help. Registry backups are stored in C:\WINDOWS\SYSBCKUP as *.cab or *.CAB files. By default, only five backups are maintained. To confirm your system is regularly backing up the registry, check the date stamps of the *.cab files. Can also run MSCONFIG and check the Startup tab for a SCANREG autorun entry. Review C:\WINDOWS\SCANREG.INI for default settings, adjust as needed, only after backup up the original file. Exercise caution when running with a problematic registry, better to restore and fix immediately, as by default every reboot creates a new registry backup and shuffles out the oldest backup, even if it was a good one. In this manner, a few reboots and there will be no good registry backups to restore. Since i prefer manual methods, when the system is running well perform a commented registry backup as outlined above. Then copy all five *.cab / *.CAB files to other media, such as an external drive or USB stick. This way a good restore is always available.

Don't apologize for that viewpoint. I hope that most of us at MSFN are 100% behind the idea that ANY user should have the right to use ANY software, including ANY OS, on THEIR machine if it meets THEIR needs, and we should not criticize them for it. We are here to talk about their, and our, experiences and help others as we can. Cheers and Regards

Standalone installers are working fine, updates have been installed.

I think we may have a problem with Microsoft Update here. I wasn't offered any Office 2010 updates with a yellow shield today as I expected, and when I ran MS Update after scanning for ages it eventually offered three updates. Security Update for Microsoft Office 2010 (KB4484127) 32-Bit Edition Security Update for Microsoft Excel 2010 (KB4484164) 32-Bit Edition Security Update for Microsoft Office 2010 (KB4484160) 32-Bit Edition None of them will install, I've tried twice. They show as failed as soon as they download. The error is 0x80096010, which apparently means "TRUST_E_BAD_DIGEST - The digital signature of the object did not verify". That does not sound good! I have a horrible feeling that we may now be blocked because of out of date certificates. I ran @heinoganda's certificates updater this morning, i hope that didn't cause this! EDIT: Just tried with HTTPSProxy disabled, just in case, same result. I guess I'll have to try installing from the standalone installers for the updates tomorrow (off to bed now!)

It's only updates that replace MSO.DLL that you have to worry about, all others seem to be OK, and should still be applied IMO.