Leaderboard

next build will change parse-thread count from core-count*4 to core-count - 1 to see if this helps. if not, it will further reduce back to single parse-thread later.

I also downgraded to 4-18 release of Serpent 52.9. On imgur.com it just stopped responding after going through a few posts. BSOD that some mentioned could also be because of excessive fragmentation the browser causes with its cache on disk. I remember long time ago (2013) I had the same problem with fireferret.

Well, knowing now internals of ESDI_506.PDR I solved this puzzle completely from the second attempt (the first attempt was disabling IOR_IDE_PASS_THROUGH handler to prevent BSoDs): IDENTIFY (including ATAPI devices) and SMART commands work in AHCI.PDR Plus fixed few other bugs seen in process of main development, I personally recommend to pay attention to N5. http://sweetlow.orgfree.com/download/ahci.zip readme: Patches of RLoew's AHCI.PDR 3.0 1. Fixed broken handler of information about internal structures (system hangs/reboots when trying to read them). 2. Fixed accessing an uninitialized pointer variable (wild pointer) in the power-down handler (SYS_POWER_DOWN) leading to BSoD / hang-on / reboot. Thanks to https://github.com/PluMGMK 3. Fixed bug in the handler for ATA commands without data transfer, such as standby drive or working with removable media. These commands were previously just not executed. 4. Made new working handler of IOR_IDE_PASS_THROUGH request, IDENTIFY (including ATAPI drives) and SMART commands are supported. 5. Fixed random CPU port write access in some cases on executing Input/Output Request. 6. Fixed bug in enable Media Status Notification function. 7. Memory copy speedup in Input/Output Request handler.

Hello again, my dear beta testers, @Dave-H, @mina7601, @NotHereToPlayGames! I modified the file ActivateProxy.exe to work as it should. If an user decides to edit the config.ini and change the FrontPort setting for some reasons, then my program ActivateProxy.exe will now activate the port value which has really been set in the configuration file config.ini. Please, replace the old file by the new one and test it! Edit the value of the parameter FrontPort, e.g., FrontPort = 8089, in the file config.ini.and execute my program ActivateProxy.exe or StartProxy.exe! Check if the new value has been set correctly by executing OpenLANSet.exe! You can do all that via the popmenu. Don't forget to set the FrontPort back to the old, well-known value of 8079 in the file config.ini after testing! I'll send you the download link of the modified version via PM as usual in the next minutes. In any case, the settings in the configuration file config.ini of ProxHTTPSProxy will be respected and applied again. Cheers, AstroSkipper

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.

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?

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?

Thanks for your quick reply and your opinion! I think so, too. But I am a mathematician, and somehow, it bothers me.

@Dave-H, @mina7601, @NotHereToPlayGames What do you think about that? Did you ever change these port settings?

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

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.

s*** can happen, but don't worry! I didn't check it, either!

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.