| Newsgroups |
gmane.comp.windows.eccopro |
| Message-ID |
<[email protected]> |
P.S. Reposting an excellent recent post on this issue by Chris Holly. Hope this helps.
> On Sep 7, 2017, at 15:05, 'Christopher J. Holly' [email protected] [ecco_pro] <[email protected]> wrote:
>
> I know this has been raised before, but with Microsoft messing with
> our computers at will, stuff happens. And so does it when I mess with
> my computer in ignorance. So it is good to keep it in the back of your
> mind. I managed to "break" my Ecco installation in Wind 10 Creator
> edition by learning eccoext rules the hard way. (But I did learn
> something.)
>
> I should have written down the exact error message, and I don't know
> how too make the problem happen at will. But basically when I tried to
> run eccoext or even ecco32, I got an error message and the program
> would not even start.
>
> I tried to edit the eccoext.ini and ecco.ini files; I looked in the
> registry for files that I knew I had messed with. None of that did
> anything that I could tell.
>
> Instead, some dim bulb went off in my head that this had happened
> before and the brain trust told me how to fix it, so I went searching
> for the deeply buried VirtualStore folder where I remember my ecco.cfx
> file now is hiding.I found that at
> C:\Users\Chris\AppData\Local\VirtualStore\Windows. (Of course only a
> few of you will find yours under Chris)
>
> But there I found not only the ecco.cfx, (which in prehistory I made
> copy itself somehow), but the ecco.alm file and the ecco.fdb file. I
> know the ecco.alm file stores alarms somehow and you can delete that
> and it seems to recreate itself next time ecco boot. I don't know what
> the ecco.fdb file is for, but it also creates itself if you delete and
> reboot ecco. It would probably be prudent to rename these just in case
> your mileage varies, but I have never had reason to restore either of
> them when I have had this problem with Ecco not wanting to start.
>
> So I deleted ecco.alm and ecco.fdb from that folder as someone taught
> me to do years ago. And then I clicked on my EccoExt shortcut, and by
> golly, Ecco started right up. Of course, it did not open any files
> because I had messed with the ini files, but I was able to open and
> *.eco and resume my miscreant behavior.
>
> I don't know what happens to ecco.alm and ecco.fdb, but so far every
> time Ecco has refused to open after I had been using it successfully,
> one or both of these files is the culprit.
>
> Hope this reminder helps others suffering from memory impairment, too.
> --Chris
>
Sent from my iPad Pro
> On Oct 1, 2017, at 13:09, MR <[email protected]> wrote:
>
> I am a 25-year Ecco user (and completely depend on it all day, every day at work), but I’m not a computer expert so the generous folks on this forum have been a godsend to me. While I was in the process of upgrading from Ecco to EccoExt (because my old Ecco file was reaching its memory limits quickly), somehow my data file got corrupted and Ecco would not even launch because it was trying to launch using the last file opened (which was corrupted). Someone on the forum suggested I delete the .alm file, but I couldn’t find it, either. Somewhere on the board, there is a program to locate the .alm file (if you can’t find it, I can search through my old emails and see if I can find the link), but the IT guru at work searched using an IT-guru method and quickly found the .alm file (which was somewhere under the Windows directory, as I recall), despite the fact that Windows Explorer couldn’t find it. He deleted the .alm file and EccoExt instantly launched (and, as others have pointed out, rebuilt the .alm file when I opened my .eco file) and all was well again.
>
> The bottom line is, many of us have experienced blind panic when Ecco suddenly stops working, but it is almost a guarantee that someone on this forum will suggest a solution to any problem so don’t give up hope. If you stick with it, you will get it working again.
>
>
>
> Sent from my iPad Pro
>
>> On Oct 1, 2017, at 11:37, PD Shearston pdshearston-/[email protected] [eccopro] <[email protected]> wrote:
>>
>> I've tried Kerry, I did a search of all my hard drives ecco.cfg, ecco.cfx and ecco.alm files, and just for *.cfg, *.cfx and *.alm files. Nothing. Perhaps they are hidden files. I will try a search on Windows directory unhiding all files. Thank you for your suggestions
>>
>>
>> On Saturday, September 30, 2017 11:30 PM, "[email protected] [eccopro]" <[email protected]> wrote:
>>
>>
>>
>> If Ecco was ever successfully started, the machine must have created .cfg and .alm
>>
>> These used to be created in the Windows directory. With the advent of the extension, the files maybe elsewhere.
>>
>> Since you didn’t find copies, you probably Do not have the necessary permissions to search all folders.
>>
>> Now can you find them?
>>
>> Kerry
>> ZVALUE
>>
>>
>>