- This topic has 25 replies, 12 voices, and was last updated 2 months, 2 weeks ago by
.
-
Posts
-
Hello.
Suddenly this error started happening.
I tried uninstalling all X-rite parts including removing traces with Revo Uninstaller. Did the same thing with Display Cal but not help.
Tried moving the Argyii folder to program files…did not help.
Not sure what is going on.Windows 10 64bits
18:43:55,204 Calibrate & profile
18:43:56,470 Detecting output levels range…
18:43:56,479 ——————————————————————————–
18:43:56,479 Session log: 0_16
18:43:56,479
18:43:56,480 Working directory:
18:43:56,480 c:\
18:43:56,480 users\
18:43:56,480 gabym\
18:43:56,482 appdata\
18:43:56,482 local\
18:43:56,483 temp\
18:43:56,483 DisplayCAL-4q1nsc\
18:43:56,483
18:43:56,484 Command line:
18:43:56,484 C:\Users\Gabym\Downloads\Argyll_V2.0.1\bin\dispread.exe
18:43:56,486 -v
18:43:56,486 -k
18:43:56,486 “C:\ProgramData\0install.net\implementations\sha1new=56ed91a0a941bf5094e0a73
18:43:56,486 40d228c195b2549ac\DisplayCAL\linear.cal”
18:43:56,487 -d1
18:43:56,487 -c1
18:43:56,489 -yn
18:43:56,489 “-P0.500165180046,0.500371195249,1.5”
18:43:56,490 -X
18:43:56,490 “i1 DisplayPro, ColorMunki Display & BenQ PD3200U (i1 Pro).ccmx”
18:43:56,490 0_16
18:43:56,490
18:43:57,336 DisplayCAL: Starting interaction with subprocess
18:43:57,338 Number of patches = 3
18:43:57,339 Setting up the instrument
18:43:57,454 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#6&38bad5a9&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 24
18:43:57,454 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#6&38bad5a9&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 24
18:43:57,454 dispread: Error – new_disprd failed with ‘Instrument Access Failed’
18:43:57,456
18:43:57,561 DisplayCAL: Reached EOF (OK)
18:43:57,562 …aborted.Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Hi,
please grab the 2018-08-23 Argyll v2.02b development snapshot (see sticky topic in this forum) and try again, without changing any DisplayCAL settings (other than using the newer Argyll, obviously), then attach the log (it will probably produce a similar failure, but with a different err code which I’m interested in). Thanks.
This? 🙂
17:56:19,369 Calibrate & profile
17:56:20,740 Detecting output levels range…
17:56:20,746 ——————————————————————————–
17:56:20,746 Session log: 0_16
17:56:20,746
17:56:20,746 Working directory:
17:56:20,746 c:\
17:56:20,747 users\
17:56:20,747 gabym\
17:56:20,747 appdata\
17:56:20,749 local\
17:56:20,749 temp\
17:56:20,749 DisplayCAL-wektu1\
17:56:20,750
17:56:20,750 Command line:
17:56:20,750 E:\Argyll_V2.0.2_beta_win32_exe\Argyll_V2.0.2_beta\bin\dispread.exe
17:56:20,752 -v
17:56:20,752 -k
17:56:20,752 “C:\Program Files (x86)\DisplayCAL\linear.cal”
17:56:20,753 -d3
17:56:20,753 -c1
17:56:20,753 -yn
17:56:20,753 “-P0.500165180046,0.500371195249,1.5”
17:56:20,753 -F
17:56:20,755 0_16
17:56:20,755
17:56:21,226 DisplayCAL: Starting interaction with subprocess
17:56:21,227 Number of patches = 3
17:56:21,229 Setting up the instrument
17:56:21,338 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&1aa99e5&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 32
17:56:21,339 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&1aa99e5&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 32
17:56:21,339 dispread: Error – new_disprd failed with ‘Instrument Access Failed’
17:56:21,339
17:56:21,444 DisplayCAL: Reached EOF (OK)
17:56:21,446 …aborted.Yes, thanks. Error 32 is ERROR_SHARING_VIOLATION, i.e. some other process is using the device. Make sure that no other process is accessing your i1D3, uninstall X-Rite devices service if present, and check any other programs that you’re using that might access USB devices. Restarting the system, or un-plugging and re-plugging the instrument may also help.
Yes, thanks. Error 32 is ERROR_SHARING_VIOLATION, i.e. some other process is using the device. Make sure that no other process is accessing your i1D3, uninstall X-Rite devices service if present, and check any other programs that you’re using that might access USB devices. Restarting the system, or un-plugging and re-plugging the instrument may also help.
So frustrating. I uninstalled all x-rite, rebooted, tried all ports (USB2 and 3). Removed any plugged USB device. Still get the error 32 . Not sure how to identify which program can be using it and seriously not sure how any program be using it at this point. :/
I hate having to go back to i1Display softwareNot sure how to identify which program can be using it
Candidates to check are programs that are running in the background that are not part of Windows (e.g. Virus scanners, Firewalls, “Monitoring” programs etc).
Tried shutting everything down. No luck. Guess I will go back to Xrite for the time being. :/
Thanks for helping though 🙂Nope I removed all X-rite software (which in fact was always there and working fine before) but now even with all of it removed and all traces gone, no service showing etc, still get the error. So weird :/
I had this exact error with my ColorMunki Display too. I managed to trace which process was conflicting by checking the System event log for event ID 225. This told me that it was my Gigabyte motherboard LED software (How!? Why!?) – RGBFusion.exe. Once I killed that process, DisplayCal works fine.
I managed to trace which process was conflicting by checking the System event log for event ID 225. This told me that it was my Gigabyte motherboard LED software (How!? Why!?)
Badly written software most likely. Motherboard tools are generally somewhat notorious for their poor quality from a software dev standpoint, probably because they seem to be produced “on the cheap” with not much if anything spent on QA. If such a tool does anything even remotely USB-related, it may happen that it opens but never releases a handle to a generic USB HID device like the i1D3, thus preventing access by other software. I think this may be one of the reasons X-Rite device manager exists: It runs with system privileges and can thus forcefully grab the instrument when the need arises.
I had this exact error with my ColorMunki Display too. I managed to trace which process was conflicting by checking the System event log for event ID 225. This told me that it was my Gigabyte motherboard LED software (How!? Why!?) – RGBFusion.exe. Once I killed that process, DisplayCal works fine.
Confirmed. First uninstall RGBFusion – that didnt help, but then i killed the process AURA – driver for my Gigabyte 2080 and everything was fine.
Thanks for the solution.
You have to turn off several Gigabyte tools for the software to work, like all the RGB, and if you have a Gigabyte video card, like the 2070 Super, the engine for that has to be turned off. Blaming this on Gugabyte and telling us that they are notorious for bad software is a poor excuse. I have over 50 apps, and they all work with Gigabyte, and XRite works just fine with Gibabyte tools. The Displaycal software is poorly written and poorly updated, for 2 years now this has been going on with Displaycal.
Thanks for your input, but the reason that it works with X-Rite is that they use a daemon that grabs the device before anything else can. And you are very clearly not in a position where you can judge the quality of software. If I tell you something is crap, I do not do that out of some hunch, but because I actually have the expertise and insight required to judge these things. So, yes, the Gigabyte software is poorly written, because it should not just grab any unknown USB devices. It is up to them to fix this (probably won’t happen, this crapware is produced a dime a dozen for various vendors and there is exactly zero incentive for them to invest time and money into it).
