linda w (cyg) wrote:
I found creating a shortcut to bash (and calling it 'cygwin') seems to
shortcut the need for using cmd.exe. When I use the provided
'cygwin.bat', I end up with a process tree:
EXPLORER:
CMD.EXE
BASH.EXE
--- makes sense, shell cmd calls bash.exe -- but I noticed this
annoyi
Adrian C. Brown wrote:
Why would I get this error when trying to start cygwin from the
shortcut placed on the desktop?
CMD.EXE was started with '\\coruscant\users\adrianb\Desktop' as the
current directory path. UNC paths are not supported. Defaulting to
Windows directory.
I am usi
Dec 2002 11:02:16 -0800
To: [EMAIL PROTECTED]
Subject: RE: UNC paths are not supported. Defaulting to Windows directory
[and side comment on lists]
Hi, pretty new to the list though have been using cygwin for several months
now, first under win98, and now under XP.
This may have bee
Hi, pretty new to the list though have been using cygwin for several months
now, first under win98, and now under XP.
This may have been covered elsewhere -- sorry, but I
doubt I will have enough time to read all the archives of
all the lists despite what the warnings say a
Adrian C. Brown wrote:
>Why would I get this error when trying to start cygwin from the
>shortcut placed on the desktop?
>
>CMD.EXE was started with '\\coruscant\users\adrianb\Desktop' as the
>current dire ctory path. UNC paths are not supported. Defaulting to
>W
Why would I get this error when trying to start cygwin from the shortcut
placed on the desktop?
CMD.EXE was started with '\\coruscant\users\adrianb\Desktop' as the current
dire
ctory path. UNC paths are not supported. Defaulting to Windows directory.
I am using Windows 2000 profess
6 matches
Mail list logo
