How To Install Staad Pro V8i In Windows 10
Phoebe Sibilio
Hi all, I have been searching this forum and Googling and Github to no avail regarding properly enabling OpenCL in Darktable for the integrated Intel Iris Xe graphics (Alder lake i5 1240P processor with up to date drivers). I am unable to properly enable OpenCL in Darktable 4.0 on Windows, even though I believe this Iris Xe graphics is capable of OpenCL compute.
I found previous threads on this forum, such as this: New install on Windows 11 not working. However, the conclusion from that thread seems like it does not work with Iris Xe graphics? And the compatibility pack from the Windows Store is also not compatible, ironically enough ( -org/darktable/issues/10767). When I installed the compatibility pack from Windows Store, I think it ended up forcing all the OpenCL computation on the CPU rather than GPU, causing my CPU to nearly max out and make the whole thing slow.
I have the alder lake Intel i5-1240P CPU (with Intel Iris Xe graphics and 16 GB RAM). The graphics drivers are all up to date (30.0.101.1743). It is the latest Intel ARC Windows* DCH driver (also compatible with Alder lake CPUs). And the Intel Graphics Command Center says that the OpenCL Runtime Version is 3.0. So, as far as I can tell, this GPU is capable of OpenCL right? So, is it possible to enable it for Darktable or is it just not properly supported yet?
If you can point me to the correct config option in darktablerc to override the blacklisting, that will be great. In the meantime, I plan to recompile darktable on my PC by modifying that blacklist header file to remove the blacklisting on Windows.
I think I got it to work! It looks like there is a bug in the code which makes it not fully respect the opencl_disable_drivers_blacklist=TRUE config parameter. And also I had to delete already registered configurations for my devices from the darktablerc file under the names cldevice_v4_intelririsrxegraphics etc. Then, re-run the darktable-cltest.exe two times for it to compile the kernel modules for my GPU. And now OpenCL works
Note that @wpferguson has been making weekly windows builds of master. It seems not enough windows users have been using them, as bugs are being found post release. Darktable does not have enough windows testers. If you want a better release version, start testing the master builds when we get close to release.
@priort is correct, the code is there in the repo and changes to increase stability on any platform are generally accepted. Windows is a goal as long as someone is there to contribute to it. Most of the developers use Linux and so it runs best there.
I have had to reinstall chief 10 on another computer and am unable to get a driver for the Hasp 2.17 dongle and therefore can't use the program. Is there a new dongle? Please help! I'm using win 10 pro. All of the video's run just fine.
I was able to get my version 10 dongle to install on my laptop but could never get it to install on my desktop (both running Windows 10 pro). I'm not sure what the voodoo magic was but I suspect it was the sequence of installation. You could try to restore your computer to pre-version 10 installation and try to install the dongle first, the version 10.
My solution is to dual boot Windows XP x32 and Windows 10 x64 on separate hard drives. When I need to use antique software like Chief versions 7-10, I boot into XP where they were natively created to run, including their dongles. I have never tried to install antique software in Windows 10.
I have even tried connecting my old hard drives to my newer PC and have been able to access the older programs but they will not run because the HASP/USB dongle is not being recognized by the newer operating system.
I am not able to get the program to recognize my HASP/USB dongle after installing the software drivers from the link to Thales support website above. I have read the support page from CA above as well. I will try asking CA support direct to see if they can help me ?
For those above who got it to work on Windows 10, well done. I am not an IT specialist so I will leave it up to them. I did get X2 working on my windows 10 PC so I will just have to create another layout file to send plans across if I need to.
That was so long ago, I have forgotten. I set it up when I had Windows 7 and it has stayed functional when I upgraded to Windows 10. You should be able to set up what to boot into via your bios. I do recall that I set it up within Windows 7 to offer a boot screen to either boot into Windows 10 or Windows XP, it can't be that hard if I did it without help from a geek. Just do a Google Search for Dual Booting Windows should gain you some useful results, just read more than one help article before you act.