Re: Re: Error message "unable to find file"

Please take me off this list

Thanks

Sent from my iPhone

> On Oct 13, 2018, at 1:58 PM, equateinc equateinc-/[email protected] [eccopro] <[email protected]> wrote:
> 
> Please take me off this list
> 
> 
> 
> Sent from my T-Mobile 4G LTE Device
> 
> -------- Original message --------
> From: "SP [email protected] [eccopro]" <[email protected]>
> Date: 10/13/18 2:44 PM (GMT-05:00)
> To: [email protected]
> Subject: Re: [eccopro] Re: Error message "unable to find file"
> 
>  
> 
> 
> Hi!
> 
> Glad to have been of help, even in an indirect way
> 
> The "%1"  is a token for a filename.   When you double click on a *file* with a particular extension (.eco, .doc, .xls or other), Windows looks for the program associated with that extension , opens the program and instructs it to open the filename represented by the %1%.  If the "%1" is not in the open command string in the Registry, Windows will just open the associated program but will not load the file.  If the open command string points to the wrong path, the program will not even open.
> 
> Enjoy Ecco!  One of the best programs ever!
> 
> 
>> On 10/12/2018 20:25, tkaliss wrote:
>>  
>> Problem solved--at least for me.
>> 
>> First, thanks to everyone who replied to my original message. Second, thanks to Santiago I figured out what was happening although it wasn't a missing %1.  By the way, Santiago, what does that %1 do?
>> 
>> Short story is that because Santiago got me do a Registry search I found most of the paths to ecco32.exe had the wrong drive letter.  But all the paths did have %1. So I changed each path entry found by the search to the correct drive.  Now I can double click on a .eco file name and it will open Ecco and load the file.
>> 
>> Longer story.  I recently upgraded to a "new" used computer with two drives--one is new with Windows 7 and the other a clone from my older XP installation which already had Ecco on it. I also created a dual boot -- 7 and XP.  Whichever I boot into sees all the files on both drives.
>> 
>> I did not do a formal installation of Ecco on the Win 7 drive. I think I just copied the working folder from Program  Files on the XP drive to Program Files (x86) on the Win 7 drive. In short, I ended up with two working installations of Ecco.
>> 
>> When I booted into Win 7, now my main working system, and wanted to associate .eco files with Ecco program I told it to always open with the Ecco on the XP drive.  Then when I double clicked on an .eco file it did open Ecco but I got the error message.  So then I tried telling it to associate with the Ecco program on the Win 7 drive and the same thing happened.
>> 
>> So, following Santiago's advice I did the registry search and found that the path under Shell  --> Open that the search found under Applications --> ecco32.exe was the correct path to  ecco32.exe on the Win 7 drive.  All the other paths that the search found under Shell-->Open were the path to ecco32.exe on the XP drive but with the wrong drive letter.  It had the wrong drive letter because I had changed the drive letter for the XP drive a while back. As I said, I changed the drive letter to the current correct letter and did so for any time that path came up (after Shell --> Open or not).
>> 
>> After making that change I went back to an .eco file and right clicked on it and went to the Open With choice and saw two identical Ecco icons I think this was because I had previously tried associating .eco files with each of the two Ecco installations. 
>> 
>> Win 7 shows two identical icons but won't show what the underlying path is.  So when I tried clicking on one of the icons Ecco opened with same error.  When I tried clicking on the other icon Ecco opened and the file loaded. 
>> 
>> I assume this is because I changed the drive letter in the Registry and I used Files Type Manager program which does show the underlying path association to confirm that the Ecco Icon  in Open With that did load the file was the path to ecco32.exe on the XP drive.
>> 
>> So that's the long story. I don't know if this works for other folks. But thanks to all and thanks to Santiago to get me to look closely at the paths in the Registry
>>   
>> 
>> 	Virus-free. www.avg.com
> 
>