Leaderboard

It's there since 2013 https://www.ghacks.net/2013/04/29/winrar-5-0-introduces-the-new-rar-5-format-what-you-need-to-know/

The ecologists are trying to save some of the survived birdies. Footage from X (twitter). https://video-s.twimg.com/ext_tw_video/1869314369823068160/pu/vid/avc1/480x852/9OrzOcDVWbz1pLl5.mp4 https://video-s.twimg.com/ext_tw_video/1869314355805736960/pu/vid/avc1/480x848/x5Exy4zq93lLvTwY.mp4

The ecological catastrophe caused by the Russians using defunct oil tankers in the Black Sea not even intended for the high seas. Many thousands of tons of heavy fuel oil will cover the seabed. CNN reports. Black Sea beaches flooded with oil from wreck of tankers https://edition.cnn.com/2024/12/18/europe/russian-tankers-oil-spill-beaches-black-sea-intl/index.html

you don't even pay me why you order me to do the work?

still working with $DAYJOB, and for builds because there is lack of upstream changes. BTW I do plan for an update to my legacy browsers addressing some NSS related bugfixes and cert updates, but no ETA at the moment.

Hello to all! Although my program package eventually passed the beta test, I still had to make significant changes due to false positives of several AV scanners: All unnecessarily embedded files have been removed from my self-created executables. Changes in calling up other programs. In all my affected programs, protection against code injection has been improved. This leads to preventing of future "space bugs", too! Different issues which could have been noticed only in very rare cases, have been fixed. All unnecessary code has been removed. New bugs I additionally found have been fixed. Autostart entries of PopMenu and the new Min2Tray, automatically added to the registry by my configuration program, have been fixed in regards to the "space bug". All message windows of my programs have been resized and adjusted for a better visibility. All my self-created program files have been recompiled by using a different compiler. All these measures have led to a reduction in the number of false positives reported by AV scanners. Now I am testing deeply my program package from scratch. Cheers, AstroSkipper

Yes it is the one i did use to make the stripped version linked in my previous message. My version only has the package for Windows XP and ProxHTTPSproxy. It is only 6.69 MB instead of 16.8 Mo for the full XP Package. Sometimes it is interesting to have the minimum footprint on old machines with very small hard disks or compact flash cards. Install is done directly from the msi file.

In the early 2022, I quit using all online services, I go to physical stores, I pay cash only. I withdraw all money that I get from the military (pension) every month. I pay with physical papers for the utilities, usually in advance (4-6 months or so). I also refused to install any water counters, so I pay a "normative", which isn't that huge. By our Glorious French Constitution, no one can enter my house without my explicit permission, and it would be extremely hard anyways, they would have to besiege me with the special ops. So they had to calculate a median tariff for me. That's what you all need to do.

Is @roytam1 on vacation? He certainly deserves one, so I have no problem if he is. I never thought we really needed weekly browser updates - or even monthly, unless some significant new feature is added or security flaw is fixed. Personally, I'd be fine with quarterly updates! But usually, each week there's either an update or a post telling us otherwise. And he's held to that pattern for so long, it stands out when the pattern breaks. So I was just a bit concerned.

I don't agree, too. I game on a very old rig with GTX 780 Ti, it was made in 2013, very low 3GB VRAM, but is usable if I gimp down the texture quality.

Those look very much older, most likely used to get the costs down. Very similar to the items from the 80s/90s, not 2003.

It's against forum rules, not to mention common sense and politeness. And to me, also looks like you simply don't know yourself but making pompous announcements based on nothing.

I said irrelevant to my question, not the whole topic. @Sampei.Nihira simply avoids answering by switching the topic. https://msfn.org/board/topic/186450-firefox-a-promised-land-of-privacy-that-never-happened-look-elsewhere-unless-youre-a-coder-with-the-ability-to-stop-the-enormous-data-mining/?do=findComment&comment=1272456

They're not talking about the same Office version. Version 2002 is the last you can run with Office 2016/365 on Windows 7. Of course, the actual version of Office XP released in 2001-02 can run on 7, just the request is to make newer Office 2016/365 releases to run on W7 (2003, 2004 ... 2212 and so on). Also I'm someone who is tempted to support this idea, as they stopped features updates in v2002, while in v2003, they introduced something I was awaiting for so long : the HEX-based color selector, which is much easier to use than the ARGB/TSL selectors. You can't imagine how p***ed off I was when I saw that.

Anyway, all Windows XP compatible AV engines on VirusTotal do not generate false positive reports anymore! And, nearly all established and well-known AV scanners, too! Except Kaspersky, but I never trusted this company in the past, and will never trust it again in terms of security for good and well-known reasons.

Good question! I am the creator, and I really don't know why! But it can be taken as a good test for insensitivity to the "space bug".

And here is an example of reducing false positives by AV scanners. It's the file Configure PopMenu.exe: Old results uploaded by @Dave-H: Now my new results after all measures: 19 false positive messages have been reduced to a value of 10.

Hello to all again! The work is almost done. I tested deeply my program package, and what can I say? It's working perfectly without any issues as far as I can see. False positive reports by the etablished and well-known AV scanners have been reduced. I am thrilled! Currently, I am updating the documentation in regards to the changelog. And, there were a lot of changes! And now, a special information to my core beta testers, @Dave-H, @mina7601, and @NotHereToPlayGames! When my package ProxHTTPSProxy's PopMenu TLS 1.3 3V3 has been released, download it and, please, remove the old installation completely! Do all from scratch! Due to the changes, a simple replacing of files is neither good nor recommended. It could lead to error messages. Too much changes have been done! Furthermore, Microsoft .NET Framework 4.0 is now needed to run my program package. And now the most important thing! I think the release of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 will be tomorrow. Cheers, AstroSkipper

I do hope so, too! Unfortunately, it's a lot of work. Changing code leads to the need of changing other code, and so on. I modified and cleaned up nearly all self-created programs. And I found bugs which apparently did not occur during the beta test.

Hello @George King! That was the very first action I did! I removed unnecessarily embedded files from all self-created programs. But anyway, thanks for the hint!