I don't know if you could use the pipe " | " to pipe the terminal output to a file or the clipboard. I use this all the time but I don't know if your participation use case apply.

Do you have the comments on the same line as the commands? If so, please move them to a separate line.

See this example: Let>strLine=testLine ReadLn>C:\temp\validpings.txt,1,%strLine% MessageModal>Hi,%strLine% This will show you that the ReadLn command is assigning the variable testLine by referring to the variable strLine . Thus the message text will not work... I think, haven't tested it. :D

You're assigning the variable in the first command and referring the variable in the second command.

Do you have the folder created on the second computer?

Good you have a working solution. Not sure if relevant/helps, I played around and note that if I create and save an empty inifile2.ini in Notepad (as UTF-8), then when running your script in MS it looks ok (shows åäö). Thanks for testing. I didn't do that test but now I learned how to parse binary ...

Okay, I managed to get my server side stuff to work by moving the encoding to the front-end. I read the ini files and parse them as binary data. So I'm all right with that solution. So no immediate hurry for my sake :) I.E. I now use the default encoding (ANSI) and the non-ANSI characters are conver...

Okay, I really hit rock bottom with this problem. I want to read the INI file and lookup a folder structure based on info in the INI. The illegal characters will not work when parsing the path to the file based on text with none-UTF-8 type.

This is how I parse a ini file in JS. Perhaps something that could be done with MS? 'iniFileToObject': function(string, pipe2array = false) { let object = {}; let sections = string.match(/^\[[^\]\r\n]+](?:[\r\n]([^[\r\n].*)?)*/gm); for (let i=0; i < sections.length; i++) { let sectionName = sections...

Oh, please don't be like Microsoft then I love my INI files. They are so portable and easy to backup compared to the registry.

To devs: is this on the horizon (as in a fix)? Or should I create a separate "clean up script" for this? I would rather it be the first options since I'm relying on the ini files to only be updated if there's a difference.. this could trigger false positives since I cannot know for sure if the value...

I have a ton but it's my intellectual property so if you want my help I would need you to pay me for my time.

I don't know what the kill switch do? Can't that be manipulated using MS at a later stage?

And have you looked into widow handles? It's the numerical (integer) id of a visual object in Windows. If you find and use that you can even "click" on things not visible.

I have one controller script that is monitoring the rest plus start them, and reboot them if they get stalled. They all post info about them self to a heartbeat.ini file (PID, window handles etc). So my main ways of passing info between them are: Ini files Txt files Command line switches (when they ...

PS. and thanks for asking because I now have put this as my default action when clicking a script Never got around to do it until you reminded me.