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

GerardLakke

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by GerardLakke

  1. Affinity Photo shows colors way too dark. I discovered this when I was experimenting with pixilating paintings of old masters. The screenprint shows the same file next in Windows Photos and Affinity Photo, next to each other. The colors in the left image are really more natural than those in Affinity (I am sure  it is not Windows Photos that shows the colors wrong; I noticed this darkening in Affinity earlier on also with my bare eyes).

    What is wrong? Is this a settings thing? Does the program needs some kind of calibrating?  

    2020-04-24_14-34-06.png

  2. 13 minutes ago, walt.farrell said:

    It's a cloud driver assistant, used at least for OneDrive. I'm not sure if it's used by other cloud functions like Google Drive or Dropbox.

    But rather than mucking about in the registry, you should be able to accomplish the same using commands as I mentioned above. From a command prompt:

    
    sc config cldflt start=disabled
    sc stop cldflt

     

    Tried that suggestion, and then I could start AF without BSOD. But I als had no longer access to files in my OneDrive folders, so that is definitely not an option.

    The fixes that are being mentioned in the posts are not installed on my sytem (??), which is completely oup to date. So deinstalling those isnt posible, and no solution either. 

    Im starting to regret buying AF and AD in de MS Store in a BlackFriday heat of the moment. 

  3. On 12/3/2019 at 5:28 PM, 倪森水 said:

    You can try it ,转发自 Microsoft 社区

    But it did for me.  So the fix is pretty basic - open regedit and look for 

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\CldFlt

    Change the 'Start' entry value from the default value of 2 to 4.

    Reboot your computer.

    Before I change values in the registry and mess up a stable system: what is the function of cldflt.sys? 

  4. On 11/27/2019 at 11:38 AM, HarriK said:

    Thanks for the tip, Scott! Unfortunately, that did not solve my BSOD.

    The crashing point has evolved over time, initially I could not get the Designer even running. Now I get the BSOD when saving (with save as...) a file.

    The Designer store app version has clearly some different code than anywhere else. Many tend to blame Microsoft's updates for the BSOD as other applications have caused BSODs after the update. But who knows... perhaps somewhere exists an open source library that Serif's developers have been using to get the Designer into the MS Store? Other parties may have used that same faulty library causing the problem.

    Serif's responses on this forum have been just shrugging the problem towards Microsoft. I am still waiting for a permanent solution, either from Serif or Microsoft.

    I wonder if has anyone with Surface and MS Store app purchase got the Designer up and running?

    Not me. And I cannot get a refund from the MS store either. 

×
×
  • 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.