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.
