On Fri, 17 Jan 2003 10:00:06 +0100 (CET) <[EMAIL PROTECTED]> wrote: > On Fri, 17 Jan 2003, rcc wrote: > > > > I like Xwine > > > > this looks so much nicer > Well than, I can try packaging it. But should wine depend on it and > run it automatically on first start (after the wine-config.pl)?
no, it's more of a frontend than a configuration program. Let it have its own menu entry and when the user starts it and then a winexe through it, wine-config will run. Ah, I see, the user might be tempted to configure wine before running an exe. Hmm, have to think about this. > > suggest splitting out the stuff into yet another package. > Lets keep it like it is, at least untill the release. alright > > Need sleep and there's a new wine package in > > cooker which brutally dumped our thoroughly crafted mdkconf. > > > aha.Didn't see that yet. My cooker install is hopelessly behind. Want > to do a fresh install anyway but lack the time. > > Thierry: any reasons for not applying some of the patches? Also: since it's not Thierry's name that's in the changelog. Guess HA Qu�c-Vi�t <[EMAIL PROTECTED]> got impatient. > > Regarding the native vs fake win question: I use only the fake win, > > so I could well live with a fake win as default. The screenshots at > > codeweavers showed an option to use a fake win in the user's > > homedir. Now, there's an idea... > Think it makes sense? It would require every user to install a new > windows program. Sometimes this makes sense. Sometimes it is a huge > waste of diskspace. I usually (symbolic) link all the files of a > program in a public dir to a subdir in my homedir. The result is that > I can save personal stuff there, but the program files are shared. maybe I'm seeing probs where there aren't any but this [registry] ;These are all booleans. Y/y/T/t/1 are true, N/n/F/f/0 are false. ;Defaults are read all, write to Home makes me think. A native win should have a perfectly working registry. And since wine alledgedly might corrupt win when installing soft through wine, I guess most people will install the soft under native win and only run it in wine. That should give them a sound registry base. Now, as I understand it, installing soft onto the fake wine will not change the global registry but only the user's ; Load Windows registries from the Windows directory "LoadWindowsRegistryFiles" = "Y" ; TRY to write all changes to home registries "WritetoHomeRegistryFiles" = "Y" Assuming that registry changes at install worked, the new registry keys are in the user's reg. Another user can see the files in the fake win but has no access to their reg entries. On multiuser systems we could make it "write changes to windows dir" which we actually don't want to have with native win installations. That registry thing has always been a mystery to me, even in my days as MS user. And I'm not that much into wine to fully understand the implications of the registry settings. - Mark
