Your responses don't quite match what I asked you to look for. I don't know
if the differences are unimportant typos on your part or indicate possible
errors in your configuration. So may I suggest that you reply once more,
this time reporting:
1. EXACTLY what the PATH= line says when you check your env (remember, the
"line" may wrap onto 2 or more lines on your screen).
2. EXACTLY what you type when you try to run wine.
2. EXACTLY what the bash error message says (the one you included is missing
spaces that my bash error messages show).
4. EXACTLY what "ls -l |grep wine" returns.
I've explained a bit more below, in reply to parts of your message. Please
understand that these comments aren't attempts to quibble; the discrepancies
between what you reported and what I expected to see may really indicate
problems with your setup.
At 05:51 AM 12/23/98 +0530, Gerard Mascarenhas wrote:
[deleted]
>/.usr/local/bin/wine is in my PATH when I checked with "env "
It shouldn't be. What should be there is "/usr/local/bin", without the "."
and without "/wine".
[deleted]
>I am still getting the message
>bash:wine:command not found
It should read "bash: wine: command not found".
[deleted]
> cd /usr/local/bin
> ls -l | grep wine
when I did the above I get the following
-r-xr-xr-x 1 root root 2055549 Dec 20 12 :53 wine
When I do an ls -l on my system, the result prints with fewer spaces between
the fields. In particular, there should be only 1 space between the
timestamp and "wine", but your report shows 2. This is a longshot, I'll
admit, but might the filename "wine" have gotten into the system as " wine"
somehow?
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
----------------------------------------------------------------
