Get the new PortableApps.com Platform 10.0: Gorgeous themes, a full portable app store and advanced functionality
Announcing the World's Best Flash Drive: The PortableApps.com Companion | Did you see a malware warning on Friday?

Toucan didn't sync - mirror a file that was updated but with the same size

roninu - August 26, 2009 - 2:22pm

I am using Toucan 2.1.2

I noticed that a Word file that I updated didn’t mirrored when I ran the Sync mode.
Trying to investigate I found that in this case even though I changed the Word file it remained in the same size and didn’t sync.
When I forced a massive change in the file, just to force a size change everything was OK.


( categories: )

Sync function different for XP and Vista?

I too have been unable to sync files on my Vista OS PC. I tried it on an XP machine and it worked just fine. Anyone know if there's a difference?

Leo
Toucan 2.1.2

There

is nothing in the code that should do this, were you using different files for yuor tests, there seems to be an issue with some files at the moment.

'...and do the other things, not because they are easy, but because they are hard...' JFK

Sorry

for the delay in replying to this thread, this is a known issue for the current version, I am currently working on it, if you could send me two different files that Toucan thinks are the same I would be most grateful, you could upload them to http://drop.io/toucantest

'...and do the other things, not because they are easy, but because they are hard...' JFK

Sorry

In my case the files include personal information so I cannot upload them.

Ok

no problem Smiling If anyone else can upload a pair of files that exhibit this behaviour I would be most grateful!

'...and do the other things, not because they are easy, but because they are hard...' JFK

I just saw this thread, and

I just saw this thread, and it is related to my post
http://portableapps.com/node/20387#comment-126888.
As I said there I used txt's for testing, but it also happened with mdb (Access) files. However I could NOT reproduce the problem on a local drive, only when syncing over a lan.

Resolved on 2.2.0

Thank you! The problem was resolved on 2.2.0.