I've noticed this for awhile, but always just.. put up with it... but I really would like an actual fix. if I call wineprefixcreate, and the wineprefix did not exist at all, it never works right. It starts, and creates 2 of the .reg files, and a windows folder with a system32 folder, and a couple of files, but far from the whole wineprefix, then just ends like its done. if I immediately run wineprefixcreate again right after it gets "done" the first time, then it *usually* finishes the job and creates the whole wineprefix. (usually, a few times I have had to run it 3 or 4 times) I know wineprefixcreate is considered depreciated, but this problem also happens with the default automatic creation. If my prefix doesn't exist and i run something, it always autocreates a ~/.wine just fine, without fail... if I have my wineprefix set to a custom location and not ~/.wine, then it fails just the same as using wineprefixcreate. its really odd... I first noticed it somewhere back in the 1.1.20s and it happens through current versions, on Mac OS X, 10.4, 10.5 and 10.6 .... anyone else played with anything like this much to notice it?
I just discovered... if I write my own script to launch wineprefixcreate... and have it manually create the wineprefix folder, drive_c folder, and dosdevices with the symlinks to drive_c and root... then after that calling wineprefixcreate works fine.... also automatically creating the prefix from just running an app works too after that. Maybe its just something faulty in the creation code on OSX?
> I just discovered... if I write my own script to launch wineprefixcreate... and have it manually create the wineprefix folder, drive_c folder, and dosdevices with the symlinks to drive_c and root... then after that calling wineprefixcreate works fine.... also automatically creating the prefix from just running an app works too after that. Maybe its just something faulty in the creation code on OSX?http://wiki.winehq.org/wineprefixcreate "Note: wineprefixcreate is deprecated and should not be needed anymore." Should all be automatic now, with wineboot taking care of the heavy lifting.
ryan woodsmall wrote:> > http://wiki.winehq.org/wineprefixcreate > > "Note: wineprefixcreate is deprecated and should not be needed anymore." > > Should all be automatic now, with wineboot taking care of the heavy lifting.I said I know its deprecated, but the same problem happens with the automatic too... if it was in wineprefixcreate only, not not with the "automatic" then I wouldn't have worried about it.
doh123 wrote:> I said I know its deprecated, but the same problem happens with the automatic too...You have unmodified, properly compiled Wine? Run this and post terminal output: Code: WINEPREFIX=~/wine-test wine notepad
doh123: What happens when you use the environment variable WINEPREFIX? I used this with wine 1.1.34 to create a testing area for the project I'm working on and it appears to work just fine like this: export WINEPREFIX=$HOME/.wine.testing wine notepad James McKenzie MacOSX 10.5.8 -----Original Message----->From: doh123 <wineforum-user at winehq.org> >Sent: Jan 13, 2010 8:01 PM >To: wine-users at winehq.org >Subject: [Wine] Re: problem with wineprefixcreate... > > >ryan woodsmall wrote: >> >> http://wiki.winehq.org/wineprefixcreate >> >> "Note: wineprefixcreate is deprecated and should not be needed anymore." >> >> Should all be automatic now, with wineboot taking care of the heavy lifting. > > >I said I know its deprecated, but the same problem happens with the automatic too... if it was in wineprefixcreate only, not not with the "automatic" then I wouldn't have worried about it. > > > > >
James Mckenzie wrote:> doh123: > What happens when you use the environment variable WINEPREFIX? >I said I figured it out in the previous post... its I was setting up in a folder that already existed that still had a .update-timestamp file in it.. which was throwing off and having it only partially make what needed to be made. Making it to a new folder, or deleting the .update-timestamp, fixes the problem. I just didn't know that file existed until I started looking a lot closer. I don;t get the love of hidden files with wine... like ~/.wine ... WHY??? why not ~/wine ????and update-timestamp has to be hidden? oh well, at least I know why the prefix wouldn't create right, its just weird that it creates some things, but not everything.