FranceBB

EAX? In x86 EAX is a 32bit complete data register, used for arithmetic operations. For instance, in a multiplication, if the size of an operand exceeds a certain threshold (16 if I recall correctly), it's gonna be stored in EAX, otherwise, it's gonna be stored in AX (the 16 bit register). Anyway, what do you exactly mean by "change"? Changing a compiled assembly? As to the source code, we all would like to have it, but unless there will be a leak, we will never get it...

OneCore API will work on both x86 and x64 as there will be two different releases. Anyway, I'm facing BSOD trying to install certain drivers with the current 5.2.8014 x64 release. As to the kernel Dibya is working on, I confirm that Windows XP x86 is booting fine and it works, even though there are some "unexpected behaviours" sometimes, but I honestly don't know whether he will work on a x64 release or not. On a side note: Windows XP x64 is actually really good, but unfortunately it has to run on supported hardware and proper drivers as many users experienced issues with certain drivers.

Ok, so you installed the version for newer Windows, which is compatible with XP anyway? Perhaps, the XP one has the bug and the newer one doesn't? Since you don't have any bugs running the one which is supposed to be for newer OS, I'm gonna install that one as well and I'll let you know.

Right now, there are: 1) Alky for applications: Windows Vista compatibility layer, which will let you run programs meant for Vista, as well as sidebars, once you install it. Just right click on an exe and choose "run as Vista". (It will ask you a Vista licence key). http://alkyforapplications.net/downloads/Alky_1_1_Trunk_032308-000051_xp.zip 2) Xompie which will let you convert programs to make them XP compatible by placing it in your "send to" folder and sending folders containing the programs you want to convert to it. http://www.msfn.org/board/applications/core/interface/file/attachment.php?id=41114 3) Mono which will let you run C# 6 Roslyn programs which have been compiled without XP compatibility flag (I.e lazy developer). https://download.mono-project.com/archive/4.6.2/windows-installer/mono-4.6.2.16-gtksharp-2.12.42-win32-0.msi 4) Direct X 10 - 11 which will let you use them. https://mega.nz/#!rNVSFCQB!eAh54cJVzmCR7nXEHTRh9GHa11agGBsLR_lM_fkG26Y 5) Custom Kernel + HAL to unlock 64 GB of RAM https://mega.nz/#!ndsRFT4L!nOb6r6rq4kN7WcIsnrNOUYqAAclfu2zv3u2hTZS5eXk (Dibya released another one to support up to 128 GB of RAM and fixed some bugs affecting USB drivers; check his version instead if you want).And finally the new project: One Core API which is the one which introduce many things in the kernel, but it's still "work in progress". Of course, the 5 tools mentioned above are x86 only.

Same problem here with the UI. I reverted back to the old version. I hope Microsoft will fix these bugs, as it's in their interest too. On the other hand, they might say "developing for XP brings new issues every time, so we are gonna drop the support". I really hope it won't happen, but it might...

Updated; works flawlessy. Thank you for the heads up

@Sampei.Nihira Well, thanks, but I already configured ipv6, in fact, it works flawlessy within the intranet, but it doesn't work in internet. As you can see, ipv6 is configured and I got both an ipv4 and an ipv6 address. Teredo Tunnelling is configured as well as 6to4 interface. So... the question is: what am I doing wrong? Why do I get an ipv6 address, but testipv6.com fails to detect it (and ipv6 only sites don't work?).

Hi. Every month, I follow a different course on MVA to keep myself updated about new technologies. This month, Microsoft Virtual Academy suggested me a course about ipv6 and I joined. They were talking about benefits of ipv6 over ipv4 and about applications switching between ipv4 and ipv6 automatically, like mail clients etc. During demos, they were using Windows Server 2012, and they suggested to update Windows 7 and Vista with the Readiness Update, and that only Windows 8, 8.1 and 10 have native Ipv6 support. As to Windows XP, they briefly said that Microsoft never implemented a full ipv6 support and that "it's time to move on", while they said "you are in the wild" for Windows Server 2003. Anyway, even though I don't have group policy and all the other fancy stuff, I decided to enable ipv6 via the old fashioned netsh, but when I try to access an ipv6 site, it fails to load. My ISP supports ipv6. Any thoughts? Is there a way to use ipv6 (whenever possible) in Windows XP?

@NoelC and @Mcinwwl yes and no: AMD Bulldozer's architecture uses Clustered Multithreading and has these things called "clusters" which it uses to process stuff. These clusters have two integer (aka ALU) units, one floating point unit (aka FPU), and share an execution engine (aka EX, the "do stuff" part). This basically makes the "cluster" (aka "core") equivalent to a dual-core processor in integer math, and a single-core processor in floating-point math. Now, having double the APUs is great for heavily multithreaded applications and there is a measurable advantage in certain types of applications. Anyway, the Bulldozer "clusters" share FPUs and L2 caches, and this causes single-threads to process slower since they have to "wait" for shared resources (aka serial, or in-order, processing). Hence, Bulldozer "clusters" have slower single-threaded performance as they get stuck in the queue. The Nehalem (Intel) architecture and its children use Symmetric Multithreading, which uses two identical logical processors per "core" - similar to an AMD "cluster," but with 100% of the same resources available to both processors. Each "core" has the equivalent of dual-core APU and dual-core FPU resources, and also shares an execution engine. But, since the processors in the "core" do not share resources in the same way as Bulldozer, it doesn't get stuck waiting for stuff to do. Let's suppose you have an 8 core/cluster AMD and a 4 core/8thread Intel. Your operating system really only sees 8 logical processors when it has to assign threads, so it assigns 1 per cluster, even though the cluster can really do two threads (if they're integer math). When things get stuck, this pretty much makes each "cluster" half the FPU performance of an equivalent Intel "core" and reduces the ALU performance advantage. Intel is faster per "core" in single-thread performance than AMD "clusters" due to their architectural differences. Additionally, Intel's improvements to their execution engines and resource scheduling have caused their 4 "core" (8 thread) processors to eliminate the advantage of 8 "cluster" processors in multi-threaded performance. Fortunately, AMD is abandoning clustered multi-threading in favour of simultaneous multi-threading (like HyperThreading on Intel). In other words, AMD processors have to "wait a lot" for shared resources in single-threaded applications, Intel processors don't, and even though threads are assigned by the OS, the threads a CPU shows to the OS and the way it shares resources across cores are a key point for single thread application. That's pretty much it and sorry for the wall of text.

@mciwnn... Intel CPUs have the ability to scale and redistribute the work on other cores automatically, which is why, if you run a single thread application on an Intel CPU, you will see every core throttling between 60 and 76%, while on AMD you will see Core 0 at 100%, and the other at 1-2℅. That's basically why if you run a single core application is faster than running as many of them as your cores and manually apply affinity. For the records, does anyone remember the failure of the AMD FX/Bulldozer when they tried to run single thread programs?

@JodyT, he probably doesn't have enough RAM, which leads Vista and 7 to use pagefile, that's the only explanation. Even because both UI and background processes are heavier than the XP ones, and that's pretty much why XP doesn't stutter at all. Windows XP, by default, uses as little as 72 MB of RAM in idle, 512 MB with all the programs installed and running in a real world scenario; Windows 7 uses 512 MB by default and 728/1GB in a real world scenario.

By the way, since you mentioned that, WhatsApp desktop supports Windows 8, 8.1 and 10 only.

I gotta thank Heinoganda because his program solved the problem once again. Tested and working, so... thank you.

Microsoft C++ Redistributable 2017 has been released for XP as well! Link

Installed successfully on mine as well. I had the same issue months ago with Silverlight when I tried to update and after googling and trying useless stuff related to the error code I got, I cleaned everything up and freshly installed it. No problem since then. Unfortunately, things like .NET and Silverlight are corruption prone during updates.

Uhm... interesting question Basically, when you install a program, links are created in the registry entries by Windows Installer which is the one in charge of creating them and use them in order to repair an installation, uninstall a program or roll back changes whenever some errors occurred. In fact, you need to specify the path in which a program will be installed at the installation time. In this case, you are trying to use tweak UI from Windows 2000 to move the programs files folder. Such a tool will also have to modify every link in every registry entries. Unfortunately though, Windows 2000 is slightly different from XP, especially because XP can run a greater version of Windows Installer than 2000. In a nutshell: I don't think it will work, but you may be extremely lucky and if nothing changed between 2000 and XP and between these two versions of Windows Installer, then it will.

Good. Will you release binaries as well on github? Besides, about the kernel and Windows internal DLLs: would compiled them with anything greater than SSE2 bring any benefits in the overall performances of the OS? Oh, almost forgot, thanks in advance for everything you are doing!

As we all know, Microsoft did psychological terrorism about Windows XP in 2014 in order to persuade users to move to newer OS. Then, they easily got rid of Vista as it wasn't widely used, and now they are applying the exact same terrorism to Windows 7, using the exact same words used 3 years ago about XP. "Care about your security? Then leave Windows 7 says Microsoft" "The old OS suffers from ‘long-outdated’ security architecture" "Microsoft is highlighting the security strengths of Windows 10 as the company waves an ‘early goodbye’ to Windows 7" "Windows 7 is no longer capable of keeping up with the increased security requirements applicable to the PCs of today, and it’s based on long-outdated security architectures" "Many hardware manufacturers no longer provide drivers for Windows 7, which means that modern peripherals such as printers are no longer recognised." Ridiculous... just ridiculous... (except for drivers).

I personally use Office 2010 and I'm fine with it. Anyway, out of curiosity, I noticed that in a company in which a friend of mine works, they used the same Office product key for 6 machines; would using it on 7 computers (one more computer) cause any issues?

@Tripredacus... page file is enabled in "O" (an hard drive) and disabled in "C" (an SSD) in order to prevent XP from wasting SSD cycles. It's set up to 8 GB instead of leaving everything to the OS because when I make DCT and motion vectors calcs I need to "cache" several frames (actually, 4x4 blocks and 8x8 macroblocks) and I make a large use of virtual memory. Both "processor planning" and "memory usage" in the "advanced" menu are set to "programs" (default). In "avvio e ripristino" (start and recovery) menu, in "write debug info", "full memory dump" was selected but got disabled for some reason, I think because of a third party software and I think Avast is the one to "blame". Well, not exactly Avast the antivirus, but the "tool" they gave to the beta testers few months ago to make a full memory dump if errors occurred while running Avast Beta when it was released. I think they had in mind to activate a full memory dump themselves for everyone for testing purposes and they later on disabled it for everyone when we were moved to the stable branch, regardless of the settings that each user had chosen before joining the beta channel. That would explain why the last memory dump I have is dated 16/04/2016, when I got a BSOD due to a faulty USB Multi-Hub driver (it was because of the PAE, 'cause I remember it worked back in the days when I didn't have the PAE patch). Well, I think we can say "Mistery Solved" this time. Thank y'all!

I already ran a check disc and sfc scannow, but everything was fine already. ( I generally run CHKDSK C: /F /R on my HSSD once a month, as it's generally a good habit). I did run memtest which resulted to be ok. Since it was the very first time I had that issue, I decided to further investigate. I replaced avisynth core 2.6.0.5 with the 2.6.1 one (which wasn't the problem anyway) and I replaced FFMPEGSource2 with DirectShowSource and... ta-da... everything is running smoothly. Well, the encode hasn't finished yet, but it has been running for about 8 hours without any issues, so I'm pretty confident it will make its way to the end. It actually seems that it was software related. Unfortunately, the "new" ffms2 has something that make the old good Windows XP crash if called multiple times in a session. That would also explain why the very first frame was "weird", like black with a few gray lines at the very beginning, something that never happened before. I will definitely report this to its developer, even though he said that even though he added XP support back, XP-related bug will have lower priority, so... fingers crossed... :|

Hi! Just wondering whether it's hardware related or software related. I started an encode using x264 and avisynth with the following instructions: http://pastebin.com/Cnq38GD8 Such an encode is actually very normal and I didn't run anything weird. A weird thing, though, is that I have a full memory dump set as default in case of BSOD, but this memory dump doesn't show up in BlueScreenViewer and it's not in the "minidump" folder in C:\Windows\Minidump. I'm running Windows XP Service Pack 3 x86, 64 GB PAE Russian Pack (Chinese mod + Windows Server 2003 x86 drivers). PosReady Updates, Windows Embedded UI, C++ Redistributable 2005 - 2015, Intel C++ Redistributable 2016, .NET Framework 1.0 - 4.0. I'm gonna run the encode again and I'll let you know. My system it's pretty old, but has never been overclocked (I stopped overclocking during the last two years).

@liquidLD... well, yeah, you can use MSE, but Avast offers a Firewall, a Sandbox, a boot-time scan which occurs while the OS is not booted (like the CHKDSK) to remove even the hardest threats, streaming definition updates, automatic software updates, and many other features... (I'm an Avast Beta Tester since 2013 and trust me, Avast is gonna release a new major release within few months which will merge the best features from both Avast and AVG in order to make a better product which is definitely worth using). Anyway, I don't wanna go off topic, so feel free to ask me anything about avast in PM.

@liquidLD... that's simply the Chinese patch which has been discussed over and over again and it may create some incompatibilities with USB drivers (as it has been discussed over and over again). There's another patch as well, which is the Russian patch, which achieves the same result as the Chinese one (same files), but includes some sys files from Windows Server 2003 x86 in order to avoid (well, at least, to limit) the USB issue discovered. I have been using the same method you posted for months, then I switched to the Russian patch 'cause I was too lazy to replace system files with the ones from Windows Server 2003 x86. @bluebolt... yes, I think it should be merged to the other main topic too.

Very good. Still, I don't get why some developers keep spending too much effort for Linux, while abandoning XP which has a greater market share... Anyway, XP rocks again! It's gonna be a good trip 'till 2019 and we are here all together, in the same boat. XP share has been a roller coaster ride, but this wonderful light OS has still a lot to offer.