Creating Folder in Private Path

[gailu]

Hi Experts,

Is it possible to create a folder in application's private path?

I am getting KErrAccessDenied (i.e. -21) on 3rd ed FP1. So answers seems to be No but just wanted to make sure that I am not doing something wrong in my code.



My Code

TBuf< KMaxPath > pathWithoutDrive;
TBuf< KMaxPath > driveAndPath;
TBuf< 2 > appDrive;

RFs fsSession;
User::LeaveIfError(fsSession.Connect());
CleanupClosePushL(fsSession);


// Private Path Without Drive
fsSession.PrivatePath( pathWithoutDrive );

// Extract drive letter into appDrive:
appDrive.Copy(Application()->AppFullName().Left(2));

// Combine drive letter and private path
driveAndPath.Copy(appDrive);
driveAndPath.Append(pathWithoutDrive);
driveAndPath.Append(_L("MyFolder"));

BaflUtils::EnsurePathExistsL(fsSession,driveAndPath); (Error Here. I checked driveAndPath in debugger and that is OK. However drive letter is z: on emulator)

CleanupStack::PopAndDestroy(&fsSession);

Best Regards
Gailu

[xhsoldier]

you need to have enough capability to do that: AllFiles

or have the certain secure ID for some certain folder.

[stichbury]

xhsoldier, that's not quite correct. If you call PrivatePath() you get your *own* process's private folder, and it's perfectly fine for you to write into that without AllFiles.

The reason, I think, you're getting KErrAccessDenied, is that you're trying to write to the Z drive - aren't you? That's the ROM drive on hardware, and cannot be written to. Although you're running on emulator, behavior is the same - you'll get an error.

If you try writing to C instead, it should be OK (though the folder has to exist.

[xhsoldier]

Oh, I did not notice the PrivatePath().

xhsoldier, that's not quite correct. If you call PrivatePath() you get your *own* process's private folder, and it's perfectly fine for you to write into that without AllFiles.

The reason, I think, you're getting KErrAccessDenied, is that you're trying to write to the Z drive - aren't you? That's the ROM drive on hardware, and cannot be written to. Although you're running on emulator, behavior is the same - you'll get an error.

If you try writing to C instead, it should be OK (though the folder has to exist.

[gailu]

Hi Stichbury,

Thanks for your response. Yes z: might be a problem that's the reason I highlighted that fact in Red.

The problem is that user may install application on internal drive C: and on external memory. So instead of hardcoding drive name I followed example at
http://wiki.forum.nokia.com/index.ph...vate_directory

i.e.

Application()->AppFullName().Left(2)

Does this means that my application is installed on ROM (at least from emulator perspective)?

[stichbury]

Does this means that my application is installed on ROM (at least from emulator perspective)?

Yes, if that's what FullName() is returning on the emulator build. I typically use #ifdef __WINS__ to write separate code that hard codes the location to C: for emulator, and then code as you were doing already for hardware builds, since you'll never be able to install to Z

[petrib]

On the device, if the application is installed in phone memory, it is the C-drive, and for the application, its own private subdirectory is writable.

If the application is installed on mass memory or a memory card (E-drive), then its private subdirectory is still writable on the E-drive, and I should think it can also create and write to a corresponding private subdirectory also on C.

The applization will not be on the Z-drive/ROM on the actual device (unless Nokia puts it there as part of the firmware), or the emulator.

[wizard_hu_]

A side-note: I am not sure about Bafl::EnsurePathExistL, but generally Symbian treats the filename portion preceding the last backslash character as "directory path", and the remaining part (if any) is strictly the name of a file (not a directory). So if you encounter problems try _L("MyFolder\\").

[stichbury]

The applization will not be on the Z-drive/ROM on the actual device (unless Nokia puts it there as part of the firmware), or the emulator.

If you put

TFileName filename = Application()->AppFullName();

into an application and run it on the emulator, it returns a filename which includes the Z drive. On the emulator, executables are considered to be part of ROM even if they're created by us, third party developers, and not part of Avkon or Symbian OS.

I imagine that if you knock up a SIS file for WINSCW and 'install' to the emulator, it will 'install' to C. But for simple development purposes it's easier to assume that the drive reported by AppFullName() is bogus on emulator builds, and hard code it instead.

[gailu]

Hi Stichbury/Petrib,

I would like to thank for explaining the details. It was really worth asking doubt and not taking assumptions (I was assuming that its not possible).

Hi Wizard_hu,
You are right, EnsurePathExitL does not create folder unless back slash are provided. Thanks for pointing out.


Best Regards,
Gailu