lievencardoen
28th November 2007 15:53 UTC

CopyFiles to Mapped drive fails
Found strange bug (or I missed something) here. If I map a network path to a drive (let's say Z:\\, then I'm able to create a directory in Z:\\, I'm able to copy files to the root of Z:\\, I can create a file on Z:\\, but when I'm trying to copyfiles to a directory created in Z:\\, then copy fails...

SharedEvaLocation:
            IfFileExists $SharedEvaLocationPath\indiegroup\*.* next CreateIndieGroupFolder
                CreateIndieGroupFolder:   
                    DetailPrint "IndieGroupFolderDoesNotExist --> Creating directory $SharedEvaLocationPath\indiegroup"
                    CreateDirectory $SharedEvaLocationPath\indiegroup
                    Goto next
                next:
                    IfFileExists $SharedEvaLocationPath\indiegroup\eva\applications\${APPLICATIONID}\*.* FinishCopyEvaFolderStructure AppNotRegistered
                        AppNotRegistered:
                            DetailPrint "CopyFiles /SILENT $INSTDIR\indiegroup $SharedEvaLocationPath\indiegroup"
                            CopyFiles $INSTDIR\usermanagement\*.* "$SharedEvaLocationPath"
                            Goto FinishCopyEvaFolderStructure

Very strange and I can't seem to figure out why. Even more strange is that when I use the path to the networklocation (\\server\\...) instead of the mapped network drive, it does work... (really, it makes no sense at all but it's like that).

Thx, Lieven Cardoen, Indie Group

kichik
28th November 2007 22:07 UTC

It's working fine for me with shared drives and I don't see any reason it'd fail just with copying to mapped drives and not with everything else. Have you tried executing a script that just copies a very specific files to that path without any variables? Just CopyFiles "C:\autoexec.bat" "Z:\".

andy11252
22nd January 2008 12:19 UTC

I've also had a similair problem, being unable to create or copy files to the top level of a mapped drive. AllowRootDirInstall has been set true.

It works fine if a UNC is specified, or if a drive letter is assigned to the mapped drive and that is used. It also works if I install to an existing sub-directory on the mapped drive.

I've also tried using the plugin to convert a path to a UNC. However, this also doesn't work for the top level of a mapped drive. (but does for a sub-directory on the mapped drive).

NSIS V2.34
Windows XP SP2

Afrow UK
22nd January 2008 13:09 UTC

For me mapped drives are not active until you access them in Windows Explorer. Not sure if that is the problem.

Stu

andy11252
22nd January 2008 13:20 UTC

Thanks, but no. I already was looking at the mapped drives with explorer.

kichik
26th January 2008 14:25 UTC

It still works fine for me. Attach a minimal example reproducing the issue.