ProxHTTPSProxy and HTTPSProxy in Windows XP for future use

[NotHereToPlayGames]

4 hours ago, AstroSkipper said:

And, unfortunately, you are not up to date.

To each their own, we all use our computers our own way.  My system is as "updated" as I want it to be 

[AstroSkipper]

1 minute ago, NotHereToPlayGames said:

To each their own, we all use our computers our own way.  My system is as "updated" as I want it to be 

No problem! Just an observation! 

[NotHereToPlayGames]

26 minutes ago, AstroSkipper said:

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 

I didn't get the new version.  Could be because I keep my inbox empty and you'll have to send as a "new" PM.  Thanks in advance.

[AstroSkipper]

6 minutes ago, NotHereToPlayGames said:

I didn't get the new version.  Could be because I keep my inbox empty and you'll have to send as a "new" PM.  Thanks in advance.

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

Edited August 2, 2022 by AstroSkipper
addition

[NotHereToPlayGames]

Just now, AstroSkipper said:

No problem! Just an observation!

My process is more of a slipstream process  --  https://ryanvm.net/forum/viewtopic.php?t=10623

[NotHereToPlayGames]

3 minutes ago, AstroSkipper said:

No problem! I'll send you the fix a second time.

Thanks.

[AstroSkipper]

32 minutes ago, NotHereToPlayGames said:

Thanks.

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

Edited August 2, 2022 by AstroSkipper
addition

[mina7601]

2 hours ago, AstroSkipper said:

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 

Strange, this time, I did not have any problems with paths having spaces, but, thanks for the new version anyway.

2 hours ago, AstroSkipper said:

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

Oh yes, you are giving me PopMenu 3V1's flashbacks!

[Dave-H]

2 hours ago, AstroSkipper said:

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. 

Understood, but your original version of StartProxy.exe was starting on boot correctly, it was only ProxHTTPSProxy.exe that wasn't (and still isn't of course).

Edited August 2, 2022 by Dave-H
Corrected the file name!

[AstroSkipper]

1 minute ago, Dave-H said:

Understood, but your original version of ProxyStart.exe was starting on boot correctly, it was only ProxHTTPSProxy.exe that wasn't (and still isn't of course).

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. 

[AstroSkipper]

25 minutes ago, mina7601 said:

Strange, this time, I did not have any problems with paths having spaces, but, thanks for the new version anyway.

Did you try the first fixed version of 3.1.0.0 automatically at Windows startup without any delay? Then, you'd have observed the problem, only if your install path contains spaces, of course. 

Edited August 2, 2022 by AstroSkipper
addition

[mina7601]

11 minutes ago, AstroSkipper said:

Did you try the first fixed version of 3.1.0.0 automatically at Windows startup without any delay? Then, you'd have observed the problem, only if your install path contains spaces, of course. 

Now, I tried it, and yes, you were right, it got me a "Windows cannot find" error. I tried it on a path with spaces, of course.

3.2.0.0 does work properly, though.

Edited August 2, 2022 by mina7601

[AstroSkipper]

2 minutes ago, mina7601 said:

Now, I tried it, and yes, you were right, it got me a "Windows cannot find" error. I tried it on a path with spaces, of course.

3.2.0.0 does work properly, though.

Very good! Thanks a lot @mina7601! That's what I meant. 

[Dave-H]

19 minutes ago, AstroSkipper said:

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

Now I am puzzled.
I thought it was actually OK with the original version of StartProxy.exe, and I've now confirmed it.
I've put the original version (3.0.0.0) back, and it still starts fine on boot, with no delay applied.
It was only ProxHTTPSProxy.exe that showed the problem and had to be delayed.

[AstroSkipper]

I will have a look in my other new files if there is code which doesn't work with paths containing spaces.