Jump to content
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. ×


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

  • Country


Everything posted by FranceBB

  1. Just as a heads up: Facebook has updated its skin and it f***ed up the visualization on Chromium 54 (spoofed as 85). It works fine on NewMoon, though: which, once again, shows how much we all appreciate Roytam's work.
  2. Well, just update it here, I'll include it in my first post: https://forum.doom9.org/showthread.php?t=175829
  3. Yep, it got updated automatically today for me. Works like a charm.
  4. Hi there, just to report that with NewMoon, Slack has to be added in about:config, otherwise it gives an error about the browser not being compatible: general.useragent.override.app.slack.com;Mozilla/5.0 (Windows NT 5.1; WOW64; rv:99.9) Gecko/20100101 Firefox/99.9 (Pale Moon) Changing the user agent works like a charm. Cheers, Frank
  5. Easy, you don't install them as those updates are meant for Win7 and they have been mistakenly rolled out to XP / POSReady users that have Office 2010 as well thus breaking their Office build.
  6. Just for info: @Dibya (a developer from our group) just patched the security vulnerability CVE2020-0674 by backporting the fix from newer Windows. @dencorso I assume we can only post it on RyanVM, right? Or can we post the patch here? 'cause if we can we're gonna post a link.
  7. Potplayer is both x86 and x64, so I think it tried to install the x64 version on your XP x64 even if you wanted the 32bit version. I wouldn't be surprised to find out that the 64bit isn't supported. The 32bit version, however, works as expected on XP x86 without any fancy mod or anything. I have an x86 version of XP myself, so...
  8. It means that a new version of PotPlayer has been released and it's still compatible with XP. PotPlayer is very well known to be a very good player based on open codecs that still supports Windows XP, so, instead of writing every time "A new version of PotPlayer which still supports Windows XP has been released, namely version xxxx" Sampei just began to write "Out PotPlayer v. xxxxx". Anyway, I understand that it can be a bit confusing for people unfamiliar with the software and the topic. For the records: I was offered to update the other day, I updated and it's working flawlessly.
  9. Yep, I've just updated Adobe Flash Player. As a side note, Oracle never replied to my ticket... I like to think that they didn't purposely ignored me and that it's just because of covid-19 and they're busy / with limited capacity...
  10. I know DoaJC_Blogger, he's on our Windows Forever Skype Group and we've been talking several times over the past months. His re-write of chromium is the best chance we've got so far, however we're not quite there yet because of GDI. Once again: If any of you have C++ skills and wants to help, please contact me on Skype (francebb1 - franceopf@gmail.com) and I'll add you to the group so that you can help in the development.
  11. Well... SunMSCAPI it's part of security.cpp in src/windows/native/sun/security/ and these APIs are used by desktop applications for things like to access smartcard certificates for TLS connections and other stuff, so I can't tell you that it's safe to ignore the update, however I don't have enough knowledge of Java to tell you that it's critical either.
  12. I finally had time to look at this as well and I can confirm that it doesn't work on my computer either and I know why. Precisely. We did backport ncrypt.dll but it also relies on a series of dlls, two of which don't exist in XP either: NTEXT.DLL and BCRYPT.DLL. Although bcrypt.dll has been backported as well, there's no current implementation of NTEXT and the following APIs in our modified version of XP: RtlDeleteResource RtlInitializeResource NtClose RtlInitializeSRWLock RtlReleaseSRWLockExclusive RtlAcquireSRWLockExclusive RtlFreeSid RtlAllocateHeap RtlSizeHeap NtOpenKey RtlNtStatusToDosError NtQueryValueKey RtlCompareUnicodeString NtQueryInformationProcess NtOpenFile NtDeviceIoControlFile RtlImageNtHeader RtlReleaseResource RtlAcquireResourceExclusive RtlAcquireResourceShared LdrDisableThreadCalloutsForDll RtlAllocateAndInitializeSid RtlInitUnicodeString RtlFreeUnicodeString RtlAnsiStringToUnicodeString RtlInitAnsiString RtlFreeAnsiString RtlUnicodeStringToAnsiString RtlFreeHeap RtlReleaseRelativeName NtCreateFile RtlDosPathNameToRelativeNtPathName_U RtlAbsoluteToSelfRelativeSD RtlGetControlSecurityDescriptor RtlNtStatusToDosErrorNoTeb NtOpenProcess RtlInitializeCriticalSection RtlDeleteCriticalSection RtlLeaveCriticalSection RtlEnterCriticalSection RtlAppendUnicodeToString And... sure, you could just replace that DLL (sunmscapi.dll) and use an older one to make Java work: However the future doesn't look bright 'cause this time we've been lucky and it was a trivial component, next time we might not be as lucky... (I'm tagging you just for an heads up: @Dibya, @neverseen, @Skulltrail) Shall we try to report it to Oracle and pray that they'll revert to the former implementation of sunmscapi? EDIT: I reported it to Oracle Name of the Applet or Application: Java 8 Update 251 Provide clear and detailed description of the problem you are experiencing, including error messages: As we rolled out the new update to our Windows Embedded POSReady 2009 tills we noticed that sunmscapi.dll was changed and is now calling ncrypt.dll which represents a problem as those APIs don't exist in our Embedded version of Windows. After we rolled out the update, we replaced sunmscapi.dll with the former one. This way, we managed to get Java 8 Update 251 work. It's a shame to break Embedded products compatibility just for a silly call to the APIs like this one. You can see that it works on this test machine running Windows Embedded POSReady 2009 x86 in Virtual Machine: (screenshot). Your Operating System: Windows Embedded POSReady 2009 x86 Java Software Version: 8 Update 251 Which Java version(s) did this work with before this issue? 8 Update 241 Thank you for taking the time to write. We will reply as soon as possible, Oracle.
  13. ElectroBOOM published a new video in which it compares different kind of lightbulbs and he used a camera to analyze the light spectrum. The software he used to see the spectrum was clearly running on Windows XP. Video (if you're curious, check minute 6:33):
  14. Yep, many Avisynth plugins can compile but don't work on XP without /Zc:threadSafeInit as XP doesn't have a way to handle the way they use to handle threads, therefore /Zc:threadSafeInit is needed to make them thread-safe and compatible with XP. If you could try to compile it again but with /Zc:threadSafeInit I can test it. As to the topic, I've seen the topic, let's move our conversation there as it's more encoding-related (doom9-related). We'll get back here if it works.
  15. The following script works: video=AVISource("Z:\Isilon\421.avi") audio=FFAudioSource("Z:\Isilon\421.avi") AudioDub(video, audio) which means that FFAudioSource is working: however if I try to use FFVideoSource directly it reports an access violation, just like the one you got: FFVideoSource("Z:\Isilon\421.avi") The weird thing is that it tries to do something and in fact the indexer does index the file and it creates the relative .ffindex file like: Analog_bad_source.avi.ffindex or test.ffindex which means that it's indeed working fine, but something fails when it tries to load the uncompressed video stream into Avisynth. Besides, it doesn't even have anything missing when I look at it in dependency walker. I mean, we're almost there, it can work! As to the SSE2 code in ffms2, you think it's that one that it's holding us back from having it running? Did you compile it with /Zc:threadSafeInit as well? Perhaps we could reply to the ffms2 C Plugin thread on Doom9. Even if qyot27 doesn't actively support XP anymore, maybe someone else like pinterf (Ferenc Pinter) or others will pop up and point us towards the problem.
  16. Well, fair enough, but DDR3 and such an old socket (LGA 1155) from 2013, it's hardly gonna attract anyone... I mean, who would want two DDR3 slots and an Ivy Bridge 22nm Intel CPU when the best thing you can put there is an Intel Core i7-4960X 6c/12th 15MB of cache released on September 2013... It would be useful to have modern chipsets released with Windows XP drivers, not old deprecated stuff brought back into manufacturing and offered as new when they're clearly not...
  17. Well I did install the free version and it hasn't caused any problems so far. On their website they also said that their patches are known to cause problems with Avast, but I have Avast Premier and nothing happened at all, everything is working fine. P.s if you're wondering why I'm replying at 1.45AM is because it's very windy and my plastic shutters are like making some sort of cracking noise (like when you're sitting in front of a bonfire)... Anyway long story short: I can't sleep.
  18. True, however that was for Microsoft updates. Anyway, if 0patch is good enough and overcomes Windows Updates with as little as 23€ per year then it's fine for me. Yes, that's exactly the same as mine: same system (but Professional instead of Home), same values. 332 patches installed, 56 patches available for purchase. Anyway, I'm really prone to pay for it, I just asked you all 'cause I wanted a second opinion.
  19. I wanna talk about 0patch again. I installed it on my system which is fully updated and it found a whopping number of vulnerabilities which can be patched. I'm gonna share a few screenshots. I also checked the service and it's using as little as 9 MB of RAM when it's in the tray icon. Free licence costs nothing, the premium one is €22.95 per year per computer. Do you think it's worth it? As to the 2020 updates, I'm particularly interested in those that are offered by 0Patch for Windows XP: CVE-2020-0683, CVE-2020-0883, CVE-2020-0668, CVE-2020-0729, CVE-2020-0687
  20. What's the point of your post? The link has been in the first message of the topic the whole time...
  21. Uh... well, that's true; I was wondering though whether they made a mistake in the documentation (it was a premier update supposed to be kept secret?) or in Windows Update (it was a legit update and should have been published)... I guess we'll never know...
  22. No they are not, they're about 500 kbytes; perhaps it was your connection. As to the repacking thing, I wonder whether it would be better to go with Windows 7 x86 or Windows Server 2008 x86 (which is Vista) to repack it for XP... Anybody wants to give it a shot? Although it's useless for many of us, it would be the first widely available (kind-of-leaked) Microsoft Premier Support for Partners update for Windows XP; that's a milestone! xD

  • Create New...