Juergen Schmied wrote:
> > I think you are right here too. This is how Windows is supposed to work. If you
>create
> > an account then there are certain things that need to be done before you can use
>it.
> > Hell, that is also how UNIX works, you need to copy /etc/skel to the users homedir
>and do
> > some other things to add the user.
> This is the exact place for wine.userreg.
> How does a mulituser unix system cope with the case that a application is installed,
> files are placed in /etc/skel but users are already created. How are this users
>getting
> the files into their home? Is the app supposed to do this? In this case it would be
>the
> responsibility of wine to create a user.reg in the home directory from /etc/skel
>
> > And actually, they are remade if you delete them when explorer restarts (killed
>explorer,
> > and when it came back they had been recreated).
> Sice we don't have a explorer, whats about a winelib-program what does things like
>this?
> I don't think its good to hard-code such things in wine. It could be executed once
>after
> wine installation and act as a kind of control-panel too.
>
Well actually, I believe it is more specifically Shell32 that does this when you call
SHGetShellFolders or whatever the heck. So as long as the user has run some normal
application that uses that function, then it will be fine.
I think the idea of a winelib program to do this stuff is a good idea too though.
-Dave
