Re: Ecco alarms are not behaving properly - urgent

Douglas Hinds <[email protected]>
Newsgroups gmane.comp.windows.eccopro
Message-ID <[email protected]>
If you are considering changing operating systems (and that was exactly
my reaction on reading your post - it's an operating system related
problem), you should be aware that you do NOT have to use M$ Windows in
order to run EccoPro successfully.  I have been using it for years on a
number of GNU/Linux Distributions (i.e. openSUSE and a number of Debian
derivatives) with no problems, under Wine (and occasionally, Crossover).

All of which are far better than any of the currently supported versions
of Windows and the community support is far better also (and if course,
there's no cost).

Douglas

Using a customized version of SparklyLinux Ultra Openbox, at the moment.


On 03/03/2014 12:17 PM, [email protected] wrote:

> I'm having a terrible time with alarms. I tried to shut down Ecco and
> it gave  me the "out of memory" pop-up, and I had to shut it down the
> hard way. When I launched it again it prompted me to turn on alarms
> that are in the file and I answered yes for each Ecco file that I
> opened. I went through them and closed the program and I think the
> same thing happened, so I removed the ecco.alm file so that it would
> rebuild itself but it displayed a list of alarms and even though
> I advanced them, it didnt stick, so I reviewed them again and they 
> still didnt stick. The only thing that stuck was when I actually reset
> the alarm for an item.
>
>  
>
> Are there any other files to remove so that the alarms will rebuild
> itself, such as ecco.cfx and ecco.fdb? I hope that someone has a
> fix for this. Please reply to this post in the group and then send me
> an e-mail at [email protected]
> <mailto:[email protected]> that I will know to check it immediately. I
> need this help right away.
>
>  
>
> Thanks,
>
>  
>
> Bill 
>
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.