I've been using PD10 since it came out - brilliant most of the time.
Until I upgraded to Win10 - then it just wouldn't load. And I got the first of the 'no dll in waterfall procedure' error messages ever.
I thoguht that thsi was just a Win10 compatability issue with PD10 - the lack of start up certainly is, in my view.
However, I've downloaded the trial version of PD14 Ultra with a view to purcahse if it works as well as PD10.
Well, it loads jsut fine, but I'm still getting these infernal 'no dlls...' messages - four or five at a time at total random moments.
Now I've searched the problem and found solutions - but realised that all that I found were related to Win7. Searching for the file locations proved a bit fruitless, and I certainly can't find the suggested dll files that are mentioned either here or Win7 forums.
So I need a Win10 fix for this. I can offer the following to help:
1) Elsewhere, uninstalling GoPro Cine software was blammed for the missign dlls. I've never used it - I do have the current GoPro editing software but it's never been uninstalled and it's a different programme.
2) Problems seem to have occured first time after Win10 upgrade.
3) Can't think of anything that I've uninstalled that would rougley remove the dlls that Cyberlink PD 10 and 14 require.
4) I've only 4MB of ram - I realise that I will need 8mb, whcih I'm prepared to upgrade to if I can get this dll problem sorted first.
5) System is an AMD Phenom II chip at 3.2Ghz, have an LG Blu Ray RW, Radeon HD Graphics card, an older one for sure, but worked fine with PD10, Win10 OS
I had hoped that installing a working demo of PD14 would somehow replace the missign dlls required if they are so needed. Woudl installing the full product rectify the problem??
Does anyone know which dll files are missign and how and where to find/reinstall them?
Any help gratefully appreciated - I have a coupel of video projects to start and need either to upgrade to PD14 with the problem solved before purchase fi possibel.
Many thanks in advance,
Peter
PS, I have mailed the supprot team - first response was to place the blame fair and square on the PC without really telling me how to go about fixing it! Am awaiting a second reaponse, but wondered if anyone here had a Win 10 fix for this old problem! The meek shall inherit the earth, if that's ok with everyone else....