Manfred Zindel

Here are four screenshots of KISS.lgo already containing procedure GETWORKINGDIRECTORY.

Hello David - I`m sorry I couldn't answer your post earlier, but now I have good news: I built the first of your proposed procedures into the preparatory part of KISS.lgo, and it solved the problems all at once. KISS.logo now covers more than 70 procedures and some libraries which are still growing. And the whole program, that appears complicated enough, now seems very stable. As I have decided to include some aspects of A.I. into the tutorial, I'm still working on it, which will have to appear in...

And here is the error message that flashed away all the time: C:\Users\Manfred\Desktop\KISS 2026-06-09>_start_Super_Vision_8K.cmd C:\Users\Manfred\Desktop\KISS 2026-06-09>echo C:\Users\Manfred\Desktop\KISS 2026-06-09 | clip 'clip' is not recognized as an internal or external command, operable program or batch file.

Addendum: I found out that clip.exe is not only missing in this project, so it perhaps is the reason. All the other computers go on with KISS.lgo in a stable manner, and so, while the main computer is going to be repaired by somebody who is well trained as an administrator and knows the inside world of Windows, I'll switch to another computer which has no such problems and go on with my AI project in KISS.lgo, which can also be done in pure FSLogo. I hope it proves to be be successful.

It now seems as if clip.exe isn't found neither by the script nor by any other method. It exists in Windows\system32, but something may be wrong with the environment variable, and as I never was an administrator, I don't know how to repair things like these. I had the seemingly simple idea, FMSLogo itself could provide the root path, as it really is part of the container. If I write POPDIR at the beginning, I get exactly the information I need, but only in the console, where I can neither store the...

Thank you very much, David, for having a look at the problem. Fact is, that the same program was the basis for everything we tested in schools, and it always worked for over two years, week by week for many interesting applications.. Now, without having changed it, it ceased working on one or the other Windows machine - that means, extracting and using the current root path failed. And I wonder what might be the reason. Well, what I'm going to do next is, to do some "modularization" for KISS.lgo,...

No,I don'see the FMSLogo window, only the scipt for a little moment, thereafter nothing.

Well, I reduced the problem by creating a program that only consists of the starting script an a small file enter.lgo, which only says "Here I am". All the huge rest is gone. And what happens? This time the failure is observed on all computers. "Here I am" is not shown. Now I created a "micro_Container" (which is no container anymore) and zipped it. I send it now.