Leaderboard

Is your Windows 7 fully up to date? From answers.microsoft.com: Mine looks like this (Windows 7 updated till now with Server 2008 R2 patches (see My Digital Life Forums):

It was requested by someone. Plus, it can be built with a modified Python 3.13 (Python 3.9 might be unsupported by yt-dlp after 31 Oct 2025).

I can suggest to go and rest here, in Vichy, it's beautiful any time of the year, top quality of everything is guaranteed. Grab some Euros with ya tho, it's not cheap. You can look it up at TikTok, oh wait a minute... xD xD xD!

China is much different because of its political system, which is forbidden to talk about here. The most out-rightly insulting crap is that they shove their "way of living" onto us. with the help of TikTok as their cyber weapon. I'm very sorry you don't understand. Why they forbid Google, for example? Tell me. And why we need their crap, if they forbid our stations?

Serpentza on YouTube released video about Rednote. This guy knows China very well - he lived there and married on chinese woman. https://invidious.nerdvpn.de/watch?v=jjWairkG9lw

pls explain

This DLL Directory thing is probably part of the secure DLL loading patch KB2533623. I have it for FileZilla Server. I have not installed a 230 MB patch and Yt-dlp works for me. I did install a handful of others. Not sure where this function was added. I can send this MSU to you if you can't find it. So what do we do after 31 Oct 2025 ?

Maybe make a disk image before applying?

I got a 403 Forbidden today. Now it works again after an update. Google can put their web where the sun doesn't shine. The problem with opus audio having a WEBM extension is still there. My player doesn't pick it up until it is given and audio extension like MKA.

I also just tried this PCI-Express to eSATA card with ASM1061 chipset: and also in this case, both 4TB and 16TB GPT disks connected directly to the eSata ports of the same card seem to work smoothly thanks to the Paragon driver v10.1.25.779.

Thanks to the Paragon GPT Loader driver v10.1.25.779, HDDs initialized as GPT can be recognized correctly in XP as data disks, but only if the motherboard bios has the option to enable IDE mode. In AHCI mode, GPT HDDs are not recognized even with the Paragon driver. The following way could allow XP to recognize GPT partitions using the GPT_Loader driver even on a system configured in AHCI mode. It is required to use a PCI-Express to Sata card with the Asmedia ASM1061 chipset which must have a selector button that allows you to choose between three positions: "AHCI Boot", "no Boot" and "IDE Boot". I have tested these two ASM1061 cards: this is the back of one of them (the other contains the same info on the rear): After selecting "No Boot" and plugging the card into the PCI-Express slot, on the boot XP recognizes it immediately as "Standard Dual Channel PCI IDE controller" with "Primary and Secondary IDE Channels". No Asmedia driver required. Here is how the GPT disk just plugged to the Asmedia card is recognized by XP before installing the Paragon driver: I chose to install the Paragon driver using a different gpt_loader.inf than the original one. Thanks to the two users "DCT" and "satmonk" with posts #30 dated 10/18/2015 at 14:31 and #33 dated 02/2/2017 at 21:08 at link: http://hardwarefetish.com/524-paragon-gpt_loadersys-bsod-analysis-and-fix it is possible to create a special .inf file that can be used to install the Paragon GPT Loader v10.1.25.779 only for the GPT disk just connected to the PCI to Sata card. I made some changes in the gpt_loader.inf file mentioned in the previous link: under the section [Strings] where I replaced Paragon = "Paragon and Co BIG HDD" with Paragon = "Paragon Software Group" and DiskId1 = "3Tb HDD disk driver" with DiskId1 = "GUID Partition table Driver Disc" The installation procedure of the Paragon driver must be executed by selecting the GPT disk -> update driver -> (advanced) -> don't search -> have disk -> browse to the path containing the required files (gpt_loader.sys, gpt_loader.cat and the special gpt_loader.inf file created above). You will get this warning: and of course you need to choose "Yes" to install the driver. The system reboot is prompted by the system, and the azure screen asking to chkdsk the GPT disk will probably appear during the next boot. I avoided doing this the first time and did it in another test, in both cases I found no problems with proper HDD operation. The driver installation procedure described above is needed for each new GPT disk connected to the asmedia card. Here is how the disk is now detected: Below is a 16TB GPT disk connected to the same asmedia board (although it has 4 sata ports only two disks connected at the same time seem to be working): In XP, I wrote many GB to the 4TB disk and then tested all the files, which were undamaged. I ran chkdsk in both XP and Win10 for both GPT disks and no error was detected. Switching disks between these O.S. also worked well. I also got the same results by selecting "IDE Boot" mode on the same Asmedia PCI-Ex cards. Some notes: - in my test I used disk.sys v5.1.2600.5597 and partmgr.sys v5.1.2600.5512. The versions from win2003 of these drivers can result in data corruption; - one or two time I encountered the error code 39 during the installation of the GPT Loader for disks just connected to the card. A restart is enough to overcome that error and then the disk is correctly detected as GPT; - due to possible incompatibility with the Paragon driver, the WinXPPAE patch to recognize the total RAM installed in the system or only 4GB can't be used, otherwise data corruption occurs; - after the first chkdsk of the 4TB disk executed in Win10, the next time it was connected to XP it was necessary to re-install the Paragon driver, which then did not happen for the 16TB disk and other GPT disks; - I tried five GPT disks connected to the asmedia board and all has been recognized correctly but I cannot be sure that this is the case for any GPT disk; - the disks tested shutdown correctly when removed via the HotSwap! tool. Please consider that I have not had the opportunity to examine in depth all aspects of using GPT disks in the above mode due to lack of time (and later will probably have even less). Those interested in trying it out will have to be aware of the risks associated with possible data loss, so it is better not to use disks with important data. What I have reported above is what has occurred on my system. Proper working on other systems is not guaranteed, because other things may lead to a different result from the one I got. Anyone who would like to apply the above method does so at his own risk.

How's this relevant to the TikTik closure? I kinda suspect they will perform the ban through the IP.

For some reason, the attachment didn't work the first time. Here's my WD made by Hitachi, works since 2020. WD80xxxx is rather old, the newer ones most likely changed their names to something else, so please, do a research before you buy. https://www.pcworld.com/article/468946/western_digital_closes_hitachi_gst_acquisition_to_operate_separate_subsidiaries.html

Cixert, as of lately, I enjoy WD models they acquired from Hitachi, they are still made by Hitachi. For example, take a look, the HDD is almost always on 24/7, since 2020, no problems so far. Millions of reads/writes almost every day, heavy usage. But they need proper cooling. But a simple vent would do just fine, too.

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.

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.

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.

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.

Yep! I noticed that too during my tests. I will correct my post accordingly. Here is my working script for passing only example.com to the local proxy: function FindProxyForURL(url, host) { if (shExpMatch(host, "example.com")) { return "PROXY 127.0.0.1:8079"; } else { return "DIRECT"; } } This script can be enhanced to pass more than only one URL to the local proxy, of course. So, your question has to be answered with yes. It's me.

Proxy Switcher and Manager 0.5.0 is the last compatible to 360Chrome due to the manifest change from 2 to 3 and works great. I tested Direct, Manual Proxy (set here the local proxy 127.0.0.1:8079) and PAC Script, and all worked as it should. So, a working PAC script (not a PAC file but a PAC script under the section Inline) can be inserted directly in 360Chrome. No need to do that in IE8 and no need to activate ProxHTTPSProxy in the system proxy settings of IE8 by inserting 127.0.0.1:8079 there. Simply call up ProxHTTPSProxy.EXE directly from the main directory of my package instead of StartProxy.exe! And that means by using this extension you can also use @cmalex's ProxyMII if you prefer a pure proxy without any comfort. BTW, all that was done in 360Chrome in a few minutes.

And @Anbima, IE8 is very old. I wouldn't implement a PAC file there. As @VistaLover already explained, IE8 has poor support when it comes to PAC files loading from disk. Install instead a proxy extension with PAC scripts support in 360Chrome as this browser doesn't seem to natively support it any longer. For example, this one: https://chromewebstore.google.com/detail/proxy-switcher-and-manage/onnfghpihccifgojkpnnncpagjcdbjod, and there are others, too.

Check the correct URL of the website which is supposed to use the local proxy! It should be example.com for testing and not *.example.com. But in the end, I don't understand the whole effort for just two websites. It would be easier to use a proxy extension to switch from the direct connection to the local proxy or vice versa whenever necessary.

Thanks again for sharing further, detailed information! And as this thread is about proxies, you are absolutely on-topic.

Thanks for the information and the linked documentation! Personally, I never used a PAC file. But one thing is clear you never stop learning. And here are some further PAC file examples: https://findproxyforurl.com/example-pac-file/