Trying to learn Wine and command lines
-
metalface13
- Newbie
- Posts: 2
- Joined: Thu Jun 30, 2011 6:38 pm
Trying to learn Wine and command lines
Hi, I'm new to Wine and command lines in general and I'm trying to learn how to use it. To start I installed the demo for Armageddon Empires (a seriously awesome game, check it out) and now I'm trying to run it. When I'm in my Wine program files I can see a folder called Cryptic Comet (makers of Armageddon Empires) but when I try to cd or any other command to get to the Cryptic Comet folder it tells me no such files exist. Any help?
-
John Drescher
Trying to learn Wine and command lines
On Thu, Jun 30, 2011 at 7:43 PM, metalface13 <[email protected]> wrote:
John
You probably need to use quotes.Hi, I'm new to Wine and command lines in general and I'm trying to learn how to use it. To start I installed the demo for Armageddon Empires (a seriously awesome game, check it out) and now I'm trying to run it. When I'm in my Wine program files I can see a folder called Cryptic Comet (makers of Armageddon Empires) but when I try to cd or any other command to get to the Cryptic Comet folder it tells me no such files exist. Any help?
John
-
metalface13
- Newbie
- Posts: 2
- Joined: Thu Jun 30, 2011 6:38 pm
-
John Drescher
Trying to learn Wine and command lines
On Thu, Jun 30, 2011 at 9:32 PM, metalface13 <[email protected]> wrote:
is to post a link to a debug log. The instructions are in the Wine
Wiki at http://wiki.winehq.org/FAQ#get_log and post the log file to a
site like pastebin.com and then post the URL here.
--
John M. Drescher
When applications fail to work the best way to allow us to debug thisCool, that worked. Now I'm trying wine ArmageddonEmpires.exe and it's not working.
is to post a link to a debug log. The instructions are in the Wine
Wiki at http://wiki.winehq.org/FAQ#get_log and post the log file to a
site like pastebin.com and then post the URL here.
--
John M. Drescher
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Here's Some More
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
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
