Home › Forums › Help and Support › 3.9.14 Version –> dispread.exe error
- This topic has 8 replies, 4 voices, and was last updated 1 year, 4 months ago by
Vincent.
-
AuthorPosts
-
2025-01-30 at 21:56 #142947
Hello,
DisplayCal works correctly in version 3.8.9.3 by disabling some windows RGB leds services.
I have an Xrite I1Display Pro Plus.But with version 3.9.14, I have the error “dispread.exe could not be started” as soon as I start the measurement (capture in attachment)
-> Disabling windows services does nothing.
-> I tried with Argyll_V2.3.1 and Argyll_V3.3.0Do you have any idea?
Thanks
-
This topic was modified 1 year, 5 months ago by
Yamh.
-
This topic was modified 1 year, 5 months ago by
Yamh.
Attachments:
You must be logged in to view attached files.Calibrite Display Plus HL on Amazon Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2025-01-30 at 23:14 #142951It’s good it works ! I had Python 3.12…I went back to 3.11
But new error with this -> CCSS <-
–> Error – Reading CCMX/CCSS File ‘ACER’ failedAttachments:
You must be logged in to view attached files.2025-01-31 at 17:16 #142959Report those issues in his github.
Right now 3.9.14 is meant for Linux and macOS.2025-02-05 at 16:07 #142990Ok thx
It’s done
2025-03-10 at 15:48 #143239
AnonymousInactive- Offline
Hi
I am facing the same problem, did you solve it?
2025-03-20 at 9:34 #143332Same here with dispread.exe and spotread.exe.
Both program runs find in the command line. They can be started.
2025-03-20 at 12:38 #143335Report those issues in his github.
Right now 3.9.14 is meant for Linux and macOS.again…
2025-03-20 at 13:09 #143337Well, back to latest olf official release for Windows. I couldn’t that a mention of that issue on the GitHub.
Anyway, Mac version is working again. Which is really great š.
Cheers.
2025-03-20 at 13:48 #143340Well, back to latest olf official release for Windows. I couldnāt that a mention of that issue on the GitHub.
It is reported in issues tab.
Seems that ther are 2 main issues: whitespace in file paths and execution errors due to installer relying on a preexisting python3 installation, system wide.
Win py3 version work if you handle those limitations which IMHO are not acceptable for , “general public” use, so unless py3 version has a new feature you want, stay with official py2 version. -
This topic was modified 1 year, 5 months ago by
-
AuthorPosts