Running 64 bit Cygwin from 32 bit cmd.exe in 2003

issue more quickly. BTW, I discovered the bitness of a running cmd.exe by using Task Manager and Process Explorer. Paul Nickerson IT Systems Administrator & Support DeskNet Inc. Portland, Maine -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com

Re: Postinstall Script Errors With Exit Code 128

> From: "Larry Hall (Cygwin)" > To: cygwin at cygwin dot com, > Date: 05/29/2013 03:51 PM > Subject: Re: Postinstall Script Errors With Exit Code 128 > Sent by: cygwin-owner at cygwin dot com > > On 5/29/2013 3:18 PM, Paul.Nickerson at desknetinc dot com wrote: > > So, I think that one of these

Re: cygutils Postinstall Script Errors With Exit Code 128

cygwin-owner at cygwin dot com wrote on 05/29/2013 11:47:20 AM: > From: Reini Urban > To: The Cygwin Mailing List , Charles Wilson > , > Date: 05/29/2013 11:47 AM > Subject: Re: cygutils Postinstall Script Errors With Exit Code 128 > Sent by: cygwin-owner at cygwin dot com > > On Tue, May 28,

Re: Postinstall Script Errors With Exit Code 128

cygwin-owner at cygwin dot com wrote on 05/29/2013 12:28:30 PM: > From: "Larry Hall (Cygwin)" > To: cygwin at cygwin dot com, > Date: 05/29/2013 12:29 PM > Subject: Re: Postinstall Script Errors With Exit Code 128 > Sent by: cygwin-owner at cygwin dot com > > On 5/29/2013 12:04 PM, Paul.Nickers

Re: Postinstall Script Errors With Exit Code 128

t redirecting output to a file, I get a little more >> information before it hangs, which I have copied out of the command >> prompt and attached as cygcheck-no-redirect.out. I do not know why >> it's saying I have multiple cygwin1.dlls on my path. There is only >>