Jump to content


  • Content Count

  • Joined

  • Last visited

About simono

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In the meantime we have figuered out where this strange mix of old lamps and new lampes has come from. This laptop was upgraded from Windows 8.1 to Windows 10. The promise given was new lamps for old. At the time, however, quite a lot of new lamps were simply not available and the new Windows did its best to accommodate old drivers. In the aftermath neither Microsoft, Intel nor Driver Easy managed to really rectify the situation. If we would have formatted the disk and installed Windows from scratch last week, the problem would have vanished. But if a user is on a single machine and is th
  2. Hi Mark DDU does resolve the issue. The only problem is that the average user will be scared to death by just looking at the 1980-type user interface with all its options, settings, warnings and disclaimers. If this hadn't been on my "old" system I probably wouldn't have plucked up the courage to start it myself. Having run it - it takes quite a long time - Affinity Photo started normally and even allowed using acceleration. After that, the Intel driver update utility told me to update my graphics driver to Feb 21, which I did. This also took a supiciously long time and had
  3. One can actually see which GPU is being used in the Task Manager.
  4. By the way, according to hearsay Topaz has a problem with GeForce. But Topaz needs Intel anyway because of openVINO. Without the latter, their stuff is too slow on most machines to be of much use. With openVINO - wow! That's why I need to keep Intel in the circuit.
  5. Sure, I realize that I am up against a driver cum Windows bug. However, using Affisity I cannot choose which platform to use - Intel or GeForce. Wondershare Filmora allows me to choose. Topaz Sharpen AI allows me to choose and even provides a "calibrate" to find out which platform is faster. Affinity Photo does not. It just tells me that two platforms happen to be there. However, the user may want to - or even need to - choose which platform to use. I do not even know which platform Affinity is using - which makes debugging driver problems in a mult-platform environment alm
  6. This is off topic, but I do not know how I can otherwise reach out to @Mark Ingram. I am on a new system - see my thread Frequent Bluescreens of Death. The new system is an i7 and has an extra getforce graphics card - i.e. it has two graphics platforms. Affinity Photo 1.9.1 does not allow me to choose the graphics card to be used fyor acceleration. It list the cards as (approx.) "Intel, GetForce" or "GetForce, Intel" depending on various Windows settings. I cannot manually select GetForce. The other programs I have allow me to choose. Wondershare Filmora 10 lists both platf
  7. That's why I included a sysinfo - with the event log. It is not really that probable that there's a hw failure. The only software displaying the problem is Affinity. Filmora along with Topaz Sharpen AI both work perfectly. And here's the appropriate Windows Memory Dump MEMORY.DMP
  8. Having invested infinite amounts of money to migrate to a modern system - my previous system had a bad Intel graphics driver and Affinity Photo had a problem in conjunction with opencl - my new confiiguration keeps getting a bluescreen using Affinity Photo At some time in the middle of every edit the program crashes taking the system with it. I get the infamous Bluescreen followed by an automatic re-boot! When it happens and where it happens is completely unclear. Up to now this has happened at least half a dozen times over the past three or four days. Other programs I am using
  9. Sure, but check dependencies was about the only useful thing I could do. I was hoping that there might be something missing that I could pull in.
  10. So there we have it. The other night a poltergeist came down the chimney and switched off all my file extension displays. Ergo - dependenciesGui.exe.config became dependenciesGui.exe. The real "dependenciesGui.exe" works. However I cannot find anything wrong. Nothing in the DLL hierarchies seems to be missing. In other words, all is well and any malfunction must be a fata morgana. Or at least, not the result of a missing component. To sum it up - all I really know is that all available Intel graphics drivers newer than 2018 do not work for openCL on my (old) machine. This statem
  11. 997 starts up ok. If you try to enable HW acc. in Pref. - note: the checkbox is enabled - you get a message telling the highly estimated user that he, she or it is sitting on a crappy Windows version. 😊 Hmm. Isn't that always the case?
  12. 997 starts up ok. If you try to enable HW acc. in Pref. - note: the checkbox is enabled - you get a message telling the highly estimated user that he, she or it is sitting on a crappy Windows version. 😊 Hmm. Isn't that always the case?
  13. You're right. But I cannot get the new version to run. Visual Basic Express keeps coming up and displaying a config file when I click on dependenciesGui.exe in the unzipped directory.
  14. Here's a new piece of information, for what it's worth. 🙂 Dependancy Walker crashes on cltest.exe. On photo.exe it complains that modules are there, which are neither 32bit nor 64bit and then also crashes. Has to be hard terminated. Running on several DLLs, picked at random, DW produces as expected a load of information. Hmmm. This is funny because DW - IMHO - does not start anything at all. It's just checking entries made by the compiler about external references for the linker/builder.
  15. That's the version that Intel installed. "Latest version". 18.02.21
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.