From: rrankin AT primenet DOT com (Rick Rankin)
Subject: RE: starting bash from a .bat or .pif file locks up win95
8 May 1998 04:09:22 -0700
Message-ID: <000001bd7a24$41e0ba20$9a1e01aa.cygnus.gnu-win32@rankin-isdn-ws2.sat.mot.com>
References: <3550e645 DOT 6539656 AT smtp DOT goodnet DOT com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
To: <gnu-win32 AT cygnus DOT com>

FWIW, I start bash from a .bat file all the time on both Win95 and NT. No
problems so far.

Rick

> -----Original Message-----
> From: owner-gnu-win32 AT cygnus DOT com [mailto:owner-gnu-win32 AT cygnus DOT com]On
> Behalf Of Mikey
> Sent: Wednesday, May 06, 1998 12:27 AM
> To: gnu-win32 AT cygnus DOT com
> Subject: starting bash from a .bat or .pif file locks up win95
>
>
> DO NOT START BASH FROM A .BAT FILE !!!	<<<< ----------
> Just discovered 5/5/98
> starting bash from a .bat file gives you a faster console,
> but it gives you the same lockups you get without
> setting CYGWIN32=tty
> always start bash directly from a shortcut (not a .pif file)
> (or manually by double clicking or using BashHere.Inf)
>
> create your shortcut with just
> &Target:	g:\bin\bash.exe	(change drive as appropriate)
> &Start in:	g:\Cygnus\home  (ditto)
> Shortcut &key:	Ctrl + F12 	(or whatever)
> &Run:		Maximized
>
> when doing this you must set your env vars in autoexec.bat
> or .bashrc
>
> =====================================================
> Linux a platform built by, and for users, standing on
> the firm legs of reliability, and speed.
>
> Microsoft Windows, a platform without a leg to stand on.
>
> (jeffdbREMOVETHIS AT goodnet DOT com)
> delete REMOVETHIS from the above to reply
>          Mikey
> -
> 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".
>

-
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".