Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Problem with files on a non C:-drive

Simon721
We have a strange behaviour with the new 5.0.1 version (PRO-license). When the files are stored on a drive other than C: (might be local D: or a USB-attached disk), we cannot alter the files. Once we copy them to the C: drive, everything is o.k., we can edit an alter them.

Strange enough, this is the case only for files from our older backs (P25, P45, P45+) and our Nikon-files, but NOT for the P65+ files. It means we can alter P65+ - files on EVERY drive.

Any suggestions? Slowly, we are running out of space on our C: drives 😂

Best regards
Simon

Forgot to mention: Windows 7 64bit
0

Comments

5 comments

Date Votes
  • Paul Steunebrink
    Maybe you have a new computer or did a fresh installation. Anyway, two possible causes I can think of:
    - the files or their folders have the read-only attribute set; this often happens when they are restored from media like DVDs
    - the logged on user does not have full control permission to the drive, folder or files
    0
  • Drew Altdo
    Simon,
    Out of curiosity is your P65+ file format EIP rather than TIF or IIQ?
    If permissions are not correct for the drive or files then the result will be exactly what you are seeing. The files are there but cannot be changed.
    0
  • Simon721
    Paul, Drew

    Thanks to you both for the suggestions. First of all, the read-only flag was not set. And only some of the P65+ files are in EIP-format, but I don't have problems with them, but with older files.

    I've tested little bit around over the weekend, and it seems like the problem indeed is inside the permissions. We have some USB-disks, which we attach to various computers. We don't use a network with an active directory, so all of the computers are stand-alone machines, but we use same user names and pw on all of them. All users have administrator privileges, they belong to the Windows administrators group. Anyway, when a file or whole directory is copied to a disk, it gets some attributes like owner and other permissions, but the owner is not visible (or visible as an unknown account) on a different computer, although the same account (by name and pw) exists. Even granting public permission (everyone, full control) is not transferable among different computers. But the group permission (administrators) is transferred! I suppose the problematic files were copies from a different computer to that disks, therefore I can't change them from an other computer.

    What I've found out is: C1 only allows to change a file if the user is the owner, or he has direct permission (by user name, NOT as a member of a group), or the file has full control for "everyone", but C1 does NOT allow to change it when permission is granted indirectly over the group (administrators). To be honest, my technical knowledge about OS is poor, so I don't know if this is a problem of C1 or Windows, or if it's simply a matter of fact. It's easy to overcome the problem if I grant permission to a whole directory for myself as a user (what I can do, because my user belongs to the administrators group), or I simply copy the file, what grants me the ownership on the copy.

    Therefore, probably my P65+ and other Pxx's analysis was wrong, maybe it's simply because the older files were copied to the disk from different computers. For the moment I have the solution to go on with my work, but if you know something more, please let me know.

    Thanks and best regards
    Simon
    0
  • Paul Steunebrink
    Simon,
    Some background information regarding Windows user accounts might help you understand the issue. When you have multiple Windows computer in a workgroup (i.e. not in a domain, you mentioned Active Directory already) each has its own security database for users and that is were access permissions rely on. Despite having the same user account name on different computers, each account is unique in its security identifier (SID). It is the SID permissions are assigned to, not the name we see. Hence, you should assign permissions on a portable disk for each account separately.

    This way it becomes messy and unmanageable.

    Solutions for this are that you either use a file system on the portable drive without security layer (FAT32 instead of NTFS). Not attractive with current larger disks. Or you access the disk through the network, not directly attached. Network access within the Windows technology works different permission wise than direct attached storage. And of course a server with Active Directory is the most streamlined and controlled solution because an Active Directory domain is a single security database. You can put users in a group, assign permissions to that group and access resources from every computer in the domain.
    0
  • Simon721
    Paul, thank you very much for your reply. We will think about how to do that. With our spreaded infrastructure, a 100TBit/s Internet connection would help very much 😂
    Best regards, Simon
    0

Post is closed for comments.