Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 13 Nov 2002 09:34:53 -0500
From: Alixberry@aol.com
To: maxb@ukf.net, cygwin@cygwin.com, lhall@pop.ma.ultranet.com
Subject: Re: Trouble compiling e100 driver
MIME-Version: 1.0
Message-ID: <0CA49EB2.4E015AEB.02241D0E@aol.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

This version of cygwin did come with BlueCat so that is the reason I have such an old version. I had considered updating it before but I had worried that a newer version might cause problems with my version of BlueCat. Now, I think I had better give it a try.

Thanks for the help. I'll see if this could be part of the problem.

In a message dated 11/12/2002 7:07:03 PM Eastern Standard Time, maxb@ukf.net writes:

> Alixberry@aol.com <Alixberry@aol.com> wrote:
> 
> >> Max,
> >> Attached is the output of the of the cygcheck.
> >> Thanks!
> 
> >> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL
> >>   setup\b15.0\mounts\0C (default) = `C:'
> 
> >>                   2000/09/22 c:\cygwin32\bin\cygwin1.dll - os=4.0
> >> img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=1999/10/28 13:15
> 
> Ouch! You are using a truly ancient version of Cygwin. I assume it somehow
> came with BlueCat.
> 
> If you can, you should update it. I don't know how tightly it is bound to
> the BlueCat system.
> 
> If you can't, then your only remaining port of call is BlueCat
> support/mailing lists. There is very likely no one here who 
> remembers the
> version of Cygwin you are using.
> 
> Max.

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