Date: Thu, 24 May 2001 09:27:01 +0300 (WET) From: Andris Pavenis To: Filip Niksic Cc: djgpp AT delorie DOT com Subject: Re: Windows 2000 and Rhide In-Reply-To: <9eh87b$q3v$1@as201.hinet.hr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Wed, 23 May 2001, Filip Niksic wrote: > There have been some posts about this topic, but I never > found what I was looking for. The problem is that Rhide > doesn't work on Windows 2000 because it cannot read > or write to files. That means that it cannot open and read > from 'djgpp.env' and I cannot open and save my C files > with it. > I've tried everything, I've installed W2k SP2 but it just > doesn't work. > It's known problem. I tested once on Win2000 that this happens since very begin (RHIDE fails to load file DJGPP environment variable points to). I don't know why this happens. Don't have Win2000 near me now and I'm not planing to use it in near future. Some thoughts: (wild guess) Maybe this is some problem with DJGPP port of TurboVision. In last months I have seen that programs compiled with gcc-3.0 development versions more often crashes after memory related problems. Some time ago I suceeded to build rhtvision-1.10 with gcc-3.0 development version and demo examples crashes when closing opstream (very similar to behaviour of my own program, they crashes when destroying std::cout, std::cerr at exit). Of course this doesn't prove we have such bug I said as I may have been done something wrong when rewrote implementation of TVision stream classes to be compatible with libstdc++-v3 In both cases I had similar iostream related crashes in my own programs, I was not able to detect these memory related problems with simple memory tracking tool (I used Fortify) Andris