Date: Tue, 3 Jan 2006 17:49:48 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.18-1: Crash launching COMMAND.COM (W98)
Message-ID: <20060103224948.GA15348@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <43b35194 AT wupperonline DOT de> <20051231043720 DOT GC2322 AT trixie DOT casa DOT cgf DOT cx> <43b7d908 AT wupperonline DOT de> <43bafca1 AT wupperonline DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43bafca1@wupperonline.de>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Jan 03, 2006 at 11:38:00PM +0100, Ingo Brueckl wrote:
>In the meantime I could reproduce the bug (which was described the first time
>in http://www.cygwin.com/ml/cygwin/2005-09/msg00058.html and then in
>http://www.cygwin.com/ml/cygwin/2005-12/msg01038.html) on a Windows 98SE PC
>which never had anything to do with cygwin before and where I only copied the
>program launching COMMAND.COM with argument 'dir' and the 20051227 snapshot
>of cygwin1.dll. Same crash. So I suppose it's a bug in the dll.
>
>Cygcheck -s didn't crash this time (as described in
>http://www.cygwin.com/ml/cygwin/2006-01/msg00010.html), it always runs fine
>as long as started from a DOS command line box, but crashes as described if
>started from the bash shell. This is the output from cygcheck -s -v -r, I
>hope it'll help:
>
>  Cygwin Configuration Diagnostics
>  Current System Time: Tue Jan 03 22:43:33 2006
>
>  Windows 98 SE Ver 4.10 Build 2222
>
>  Path: C:\WINDOWS
>        C:\WINDOWS\COMMAND
>
>  SysDir: C:\WINDOWS\SYSTEM
>  WinDir: C:\WINDOWS
>
>
>  TMP = `C:\WINDOWS\TEMP'
>  TEMP = `C:\WINDOWS\TEMP'
>  PROMPT = `$p$g'
>  winbootdir = `C:\WINDOWS'
>  COMSPEC = `C:\WINDOWS\COMMAND.COM'
>  DIRCMD = `/o:-gne'
>  windir = `C:\WINDOWS'
>  BLASTER = `A220 I5 D1 H5 P330 T6'
>  CMDLINE = `cygcheck -s -v -r '
>  POSIXLY_CORRECT = `1'
>
>  HKEY_CURRENT_USER\Software\Cygnus Solutions
>  HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
>  HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
>  HKEY_LOCAL_MACHINE\Software\Cygnus Solutions
>  HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin
>  HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2
>
>  a:  fd             N/A    N/A
>  b:  fd             N/A    N/A
>  c:  hd  FAT32     4086Mb  31% CP    UN           TEST 98
>  d:  hd  FAT32     8173Mb  84% CP    UN           DATEN
>  f:  cd             N/A    N/A
>  g:  cd             N/A    N/A
>
>
>  Not Found: awk
>  Not Found: bash
>  Not Found: cat
>  Not Found: cp
>  Not Found: cpp (good!)
>  Found: C:\WINDOWS\COMMAND\find.exe
>  Not Found: gcc
>  Not Found: gdb
>  Not Found: grep
>  Not Found: ld
>  Not Found: ls
>  Not Found: make
>  Not Found: mv
>  Not Found: rm
>  Not Found: sed
>  Not Found: sh
>  Not Found: tar
>
>  Warning: cygwin1.dll not found on your path
>
>  Cygwin Package Information
>  No setup information found
>  Use -h to see help about each section

The above would indicate that you don't actually have cygwin installed since
there is nothing in your mount table and no packages listed.  So, this doesn't
really help.

cgf


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/