Message-ID: <37BD57C8.D1A15478@montana.com>
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i586)
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: fall of rsxntdj??
References: <37B76E28 DOT 72198225 AT geocities DOT com> <013u3.523$ei1 DOT 1216 AT newsfeeds DOT bigpond DOT com> <7pe6ns$kil$1 AT antares DOT lu DOT erisoft DOT se> <Vh9v3.2505$ei1 DOT 5232 AT newsfeeds DOT bigpond DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 23
Date: Fri, 20 Aug 1999 07:27:36 -0600
NNTP-Posting-Host: 208.4.224.80
X-Trace: newsfeed.slurp.net 935155448 208.4.224.80 (Fri, 20 Aug 1999 08:24:08 CDT)
NNTP-Posting-Date: Fri, 20 Aug 1999 08:24:08 CDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Johan Venter wrote:
> 
> Now, would there be any call for this? Or has everyone abandoned RSXNTDJ
> forever? I'm willing to fix this thing (if only to save my bandwidth :-))

When I started using RSXNTDJ, MingW32 was a somewhat awkward patch on
the main Cygwin distro, so I learned to live with RSX, got working
patches for the current SDK to work, repaired the specs file, put all
the stuff on my site, and answered questions, much as you are now doing.

Under Mumit Khan's guidance, MingW32 has really developed into a nice
tool for Windows programming. Given that, I personally see no reason to
duplicate the effort, and have removed the RSXNTDJ material from my
site, and point people toward MingW32 or Lcc-Win32. 

Currently. I use Linux at home and work, and have little time for any
DOS/Windows work. Fixing RSXNTDJ to be a fully usable C/C++ system is a
little more work than is first apparent, but it is your call.

-- 
Bear Technology  Making Montana safe for Grizzlies

http://people.montana.com/~bowman/