There's now one FIXME in wineinstall, regarding installing the global
registry. Wanting to fix it, I looked for ways to actually do it. Now, I
could just copy the ~root/.wine/system.reg and ~root/.wine/wine.userreg to
$sysconfdir/wine.systemreg and $sysconfdir/wine.userreg in wineinstall,
but
On Sun, Apr 09, 2000 at 06:24:28PM +0200, Ove Kaaven wrote:
There's now one FIXME in wineinstall, regarding installing the global
registry. Wanting to fix it, I looked for ways to actually do it. Now, I
could just copy the ~root/.wine/system.reg and ~root/.wine/wine.userreg to
On Sat, 8 Apr 2000, Patrik Stridvall wrote:
[...]
The problem with this solution is that it ius "permanenting" the
problem.
[...]
There seems to be a misunderstanding. What I proposed is
strictly a technical replacement to the use of the 'include_next'
statement (for the files
On Sun, 9 Apr 2000, Nathan Roberts wrote:
I read somewhere that VxD's don't work in Windows 2000. Will this make
some parts of Wine's development easier and faster? Or am I totally
wrong on that?
Which Windows 2000?
Microsoft has adopted a new naming scheme to make things
On Sat, 8 Apr 2000, Patrik Stridvall wrote:
[...]
The problem with this solution is that it ius "permanenting" the
problem.
[...]
There seems to be a misunderstanding. What I proposed is
strictly a technical replacement to the use of the 'include_next'
statement (for the
On Sun, 9 Apr 2000, Andreas Mohr wrote:
when root saves the registry:
Why do the symlinks get replaced ?
I assume that is happening because it's the temp file mechanism in the
registry code that is responsible for saving the registry, no ?
And as we don't append to a reg file, but create a
On Sun, Apr 09, 2000 at 10:50:00PM +0200, Ove Kaaven wrote:
On Sun, 9 Apr 2000, Andreas Mohr wrote:
when root saves the registry:
Why do the symlinks get replaced ?
I assume that is happening because it's the temp file mechanism in the
registry code that is responsible for saving the
