Leaderboard

@Dietmar Yeaaah, it worked I spent all night creating a way for WinXP 64-bit to access the UEFI BootMenu - it works - read/write. So far I have only tested in VMware:

OpenSSL 3.6.2

had a look, many commits in his repo look messy and 1 commit combines many unrelated changes. I'll just wait until he cleans-up and put them in MCP's repo/issue tracker.

@roytam1, you may have seen that wuggy has made an other UXP fork. There may be things that are interesting for your forks, he also worked on performances apparently. Dactyloidae UXP fork: https://repo.dactyloidae.xyz/Dactyloidae/UXP Some of those improvements might get merged by mainstream: https://repo.palemoon.org/MoonchildProductions/UXP/issues/3030

Don't use the LUA script if you don't know how it works and which configurations have to be done! First read, then act!

Maybe for you but my package needs a correct configuration of Min2Tray for minimizing the proxy console. There’s no need to reinvent the wheel. My package works perfectly as it was described in my thread and inside the archive. Any modifications done by users at their own risk!

Hello @sea! Thanks for posting and interest in ProxHTTPSProxy's PopMenu TLS 1.3 3V3! However, it is more or less portable. It only uses modules from inside its programme folder and stores its settings there. The "Configure PopMenu.exe" is necessary to adapt all absolute pathes, to configure Min2Tray and to set the autostart of PopMenu and Min2Tray. You can of course use relative pathes but Min2Tray has then to be manually configured as well. It needs own registry entries and is therefore not really fully portable. I personally use ProxHTTPSProxy's PopMenu TLS 1.3 3V4 which I had updated to the most recent ProxyMI-20230813 long time ago but never released here due to the lack of interest. Strictly following the rule: No demand, no supply.

No, my original version of ProxyStart.exe was starting on boot correctly only with a delay of 10 seconds, with less or no delay it didn't work, either.

Did you get it? And please, do not delete the message thread until the beta test is over! Thanks!

No problem! I'll send you the fix a second time. But a bit strange, I could see all links in our private zone.

No problem! Just an observation!

Of course! It's the same problem as it was with my starter program. It can't find its working directory in the early boot phase of Windows. The code inside the starter program has to point to its working directory.

And, by the way, I am really begining to hate these d**n spaces. Same problems as last time!

Hello again, my dear beta testers! My starter program is now of version 3.2.0.0 and should even run with install paths containing spaces. I am very excited if it now works for you all. Cheers, AstroSkipper