Date: Sun, 20 Feb 2000 11:29:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Vinzent Hoefler <JeLlyFish DOT software AT gmx DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Win 2000 & Djgpp
In-Reply-To: <88j4ti$ef0$2@news02.btx.dtag.de>
Message-ID: <Pine.SUN.3.91.1000220112819.25009d-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 18 Feb 2000, Vinzent Hoefler wrote:

> IMO they should return to their desks and start a complete new design
> & programming session. Maybe Win2030 will make it.
> 
> Yes, I agree, it's really hard to make such thing stable (especially
> with all those neat DPMI-apps we write running in a DOS-box ;), but it
> is a matter of a good design to make this thing stable and this should
> be possible including a reasonable speed behind the design.

Care to reveal the secrets of making such a good design?  How do you
make a design that lets 16-bit real-mode code that accesses hardware
on the lowest level, 16-bit protected-mode code, and 32-bit
protected-mode code peacefully coexist?

Some technical problems are so hard that no good design can solve them.
It doesn't help a discussion to claim that the problem happens because
those who were charged with solving it are a bunch of ignorant morons
who didn't learn what software design is.