Jump to content

AstroSkipper

Member
  • Posts

    4,565
  • Joined

  • Days Won

    457
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by AstroSkipper

  1. Good news! As already reported here, the patch + proxy method for accessing MU is still working. Checked in January 2025. And the Legacy Update service is also working. Checked in August 2024 which I reported in this post. Is anyone here using other methods? Referring to the list of all known methods for accessing MU, please report here if your favoured method is still working in today! This would be very interesting for all users of Windows XP. Thanks in advance! Cheers, AstroSkipper
  2. Which method are you referring to? The patch + proxy method uses the TLS 1.2 or TLS 1.3 ProxHTTPSProxy which is needed to connect to MU via Internet Explorer. The service Legacy Update provides their own client software which means no additional proxy is needed. Here is my report from August 2024 when testing the Legacy Update service: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1270925 One thing is clear. Today, most connections require at least the TLS 1.2 protocol. Please, first read about the methods before asking! All is described in detail.
  3. No problems here to access Microsoft Update under Windows XP from Germany when using the patch + proxy method. Maybe, your location is the problem due to any restrictions. If you need to check for system updates, try Legacy Update as it is easy to install.
  4. My memory wasn't playing tricks on me. I was able to run even this method in Mypal 68.14.4b one more time. I combined methods from the Alice0775 project targeting FF 69+ and FF 72+ to get this script loading method (without binding via the userChrome.xml file from the Nuchi project) from 4th place of my ranking list running. However, two little fixes inside the userChrome.js file were necessary for that. As I already mentioned, this should actually only work from Firefox 72 onwards. Perhaps, Alice0775 did not even consider this possible variant for FF 68 at that time.
  5. Overview of script loading methods for Mypal 68 This is a ranking list of all script loading methods for Mypal 68, which I am aware of, and reflects the experiences from my tests in the currently most recent versions 68.14.4b and 68.14.5b of this browser. Edit (05.05.2025): This ranking list is valid up to and including version 68.14.7b: Nuchi-Sporif script loading method Alice0775-Nuchi script loading method Nuchi script loading method Alice0775 script loading method Aris-t2/Ardiman-Endor8 script loading method Endor8 script loading method Xiaoxiaoflood script loading method The Nuchi-Sporif script loading method in 1st place is the one I have been making available for download here since 2022. All scripts that are really compatible with Firefox 68+ work with this method in Mypal 68 right from the start. The Alice0775-Nuchi script loading method in 2nd place works similarly well if a small fix I was able to find due to an error message in the browser console is made in its code. The pure Nuchi script loading method in 3rd place does not automatically recognise scripts in the chrome folder. They must be imported manually by the user. But this method works just as well as the two previous methods. The pure Alice0775 script loading method in 4th place is actually available only starting from Firefox 72. But I also got it working in Mypal 68 if I remember correctly. I have tested so much that it is sometimes difficult to keep an overview. If anyone is wondering why I'm bothering with other script loading methods at all when the best one has already been provided by me, then I should mention at this point that the Nuchi-Sporif script loading method no longer works as of Firefox 72. Incidentally, this applies to all Nuchi script loading methods. Since I don't know what @feodor2 plans to do with Mypal 68 in the future and to what extent compatibility will be maintained, it's good to know what alternatives are available. In any case, the methods in 4th to 7th place are also available for higher Firefox versions. When using the Aris-t2/Ardiman-Endor8 or the pure Endor8 script loading method, however, some scripts need to be additionally fixed which I have already successfully done in some cases but this is not always easy. In any case, these two methods led to more fixes to be done in scripts than the methods from 1st to 4th place and need deeper JavaScript and CSS knowledge. Unfortunately, the Xiaoxiaoflood script loading method in 7th place was the worst. Many of the scripts I use do not work with this method. Nevertheless, there are at least 7 methods to load UC.JS scripts in Mypal 68, even if they vary in their structure, user-friendliness and script compatibility. Greetings, AstroSkipper
  6. @Multibooter Just a little tip. If you want to mention and reach someone from this forum, then for example @AstroSkipper is not enough, it should look like this: @AstroSkipper. Otherwise it would only be pure coincidence if your enquiry was noticed.
  7. This is of course true, but it is not the only positive effect. Password protection prevents MediaFire's virus scanner from being able to scan these files and therefore from reporting any further nonsense. My uploaded files should only be downloaded by people who trust me and my information. It works according to the principle Take it or leave it! Nobody is forced to download anything from me. And if after downloading my files a locally installed antimalware programme reports files as malicious, they should then be excluded from scanning as usual.
  8. Only 2 of 62 scanners flag the cacert_Updater_Fixed_Recreated.7z file as malicious. That's a perfect result. One of these two scanners is Kaspersky. So again, forget about Kaspersky! It's trash just like Jiangmin.
  9. In April of 2022, I already recreated the cacert_Updater.exe due to false positives generated by some scanners. Read more about it here: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1217288 Strangely, the archive in this post has not been flagged as malicious by MediaFire although it contains the same cacert_Updater.exe file.
  10. The four files are now password protected and stops MediaFire from spreading further untruths. That's quite enough for me.
  11. The files were uploaded to MediaFire by me more than two years ago. Only in the last few months they have been flagged as malicious by MediaFire. They are probably using some new scanner that works just as well as Kaspersky.
  12. Just for clarification, the cacert_Updater.exe is not a root certificate updater for the Windows OS. It only updates the cacert.pem certificate bundle inside the ProxHTTPSProxy folder, exclusively the root certificates of ProxHTTPSProxy itself, so to speak. This is a quotation from my main article: That means it does not do the same as the Cert_Updater_v1.6.exe file. For more information, read the section 5.1 of my main article in the first post of this thread.
  13. Then, Kaspersky is as bad as the virus scanner which MediaFire is using. These files are all clean and virus-free. The cacert_Updater.exe file has been fixed by me as the original version from @heinoganda stopped working. It is totally clean. And the cmdow.exe file is a DOS file from a trusted source and checked by me. Unfortunately, some scanners don't like it but it is totally clean, too. So, forget about Kaspersky!
  14. Of course, you can download these files from the original source provided by @cmalex: https://mega.nz/folder/68dj2YTY#As2w31IO4Smr7gy6p1ciSg
  15. For my personal use, I have additionally modified the Nuchi-Sporif script loading method to load all UC.JS script files from a chrome subfolder called "Scripts". This gives the user a better structured chrome folder. If someone is interested how that can be done, just ask here. This modification has not been implemented in my new download package Mypal 68 CB requirements - Updated 12.01.2025.7z to avoid confusion.
  16. These two files, for example, both created by @cmalex, are incorrectly classified as malicious by MediaFire's virus scanner although they are virus-free: https://www.mediafire.com/file/pdy1cd8insmdq7g/ProxyMII_220717.7z/file https://www.mediafire.com/file/yb0xjos28l110xx/ProxyMII_230813.7z/file
  17. Script loader package for Mypal 68 - Update notification My download package MYPAL_68_CB_requirements.7z has been updated. I edited different files to tidy up the package and remove unnecessary code. Here is a short changelog: In the config-prefs.js file, comments added and the pref general.config.sandbox_enabled deactivated. In the config.js file, unnecessary code removed. In the userChrome.css file, information added how to import CSS stylesheets. In the userChrome.js file, the error "ReferenceError: XPCOMUtils is not defined" fixed in two different ways: either unnecessary code completely removed, or the corrected file userChrome.js.FixedJustForFunByAstroSkipper can be used (the extension .FixedJustForFunByAstroSkipper has then to be removed, of course ). Instructions in the Instructions - Please read me first!.txt file updated. The download link of my package Mypal 68 CB requirements - Updated 12.01.2025.7z can be found as always in the first post of this thread. Greetings from Germany, AstroSkipper
  18. I was able to finally get it after creating a mediafire account and through URL manipulation. Hello! You are the very first reporting problems with the download of files I hosted on MediaFire. In any case, all my files are clean and free of malware. If MediaFire really reports something like this, it is very wrong. I have now checked my MediaFire account, and indeed, some of my files uploaded years ago are suddenly and wrongly flagged as malicious. MediaFire seems to use a new virus scanner, and it must be very bad. Therefore, all flagged files will be replaced by me with archives protected by a password to free MediaFire from such false positives. The password will be provided in the section 11. Downloads of my main article in the first post of this thread. Four archives are incorrectly classified as malicious by MediaFire's virus scanner. Of course, all my uploaded files are virus-free. I have now re-uploaded these files with password protection so that MediaFire doesn't continue to make such nonsense. As always, the download links with the corresponding password will be provided in the section 11. Downloads of my main article in the first post of this thread. Cheers, AstroSkipper
  19. The last few weeks, or rather the last few months, I have expanded my JavaScript and CSS knowledge considerably. I started to develop not only new custom buttons for the legacy extension Custom Buttons and custom CSS stylesheets, both targeting Mypal 68, but also UC.JS scripts for Mypal 68 and compatible browsers. Additionally, I have tested and analysed all available methods for loading UC.JS scripts. I also put my favoured method, which I presented in the first post of this thread, to the test. The loading method in my download package MYPAL_68_CB_requirements.7z is based on the loading method of Nuchi and Sporif. At the time, I assumed that additional code inside the config.js file was needed to load UC.JS scripts. This code comes from the alice0775 project and, however, it is not needed at all for the loading method I have provided, as I have realised in the last few days. It is only needed if there is no binding via the userchrome.xml file. Fortunately, it didn't do any harm either, but I have nevertheless tidied up my package and got rid of unnecessary ballast. I will now create and upload a new download package which will also contain my fix for the error "ReferenceError: XPCOMUtils is not defined" in two different ways. What I can already say at this point is that my favourite Nuchi-Sporif method is one of the best of all regarding Mypal 68. More on this soon. Greetings from Germany, AstroSkipper
  20. If you are prepared to pay for an antimalware programme, I would have bought a RogueKiller licence. Glarysoft's Malware Hunter doesn't have many features, and I would rank it far behind RogueKiller. But to each their own.
  21. Don't you always do browser builds every week every time there's a change to the source code? I'm only just ordering cause you always build every week I can hardly believe what I'm reading here. A user of browser versions for which no money is charged and which have been developed on a purely voluntary basis for years (and this is of course very time-consuming!) has zero rights to order anything. I regard such comments as impertinent and disrespectful. What you can do with it is actually just this: And to give such claims a real reference again, new versions will come when they come. Be happy if something comes at all! AstroSkipper
  22. Yep, same here. It does not work in Mypal 68. You can test in Firefox 68 Portable and up if it is working at all. As I already wrote in my thread, not all extensions offered as compatible can be installed in Mypal 68.
  23. I was able to finally get it after creating a mediafire account and through URL manipulation. Hello! You are the very first reporting problems with the download of files I hosted on MediaFire. In any case, all my files are clean and free of malware. If MediaFire really reports something like this, it is very wrong. I have now checked my MediaFire account, and indeed, some of my files uploaded years ago are suddenly and wrongly flagged as malicious. MediaFire seems to use a new virus scanner, and it must be very bad. Therefore, all flagged files will be replaced by me with archives protected by a password to free MediaFire from such false positives. The password will be provided in the section 11. Downloads of my main article in the first post of this thread.
  24. I was able to finally get it after creating a mediafire account and through URL manipulation. Hello! You are the very first reporting problems with the download of files I hosted on MediaFire. In any case, all my files are clean and free of malware. If MediaFire really reports something like this, it is very wrong. These are the system requirements for ProxHTTPSProxy's PopMenu TLS 1.3 3V3. So, it actually should run on your Athlon XP computer. Especially, since @cmalex made it compatible with SSE only processors. And again, you are the very first reporting compatibility problems with ProxHTTPSProxy's PopMenu TLS 1.3 3V3 running on Windows XP SP3 machines with an Intel SSE2 processor. My main Windows XP computer is equipped with an Intel Pentium 4 SSE2 processor, and ProxHTTPSProxy's PopMenu TLS 1.3 3V3 works there like a charm . BTW, it was developed and tested on this computer. So, I fear you did something wrong, or all your machines are missing something.
  25. I have updated the download links of my All about custom buttons to let the tooltip look more compact as shown above. You can find them in this post: https://msfn.org/board/topic/183923-extensions-and-custom-buttons-for-uxp-browsers-corrections-modifications-adjustments-and-special-recommendations/page/46/#findComment-1274608
×
×
  • Create New...