Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Drive letter changed, SyncToy fails RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I sync to an external hard drive, where the usual drive configuration is:

     

    C: D: E: - Local disks

    F: G: - Optical drives

    H: - External drive

     

    SyncToy has worked flawlessly with this setup, synching between D: and the external drive.

     

    I recently had both a flash drive and my hard drive plugged in, which resulted in the hard drive being shifted to I:. Now SyncToy refuses to work.

     

    I understand SyncToy is meant to scan all drives if it can't find the correct files, but I get an error straight away saying the folder pairs can't be found. This happens using both synctoycmd.exe and the GUI.

     

    I don't know if this is a known bug or something particular to my configuration.

     

    I'm running Vista 32-bit SP1, with SyncToy 2.0 Beta.

     

    It appears SyncToy is not working as it should in this situation. Any help much appreciated.

    Friday, May 16, 2008 5:02 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Same for me, I am running it on Windows 2008 Server 64 bit and it works perfectly however the dynamic drive letter assignment doesn't work.
    Even if I run it from the GUI it fails straight away saying it can't find folder pair.
    In my case it doesn't even attempt to find the new drive letter, it just fails instantly, that fast that it wouldn't even of had time to scan for other drives
    Monday, July 7, 2008 7:34 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I think I have a similar problem.

    I have two physical HDs one for XP32 and another for XP64. I have tried to install SyncToy in XP64 but I have this problem:

     

    E:\Document and Settings\Administrator\Desktop\SyncToySetup.exe is not a valid Win32 application

     

    Where 'E' is the HD where I have the operative system.

     

    I am not sure if this is an issues related to 64 bit comptibility.

    Thursday, July 10, 2008 1:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same issue with an external HD. It failed so fast I doubt it had time to scan the drive to see if a matching directory existed. Works fine still if I remap the drive letter.

    Thursday, July 10, 2008 4:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Thanks everyone for reporting the issue. You are correct and we have a bug in the Beta code when trying to detect correct new drive letters. We are working on fixing it for the RTM code.

     

    Thanks

    Deepa

    Wednesday, July 16, 2008 4:02 PM