Leaderboard

I agree as a general off-topic observation that while you do, of course, need to have a general awareness of security and privacy issues when working online, there's really no need to be paranoid about it.

Unapplicable legal snippets. msfn.org is an international forum, not a USA forum. My Ancient Version of Kaspersky is definitely not an unlawful program for me or for the great majority here at msfn.org. Why don't you wear a head scarf in your msfn.org picture, to obey Iranian Islamic Law, to avoid offending strict Moslems? Maybe you should tell your fellow Canadians to stop travelling to Cuba in winter, because U.S. laws declare tourism to Cuba as illegal. There are good laws and bad laws. Would you have obeyed in 1935, as a good Canadian, the German Nuremburg Laws https://en.wikipedia.org/wiki/Nuremberg_Laws and betrayed Jews to German concentration camps? Would you have obeyed in 1964, as a good Canadian, the United States Jim Crow laws https://en.wikipedia.org/wiki/Jim_Crow_laws ordaining racial segregation and racial discrimination? There is no need to commiserate here with the lack of freedom of U.S. subjects. This is an international technical forum. Hopefully, U.S. subjects will eventually get their freedom back. And no more unapplicable legal advice from a U.S. fifth column in Canada.

@genieautravail The ungoogled version has the flags #disable-encryption and #disable-machine-id. Enabling them will disable encryption and machine ID creation, allowing you to transfer your profile to another computer. The developer will not transfer them to the regular version, leaving the functionality completely stock. Therefore, for the regular version, use third-party tools to create a portable version.

All revisions (ALPHA/I386/MIPS/PPC) of Windows NT 4.0 and Windows NT 3.51 has issue with maximum possible total video mode count limit and it is around 296 modes. Any mode provided by driver above 296 will be cutted down. It is not depended on driver issue, this bug is inside Windows NT system itself. Windows 2000 and later does not have such issue. Here it is a binary patch for Windows NT 4.0 (I386, any SP/edition, language) for SYSTEM32\WIN32K.SYS : Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0x6A to 0x68 0xB8 0x00 0xFF 0x03 0x00 0x6A Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0xFF to 0x68 0xB8 0x00 0xFF 0x03 0x00 0xFF Recalculate checksum, f.e. EDITBIN.EXE WIN32K.SYS /RELEASE Here it is a binary patch for Windows NT 3.51 (I386, any SP/edition, language) for SYSTEM32\WINSRV.DLL : Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0xA1 to 0x68 0xB8 0x00 0xFF 0x03 0x00 0xA1 Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0xFF to 0x68 0xB8 0x00 0xFF 0x03 0x00 0xFF Recalculate checksum, f.e. EDITBIN.EXE WINSRV.DLL /RELEASE This will increase total limit to 1190 modes. Below are results in screenshots, before and after.

Well... That's the latest official 'xidel-0.9.9.20230616.8842.e14a96920e01.openssl.win32.zip' on https://sourceforge.net/projects/videlibri/files/Xidel/Xidel development/. Or 'xidel-0.9.9_2025-02-22-git-3e7e88a62307-openssl-win32.7z' on https://rwijnsma.home.xs4all.nl/files/xidel/personal_builds/, which I compiled myself. On Linux Xidel by default requires OpenSSL to open https urls at all. On Windows the normal win32/win64 binary relies on Microsoft's SChannel SSP (Secure Channel Security Service Provider) to do that. On Windows XP SChannel is limited to TLS 1.1, while practically all websites nowadays use TLS 1.2 and newer. So Benito, Xidel's author, created the openssl-win32 build especially for WinXP users. Xidel supports all OpenSSL versions. If you'd like to know what Xidel can do, I suggest you have a look at StackOverflow here or here. Obviously every piece of software that requires the OpenSSL dlls for internet connectivity can use these.

The "AutoPatches" for My Ancient Version of Kaspersky I succeeded in updating both the application modules and the signatures of My Ancient Version of Kaspersky with a single combined update, without a license key and without activation. By installing the final AutoPatches, My Ancient Version of Kaspersky has been updated to the ultimate final version, with the most recent program file digitally signed OK 26May2014. The screenshot above indicates the final AutoPatch "r" next to "Application version" and the Database release date "2/4/2026". Once knowing how-to, preparing future combined updates will be quite easy. The term "AutoPatches" by Kaspersky corresponds roughly to the term "Hotfix" by Microsoft. The screenshot above indicates "Update completed successfully" and "Update application modules: Yes". The signature updates were from a Kaspersky Lab update server, the application updates ("AutoPatches") were from my personal archive. Signature updates and application updates ("AutoPatches") were combined into a single update folder. The screenshot above indicates signatures of 2/4/2026 and the message: "Database status: Reboot is required". This message "Database status: Reboot is required" is displayed by My Ancient Version of Kaspersky when the update of the application modules via AutoPatches is pending. A tiny red square is added to the Kaspersky icon in the System Tray, indicating that AutoPatches are pending. During the reboot after the update, the Kaspersky driver updates and installs the program files contained in the AutoPatches and updates the registry, completely hidden and invisible to the user. StartUp Organizer, for example, which I use as a watch dog, does NOT notice any changes before, during and after the reboot. After rebooting and AutoPatching, the Kaspersky icon in the System Tray looks normal again, without a tiny red square. The successful installation of the AutoPatches is indicated in the About screen above by the display of "r" [=version of the AutoPatches] next to the Version (Note: the About screen is displayed by right-clicking on the Kaspersky icon in the System Tray -> About) and in the Support window (1st screenshot, at the top of this posting). Also, LastSuccessfulUpdate in the registry contains a hex value (Unix timestamp), which confirms that the update was successful. Furthermore, virus-checking with the updated application module and the new signatures works fine. The installation of the final AutoPatches plus a signature update of My Ancient Version of Kaspersky had faced three challenges: 1) The files of the final AutoPatches were removed from the Kaspersky Lab update servers and are most likely not available anywhere in the internet. 2) Kaspersky Lab does not provide license keys for My Ancient Version of Kaspersky anymore, which would permit multiple updates. My Ancient Version of Kaspersky is an unexpiring trial version and can only be updated once. An initial update with the final AutoPatches followed by a second update with current signatures is therefore not possible. Only one update is possible, either an update of the signatures from the Kaspersky Lab server or an update of the application module from my personal archive, but not both.. 3) The digital signature of the .xml file in the subfolder \index\ in the update folder impedes the combining of AutoPatches and current signatures into a single update folder. Before August 2019 the online updates from Kaspersky Lab of My Ancient Version of Kaspersky had consisted of three sub-folders: \AutoPatches\, \bases\ and \index\. After August 2019 no sub-folder \AutoPatches\ is created when downloading updates. The sub-folder \AutoPatches\ contained updates of the installed application modules, \bases\ contained the signature updates and \index\ contained only a .xml file validating \AutoPatches\ and \bases\. The .xml file in \index\ contains at the end a string which is an encoded digital signature generated using the private signing key of Kaspersky Lab. Changing text in the .xml file without updating the signature at the bottom will result in the error message "Invalid file signature" when trying to update. The final release of December 2012 of My Ancient Version of Kaspersky had been updated by several sets of "AutoPatches" supported by Kaspersky until 2017, identified by a letter of the alphabet appended to the build number of Kaspersky Anti-Virus. The last AutoPatch for My Ancient Version of Kaspersky is "r" and contains for example an updated basegui.dll, digitally signed OK 26May2014. The AutoPatches for My Ancient Version of Kaspersky were available from the Kaspersky Lab update servers until about 2018. When I tried to update in August 2019, all files of the AutoPatches for My Ancient Version of Kaspersky had been removed from the Kaspersky Lab update servers and My Ancient Version of Kaspersky could not be updated to release "r" (about 26May2014) anymore. The application modules of My Ancient Version of Kaspersky consequently remained those of the final release of December 2012, without any AutoPatches applied.. In addition Kaspersky Lab removed the text string which identified My Ancient Version of Kaspersky, from the digitally signed .xml file in \index\ downloaded from Kaspersky. Kaspersky Lab must have decided by August 2019 to definitely stop supporting My Ancient Version of Kaspersky, because they removed the application update files from their update servers and made it generally impossible to update the program with AutoPatches by removing the string permitting updates of My Ancient Version of Kaspersky from the digitally signed .xml in \index\. The final AutoPatches, including "r", probably also improve the Protection Components of My Ancient Version of Kaspersky. I have used My Ancient Version of Kaspersky only as an on-demand scanner, I have no need for the Protection Components. Nevertheless, I may eventually add the Protection Components to the installation, for further testing and to see whether activation is required to get the Protection Components to work. According to the User Guide of My Ancient Version of Kaspersky, if you select "Activate later" after installation, "you will have access to all the application's features, except for updates (only one application update will be available)".

I think inserting the brackets is logical and correct.

I have updated my old guide about compiling Chromium. Now it only applies to compiling clear Chromium. A new one will be created for building with e3kskoy7wqk patches.

Sorry to resurrect this again but I think the yt-dlp4vlc script has an error. I think the probe function is incorrect . . . function probe() -- Check if the input is a YouTube link return vlc.access == "http" or vlc.access == "https" and (string.match(vlc.path, "youtube%.com") or string.match(vlc.path, "youtu%.be")) . . . should be . . . function probe() -- Check if the input is a YouTube link return (vlc.access == "http" or vlc.access == "https") and (string.match(vlc.path, "youtube%.com") or string.match(vlc.path, "youtu%.be")) . . . notice the brackets around the first 'or' pair. Bit marginal but without those brackets any http url will return true. Ben.

Yes, apparently it has to do with the switch from icu63 to 78. I wrote on December 25th: "Latest RT's releases 20251225: These can't start anymore with the roll back of only XUL.dll 20250531 and mozsqlite3.dll (nss3.dll) 20250531. Now ICU78 and mozjs.dll have to be swapped to previous version 20251220, too. So this procedure makes less and less sense in the future." More in-depth investigations are pending.

Hi, I am going to build from scratch a Lan driver for XP SP3 for any i219. I use Ndis5.1 original from XP, not Ndis6 from Vista, win7 etc. Just now, for the very first time, I get this my lan driver startet under XP. Oh crazy..what a hard work with Windbg Dietmar 0: kd> !devnode 8b5e8ee8 DevNode 0x8b5e8ee8 for PDO 0x8b51ccf8 Parent 0x8b5e9998 Sibling 0x8b5e8dc8 Child 0000000000 InstancePath is "PCI\VEN_8086&DEV_15B8&SUBSYS_15B81849&REV_00\3&11583659&0&FE" ServiceName is "i219" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) StateHistory[07] = DeviceNodeEnumerateCompletion (0x30d) StateHistory[06] = DeviceNodeStarted (0x308) StateHistory[05] = DeviceNodeStartPostWork (0x307) StateHistory[04] = DeviceNodeStartCompletion (0x306) StateHistory[03] = DeviceNodeResourcesAssigned (0x304) StateHistory[02] = DeviceNodeDriversAdded (0x303) StateHistory[01] = DeviceNodeInitialized (0x302) StateHistory[00] = DeviceNodeUninitialized (0x301) StateHistory[19] = Unknown State (0x0) StateHistory[18] = Unknown State (0x0) StateHistory[17] = Unknown State (0x0) StateHistory[16] = Unknown State (0x0) StateHistory[15] = Unknown State (0x0) StateHistory[14] = Unknown State (0x0) StateHistory[13] = Unknown State (0x0) StateHistory[12] = Unknown State (0x0) StateHistory[11] = Unknown State (0x0) StateHistory[10] = Unknown State (0x0) StateHistory[09] = Unknown State (0x0) StateHistory[08] = Unknown State (0x0) Flags (0x000000f0) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED CapabilityFlags (0x00002000) WakeFromD3

Hi Isolar, long time no see. About your question: there are two possibilities, or their combination. 1) Your HD Audio controler needs a nosnoop bit set, you can check with WPCREdit. 2) The parser of WDMHDA identified some verbs you didn't use in your HDAICOUT.HDA. Possible candidates: 'opening' inputs (mixer?), EAPD or GPIO. Search in this thread for verbs.

Hi Drew, With initial help from Deomsh over at the 'Audio driver for Realtek HD Audio' thread, I have been using Watler's driver to get HD Audio working on Windows 98 laptops for a while, and came across one that I had some trouble with. Currently I have managed to get SoundMax AD1981HD working on a HP6710b laptop, IDT 92HD75B3X5 working on a HP 6550b laptop, and Realtek ALC272 working on a Lenovo S10-3 laptop with Watler's. Attempting a Lenovo S20-30 proved difficult as the codec was identified as 10EC 0280 of which I could not locate a datasheet for. I used HDAICIN responses to identify all NID's/CAPS and found the connection path to be the same as ALC 272 (and most other Realtek codecs from the looks of things) with $01 = AFG, $02 = DAC, $0C = Audio Out connected to NID $14, and NID $14 = Line Out. I managed to create a working HDAICOUT.HDA file but no sound. I had stumbled across your driver (great work I can see this being invaluable in the future!) and trialed v16, but sadly no sound to start with. So I re-installed Watler's to try some other options. What I notice is that your driver, although removed from device manager and 're-installed' to Watler's, is maybe still using the registry entries, so when I go to multimedia settings I can see the WDM driver still listed as an option, along with the midi/volume control, however Watler's is selected and installed. The HDA.SYS driver file still exists in windows\system32. The veeeery interesting thing here is that this combination has helped me to get sound working (although buggy) on the S20-30 laptop! I have no idea how or why this works but hoping you could shed some light on it, or I can provide you some more info that may be able to help you with development? I did try to rename HDA.SYS to HDA.BAK and rebooted but got no sound at reboot which indicates to me that although Watler's driver is installed it is still somehow using HDA.SYS in combination with HDA2.DLL to route the sound to the speaker - I am good with verbs but not with codec initialization, CORB, RIRB etc. To note: HDAcfg.ini from Watler's driver shows codec index $2 is active, which is incorrect (this is the HDMI audio out, whereas the 10EC 0280 codec is on index $0) so how I am getting any sound at all is a mystery.. At boot I get a high pitched squeal through the speakers until the initial windows start sound finishes, then I can go to sounds and play the sound samples. DirectX 9C is installed and runs the tests all okay. Happy to assist here with any information I can provide to get you further and help me understand why sound works with this combination, just let me know if anything is required. All the best and I will be following your progress. Cheers!

I did find a site which had links to many downloads of AutoPatches: https://filemood.com/result?q=autopatches Unfortunately, there were no AutoPatches for my Ancient Version of Kaspersky and the download links are dead bittorrent magnet links. Kaspersky Lab has 30+ products with signature updates, with different versions etc, so the chance is exceedingly small that the relevant AutoPatches are still available anywhere in the internet. Maybe in archives of corporate users of Kaspersky of 10+ years ago, although I doubt that corporations archive old stuff that long. OT: When I looked into my own personal archive I have found an AutoPatch containing avp.exe v6.0.3.851 for the last version of Kaspersky Anti-Virus for Windows 98. klif.sys in this newly-found AutoPatch is digitally signed OK 1Apr2009. I had previously thought that Kaspersky Anti-Virus v6.0.3.844 (28Apr2008) was the last version for Windows 98, but this newly-found AutoPatch may update the last Win98-compatible build of Kaspersky Anti-Virus even further. This AutoPatch seems to be a major final update, it contains 27 files. What confuses the matter is that this newly-found AutoPatch was in a sub-folder \6.0.3.830\ with a lower version number than Kaspersky Anti-Virus v6.0.3.844 (28Apr2008) for Windows 98. Eventually I will have to check whether this newly-found AutoPatch can be installed under Win98 and whether the resulting ultimate final build for Win98 can be updated with current signatures.

We all know where this is going to go. Please get back on topic.

Then you need to promptly delete everything you posted about the unlawful programme and start to obey your government. Probably, it's the right time to consult a lawyer. USA citizens - they do need to obey sanctions. "All U.S. citizens and permanent residents must comply with U.S. sanctions, regardless of their location. This includes individuals and entities within the United States and U.S. incorporated entities and their foreign branches." It's against the law, what you do! See the links. https://ofac.treasury.gov/faqs/11 https://www.sgrlaw.com/ttl-articles/860/

I understand you weren't addressing me specifically, and your general observations may well be correct. Yet, I think it's rather telling of a person's character when they let something little like "Micro$oft" get them riled up. To be clear, I use many Micro$oft products, and I actually like some of them! But I haven't found much to like in Windows versions beyond 7 (well, 8.1 wasn't too bad). Unfortunately, neither 7 nor 8.1 is supported any longer. I have no problem with that - few companies can afford to support decades-old products - but M$'s business model depends on them not giving me the choice to remain on an unsupported OS, even though I knowingly accept any security risks from doing so. Thus, I choose both to visit sites like MSFN, in order to keep Win 7 going; and to mildly protest M$'s attempts to force me to pay them for an OS I strongly dislike, with that little dollar sign.

Stuttering and freezing on YouTube is not a "bug". It's expecting too much of an old processor, an old OS, and backported browsers to NOT stutter and freeze. There are userscripts that can force h.264 and to force less-resource-hungry resolutions. Again, expecting too much is not a "bug", it's a "reality check". Another thing that I find helpful is to *INTENTIONALLY* "throttle" my internet speed. It does not cause "lags", it forces the streaming service to NOT send me UN-NEEDED 4K.

@Slavich Shazam has already been fixed. Stuttering and freezing of sound and video on YouTube is usually associated with a weak processor that lacks the power to process 1080 video, especially if it is VP9 and even more so AV1.

@VistaLover I have uploaded an updated Vista+ compatible PyInstaller here. Could you test if the yt-dlp built with it works well on your Vista system?

My primary system for general browsing is still on Windows 7, so that may not be correct. The three browsers I am running surely cannot be anywhere close to being modern by this point: Iron 109.0.5550.0 Chrome 109.0.5414.120 Firefox 115.32.0esr (this one actually does still update actually)

Our supervisor says Cloudflare isn't fake. Read a lot of posts where MSFN members do solve Cloudflare ans other verification captchas. I immediately close such websites.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260131-3219d2d-uxp-6ee9e34e29-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260131-3219d2d-uxp-6ee9e34e29-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260131-3219d2d-uxp-6ee9e34e29-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260131-d849524bd-uxp-6ee9e34e29-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2914 - Explicitly allow mixed content websockets on localhost. (151ef21890) - Issue #2828 - Follow-up: Simplify rule node tracking and ensure rule walker state isn't reset for the first child processor (226a443c96) - Issue #2916 - Restore the ability to set a default log level when using MOZ_LOG (a8960dc462) - Issue #2889 - Follow-up: Update eventPtr/eventEndPtr for XML_ParseBuffer (4b983c32b0) - Issue #2889 - Follow-up: Add patch for XML_ParseBuffer. (e5497c8425) - Issue #2895 - Implement 32-bit compatible Xoroshiro128++ (0dbad452e6) - MoonchildProductions/UXP#2351 - Fix webrtc video encoding on macos (3224ec7ddd) - MoonchildProductions/UXP#2351 - Fix webrtc for Windows and Linux based on MacOS fix (1d03a05e54) - Whitespace Compatibility for ICU 72+ (20525d238b) - Issue #2403 - Implement SubmitEvent functionality (#2919) (9b3d172a95) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - import from mozilla: Bug 2010411 - CLDR 48 'h' hour format is possibly web incompatible (3b9a3ec8e0) - Revert "Issue #2895 - Replace XorShift128+ with Xoroshiro128++" (75ca0c37f8) - Revert "Revert "Issue #2895 - Replace XorShift128+ with Xoroshiro128++"" (952e3022b8) - js-random: reorder Xoroshiro128++ code flow to reduce intermediate registers (454565b2ac) Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Funny, instead saying thanks for sharing, another request? And yes I have them all, spend a lot of time with them.

So, will they tell you what they actually did, or not? Just saying "it worked" isn't helpful.

How to force Aero on vista RTM "the reg hacks were disabled in the final release, so as far as I know there will be no way to enable" https://www.experts-exchange.com/questions/22128056/How-to-force-Aero-on-vista-RTM.html

Beep

Nottingham

Actually this bug is present on Vista, too. It's not "XP-only", like someone there tried to imply. Therefore, you're in the wrong right repository, Dave, you can edit the post and include Vista so they get out of your hair. They have no respect to the famous moderator!

No, it was Thorium's creator who referred to this in the quoted reply.

Alex313031: "I have fixed GDI fonts being askew by rolling a newer version of Skia and then using a patch that win32ss created. " https://github.com/Alex313031/Thorium-Win/issues/210#issuecomment-2081336104

Kippers

Hi to all, I have updated the content of my article in first post. Due to the fact that some of you had problems when running ProxHTTPSProxy or HTTPSProxy in older systems I have examined the correlation of crashes with the SSE2 capability of a CPU. The current results can be found in sections Prerequisites and Versions. Furthermore both versions of Root Certificate Updater have been updated and are now of 02/24/2022. Regards, AstroSkipper

In your linked post the solution was to check if Microsoft Client Network is properly installed.

Due to the fact that some of you had problems when running ProxHTTPSProxy or HTTPSProxy in older systems I have examined the correlation of crashes with the SSE2 capability of a CPU. The current results can be found in sections Prerequisites and Versions of this post: @maile3241 I have mentioned your findings relating to getting access to MU in Windows XP Professional x64 and linked your post.

Of course, I have. Forget about Windows 2000! As you already wrote in a post above: And you are absolutely right. But for all not reasonable people there is an antivirus tool which works with Windows 2000 too, called ClamWin. Here is a link: https://clamwin.com/ PS: By the way I don't think you have an infection in your system.

This thread is about Root Certificates and Revoked Certificates for Windows XP. You can update your Root Certificates automatically by using the Certificate Updater 1.6 or manually by using the Root Certificate and Revoked Certificate Updater of 02/24/2022 created by me in section Downloads It works perfectly and is intended to keep your system as recent as possible regarding your Root Certificates. Kind regards, AstroSkipper

@WULover This thread is a support thread about Microsoft Update (MU) or Windows Update (WU). So we have reached a point where everything regarding hardware extensions is unfortunately off-topic. If you have further questions relating to your hardware, you must open your own thread with a topic of your choice. Here we can only discuss problems accessing MU. I hope I could help you and if so, I would be pleased about any reactions. Kind regards

Now do this once again: And what is about your time server?

Newer browsers do not need HTTPSProxy or ProxhttpsProxy. I use these tools only for accessing web sites using IE or IE engine. Some programs use IE looking for updates or providing other services. Same for email clients. Most of the time HTTPSProxy is disabled in my system.

Of course but I don't trust such features anyway and in case of Malwarebytes Premium for Windows 3.5.1.2522 even more. Your log looks fine until warning and error code 0x801901f6 appears, a cold comfort unfortunately. Please check if my provided config.ini is used and check Trusted Zone if only the three provided urls related to Microsoft exist. Check your Internet Zone too, maybe lower restrictions i.e. lower security level.

Yet again , I think I wrote that offsets may change (depending on the version) . Here you go , take a look at the "patched" russian popular version 12.0.1012.0. And it makes it's connections each time you restart the browser. I don't know how often , because I don't use it . Yet again , the russian patch doesn't touch child_dll and the "exe" file, but they contain telemetry too. About pale moon and other firefox forks and firefox itself , a word of warning , I've read it sold it's soul to the KGB (Yandex). Of course, you don't have to trust me and check for yourself , https://lockshot.wordpress.com/2008/10/15/exploring-partnership-with-yandex/ .

1 - Why such blind trust in Russians ? Chinese telemetry removed , russian added , why not ? xD . You may as well install Antivirus software from KGB officer Kaspersky , just search for "Kaspersky , KGB" , you'll get plenty of results ... Have you ever checked the file yourself ? I've just opened it and I see they have LEFT a ton of Chinese telemetry , and it is NOT enough just to patch the chrome.dll . The executable and child are needed to be patched too ! Offsets may differ , due to the various versions . This one is from 12 , but 13 has them too (even "patched" by the russians) AT OFFSET chrome.dll 2B934B5 DNS resolver (chinese IP 101.226.4.6 ) AT OFFSET chrome_child.dll 3C0280D DNS resolver (chinese IP 101.226.4.6 ) 2 - Regarding RAM , just use this flag --process-per-site . It will reduce the usage of RAM and each site will run in one process. P.S. It's kind of one the first rules of internet , do not trust anyone.

Yes , some custom dark theme , since the original dark theme has been removed from MSFN.

It's strange why some members do not have their flag shown at all , this one , for example . I think it's unfair . My flag is shown , even though I removed the country information before this new "feature". Why this member's flag is not shown ?

Hi , first off , I'm sorry to remind : this top is : Share your Windows >Vista< experience! and not about "the look of 7". There's too much to write about the differencies . Some of the ugliest things about Win 7 are : fonts (yes that "true" type ones) - washed out and blurry , oversaturated UI colours , like for ravers at the acid party. I always had the best monitors available , so I can tell. Also , sound , oh boy. It's nowhere near Vista's punchy and sharp audio quality . I have Asus D2 , so I can also tell the difference . Win 7 has fat , thick , flat , ugly taskbar . etc , etc , etc . P.S. Compare Vista's wonderful orb and Win 7 (I don't even know how to name that "acid something").

I suspect that it is for creating registry entries with "HD" capable device strings under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\{my receiver auto generated id}\Properties] This one is interesting too , notice different "oem" for win7 and Vista. oem9.inf:NVIDIA.NTamd64.6.0:NVHDA64V:1.3.34.3:hdaudio\func_01&ven_10de&dev_0044 oem3.inf:NVIDIA.NTamd64.6.1:NVHDA64V:1.3.34.3:hdaudio\\func_01&ven_10de&dev_0044 If drivers gets 6.1 or anything higher , it will create those missing and/or different entries I was talking about earlier . They are auto generated and couldn't be added manually to stay forever , they will get erased and replaced with the non-HD strings. Nvidia forbids HD audio on Vista , even if you have HD capable device. By the way , this "issue" could be a lawsuit since Nvidia claims GTX780 full support on Vista , including HD audio. How to put it polite - customer misleading. In the meantime, I use that Chinese player with that pleasant "glitch", now I know how to replicate the glitch . It's not the best solution , I hope to get a fully working driver.

Opera 72 with these latest files "SHAssocEnumHandlersForProtocolByApplication not found in SHELL32.dll".

It's from 2013 or so . Acer Aspire E5-731-P3ZW (EU) - 17.3" - Nvidia 830m (V1), Intel Pentium 3556U , 8 GB DDR3L 1600Mhz (only in European model) , 1TB HDD . It's a rare EU version with Nvidia GPU , it's hard to find any info on that model . Almost all websites show that it doesn't have a discrete GPU , but mine has .

I have a laptop with the dreaded optimus and don't know how to disable it via bios edit. The thing is , it has a fully supported (by Vista) Nvidia GPU and that "famous" dreaded Intel which has no drivers (Haswell). I had tried drivers for XP , but they BSOD , even with XP installed.