Strange message "Connot find plugin:Canon Digital Camer

[rickd]

remote control"

I run Mouse Remote and WinLUAex from Mark F's serial plugin I also have been having the odd Girder takes up 100% so I suspect something in my new updated Girder 3.2.6b is not well.

Any idea where this message displayed at the bottom is coming from?

Everything is working though apart from the odd 100% cpu suck out occurring intermittently.

R.

[Ron]

Since Girder 3.2 has no canon plugin I think there is something messed up with your setup. As always I'll suggest to remove all plugins and start putting them back until you see the problem come back. Also please give more information on when the 100% problem comes back, specify exactly what you did.

[rickd]

I was pressing a channel number on my mouseremote, the action is based on what source is selected. If it is satalite it sends the appropriate ir commands via the slink-e to change the channel.

I did this and then I could not change channels and do anything so checked the system running xp and it had girder at 100%. I have left Girder open on the desktop so if it occurs again I can see where in the tree it is and see if it's in a never ending loop. This is the second time it has happened it is very intermittent. I am temped to do a clean install and just backup the registry for slink-e. I still have old versions on the system back to 3.0.

I upgraded from 3.2.4 GVMS to lua and 3.2.6 this is when these strange problems started.

I simply downloaded the installer and loaded it over the top.

I know their is no Canon plugin where could it possibly be getting this from?

[Ron]

Okay,.. this way we should get a little closer to the solution.

About the canon plugin thing, Girder 3.0 had a Canon plugin and it had device number 127. Do a search in your GML file for this number. I suspect there is some reference to it.

[rickd]

Ok thanks Ron I'll check that what is the best tool for editing a gml file will notpad do?

Thanks rick

[rickd]

MatchHidden>FALSE</MatchHidden><MatchNum>1</MatchNum><ActionType>127</ActionType><ActionSubType>1</ActionSubType><sValue1>192.168.1.3</sValue1><sValue2>girder

There are a few of these in the gml file related to ip server

Does that help?

Thanks Rick

[Ron]

Now that is weird, the ip server has ActionType 103, and the source doesn't have any 127 in it. Can you check if those commands are actually used, and how the got there ?

[rickd]

how do I match them to the tree inside girder?

Thanks Rick

[rickd]

Actually I found the commands and they are not used so I deleted them they were legacy commands not sure what I was planning on doing with them.

I think they were ip client events but they would have been from version 3.0

Rick

[rickd]

This 100% problem seems to be occurring randomly I cannot isolate it....when I maximise girder nothing is happening in the tree. but 100% cpu is taken by girder.

Sorry about the lack of info I am perrhaps going to run on my test partition for a while and see if the problem is there too.

I suspect a clean install maybe required.

Any ideas? The only three plugin being used typically are slink-e, serial, mouseremote, ip cleint and server occassionally but not when problem occurs......it can be anything

It seems to work perfect 24 hours and then it locks up

R.

[Ron]

Hmm,.. these are the most difficult to find bugs (mainly because it fault takes suchs a long time to show it self ) :( and the worst thing is I have no clue where to start. Have you tried running girder witout any plugins ?