controling WinDVD on PC2 via girder running on PC1

[Torsten]

My situation is a follows:

Girder is running on PC No.1 (192.168.0.255), on PC No.2 (192.168.0.254) WinDVD is running and I would like to use girder (on PC No.1) to execute the commands on PC No.2 so that WinDVD is remoted by PC No.1.

How can I manage this? I read the documentations of various plug-ins, especially the internet event client and server, but I did not found a solution jet.

Could somebody be so kind and give me a hint?
:roll:

[Mark F]

The Internet client and server are plugins that will let you do this.

The server will opperate inside of Girder on PC2 (accepting messages from PC1 and executing commands against WinDVD) while the client (or a lite version of the client like ievent.exe) will execute on PC1 (sending messages).

I would suggest this plan of attack:

Download and enable the Logger plugin on PC2 so you can see all the events as they travel through Girder
Build a command inside Girder on PC2 that does something to WinDVD and test it using F5 to make sure it works
Enable and configure the Internet server on PC2 using the information in the C:\Program Files\Girder32\Help\ievent_readme.txt file
Enable and configure the Internet client on PC1 OR use ieventc.exe to send something to PC2 and verify what is occuring in the Logger window is what you are trying to send
Learn the sent data to trigger the command on PC2
[list:ae380bd9b7]
Highlight the command you built previously
choose the Internet Event Server from the pulldown next to the learn event button
press the learn event button
cause PC1 to send the data on the network using the Internet event client or ieventc.exe

Test the trigger by causing PC1 to send the data on the network again
[/list:o:ae380bd9b7]

I have probably glossed over some of the finer points ;) so please ask more questions if you get stuck.

Good luck. :D

[Promixis]

A better way is netremote and girder.

Check out www.netremote.org

[Torsten]

@Mark F.

Sorry to come back a little late on this subject, i was out for a few days.

I did as you suggested in your above post. On PC1 I configured a command as follows:

Server: IP of PC2
Port: 1024 (as I have configured on PC2 the internet event server.)
Password: Same as on PC2
Eventstring: eventsring
Payload: payload128
Timeout: none

Executing the command on PC1 shows nothing in the logger window on PC1. On PC2 the logger window shows:

15:52:30 Tuesday, October 07, 2003 EVENT: Dev: 203 Disconnect Pld1: 192.168.0.1
15:52:30 Tuesday, October 07, 2003 EVENT: Dev: 203 eventstring Pld1: 192.168.0.1 Pld2: payload128
15:52:30 Tuesday, October 07, 2003 EVENT: Dev: 203 Accepted connection Pld1: 192.168.0.1
15:52:30 Tuesday, October 07, 2003 EVENT: Dev: 203 Incoming connection Pld1: 192.168.0.1

So it seems that something is incoming on PC2, but this is not triggering the command on PC2 which opens WinDVD (the command itself is tested and works).

When I want to learn on PC2 the command to open WinDVD, I highlight the command, choose Internet event Server and press the learn event button and a message box opens asking: ”Enter the eventstring you want will send over the internet”

I am lost here: what do I need to fill in here?

Thanks,
Torsten

@ mjcumming
Thank you for your hint regarding Netremote, but I like to use girder to become more familiar with this great tools.

[JimHugh]

Server: IP of PC2
Port: 1024 (as I have configured on PC2 the internet event server.)
Password: Same as on PC2
Eventstring: eventsring
Payload: payload128
Timeout: none

Replace "Eventstring: eventsring " with something like

Eventstring: WINDVDPlay


When I want to learn on PC2 the command to open WinDVD, I highlight the command, choose Internet event Server and press the learn event button and a message box opens asking: ”Enter the eventstring you want will send over the internet”

Then on PC2, enter WINDVDPlay

Repeat for each remote command that you want triggered.

[Torsten]

Jim, thank you for your help. I did as you wrote and my log on PC2 looks now so:

16:56:11 Tuesday, October 07, 2003 EVENT: Dev: 203 Disconnect Pld1: 192.168.0.1
16:56:11 Tuesday, October 07, 2003 EVENT: Dev: 203 WINDVDplay Pld1: 192.168.0.1 Pld2: payload128
16:56:11 Tuesday, October 07, 2003 EVENT: Dev: 203 Accepted connection Pld1: 192.168.0.1
16:56:11 Tuesday, October 07, 2003 EVENT: Dev: 203 Incoming connection Pld1: 192.168.0.1
16:55:37 Tuesday, October 07, 2003 EVENT: Dev: 18 GirderEnable
16:55:37 Tuesday, October 07, 2003 EVENT: Dev: 18 GirderOpen

But: it triggers nothing :cry: I think I do something wrong.

[JimHugh]

The event string is case sensitive.

WINDVDplay is not the same as WINDVDPlay.

Does the WinDVD Girder command on PC2 work when you use F5 (Test command) directly?

[Torsten]

The event "learnd" on PC2 is exacly like the eventstring on PC1.

When testing the command that should be triggered on PC2 (F5) it starts WinDVD perfectly.

It seems that it just got not triggered.

[JimHugh]

You are probably tired of running back and forth...

You can run the IEC and IES on the same machine.

On PC2, configure a command like you did on PC1 that sends a IEC trigger to PC1.

That way when you use F5 on the new command, you should see Girder jump from the new command to the command being triggered.

[Torsten]

Well, not tiered of running back and forth... I have VNC installed on the computeres, that makes it much more easyer.

What tieres me more is, that it seems to be right what I did so far but it does not work. I may better take a break.

Thanks for your kind help Jim.

[Torsten]

Courious, after installing internet event server plus internet event client on both PC`s it works. :D

Thanks to all of you for your help, girder rocks and this forums as well!!!