All Activity

Same here. Which crucial features do you miss in the free edition of IOBit Malware Fighter? And why don’t you get a 6-month licence for the Pro version? You can find them everywhere, and they’re even available at regular intervals. IOBit runs lots of promotions. I managed to get hold of some yesterday.

And what exacty does that mean? The problem with one-sentence answers that contain no information is always the same. They’re of no use to anyone. And the reader is then left to guess, interpret or make assumptions, which only lead to rumours and wild theories. That is completely counterproductive. So please provide a bit more information!

Notice: since there is no significant commits in upstream, no builds will be released tomorrow.

The problem with VirIT is their quote: "Virus and malware removal for 60 days", so a non-starter for me. Oh and Panda is acting up again, surprise surprise. :-/

For reference, here is the menu bar in question. You can toggle to hide/unhide it with "Alt" back in StartIsBack on Windows 10. Right now for Windows 11 I could not find a way to access it when using the Windows 7 ribbon.

Nothing is "unblockable". Just need to use more creative methods. I would love to assist further, but my three "throwaway" Yahoo accounts no longer allow me to log in and trying to create a new Yahoo account is asking for a phone number (which I will not provide).

It seems that Yahoo Mail have just switched to new, slow interface, which doesn't work anymore with New Moon, and tells me to update the browser. The simple/basic/classic mail, which was one of the two choices, is no longer accessible, and the modern one looks entirely new. It has so many ads, holy crap. It uses the unblockable AdShield service I mentioned before from randomized domains.

A review Of VirIT kind of old but I would say rather indicative of what to expect 12 years later. https://www.insightsintechnology.com/2014/01/virit-explorer-lite.html @AstroSkipper Conidering this plus the post right above this one, I think I am going to get myself an AV..

@VistaLover Thank you for reporting the problem. I will investigate and make new builds.

For the time being I am trying to avoid going back to a full build which may contain many libraries that nobody uses. It will expand as fixes and requests are added to it. Here is a build for you to test with added support for https. The next release can include it in all builds. https://files.videohelp.com/u/69760/ffmpeg-8.2-2237-b4b30ff8fd-win32-shared-xpmod-P4.7z

Thank you once more for these new releases ; however, I have to report that the latest ffplay.exe compiles for Vista x86, BOTH the static+shared binaries, are completely broken under Vista SP2 x86 (with ALL MS updates until EoS, and then some ); whatever media file you throw at FFplay.exe (e.g., via drag-n-drop) results in the app instantly crashing; below, an instance of a plain MP4 file containing h264 video + aac audio: Your previous VISTA release works as expected with that same MP4 file: FWIW, your latest FFplay.exe static compile for WINXP doesn't suffer from this issue and plays the MP4 file without any problem: You'll probably need a Vista SP2 x86 VM to troubleshoot this, as I have no clue as to what might have gone wrong; perhaps an updated third-party lib has in the interim (n8.2-dev-1568...n8.2-dev-2232) removed support for NT 6.0? We know it's not caused by upstream (FFmpeg source code), because your n8.2-dev-2232 compile for XP works OK; in addition, when I probe the MP4 file with latest FFmpeg for VISTA, it doesn't crash: ffmpeg version N-125505-gc57660fb18-WINVISTA Copyright (c) 2000-2026 the FFmpeg developers built with gcc 16.1.0 (Rev5, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libdav1d --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug --enable-librubberband --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 61. 2.100 / 61. 2.100 libavcodec 63. 5.100 / 63. 5.100 libavformat 63. 3.100 / 63. 3.100 libavdevice 63. 2.100 / 63. 2.100 libavfilter 12. 2.100 / 12. 2.100 libswscale 10. 2.100 / 10. 2.100 libswresample 7. 2.100 / 7. 2.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Mastermind_Se8Ep12[2494504515559].mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf62.13.101 Duration: 00:25:41.93, start: 0.000000, bitrate: 968 kb/s Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(progressive), 768x432 [SAR 1:1 DAR 16:9], 837 kb/s, 25 fps, 25 tbr, 90k tbn (default) Metadata: handler_name : VideoHandler Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 125 kb/s (default) Metadata: handler_name : SoundHandler At least one output file must be specified Hopefully you'll be able to get to the bottom of this, as I do use FFplay.exe myself under Vista SP2 (32-bit) ; thanks for all your hard efforts already!

What I now expect from an anti-malware programme is that it simply warns me of any threats. No automatic removal, as I’ll take care of that myself should one ever arise. I have my own specialist tools for that. And most alerts are false positives anyways. It’s very important that it uses very little RAM and CPU. That’s why I think VirIT eXplorer Lite is great for my system. And I prefer real offline definition updates. Cutting down unnecessary features is therefore no problem for me.

https://startisback.com/StartAllBack_setup.exe

[HKLM\SOFTWARE\Microsoft\PolicyManager\current\YOUR-USER-SID\Connectivity] DisableCrossDeviceResume = (DWORD)1 DisableCrossDeviceResume_ProviderSet = (DWORD)1

I forgot to answer that one. No no, I don't use any fancy kernel extensions, just USP4. 12.5 is for XP no doubt. However I already threw it off my box because it's too cut-down. I have, as before, observed that Panda (my favourite version 22.03.01) 2x calls rootsupd.exe (XP's cert thing) during installation, so I quickly reacted and after the second time I ran a-new extracted Thomas' CA Updater so it finished before green-blue Panda orb appeared in the tray. We'll see if this now works. As I said before - the whole thing to me is certificates, don't know specifics though. Depths of Satan... Otherwise it's Avast patchwork quilt for me again...

@modnar Or do you use an extended kernel or an additional layer in your Windows XP installation where you have installed IOBit Malware Fighter 12.5?

I also mentioned that very often, people who use Windows XP also use the latest versions of Windows, such as 10, 11 and so on. If you’re completely disappointed by one operating system in terms of Panda Dome, it doesn’t reflect well on the others. Here is aditionally a screenshot with nearly all Panda hotline numbers at no costs: All Windows XP users here on MSFN and all guests reading this thread! Call them and report your issues with Panda Dome under Windows XP!

That's great, but as you say, it has to be more than just you and me! Especially good that they now have reports from two different countries. 👍

The same stream is available through plain HTTP, http://paranormalium.waw.pl/radio/8000/mp3_48 so you can use that with an FFplay compile without HTTPS support built-in ...

FYI, today I contacted Panda Security by telephone via AnyTech365 and informed them of the problems with Panda Dome's PSANHost process on Windows XP, which have been ongoing since 2 July. There are indeed free of charge helpline numbers for all sorts of countries, and as many users as possible should get in touch. Here is the page with the telephone numbers: https://www.pandasecurity.com/en/homeusers/free-antivirus/support/ So please leave a message there. Call them! The more people who get in touch, the better.

... But the author has already mentioned that : The community of XP-using members here has to reach a consensus as to what should be the minimal configuration of the FFmpeg/XP compiles, so that autodidact doesn't have to jump through hoops to try and satisfy each and every one of you ; remember, this most kind person is offering an invaluable service out of the goodness of their heart ; compiling binaries is a time and CPU (read: electricity) consuming convoluted process...

Versions for XP. All full versions work fine. The lighter, stripped-down versions, including the latest one, do not support HTTPS. For example: ffplay.exe -i “https://paranormalium.waw.pl/radio/8000/mp3_48” ffplay returns this error: https or dtls protocol not found, recompile FFmpeg with openssl, gnutls, or securetransport enabled. https://paranormalium.waw.pl/radio/8000/mp3_48: Protocol not found So here’s my question: Could you release the full version for XP at least once in a while? The lightweight versions are great, but there are always unexpected issues with them, just like in this case.

Don't you have UnofficialSP4 from harkaz installed? There is all you need in that Service Pack.

Check all available log or dump files! Maybe, there you get a hint.

It was a very old version long time ago. I don't remember what version number it exactly was. But what about 12.2.2 advertised by COMODO? 😜