- This topic has 7 replies, 2 voices, and was last updated 8 years ago by
.
-
Posts
-
Not sure what to do next, I’ve uninstalled, reinstalled and the rest. I’ve checked the permissions, run as admin, turned off the smart whatever the name is subsystem, checked the unblock command for Argyll etc
Unfortunately I can’t get displaycal gui to get dispcal to start. I’ve gone through the logs to find the exact strings it is sending to dispcal, and if I throw that into a command window, bingo it pops up. So it does work, and the Argyll driver works in hcfr as well, so I know that is good to go. It is just that it isn’t being called right from displaycal’s gui.
The only thing I’ve been able to find so far is this:
2016-03-19 00:35:27,794 Traceback (most recent call last):
File “DisplayCAL\wexpect.pyc”, line 2501, in __init__
File “DisplayCAL\wexpect.pyc”, line 2586, in initConsole
error: (87, ‘SetConsoleWindowInfo’, ‘The parameter is incorrect.’)which seems a bit strange.
2016-03-19 00:35:27,781 ================================================================================
2016-03-19 00:35:27,783 OEM code page: 437
2016-03-19 00:35:27,786 Console output code page: 437
2016-03-19 00:35:27,788 Setting console output code page to 1252
2016-03-19 00:35:27,790 Console output code page: 1252
2016-03-19 00:35:27,792 Spawning C:\Users\game\Downloads\Argyll_V1.8.3\bin\dispcal.exe -v2 -dweb:8080 -c1 -yn -Iw -ql -t -g2.2 -f1.0 -k0.0 -A4.0 -b “Web 2016-03-19 00-35 2.2 F-S XYZLUT+MTX”that’s the string, it works just fine.
One other part that seems strange, the call seems to time out after 5 seconds . Not sure if it is due to the above error or if 5 seconds isn’t long enough.
2016-03-19 00:27:37,505 Spawning C:\Users\game\Downloads\Argyll_V1.8.3\bin\dispcal.exe -v2 -d1 -c1 -yn “-P0.508225411271,0.546304163127,4.09583333333” -Iw -ql -t -g2.2 -f1.0 -k0.0 -A4.0 -b “#1 2016-03-19 00-26 2.2 F-S LabLUT”
2016-03-19 00:27:37,507 Code page: 1252
2016-03-19 00:27:37,509 “C:\Program Files (x86)\DisplayCAL\lib\python.exe” -S -c “import sys; sys.path = [‘C:\\Program Files (x86)\\DisplayCAL’, ‘C:\\Program Files (x86)\\DisplayCAL\\library.zip’, ‘C:\\Program Files (x86)\\DisplayCAL\\library.zip\\DisplayCAL’, ‘C:\\Program Files (x86)\\DisplayCAL\\lib\\library.zip’, ‘C:\\Program Files (x86)\\DisplayCAL\\lib\\library.zip\\DisplayCAL’] + sys.path;args = [‘C:\\Users\\game\\Downloads\\Argyll_V1.8.3\\bin\\dispcal.exe’, ‘-v2’, ‘-d1’, ‘-c1’, ‘-yn’, ‘-P0.508225411271,0.546304163127,4.09583333333’, ‘-Iw’, ‘-ql’, ‘-t’, ‘-g2.2’, ‘-f1.0’, ‘-k0.0’, ‘-A4.0’, ‘-b’, ‘#1 2016-03-19 00-26 2.2 F-S LabLUT’]; import wexpect;wexpect.ConsoleReader(wexpect.join_args(args), 5156, 10208, cp=1252, c=160, r=None, logdir=’DisplayCAL’)”
2016-03-19 00:27:42,549 Timeout exceeded in Wtty.spawn().2016-03-19 00:30:43,642 ================================================================================
2016-03-19 00:30:43,645 Buffer size: 2000
2016-03-19 00:30:43,647 Timeout: 5sOtherwise all I ever see is : The process C:\Users\game\Downloads\Argyll_V1.8.3\bin\dispcal.exe could not be started.
Any help would be greatly appreciated!
Hi,
please open Windows Registry Editor and go to HKEY_CURRENT_USER\Console. Export the whole “Console” subtree (right click, “Export”), create a ZIP of the exported reg file and attach it. Thanks.
Not to be too annoying, I generally do not cut and past my registry due to microsoft’s weird ability to include critical information in places where it shouldn’t be. Do you have anything specific you are looking for under console? I am very familiar with the registry and regedit, so i should be able to find what we are looking for quickly and easily.
Under console I see three additional sub-keys,
one for cmd.exe, one for 32 bit powershelgl and one for 64 powershell.
Is there a key missing? Specific dwords needed?
I also created a new user, installed the zero install version and tried again. Same issue.
wexpect log shows witty.spawn() timeout error
wexpect exceptions log shows Error: (87, ‘SetConsoleWindowInfo’, ‘The parameter is incorrect.’)
The mentioned registry subkey shouldn’t include any personally identifyable information. It’s where Windows stores the command prompt window configuration (fonts, sizes, colors etc). If you feel unfomfortable attaching to this public forum, you could also send it to me via mail (florian <at> displaycal . net).
This is the underlying error:
2016-03-19 00:35:27,794 Traceback (most recent call last): File “DisplayCAL\wexpect.pyc”, line 2501, in __init__ File “DisplayCAL\wexpect.pyc”, line 2586, in initConsole error: (87, ‘SetConsoleWindowInfo’, ‘The parameter is incorrect.’)
Which seems to indicate that the default console size of 80×25 seems to be too large for your screen (notwithstanding the typical as-generic-and-vacuous-as-it-gets MS error message), which I have a hard time imagining. Try this: http://displaycal.net/temp/DisplayCAL-3.1.2.2-win32.zip
Figured it out based on your description. Using my old “Windows Logic” hat for troubleshooting, I went with the least logical possible thing and it turned out to be right!
I am using DisplayCal with a 65″ tv at 4k. Sounds great, but I sit about 12ft away from it, so I have to scale text up to be able to read it easily. This gives a “some apps may not work right with scaling” message when enabled, and your comment about not having enough room for 80×25 is what triggered the connection. Even though it is obviously FAR from the truth.
If you scale it up 175% or greater, the functions you call are trying to create a console and hitting the issue. If you change the text scaling to 150% or less, the scaling is small enough that the issue is no longer hit. It doesn’t matter that there is more than enough room for far larger than 80×25 on the actual screen, something is broken in the call or in windows related to the combination.
So in the end it is just a microsoftism, but there is probably an updated way to call for a console window that would get around this scaled window issue. I’d throw this down as a KI with a simple workaround for now if you don’t want to get your hands dirty immediately, but I do suspect other HTPC people will have similar issues.
Thanks for the assistance! Running through the calibration process now.
Have you tried the file I linked? Does it fix it? (In theory it shouldn’t be possible that the error occurs with the updated files)
