S y s e x doesn't work

[sylvain kepler]

Configuration :
----------------
PCwinXP sp3 <--> Ethernet <--> MAC pro 8c. <---->Amt8<----> h.w. Synth

Latest version of MolcpIII installed on MacPro and PCWInXP. Properly configured
Midi PatchBay also installed on the Mac , so I can forward signals from Midi AMT 8 interface to MolCpIII and the opposite.
MolCPIII monitors (mac and pc) show correct indication when information goes in and out (green and red 'leds')
Can send midi s y s e x messages from PCWinXP (from SoundDiver v3.0.4);
Values or any modified parameter are seen and implemented on the hardware synth to be edited.

However, I cannot receive s y s e x Midi messages from the synth provided manually or requested remotely by sounddiver.

In a few words, s y s e x goes fine from Sounddiver to the HW synth, but not in the opposite way.

It's really puzzling...(please not also I deactivate firewalls on both machines) Tried both cases were a single molcp port handles midi in and out signals , also using 2 ports with a midi direction each. Played with all the available parameters onboard, timeouts values etc. No joy.

Any help on this issue welcome.
Thanks

[sylvain kepler]

Well, I 've somewhat wasted a couple of days this week trying to solve the problem about s y s e x ...

I actually recently realized that , using another mean I won't advertise here with respect, molcp3 was indeed in fault and caused those troubles
I took me a quarter to succeed another way, but applying the exact same 'structure'. Say I put fuel in a car, one goes foreward and the other remains static.

So may I suggest musiclab to come back to me and try , anyway, to solve this issue in case I'm in fault by having mishandled or not properly set a hidden parameter hidden somwhere in the "deep field" of my interfaces but not explained in the manual ...just to be comforted I have not actually wasted my money nor my time with that tool ...