RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32

["Trenton D. Adams" <tadams at extremeeng dot com>]

I had troubles getting it going, and someone said to use 1.3.1.2 because
it doesn't have any problems with using the latest CVS.  Anyhow, I
looked back at my earlier messages, and I think I miss read one of them.
Ever since, I've thought that the new Tool was being used with a special
CVS or something.  So, I thought it was being designed to replace the
old tool, and the old style of CVS or something like that.

-----Original Message-----
From: gary@chez-thomas.org [mailto:gary@chez-thomas.org] On Behalf Of
Gary Thomas
Sent: Wednesday, June 13, 2001 8:53 AM
To: Trenton D. Adams
Cc: eCos
Subject: RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32



On 13-Jun-2001 Trenton D. Adams wrote:
> I was told you can't use the Config Tool 2.0 alpha with the latest CVS

> so I haven't bothered to try.
> 

I think you've got it mixed up - you can't use the _old_ tool (1.3.1)
with the latest (CVS) repository.  You most definitely _can_ use the new
tool with it (otherwise, it'd be pretty useless, wouldn't it?)

The only caveat is that it is still quite new, hence "alpha", but we do
expect it to work and for users to try it and give us feedback when it
doesn't work as expected.

> -----Original Message-----
> From: gary@chez-thomas.org [mailto:gary@chez-thomas.org] On Behalf Of 
> Gary Thomas
> Sent: Wednesday, June 13, 2001 6:14 AM
> To: Trenton D. Adams
> Cc: eCos
> Subject: RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32
> 
> 
> 
> On 12-Jun-2001 Trenton D. Adams wrote:
>> I have two separate configs.  The are identical except one is RAM, 
>> and
> 
>> the other is ROM support for the kernel.  If I change from ROM to RAM
>> support, it doesn't allow me to save the new configuration under the 
>> current project.  I have to select File|Exit in order for it to ask
me
> 
>> to save and then it will finally acutally save it.  This caused me to
>> compile a program thinking it would run in RAM when it was actually 
>> meant to be run in ROM.
> 
> Does this problem exist with the latest (Config Tool 2.0 alpha)?
> 
> The old tool is no longer maintained, so the most we can do is make 
> sure that the problem is fixed in the new one.