Leaderboard

Yes but not its API. Nobody uses vanilla XP, everybody use SP3 whose additional APIs were actually released not so long before Win7 came out. Most of the time the excuse is that XP is from 2001 and it's too old when actually the latest version of the APIs and calls is from about 2008 so not so terribly old as people think. I would agree with them if they meant vanilla XP only pre-SP1; in that case the OS would indeed be so old that it would be a pain to develop a program for it, but not SP3 as I consider it fairly modern.

Avast: yes of course it's disgusting, but don't they all sell our complete life profiles, long since?? Lying and selling people is the normal state today, being honest and human friendly has become an almost fiction like exception. Especially Google/FB/MS/etc. If I remember correctly, Google meanwhile is worth 1.000.000.000.000 dollars, that doesn't come from nothing. Or was it FB? No, guess Google... But not much difference anyway. Perhaps also Cloudflare, who knows?? Have read somewhere that half the global internet traffic is meanwhile traveling through their servers, and that they have full unencrypted access to everything, incl. passwords. What a goldmine... Which reminds me that Trump changed the US laws to allow all internet providers to sell their own customers data for money, to do what they want with them. And that he also changed the laws to allow them to filter access to websites for their customers. They get to see now what their providers want them to see. And of course, most definitely all Android Phones are just pure bugging devices, wiretaps, active 24h a day and 365 days per year. Whatever other functions the devices may have is merely the bait to lure the prey into using it. And it doesn't help to switch them off, considering their purpose they can happily switch themselves on again whenever they wish, and switch on the microphone to listen a bit, and take secretly photos and movies, to send home. All with the supposed "permission" of the owners of course (or they couldn't use them at all). The only reliable way to prevent secret remote access is to remove the battery. But of course, those little escapes must be prevented, people must by spied 100% of the time, therefore our bugging devices must not contain removable batteries anymore. And of course, it's also better to trash them frequently, after 1-2 years, to be replaced with newer devices with yet better spying technology. Not to forget more profit by selling lots more devices. There was that absolutely incredible report about a year ago, how a technical journalist used a man-in-the-middle device to catch all the data his Android phone was "phoning home", after a trip into the city with his phone in flightmode. Obviously, that doesn't help at all. As soon as he let it go online again, Google was sucking up all the accumulated full spy data it had just temporarily stored inside, during the flightmode. It had been clear since years that they spy on us every second, but the real amount was still breathtaking. Incredibly detailed, every step and movement, pre-analyzed by AI already, including when he "walked by foot" or "left the car" etc And almost all Android apps nowadays too, chock full with trackers, often up to 10 or more! Of course we all know about those torchlight apps, needing access to contacts and internet, but that's only the tip of the tip of the iceberg. As example just a little collection, of email apps: https://android.izzysoft.de/applists/category/named/network_emailapps It's not by coincidence that Google makes such a bitter war against all smartphone OWNERS who DARE to try and escape a bit the 100% spying and selling. Google has full control of Android and can do what it wants with it, and that includes forcing manufacturers to also do what Google wants. Like when a few years ago their hidden permission manager (AppOps) was discovered in the system, and companies like Huawai dared to make it visible to users, Google simply forced them to REMOVE it again. And when they finally did include a permission manager in stock Android, it was just a lie. They made sure at the same time that ALL apps then got full access to all networks, incl. mobile data and bluetooth etc., declaring this permission as completely "normal", not dangerous. And users could do nothing against it, that info was hidden from them. This makes perfect sense of course, the job of bugging devices is to spy as much as possible. And secretly, Google gave ALL apps even full access to all network logs, containing the full traffic data of all other apps too. Or also, at some point, continuing to make the permission system as useless and deceiving as possible, Google stopped showing users all permissions at installation time. From then on, they only got to see a few harmless permissions to confirm, but afterwards all apps could happily update themselves and pull lots more permissions, now without any notice anymore. Or, of course SDcards are evil, allowing users too easily to exchange lots of data with their home computers. How dare they trying to rob even a bit of their personal data from Google! That must not be allowed, they must be made to upload just about everything onto cloud servers first, if they want to exchange files with their own other devices. So, lets try to abolish SDcards, and lets declare them completely out of fashion. And many followed, but not all. Some manufacturers still allowed users to have an SD-slot. So Google had to find another solution. Why, quite simple: just make it impossible to write and read it, let's block it by firmware! If absolutely must be, allow to store photos and videos, but nothing else. Especially not cross-access, for example to open a text file with a free editor, or edit an image with a free editor etc. And most of all, bugging devices must of course make sure that their OWNER can't get any access to system files, for example daring to try and block some native trackers and trojans inside. So let's lock the phones OS down completely, out of factory. No chance for owners to get root access anymore, no chance to unlock bootloaders anymore, not even by experts knowing all tricks, and if they dare trying anyway, lets just destroy the whole phone. Yeah a few still allow unlocking, mostly by forcing people to create an account, and give them a working mail addy and your devices unique ID-numbers. But the trend is clear, step by step every year more stuff becomes blocked. And of course, Microsoft as well. Windows machines have long since become pure bugging devices too, with other functions being only the bait for the prey. Therefore the owners must be made completely rightless too. Quite easy, just make it impossible to block any updates, for example to Win10. Let's declare this a little essential "security update" to fool people. Or whatever, all the FORCED upates anywhere, of course in Desktop Chrome browser as well etc. The only people who are always BLOCKED now are the owners, blocked from getting full access to their own devices, while the spy companies with remote access can do whatever they want to them. And of course, nothing better as just control the whole money transfer, up to the last penny! Anonymous cash must be abolished by all means, since it helps escaping full 100% tracking, so it's all evil! Everyone must be made to pay only if recording his name, no exception. Of course, this process will take some time, and it's best introduced as sneakingly as possible. Step by step, a little new law here, another little law there, and with propaganda everywhere how great it is to pay everything everywhere only by card, so very simple, so very handy, so very safe. Have even read the European Union has given out advice papers to the governments how to best go about it, without the population becoming suspicious too early. Oh yeah, and of course: "smart" home devices everywhere and for everything, listening permanently. Even "smart" puppets, talking to little kids, recording all their little secrets at the other side of the world. Or in Germany incredible new laws that in the future all electricity meters must be "smart" too, reporting via internet every hour or so (?) which devices are switched on... quite a goldmine too for certain people. Of course, this is merely meant to "help the environment" and "save money", by analzying possible waste... And a bit back someone dared to go to court when his landlord insisted to place a fire warner in the middle of his living and sleeping rooms, at the ceiling, which is also forced by a new law - so far sounding harmless, but this very special device in this case included a microphone inside (can't remember if also a camera), and it will get remote controled from outside at any time! Plus RADAR included inside to make sure the poor renters cannot even dare to cover it, in at least 1m distance! Of course, the landlord claims the microphone were just fake, not functioning at all, and of course, that's also what the manufacturer claims. So, what did the judge say? Always expect the worse, and you'll always be right nowadays: He judged that this is perfectly okay! If the manufacturer claims the spying equipment wouldn't work, then it surely must be so. Period. Just very funny IMO that this supposedly fake stuff was so very important to the landlord, that he even fought at court to install it in his renters rooms. And the german version of NSA is permanently listening the whole traffic on "the worldwide biggest internet node", which seems against the law, which is supposedly oh so privacy friendly. Only under very strict conditions and in special circumstances the state is allowed to watch innocent people in masses, and not more as a 20% share. So the company who runs that giant node (DE-CIX) went to court in 2018, and guess what, the judge simply ignored it and declared it okay, and blocked also all possibilities for revision. https://www.notebookcheck.com/BND-darf-weiter-Internetknoten-anzapfen.306254.0.html While at occasions, where surveillance would actually help society, to catch criminals at known hot spots, it's strictly forbidden, phonily pretending "privacy" reasons. By the way even wildlife cameras deep in forests are forbidden too since awhile, a new law created around the time when wolfpacks were intruced again - of course also for "privacy reasons"! Only allowed now: position not higher as knee hight, not pointing towards any ways where possibly a human could walk by, NO automatic triggers to start filming, only one photo every 5 minutes etc. There's no end to all the spying and phoniness... Sorry, have read too many horror reports, it's just beyond bearable :-(

Hello, i managed to get installed XP on Z370 MB - https://www.gigabyte.com/Motherboard/Z370-AORUS-Gaming-7-rev-10#kf , but USB3 is PITA, only 1 Asmedia on board USB3.1 port are working. Intel USB3 is not supported. I tried VIA 8xx USB and other Asmedia PCI-E controllers, but both are not working some error code in Device manager.. Sorry im not in machine location, but is something like Code 10 or Code 12, device is not working, on part of driver is not working.. Controller worked with other machine and are working with Windows 7/10.. so problem are XP drivers.. Etron and Renesas arent available outside of US on Ebay with reasonable price, what you thing about Fresco FL1100 its not cheap - 20 bucks? Or is there some other good USB3 controller manufactor?

Since we are in an anti-virus related thread, JFYI: https://www.pcmag.com/news/avast-to-end-browser-data-harvesting-terminates-jumpshot jaclaz

Mail and PM issues fixed.

I don't actually see any new revelations there. That concern was already brought up by Mathwiz on August 29, 2019, who stated in his next post, "Despite the cautionary note I posted above, I still use Avast Free on my XP VM myself." I will continue to use Avast Free 18.8 on Vista for reasons already explained on the same page of this thread. According to the first sentence of your first link: It's been about 6 months since I installed Avast, but I definitely did a custom install and probably did not opt in if there was such an option. In any case, if those companies studied my data very carefully, they would find that I never use this PC for banking or shopping, but spend a lot of time at MSFN and other forums. Of course if I was using Windows 10 and Chrome like most people, then companies like Google and Microsoft would no longer have to pay Avast for this valuable data, and it might become even harder to find a good free antivirus! @VistaLover are you still using a Kaspersky 19.x product? At least in the United States, Kaspersky's popularity declined after news reports in October 2017 (see New N.S.A. Breach Linked to Popular Russian Antivirus Software). I understand that Kaspersky has moved its headquarters to Switzerland, perhaps in an effort to repair its image as Russian spyware. If I was interested in paying for an antivirus for Vista, my current inclination would be Eset (see my January 19 post above) - in fact I have stored an installer just in case.

I can certainly add this to the list. But, currently my installer is in maintinence-mode (only fixing serious bugs and not many new stuff) due to not having much free time. I have things for the installer of a higher priority when the free time arises, but I am commited to adding an "install as portable" option eventually. But, yeah. As a reminder, @roytam1 is not affiliated with the house of cards known as my browser installer. He ports changes and compiles binaries, I just make an (Unofficial!) installer that eases the retreival and unpacking of said binary archives.

system.cb is used instead of system.ini when booting in safe mode I believe so whatever is in it shouldn't affect operation of the OS when booted normally.

then this is no longer portable.

The thing is, @roytam1 didn't write and doesn't maintain the installer; @i430VX does! It probably wouldn't be hard for his installer to ask if you wanted a portable install, and add the necessary options to the shortcuts it creates. But @i430VX is the one to ask.

NT 5.1 is almost 20 years old...?

I believe that is the "new layout" mentioned there (but, God forbid, I'm not a twitter user )... It appears you're on Win7 or higher (since you can run FxESR 68); in "about:config" disable native forked-UXP's decoders by setting "media.ffvpx.enabled;false" and make sure "media.wmf.enabled;true" ; restart NM28 (or St52; what is it exactly you're using?) and then see if the audio on Twitter is OK... If Twitter gets also broken in the official UXP browsers (you can also check this yourself, if on Win7), then I suspect upstream will have to deal with that, eventually; there's one report already on the official forums, https://forum.palemoon.org/viewtopic.php?f=37&t=23597&p=181680 however the OP has not indicated yet whether offered remedy cures the issue for him...

You seem angry, not sure what your point is since the forum is about those of us who prefer the older but better versions of firefox. Actually I do use 68esr or the nightly, often side by side with UXP. They both have their advantages and on Windows 7 the UXP version plays videos even better and with less dropped frames and skipping the newer ones. But the quantum versions are better when it comes to javascript in my experience. So they all have their uses. Also I do get that the websites won't support older versions forever but Twitter is heavily trafficked so if it's possible to maintain it a little longer why not try?

... Recently discussed, only four pages ago... Starting post is this one: Please read relevant posts that followed it; I assume you're on XP (the setting under your forum avatar just says "OS: none specified" ), it might be necessary to switch to APCDM in St52 for Twitter (along with an IE SSUAO); also, everyone using XP here should realise that the major "trendy" social sites (youtube/facebook/instagram/twitter etc.), laden with heavy scripts and rich embedded media content, are constantly evolving to cater to (mostly) mobile platforms and, for desktop, to what is the Win10 version du jour... Roytam1 did try successfully to mitigate the lack of WMF and OS patented decoders under XP, but those ffmpeg decoders inside his custom ffvpx library (in UXP browsers) can only cope as much; FFmpeg itself has long ago abandonned XP support, so, if I'm not mistaken, current decoders are based on an older, XP compatible, FFmpeg branch (3.x.x ?) ... OTOH, those social/media sites (especially twitter & instagram) use encoding profiles & new methods of stream delivery that are not guaranteed to remain compatible with forked-UXP's media decoders...

Then USE firefox 68esr or the nightly! Whoala, "problem" solved! Seriously, I do contend that "these" issues will only get WORSE the further along we go. We are using cherry-picked snippets of code designed for SOMETHING ELSE and crossing our fingers that they will work 'here'. I personally have SEVERAL sights that stopped working a LONG TIME AGO so I use 28.2.2. TOO MANY around here give WAY too much credance to the whole Roytam Builds process. NOT to undermine that process, don't get me wrong (I don't know how to do the whole github patching). I see absolutely, positively, ZERO justification for anybody and everbody to ramble off lists upon lists of web sites that "don't work". It kinda gets old, no offense. This "old dog" (New Moon version 28.2.2-ish) does EVERYTHING that *I* need it to do. You can NOT teach an "old dog" new tricks! Throw every "patch" you want at the "old dog", that doesn't make it some new miraculous "breed". If you want 100% compatibility with Twitter, then browse on over to the "supported browsers" page - https://help.twitter.com/en/using-twitter/twitter-supported-browsers (I can't at the momemt because company firewall blocks access) But my hunch is that Twitter is NOT "supposed" to work on any browser "this old", patched or not. But I digress... Again...

Well, I got most of these. I know I have the rest, I've seen them but they weren't in the stuff I had easily accessible.

Another common cause is software depending on software depending on software. If one library drops XP support, others depending on it follow by default.

How charming! Saying that sort of thing to a forum supervisor, even if it was in jest, is not a good idea!

Dedicated to fans of windows XP/2003 running on moderm (Acpi 2.0) PC Main purpose of patcher is help with eliminate/fixing Acpi 2.0 opcodes and 64-bit fields/regions/math without touching bios. Patch modify acpi tables every time when os start, it change current state of acpi tables in RAM memory (Bios load tables from flash chips to ram). Patcher works only with CSM (compatibility) mode, it will never works in UEFI boot mode. Using: 1) All custom files must named in old "8.3" DOS way ! 2) Create folder "ACPI_PAT" at root of you boot drive where installed target OS, this folder is place for storing all custom files (except bootloader) 3) Replace original bootloader (NTLDR for windows 2000/2003/XP, BOOTMGR for Vista/7/8/10, GRLDR for grub4dos) with patcher, original bootloader save as "xpldr" in ACPI_PAT folder 4) Place acpi_pat.img at ACPI_PAT folder 5) Place main configuration file ACPI_PAT.CFG: [DSDT] reload.bin bnum_fix.dif iotr_fix.dif,201904 test1.dif test2.hex [SSDT1] ; patch1 ;SSDT_FI1.HEX [SSDT3] ; patch 3 ;SSDT_FI3.HEX [SSDT*] # universal ssdt patch #SSDT_UNI.HEX [FACS] ;APIC_FIX.HEX [DSDT] [SSDT] - name of acpi table, only 4 chars !!! [SSDT3] - patch 3rd ssdt table, order of the ssdt table is determined by its position in the rsdt/xsdt tables [SSDT*] - special name to modify all ssdt tables ; patch1 - comments start with ";" or "#" reload.bin - BIN override table from binary file bnum_fix.dif - DIF is text format for GNU Patch iotr_fix.dif,201904 - DIF format with forcing iasl compiler version test2.hex - HEX is text format of "Find&Replace" hex strings 6) Order of applying patches is up-to-down, better to place first .bin patch, then .dif or .hex 7) Example of .hex format: ; comment 706869637320/706869637420 ;without spaces 70 68 69 63 73 20 / 70 68 69 63 74 20 ;with spaces, more readable 70 68 69 63 73 20 - hex string to find 70 68 69 63 74 20 - hex string to replace you can increase/decrease count of replaced bytes, size of table will be changed dynamicaly 8) Patcher supplied with 3 versions of iasl compiler/decompiler: IA201604.EXE IA201612.EXE IA201904.EXE These versions are equivalent of 20160422, 20161222, 20190405 at acpica.org Default version for processing dsdt/ssdt tables maded before 2016-12-31 is IA201612.EXE, for later dates is IA201904.EXE. You can also use your own version (DOS VERSION, compile yourself from acpica sources), name it "iaXXXX.exe" and place inside EXE.7z archive on floppy image. 9) Examples of .dif format: Fix BNUM Decompiling Bug: --- DSDT.dsl +++ DSDT.dsl @@ -1,1 +1,0 @@ - External (BNUM, UnknownObj) Fix Resource conflicting on Windows XP for Gigabyte H110-HD2 bioses: --- DSDT.dsl +++ DSDT.dsl @@ -1,36 +1,13 @@ AMI1 = ITA1 /* \ITA1 */ AMA1 = ITA1 /* \ITA1 */ AMI2 = ITA2 /* \ITA2 */ AMA2 = ITA2 /* \ITA2 */ AMI3 = ITA3 /* \ITA3 */ AMA3 = ITA3 /* \ITA3 */ - If ((ITS0 == One)) - { - ConcatenateResTemplate (Local0, BUF0, Local1) - Local0 = Local1 - } - - If ((ITS1 == One)) - { - ConcatenateResTemplate (Local0, BUF1, Local1) - Local0 = Local1 - } - - If ((ITS2 == One)) - { - ConcatenateResTemplate (Local0, BUF2, Local1) - Local0 = Local1 - } - - If ((ITS3 == One)) - { - ConcatenateResTemplate (Local0, BUF3, Local1) - Local0 = Local1 - } Return (Local0) } } } Scope (_SB.PCI0.LPCB) Patches generated by invoking (you can change/remove "-u6" option) Diff : diff -u6 --strip-trailing-cr OLD.DSL NEW.DSL > my_patch.dif Keep in mind that different versions of the compiler generate different versions of the ASL text. So context of .dif file is in most cases bound to specific version of the compiler 10) If using .dif patches, need additional file external.txt this is text format for using iasl.exe decompiler "-fe" option like this: External (AL6F, MethodObj, 0) External (HLVT, MethodObj, 0) External (P0L6, MethodObj, 0) External (P1L6, MethodObj, 0) External (P2L6, MethodObj, 0) External (PS0X, MethodObj, 0) External (PS2X, MethodObj, 0) External (PS3X, MethodObj, 0) External (_SB_.PCI0.GFX0.IUEH, MethodObj, 1) External (_SB_.PCI0.GFX0.GSCI, MethodObj, 0) External (_SB_.PCI0.PAUD.PUAM, MethodObj, 0) External (_SB_.PCI0.PEG0.HPME, MethodObj, 0) External (_SB_.PCI0.PEG1.HPME, MethodObj, 0) External (_SB_.PCI0.PEG2.HPME, MethodObj, 0) External (_SB_.PCI0.XHC_.DUAM, MethodObj, 0) External (_SB_.PCI0.XHC_.RHUB.INIR, MethodObj, 0) External (_SB_.PCI0.SAT0.SDSM, MethodObj, 4) External (MDBG, MethodObj, 1) External (_SB_.TPM_.PTS_, MethodObj, 1) 11) If using .dif patches, may be need additional file ignores.txt this is text format for filter iasl.exe decompiler errors, example of file: [BNUM] Namespace lookup failure, AE_ALREADY_EXISTS Many kabylake/coffelake bioses created with uncorrected asl code around BNUM fileld, when you decompile it, you will get "ACPI Error: [BNUM] Namespace lookup failure, AE_ALREADY_EXISTS (20161222/dswload-390)" error. With ignores.txt possible to filter/ignore these errors 12) When using .bin files, take care about override DSDT/SSDT tables, "template" from BIOS image is bad choice for such files. Bios patch some parts inside table before deploying to OS (bios usualy set absolute adresses). In this case run OS and save tables from runned state. Regards & Copyrights: FreeDOS by FreeDOS Project SHSURDRV by Jason Hood 7zdec by Igor Pavlov/7-zip.org Move by Joe Cosentino/Imre Leber XCOPY by Rene Ableidinger/Eric Auer GRUB4DOS by GRUB4DOS Developers FAT module for grub4dos by chenall.net Volkov Commander by Vsevolod V. Volkov NTFS for DOS by Avira GmbH iASL by Intel/Acpica DJGPP by DJ Delorie CWSDPMI by CW Sandmann inih by benhoyt Internals & Hacks: - acpi_pat.img is bootable 2.88MB FAT12 floppy image with FreeDOS & utils - When pressing any SHIFT key when starting, Patcher will go to debug mode, it will stop loading OS and run shell - Patcher replace original bootloader with grub4dos, when all job is done, patcher run grub4dos.exe for loading original loader - Patcher reserve 2Mb of RAM for storing acpi tables (Windows will report -2Mb available memory) - Before decompiling any table, all ssdt and dsdt tables stored at disk and used as external files "iasl -e ssdt1 ssdt 2 ... " History: v1 - Initial (Beta) Download Binaries https://github.com/MovAX0xDEAD/ACPI-Patcher/releases Download Sources https://github.com/MovAX0xDEAD/ACPI-Patcher

This thread is inspired by pointertovoid's USB functional patches for Win2000 after SP4 and R1, of course! Only those files related to USB that were actually updated after SP3 are mentioned here. None of these updates is known to cause any issues. -----------------XP-SP3----948101v3-949764-945436-949033-959765-968764-969238-2828030-2807986-2868038-2862330-2862335-2884256-3139398-- ======================================================================================================================================= usbd.sys--------2600.0----------------------------------------------------------------------------------6437--------------------------- usbccgp.sys-----2600.5512-------------------5585--------------------------------------------------------6437--------------------------- usbehci.sys-----2600.5512--------------------------5587----------5778---5825----6368--------------------5778--------------------------- usbohci.sys-----2600.5512----5550------------------------------------------------------------------------------------------------------ usbuhci.sys-----2600.5512-------------------------------------------------------6368--------------------------------------------------- usbport.sys-----2600.5512------------5551------------------------5778-----------6368--------------------6437--------------------------- usbstor.sys-----2600.5512-------------------------------------------------------------------------------------------------------7012--- usb8023.sys-----2600.5512---------------------------------------------------------------6352------------------------------------------- usb8023x.sys----2600.5512---------------------------------------------------------------6352------------------------------------------- usbaudio.sys----2600.5512-----------------------------------------------------------------------6425----------------------------------- usbvideo.sys----2600.5512-----------------------------------------------------------------------6425----------------------------------- usbser.sys------2600.5512-----------------------------------------------------------------------------------------------6442----------- usbscan.sys-----2600.5512---------------------------------------------------------------------------------------6418------------------- rndismp.sys-----2600.5512---------------------------------5716------------------------------------------------------------------------- rndismpx.sys----2600.5512---------------------------------5716------------------------------------------------------------------------- hidparse.sys----2600.5512---------------------------------------------------------------------------------------6418------------------- irbus.sys-------2600.5512-----------------------------------------------------------------------6425----------------------------------- ======================================================================================================================================= ---------------------------948101v3-949764-945436-949033-959765-968764-969238-2828030-2807986-2868038-2862330-2862335-2884256-3139398--