Leaderboard

lol - yeah, they're already worried about 3-digit version numbers in the User Agent string. And at this rate, four-digit version numbers is quite literally (not figuratively, but LITERALLY) "just around the corner".

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220219-f5d811828-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220219-f5d811828-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220219-f5d811828-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20220219-f5d811828-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1132920: Use movddup for SIMD swizzle pattern (0, 1, 0, 1) on SSE3 enabled machines; r=sunfish (2f6ff1e5ae) - cleanup (a843df02f4) - Bug 1201810, IonMonkey - Part 1: Move the platform specific shared ic stubs, r=jandem (41103c7241) - Bug 1201810, IonMonkey - Part 0: Improve code of EmitIonTailCallVM, r=jandem (aa72188407) - Bug 1203297: Fix makeFrameDescriptor warnings on x86 and x64, in non-unified builds; r=terrence (8ff0ef518d) - Bug 984018 - sincos optimization. r=nbp (8e82c1249e) - rearrange (9eec87ba05) (f5d811828)

I'm not sure exactly what you mean about lets encrypt certified sites being broken or the certs being from 2016, the cert updater on my site automatically fetches the latest ones. My own site uses a lets encrypt certificate and is properly validated in IE8 on XP, after using the updater. In case there is some confusion, i mean this one HERE: http://i430vx.net/files/misc/Cert_Updater_v1.6.exe Edit: (my two cents about the first post) If one wants to manually update the certs, i would run the cert updater with wireshark or tcpdump and just look at where it is downloading from... those are what you need. Edit 2: A lot easier is just to view its files. It extracts to %tmp%\certupd.tmp\ There, among other things, you will find the batch file.

you're welcome! happy to hear you got it working!

maybe not all the USB drivers were copied across? I think this is a bug windows 2000 had. On your windows 2000 CD - go to \I386 and open DRIVER.CAB with 7zip or WinRAR, scroll down and extract everything with usb in the name and put it in \system32\drivers. See if that works. edit: these too - mouclass.sys mouhid.sys kdbclass.sys kbdhid.sys

I see that you have a native USB 2.0 controller on board Intel(R) 8 Series/C220 Series USB EHCI #2 - 8C2D PCI\VEN_8086&DEV_8C2D&SUBSYS_06121028&REV_04 PCI\VEN_8086&DEV_8C2D&SUBSYS_06121028 PCI\VEN_8086&DEV_8C2D&CC_0C0320 PCI\VEN_8086&DEV_8C2D&CC_0C03 ^ This should work for your mouse and keyboard since Windows 2000 has native USB 2.0 drivers.

I actually got one friend in Texas who visited there multiple times to get good hardware. I kinda wish we would have similar here but no since many places even trash motherboards with hammers "since they contain sensitive data". I have no idea where thing came from. That is true for some newer laptops with onboard EMMC storage, but desktop mainboards (expect maybe management engines) contain no company data. If very paranoid just wipe cmos and even on servers with ILO or similar remote management there is "emergency reset jumper" to wipe it clean from custom settings. I give my old hardware away for someone who need it or sell it away instead or trashing it. Best way to find free old hardware here is dumpsters and friends. People sometimes leave stuff visible on purpose so someone can pick it up. That is how I got my brother laser printer. Someone had left it next to garbage cans one place. I just put it on bag quickly and took away.

A little OT, but I found it interesting that 2 Microsoft Root Certificates expired in the past 2 years. One of them is the Microsoft Root Authority, signed using MD5 and valid from January 10, 1997 to December 31, 2020. The other one is the Microsoft Root Certificate Authority signed using SHA-1 and valid from May 9, 2001 to May 9, 2021. Both of the expiry dates lined up with Microsoft's SHA-1 deprecation plan.

New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.4.5-Goanna-20220219.7z Changelog: Out-of-tree changes: * update Goanna3 to git 850741b59...f5d811828: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1132920: Use movddup for SIMD swizzle pattern (0, 1, 0, 1) on SSE3 enabled machines; r=sunfish (2f6ff1e5ae) - cleanup (a843df02f4) - Bug 1201810, IonMonkey - Part 1: Move the platform specific shared ic stubs, r=jandem (41103c7241) - Bug 1201810, IonMonkey - Part 0: Improve code of EmitIonTailCallVM, r=jandem (aa72188407) - Bug 1203297: Fix makeFrameDescriptor warnings on x86 and x64, in non-unified builds; r=terrence (8ff0ef518d) - Bug 984018 - sincos optimization. r=nbp (8e82c1249e) - rearrange (9eec87ba05) (f5d811828) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

Clipboard and drag and drop both work for me with BWC's extended kernel installed. Your system (or VM) must be having a misconfiguration. There are sometimes blog posts & comments in english.

or this instead https://msfn.org/board/topic/181915-system-certificates-updater-the-easy-way/

I agree, while there are some pretty nice themes for WB , the one thing it has NEVER been able to do is skin the entire OS and it kinda sucks if you are creating a dark theme and are left with areas of white that WB cannot skin. Another thing is the system resources it uses, which is really not a problem with today's computers but why waste system resources running third party themes when it really isn't necessary? just another area they have never tried to correct or advance in and is where Stardock falls behind. Instead of them joining, embracing and working with the themeing community they choose to keep all their stuff proprietary, like themeing cannot be achieved without their software ... lol, in the long run is only going to hurt them. Word is they will not have a fully working Window Blind program for Windows 11 until 2023 ....... Ouch! That is gonna cost them. As far as BM , I sincerely hope he is ok and would like him to answer even if it is to say he is not continuing on with Aeroglass. Aeroglass was always a far better option than Window Blinds. Don't really know if anyone can take over his works , you would need source code for that and who knows how close BM kept his secrets to his vest? and IF anything , god forbid, has happened to him if anyone else even had access to his works. I am no programmer or anything but I wounder if Aeroglass can be de compiled to show it's source code?

Adding the -R will keep the original server timestamp curl -O -R