Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

96 Excellent

About FranceBB

  • Rank
    C# Developer
  • Birthday 07/29/1993

Contact Methods

  • MSN
  • Website URL
  • Skype

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

2,291 profile views
  1. Thank you @harkaz for pointing out the differences and thank you all for reporting the bug. As a matter of fact, we tested the update with both Windows XP (Real Machines), WES09 and PosReady 2009 (Virtual Machines) and the bug is still there. With all the informations collected here, I contacted Microsoft to let them know about the issue. I'm confident they'll fix it and roll out a new update in the future. Cheers.
  2. Windows XP Spotter (the club)

    I got myself a router from the States today. Unfortunately, the seller shipped it to my house in the UK with the American charger, so I went to a local shop here in Queensway. As soon as the guy went behind to look for the adapter I asked, I quickly took a picture of the computer of the shop: a dusty machine running Windows XP Professional.
  3. I know many people are complaining about the recent updates, but luckily nothing happened to my machine. I think it really depends on our hardware. With my 1TB Seagate HSSD, my Intel i7 6700HQ 4c/8th 2.60GHz and 16 GB DDR4 (8x2), I didn't have any issues. My system is running just fine. I think that these updates might have screwed up a few things in systems with older hardware. Perhaps Microsoft engineers tested these updates on virtual machine with recent hardware? Who knows. By the way, NHS just signed an agreement with Microsoft to get Microsoft's Enterprise Threat Detection Service which provides an antivirus service as well as updates for their systems, including Windows XP and Server 2003 until this summer, so it's very likely that their 30'000 XP machines will get the same updates we get, which is a good thing. (This actually reminds me that it's been two years since the last time I had a blood test. I think it's time to ask NHS for a new one).
  4. I have an AVX and AVX2 capable CPU, although XP only supports SSE4.2, that's why I compiled everything in SSE4.2. Anyway, I accidentally tried to run an AVX-compiled program once and it didn't run: it got stuck at launch-time, executing only partially the code (the asm part of it), thus complaining about non monotonic function once it passed the result to the encoder. In other word, AVX, AVX2, AVX512, FMA don't work in XP, AFAIK.
  5. I'm not facing issues either on my NTFS SSHD nor on my Synology racks network drives formatted in ext4. It's mainly a computer I use for work and an encoding running since I installed the latest updates and rebooted, so I didn't have the chance to test it properly. (It's a 4K Remaster of a movie that implies using many filters during post processing, thus using 6 GB of RAM for Fourier calculations, Karhunen-Loève Transform, Discrete Cosine Transform calculations, motion vectors calculations and so on, so the system it's stressed, but so far so good. People generally don't believe that some of the detailed 4K they see on air are processed using Windows XP). It's probably going to finish in the next few hours after days of encode, so I'll soon have the chance to install the .NET Framework, the "latest and greatest" Avast beta update and perhaps reboot and make it rest for a while. It deserves it after days at 100% CPU usage. My only concern is that I'll never get the patch for my CPU... and I'm definitely affected by Meltdown and Spectre, 'cause I'm running an i7 6700HQ, 4c/8th with 16 GB DDR4 (8x2) and an NVIDIA GTX 950M. Well... I hope Avast will prevent threats from stealing data, but still...
  6. I strongly suggest you not to crack an antivirus; they could stop providing new defitions anytime without bothering to tell you, or worse.
  7. I sent a message to Microsoft, trying to sensibilise them on the issue: "According to the Microsoft statement about the Spectre and Meltdown issue, Windows XP and XP-Based systems like POSReady 2009 won't get the patch, despite the latter is supported 'till 2019. Many manufacturers providing recent hardware don't even support XP and many old CPU are not affected by the issue, but many businesses are running VMs on recent hardware, that's why I think it would be extremely useful to have the patches available for XP and XP based OS, considering it's still the third most used OS." They'll probably just ignore my email, but at least I tried.
  8. Installed both from the yellow shield that popped up; rebooted successfully and no issues found. Nice and quick. It seems that the latest Avast beta works fine. (I have Avast Premier, though).
  9. A new security flaw has been discovered; it affects CPUs and it's bad... like, really bad... "Details of the flaw and how it might be exploited are being kept strictly under wraps while programmers rush to redesign operating systems including Windows and Linux to work around the bug. Calcs executed by the CPU may not necessarily remain hidden between the Kernel, the HAL and the CPU itself and an attacker might be able to steal passwords or other key information from the kernel. Operating system vendors are making fairly significant changes to work around this issue. This is going to be one of the most complex security updates any OS vendor has ever had to deliver."
  10. FFMpeg and Windows XP in 2017

    The latest Zeranoe xp-compatible build was ffmpeg-20150525-git-8ce564e, released on May 2015. After that, people started complaining about the following error: "The procedure entry point _wfopen_s could not be located in the dynamic link library msvcrt.dll". On the official Zeranoe FFmpeg Builds site, it says that "All builds require at least Windows 7". So, I took a look at the code and I noticed that FFmpeg code itself has not stopped being XP compatible, but the inclusion by Zeranoe of some external libs that are either themselves by default not compatible or have become incompatible at some stage of their development is what broke Zeranoe builds. Anyway, many external libraries and codecs are still compatible with XP, they just need to be tweaked correctly, just like MSYS2 did, in fact I used their project to compile ffmpeg with GCC and, as result, the build is updated and XP compatible. FFMpeg 2017 x86 - Windows XP, WIndows Vista, Windows 7, Windows 8, Windows 8.1, WIndows 10 Compatible https://mega.nz/#!Od9DRD5R!ynjjY9uHzLM6UYLZl5xFMxQ1gnkPZxbmcCvGr9fuAvk Happy new year.
  11. Hi, I'd like to replace the default login background image with a solid color one (grey) for all users and I would also like to change the default picture of every account with the company logo. The problem is that I don't know how to do it with Windows Server 2016 (group policy). I already set up a bunch of things that were consistent with the 2008 R2 version. We recently upgraded from Windows Server 2008 R2 to Windows Server 2016, but I've been hating it since day 1. Although all the new stuff available with PowerShell are lot of fun, it doesn't seem to match my idea of server: too much graphic design that is absolutely unnecessary for a server. Thank you in advance.
  12. You know, I didn't have any issues, but when you pointed that out, I checked my winlogon.exe and I found out I had the old version: 5.1.2600.5512. I've just donwloaded the Italian version and updated. Thanks ^_^ As to the KB955704 (exFAT), I tried to google it but I didn't find it. Dencorso, your version is the English one, but my XP install needs the Italian one. I found a user who uploaded it on his dropbox in 2016, but that link expired too. It seems that only the one for Windows Server 2003 is available, which is a shame. Many people complained in the Italian Microsoft forum, but didn't get any useful answer from Microsoft MVPs. Perhaps @jaclaz has an Italian XP install and KB955704?
  13. KernelEX for XP.

    Rather than Alky for applications - which is quite outdated - give XomPie a shot. Hopefully it will patch it correctly and you'll be able to run it.
  14. Windows XP is still king

    October 2017. Stats by Verizon.