Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/23/2018 in all areas

  1. @Tamris The version of Audacity that was patched by @FranceBB to run on XP belongs to the alpha development channel, as such it is only available in the default en-US localization ; exact version is 2.3.1a-git-20181022-g72fbf1b (reported as Audacity 2.3.1-alpha-Oct 22 2018 in the app's GUI), the download link for the ZIP package - for those on Vista+ - is at: https://www.fosshub.com/Audacity-devel-old.html => https://www.fosshub.com/Audacity-devel.html?dwl=audacity-2.3.1-alpha-72fbf1b.zip So there's no way to change the GUI's locale via Edit => Preferences => Interface => Display => Language Only options there are System/English ... Luckily for you, there have been only minimal string changes between the release channel version 2.3.0 and the alpha channel pre-release (patched for XP compatibility), so what you can do is 1. Download the official ZIP package for release version 2.3.0: https://www.fosshub.com/Audacity.html?dwl=audacity-win-2.3.0.zip 2. Extract from it the Languages directory; at this stage, you can optionally remove locales you are never to use in the future... 3. Place the Languages directory inside the same root folder where (patched) Audacity.exe is located. 4. Launch the app and now the option to change to a different (to default English) GUI language should be present; select as desired... 5. Restart the app for full localization: 6. Enjoy... BTW/FYI, release channel version 2.3.1 is scheduled for Dec 28th, 2018...
    2 points
  2. That quote was from the browser.taokaizen.com (author of advanced Chrome for XP/Vista, etc.) forum admin. Guess they don't know about @roytam1's work
    2 points
  3. Jack Finley - Maybe you nailed it. I just rechecked properties for my NIC, and, in Power Management, two "Reduce link speed" settings were ON. I just UNchecked them. I always UNcheck the "Reduce link speed" boxes - I want my PC's NIC going full speed all the time. Maybe IProSetMonitor updated the driver and these settings went into a "reduce speed" default? ALSO, in Event Viewer - System, I have groupings of "Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0023AE71AAF4. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server." Thoughts? Anyway, thanks for suggestion. We'll see, Zoom zoom!
    1 point
  4. Download and manually install the version for Windows XP from the following link. The update KB2686509 differs to the Windows Embedded version! http://www.catalog.update.microsoft.com/Search.aspx?q=KB2686509 xp Note: When installing Windows XP first, the available and desired updates should be installed by WU / MU, only after that after several searches no more updates should be made to the POSReady key in the registry. Then the order and the correct update KB2686509 for Windows XP will be installed.
    1 point
  5. @Dibya The inconvenience I do not have, but the users who use this RAM patch. In actual life we all have to carry our "packages". I wish you a speedy recovery in your health.
    1 point
  6. Discord voice calls work on Yandex Browser (Chrome 57 engine, IIRC) without any modification.
    1 point
  7. Or create a cmd to run @heinoganda's MSE updater from the startup folder or as a scheduled task...
    1 point
  8. I don't think so either. Unless somebody demonstrates convincingly it contains any unredistributables, links to it should be OK.
    1 point
  9. So I guess users who do have the POSReady entry, and who now receive MSE updates automatically, will also need to make this change (and start updating MSE manually) after POSReady EOS next April.
    1 point
  10. @sal here Here is a helper where the entry in the registry changes (UPD_MMPC.bat) or back to the original entry (UPD_Default.bat). Download: here Password: n29TD$h"y9j5V23K6K§hb1%vA7vM9CrP&eU3BYzI4 Note: To unpack completely for execution Only of interest if no POSReady entry is used in the registry. The entry makes it possible (but only manually) to update the virus definition from the MSE interface.
    1 point
  11. ... I can confirm that the most current release (v7.6.1) continues to be Vista SP2 compatible: Notepad2-mod hasn't been updated in a long while; its github repo is marked as archived, last commit was pushed on Aug 15, 2017. So it is safe to assume that this project has become "abandonware", with the latest official release v4.2.25.998 becoming in essence the very last (final) one (still compatible with Windows XP SP3 + Vista SP2): As you say, NotePad3 does not officially support the Vista OS (and the new owners, Rizonesoft, also dropped WinXP support): However, the last stable release v4.18.512.992 apparently runs fine on Vista SP2: Most sadly, the rosey story ends up here ; during the autumn, the dev team moved on to a new compiler with revised compiler settings/kernel optimisations so that the new branch 5 released builds (currently in the Release Candidate dev stage) are not capable of being launched under Vista, due to missing API calls: So, version 4.18.512.992 should be marked as the last Vista compatible one ; obviously, the maintainers themselves have no intention of restoring Vista support to the app, but it is my gut belief - without, that is, browsing the code itself - that, again, we may have to deal with an artificial Vista block; the app is open source, so hopefully the code could be recompiled targeting again the Vista OS... Here's hoping...
    1 point
  12. New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20181222-ba81aaf07-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20181222-ba81aaf07-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20181222-ba81aaf07-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20181222-ba81aaf07-xpmod.7z Official repo changes since my last build: - Update NSPR to 4.20 (09ef48bd0) - Update NSS to 3.41 (74cabf794) - Clobber for NSPR+NSS update (c2478b9e1) - Update HSTS preload list (f0fe6b69d) - Issue #910 part 1. Don't navigate when location.protocol is set to anything other than http or https. (aa130641c) - Issue #910 part 2. Strip ':' and anything following it from the string passed to the location.protocol setter. (871c1d78c) - Issue #910 part 3. Throw SyntaxError from Location::SetProtocol on URI parse failures. (d0b9276f2) - Remove AndroidMediaDecoder and friends (ec2346967) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (8b017fb09) - Remove OMX related options from configure (ea6cc74f2) - Remove omx-plugin 3rd party libs (5104ad6ac) - Stop including a dummy dll on Windows for broken old versions of WebSense. (ff8b573a6) - Merge pull request #911 from trav90/code-cleanup (7457ca4ac) - Stub out FxA context menu functions. (6f3a1803c) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (680c3eadb) - Fix false positives in the preprocessor-checker (b7fac3839) - Make sure channel-prefs.js is packaged into MAR files. (d24869a15) - Update SQLite lib to 3.26.0 (aa771e77e) - Merge pull request #914 from JustOff/PR_preprocessor_fix (e91f221f2) - Return an empty set if getting recipes for host fails. (76c942b1d) - Replace status bar download overlay glow arrow with SVG. (ba81aaf07)
    1 point
  13. I hate MS for what they did to people like Roffen. Poor guy.
    1 point
  14. According to the ASUS website both of those motherboards support XP and have XP drivers available. Just google the motherboard model number and find your way to the support site for each model.
    1 point
  15. Beta channel for Adobe Flash Player updated to 32.0.0.105 on December 10 and confirmed working on Windows XP SP3. https://labs.adobe.com/downloads/flashplayer.html Chrome 45 and newer PPAPI: https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player_ppapi.exe Chrome 44 and older, and Mozilla Firefox (NPAPI): https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player.exe Internet Explorer: https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player_ax.exe Uninstaller: https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/uninstall_flash_player.exe
    1 point
  16. i don't really know. @Roffen might tell you since he asked
    1 point
  17. Fantastic! Thank you.
    1 point
  18. Can be installed using Microsoft Application Verifier x64. Now Open Application Verifier from all programs, click on File-> Add Application. Select and open the office setup.exe from the DVD. On the right Tests pane unselect Basics, Expend Compatibility list and select HighVersionLie. Now Right click on HighVersionLie and select Properties as shown below. Set the following values: Major Version: 6 Minor Version: 1 Build Number: 7600 Service Pack Major: 1 OK the Properties window, then click Save. Now install the Office 2010 Double Clicking on Setup.exe in DVD. Sorry for my english
    1 point
  19. They have realized they can only give this crap away..
    1 point
  20. It's all relative, but clearly rational thinking based on what makes sense technically has been replaced with thinking solely of trends and fashion. I see it as very simple: Bill Gates was a geek, and ultimately did things (that yes, were good for Microsoft business) that made good sense. By comparison, when he handed the reigns over to successor marketeers and "businessmen" things no longer needed to make sense at all (while still being good for Microsoft business). I think the transition to "openly predatory" has been fairly recent, with their previous state, ending around 2010, being more benign with a healthy dose of "don't quickly attribute to malice that which can be explained by incompetence." -Noel
    1 point
  21. The "free upgrade" license, which will IMO be worth every penny and not a penny more, is described by Microsoft as being valid for the life of the device. Note the implication of the wording here: "This is more than a one-time upgrade: once a Windows device is upgraded to Windows 10, we will continue to keep it current for the supported lifetime of the device – at no cost." Whether in practice you'll be able to reinstall Windows 10 on that same device should you need to do so down the line, is anyone's guess. My advice: Become VERY well educated before deciding that this "free upgrade" offer is worth taking. I have a suspicion you won't be allowed to go back! Note my statement above and do your own research how much other knowledgeable users feel it's worth. TRY Windows 10 yourself - for example in a virtual machine. Do NOT blindly believe this is the same Microsoft that had users' interests at heart when they built Windows 7 and earlier. They have turned openly predatory. -Noel
    1 point
  22. Sure , after having applied - one year later - Service Pack 1 it actually worked ..., perhaps slightly better with SP 2 and some say even better with Service Pack 3 Windows 7. But I have seen grown up men cry back in 2007, and what has been seen cannot be unseen. @dencorso The usual point of debate revolves around the fact that IF they were after you, they would have ALREADY got you. @all Maybe if you look at the half full glass , the great advantage with the upcoming Windows 10 is that it is very convenient, you need to do nothing to update, no need to download huge .iso's no need to read lengthy instructions, no need to waste a DVD to burn anything, no need to reboot, the good MS guys will deliver it (no matter if you want it or not) overnight, whenever it pleases them to do so, and you will be greeted one fine morning by the sweet voice of Cortana .... you will be transferred in the new world of computing at no cost and with no hassles (maybe).... Time for a new issue of the sci-fi magazine: jaclaz
    1 point
  23. I'm far from perfect, but that has nothing to do with Vista, which was a fine system when tweaked, augmented, and tuned up. -Noel
    1 point
  24. (emphasis mine) Though you feel confident in writing that, my point is that (unless you know something most folks don't) such a judgment is really not possible given what little we know - which is all being fed to us from the very same people we now eye with suspicion. When Microsoft's focus shifted from providing value to users in return for payment to providing ad-supported software for free, it was more than just a trivial observation. It actually is starting to affect us. I've been called paranoid, but let's not forget that they're obviously trying to deliver these Trojan horse updates couched in deceptive language. That's a fact so obvious it cannot be debated and it cannot be attributed to incompetence or language barriers or whatever. It ain't paranoia when there's actual evidence. "Political correctness" and "societal conformance" would have us accept this new level untrustworthy behavior as the "new normal", without speaking up and being labeled an extremist. But should we? Where does it lead? Never forget we are all akin to frogs in a pot of water. -Noel P.S., Jaclaz, I'm not being in any way critical of your judgment or what you wrote, specifically. But it helps to make my point that this is a bigger issue than mainstream public opinion is acknowledging.
    1 point
  25. You're smart enough to know that they could be slipping things into places that don't seem problematic. Or have you decompiled the code to see what the changes are? They've turned devious and predatory. Everything we know about them from past experience is out the window. Everything we think should be off limits isn't. -Noel
    1 point
  26. i always love in their video blogs when they mention "our Telemetry shows" which in other words is built in spyware & keylogger
    1 point
×
×
  • Create New...