Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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-Internal-ID: 3D171F790002C506 Message-ID: From: Mark DOT Bevan AT gwent DOT wales DOT nhs DOT uk To: robert DOT collins AT syncretize DOT net, cygwin AT cygwin DOT com Subject: RE: install process hangs on when run under windows 98 (using set up v2.249.2.4) Date: Tue, 2 Jul 2002 13:38:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I have tried to run cygwin following a reboot after a hung install and think I may have found something that may help : Cygwin runs fine - I get a shell prompt (after creating a home dir for me) I try and run mkgroup (either mkgroup or mkgroup -?) and I get a message in the shell window : BASH: /usr/bin/mkgroup: permission denied and a dialogue box which is titled error starting program saying : MKGROUP.EXE is linked to missing export ADVAPI32.DLL:LsaClose I click on OK and cygwin shell seems ok still - I can enter other commands and exit fine. I checked my system and the DLL is in c:\windows\system from the properties file version tab I have the version 4.80.1675 of the DLL on my system. Hope this helps, Mark -----Original Message----- From: Robert Collins [mailto:robert DOT collins AT syncretize DOT net] Sent: 02 July 2002 12:35 To: Bevan, Mark; cygwin AT cygwin DOT com Subject: Re: install process hangs on when run under windows 98 (using setup v2.249.2.4) ----- Original Message ----- From: To: ; Sent: Tuesday, July 02, 2002 8:30 PM Subject: RE: install process hangs on when run under windows 98 (using setup v2.249.2.4) > I have attached a zip'ed version of the c:\cygwin\etc tree as requested Thanks. You've got win9x don't you? I need someone else on this list who has 9x to confirm that the default content of the 'group' file should be empty. (I don't think it should be. All the postinstall files show as completed (they've been renamed to foo.done). This is probably due to the failing .dll location, which setup won't detect. IOW we haven't managed to test the problem you experienced yet :[. I think that a corrupt setup.ini has been released, as there was another report of a missing cygwin package just earlier today. I haven't looked into this yet, but will do so soon. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/