user profile structure
Moderator: Moderator Team
user profile structure
the current release of reactOS follows the xp style of profiles which, i think, is confusing.
for example there is a user_name\application data and there is a user_name\local settings\application data folder. why is this beneficial? this seems redundant and harder to find/back up data. windows2000 was just fine witha single user_name\application data folder.
what's the benefit of having these two folders?
for example there is a user_name\application data and there is a user_name\local settings\application data folder. why is this beneficial? this seems redundant and harder to find/back up data. windows2000 was just fine witha single user_name\application data folder.
what's the benefit of having these two folders?
pax mei amici amorque et Iesus sacret omnia
This is a windows habit...
I don't know why there are these 2 directories.
I can only say it's the same in windows >=NT5.0
Maybe Reactos is doing so because some third party software installers would get into trouble if the OS string displays "win NT compatible" and one of these directories is missing?
I can only say it's the same in windows >=NT5.0
Maybe Reactos is doing so because some third party software installers would get into trouble if the OS string displays "win NT compatible" and one of these directories is missing?
It has to do with roaming profiles. When on a corporate network, the sysadmin can set your profile to be "roaming". This means it is loaded from a network share during login and written back to the network share during logoff. The advantage of that is that you will have the same profile if you login on a different workstation.
Some files in your profile don't need to be copied back to the network share. "Temporary Internet Files" comes to mind. This stuff is stored under the "Local Settings" subdir.
Some files in your profile don't need to be copied back to the network share. "Temporary Internet Files" comes to mind. This stuff is stored under the "Local Settings" subdir.
I'm fairly sure win2k does have both but I have seen that one of them is definatly hidden (just has the hidden attribute set). I can't comment on NT4 but if it doesn't have the second folder a lot of unnessesery files would bave to be copied for roming profiles, the regestery may list the location of the folder but withought a seperate folder it would have to list each individual file, and i'm sure it doesn't do that (I assume NT4 suported roaming profiles?).
it did support roaming profiles.
you would copy the profile to a server and then you had options like "don't download wallpaper" and so on.
i still believe two "application data" folders is confusing. if it is just about roaming vs. local then the two should be clearly defined.
you would copy the profile to a server and then you had options like "don't download wallpaper" and so on.
i still believe two "application data" folders is confusing. if it is just about roaming vs. local then the two should be clearly defined.
pax mei amici amorque et Iesus sacret omnia
The dreaded wait for loading a roaming profile. Ahhh, the days desktops were 1 gb and the lan connection 4 meg toekn ring...
Seriously, you defined the extent of you roaming profile at the server. You could still used locally unique settings in the same user profile. You could even mix mandatory settings with flexible ones.
Seriously, you defined the extent of you roaming profile at the server. You could still used locally unique settings in the same user profile. You could even mix mandatory settings with flexible ones.
*************************************
Go Huskers!
Go Huskers!
that would be fine if that's how it actually works, local settings would be fine if that's the way it works, it actually puts a single file there and then puts the actual data into user_name\application data.Phalanx wrote:The fact that it is in localsettings is enough. Really, if you are in there, you should know what your doing, or not be there.Floyd wrote:i still believe two "application data" folders is confusing. if it is just about roaming vs. local then the two should be clearly defined.
and i do know what i'm doing--as i have worked with roaming profiles before. whether you're experienced at it or not seeing two 'application data' folders is not wise unless they are very clearly separated. otherwise you're just defending poor design.
pax mei amici amorque et Iesus sacret omnia
It is a good design in many reasons. Take Shareaza for example. You do not want to be sending 600mg iso images back to a server then back to the user's computer. So in this case, the programs does place this in the localsettings folder.Floyd wrote:that would be fine if that's how it actually works, local settings would be fine if that's the way it works, it actually puts a single file there and then puts the actual data into user_name\application data.Phalanx wrote:The fact that it is in localsettings is enough. Really, if you are in there, you should know what your doing, or not be there.Floyd wrote:i still believe two "application data" folders is confusing. if it is just about roaming vs. local then the two should be clearly defined.
and i do know what i'm doing--as i have worked with roaming profiles before. whether you're experienced at it or not seeing two 'application data' folders is not wise unless they are very clearly separated. otherwise you're just defending poor design.
That is a choice of the program developers. However, it is not going to make too much difference. The reason it is place there in this program is the file can range in many sizes (hence why you don't send it over a network). But placing it in a user's area means it is not placed into other user's access (within rights...) . However, these files are not the program's final output, but works in progress. I think they rather people do not mess with them.
not really you still have to copy the profile to a central server. you're not really gaining a whole lot by the bizarre structure of folders (i verified this in my MCSE books).Phalanx wrote: It is a good design in many reasons. Take Shareaza for example. You do not want to be sending 600mg iso images back to a server then back to the user's computer. So in this case, the programs does place this in the localsettings folder.
pax mei amici amorque et Iesus sacret omnia
Who is online
Users browsing this forum: No registered users and 26 guests