Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/22/2020 in all areas

  1. On the very long run, yes, but we're talking about years... I gotta say though that XP is suffering the lack of support for many things by now and although many things still work for Professional Usage (Avisynth+, x262/x264/x265, ffmpeg, etc) some other don't (recent version of Visual Studio, Photoshop, Premier, AVID Media Composer, Davinci Resolve, Blender, AVID ProTools, Cubase, etc) making it impossible to be used for professional stuff anymore... Even Avisynth+ - which is still supported as a frameserver along with many filters - suffers a pretty bad thing: it doesn't have any updated indexers and without an indexer you cannot create an uncompressed A/V stream to be used inside a frameserver, so... And sure there are workarounds like using ffmpeg to make a lossless mezzanine file with HuffYUV or FFV1 etc but still it's far from being an ideal workflow... Besides, some other lossless codecs like UTVideo dropped XP support entirely along with Windows 7 support, so it's a no go as well. Things are different for a non-professional use of XP, like browsing (we do have updated browsers), watching videos (we do have updated video players like PotPlayer), listening to audio files (PotPlayer again to name one or Foobar 2000 etc), chatting with our friends and relatives (there's Miranda which supports Skype, Facebook, Discord, IRC and other platform, there's Telegram which still works although new version don't work, there's TeamSpeak which works if you use an old version and you connect to an old server and so on). Of course, no one is stopping you from using old version of very well-known programs, however the problem is that bugs will never be fixed and of course nothing new will be supported. For instance, a friend of mine bought the Sony A7III which shoots pictures in 6K HLG HDR. I wanted to edit the raw footages with Photoshop CS4, however I couldn't because it didn't support that camera and the plugin released by Sony didn't work with older version of Photoshop. I couldn't even see them 'cause although Irfan View managed to display them, Windows XP has NO FLIPPING CLUE about what a color curve other than the Linear BT601 and Linear BT709 is, therefore it was totally ignoring both the colormatrix BT2020 and the color curve HLG (Hybrid Log Gamma), thus displaying a gray-ish image. One more example? Well, a friend of mine bought a BlackMagic Cinema Pocket Camera and I wanted to see the videos on my computer, but sadly .braw files can be decoded by the BlackMagic Player only (no MPV, no Media Player Classic, no PotPlayer, no VLC etc) but of course it didn't work on XP as I couldn't install it. Of course the guys from BlackMagic also released an .msi with the codec so that you can use whatever player you like as long as it uses DirectShowSource (like MPC-HC), but again I couldn't install it because it didn't support XP... Long story short: I do like XP, it's something that really matters to me, but it's just a VM on my computer now... I also have a VM with Windows 98SE which is constantly closed and I turn it on once in a while when it's its "birthday", I look at it, I remember the good old days and then I turn it off again. As to XP I do use it, but only as my non-work-related OS. You know, I use it to check Facebook, to go to Doom9, MSFN, to chat with my friends, to listen to music and to help the Avisynth community, but that's pretty much it. For everything else, I have Windows 10 which I use for stuff like Visual Studio, Eclipse, MATLAB and other stuff. As to the main OS which handles the VMs, I'm using Fedora (which is Linux, namely the distro used by Linus Torvald himself and the one that it's a "beta" of the RHEL used by many companies) and I'm quite happy about it. Sure, it's not XP, but at least it's not Windows 10... As a side note, for everyone holding their breaths for One Core API and the modified kernel, just... don't... Sure, the development is going on, we're making progress and it indeed adds some functions/kernel calls that didn't exist on XP before and you can download it, install it and use it even now like I've been doing for quite some time, but if you think that it's going to be a miracle that makes everything run for years to come, including drivers etc... don't... In the foreseeable future, I think .NET Framework 5 will be one of the things that will kill XP and Windows 7.
    1 point
  2. Change is inevitable. Necessary. We have increasing needs for tech. Embracing change is not what this is about. Creating incompatibility to suit business goals is not right. Our parents were appalled at planned obsolescence. Now we're told to accept it. Embrace it. Our tech becomes obsolete even before it can wear out the batteries! Using Fear, Uncertainty, and Doubt in the name of "security" as a way to herd people into doing what they would not do is deplorable! Yet for the most part we find ourselves powerless, because people who predicted this and warned against ceding control were marginalized. Ridiculed. Pushed aside. -Noel P.S., the latest incompatibility I've noticed: RDP from an older system into a Windows 10 v1903 system and your mouse jumps around when the cursor graphic is changed. It didn't do that remoting into v1809. The protocol has been good enough - indeed excellent - for decades. It doesn't have to change. Aero Glass just gets shut off and requires regular reinstalls, even though it works fine. Presumedly because some jerk inside Microsoft wants us NOT customizing our Windows look, because that goes against their current Marketing direction. Who the &%$& do they think they are? We could talk about the atrocities Apple is pushing on people... No more 32 bit programs. No more putting things where you want them on your disk. Can't reach your Documents area even though you've shared it? Oh, right, that's security. P.P.S., I'm typing this on a perfectly good Digital LK250 keyboard circa 1985. And there isn't a better one built today. Stuff doesn't HAVE to go bad just because it's tech.
    1 point
  3. Ok after much testing found I had to mount the "Boot.wim" & change the Lang.ini , committed image & remade the iso working as expected now!
    1 point
×
×
  • Create New...