What happens if you go to terminal and do: wine winecfg.exe ? Step two would be making sure you succeeded in compiling WINE from source. Go to terminal and do "wine --version". Is this the version you compiled? Next try would be to do this in terminal: cd [path to where you hope you succeeded in compiling WINE] wine --version Does it even output the wine version? If so, is this the version you compiled from source? If you have more than one version of WINE present, make sure you use them with different WINEPREFIXES. Here is an EXCELLENT howto on how to use WINEPREFIXES: http://forum.winehq.org/viewtopic.php?t=2501&highlight= If you use WINEPREFIXES, every time you want to run a program in WINE (except for the possible exception of with one version of wine and one default WINEPREFIX with that one version of WINE), you have to run a program through terminal, or a launcher or something that sets the WINEPREFIX - every time. Please note that I haven't compiled WINE from source, but I have compiled other things from source, and I can say a few things that should apply. The tar.bz2 file is the source code. They like to call those tarballs. Did you succeed in compiling WINE from source? Did you do "make install"? Did you have any other versions of WINE installed at the time you compiled? If you succeeded in compiling WINE from source, but didn't do "make install", you will have to run it out of the folder you compiled it in; it isn't copied over to where Linux looks by default when you tell it to run a program. So if you compiled WINE from source, but didn't do "make install", and had no other versions of WINE present on the system, and went to a new terminal and just entered "wine", it would say that it can't find anything to run called "wine". If you changed the directory of terminal to where you compiled it, and THEN entered "wine", it would output the wine help (default parameter when no other parameters are specified). Doing a "make install", from the directory of where you compiled WINE, copies WINE over to where Linux looks by default to run a program, and then you could just enter "wine" in a new terminal and it would output the wine help. At that point you can delete the folder you compiled wine in. Please note that your package manager is not aware of any program you compiled from source. So you cannot use Synaptic to remove WINE that you compiled. You have to delete it manually. I believe there is a prefix option that lets you say where you want WINE to go after you compile it and do "make install", so that one version of WINE can be in one place, and another version of WINE can be in another place. Don't confuse this with WINEPREFIX, which lets you have different WINE "drive_C + registry" folders, which you will wind up wanting to do, I'm sure. I don't think compiling WINE from source would put all those shortcuts in your main menu, unless "make install" does that. It's possible that you compiled a version of WINE that doesn't have a GUI (for configuration). I just installed Linux Mint 11 64 bit on my computer yesterday and am getting that all set up. Hopefully I can help better by actually having WINE and Linux and being able to test some things. Hey, quick question: If you install WINE through MacPorts, does that make it Port Wine? That last one was a joke, for those that didn't get it. Yeah, I've had this computer for 6 years, and just this year found out it is a 64 bit computer by accident. It came with 32 bit WinXP. When booted in a 32 bit OS, the processor reports itself as 32 bit. So that's what I thought it was. So when I switched to Linux, I installed 32 bit Linux. HardInfo (in Linux) consequently still said "32 bit".
