Jump to content
You must now use your email address to sign in [click for more info] ×

Phil Friel

New Members
  • Posts

    1
  • Joined

  • Last visited

  1. I have all of my legacy Serif software on the original physical discs, plus all of the serial codes saved in a text file, plus all of the manuals, associated books, etc. I have boxloads of the stuff, virtually every piece of legacy Serif software going right back to Pageplus v1. So I've been with Serif right from the start and bought almost everything that they ever released. I'll never have a problem with reinstalling old Serif software, as long as I have an old Windows computer to run it on. But Jim B has an excellent point. Windows is at version 11 now, and it's only a matter of time before Windows no longer supports Pageplus/Drawplus/Photoplus. It's not a matter of IF but WHEN. What do we do then? The only thing I can see is to permanently keep an old Windows 7 computer running just for the legacy Serif software, but that's simply not a realistic option for the majority of people. There is also the fact that many people have moved on to the Affinity software and have no wish to keep working with old software, but they absolutely still need to use the files produced by the legacy software, preferably in the new Affinity products. I'm in the same boat as many others, with thousands of Pageplus, Drawplus and Photoplus files, and would love some kind of converter or import option to get those files into the Affinity software. We aren't talking about Serif having to actually support the legacy software, just provide an option to import the files from legacy software into the new software. Why have they not done this long ago? Forgive me if this has been answered elsewhere, but I've never seen a clear explanation. Is it a matter of too much trouble/can't be bothered to implement? In which case this doesn't reflect well on Serif's attitude towards long term customers or bode well for the future, if the same situation ever arises again. Or is it a technical/compatibility issue, meaning that it simply can't be done? In which case we'll just have to move on and try to find workarounds. I'd just like to understand the reason(s).
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.