dencorso

Dump WinZip and use 7-Zip instead.

http://web.archive.org/web/20071011202506/http://www.scitechsoft.com:80/ftp/snap/winnt/ http://www.bearwindows.boot-land.net/winnt4.htm

Even when "Automatic Updates" is turned OFF in the Control Panel, which has been my selected setting since at least 2007, there is an eponymous sevice which is set to "Automatic" by default, which I've always kept untouched. I'm disabling it right now. It might solve the issue in an easily reversible way, IMO, being an alternative to removing the POSReady key. Let's see what happens... Cross your fingers!

Welcome, Eric!

I prefer my browsing habits sent to China than to Google anyway. And I never keep logged in to it... just for Gmail, if at all, when needed.

Good. Meanwhile, 360 Chrome is working OK, and actually can display correctly things well beyond Serpent 52. Even if not perfectly compatible with Chromium 69, it sure is way beyond Google Chrome 49, and that's pretty useful as it is.

Done!

@heinoganda & @Dave-H: I've noticed if I let the machine on for many days MSE tries to update on its own and fails, populatin the event logs (both system and application). Please observe the errors always happens around the exact same hour, day after day. See attached window-capture below:

But, but... Does 52 esr even need that fix? Are you positive? I've got 52.9.1 esr and it's working fine...

Then again, Windows Embedded POSReady 7 EoS is on October 12, 2021...

Welcome to MSFN!

Good. So, now that I gave it it's own topic, I hand to you the task of giving it a proper title (unless you think the one I gave it is good enough).

I see no rudeness whatsoever in Frank's post. Yours, OTOH, is unnecessarily offensive. People nowadays are too oversensitive...

It's not "/! UO0" but "/!UO0": there's no space between the bang and the U.

Well, you're much welcome to vent up. So am I to rant, right? Yeah, it goes like this: 1.) All the issues you mentioned have solutions described in detail in this very forum. 2.) Athough it's easy to filx the Word 2010 issue, one can remain using Word 2000 (or even Word 97) for most if not all tasks commonly performed with it. Same goes for XL and Powerpoint. 3.) Al that is required is to arm oneself with patience and read the threads where the solutions are described. XP went EoS, then POSReady 2009 went EoS. MS did it because it was in their power to do so and they've decided it was in their interest to do so. Regardless of what any of us thinks about it. So it's up to us, the die-hard users, to support ourselves 'n one another... it's less confortable than leaving all responsibility fall on MS. Then again, for one who loves XP or just isn't confortable (or able) to cave in, it sure is worth it. One may whine. Then again, one may stand up and fight. Long live XP!

https://msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1061758

what part of "360chrome is Chromium 69 and needs no kernel wrappers to run on XP SP3" did you fail to understand?

We have @roytam1's browsers and 360chrome on top of it. Why lose time reinventing the wheel?

Chrome 360 installs itself in "%USERPROFILE%\Local Settings\Application Data\360Chrome", instead of in "%PROGRAMFILES%\360Chrome", as usual. Besides that and having to find out one has to select 显示为空白页 and deselect the other two options on the settings of the "New Tab" page to get a blank "New Tab" page, instead of that annoying Chinese search page , I think it's working great. So there's one more relatively recent browser working on XP. This is good news indeed! Thanks @Windows 2000, you rock!

We never know anything for sure... and, BTW, it's not safe, as you know.

Hope is last one to die...

It has to mean xper silently made another IP.B update and probably is tweaking it as time permits. But since xper has been utterly silent of late, I can inform you just what I deduced from those changes...

@Jaroslaw

I´m getting 'em galore, too! Both on the system and on the application logs, usually in threes. I've started to look for a way to at least suppress those errors, but haven't got anywhere yet. It should be something like deregistering some events... but then: which ones? Any advice much welcome, of course.