Page 3 of 3 FirstFirst 123
Results 21 to 23 of 23
  1. #21
    Join Date
    Dec 2011
    Posts
    11

    Default

    I am continuing to have this problem with great frequency when using BC3 to copy directly over the network between Win7 and my Mac Mini. Have you been able to determine anything further about it or can you suggest other things to try?

    I have come up with a temporary, if very unsatisfactory workaround that involves mounting the PC folders via the network on my Mac, then running BC3 under XP in a virtual machine (using VirtualBox). Updates and copies that are not possible from BC3 on the Win7 machine proceed here without difficulty (just as they do in Windows Explorer and in the Mac Finder), but I have to go back through and "touch" every copied file thereafter, since this roundabout way of getting it to work seems to mess up the timestamps.

  2. #22
    Join Date
    Dec 2011
    Posts
    11

    Default

    I continue to have the problem as I previously described it, but I realised at some point that it only seems to affect .doc files. The solution has thus been to open the offending files in Word and then save them as (XML-based) .docx files.

    I don't know if the voodoo (data corruption?) goes away simply because the file has been saved as a fresh one or if it is the XML-based format that somehow makes the difference. In any case, I have so far never had problems copying .docx files.

  3. #23
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,908

    Default

    Hello,

    I've only recently added a Mac Mini to my testing hardware suite. It currently runs 1.8.3, and I enabled sharing in a similar method as you described (Sharing Settings, enabling Samba, and my similarly named user).

    Unfortunately, I'm not seeing the same issues you are running into. The sync seems to work as expected between Windows 7 and the Mini. I also noticed in an earlier screenshot that at least one .docx file was included in your error list. I would guess that it isn't doc vs. docx that is the problem, but once you hit the issue something gets cached and converting the file gets avoids this.

    Are you still running a version of OSX 10.7? Are you testing with the latest BC 3.3.7?

    Are there any other pointers you can think of to help replicate the environment of your sync?
    Aaron P Scooter Software

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •