On 24 Oct 2000, Alexandre Julliard wrote:
> Martin Pilka <[EMAIL PROTECTED]> writes:
>
> > thanks for you answer, this could solve the problem. if windows do so,
> > wine probably should copy its behaviour, and "inherit" that key values
> > from .Default/ for every new user.
>
> I'm afraid you cannot simply copy the values, some have to be adapted
> for the current user; for instance on my NT box the programs directory
> is in C:\WINNT\Profiles\<username>\Start Menu\Programs so you need to
> plug the right username in there when setting the key.
Yes. I assume that Windows keeps some sort of list of entries that
must be adapted to each user. Or maybe it's all based on variables like
%SYSTEMDIR% so that it works fine.
> A possible approach suggested by Jeremy White is to specify a user
> setup script in the global configuration. Then when Wine notices that
> the user doesn't have a .wine directory it will launch this script,
> which can copy the registry files from some templates and run a sed
> script on them to fix the necessary things.
We can do it this way. Whether the setup is done by Wine itself (C
code) or by a shell script is transparent for the user anyway. A shell
script may be better because it is more flexible.
Maybe the template should be the file for the .Default key itself.
Then we would replace things like %USERNAME% using sed.
One thing to do is to check what this key actually contains on
Windows 9x and NT. I don't know if it contains user specific paths like
the one you mention. If not then it would be interesting to find out
where these come from (user management, NT policy editor???).
--
Francois Gouget [EMAIL PROTECTED] http://fgouget.free.fr/
Good judgment comes from experience, and experience comes from bad judgment
-- Barry LePatner
