Leaderboard

Announcement: Release of ProxHTTPSProxy's PopMenu 3V1 I am proud to announce my first release of ProxHTTPSProxy's PopMenu. The beta test phase has been finished successfully. Thanks to my beta testers @Dave-H, @NotHereToPlayGames and @mina7601, for a great job! Without them I would definitely have come in some troubles! And thanks to @xpandvistafan for a positive rating of my work! As already announced some posts before I've decided to publish my latest work and this is the first release of ProxHTTPSProxy's PopMenu 3.0 in version 1.0.0.0 shortened 3V1. And today is the day. So what would Dirty Harry say? Make my day! Purpose and components of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSProxy's PopMenu is a one-click menu in systray to access and control the well-known proxy ProxHTTPSProxy. All information about this proxy can be found in my article (first post in this thread): https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1213600 Features of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSProxy's PopMenu 3V1 is a synthesis of self-programmed executables, a very few commands, credits to @AstroSkipper at MSFN, and the freeware PopMenu 3.0, credits to Jochanan Agam at freeware.persoft.ch. ProxHTTPSProxy's PopMenu is not a classical launcher, it is rather a systray popup menu. It can be totally customized and continuously extended according to user's needs due to its modular structure, therefore much more flexible than a classical, compiled launcher. More features can be added easily without touching existent code. Due to ProxHTTPSProxy's PopMenu's modular structure the user can change, add, delete and reorder features. Even the icons in menu can be changed easily by user. Here is the complete list of features implemented in ProxHTTPSPoxy's PopMenu 3v1: 1. Start ProxHTTPSPoxy 2. Stop ProxHTTPSPoxy 3. Hide ProxHTTPSPoxy 4. Show ProxHTTPSPoxy 5. Check if ProxHTTPSPoxy is running (in RAM) 6. cacert.pem Update 7. Root Certificates Update 8. Open IE Proxy settings 9. Close IE Proxy settings 10. Check system proxy status 11. Enable ProxHTTPSProxy system-wide 12. Disable ProxHTTPSProxy system-wide 13. Edit config.ini 14. Read documentation And here is a screenshot of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSPoxy's PopMenu is provided together with ProxHTTPSProxy REV3e. This new archive called "ProxHTTPSProxy_REV3e_PopMenu_3V1" has been additionally updated by me. These are the changes to original package of @heinoganda: Changelog of ProxHTTPSProxy's PopMenu 3V1: - @heinoganda's Certificate Updater 1.6 added. - Old CA Root Certificate CA.crt replaced by new one valid until 02/19/2032. - ProxHTTPSProxy CA Certificate Installer and Uninstaller replaced by more recent ones corresponding to pre-generated CA Root Certificate valid until 02/19/2032. - Old cacert Updater removed, recreated cacert Updater Fixed added. - cacert.pem updated to most recent one. - Alternative latest cacert.pem dated of 2022-04-26 from Mozilla added with download url. - All self-programmed executables of ProxHTTPSPoxy's PopMenu 3v1 created in two different versions, UPX and noUPX, following the spirit of ProxHTTPSPoxy's creator. Installation and configuration of ProxHTTPSProxy's PopMenu 3V1: 1. Unpack archive and copy the complete folder ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX or ProxHTTPSProxy_REV3e_PopMenu_3V1_UPX (or its complete content) to desired location. 2. Although both, ProxHTTPSProxy REV3e and ProxHTTPSPoxy's PopMenu 3V1, are fully portable, the config file of program PopMenu has to be adjusted to new location. This can be done manually or much more comfortable automatically by a tool I created for this purpose only. Go to subfolder PopMenu and execute "Configure PopMenu.exe". This procedure will always set the menu back to default settings. If you modified the menu in the past to your needs, you have to adjust the config file "PopMenu.ini" manually, otherwise you'll lose your modifications. In any case the paths in config file "PopMenu.ini" have to be adjusted when the complete program folder (or its complete content) was copied to a new location. Tranferring all settings of an existing ProxHTTPSProxy's installation: Copy the files "CA.crt" and "config.ini" from old installation folder to new one. Same with complete subfolder "Certs". Doing it in that way you won't lose any old settings. Usage of ProxHTTPSProxy's PopMenu 3V1: To start ProxHTTPSPoxy's PopMenu, just apply "ProxyPopMenu.exe" in main program folder ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX or ProxHTTPSProxy_REV3e_PopMenu_3V1_UPX. ProxHTTPSPoxy's PopMenu can be set to "Start automatically at Windows startup" in context menu item "Settings" which is called up by right-clicking systray icon. Here the PopMenu can be configured generally. ProxHTTPSPoxy's PopMenu has been pre-configured by me. The provided functions (items) corresponding to their labels are in most cases self-programmed executables and in a very few inserted commands. All items of ProxHTTPSPoxy's PopMenu are generally self-explanatory. Feel free to click on them and test them! If you click on item "Enable ProxHTTPSProxy system-wide", my program checks whether ProxHTTPSProxy is running or not. If not, it will be started immediately. This is necessary to set ProxHTTPSProxy to mode system-wide or setting process would fail. And one recommendation: Do not change or modify files in subfolder PopMenu and keep the file or folder structure inside main folder otherwise the ProxHTTPSProxy's PopMenu won't work properly! If you want to modify the menu, do it in PopMenu's "Settings". But you have to know what you do otherwise ProxHTTPSPoxy's PopMenu won't work as expected. ProxHTTPSProxy's PopMenu itself has a very low usage of RAM. It's only about 2 MB. And now my first release of ProxHTTPSProxy's PopMenu 3V1: Download of ProxHTTPSProxy's PopMenu 3V1: Link: https://www.mediafire.com/file/djg5n0n9osqco7m/ProxHTTPSProxy_REV3e_PopMenu_3V1_CheckedByAstroSkipper.7z/file Password: CheckedByAstroSkipper If you find a bug, need help or have questions relating to this package, post it in commenting zone of this thread! And finally I would be very pleased about posting your experiences and opinions relating to ProxHTTPSProxy's PopMenu 3V1. Any reactions by liking, upvoting and commenting are desired and welcome, of course. Kind regards, AstoSkipper

This is a very nice product and it is nice to finally have it in RTM. It will be a product I will use. It has lots of features, that are great for ProxHTTPSProxy. I was happy to be a beta tester!

This has been explained often times in the past, though I'm now plainly lazy to track down relevant MSFN posts... The gist of it is: H.264 (for video) and AAC (for audio) are patented decoders, inclusion of them into an app demands the app authors pay a handsome fee to the patent holders (currently the MPEG consortium). Google are big/wealthy enough to afford the fee and thus have included those decoders in their Google Chrome web browser; this is not the case for many of the rest of the Chromium-based browsers (e.g [Chrom]Opera, etc.) Mozilla couldn't afford including those patented decoders inside the Firefox browser core; instead, they shifted the onus on the operating system itself... Through the Windows Media Foundation (WMF) framework, Firefox can make use of the OS-provided copies of h.264/aac decoders for decoding HTLM5 video (audio) clips; Media Source Extensions, MSE, also comes into play here for the playback of fragmented (DASH/HLS) streams... The unfortunate thing for XP die-hards is that WMF is only supported on Windows Vista SP2 and onwards - in the case of Vista, a slightly less complete (to the one in Win7) implementation of WMF is installed via Platform Update Supplement (PUS), itself a Windows Update offering... And I can tell you that "native" H.264 support in Fx came long before v53.0 (but only available, as explained, in Vista SP2+, not XP)... Roytam1 browsers on WinXP: The FxESR 45 fork and the Goanna 3 (Tycho) based forks, i.e. New Moon 27+K-Meleon, have been modified to load the patented decoders from externally supplied (and manually installed in the application folder) LAV dlls (these are based on the open source FFmpeg project; XP-compatible versions of FFmpeg are used to compile those LAV dlls...). The UXP-based browsers (New Moon 28, Serpent 52 etc.) have been modified to load the patented decoders from a modded, internal, codec library called ffvpx; ffvpx is itself derived from FFmpeg, but in Firefox it normally only includes support for VPx and other non-patented decoders; the roytam1 version of this library has been patched to also include h264/aac support (via native FFmpeg decoders). Indeed, if you toggle the about:config pref media.ffvpx.enabled to false, said browsers lose h264/aac decoding capacity under XP... Serpent 55.0.0 => Same case as with Serpent 52 Feodor's new child MyPal68: I haven't been following its code development, feel free to visit the main code repository and discover how native h264/aac support under XP has been implemented; my educated guess is, again, via FFmpeg libs... FWIW, the Cisco Openh264 Video Codec plugin was provided in the context of WebRTC video-calls (it can both encode/decode the video stream), but it was limited to low video resolutions, only, and could not (to the best of my knowledge) be used as a full-fledged h264 decoder for general MP4/HTLM5 web clips (i.e. unlike the Adobe Primetime CDM's included decoder) ... NM28 is being compiled without WebRTC support (this is set from upstream, they NEVER supported WebRTC in Pale Moon), so no wonder the Cisco plugin is not installed by default there... And Serpent 52/55's WebRTC implementation is lagging very much behind the current Google-dictated specs, so much so that the majority of services requiring WebRTC today (2022) don't work in those browsers... OK, have you got a clearer picture now?

Windows XP just need a developer team to develop and support browser. Some websites do not give you a chance to try your Windows XP browser and just redirect user to "Bad browser" page. I do not use those websites and write critical review about their practice. But I know only 2-3 website that move you to "Bad browser" page.

should be fixed in next build

Check this out, lol https://www.techradar.com/uk/news/windows-11-is-apparently-less-popular-than-windows-xp

I'm personally of the opinion that the MAT Drama is a "toxic environment" that should probably be "limited" to its own dedicated area here at MSFN. It's like Court Room TV or Soap Operas - I know they "exist", but my life is better off not spending ANY of my time to tune into them

Do not waste your time. It is much easier for a fifth-grader to understand college calculus than it is to understand the topic matter you are seeking to understand.

Thank you @mina7601 and @hpwamr, Good day from Australia!

Of course they ain't! Don't let your wishes shield you from reality...

These statistics are rigged , beyond nuance

True enough... here you go!

In fact, the number of computers with windows XP installed is much, much larger. Almost all payment terminals, ATMs and cash registers still work on XP. Also, a lot of computers are used in organizations where there is not even access to the Internet. And also in special equipment in hospitals, auto diagnostics and so on.