Pages: [1]   Go Down

Author Topic: Can't run ColorEyes Display Pro's precalibration!  (Read 3468 times)

PCguru

  • Newbie
  • *
  • Offline Offline
  • Posts: 7
Can't run ColorEyes Display Pro's precalibration!
« on: June 20, 2007, 01:50:46 pm »

I cannot get ColorEyes Display Pro to precalibrate on my system:

Windows XP Pro
motherboard: A8N-SLI Premium
AMD Athlon 64 X2 3800+ 2.0GHz Socket 939 Processor
2GB Corsair RAM
two HP w2207 monitors
nVidia nForce SLI chipset
nVidia 7800GTX graphics card.

Once I am through filling in the Application Setup and Hardware Setup, I am ready to proceed with all green lights to the Monitor Pre-Calibration section.  When I click on Precalibration from the Hardware Setup's Black Point prompt, the program hangs, using 50% CPU in Task Manager, dropping to 44-48% after about 15 minutes, and then hanging there indefinitely.  It will not proceed.  

I've also tried just going into the Monitor Pre-Calibration area manually and clicking on Set Monitor White.  When I do that, the whole control panel goes white and the system hangs at 50% CPU usage indefinitely.  It will not proceed here either.

I have tried the software on my Sony Vaio laptop and it worked amazingly well (Pentium M processor with Windows XP Home).. even the activation of the calibration sensor only took 2 seconds whereas my Athlon system takes about 30 seconds.  

I'm wondering if this software is not compatible with the AMD Athlon 64 X2 3800+ 2.0GHz Socket 939 Processor.  Is there anyone else out there that runs the program successfully with that processor or with the nVidia nForce SLI chipset?  I really need to get this working in my print lab.
Logged

Scott Martin

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1315
    • Onsight
Can't run ColorEyes Display Pro's precalibration!
« Reply #1 on: June 20, 2007, 04:06:13 pm »

Debugging Windows software for a bajillion different PC configurations is a big task but your feedback is exactly the kind of thing that ICS and integreated-color wants to here. Send your message to jack@integrated-color.com
Logged
Scott Martin
www.on-sight.com

PCguru

  • Newbie
  • *
  • Offline Offline
  • Posts: 7
Can't run ColorEyes Display Pro's precalibration!
« Reply #2 on: June 20, 2007, 04:30:25 pm »

Quote
Debugging Windows software for a bajillion different PC configurations is a big task but your feedback is exactly the kind of thing that ICS and integreated-color wants to here. Send your message to jack@integrated-color.com
[a href=\"index.php?act=findpost&pid=123999\"][{POST_SNAPBACK}][/a]

I've actually done a log (see below) and sent it to Jack but I'm not getting a response.  Maybe they're busy but I need to get my setup running so that's why I'm posting here.  Sorry I forgot to post the log.  

00000000   0.00000000   [1028] QPixmap::fromMimeSource: Cannot find pixmap "loading.png" in the mime source factory   
00000001   0.03279132   [1028] DDC_Init   
00000002   0.05218345   [1028] Profile path =    
00000003   0.05220887   [1028] C:\WINDOWS\System32\spool\DRIVERS\COLOR\sRGB Color Space Profile.icm   
00000004   0.05222926   [1028]    
00000005   0.27208263   [1028] QObject::connect: No such slot MainForm::mMonitorListMenuSelection(int)   
00000006   0.27210554   [1028] QObject::connect:  (sender name:   'unnamed')   
00000007   0.27213180   [1028] QObject::connect:  (receiver name: 'MainForm')   
00000008   0.27216643   [1028] QObject::connect: No such slot MainForm::mMonitorChanged()   
00000009   0.27219325   [1028] QObject::connect:  (sender name:   'unnamed')   
00000010   0.27223989   [1028] QObject::connect:  (receiver name: 'MainForm')   
00000011   0.29082328   [1028] Reloading Profile...   
00000012   0.47615325   [1028] Profile path =    
00000013   0.47617894   [1028] C:\WINDOWS\System32\spool\DRIVERS\COLOR\sRGB Color Space Profile.icm   
00000014   0.47620103   [1028]    
00000015   0.66770077   [1028] QObject::connect: No such slot MainForm::mMonitorListMenuSelection(int)   
00000016   0.66772622   [1028] QObject::connect:  (sender name:   'unnamed')   
00000017   0.66777289   [1028] QObject::connect:  (receiver name: 'MainForm')   
00000018   0.66780639   [1028] QObject::connect: No such slot MainForm::mMonitorChanged()   
00000019   0.66783291   [1028] QObject::connect:  (sender name:   'unnamed')   
00000020   0.66785836   [1028] QObject::connect:  (receiver name: 'MainForm')   
00000021   0.68600619   [1028] Reloading Profile...   
00000022   1.86186016   [1028] Instrument Set to LCD mode:     
00000023   1.86220455   [1028] SKIPPED (Unchanged)   
00000024   26.64067078   [1028] QObject::connect: No such slot MainForm::mMonitorListMenuSelection(int)   
00000025   26.64069748   [1028] QObject::connect:  (sender name:   'unnamed')   
00000026   26.64072227   [1028] QObject::connect:  (receiver name: 'MainForm')   
00000027   26.64075279   [1028] QObject::connect: No such slot MainForm::mMonitorChanged()   
00000028   26.64077568   [1028] QObject::connect:  (sender name:   'unnamed')   
00000029   26.64079857   [1028] QObject::connect:  (receiver name: 'MainForm')   
00000030   51.12500000   [1028] Instrument Set to LCD mode:     
00000031   51.12504959   [1028] DONE   
00000032   63.68358994   [1028] ##########  calibrateInstrument (start)   
00000033   63.68363953   [1028] ##########  calibrateInstrument (set aperture LCD)   


The line that says DONE is when the sensor has been activated.  The next two lines at the end are where the freeze happens when clicking Set Monitor White.

I honestly don't see what something like this would do to help debug the problem.. unless one knows the right order of processes that should be seen.  If that's the case, I'm at their mercy.
Logged

PCguru

  • Newbie
  • *
  • Offline Offline
  • Posts: 7
Can't run ColorEyes Display Pro's precalibration!
« Reply #3 on: June 22, 2007, 03:52:36 pm »

I've experimented turning off just about everything other than system drivers with no luck still.  I've even disconnected my audio workstation hardware and Saitek Eclipse Ii keyboard.  The only thing I haven't tried yet was disconncting my Logitech G7 mouse.  That can't cause an issue, could it?
Logged
Pages: [1]   Go Up