X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Harbour
Date:	Wed, 01 Dec 2004 21:15:27 CST
Organization:	Rice University, Houston, TX
Lines:	22
Message-ID:	<41ae88cf.sandmann@clio.rice.edu>
References:	<r5-dncaxec_05jPcRVn-hg AT comcast DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1101957729 441 128.42.105.3 (2 Dec 2004 03:22:09 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	Thu, 2 Dec 2004 03:22:09 +0000 (UTC)
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Although Client uses Win2K, none of our current C or Clipper tools 
> know anything about Windows. Moving from Clipper to *Harbour is 
> interesting for me, developer, but of no concern of Client, who 
> doesn't want to know what we're talking about.

One additional concern is Microsoft has said the 16-bit VDM will
not be supported under 64-bit Windows (32-bit and 64-bit only).  It's
too early to tell if that's important or will stick.

> My C and Clipper DOS programs are handled nicely by ntvdm.exe under 
> Windows 2K. Why not under XP?

I have found XP to be mostly bug compatible with Windows 2000.  I
use DJGPP V2.03 (refreshed) images under Windows 2000 and XP daily
without any issues.  But these are usually simple text processing
tools, no graphics or screen manipulation.  I have also had good
luck with V2.04 pre-release code on 2K and XP.

Interestingly enough, quite often the DJGPP memory allocation routines,
file I/O and screen I/O are faster than the native Win32 ports of the
same programs.

- Raw text -