wine users - Mar 2012 - Wine refusing to create a configuration directory there

Hello,

I am new on the forum, and apologize in advance if this question  was answered
somewhere else -I looked up, but couldn't find it.

This is NOT an issue with running wine as root; I am NOT trying to do that. Just
so everybody knows!

I am using MacOS 10.7.3 on a late 2011 MacBook Pro, and Wine used to work on it
up until last week (it had been ported from a preceding Snow Leopard machine).

Unfortunately something happened, and I had to reinstall it -and can't. The
install itself works, but wen I try either to winecfg, or to open an .exe file
(same difference, I gather), I get this Terminal message:

MacBook-4:~ pierregervais$ winecfg
wine: '/Users/pierregervais' is not owned by you, refusing to create a
configuration directory there

As you see, I am NOT working under the root shell. However, for some reason the
wine process, which was installed at the root -and from what I read there is no
other way- decides that it is not allowed to write into my Home Directory. Of
course I could sudo evrything, but this would be tantamount to running wine in
root, wouldn't it? And I fully agree with the rule which forbids that.

Install: I tried two ways, first the way I had installed it on Snow Leopard,

http://www.davidbaumgold.com/tutorials/wine-mac/

with the special PATH commands after MacPorts

then a more streamlined way

http://computechtips.com/install-wine-mac-lion

without any PATH terminal fiddling.

Either way ends up in the same mistake. 

All this may be created by a permissions issue on my Mac; I tried reparing
permissions of course, to no avail...

Any help, hint, or pointer would be deeply appreciated. I am not a very compeent
user, and know probably way not enough about the structure of permissions. But
Installing Wine seemed, and was straightforward the first time out, and I
can't figure out what I am doing wrong here!

Pierre Gervais

Good morning, and never mind! One should never take up forum space late at
night. With a few hours' sleep, I was coherent enough to think of checking
Home Directory ownership through BatChmod -and to discover that owner had been
mysteriously set to root instead of username.

When ownership was changed back (replacing root as owner with my username
through BatChmod), there were still a few bugs in the system, but Wine is indeed
up and running. Will reinstall, though, and confirm that the problem is
solved...

Sorry for the wasted space!

PG