For more info about WINE with command line than you ever wanted, go to terminal and enter "man wine". "Man" is short for "manual". Lots of terminal programs have a "man page". You could do "man modprobe" or "man mount" or "man sudo", etc. This is assuming you're in Linux. But yeah, quotes are a pain. There's a lot of funny command line stuff out there. Should it be a single quote or a double quote? Can I use quotes, or do I have to rename all the folders in the path to have underscores instead of spaces? What about the funny "/%20" gibberish? In fact, some command line programs ARE SO BAD that you ACTUALLY have to "CD" EACH LEVEL TO WHERE YOU WANT TO GO!! Chntpw used to be that way. If you wanted to get to HKLM\Software\Microsoft\Windows\CurrentVersion\Run , you had to "cd" to "Software", then cd to "Microsoft", then ... Then there's forward slashes vs backslashes vs double backslashes. Windows command prompt is NOT caps-sensitive and terminals ARE caps-sensitive. But running WINE through terminal is useful for debug outputs and for running a program in a certain prefix. Prefixes lets you keep separate virtual "WINE C Drives". Just do "WINEPREFIX=[path to prefix folder] wine [path to program]" and it is ran in that prefix. The default prefix (the one wine uses when you don't specify one) is the .wine folder in your home folder. It's hidden, so you can't see it with Nautilus until you do a Ctrl+h. Every time you want to run a program in a prefix other than .wine, you have to specify the prefix in commandline. If you forget to specify even once, it will be ran in the default prefix. Fortunately, you can make launchers to do this for you. When things get extreme, there's even special WINE debug parameters you can tack on in command line and have WINE output to a text file according to the parameters you added. You don't HAVE to specify a debug parameter to get a "debug log", it's just a more advanced option when a plain debug log isn't good enough. Cheers, Jake
