search

AnantLabs / big5sync

Automatically exported from code.google.com/p/big5sync
1 stars 0 forks source link

Recover gracefully if user doesn't have permission to write to C drive #213

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What problem you encounter when using Syncless?
Syncless throws an exception when run syncless in a computer where the user
doesn't have write permission to C drive.  

How do you think we can enhance your user experience?
If C drive is not writable, let the user choose another location?

Original issue reported on code.google.com by dam...@gmail.com on 6 May 2010 at 2:43

GoogleCodeExporter commented 9 years ago 
writing to C is because we need to have a guid in the drive to identify the 
drive =/. I 
am currently looking into a better way to handle this. 

Does the program just hang ?

Original comment by ericnjf on 11 May 2010 at 4:33

GoogleCodeExporter commented 9 years ago 
It throws a syncless exception and quit. This happened in a PC where the user 
did not
have permission to write to "C:\Program files" but had permission to write 
elsewhere
in C drive.

Original comment by dam...@gmail.com on 12 May 2010 at 5:06

GoogleCodeExporter commented 9 years ago 
I have the same issue with a USB drive (let's call it G:) where the root is 
write protected, while the subfolders are not. The drive is NTFS formatted, and 
I cannot sync on it due to Syncless Exception.
The write protection for the root folder G:\ has been set to reduce the risk of 
infection by viruses, so I cannot simply remove the protection.

Original comment by r.dellav...@gmail.com on 3 Aug 2010 at 4:38