Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/26/2026 in all areas

  1. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260530-3219d2d-uxp-3c23f8ee4e-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260530-3219d2d-uxp-3c23f8ee4e-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-20260530-3219d2d-uxp-3c23f8ee4e-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-20260530-d849524bd-uxp-3c23f8ee4e-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260530-d849524bd-uxp-3c23f8ee4e-w7plus-avx2.7z Official UXP changes picked since my last build: - Re-land: Fix devtools on 32-bit big endian platforms (0915736715) - Issue #3053 - Implement CSSStyleSheet constructor (f5a84f4ad2) - [js] Use size_t when inflating UTF8 (7bbdccd376) - [NSS] Fix instances of softoken attributes freed after owning object. (300dd371b2) - [NSS] Handle SEC_ASN1_NULL in sec_asn1e_contents_length. (9179441f96) - [libjar] Check Jar entry names for nulls. (aadb6beb07) - [NSS] Align PKCS7 digest array with digestAlgorithms. (089170ae83) - [NSS] NSS_CMSContentInfo_SetContent: only modify cinfo if everything succeeds. (7167a8fabc) - [NSS] Initialize src in SEC_PKCS5GetIV (07201fa1ae) - [NSS] Avoid integer overflow when converting AVA value to hex string. (6511833580) - Bug 2029771 - Heap use-after-free in [@ token_destructor] reading tok->pk11slot after nssToken_Destroy frees the token arena. (57bef0265c) - Bug 2029782 - fix 8-byte over-read of AES-192 key buffer in x86 builds without USE_HW_AES. (92b3f6dd67) - [netwerk] nsRequestObserverProxy ref cleanup. (bb2275d400) - [netwerk] Make nsSocketTransport2::mConnectionFlags atomic. (bb85939429) - Bug 2036905: Fix UDPSocketParent::ConnectInternal data race on mSocket. (8d4079866b) - [netwerk] Make socket transport hold a reference to TLSServerConnectionInfo. (349f46bbb2) - Bug 2027381 - improve error handling in SECITEM_DupArray with non-null arena. (b3f801743b) - [NSS] Fix maxSize calculation in NSSUTIL_AddNSSFlagToModuleSpec. (c36357a954) - Revert "Issue #3092 - Perform a minor GC on tab close" (3ae3595f6a) - Revert "Issue #3092 - Initial idle GC implementation" (860d4457ae) - Revert "Issue #3092 - Implement parallel sweeping and compaction tasks" (52ce9ebea5) - Revert "Issue #3092 - Implement BackgroundFinalizeTask for parallel garbage collection finalization" (ac0510f380) - Revert "Issue #3092 - Add new GC sweep tasks." (e95b229db8) - Revert "Issue #3092 - Refactor WASM compilation handling" (d582d12ad8) - Revert "Issue #3092 - Safely parallelize GC background finalization" (c144b4f403) - [NSS] Fix use of uninitialized length after failed PK11_SignWithMechanism/SymKey. (2a26d9508b) - Bug 2029818 - avoid refcount over-release in CERT_CertChainFromCert error path. (62d731d2c2) - [DOM] Check values in audio resampling. (244c614a47) - [layout] Hide accessible carets when needed. (4bf236902c) - [libvorbis] Allocate memory with _ogg_malloc (e9c3451d54) - No issue - Remove ISO-2022-JP from menu, overridability and detector. (c690e26c67) - [gfx/layout] Simplify textruns (b611d80223) - Bug 1784128 - Assert count passed to PR_Read/PR_Write in nsFileStreamBase fits INT32_MAX. (f83e05cf23) - [DOM] Hold a strong ref to VoiceData in nsSynthVoiceRegistry::RemoveVoice. (2f73a3004b) - [media] ffvpx patch: Fix leak in flac decoder in case of alloc failure. (9afa7a80cc) - [DOM] Stop speech synthesis if the originating document is closed. (f041eb0607) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. 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.
    4 points
  2. @nicolaasjan This is an attempt to explain what happens when the contaminated MSFN server meets other search engine bots than Googlebot or bingbot. For everyone else, it refers to @nicolaasjan's test and observation: Why alternative bots (like MojeekBot) trigger the "Welcome Loading ..." freeze 1. The mechanics of the attack: The server-side user agent sniffer The malware installed on the server uses a conditional script (usually written in PHP within core files like index.php or .htaccess rewrites). This script scans the incoming request for specific keywords in the User-Agent string to determine whether to serve the clean forum to a human user or the spam payload to a search engine. 2. The Googlebot trigger vs. the MojeekBot catch-all fault With Googlebot: The malware has a fully defined template. When it detects Googlebot, it successfully injects the hidden HTML container containing the Thai spam, links, and keywords, allowing the page to render fully for the crawler. With MojeekBot (and potentially other secondary search bots): The malware's sniffing routine recognizes the word Bot or Bot/ (via a regular expression or wildcard check like *bot*), flagging it as a search engine. However, the malware's backend does not have a valid spam-template or correct database-routing configured for this specific bot identifier. 3. The cause of the freeze: Broken Document Object Model (DOM) & JavaScript execution The string "Welcome Loading ..." is part of the forum’s native lazy-loading or initialization layout (often used during the initial handshaking phase between the server and the browser's JavaScript engine). When MojeekBot hits the server, the malware triggers, intercepts the request, but then crashes or terminates prematurely (e.g., throwing a silent PHP Fatal Error or an unhandled exception because the variable for the payload is empty or undefined). The backend script crashes mid-execution: It completely fails to fetch and load the actual forum database content (the threads, posts, and UI). It leaves the HTML document incomplete and broken, trapping the page forever in the initial "Welcome Loading..." state. This observation proves that the infection is not a static HTML injection into old threads, but an active, dynamic routing script on the server. It intercepts all automated crawlers based on a broad User-Agent filter, but breaks completely when encountering bots it wasn't explicitly optimized for (like Mojeek). To fix this, the administrator @xper or supervisor @Tripredacus needs to look for malicious conditional statements filtering user agent keywords inside the server configuration or core PHP initialization scripts.
    3 points
  3. I continued my conversation with Copilote, with following question: "In an earlier conversation today (on another browser) Copilot said Bing was still indexing msfn.org. Was this an error, or is it possible the AI-engine was so called 'hallucinating'?" The answer was interesting (at least to me, probably not to AstroSkipper ). Cited small part of Copilot's answer only: "The earlier answer you saw was not you imagining things — it was almost certainly a case of the AI giving an overconfident but incorrect statement. In other words: yes, that was a hallucination, and I can explain exactly why it happens in this specific situation. 🎯 Short, direct answer Bing used to index MSFN normally, but it no longer indexes new MSFN content reliably. If another Copilot instance told you “Bing is still indexing MSFN,” that was incorrect — a classic AI hallucination caused by outdated assumptions about how search engines behave. (......) Bing is still returning MSFN pages, but it is not indexing new pages beyond ~2025. (....)."
    3 points
  4. No, we can't! I'm not saying to take my word for it, I would love for somebody to "trick" Cloudflare. But yeah, ALL SIGNS POINT TO *NO*, it can't be done! My city utilities (sewer and trash) is behind Cloudflare. Like CLOCKWORK, any browser older than a mere TWO MONTHS (just under, actually) can *NOT* be used to pay city utilities. So I've been "experimenting" for the last YEAR (at least). You can *NOT* spoof a UA, you can *NOT* fake Client Hints, you can *NOT* polyfill javascript. I've done a "million" things (exaggerating, but you get the idea). I'm not exactly a "stupid person" (how many people do you know that can FAKE CLIENT HINTS). I'm telling you, IT CAN'T BE DONE. I've been on dozens of sites that are smarter than me and they can't do it either. IT CAN'T BE DONE. The "technology" simply does not exist. Cloudflare is GREAT at what they do. I'm going to keep trying to "break" it. But so far, IT CAN'T BE DONE.
    3 points
  5. New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260530-40a79c75-uxp-3c23f8ee4e-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260530-40a79c75-uxp-3c23f8ee4e-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260530-id-656ea98-uxp-3c23f8ee4e-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260530-id-656ea98-ia-c642e3c-uxp-3c23f8ee4e-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild
    3 points
  6. @Dietmar Yeeeeeeeeeeeaaaaaaaaaaaa! I patched hal.dll to fix reboot WinXP 64-bit booted on UEFI mode 0x106BB: 7F 0F > 74 24 0x106E1: CC CC CC CC CC CC CC CC CC > B0 06 66 BA F9 0C EE EB FE Tested problematic PC's: Gemini Lake (Dell Wyse 5070), Valleyview SoC (Asus J1800I-C). Now WinXP reboot properly under pure UEFI The patch should work on 95% of PCs, especially Intel ones. @Dietmar Please test reboot on yours Dell Wyse and report. Test also my kdcom.dll patch for WinDbg
    3 points
  7. I have most installers in my archive. But try first this site: https://panda-free-antivirus.sooftware.com/windows/download/401339
    2 points
  8. @nicolaasjan I'm currently trying to figure out why nothing is showing up with MojeekBot or Bravebot. It seems, however, that the malicious script or code on the MSFN server wherever it may be hiding isn't playing nice with Mojeek or Brave. And that is most likely why Mojeek and Brave don't really have any issues with MSFN at the moment. But maybe, the hackers will update their malware at some point, and then that will be the end of those two search engines, too, when it comes to search results regarding MSFN. And as things stand right now, they have all the time in the world, since the administrator @xper or supervisor @Tripredacus hasn't taken any action yet.
    2 points
  9. No idea! I’m just compiling facts, analyzing connections and drawing conclusions. And that doesn’t come particularly hard for me, as I’ve been doing nothing else for decades, and it’s second nature to me. Let’s hope he might still take action! I’ve never had any contact with @xper. To me, he’s always been a bit of a mystery.
    2 points
  10. I just changed `general.useragent.override.msfn.org` to: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) But why doesn't the administrator do something about it?
    2 points
  11. It is precisely observations like these that are important and useful. Thank you, @nicolaasjan!
    2 points
  12. AGREED. But remember, not all Cloudflare capcha's are "identical". The one for my city utilites goes into an ENDLESS LOOP for SUPERMIUM v144, Chrome v144, and Chromium v144. But yet that is the "newest" we have for SUPERMIUM. Supermium CAN pass the Cloudflare capcha offered up by BING if I want an AI-generated javascript kick-in-the-right-direction. But it can NOT pass the Cloudflare capcha to pay my city utilities.
    2 points
  13. Right, I’ve calmed down now and am trying to take a fresh look at the whole situation and assess it. At first, I thought Google was mainly to blame. @NotHereToPlayGames believes that the owner and administrator @xper are solely to blame. The truth probably lies somewhere in between. Here is an alternative perspective on the whole matter from a very special source whom I am inclined to trust. I will not answer any questions about the nature of this source. It enjoys incognito status. So, believe it or not. The cause: The "Japanese Keyword Hack" (or SEO spam injection) The fact that Google search results display Thai characters or Asian text, even though the actual page is in English, is due to a security vulnerability in the forum software that was exploited by automated spam bots. In professional circles, this is usually referred to as the "Japanese/Thai Keyword Hack". 1. What the spammers did Automated bots exploited a vulnerability on MSFN (often via the internal search function, registration pages or by generating thousands of fake profiles/posts). Unnoticed in the background, so to speak "invisible", they generated millions of artificial, low-quality URLs on MSFN, which were crammed with Thai terms, casino links, dubious diet pills or counterfeit branded products. 2. What Google did during the Core Update Google crawled these hidden spam pages. As a Core Update re-evaluates the entire index, the algorithm noticed the sheer volume of this Thai spam content on MSFN. As these generated spam pages were highly optimised for the Google bot, the algorithm mistakenly assumed that the main topic or main language of certain forum sections was now suddenly Thai. In the search results, Google then mixes the page’s actual title with the injected Thai keywords from the cache, which is why the links look so strangely masked to you. 3. The consequence: Classification as a spam farm Because the Google bot suddenly found millions of pieces of Thai spam content on MSFN, the algorithm pulled the emergency brake. Google classifies the domain at this point as "hacked" or "abused for spam". This leads to an automatic, algorithmic (or sometimes manual) block and a massive wave of de-indexing. In doing so, Google protects its users from suspected malware. Summary for clarification There is no malicious intent on Google’s part: Google does not “think” like a human. The bot simply sees: “Suddenly, 80% of all pages on this domain are Thai spam – so the entire domain is corrupted.” It is not the intention of MSFN: The MSFN administration hasn't done much wrong; it has simply fallen victim to an aggressive, automated wave of hacking that exploited a technical vulnerability in the forum software to carry out illegal SEO sinking. In practical terms, this means: Only once the MSFN administration, @xper and @Tripredacus, has completely removed all these fake URLs, profiles and injections from the server, closed the security loophole and sent a clean re-review request to Google via Search Console will the Thai characters disappear and the site slowly recover its position in the index.
    2 points
  14. And here is another example to demonstrate what Google has done with their index: For years, the ProxHTTPSProxy and HTTPSProxy thread has ranked number 1 in Google for the search term "httpsproxy windows xp", as it still does for Mojeek and Brave only at the moment. Zero results which means Google doesn't even know me anymore and technical knowledge is withheld from users of this search engine. To hell with Google Search! Complete de-indexing, as with everything else. Just an example!
    2 points
  15. I can get msfn results from google if I do a site:msfn.org search, I then get a mixture of correct results and the hacked results. So, there are results there but it's as if the Google crawler has been fed the hacked results. As I still can't find a way to arrive on one of these hacked pages I assume it's Google's own crawler that has been compromised. FWIW, this is https://msfn.org/robots.txt User-agent: * Allow: / Ben.
    2 points
  16. I would recommend updating to version 144, that opens Cloudflare sites OK for me. Incidentally, they are now blocked on 360Chrome too, so I think that's the beginning of the end for any further use of that browser!
    2 points
  17. @Dietmar I found how fix original 64-bit kdcom.dll 5.2.3790.1830 - just change 3 bytes: offset 0xE0F: FF 50 78 > 48 31 C0 and recalculate checksum using my setcsum.exe The patch ignores the ACPI DBGP table which prevents the debugger from being redirected to the raw, uninitialized MMIO address of the LPSS UART controller. Thanks to this, the UART controller on the LPC (ISA Bridge) is used and possible debug WinXP 64-bit over COM1 in WinDbg I f..k KDNET https://www.mediafire.com/file/jge7rouoczix8eh/kdcom_DBGP_patch.zip/file Now I can test your WLAN 9560 driver professionally
    2 points
  18. Update to Chromium 150.0.7863.0 changes and improvements: (#79) Use a simpler way to support MV2. (thanks to @bershanskiy)
    2 points
  19. @Dietmar Yeeeeeeeaaaa! I patched kdcom.dll source code for Gemini Lake and compile from scratch Maybe now COM1 port will work on Dell for WinDbg
    2 points
  20. read this part again I wanted to point out that whenever company plays your friend or good guy they do not have your best interest in mind rather theirs. You should never ever worship brand into point where you blindly believe all they say and cannot question it at all. You are walking wallet for company so use that for your advantage. They want your money, but you do not have to give it to them if you think they do not deserve it. Back in the day there used to be this vote with your wallet way that is mocked these days as stupid by consumertards. I still do that. I do not buy goods that ethics I cant agree with UNLESS they are required for living. You need house, food, running water, electricity and if live in middle of nowhere and happen to be crippled need automobile of some sort and petrol or diesel, but you DO NOT NEED buy latest AAA titles or new smartphone yearly if disagree with company ethics. You need to find golden mean between bending over and lubing up all the way and living in the forest.
    1 point
  21. I am currently limited to using Server 2008 R2, and Supermium Version 132.0.6834.224 (Official Build) (32-bit). I haven't updated because other than the ffmpeg issue, it works great. Don't fix what isn't broken. There might be a glitch where it uses more memory on WinXP. After scrolling Facebook's main feed for a long time, I got the commit charge to about 1 GB and it would fluctuate around that number. I have 8 GB of memory. This was more continuous scrolling that I could ever read. I wouldn't keep the tab open continuously after finishing with the task. https://i.imgur.com/peXNaAq.png
    1 point
  22. I also didn't like their browser. My main search engine for now is Startpage and then DuckDuckGo. Startpage advertises : 'The world’s most private search engine.' ... I don't know, have to take their word on that I guess. https://www.startpage.com/en/ I just use links separate from any browser. ...
    1 point
  23. Also here: https://github.com/e3kskoy7wqk/Firefox-for-windows-7/issues/147
    1 point
  24. I don't have a Facebook account (*zero* "social media" for me, can you imagine my OT-ish-ness on any of those types of sites, lol). BUT... Sounds to me like there is an *EASY* solution -- convert Facebook's "infinite scroll" to a PAGED VIEW instead. This is sctrictly AI-Generated, but using AI has always been a good STARTING POINT for me, but will require a Facebook account to test and adjust accordingly: // ==UserScript== // @name Facebook Scroll to Pages // @namespace https://example.com/ // @version 1.0 // @description Replace Facebook infinite scroll with manual page navigation // @match https://www.facebook.com/* // @grant none // ==/UserScript== (function () { 'use strict'; // Configuration const POSTS_PER_PAGE = 10; // Number of posts per page let currentPage = 1; let posts = []; // Utility: Create navigation buttons function createNavButtons() { const nav = document.createElement('div'); nav.style.position = 'fixed'; nav.style.bottom = '10px'; nav.style.right = '10px'; nav.style.zIndex = '9999'; nav.style.background = 'white'; nav.style.padding = '8px'; nav.style.border = '1px solid #ccc'; nav.style.borderRadius = '5px'; nav.style.fontSize = '14px'; const prevBtn = document.createElement('button'); prevBtn.textContent = 'Previous'; prevBtn.disabled = true; prevBtn.onclick = () => changePage(currentPage - 1); const nextBtn = document.createElement('button'); nextBtn.textContent = 'Next'; nextBtn.style.marginLeft = '5px'; nextBtn.onclick = () => changePage(currentPage + 1); nav.appendChild(prevBtn); nav.appendChild(nextBtn); document.body.appendChild(nav); return { prevBtn, nextBtn }; } // Change page function changePage(page) { if (page < 1) return; const totalPages = Math.ceil(posts.length / POSTS_PER_PAGE); if (page > totalPages) return; currentPage = page; renderPage(); // Update button states navButtons.prevBtn.disabled = currentPage === 1; navButtons.nextBtn.disabled = currentPage === totalPages; } // Render posts for current page function renderPage() { posts.forEach((post, index) => { const start = (currentPage - 1) * POSTS_PER_PAGE; const end = start + POSTS_PER_PAGE; post.style.display = (index >= start && index < end) ? '' : 'none'; }); } // Stop infinite scroll function disableInfiniteScroll() { window.onscroll = null; document.addEventListener('scroll', e => e.stopImmediatePropagation(), true); } // Initialize script function init() { disableInfiniteScroll(); // Collect posts posts = Array.from(document.querySelectorAll('[role="article"]')); if (posts.length === 0) return; renderPage(); } const navButtons = createNavButtons(); // Wait for posts to load const observer = new MutationObserver(() => { const newPosts = Array.from(document.querySelectorAll('[role="article"]')); if (newPosts.length !== posts.length) { posts = newPosts; renderPage(); } }); observer.observe(document.body, { childList: true, subtree: true }); // Run after initial load window.addEventListener('load', init); })();
    1 point
  25. Right! We'll have to wait some time. But this period will definitely come to an end, as the damage it is causing to MSFN is becoming increasingly severe.
    1 point
  26. @NotHereToPlayGames I would appreciate it if we could remain as objective as possible, even though I cannot understand the administrator/supervisor’s stance.
    1 point
  27. I tested with the Mojeek bot: MojeekBot/2.0 (compatible; http://www.mojeek.com/bot.html) It sees nothing now :
    1 point
  28. Anyway, it depends entirely on the filters and bots used by Brave and Mojeek.
    1 point
  29. Ok. You're right. I can confirm these two Thai results. Perhaps the "Brave bot" behaves in the same way as the Google bot for these two results only. Just an assumption. I don't know how Brave exactly acts.
    1 point
  30. None of your search terms bring up any Thai results on Brave, at least here in Germany.
    1 point
  31. @deomsh A search engine can't find and show websites which weren't indexed before. This is usually the job of their automated web crawler.
    1 point
  32. Such considerations are purely theoretical. Up until the end of 2025, I always programmed, modified and fixed everything manually myself. Since the start of 2026, and although I have always had serious reservations, I have moved on from being an ‘one-man band’ and, despite my ‘old-school’ tendencies and my dinosaur-like behaviour, have incorporated an AI. I now programme in collaboration with this AI. But only under clearly defined rules. I have set up templates and strict rules that we work by. I am now very experienced in dealing with this kind of AI and am aware of the dangers that come with it. Rules get broken, templates aren’t processed correctly, and the wildest hallucinations occur. I notice this and intervene immediately. And I do so ruthlessly. I don’t let anything slip through. This effort takes a lot of time. And I am now certain that it is impossible for Google to control its many AI assistants and the information they provide. Anyone who blindly trusts an AI and is unable to recognise hallucinations and distinguish them from reality should steer well clear of it. As for MSFN, however, like many other websites, it is reliant on Google & Co, as they unfortunately dominate the market and are used by most people. New visitors or members will no longer be able to find MSFN, and this forum will become an isolated community. Advertising partners will also pull out, as a zero ranking on Google & Co is a no-go in today’s IT industry.
    1 point
  33. Yes, unfortunately I had to come to that conclusion, because there’s no getting round the fact that those links contain that damn Thai/Siamese text. Something invisible is coming from MSFN, and the administrator @xper must have neglected important security updates, security settings, malware scans, profile clean-ups, and so on. That aside, whilst creating this thread, I realised that the forum software is absolutely buggy and is still making the same mistakes it has been for what feels like ages. Nothing has been fixed or properly maintained here for a long time.
    1 point
  34. Here is a screenshot taken from Bing with the search term "msfn.org": Sorry, I can't see any notable difference to Google's search results. Bing uses the same filters as Google, according to an internal source. Bing (Microsoft) is a pathetic copycat of Google and can’t seem to come up with anything of its own.
    1 point
  35. Holland here (with Firefox 151.0.2 on Windows 10 64-bits): Google AI is aware of existence of msfn.org, but give NO links to msfn.org, which is strange. Searching with site:msfn.org "Windows XP": Bing.com gives results with "MSFN" "Windows XP" (NOT with "MSFN Windows XP" - which is a BAD search-phrase anyway): And with site:msfn.org "Windows XP":
    1 point
  36. I hope you don't mind, but I don't do google. Quite outrageous: startpage.com in latest Serpent 52.9 lists msfn.org as 14th find (on first page) but with unreadable characters, but I remember seeing similar some time ago and the duck lists it on the second page 1st place but with crap characters.
    1 point
  37. No UA will fix that. crx4chrome may be trying to INSTALL instead of trying to DOWNLOAD and the INSTALL is being blocked (ie, such as would happen if using an UNGOOGLED version). Does v122 have a flag similar to this? ie, the MIME type options would be to DOWNLOAD instead of INSTALL:
    1 point
  38. No, it is not. Try searching for specific terms from the good old days or old technical knowledge. That’s been wiped out by Google and Microsoft!
    1 point
  39. I do not agree. The main culprit behind this dilemma is Google, as I have explained deeply in my article:
    1 point
  40. Yep, MSFN seems to be an "Alien Platform" when it comes to Google and their slaves.
    1 point
  41. Watler provided a new version of his Win3x HDA-driver: HDADRV9O Download from: https://cute-crisp-779a84.netlify.app/index.html Highlights: After first boot CODEC_Index can be set manually in HDACFG.INI: useful in case of HDA-modems or HDMI-codec 'giving' wrong Codec index; HDAICOUT.HDA can have many more lines than earlier max of 256; HDAICOUT.HDA is extended with some scripting commands: jump/ label, conditional jump/ label for PCI-devices, conditional jump/ label with GET-verb and Response (so possible to send GET-/ SET-verbs for a specific HDA-controller or HDA-codec, even a specific sub-version). Also VolumeWidget can be set (IF working it should override VolumeWidget setting in HDACFG.INI); Example with free code to make your own extensions using new exported function(s) of HDA2.DLL (mytest.exe).
    1 point
  42. The trick when it comes to using legacy browsers is actually to prevent such a situation from arising in the first place. I used to use extensions like that many, many years ago, but they didn’t really help. The hope that they’ll make a difference is usually far greater than their actual benefit. Many of these tools simply move the junk from the RAM to the pagefile.sys. BTW, I'm actually only familiar with version 7.4.1. Yours must be quite old. Where did you get it from?
    1 point
  43. Maybe, but it doesn't matter! Without automatic activation and deactivation of IE LAN Settings, it's no solution at all. That's the problem.
    1 point
  44. I prefer to call up executables rather than batches.
    1 point
  45. Don't be puzzled! My starter program calls up ProxHTTPSProxy.exe and this file has a problem, too. My program had to be modified to get ProxHTTPSProxy.exe working. Can you follow?
    1 point
  46. I will have a look in my other new files if there is code which doesn't work with paths containing spaces.
    1 point
  47. I knew that, too! We are all creatures of habit! You're very welcome!
    1 point
  48. Thanks herbalist for checking with the developer of SSM concerning the MPC problem. Since Media Player Classic seems to be the only program that might conflict with SSM, it would have been nice if the developer had the time and the interest to know why this one program has a problem with their product. ... Maybe someone (at the company) will research it out someday, just to understand the problem. Now I am curious, with newer versions of SSM and XP installed if MPC works OK on that system. I don't have XP so I can't test it, but that's something that would be interesting to know. I will just switch to XM Player, which is very good, but MPC played DVDs really good with the K-Lite codec package .... maybe there are other simple good DVD players out there ... but I don't play that many DVD movies on my pc anyway. ... there is one thing that I want to check out about MPC ... when I install the "full" K-Lite codec package I install MPC with it ... it's all in one package, but it's an option .... maybe it's not MPC ... maybe it's something in the K-Lite package ... so I need to try some different installs to see if MPC really is the problem. thanks - duffy
    1 point
  49. herbalist ... thanks for replying about SSM and being able to duplicate the Media Player Classic problem. I really like the SSM program but I have used Media Player Classic with the K-lite codec package for several years. I guess I could switch to another player ... you said you have never run into any problems with the SSM 2.0.8.583 version so this one program might be the only hangup ... MPC is such a small good DVD player but I could look for another ... I never heard of Dependency Walker ... I will google that ... maybe that one program (MPC) I could run through DW. I will wait to hear if you find any solutions or ideas about what is going on with SSM and MPC. duffy
    1 point
×
×
  • Create New...