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. 


FranceBB

Member
  • Content count

    267
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

FranceBB last won the day on April 8

FranceBB had the most liked content!

Community Reputation

99 Excellent

1 Follower

About FranceBB

Contact Methods

  • MSN
    franceopf@gmail.com
  • Website URL
    http://www.adcelites.cloud
  • Skype
    francebb1

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

2,457 profile views
  1. TeamViewer crashes after update

    It's working fine on my machine. I don't know why it crashes on your. It lets me connect to Windows Server 2016 flawlessly.
  2. TeamViewer crashes after update

    I use XP on a daily basis on XP and it was working fine 'till last week, but I might not have the very last version. I'm not at home right now, but as soon as I get back home, I'm gonna check with the latest update.
  3. Up to date browsers for Windows XP SP3?

    Firefox 52 ESR still supports XP. Advanced Chrome (a modified chromium fork) supports XP. For a longer and more detailed list, please check this topic: https://msfn.org/board/topic/176299-latest-version-of-software-running-on-xp/
  4. NVidia stops support for 32bit

    That's so sad... Years ago, softwares were all x86 32bit and just a few of them were x86_64 64bit... now it's the other way round... Sadly, 64bit systems were able to emulate 32bit programs, but 32bit ones can't emulate 64bit for obvious reasons... I know that was just a matter of time before this happened, but guys, it seems yesterday when the first x64 systems were developed... Doesn't time fly? :'(
  5. Latest Version of Software Running on XP

    There you go. http://rwijnsma.home.xs4all.nl/files/ffmpeg/ffmpeg-N-89661-ge45f7bc-win32-static_legacy.7z
  6. Yes, sure, but it's user-defined and applies to you only. You can whitelist programs or directories. What I thought you asked me was to send it to the lab so it would have been checked and whitelisted for every Avast user xD
  7. Nope, it scans it on access every time you try to open it, unless the lab says it's ok. If you download the latest beta I think you can actually send it to the lab too and attach a note in which you briefly describe what's that about and why it should be marked as safe. Avast won't do that automatically.
  8. Repacks are not digitally signed by anyone and are therefore scanned. Avast shouldn't scan those files twice, but only once, though. Maybe there were multiple executables, that would explain the double scan. Anyway, it should scan files on access, which means when the user tries to run an unsigned executable. As long as it's just the scan, you can skip it or add paths or files as exceptions, but if you are willing to let the lab know, I can send it through, however even though it's gonna pass the test and be marked as safe, it's gonna be for that patch only. This basically because it's important to scan every non digitally signed executable 'cause it might contain hijacked code meant to harm users. Heinoganda is a very good member of this community, I kinda trust him, but I can't say the same for every folks out there who modify a program.
  9. Latest Version of Software Running on XP

    As long as potplayer and the open codec project are alive, nothing, but in the future, I would say compatibility with newer version of famous under development codecs, like HEVC, but for the moment we are still safe. I don't think potplayer and open codecs will drop their support until 2019, then we'll see. FFmpeg and ffms2 have already been backported and are constantly updated, x265 works under XP as well as avisynth frameserver and pretty much every filter for that frameserver. As long as all these things don't break, we are kinda safe, however we are living on borrowed times...
  10. Latest Version of Software Running on XP

    K-Lite Codec Pack dropped support for Windows XP with version 14.0 The latest version that works with Windows XP is 13.8.2 which is recent and supports many codecs, but it will get older and older within the following months. This sucks because without the K-Lite Codec Pack, there won't be new updates for LAVFilters, MPC-HC and we won't be able to open videos encoded with brand new codecs. At the current stage of things, we have compatibility with pretty much any kind of codecs ever invented with any resolution, bitdepth and color space, except a few things involved with the new AV1, which is currently under development https://en.wikipedia.org/wiki/AV1. Anyway, the open codecs project still support Windows XP, so we will still be able to get updates for PotPlayer and we will still be able to open videos made with new codecs, including the latest version of AV1. I don't know how long they'll keep XP support, though. Times are tough...
  11. 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.
  12. 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.
  13. 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).
  14. 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.
  15. 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...
×