X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: postinstall hang
Date:	Thu, 3 Apr 2008 16:05:04 -0400
Message-ID:	<A28965E490DE4B4DBE938ECF7CC19C04073F5032@blums0014.na.baesystems.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> <004a01c89428$ea981fe0$2708a8c0 AT CAM DOT ARTIMI DOT COM> <A28965E490DE4B4DBE938ECF7CC19C04073F4FD1 AT blums0014 DOT na DOT baesystems DOT com> <0a7501c894a6$ae4e2ce0$2708a8c0 AT CAM DOT ARTIMI DOT COM>
From:	"Popper, Samuel \(US SSA\)" <samuel DOT popper AT baesystems DOT com>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id m33K5UHI010949

> SERVICE_NAME: Sentinel
> DISPLAY_NAME: Sentinel

> SERVICE_NAME: SNTNLUSB
> DISPLAY_NAME: Rainbow USB SuperPro

>   Security/rights management/license control thingy of some sort.  It
> could
> easily have been coded under the mistaken assumption that hooking
process
> creation is a reasonable means of tamper-proofing your software.
> 
>   Is it practical to try uninstalling and seeing if that's the cause?

Unfortunately, I can't easily uninstall those drivers, since they are
needed and used by other users of the machine.  Is there a way to get
the paths to those drivers?  I can probably get away with renaming the
files and rebooting long enough to tell if that fixes the problem.

FWIW, we have other servers in a near-identical configuration (with
those same IO card and dongle license drivers), and they don't have any
problems running Cygwin.

Thanks in advance, 

-Sam



--
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 -