Leaderboard

semi-OT: yeah, this is how Matt commits. https://github.com/binaryoutcast/binoc-central/commit/94ce5d681724aee1ecc6c2b0acfe3a15d771f583

... Then get yourself educated! ... and there's no need to "scream" with bold capitals In fact, you should care who that person is: He's the "right hand", so to speak - no insult intended to left-handed people , of Moonchild himself, an integral part of Moonchild Productions, the dev team behind the UXP platform and all the applications built on it: Pale Moon 28 [New Moon 28.x.xa1], Basilisk 52 [Serpent 52.9.0] and Matt A. Tobin's most recent offerings, Interlink [Mail News] and Borealis Navigator [BorealisXP]... Matt A. Tobin contributes a lot of code to the UXP repo, all this code will end up virtually unchanged inside @roytam1's XP/Vista compatible forks... He's infamous for harbouring a strong aversion to Windows XP (and Windows Vista) and being generally extremely hostile to fans/users of these OSes; and make no mistake: he'll go the extra mile to make sure his code is NOT compatible with said OSes, making Roy's hard work even harder ... So yes, the subject of "Matt Tobin" is sort of relevant to this thread... It seems my previous detailed reply to you has fallen onto deaf ears (or shut eyes, to be precise...); Roytam's task is not to rewrite the Pale Moon code committed by the Moonchild Productions team to accommodate a specific user's personal needs, he has only reverted those bits of code that prevent it from compiling and successfully running on XP+Vista OSes, period... Had you bothered to check my link to UPX PR #874, you would have noticed that Matt A. Tobin had nothing to do with the "tab-audio-indicator" code that you're implying and you feel strongly vexed about; this PR was submitted by @FranklinDM, another dev in their team... We haven't yet witnessed in this thread other NM28 users complaining about the issue affecting your setup(s), so, as of now, it appears to be only manifesting itself on your systems; worse yet, you haven't produced a list of system specifics and detailed reproduction steps so as to facilitate troubleshooting of your issue... Moonchild code targets "recent" Oses (Win7+) and "recent" hardware (e.g. SSE2+ capable CPU), so if your system is under-resourced it would not run NM28 properly... In closing, if "rebuild NM28 without the new feature" is what you actually want, then, again, I have provided the links for that: 1. Clone the UXP repo 2. Revert PR #874 commits 3. Apply latest UXP patch by Roytam1 4. Provided you have a suitable building environment set up (Win7SP1+ 64-bit with 12+GB RAM, Visual Studio 2015+,etc. ), build from modified source; I am certain that @roytam1 would be willing to guide you through, that is if his spare time permits him to... So, no more moaning on your side, please...

yeah there is a point. but why I posted it is that, that message will be in my next release notes, so I forespeak that I need to rewrite this message for my next BOC-uxp build's release notes (IF I can remember to do so)

Adobe Flash Player 32 Final has been released today: 32.0.0.101 (tested/working on Windows XP SP3 and XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.101/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.101/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.101/install_flash_player_ppapi.exe

On their website, they state that XP is supported, but when I downloaded it and tried to run it, I got the same message you got: Let's see who is to blame... Uhm... ADVAPI32.DLL which calls RegGetValueW. A function that retrieves the type and data for the specified registry value. LSTATUS RegGetValueW( HKEY hkey, LPCWSTR lpSubKey, LPCWSTR lpValue, DWORD dwFlags, LPDWORD pdwType, PVOID pvData, LPDWORD pcbData ); "hkey" is used to open registry keys, "lpSubKey" is the name of the registry key, "lpValue" is the name of the registry value, "dwFlags" is a flag to define the data type of the value (REG_DWORD, REG_BINARY, REG_QWORD ecc), "pdwType" is pointer to a variable that receives a code indicating the type of data stored in the specified value, "pvDat" is a pointer to a buffer that receives the value's data, "pcbData" is a pointer to a variable that specifies the size of the buffer pointed to by "pvData". According to MS documentation, the function is available on Windows Vista. And "abracadabra": mIRC 7.53 Windows XP: Link Cheers.

Try http://www.oldversion.com

Which is the actual logical impossibility. Everything in Windows 10 is intentionally made to make possible ONLY "visions" that conform (to a certain extent) on what the good MS guy's vision is, by making each and every "customization" a (greater or lesser) PITA or by silently reverting or blocking it at next update. And it is only natural that the people that don't have issues are much less vocal than people that have them, after all there is an unwritten and unsigned contract about the OS being able to just do whatever an OS is supposed to do. I mean, noone writes about (say) Ford telling how good it is that his/her new Fiesta engine started this morning, while you might find someone blaming the battery (or the alternator, or whatever) because the car did NOT start this morning. Cars are supposed/expected to start EVERY morning. jaclaz

I did a little doohickey, untested. Throw it in python directory. Edit: whoops, I f***ed up, redownload. Edit: third time is lucky. patch.zip

Holy win https://linustechtips.com/main/topic/1002853-windows-xp-pc-first-ram-slot-not-working/?tab=comments#comment-12031484 It got fixed

Hi folks! Python (multi-platform programming language) officially dropped its support for Windows XP. Python programs are slightly different compared to other programs, because they are not compiled when you download them: they are just scripts. When you click on them, they will look for Python "assemblies" in order to quickly compile the program during the runtime. (It's not 100% true, but that's an over-simplyfied explanation). So... since Python dropped its support for XP, this meant a big issue for Python programs 'cause the old "assemblies" can't compile 3.5 scripts; that's why Python 3.5 Runtime Redistributable - Windows XP is here for you. Please note that this is an unofficial Runtime Redistributable package. Extract it to "C" and rename it "Python35". The core and its dependencies have been compiled to run in Windows XP, but I have been able to test with a single program 'cause I don't have any other programs written for Python 3.5. You'll find the official Python website screen and the backported version below. Link

WMP 10 is like WMP 9 but better. WMP 11 is like WMP 12 (fewer details, more graphics). I have used both on Windows XP with no problems, it is basically a matter of preference. As for codecs the Shark007 ones are also good (I use them on Windows 8 but they can be used on Windows XP too as far as I remember).

MSFN-where people go to see the magic @FranceBB thank you.You made magic again

Offline Registry Editor: http://reboot.pro/files/file/313-offlinereg/ jaclaz

Stop nagging. It won't make things any faster, but does annoy.

He's just lucky that GitHub have not imposed a "profanity" filter - simple as that FWIW, anyone with a GitHub account can report @mattatobin for using objectionable language...

I have upgraded 3 laptops, 1 desktop and 4 VMs to 1809 build from the 1803 build. All have upgraded without problem.

C:\Temp\python-3.7.1>python Python 3.7.1 (v3.7.1:260ec2c36a, Oct 20 2018, 14:05:16) [MSC v.1915 32 bit (Intel)] on win32 >>> import socket >>> import _socket >>> ^Z C:\Temp\python-3.7.1>python get-pip.py Collecting pip Downloading https://files.pythonhosted.org/packages/c2/d7/90f34cb0d83a6c5631cf71dfe64cc1054598c843a92b400e55675cc2ac37 /pip-18.1-py2.py3-none-any.whl (1.3MB) 100% |████████████████████████████████| 1.3MB 728kB/s Collecting setuptools Downloading https://files.pythonhosted.org/packages/e7/16/da8cb8046149d50940c6110310983abb359bbb8cbc3539e6bef95c29428a /setuptools-40.6.2-py2.py3-none-any.whl (573kB) 100% |████████████████████████████████| 573kB 819kB/s Collecting wheel Downloading https://files.pythonhosted.org/packages/ff/47/1dfa4795e24fd6f93d5d58602dd716c3f101cfd5a77cd9acbe519b44a0a9 /wheel-0.32.3-py2.py3-none-any.whl Installing collected packages: pip, setuptools, wheel Successfully installed pip setuptools wheel Everything works perfectly! UPDATE: Just FYI - ws2_32.dll from Extended Kernel for XP (ExtendedXP) works great too.

Well I have discovered what appears to be an Electron-based application that still supports Windows Vista (and maybe even XP) - Megasync (a cloud storage desktop client from MEGA): If it is Electron based, it makes me wonder how they do it... perhaps they still use older Chromium 49 code? Or if it only supports Vista or later (I haven't tested XP), perhaps they've somehow ported the Win7 version to Vista? Makes me wonder... Also thanks to the recent Discord findings, I have clarified Discord Voice support under Vista as well: Hope my list continues to make the lives of those of us on Vista (and XP) a little easier! Thanks to everyone who has continued to contribute to the topic!

So called "Avast! MP#3player" thanks to its UI

Yes, this confused me for a while, especially when I was trying to find old Avast versions to test with! They did indeed go straight from version 12 to version 17, as they introduced a new system where the version number is the year of release. Version 12 was only in 2016, so it's not as old as it sounds relative to 17 and 18 (released in 2017 and 2018 of course). I'm using 12.3 now (not 12.4 as I mistakenly said earlier) and that is the last version that works reasonably well on my XP system, without slowing everything down horribly and/or filling the Windows logs with error messages. I think they introduced a new UI with version 17, and I strongly suspect this may be causing at least some of my present problems. I actually like the 12.3 UI better anyway!

Hmmm, the registry settings I had in mind are relevant to py.exe launcher, which is useful for managing multiple python versions rather than a portable package. https://www.python.org/dev/peps/pep-0514/ https://pastebin.com/Da2NYpTd How these work is that py.exe will launch appropiate python(w).exe according to registry settings and beginning of script. #!python2 #!python3 #!python3.4 #!python2.7 It's good to know when installing new python into place. Also another note is when installing on x64 system with x86 python, is changed reg path. [HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Python\PythonCore\...

2.8 beta , Centered task icons works on Windows default but does not work on 3rd party themes.

@Dclem It is good to hear you have your PC running as you like without troubles, but unfortunately your case is an exception, maybe IMAGEFOLIO 4.5 didn't make changes to Windows register when it was installed on your previous PC/OS, and it only expanded to its folder location on Programs directory during install, but that is not the case for almost all programs. alacran

What a joke reddit.com/r/firefox/ has become. Besides the usual quantum suckups where no criticism is tolerated for anyone who even hints at still using an older version there's an auto moderator that chimes in to spank the poster. They are scolded to immediately upgrade to a newer, safer, warmer version complete with Alice in Wonderland coloring books before the big bad security bogeyman gets ya. Apparently Mozilla thinks we're all a bunch of little children who need their constant hand holding to save us from ourselves. Not even Microsoft is that much of a nanny.

Hey dude , I got a snake from jungle ported for you . Take care of my pet python. python xp

Thanks for pointing that out! Fixed That's a darn shame... oh well, I never was too big a fan of Avast myself to be honest. I still run an older version of MSE along with the last major version of Malwarebytes for XP/Vista, both of which still receive definition updates which is what really matters (Avast will still receive definition updates on XP/Vista too ) Anyway, aside from Avast/AVG, I have found a couple of pieces of software that no longer support Windows Vista: 1. OBS Studio, a popular livestreaming software, no longer supports Windows Vista after 21.0.1 (released Jan. 2018), so this version has been added to the list: 2. Dolphin, a popular GameCube/Wii Console emulator, hasn't officially supported Windows Vista for quite some time. Despite this, the latest "Stable" release (5.0) along with new "Development" releases continued to work on Windows Vista until a certain point at which I cannot exactly pinpoint, since there are so many versions that have been released since the last time I tested Vista compatibility. For this reason, I have simply listed the last "Stable" version to work with Vista for now: Also, I have added a couple of new pieces of software that continue to support Vista to the "Video & Photo Editing Software" section (thanks to @i430VX for showing me these):