Jump to content

AstroSkipper

Member
  • Posts

    4,577
  • Joined

  • Days Won

    496
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by AstroSkipper

  1. I'll try to change that. I hate such inconsistencies. If you edit the config.ini in my popmenu, the changes should have an effect and work in any cases I think. I am not a professional but a hobby batch programmer. But I know a programmer has to think of all cases which could happen.
  2. Do you mean that I should leave it as it is? I know you don't like that kind of inconsistency, either. Isn't it?
  3. Thanks for your quick reply and your opinion! I think so, too. But I am a mathematician, and somehow, it bothers me. If an user decides to edit the config.ini and change the FrontPort setting despite my hint not to do that, or it has to be changed for some reasons, then my program ActivateProxy.exe will activate the wrong port. And I don't really like that so much. What do you think about such a scenario?
  4. Thanks for your quick reply and your opinion! I think so, too. But I am a mathematician, and somehow, it bothers me.
  5. @Dave-H, @mina7601, @NotHereToPlayGames What do you think about that? Did you ever change these port settings?
  6. Hello again, my dear beta testers, @Dave-H, @mina7601, @NotHereToPlayGames! I forgot to mention a very important thing! Do not change the FrontPort setting 8079 of ProxHTTPSProxy in its configuration file config.ini! I've programmed the automatic activation to use this well-known standard port of ProxHTTPSProxy each time StartProxy.exe is executed. Also in the versions of @heinoganda this port was always the default. I think the users never changed it in the past. It would be a bit more complicated (but not impossible) to check and import this setting directly by a query of my program ActivateProxy.exe each time when it is executed. Anyway, I will add this information to the documentation and think about it the next days. Furthermore, I would like to ask you to do your final tests. As far as I can see the beta test is slowly coming to an end! Cheers, AstroSkipper
  7. Hello @NotHereToPlayGames! Yep! That's all! Thought you wouldn't be around here anymore. Any news for me? BTW, the docx file is none of my files, it's the corrected version from @Dave-H.
  8. I would call it an almost portable program package. It's not one program but a package of different programs. A portable installation is not bad, either. Thanks a lot for your efforts and your confirmation! Very good!
  9. What do you mean with a complete install? Most of my package is portable. Anyway, delete the keys of PopMenu and Min2Tray in the key RUN and execute Configure PopMenu.exe! Check if the two autostart entries will have been added again when my configuration utility has finished its work! And, check if all pathes are correct in PopMenu!
  10. Which version of Configure PopMenu.exe did you use? The version 3.1.0.0 is faulty. Use the new one in version 3.2.0.0!
  11. My dear beta testers, @Dave-H, @mina7601, @NotHereToPlayGames! Two programs had to be fixed, the program Configure PopMenu.exe by cleaning its code in regards to the space bug, and the program EnableProxSysWide.exe which incorrectly calls the old start program ProxHTTPSProxy_PSwitch.exe instead of StartProxy.exe. I'll send you the download link of the fixed versions via PM as usual in the next minutes. Please, check if they work properly! Cheers, AstroSkipper
  12. Correct! Correct! Correct! My version is portable except the settings of Min2Tray, the autostart settings of PopMenu and Min2Tray, and ProxHTTPSProxy's certificate. From now on, you do not need @heinoganda's version. @cmalex's proxy supports all TLS protocols from 1.0 to 1.3.
  13. I described this feature in my article, the first post in this thread. It enables the proxy system-wide in Windows XP. For example, the Windows Update service has to look for updates on its servers. When this feature is enabled, then the connections will go through this proxy. But, if the proxy is running only locally, then they won't.
  14. No problem! At first, thank you very much for deeper testing! That's what I need! Did you never use this feature in the past? Anyway, that kind of testing you are doing now is what ensures to find misbehaviour or bugs of programs. Not believing or assuming but checking! Cheers, AstroSkipper
  15. Well, your fixed "Configure PopMenu.exe" gives the error "Error: Too many command-line parameters" during configuration. Your original "Configure PopMenu.exe" (inside ProxHTTPSProxy PopMenu TLS 1.3 3V3 archive itself) does not give the error. Very good! Now, you know what I mean. Testing everything is the only way to find such bugs. Frankly, I wanted to fix the space bug and overdid it a little bit. Anyway, you're really great! Thanks a lot for your find and confirmation! I already cleaned the code, and a fixed version will be uploaded, too!
  16. @mina7601! Please, do some further tests to ensure that there are no other bugs! Click all possible combinations! A fixed version will be uploaded, too! Thanks for your efforts in advance!
  17. s*** can happen, but don't worry! I didn't check it, either!
  18. Yep! Finally! I would have been surprised if that had worked! The program was written by me for @heinoganda's proxy. So, not all features were tested, right? q.e.d.
  19. Yes, they all work. No, unfortunately not! Check especially features referring to the system-wide use of the proxy!
  20. Yes, of course! Do it if time is available but, please, be as accurate as possible! And I definitely know that you can be! Thanks for that in advance!
  21. Thanks a lot for your request and your quick reply! Please, try to do all from scratch, once again! Clean up everything referring to previous installations of ProxHTTPSProxy! Thanks in advance!
  22. A beta test has to generate data, as complete and traceable as possible, to let a creator correct or improve their programs.
  23. These are the results I have so far. No detailed data is available from @NotHereToPlayGames until now! I marked red the statement I asked for. Please, check this statement once again! Cheers, AstroSkipper
  24. Unfortunately, I heard a lot about TrayIt!, the unaccustomed systray icon's behaviour of ProxHTTPSProxy, and a non-existent autostart feature, but less about the already provided features of my package. Did you really test all existent features? And, did you uninstall all previous versions of ProxHTTPSProxy before testing as recommended? Furthermore, did you delete all previous global and local path settings in regards to ProxHTTPSProxy? And I mean all of my beta testers, @Dave-H, @mina7601, @NotHereToPlayGames, of course! Cheers, AstroSkipper
×
×
  • Create New...