Latest Profile Creator (delivered 5/17/99) 1. Launch Apprunner on clean system (delete Users50\, delete windows\mozregistry.dat prior to running apprunner.exe) 2. Specify the profile directory as c:\NSCP_Profiles\ 3. Create New profile and name it Test1 4. Run MS-Explorer and check the contents of C:\NSCP_Profiles\ Results: The C:\NSCP_Profiles\ directory contains: Cache\ Mail\ News\ Expected: The C:\NSCP_Profiles\ directory should contain a folder called Test1\. The Test1\ directory should then contain Cache\, Mail\, and News\ folders and associated prefs50.js file.

While this may be a user misunderstanding, I think it points out a common interpretation that we'll run into. Any UE input on whether the directory specified should be the directory used or the parent of the directory used? Either way, we should probably make it clearer in the description of this field.

If user defines his/her own profile directory, as specified in the existing Profile Creator UI, the expected result is that the Profile Creator/Manager will create that directory and populate it with the newly created profile and sub-directories and files. I don't think there's user mis-understanding here.

Is this what happened in the 4.5 ? I thought we had a field in the create profile wizard that collects the information about the directory that you want your profile information to live. So is the behavior we looking at.

If needed, we will parallel the request to name the profile directory after the profile anme itself thus allowing bunch of profiles to live under a root directory of user's choice. Moving the target milestone to M8.

If needed, we will parallel the request to name the profile directory after the profile anme itself thus allowing bunch of profiles to live under a root directory of user's choice. Moving the target milestone to M8.

We do this currently with the default profile location. We might just want to do it there. Marking fixed.

build 1999070108 Run Profile Manager from clean system (no Users50 directory or mozregistry.dat) Specify profile (mozprofile), directory=c:\NSCP_Profiles Directory C:\NSCP_Profiles is created with cache, mail,news subdirectories and prefs50.js file Expected a subdirectory called mozprofile - name of profile with appropriate subdirectories as noted when bug created If using default directory (Users50) a directory called mozprofile (or whatever) will be created to hold the cache,news,mail subdirectories. One level of directory is missing when specify other than default directory for profile storage

This requires some new code that isn't in place already. Moving to M9.

Clearing Fixed resolution since this is reopened.

When user provides a directory name in the 'profile directory' field of wizard, the app appends the profile name so as to create to a create a folder specific to that profile. Please follow the Test case given below for more details. Test : 1. Launch Apprunner on clean system (delete Users50\, delete windows\mozregistry.dat prior to running apprunner.exe) 2. Specify the profile directory as c:\NSCP_Profiles\ 3. Create New profile and name it Test1 4. Run MS-Explorer and check the contents of C:\NSCP_Profiles\ Results: The C:\NSCP_Profiles\ directory contains a folder called Test1\. The Test1\ directory contains Cache\, Mail\, and News\ folders and associated prefs50.js file.

build 1999072711

Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.