X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_NM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4C7EEC78.1050008@tlinx.org> References: <4C7EEC78.1050008@tlinx.org> Date: Thu, 2 Sep 2010 10:00:34 +0200 Message-ID: Subject: Re: difference running from cmd vs. bash? From: Csaba Raduly To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: 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 Thu, Sep 2, 2010 at 2:14 AM, Linda Walsh wrote: > In Bash: >> >> winmgmt /verifyrepository > > WMI repository verification failed > Error code: =A00x8007007E That is the COM error code for "The specified module could not be found". Perhaps bash has altered the PATH. Do you get the same error when running winmgmt without any parameters? If yes, here's how to find out which DLL is not found: cugcheck 'c:\Windows\System32\Wbem\winmgmt.exe' This will give you a list of which DLLs are loaded and which ones are missi= ng. --=20 Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torv= alds "People disagree with me. I just ignore them." -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple