 |
 |
|
|
 Downloading |
 |
|
Q: I cannot download your ".sit" files.
|
 Licensing and RegistrationFile.txt |
|
|
Q: I unstuffed and put the RegistrationFile.txt within the FoldersSynchronizer folder, just near the application icon. But it still says that it is an unregistered copy. I didn't modify nor rename the RegistrationFile.txt. |
|
| Q: Two days ago I purchased a license for FS and I didn't yet receive my RegistrationFile.txt. What should I do? A: After you pay for a license, Kagi sends you and us simultaneously an email (with the subjects "Thanks For Your Purchase") which confirms the payment has been processed successfully. Then we send you the RegistrationFile.txt, usually within 24 hours from the Kagi's email. 1) If you didn't receive the email from Kagi, it means that your payment has not been accepted for some reason, or they cannot reach your email address (may be you wrote a wrong email address in the order), so please go to the Kagi web site and check for you order. 2) If you received the email from Kagi but you didn't yet receive the RegistrationFile.txt from us within 3 days, most likely we cannot reach your email address from our domain for some (and very rare) technical reason. Or maybe your email box filtered-out our email or rejected it as spam. So please contact us at info@softobe.com and provide us an alternative email address (different domain) to send your registration to. |
|
| Q: When I launch the program, it says "this beta version has expired". Should I pay again? A: No, you don't have to pay again. The Beta version expired. Your RegistrationFile.txt didn't expire. We use to time limit our beta releases because they can contain minor bugs. Simply download the latest final release from our web site and move your RegistrationFile.txt to the new version folder. Final releases never expire. |
|
| Q: I registered and pay for a regular license but I received a time limited RegistrationFile.txt. What does it mean? A: Sometimes (it's rare) we cannot send RegistrationFile.txt to our clients because we are far away from the office, or because we are updating our system, so we automatically send a time limited anonimous RegistrationFile.txt without registering the client to our client database. In few days, at least within one month, always before the registration expires, we send the user the final, never expiring, RegistrationFile.txt. This could happen one or two times a year (for vacations or conferences, for example). When an user receives via email a time limited Registration, the email specifys the date within he will be receiving the final Registration. |
 FoldersSyncronizer 3 |
|
|
Q: I can't run FoldersSynchronizer 3.4.9. I get this warning at any launch: "In order to run this application requires the font Lucida Grande 10pt installed in the system. Cannot run". How to solve this trouble? A: Please download the version 3.6.2. It doesn't require any font. |
|
|
Q: I can't get FoldersSynchronizer 3.6.2 run under Leopard. Any suggestion? A: FS 3.6.2 runs on Leopard very well. And the version 3.6.1 runs on Leopard very well too. |
|
| Q: I have just finished to backup my boot disk, but I cannot set it as boot disk in the System Preference panel. So it seems to be a non bootable disk. Why? A1: Most likely, you executed a Simple Backup and not an Exact Backup. When backing up the boot disk you always have to execute an Exact Backup. The Simple Backup (or only Backup) performs an incremental backup. That is, it copys the new source items to the destination and replaces the old destination items with the most recent source items. But it doesn't delete any item. Let's say you made a first simple backup. It went well. If you now delete a file from the source volume, and execute a simple backup again, you will see that file still existing on the destination volume. So the source and destination volumes will not contain the same files. In case of boot volumes, this condition could make the destination volume non bootable. So you need to perform an Exact Backup. The Exact Backup, more than copying new files and updating the old files (simple backup), deletes from the destination volume all the items not longer existing in the source volume. So at the end of the backup the destination volume will be exactly equal to the source volume. Only in this case the destination volume will be bootable as the source volume. See how to perform a good backup of your boot disk. A2: Most likely, on your destination volume, you forgot to unmark the check-box "Ignore Ownership on this volume" in the Get Info panel of the Finder. If so, please select the destination volume icon in the Finder, call the menu item "Get Info", go to the subpanel "Ownership" then unmark that check-box. It must be always unmarked, even if you are backing up simple files and not the whole boot disk. Then execute the Exact Backup of your boot disk again. Don't apply any Filter nor Exclude system files from the backup. See how to perform a good backup of your boot disk. A3: maybe you backed up your boot disk to a subfolder of your destination disk. If so, this is wrong. You always have to backup your boot disk to the root of the destination disk. |
|
| Q: I use to backup my files to a remote Windows machine, but sometimes FS finds that all the files have been changed, then it backs up all the files again and again. Instead only two files have been really modified and needed to be backed up. Why? A: There is a bug in the Windows OS about the dates. It's a Windows problem. Not a FS problem. Windows changes the files modification date, so FS understands that the file has been modified then it backs up the file again. The following web site reports a detailed documentation and solutions about this Windows bug. Please check http://www.macwindows.com/time.html One of the solutions this web site reports is to unmark the system option "Automatically change the daylight". |
|
| Q: I set source and destination folder on the FS console, but when I try to start a sync, FS tells me "Source folder not defined". I can see that folder in the Finder. Why cannot FS recognize that folder? A1: Most likely you have not enough privileges on that folder. If the Finder can see that folder and FS can't, most likely you logged in on your computer as simple user, you are running FS as root and the folder is located on a remote volume. So, the simple user has the privileges to see that folder in the Finder and the user root (that is FS) has not because of a MacOS X limit on the user root in front of remote volumes. Please see the next FAQ here below. A2: If you are using a version lower than the 3.4.9 version and your folder is located on a remote volume not yet mounted, please go to the Preferences panel and unmark the check-box "Ask Confirmation". The versions lower than version 3.4.9 were not able to auto-mount the volumes because they checked for the folders validity before mounting the volumes. The version 3.4.9 fixed this minor but annoying bug and can mount the volumes even with that check-box on. |
|
|
Q: I need to backup to a remote volume using the "Run as Root" option, but I know this option doesn't work on remote volumes. So, how can I backup my boot volume to a remote volume?
A: Since there is a MacOS X limit on the user root in front of the remote volumes, you should mount the remote volume as FireWire volume. Your computers should be connected by a Fire-Wire cable. Turn on your remote computer holding down the key "T" until a big FireWire icon appears on the remote computer screen. Then you will see the remote volume icon appear on the desktop of your local computer. You can manage these volumes as they are simple local FireWire disk devices directly plugged in your local machine. Then run FS as root and backup your boot disk. The user root can do everything on these volumes. Please read our web page about backing up the boot disk. The theory Run as root means that FS works as you logged in on your computer as user "root". |
|
| Q: I try to drag a folder onto the Multiple list, but FS sometimes doesn't accept the drop. Why? A: It was a bug in the version 3.0.1. In order to drop a folder in the Multiple List or the Exclude List, the version 3.0.1 requires to be the front most application, so if you are using the version 3.0.1 you have to activate FS, then drag your folders. The version 3.2 fixed this bug. Even if FS 3.2 is not the front most application, it accepts the drop. Please keep in mind that you always have to mark the check-box "Multiple On" or "Exclude On" in order to edit these list (including dragging and dropping an item). |
|
| Q: FS tells that it cannot copy some Photoshop plugin file and some other file. A: The version 3.2 fixed this problem. Please download it, move your RegistrationFile.txt to the new version folder, and use it. |
|
| Q: When I launch FS, it says "this beta version has expired". Should I pay again? A: No, you don't have to pay again. The Beta version expired. Your RegistrationFile.txt didn't expire. We use to time limit our beta releases because they can contains minor bugs. Simply download the latest final release from our web site and move your RegistrationFile.txt to the new version folder. Final releases never expire. |
|
| Q: With earlier MacOS X builts prior to Jaguar everything was fine. FS 3.0 was working in the background and I continued with my work flawlessly. However, since Jaguar I have a problem. It is almost impossible to do anything else when a backup is running. It seems to me that FS is taking all the processor´s performance. The same trouble occurs even running on MacOS X 10.2.1. A: FS version 3.0.1 fixes this trouble. It runs on Jaguar properly. |
|
| Q: We are working with FoldersSyncronizer 3.0 on MacOS X 10.2 Jaguar and we ran into an error. WARNING: Cant Copy the File "/ Volumes/ MacHD/Applications/Utilities/Java/Java Web Start.app to:" "G4/Applications/Utilities/Java/Java WebStart.app" Error: Can't Set the attributes to the destination file. Would you skip or continue? A: FS version 3.0.1 fixes this trouble. It runs on Jaguar properly. |
 FoldersSyncronizer 2 |
|
| Q: I'm getting some trouble running FS2 on MacOS X. Why? A: FS version 2.x.x on MacOS X doesn't manage long filenames, unix permissions, multiple forks. Thus it's not indicated to work with the new file formats introduced by MacOS X (like files placed into the MacOS X system folder or files coming from Unix file systems). It runs properly with files you use on MacOS Classic. Please use the version 3 "Cocoa" which works well with long file names, unix permissions, multiple forks, forks > 2 GBytes, Sym Links and GMT modification dates. Moreover this version has some features more, like multiple sessions, filters by filenames (starts, ends, contains, is, is not, doesn't contain), better features on Timers, it can run with root's privileges, can send the Log via email to a custom address, and more. |
|
| Q: FS2 truncates Mac OS X long file names. Any idea? A: Simply the version 2.X.X has not this feature. The version 3.X.X has it. See the previous question. |
|
| Q: FS "forgets" the location of the main folders on the external and remote volumes. Is it a bug? A: Yes, we can't let FS remember the location on remote and external volumes because CarbonLib has a bug regarding the Alias Manager. We notified this to Apple. They verified it's really a bug and assigned the bug number #2690899 against CarbonLib. We hope Apple solves this bug very soon, so we can do the same with FoldersSynchronizer. In the meantime, please, you can use one of these tricks: 1) Make an alias of each source and destination main folder and put them on your boot volume. Then use those aliases as main source and destination folders. FS always resolves the main source and destination aliases, thus you don't have to mark the check-box "Resolve Alias" in the Setting panel (this resolves aliases nested into the main folders). 2) Mount your volumes always in the same order before launching FS. |
|
| Q: If changes are made in both source and destination files, when you sync/backup, will both changes be preserved? A: Yes, you have to mark the check-box "Check Backup Date". This feature is available since the 2.1.2 release. If that check-box is checked, and if since the last Sync/Backup both the files have been modified, FS considers this case as an error, thus it behaves as defined by the "If an error occurred" radio button marked. If you defined "Stop", FS will stop the whole task. If you defined "Skip", FS will not replace the destination file but will skip that single task. If you defined "Ask", FS will show you the "Replace File" dialog. From there you will be able to read the pathnames and the modification dates of the source and destination files, to launch and inspect the source and the destination files with their own application, to open their parent folders in the Finder, and then to choose if "Stop", "Skip" or "Replace" the destination file. If the check-box "Check Backup Date" is unmarked, FS will never check the last Backup Date, thus if the source file has the most recent modification date, it will always replace the destination file. |
|
| Q: I can't figure out how to EXCLUDE the Desktop Folder. A: If you are using the version 2, go to the Exclude area. Click on a cell in the list. You will see the Navigation Services Dialog "Choose Folder". Hold down the OPTION key while selecting the item "Desktop" from the top-right pop-up menu. The Destop Folder will be automatically set in the cell. This is a MacOS feature, not a FS feature. |
|
| Q: I launched the version 2.0 beta but it shows an error message: "... could not be opened because PowerMgrLib (or NameRegistryLib) could not be found". What should I have to do? A: The version 2.0 beta18 fixed these troubles. Please download the latest release from: http://www.softobe.com/products/flsy/pp.html |
|
| Q: I am a v.1.9.6 registered user. The version 2.0 seems to be an unregistered copy. Should I upgrade? If so, how should I upgrade to the version 2? A: Simply going to the http://order.kagi.com/?U3S and paying 10$. You will receive a new RegistrationFile.txt you have to put into the FoldersSynchronizer folder. You can also launch the "Register" application, fill the fields regarding the "FoldersSynchronizerUp1_2", save the Payment to a file and send that file to sales@kagi.com. |
|
| Q: Does FS synchronize single record of my FileMaker file?: A: No. FS can synchronize the entire file only. |
|
| Q: Does FS work well on very large amount of files (e.g. 400.000 files and 16 Gb)?: A: Yes. Sure. FS have no limit to the amount of files or bytes to be copied. Also, FS uses a buffer memory to copy the files one by one, as the Finder used to do. So it never requires you increase the application memory. Increasing the application memory doesn't improve the FS performances. Also, the version 2.0 doesn't work slow longer whether copying a large amount of files. Moreover, the version 2 works at the double speed than the versions 1.X.X |
|
|
Q: When I quit, using the menu OR using cmd-q, the app does not quit until I do a mouse click anywhere on the screen. Strange. Do you have any idea what is causing that? |
