All Activity

You are writing nonsense opinions you have heard WinXP 64-bit is a stable system - I know what I'm writing because I have been using it for a long time and it works great Besides, before you write something, check if it works. I checked it and it works OK on WinXP 64-bit @Tech Stuff actually did a good job - his patched version works. Thanks for you

Vista, even Vista SP2 is version NT 6.0 (6002), I don't know where you got 6.1, that's Win "7". Now do that in real XP; WinXP has always been x86 and not that patchwork of so called XP 64-bit. That's server (NT 5.2). With no real software support, so useless.

In the mean time I have cleaned my system of pandas, so I cannot really be of assistance. As we've all observed their technical support is a joke and now also their program is a joke, even more as it was before, so good riddance. I don't know why they would be promoting themselves as best for WinXP though, when clearly they do not want anything to do with us.

@Tech Stuff OK, after vcredist x86/x64 (Microsoft Visual C++ 2008 Redistributable - 9.0.30729.6161) install now VMware Workstation 11.1.4 work on WinXP 64-bit Is it possible to activate the network somehow? I can install VMware Bridge Protocol but I cannot add a Bridged connection: Cannot change network to bridged: There are no un-bridged host network adapters Other VMware connections do not appear in the network connections window in the WinXP control panel

At the end of the installation I get an error: Setup failed to generate the SSL keys necessary to run VMware Server. Click OK to cancel this installation.

I'm not using OCAPI, I patched a few binaries from VMware to fix the missing APIs. You can get my patched installer here. Do note it needs the Microsoft Internationalized Domain Names Mitigation APIs update, which you can get here.

@Dave-H If you absolutely want to stick with Panda – presumably because you still have a valid licence – then I’d uninstall it completely, give everything a thorough clean, then reinstall it, but without allowing any connection to the internet. Then set the cache folder to read-only for everyone, especially for the System account, or if that doesn’t work, delete it completely. Then set all your exclusions and only then connect to the internet. No updates must be carried out locally. Perhaps it will then run stably. But to be honest, this isn’t of course a good workaround, as it unfortunately results in a loss of functionality. Personally, I’m done with Panda and would only go back if an official fix has been released or the update server has been corrected.

This absolutely confirms what I’ve already said here and what many other customers have reported across the web. At first glance, Panda Support seems great, but on closer inspection it’s a joke. For home users, it’s practically non-existent. They probably focus more on enterprise customers. Money makes the world go round.

Assuming you haven't already uninstalled Panda, could you try excluding from scanning the folders I detailed in my earlier post? I would just be interested to know if this helps the problem on your system. I'm still getting occasional stops and starts of the main Panda service, and I'm trying to find out exactly what is triggering them. Again, not a fix, just a better understanding of where the mechanism is now failing. Incidentally, Panda's online support forms are pretty useless, as once you've submitted one, you are supposed to be able to add new information to it by clicking on the link in the e-mail it sends you. Unfortunately, this doesn't work. When you submit the revised form, you just get an error message that the e-mail and customer number don't match any current user! I've had to submit two further forms from scratch to give them more information.

It remains free but after the period of 60 days, the removal of malware is no longer possible. If you need this feature, you have to buy a license. That's ok for me. I personally do not need this feature.

About panda acting up, same as before, but now crappier: service crashes and even on occasions with no service crashes now sistem also becomes very slow while clicking through start menu, e.g. recent documents. Even doing regular tasks, opening e.g. Task Manager I had to wait around 1 minute before it would open. And get this: panda decided it's king of the system somehow and Diskeeper that I use could not even save fragmentation prevented statistics for the current day. The next day it showed as "---------" (none). Unglaublich! Anyhow, applying their panda-b-gone uninstaller things are finally making sense. P.S.: Regarding this about IOBit Malware fighter Its drivers have win7x86 path, and it just makes AppData/Local/Low directories in XP as if it owns the place. Not applicable. Yes, Comodo can be good, though their HIPS system can be quite heavy (but that is with Comodo Firewall). I used both (AV & FW) in the past. Might test it again... They are advertising all over the place "It's Free" and then when wanting to download, you get hit with the remark "for 60 days" when there is a comparison drawn between the two releases. Disgusting!

It is not NT 6.0 incompatible code as otherwise it wouldn't work no matter which compiler was used. This is likely a compiler issue so for now GCC 15 will be more reliable. The GCC 16 compiler hasn't been changed since the previous working build so I haven't been able to isolate the root cause yet. I will continue looking into it.

... I'm trying somehow to understand, but, as a non-coder, I fail to do so ... Your previous working, FULL, FFplay.exe (32-bit) binary from early June, ffplay version N-124841-gb355200263-WINVISTA Copyright (c) 2003-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 60. 32.100 / 60. 32.100 libavcodec 62. 36.101 / 62. 36.101 libavformat 62. 19.101 / 62. 19.101 libavdevice 62. 4.100 / 62. 4.100 libavfilter 11. 17.100 / 11. 17.100 libswscale 9. 8.100 / 9. 8.100 libswresample 6. 4.100 / 6. 4.100 was compiled with GCC16, was it not ? However, more recent FFplay (32-bit) builds, when again compiled with GCC16, end up exhibiting the crash-y behaviour I have reported so far; have you changed in some aspect the compiler itself (GCC16) since the start of June or are the recent crashes the result of upstream (FFmpeg) new code, that makes the final binary incompatible with NT 6.0 x86? The GCC15.2 compile launches OK here, ffplay version N-125551-ga09be9b91e Copyright (c) 2003-2026 the FFmpeg developers built with gcc 15.2.0 (Rev14, Built by MSYS2 project) configuration: --prefix=/local32 --bindir=/local32/bin-video --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-zlib --enable-sdl2 --enable-gpl --enable-libmp3lame --disable-debug --enable-libfdk-aac --enable-libass --enable-libxml2 --enable-libshine --enable-gnutls --enable-libx264 --enable-libx265 --extra-cflags=-DLIBXML_STATIC libavutil 61. 4.100 / 61. 4.100 libavcodec 63. 6.100 / 63. 6.100 libavformat 63. 4.100 / 63. 4.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 Simple media player usage: ffplay [options] input_file ... and I couldn't help noticing lots of "first-time-to-be-seen" configure flags : --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion As for my audio-only MP4 file, it plays there with NO crashes : So, does this mean it's goodbye GCC16.1 and welcome GCC15.2 ? (OT: the appalling forum's code viewer did push my patience to its limits, while trying to send this comment ; will it ever get fixed?)

@VistaLover I reversed this commit which got partial functionality but GCC 16 is still problematic for 32-bit builds. Here is a smaller build using GCC 15 for you to try. https://files.videohelp.com/u/69760/ffmpeg-8.2-2278-a09be9b91e-static-VISTAx86.7z

Fair enough, just know it was unintended to have any meaning on purpose & you are right about the last part

The crash on the audio file isn't to do with it being tagged, because the crash is still invoked even without a tag (text metadata+cover): Format : MPEG-4 Format profile : Base Media Codec ID : isom (isom/iso2/mp41) File size : 39.6 MiB Duration : 57 min 0 s Overall bit rate mode : Constant Overall bit rate : 97.1 kb/s ContentType : Movie Writing application : Lavf62.6.100 rati : (Binary) Audio ID : 1 Format : AAC LC SBR Format/Info : Advanced Audio Codec Low Complexity with Spectral Band Replication Commercial name : HE-AAC Format settings : Implicit Codec ID : mp4a-40-2 Duration : 57 min 0 s Bit rate mode : Constant Bit rate : 96.0 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 23.438 FPS (2048 SPF) Compression mode : Lossy Stream size : 39.1 MiB (99%) Language : English Default : Yes Alternate group : 1 PS: The same untagged audio file plays OK with the latest n8.2-dev-2237 SHARED FFplay binary for XP:

... Well, I think I spoke too soon ; while, indeed, MP4 media files with h264+aac now don't cause an FFplay crash, a tagged (metadata+cover) MP4 file with audio-only (HE-AACv1) still leads to a crash: The same tagged audio file plays fine with previous FFplay n8.2-dev-1568 (from early June): That file was downloaded from BBC Sounds with yt-dlp (it has now expired); if it's any help, below its MediaInfo log: Format : MPEG-4 Format profile : Base Media Codec ID : isom (isom/iso2/mp41) File size : 39.6 MiB Duration : 57 min 0 s Overall bit rate mode : Constant Overall bit rate : 97.1 kb/s Title : Dance Sounds of the 90s with Vernon Kay, Party Classics With Ultra Naté In The Mix Description : Ultra Naté makes a mix for Vernon's Classic 90s Party. Writing application : Lavf62.6.100 Cover : Yes Cover type : Cover Comment : https://www.bbc.co.uk/programmes/m001yrds LongDescription : Ultra Naté makes a mix for Vernon's Classic 90s Party. Audio ID : 1 Format : AAC LC SBR Format/Info : Advanced Audio Codec Low Complexity with Spectral Band Replication Commercial name : HE-AAC Format settings : Implicit Codec ID : mp4a-40-2 Duration : 57 min 0 s Bit rate mode : Constant Bit rate : 96.0 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 23.438 FPS (2048 SPF) Compression mode : Lossy Stream size : 39.1 MiB (99%) Language : English Default : Yes Alternate group : 1 Image Type : Cover Format : JPEG Muxing mode : moov-meta-covr Width : 1 200 pixels Height : 675 pixels Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Compression mode : Lossy Stream size : 104 KiB (0%) This is turning into a nightmare ; thanks in advance for any insight...

Thanks a lot for recompiling ; I've downloaded and tested the new n8.2-dev-2273 VISTA binaries and can confirm the new FFplay.exe files work as expected : If it's not too much to ask , can you share what the issue was with the previous FFplay offering?

This fixes the issue, now works, thank you.

Well, there "is" political meaning behind it whether intended or not, lol. I see "both sides" of that unintended political meaning. Very strange job market, kind of a "once in a lifetime" type of job market. But definitely depends on your locale and type of career.

ah dont worry it was a joke no political meaning behind it

Actually, I had to look it up. I don't watch "cartoons" (ie, "animated tv series") so your reference was completely foreign. Just seemed "best" to comment on that aspect of your post as opposed to the political nature of the "no job crisis" comment.

lol, someone who gets it haha

I wondered why it said "we", lol Congrats on finding a fix! I honestly was trying to find a hosts-file-only type of fix, but every time I fire up a UXP browser these days has me wanting to pinch my nipples with battery cables. Much LESS pain than the "experience" UXP provides. I really don't know how you guys (without Android backups) "survive" in this day and age.

Yes that is what we believe. I blocked fen.peryuck.com (yuck!), and it is not redirecting me to an error page at this time. So everything seems to work. I only need the mail to activate or log into some account, or refresh a sytes.net domain once a month. The adblocker would have to kill a script that goes inside the main page, which then errors out when ads are blocked, to stop it doing so. Maybe Yahoo didn't properly add it. The Ad-Shield guy talked about "billions" of lost revenue from ads, as if they were some kind of resource harvesting machine. Somehow knowing what my machine properties are through tracker scripts would generate them revenue. Most in capitalism only transfer fake money from one another. We may have saved billions of grams of greenhouse gases from being made by not watching ads.