wine users - Mar 2010 - finding or creating ~/.wine folder (Snow Leopard problem)

So I installed the developer's Wine build on my Snow Leopard after searching
the internet for close to two weeks i finally have a wine build (using the
+universal build) on my hard drive. My only problem is I can't use wine
because my Users/username/.wine folder does not exist, pumps out, wine: chdir to
/Users/elixir/.wine
: No such file or directory
after typing in wine and dragging the .exe file into the terminal.
 
Can someone please tell me how I can either find this .wine folder or how I can
create it with my entire build within the folder?

I know most people would tell me that you need to read the FAQ to figure this
out but I've been reading documentation non-stop and have not found the
answer to my question. Can someone give my eyes a break and let me know how, if
this is even possible, I can finally get a working build on Snow Leopard.

hobbsilla wrote:
> My only problem is I can't use wine because my Users/username/.wine
folder does not exist, pumps out, wine: chdir to /Users/elixir/.wine
> : No such file or directory
> after typing in wine and dragging the .exe file into the terminal.
> 

~/.wine doesn't get created until you run Wine the first time. Typing
wineboot at the command prompt will do it. Or you could just install an app;
Wine will automatically create ~/.wine if it doesn't exist.

Thanks for the response but i still got the same response. I also have the
Winebottler combo installed and it has its own directory should i uninstall
Winebottler and sudo rm -rf its directory to see if it will work?

hobbsilla <wineforum-user at winehq.org> wrote:
>
>Damn it still gave me the same error message. Snow Leopard makes wine so
much more complicated.
>I used my Macports (the most recent one 1.8.2) in my terminal to install it.
I had to do
>enforce-variants (with +universal at the end) for about 10 or 12 different
items individually
>to finally get the wine-devel to build. Wine is up to date and everything. 
>
This is not a MacPorts issue per-se, but rather a known problem with building 32
bit programs on Snow Leopard.  You did exactly what is needed to build 32 bit
variants.  This is one of the reasons I have not switched from Leopard, as
Leopard builds are 32 bit.
>
>If you know how to do a more "proper" Snow Leopard install can I
get a link? I've gone to 5
>different sites/blog posts attempting to explain it. There is very limited
documentation on
>this from what I can gather.
>
You stated you have WineBottler.  The builds for it are done on Leopard (maybe
even Tiger) and are completely 32 bit and require no external programs.

The only other suggestion is to completely remove WineBottler AND MacPorts Wine
and rebuild Wine from MacPorts with the +universal variant.

As to why your .wine is not working, I suggest looking at WineBottler first to
see if the bottle exists in it.  If it does, delete it from there and then
attempt to run

wine winecfg from terminal to see if the bottle will be recreated.  In my
testing with WineBottler, no Wine bottle was corrupted using it.

Hopefully, this will fix the problem.

James McKenzie
>
>
>
>

Oh I figured out what I did wrong. My Macports were installed correctly. I'm
currently rebuilding my build and everything has been going smoothly with no
error messages. I think it will work now.

Oh thank you James! Its working now. I'll just have it on my Desktop instead
just so long as a I get access to it. I assume if I wanted to I could rename and
possible put it in my home directory and change the prefix at a later time
correct?

I went to Disk Utility and verified and repaired disc permissions. I went to Get
Info on my home directory (named elixir). It shows elixir(Me) as having
read&write permissions and staff and everyone else as having read only
permissions. I unlocked my settings and locked it. Typed in the command in the
command line and still now luck.

I attempted to copy my winetest folder on my desktop into my home directory and
rename it .wine but it gives me this message that renaming a folder with a
period prefix is only for files "within the system."

It says under my system preferences that I am indeed an admin. On Get Info for
my home directory it says that my username (elixir) which has a parentheses next
to them saying Me that I have read&write permissions. I'm the only user
on this laptop. Should I create a new account or use a guest?

I don't understand how my OS wasn't installed properly, I think the
admin capabilities were deliberately limited by Apple to make it so normal day
people wouldn't go around deleting vital folders on their home directory
preventing them from using their computer. Its sorta frustrating that their
isn't a way to at least create a directory.

by default you cannot name files with a . in front through Finder, you need to
rename it in Terminal... and Finder will not show any file that starts with a .
as that is for marking it as hidden.

do you already have a ~/.wine folder thats locked down because of a sudo run?
you will not be able to see it in Finder if it exists with default settings.

in terminal you can type

Code:
open ~/.wine


and if it opens and shows you the contents of the folder, then you already have
a .wine folder there.  At that point, if it opens you can right click on it and
Get Info to change permissions.... or just use sudo in the Terminal to remove it
if there is nothing you wanted inside of it.

if you try to create a folder in your home, what error message do you get?  Just
go to your home folder in Finder and select to create a new Folder.  You may try
changing the settings to read only, exiting Get Info, then change it back to
read/write.  Also check your whole hard drive for errors, not just permission
problems, in Disk Utility.  If it doesn't let you write to the folder, yet
says you have permission to do it, you may have some really serious problems
going on.

some other questions...
you installed Wine from Macports?  when you type in (no quotes) "which
wine" in Terminal, it should say its in /opt/local/bin ... or its not
trying to use the Macports install at all.  it might have a Wine executable
installed to /usr/bin or elsewhere from some other install you used, thats
pointing to the wrong locations.  if Wine is in /usr/bin (or where ever) from
Macports, try editing it as its a bash script.  You can open to look at it in
TextEdit.app by typing "open -e /usr/bin/wine"  or wherever it is.  If
it opens looking like a bunch of garbage, its a real Wine file, don't change
or save anything.  If its a text bash script, it should have a couple of
lines... need to see what they say.

You are not doing any of this as sudo are you?  not using sudo to run Wine the
first time?  if so its going to create the .wine folder as root, and you wont
have any access to it as your user.  You do need to use sudo when you install
Wine through Macports, but never again.

So I copied and pasted just like you said and it keeps telling me the operation
is not permitted.

You have to be kidding me that is so a problem people that upgrade from 10.5 to
10.6 get. My laptop is brand new came straight from Apple no less than 90 days
ago. Well I'll get MacPilot and work on repairing my ACLs then.

hobbsilla <wineforum-user at winehq.org> wrote:
>
>You have to be kidding me that is so a problem people that upgrade from 10.5
to 10.6 get.
Maybe, maybe not.  Some folks actually 'lost' access to the Documents
folder.
>My laptop is brand new came straight from Apple no less than 90 days ago.
With respect to Ryan, take your Apple to the Genuis Bar and let them fix it.  
Your system is still under warranty (if you bought/use it in the United States)
and they should fix it.  Your system may have a bad Operating System install. 
This happens to Apples as well as other systems.
>Well I'll get MacPilot and work on repairing my ACLs then.
This will void your warranty.  Again, let Apple fix this if your system is still
under warranty.

This may also indicate a failing hard drive, although I would be highly suspect
that this is happening.  They usually fail immediately or after many years of
use (I have the original hard drive for my Thinkpad and it has been dropped a
few times and it is still working after 12+ years.)  A good example of failing
hard drives where the Hitachi 20GB drives used in many computers about 10 to 12
years ago that would 'death spiral' after about three or four months of
use.  They were replaced in many cases after the problem was discovered to be
bad manufacturing.

Ryan:

Thank you for the suggestions.  I'm going to run them tonight to see what I
get out of my system and record them.  This way if my system starts acting
wonky, I can fix it.

James McKenzie

hobbsilla wrote:
> 
> Their isn't any type of terminal command line I can use that forcibly
creates a directory anywhere in my UNIX system that isn't $sudo mkdir
./wine? The wine directory won't make itself on its own in a Guest account
as well.
> 

if you use sudo, it will never make anything with your current user being the
owner, the owner will always be root, and you will not have access to it.

if you want to make a folder (aka directory) you could just mkdir with no sudo. 
If you open terminal (it should show you in your home folder by default on a new
open) and type 'mkdir testfolder' then a new folder should be created
you have access to.

sudo mkdir ./wine   will make a root owned folder from the current folder named
wine, not .wine


hobbsilla wrote:
> 
> I promise you /.wine does not exist on my computer. I searched how to look
for hidden files and .wine simply does not exist anywhere on my computer
especially in the home directory.
> 
I was more interested in what trying to open it said, since searching for hidden
files in finder via spotlight doesn't always find them... it would either
fail saying it doesn't exist, or it would open, and you'd know for sure
really fast.


hobbsilla wrote:
> 
> Again the error message I get whenever I try to run a Wine app (after
closing out of the terminal and reopening it using the method James described)
is the following:
> 
> 
> Code:
> wine ~/path/$appname.exe
> wine: chdir to /Users/elixir/.wine 
> : No such file or directory 
> 
> 
> 
which leads me to believe you have a wine launcher file thats trying to change
folders.. since normal running of wine should never even try to change the
directory to that


hobbsilla wrote:
> 
> I installed Wine using the Macports. I installed the Macports using a .dmg
file that puts it in the default location of /opt/local/etc etc etc.
> 
> When I use the terminal to chdir to /usr/bin, a directory named wine
isn't present, but even more interesting when I type in $which wine in the
terminal it tells me its in /opt/local/bin/wine but when I chdir to that it also
says its [the wine folder] not an existing directory. Does this help at all for
you guys?
> 
you are either not understanding how Wine installs, or your mixing up
directories and files.
/opt/local/bin/wine  is a program, its not a directory, you cannot change
directory to it, of course it will fail.
you can change directory to /opt/local/bin as thats a directory (aka folder),
then type ls and see everything thats in there, one of which is the wine
program.


hobbsilla wrote:
> 
> I am not using sudo for any of these commands (with the exception of $sudo
port install wine-devel back when I was building Wine). I only was using $sudo
mkdir thinking it would forcibly make /.wine in hopes that Wine would finally
work but again, it didn't.
it would make a wine folder sure, but it would be owned by root.


you really need to try to open the wine program with textedit like I said, and
if its a standard text file without gibberish, let us know what it says inside.


Code:
open -e /opt/local/bin/wine


should open the file in TextEdit.app ... if its gibberish (weird symbols and
stuff), just close it without changing or saving anything... if it looks like a
normal bash script.. with probably less than 10 shorter lines of stuff, its a
Wine launcher file, and not the true Wine executable.  I'm pretty sure
Macports still makes a launcher file like that, with probably some lines in
there about DYLD_FALLBACK_LIBRARY_PATH being set to /usr/X11/lib  and other
things.  Just let us know what it says in there, because it sounds like its
trying to change to the .wine folder, which it shouldn't do...

overall if its real Wine being launched, it shouldn't be able to give that
error message... Wine isn't even getting launched to try to create it.