AssoEdit: Looping on ADD...

     ****Resend, because the thread not appearing in my NG  ****
     ****list And, because it happens on every ADD, not     ****
     ****just the *.WMV pattern.]                               ****

I am attempting to ADD a File Association by File Filter to an eCS 2.0
RC2 system that is running fine except for the below:

I've never had a problem before, but now trying to add:
     *.WMV  [The actual pattern is not significant.]
to the list, the system goes into a loop.  One of the two processors
starts running about 80-90%.  Most of the processor is going to:
     CPU0-IRQ Load

The only way to exit is  Ctrl-Esc and CLOSE the task.  The task closes
clean.

On 04.04.08 18:41, Carl Gehr wrote:

> I am attempting to ADD a File Association by File Filter

What does "ADD" stands for? Do you mean "add"? ;-)

> the system goes into a loop.

Your ini files are broken. That happened here a few years ago, too. I
fixed that by removing handles from OS2SYS.INI, you know the tools for
that. With luck, that will work for you as well.

But you can't be sure, that anything else is OK. So, it's better to
restore a WPS archive. (I hadn't done that, because the installation
had already other problems, that couldn't be fixed by the archives I
had. I finally did a reinstall.)

-- 

On 04/04/08 03:12 pm, Andreas Schnellbacher wrote:
> On 04.04.08 18:41, Carl Gehr wrote:
> 
>> I am attempting to ADD a File Association by File Filter
> 
> What does "ADD" stands for? Do you mean "add"? ;-)
> 
>> the system goes into a loop.
> 
> Your ini files are broken. That happened here a few years ago, too. I
> fixed that by removing handles from OS2SYS.INI, you know the tools for
> that. With luck, that will work for you as well.
> 
> But you can't be sure, that anything else is OK. So, it's better to
> restore a WPS archive. (I hadn't done that, because the installation
> had already other problems, that couldn't be fixed by the archives I
> had. I finally did a reinstall.)
> 
Thanks for the response.  I was afraid that would be the suggestion.

Honestly, I'm very reluctant about the INI tools.  I really have no clue 
what all the messages are that come from, for example CleanINI, so I 
don't know what to respond.  I tried using CleanINI a number of years 
ago and so hosed my system that I had to start over from scratch.  And, 
at this point in my usage, I just cannot afford to start over.

Is there a nice simple set of dummy instructions, such as:
*  Copy/Backup xxxx
*  Run 'CleanINI' and look for '....'
*  Delete, change, ???? to...
*  Try AssoEdit again...
Sorry to be so dense...  But, I am an OS/2 *user* not an OS/2 SysProg. 
[And, really have no desire to be.]

Thanks, again,