@Gérard
I was able to get into the editor and I made the changes that were suggested, but unfortunately my Bluetooth controllers are still not working. They worked a few years ago when I originally bought my pi. I guess I’ll keep digging around on the Internet.

@YFZdude said in System xxx is missing name, path, extension or command:

@sirhenrythe5th
I've been watching several of these threads from the same user and I find it interesting to see how hard a person might work to make all these tweaks, changes and manual repairs trying so hard to save a broken installation but still be so resistant to the idea of just imaging the sd card fresh and starting over.

There are other things on the SD card like just Retropie, e.g. browsers or other tools, all of which have long been set up. Of course I have a backup of that. However, reinstalling the image is not a solution for me, if you can get the problem under control yourself with appropriate help, especially since it has meanwhile turned out that a software bug is obviously responsible for the last-mentioned problem. I may be a newbie when it comes to Linux and therefore don't have the prior knowledge like many others here, but I try to solve such problems myself as far as possible, especially since you can now read (almost) everything on the net - but only almost everything. I set up Retropie exactly as recommended by the website and did the configuration within the respective emulators - just as I have been used to for decades with the PC and the standalone emulators. I could neither guess nor understand that problems like this would arise right away. Nevertheless, I am of course grateful for everyone who helps me in such a situation. And yes, at times I was pretty boisterous, excited and venting my anger because I wasn't used to such problems. But it was never meant personally. Giving up is just not my thing. Better sleep on it for a night or two and just try again in a new attempt.

With this in mind: Thanks to everyone who helped me, even if it was just with links and references to other topics.

@sleve_mcdichael said in Escaping commands in script modules:

Is this right, though?

It is, because the filename globbing for * doesn't happen inside the quoted string:

$ ls "~/roms/nes/*" ls: cannot access 'roms/nes/*': No such file or directory # tries to list a file named '*' $ ls "~/roms/nes/"* roms/nes/240pee.nes roms/nes/game1.zip ... # filename expansion happens normally

MODERATION NOTE: I merged the 2 topics you opened. If you find your posts flagged as spam, try removing the code blocks first when posting.

Just what I needed. Thanks!

@valor852 said in Command Screen:

Where are these Raspberries?

4 Raspberries = 4 Cores = Quad Core = Raspberry Pi2 or Pi3. You see them when you boot the device.

@kenibure said in I cannot use this system correctly.:
Problem number 1:
When I try to reboot the Raspberry, the graphic interface disappear, and then appears a command console. I would have to make "sudo reboot" or "sudo poweroff", but then, the system doesn´t detect my keyboard.

I can confirm this is a common problem - especially when the program encounters a fault and exits to terminal. To properly shut down the computer I have to SSH into it and "reboot" since you can't use the keyboard hooked up to the Pi anymore at that point.

...can't help you with how to fix it I'm sorry to day.

thanks