I ran Midi-ox to see if Sysex messages are coming in. They do

This is the message that worked with the Midi out from the script you gave me. Button 2 transmitted this and my synth worked. fyi

message icon that says 963

No response at all when i click on F3 and try to assign

God bless you malcev! Thank you so much for tunning back in!

Trying it right now.....

mikey, do you think I made malcev upset?

I hope not. I literally refresh the page every few minutes to see when you are online! LOL

I'm very excited to get this thing going! I feel we are almost there

This is how it works exactly

https://youtu.be/YVSTOz5JutM

Please see the attach picture - It looks like my C: drive is indeed NTFS

As I understand after You click on the picture with number 2 - it will work and shows 3? How do You plan to open files manually? As I understand after You click on the picture with number 2 - it will work and shows 3? ------>That is correct!!! I believe you are referring to the hard drive. Fat32, N...

Just executing the file as a double mouse click or tap on it if I have a touch screen but nothing from the computer will execute it. I'm doing it I basically asked, how can we merge the Sysex function with the automapping script we have (I mean, you :) LOL) already made? Here's the flow 1. got to fi...

OMG!! Oh...Hi Mikey, thank you for joining here. Ok, I copy-paste the relevant message to the script I then, executed the script and click on 1 - nothing happened clicked again, the picture showed 2 - nothing happened Clicked again - and my synth responded !!!! When picture 3 was up had to click twi...

Got it

Hold on: Is it suppose to send the Sysex command out? To my synth?

I gives me a count 1,2,3,4 done! ???

It will be not easy, because as I said before there are not many ways to get event when file is opened. I do not want to write driver or rootkit. May be it can be done with parsing Change Journals. But it is only for NTFS. To send Sysex to midi You can do like this SysexMessage := "F0 00 20 29 02 0...

I'm so grateful to you and Mikey for what we have already accomplished that trust me, I have no expectation. So appreciative, really!

Trying it out now. Standby...

We have two tiny issues to make it perfect and then you better give me your PayPal email address :) LOL 1. As I originally posted, I wanted SYSex to be captured and not Note. I would love to keep both functions but the Sysex is the main function that is necessary 2. The last thing is that I would li...

OMG!!!!!!

I think it worked!!!!!

No sir,

I only wrote the file path without creating a *.INI file - I'm such an idiot LOL

Ok, this is the message i received after following your instructions
and Hitting OK

Seems more like a confirmation message than an error No?

Here you go...

I don't know if this is related but out of curiosity i checked the target folder i placed for the INI file ---> C:\Users\eladb\Desktop\TEST

I saw that no file was created

Maybe i should change to lower case folder name?

Didn't work, same error message appears

This is the message that i get - error message

- The script excute without errors
- F3 pop up open
- Midi is receiving - a midi message

Upon hitting OK - the error message appears

Got it!

Trying it now.. Fingures crossed

I'm very excited to try it.

Before I do, one final question because I didn't get it before:

What is INI file? Where is it located?

I understand how to change the path in the script but I still don't know where is it by default?