Girder shutsdown on startup with Autoenable plugin

[rickd]

If I turn off autoenable via regedit and restart Girder fires up fine but as soon as I slect auto enable plugins it shut's itself down.

I run XP sp1 slink-e, ipc, ipes, task create, logging, userevent, xposd, osd,etc

Actually I have had this problem on several machines but managed to solve it on the others just not sure how?

THanks Rick

[Ron]

cannot recreate. You'll have to give more details.

[rickd]

Basically on a reboot girder starts but then shuts down after a minute it never enables plugins it seems to be failing at this point. If I disable autoenable plugins via the rgistry and restart girder and manually enable all is ok.

I will start removing plugins to isolate which one is causing an issue. I think I might have an old version of a plugin somwhere in their.

I just upgrades from 3.2.4 to 3.2.6 with lua.

Cheers Rick

[Ron]

Good, that was going to be my next suggestion. :-)

[rickd]

It is the serial plugin causing the autoshut down the only device connected is the Mouse remote I have Marks plugin 3.08 and the lua extensions for this loaded.

It starts ok if I manually enable plugins.

Any ideas?

R.

[Ron]

We'll have to ask Mark.

[Mark F]

I can't recreate this on my NT 4.0 system. I haven't seen it at home on my Win 98 or Win ME systems but I'll try them again tonight.

Just to be sure, are you using Girder 3.2.6b?

Before unloading all of them, did you also have the WinLUAEx plugin loaded? The included MouseRemote support requires that plugin though having the plugin missing shouldn't cause a crash like this.

What happens if you change the MouseRemote definition to "No Port" from the current serial port (COMx)? Does Girder still crash on startup?

[rickd]

Hi Mark
yes I am using 3.2.6b and have WinLUAex plugin loaded. The mousremote and every thing else works great if I enable the plugins manually.

All I removed to resolve this was the serial plugin 3.08 .

I'll try the no port thing thanks R.

[rickd]

Mark setting it to no port solves the problem but of course is not a solution

hope this helps you figure it out

Note I have loaded 3.2.6b over many versions back to 3.0

if that helps

Thanks Rick

[Mark F]

Have you used the Serial plugin on this machine before? Do you have multiple device support files loaded but pointed to "No Port" or is the MouseRemote the only device listed? (go to file/settings/plugins/generic serial support and press settings)

As you mention installing over many older versions, I'd really like for you to do a clean install, if that is at all possible. If you would lose too much, DON"T DO IT! We will find another way.

[rickd]

Clean install is no problem I will just back up the registry for slink-e which is the biggy.

Remove all versions of girder and reinstall form scratch.

I only have Mouseremote on this machine nothing else and it only started playing up after upgrade and moving to your new .ini with the scripting for mouse move etc.

I also have a problem with girder going to 100% cpu randomly and having to be restarted usually after 24-48 hours. I have a feeling all this is related.

Cheers Rick

[Mark F]

Thanks for being so understanding. :D

[Pete]

I'm a new user of Girder and I did my very first install of Girder today (v3.2.6b). I'm using Windows XP. The only plug-in that I enabled was StreamZap.dll.

Everything was working fine and I created a complete GML file to use with WinDVD. It worked perfectly.

Then, I'm not sure what happened, but I just bought a Harmony remote and installed the software. I rebooted when prompted. Girder loaded okay, but it didn't automatically load my GML file like I wanted. I quit Girder and then could not get it to restart. I'm not sure if this has anything to do with the Harmony software or not.

Unlike rickd, after disabling Auto Enable in the Registry, Girder still didn't successfully load. The strange thing is that there were no error messages. Girder tried to start, but then quit without any dialog.

I had added a shortcut for Girder in the "All Users Startup" folder. I realized that Girder had also restored this shortcut to my userid's startup folder although I had deleted it. I thought that this might be causing the problem (two copies of girder.exe trying to start at the same time during a Windows' boot). So I disabled the option in Girder to load at startup, and only kept the shortcut in the "All Users" folder.

After rebooting, I got a dialog box from Girder that was titled "Fatal Error" and said "Cannot find required DLL (gvms.dll)". I clicked the OK button. I manually started Girder. Now, it started okay and automatically enabled my GML file.

Sorry this is such a long post (especially since it's my first one). I'm just trying to provide as many details as possible in the hope that someone will notice something.

Here's what I'm trying to do: I'm using my Harmony universal remote to send signals to my StreamZap IR receiver. Then, I'm using Girder to redirect these signals from StreamZap to WinDVD and such.

Like I said, everything was working perfectly before I rebooted and I was totally impressed with Girder. I hope that there is a solution to this.

Thanks,

Pete

[Pete]

I'm so embarrassed! When I created the shortcut to girder.exe in the All Users Startup folder, I accidently copied the executable there instead of creating a shortcut. Of course there was no gvms.dll file in the Startup folder. Doh!

Everything's working fine now. Sorry for bothering you.

Pete

[Mark F]

If I had a quarter for every time I've done that... :D

By the way, your original post was NOT too long. More information is always better than not enough. I'm glad you were able to self-solve this one.

Now I just hope we can solve Rick's problem.

[rickd]

Just to update you Mark in the weekend I switched to a clean install on my test parition the problem is still their (enable pluin on startup girder starts and shutdown) it must be something to do with your script on enable for mouse remote that XP is not happy with.

The 100% problem has not returned though since switching to the new clean install on my test parition......so I will duplicate on my production parition.

I believe all these issues are rleated to the mousermeote stuff.....another test I can do is switch to using just raw serial commands again to trigger my slink-e commands.

But we will see

Cheers Rick

[Mark F]

I've tried and tried but cannot reproduce this on NT 4, Win '98 or Win ME. :(

My only suggestion would be to build a command and learn the Girder "OnEnable" event to trigger it. The command would be a Variable Manipulation Script and the contents would be the script currently residing in the MouseRemote Enable event. Then uncheck the enable event box in the mouse remote device and try this again.

Basically I'd like you to move the enable script processing out of the serial plugin and into Girder (as part of the OnEnable processing) and see if you have the same problem.

Again, thanks for being so understanding.

[rickd]

Thanks Mark that is a good idea I will try that I am sure it will work I think it is some kind of timing issue so I could even delay it with userevent. I read somewhere that xp takes a while longer to initalise serail ports per it has something to do with it.????

Cheers Rick

[rickd]

Mark I have done a clean install on girder and still have this 100% problem where it seems to get stuck in the mouseremote script.

I am reverting to just using raw serial events as this works fine. THe mouse will not work anymore though.

XP seems to be the only thing differnt here.

I use the mouseremote to trigger slink-e events mostly if thats any help and it seems to occur on them regardless of the event type but always mouse remote. I use various antirepeat times on event strings but that should be fine?

Girder hangs with 99% CPU and I have to end the process.

THanks Rick

[rickd]

Ok guy's I can now reproduce this problem anytime I like.

I have elimated the slink-e as the cause as I removed any ir esend commands from the action of this event and it still fails.

Firstly if Girder is in foreground it is difficult to reproduce. In minimised it is alot easier.

ie I setup an counter and pressed over 1000 events no failute put it to minimised and it fails within 20-40.

Here is the code:

Channel+
If zoneout==4 then result=1
else
result=0
(the result is 1 so it would send the corresponding slink-e ir ch+)
their are other statements with different ir based on the zoneselection but they produce result=0 so no jump to.
I substitued the send ir command from slink-e with an onscreen display and it still fails.

So to me this says there is something wrong with the Mouseremote scripting or it compatibility with XP.

I can reproduce this on two separate paritions on XP professional.
It have only occurred since implementing the winluaex and new mouseremote.ini for mouse movement.

r.

[rickd]

Ok more progress disabling the receive script under serial plugin solves my problem 100% CPU hang problems and everything keeps going so far and it all still works regardless ...including mouse movement and click stuff so it something in the receive script is eventually killing Girder under XP. Usually after several keypresses.

As for the original enable issue using the enable script inside Girder triggered by "on enable" solves the issue of Girder shutdown on enable of plugins at startup.

Everything working smooth all be it via some work arounds. :D

Hope this allows you to get to the bottom of it.

Cheers Rick

[rickd]

Ok had another failure after a week or more but it's more stable with no serial script on event enabled (100% problem)

Maybe a restart of Girder every day or week will prevent as it is definitely related to the number of transactions processed from startup.

Mark are you able to comment?

[Mark F]

Only that I don't have this problem on a non-XP system.

I would suggest NOT starting Girder when the system is initializing. This seems to be the cause though I have no idea why.

Sorry. :(

[rickd]

Any plans to go XP in the future ?

[Mark F]

I will be forced (kicking and screaming) to XP or one of it's offspring when I buy/build my next PC. Depending on more things than I can enumerate, I may be buying/building an NForce2 equiped HTPC this summer (July-August).