Content Type
Profiles
Forums
Events
Everything posted by dencorso
-
KB4487085. But do wait a couple of days before updating. Let's see what else emerges.
-
I didn't actually say you said anything. Nor did I mean to offend. The simple opening of this thread shows a single-minded insistence in fixing a rig that seems to be foobar, and this creates the idea you aren't able to at least replace the board for another used one of the same model and maker and also buy one brand new memory stick to go with it. From my POV, that's OK. But then, when you start talking about a huge 850W PSU I got surprised and expressed it. As for your health problems, you have my sympathy and my respect. But have in mind RL sucks everywhere, and money don't grow in trees here in Brazil either. I also try to avoid contributing to the e-waste problem. That's why I decomissioned 3 perfectly working Athlon XP machines and sold or gave away to friends all their parts. Had I kept one to use as a hardware firewall, I'd have a 600 W PSU running all the time... instead, I do that with a Raspberry Pi running OpenWRT. Makes sense in my book.
-
That's why one should do full backups before adding updates. Once I realized the system was foobar, I redeployed the jan 31 image, and lost nothing. I had to reinstall the latest Flash and Basilisk, though. Had I made a new backup imediately before updating, even that would've been unnecessary.
-
I saw the crappy message below, too, and DaemonToolsLite 4.45 (important) and two other uninportant start-up programs crashed in flames! "The procedure entry point sprinttf_s could not be located in the dynamic link library msvcrt.dll." @Ascii2's posted before I had found out which update was to blame. My thanks to all of you who posted about it. It seems KB4487085 is the latest crappy update MS came out with... @Ascii2: did KB4486463 install correctly for you? If so, you should have: %windir%\system32\ntoskrnl.exe v. 5.1.2600.7649 (orig. ntkrnlmp.exe) and %windir%\system32\ntkrnlpa.exe v. 5.1.2600.7581 (orig. ntkrpamp.exe) In case your machine uses a multicore processor, of course.
-
-
Errm... @TrevMUN: You actually want me to believe you have no money to buy another board and memory sticks, but actualy do have plenty money to sink in an overpowered 850W PSU? Are you kidding or what?
-
IMO, no. Eudora is one of the best (if not the very best) stand-alone e-mail client ever. So, now that we have a diagnostic of the problem, at last, it seems proper to pursue the actual solution in the same thread. Me, too. But if @jumper is willing to try and create a standalone wrapper library to be dropped in Eudora's folder (even if some local executables will have to be hexedited to redirect some calls to the wrapper) he sure has the expertise to do so. I think we should go for it.
-
Done!
-
Now, that's something I don't see in RL for at least 30 years... and if someone still has vintage ones in stock, unless they were stored under nitrogen or in vacuo, they must be too oxidized to be of any use...
-
And that it sure is! But it may be the best workaround more-or-less readly available. Proxomitron is a very versatile filter proxy, so that it can filter any offending html code before it reaches the browser (er... in you case that'd be Eudora, of course!). So, the part you have to solve is how to insert Proxomitron in your proxy chain, just for Eudora (I bet @heinoganda can help you with this part) and how to program Proxomitron for it to filter what you want to filter (it should be via a script or a config file, of course) and maybe how to disable some potencially annoying extra paranoid default normally used by Proxomitron. I cannot help much because I've never used Proxomitron, till now (although I suspect I'll need it sooner or later). We have some Proxomitron users here at MSFN, who I'm sure will be glad to help. It's a pity owr own resident specialist in it (@herbalist) seems not to be around anymore...
-
You mean: they announced last February that [it] would be the last [to] officially support XP ???
-
You've got two suggestions already, which seem to have passed below the radar: Privoxy or Proxomitron. Perhaps there may even be another simpler filter proxy to do the job, but we do know that HTTPSProxy does work with Proxomitron or Privoxy... so that this may be a start for a good workaround (not a solution, but no real solution seems possible ATM).
-
I'm sorry to say it sure seems so.
-
Looks like problems with antivirus software or a missing certificate. This report does not refer to XP but may be enlightening nonetheless: https://www.bleepingcomputer.com/news/software/mozilla-halts-firefox-65-rollout-due-to-insecure-certificate-errors/
-
My Browser Builds (Part 1)
dencorso replied to roytam1's topic in Browsers working on Older NT-Family OSes
No. -
ChromeOS (in chromebooks) and Android (in tablets). Not Linux, nor xxxxBSD, much less MacOS.
-
My Browser Builds (Part 1)
dencorso replied to roytam1's topic in Browsers working on Older NT-Family OSes
webgl.webgl2-compat-mode=true