From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
Subject: RE: Windows 95 support ?
Date: Tue, 25 Apr 2006 22:43:43 +0100
Message-ID: <056301c668b1$52a03910$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
In-Reply-To: <20060425213820.GB7180@bouh.residence.ens-lyon.fr>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On 25 April 2006 22:38, Samuel Thibault wrote:

> Dave Korn, le Tue 25 Apr 2006 18:34:48 +0100, a écrit :
>>   Hm.  Sounds like a silent dll initialisation failure.  I have to ask the
>> dread question: do you have any debgging tools installed?  Setup requires
>> the following functions from msvcrt:
>> 
>> _access, _fdopen, _mktemp, _putenv, _read, _setmode, _strdup, _stricmp,
>> _strlwr, _strnicmp, _write 
>> 
>> so you could check that the version you have actually supplies them all.
> 
> It does supply them all.
> 
>> It's also possible that it has some dependencies on other dlls that
>> normally get installed at the same time as the rest of the IE4 package
>> - maybe updated kernel32 or something.
> 
> It depends on kernel32, but all the needed symbols are provided by the
> installed kernel32.dll.


  Sounds like the comctl32 theory would be the next one to test then.  That
should be available whereever you got msvcrt.dll from - they were shipped in
the same cab in the IE4 release according to that KB article mentioned
upthread.


    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/