From: jbanes AT midplains DOT net (theace) Subject: Re: Win95b and long filenames of the /usr mount 3 Jun 1997 11:19:58 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <3393AB20.4840293B.cygnus.gnu-win32@midplains.net> References: <199706021945 DOT MAA03450 AT ultra DOT Franz DOT COM> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------0B9140DC3BCC51C6D2DB6FCD" X-Mailer: Mozilla 4.0b3 [en] (Win95; I) Original-To: Kevin Layer Original-CC: gnu-win32 AT cygnus DOT com X-Priority: 3 (Normal) Original-Sender: owner-gnu-win32 AT cygnus DOT com --------------0B9140DC3BCC51C6D2DB6FCD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kevin Layer wrote: > I don't know if this has been reported yet, but the OSR2 release of > Windows 95 (aka "Windows 95b") doesn't have a DOS that allows long > filenames. This means that until Windows starts you can't put > ...\H-i386-cygwin32\bin in your PATH. This also means you have a > classic chicken and egg problem: if you do it after Windows starts, > then all processes started by the explorer won't inherit the new > PATH. > > Kevin Layer layer AT Franz DOT COM http://www.franz.com/ > > Franz Inc., 1995 University Avenue, Suite 275, Berkeley, CA 94704, > USA > Phone: (510) 548-3600 FAX: (510) 548-8253 > - > For help on using this list (especially unsubscribing), send a > message to > "gnu-win32-request AT cygnus DOT com" with one line of text: "help". The solution is as follows. Don't use Win95 path. Plain and simple. How you ask? If you do a directory command, you will find H-i386-cygwin32 listed as H-i386~1 . So just change it to \H-i386~1\bin\ . Neat huh? jbanes AT midplains DOT net This E-mail is powered by: [Image] --------------0B9140DC3BCC51C6D2DB6FCD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Kevin Layer wrote:
I don't know if this has been reported yet, but the OSR2 release of
Windows 95 (aka "Windows 95b") doesn't have a DOS that allows long
filenames.  This means that until Windows starts you can't put
...\H-i386-cygwin32\bin in your PATH.  This also means you have a
classic chicken and egg problem: if you do it after Windows starts,
then all processes started by the explorer won't inherit the new
PATH.

Kevin Layer             layer AT Franz DOT COM        http://www.franz.com/
Franz Inc., 1995 University Avenue, Suite 275, Berkeley, CA  94704, USA
Phone: (510) 548-3600   FAX: (510) 548-8253
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
   The solution is as follows. Don't use Win95 path. Plain and simple. How you ask? If you do a directory command, you will find H-i386-cygwin32 listed as H-i386~1 <DIR>. So just change it to \H-i386~1\bin\ . Neat huh?

                                jbanes AT midplains DOT net

This E-mail is powered by:
--------------0B9140DC3BCC51C6D2DB6FCD-- - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".