What's the difference between clicking an app to run it through my File Browser than running it through a command in the command prompt?
There's two apps that are kind of annoying. Instead of just typing out the command, I have to navigate through to the directories. One of them is Quake II, which I run through wine. When I run it through terminal with
$wine /home/user/.wine/drive_c/Games/Quake_II/quakeII.exeI get an error dialogue that pops up saying "Couldn't load pics/colormap.pcx", and in the terminal, it says "recursive shutdown". But when I do a simple click and run, it runs great (better than it ran when I played it on Windows XP, actually).
On the otherhand, I have a few videos located in my root (i.e. /home/user/ ). They are a bunch of real media (.rm) files. I expected to play them with either mplayer or vlc player with just a click or two. But I have to play them with mplayer through the terminal. Otherwise, when I click through my file browser (which is thunar, by the way), I just get errors within the media players.
What I'm wondering is, what is the difference between running apps through terminal or through a simple point and click? Doesn't either process still access and run the same files? I wonder what the problem is...