Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3DB323AA.254BDE7C@yahoo.com> Date: Sun, 20 Oct 2002 17:44:10 -0400 From: CBFalconer Reply-To: cbfalconer AT worldnet DOT att DOT net Organization: Ched Research X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Initializing and cygwin.bat Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit As a new user I wanted to customize cygwin.bat to my system, which uses 4dos as the shell and only maintains command.com as an antique. W98 BTW. I found that various commands wouldn't work! The reason was that command.com was being called in the .pif file. I simply changed the .pif to specify "%comspec%" in place of "c:\windows\command.com". Is there any reason setup shouldn't do this in the initial creation? Since the .pif files are of some peculiar structure I had to use explorer and the fursluginner mouse to make this change. -- Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net) Available for consulting/temporary embedded and systems. USE worldnet address! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/