Danko,
I won't try to minimize your complaint, but I'd suggest looking at something
outside the CodeWarrior environment. The reason I make this suggestion is
that I've used and been involved with CodeWarrior on Windows for almost four
years and I have never seen this problem.
What types of system services are you running that might be affecting text?
My wife's Win98 machine is always blowing up because she is constantly
installing junk she finds on the Net.
Have you installed something recently that may have patched the MFC or
custom controls DLLs in your Windows directory? Most installers try to
install their versions of these DLLs and few check version numbers
correctly.
Have you tried reinstalling just the "core tools" from the installer again?
-E
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Danko Radic
> Sent: Thursday, December 09, 1999 8:03 AM
> To: [EMAIL PROTECTED]
> Subject: Re: CW R5 trashes source
>
>
> > >I'm not sure why did it happen to me only. Maybe it's so rare
> because most
> > >of projects are not that large. I have some source files
> opened in editor
> > >(IDE), editing one of them and when I press F7 (compile) I
> notice that one
> > >or more opened but not edited files are trashed by non ascii chars in a
> > >way as if you fired a shotgun into a sheet of printed paper (some chars
> >
> > - you don't happen to modify files marked dirty _during_ a make?
> > (this leads for me to loss of the modifications in the case the
> former code
> > had errors or warnings)
>
> No, I've never tried to do such...
>
> > - visual garbled chars might be a sideeffect of inacurate
> screen updating.
> > Is really the file trashed?
>
> It's really trashed. I notice that by compiler error report Illegal token
> (or something like that) and then look into sources and find horror.
>
> > - Beyond that I'd try to get more Ram for the machine. (It
> sounds like the
> > IDE running out of memory and not detecting it)
>
> Well, I've tried R4 on 486 with 16MB. Sources were one half of these
> today, it was slow but working! It's not likely to run out of mem on P233
> with 64MB, but maybe... I might test it.
>
> > Regards,
> > Tom_E
>
> Thanks,
>
> -DR
>
>
>
