thanks again mate!
thanks again mate!
It was logical. Now we just need to display the MAC version. Thanks.
Mac version most probably won't appear - a dedicated and talented cracker is needed. Just look how many years it took to patch i1 profiler... so I would not count on mac version any time soon. :(
works ok with i1pro2
hmm. i have an i1pro 1. i1 match software recognizes the meter, but the profiler just show "please connect the device"..
Yeah, it does not work with the i1 :(
I have profile maker pro + dongle (print, camera, screen, web, 6 colour etc). Works OSX or PC. I use this for writing profiles for all my flatbed and wideformat printers and all pc/macs connected to em.
Is there anyway this can be emulated to share some love around?
The crack supplied by Bob12345 is for i1profiler v1.2.0
If you have downloaded a later version, uninstall it and download the correct version [URL="http://www.xrite.com/downloader.aspx?FileID=1121&Type=P&returnurl=%2fpr oduct_overview.aspx%3fID%3d1397%26Action%3dsupport %26SoftwareID%3d1121"]here[/URL].
Works fine for me with the i1.
Thanks again to Bob!
nvm... works great... now I just need to find the Mac version! :D
Last edited by mbze430; 05-22-2013 at 12:01 AM.
as stated, if you can find a way to emulate a dongle on mac, I have a full dongle.
Looking for Mac version as well...
Haven't tried calibrating any screens yet.
I did have to play around with the driver to get 1.2 working when I loaded that a few months ago, have you got 1.2 working? Could your drivers be the problem??
Thanks to original uploaders
i found a trick on some website:
"You need to press F8 just when your computer starts to boot to Windows, then push the down error to "Disable Device Driver Signing" or something like that.
For improved security on 64-bit systems, microsoft decided to force all 64--bit drivers be signed with Vista, and now Windows 7. In 32-bit vista, you just get scary prompt the the driver is not signed, but you can select to use it anyway. In 64-bit Vista, you must reboot and press "F8" each time you want to connect a new device that does not have signed drivers. Of course the problem mostly stems from Microsoft's driver verification process. Seems to impact smaller hardware vendors the most. "
Hope it'll help