X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: problems running mmv on cygwin Date: Thu, 23 Mar 2006 20:41:51 -0000 Message-ID: <020401c64eba$36b430a0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 23 March 2006 20:25, Igor Peshansky wrote: > On Thu, 23 Mar 2006, Dave Korn wrote: > >> On 23 March 2006 18:49, Igor Peshansky wrote: >> >>> You should really be asking the suppliers of mmv, but error 0xc0000005 >>> ("the application could not be initialized properly") >> >> ITYM "0xC0000005: STATUS_ACCESS_VIOLATION". It can indeed a) be >> caused by bad perms or b) lead to the application failing to initialize >> properly, but the message you quoted above is IIRC 0xC0000142, isn't it? > > No, I did mean 0xC0000005, though I misremembered the exact message (which > is "The application failed to initialize properly") -- see, for example > . > Igor Last thing I remember, it was Microsoft, not Adobe, who get to define the meanings of NTSTATUS values. Please refer to the DDK docs, or indeed to the canonical header file ntstatus.h dk@rainbow /usr/include/w32api/ddk> grep 'C0000005' ntstatus.h #define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L) dk@rainbow /usr/include/w32api/ddk> grep 'C0000142' ntstatus.h #define STATUS_DLL_INIT_FAILED ((NTSTATUS)0xC0000142L) dk@rainbow /usr/include/w32api/ddk> cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/