rushcas.blogg.se

If (!SetFileAttributes(dst, fInfo.Home › Fix › Windows 10 › Errors › Save location permission Static bool copyAttributes(const char* src, const char* dst) HANDLE h = CreateFile(filename, GENERIC_WRITE, 0, 0, Static bool setFileTimes(const char* filename, Open a handle to the access token for the calling process. Tp.Privileges.Attributes = SE_PRIVILEGE_ENABLED TOKEN_ADJUST_PRIVILEGES | TOKEN_QUERY, &hToken)) If (!OpenProcessToken(GetCurrentProcess(), If (!LookupPrivilegeValue(NULL, privilege, &luid )) Static bool SetPrivilege(LPCTSTR privilege) The latter will copy the files since i explicitly use backup semantics

Take a look at this program i wrote to see what i mean.Ĭopy1.exe -rw src dst (uses manual read-write copy) it would be nice to have a reg setting to do this for BC. if you have your process acquire admin privileges it works! because the admin can always read the files. I was intriged that "cp" and "cat" can get them and i think they are essentially working as Administrator. so "copy" and "type" cannot even access them. this user is obviously me on my other machine, but since these machines are on totally different networks the internal user GUIDS (or whatever) dont match. I dont really care about the extra "pro" ntfs info, but the rub is that some of the file are owned by another user and home editions cannot access them. the pro/business computer is able to create NTFS information that cannot be overriden by the home computer because home is always in simple file sharing and you can't override the advanced/ownership/permissions because the tab is not there on the file explorer! i think there's some hacky tools you can get to "chown" your stuff on home editions, but i dont really want to be doing this before each and every sync. The problem is down to the fact that one computer is vista business/ultimate or XP pro and the other is XP home or vista home. basically say you want to shuttle data between two computers (eg home & work) and use BC to perform the sync.

I think other users of BC will start to encounter this problem as well if they are doing what i am. thanks for the registry tip, but it turns out this is not to do with replicating ACLs. I've done some digging around to try to get to the bottom of this problem.