Question for Windows 7 64 bit users
I just migrated to Windows 7 64 bit from Windows XP 32 bit. Currently running Capture One Pro 6.2.1 64 bit version. Other than setting it up to "run as administrator" are there other gotchas I am unaware of. The 32 bit version ran fine on XP 32 bit.
0
-
You should not 'run as administrator'. CO6-x64 is fully compliant to the Win x64 standard. You install and activate it as administrator and run it as regular user. There are no gotchas for the 64-bit version. 0 -
[quote="Paul_E" wrote:
You should not 'run as administrator'.
You shouldn't have to Paul, but I have to "run as administrator" every time I fire it up, or nothing works - the program opens, but every slider on every panel looks like this:
http://www.capture-the-moment.co.uk/tp/tfu29/upload/cap_one_raa2.jpg
I've just downloaded and reinstalled it - as administrator - again. Same result.0 -
When a user experiences malfunction when running a program and elevating its privileges solves the issue, there are either two possibilities regarding the cause of the malfunction. The common factor is that there is a permissions issue regarding file or object access. Note that in a Windows system with NTFS formatted drive each file and folder, plus all registry keys have a so-called access control list or ACL for short which control who has access and what kind of access a user has.
One option is that the program does not handle properly the user and computer locations at folder, file or registry level. In plain English, a user has in general read but no write permission in the computer locations. Capture One 3 and earlier has (had) this flaw because it stored image (related) files in the program area. You need Power User privileges at least to run the program. Since Capture One 4 this has changed.
The second option is that the ACLs are mixed up in a sense that a user area - where a in general user has write access - is more restricted to read or list access only. The restriction is overcome by elevating the user its privilege or run the process or program with elevate privileges. In the Windows world this occurs quite frequently. In most if not all cases file and folder permissions are the culprit and in a few case the registry is mixed up. Capture One 4, 5 and 6 are fairly sensitive for this scenario because you need write access to the folders with images.
Typical scenarios for options 2
One scenario is when files are store outside the user profile area (you know: My Documents, My Pictures default folders); in a second internal or external disk. By default a non-admin user has not sufficient access for Capture One to alter adjustment files. Hence, Capture One treats the images as read-only.
An alteration of this scenario is when you have for example your images on a D: drive and you run WinXP 32-bits (installed on the C: drive). Now you install Win7 64-bits on your C: drive. Because this is a new (not an in-place or upgrading) installation, the user despite the same name, is a new user with a different SID (secure Identifier) which has no or insufficient access to your images on the D: drive.
An other alternation of this scenario is that you moved your image drive (you had a nice separate drive) to your new (Win7) computer with a user name that is the same as your older computer. Because it is not the same user (different SID), you can not access the images at all or not sufficiently for Capture One.
This could be the case for your computer Keith, but not necessarily. Look in the Library tool at Info (bottom) for permissions.
How to cure?
Most of the time access permissions are inherited from a higher level folder or even the root folder. Change the permissions to 'Change' or 'Modify' for the group of Users and select the options to propagate the change in permissions to files and folders below.
As an alternative you can go the the top folder of your images (which can be sub folder one or a few levels below root), stop permissions inheritance and set the desired permissions as just mentioned.
For Windows 7 users there is also the alternative to move the default My Pictures folder to a new location (extra HDD with more space) because this sets the permission right from the start or add a new folder under the My Pictures Library.0 -
Thanks Keith and Paul. I was experiencing what Keith was experiencing when I first started the 64 bit version in Windows 7.
I think Paul's point about privileges on my image folders is probably right on. Thanks.0 -
[quote="Luke_Miller" wrote:
Thanks Keith and Paul. I was experiencing what Keith was experiencing when I first started the 64 bit version in Windows 7.
I think Paul's point about privileges on my image folders is probably right on. Thanks.
I added some scenarios and solutions (cures) to the post from earlier today.0 -
Yeah, it's a privileges issue, but - really - I don't see why this should matter to Capture One when, on my machine, it doesn't matter to Lightroom 3.
Or Bibble 5.
Or Nama5.
Or Raw Therapee 3.
Or ACDSee.
Or ACR.
Or Photivo.
Or UFRaw.
Or... Well, I'm sure you get the point..!
😉0 -
Problem resolved with a permissions change on the drive where my images are stored. Now I do not have to run Capture One 6 as an administrator. 0 -
[quote="Luke_Miller" wrote:
Problem resolved with a permissions change on the drive where my images are stored. Now I do not have to run Capture One 6 as an administrator.
That's great to hear Luke. Thanks for your feedback.0 -
Thank you, Paul. You have always been very helpful when I have posted questions.
Regards,
Luke0
Post ist für Kommentare geschlossen.
Kommentare
9 Kommentare