X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Wed, 30 Apr 2003 11:17:47 -0500
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: djgpp AT delorie DOT com
Subject: Re: djgpp-friendly parallel port ZIP driver
Message-ID: <20030430161747.GD4866@kendall.sfbr.org>
Mail-Followup-To: djgpp AT delorie DOT com
References: <20030430142644 DOT GB4866 AT kendall DOT sfbr DOT org> <b8oqek$pt9$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b8oqek$pt9$1@nets3.rz.RWTH-Aachen.DE>
User-Agent: Mutt/1.4.1i
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

-: > Does anyone know of djgpp-friendly software that might be used to
-: > replace the Iomega driver?
-: 
-: I wonder what makes you think that a driver being closed-source makes
-: it "unfriendly" to DJGPP, just like that.  There's no particular
-: reason to assume that it shouldn't just work as it is --- or do you
-: have experience otherwise?

Misunderstanding.  The Iomega driver works just fine with djgpp.
I am asking if anyone knows of a replacement (with source) that
I can build with djgpp.