www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/04/01/13:48:33

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <001901c89348$cd86c8b0$06bca8c0 AT bigtower> <A28965E490DE4B4DBE938ECF7CC19C04073F4FB1 AT blums0014 DOT na DOT baesystems DOT com> <47F19881 DOT 2080508 AT byu DOT net> <A28965E490DE4B4DBE938ECF7CC19C04073F4FBF AT blums0014 DOT na DOT baesystems DOT com> <00b001c89400$e59d20d0$2708a8c0 AT CAM DOT ARTIMI DOT COM> <A28965E490DE4B4DBE938ECF7CC19C04073F4FC7 AT blums0014 DOT na DOT baesystems DOT com>
Subject: RE: postinstall hang
Date: Tue, 1 Apr 2008 19:48:03 +0100
Message-ID: <004a01c89428$ea981fe0$2708a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <A28965E490DE4B4DBE938ECF7CC19C04073F4FC7@blums0014.na.baesystems.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Popper, Samuel (US SSA) wrote on 01 April 2008 16:53:

> Here's my list of candidate BLODA .dll's from procexp:

> They all appear to be from cygwin or right from Windows 

  Yes, I think you're right about that, so I doubt any of them is related.

> (I can send the desciption/version number information if desired).  

  Shouldn't be necessary.  If there was a BLODA problem with one of the
bog-standard MS-shipped system DLLs, we'd surely be hearing from a lot more
people with problems on the list.

  Here's a couple more bits of info you could try sending that might give us
clues:

#1.  Run "cygcheck -s -r -v > cygcheck.out" and send the .out file as an
attachment (specifically, please, not inline text) with your next post to
the list.

#2.  Using the "sc.exe" command (originally from MS' Resource Kit, but IIUIC
built-in to all recent versions), get a list of all services and drivers by
running "sc queryex type= all bufsize= 65536 > sc-out.txt", and send that as
an attachment.

#3.  If #2. can't work for any reason, you can still get part of the info (a
list of running services) by running "net start > servs.txt", and send that.


    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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019