Script errors and goes into endless loop

Question

Script errors and goes into endless loop

blstrueb opened this issue 7 years ago · 18 comments

HI Chris - looks like you have done some great work here, but this is where your script errors and goes into and endless loop of checking for the config file. I deleted files from the .emulation station folder and restarted based on our troubleshooting, but same result. Any ideas?

System ERROR:
The filename, directory name, or volume label syntax is incorrect.
& : The term 'C:\Users\Owner.emulationstation\systems\retroarch\retroarch.exe' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At line:159 char:3

& $retroarchExecutable

+ CategoryInfo          : ObjectNotFound: (C:\Users\Owner\...h\retroarch.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Checking for config file...
Checking for config file...
Checking for config file...
Checking for config file...

Here is the log file:
lvl2: EmulationStation - v2.0.1a, built Mar 8 2015 - 16:10:39
lvl2: Creating surface...
lvl2: Created window successfully.
lvl2: Checking available OpenGL extensions...
lvl2: ARB_texture_non_power_of_two: ok
lvl2: Loading system config file /etc/emulationstation/es_systems.cfg...
lvl0: es_systems.cfg file does not exist!
lvl0: Example config written! Go read it at "C:/Users/Owner/.emulationstation/es_systems.cfg"!
lvl0: Error while parsing systems configuration file!

Answer 1 · 2017-12-14T02:54:25.000Z

Hey blstrueb,

Will try and replicate this when I get a chance.
Bit busy with work at the moment!

Can I ask if you've tried running it more than once?

Answer 2 · 2017-12-14T03:58:30.000Z

Thanks for the reply... I re-ran it several times after deleting files in the folder as described. I already have the latest mame update (192), and had already installed emulationstation when I ran the script - could that be the issue? Not ready to give up yet as this looks like a great UI. Let me know if you think there is anything else I should be checking. Thanks again Brian

…

Sent from my iPhone

On Dec 13, 2017, at 8:54 PM, Chris Franco ***@***.***> wrote: Hey blstrueb, Will try and replicate this when I get a chance. Bit busy with work at the moment! Can I ask if you've tried running it more than once? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 3 · 2017-12-17T12:56:23.000Z

Hey blstrueb!

Just ran the script on a fresh Windows 10 PC and it seems to have worked.
I suspect it has something to do with your existing installation.

Have you tried removing the entire emulation-station folder?

"C:/Users/Owner/.emulationstation/"

In-addition. Given it's looping at the retro-arch step might be worth deleting the "RetroArch.7z" file from the resource folder in-case its corrupted. Low possibility but there's a chance that that's the case.

Give both of those a try and let me know how it goes.

Thanks!

Answer 4 · 2017-12-18T02:27:32.000Z

I have not removed the entire folder, only the contents. I will try your suggestions and let you know. Do I need to have the rims in a certain directory, or does the script look for them on my machine? Thanks again,

…

Sent from my iPhone

On Dec 17, 2017, at 6:56 AM, Chris Franco ***@***.***> wrote: Hey blstrueb! Just ran the script on a fresh Windows 10 PC and it seems to have worked. I suspect it has something to do with your existing installation. Have you tried removing the entire emulation-station folder? "C:/Users/Owner/.emulationstation/" In-addition. Given it's looping at the retro-arch step might be worth deleting the "RetroArch.7z" file from the resource folder in-case its corrupted. Low possibility but there's a chance that that's the case. Give both of those a try and let me know how it goes. Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 5 · 2017-12-18T02:35:55.000Z

I assume you mistyped roms?

The script will download everything it needs to the 'requirements' folder each time it runs so you shouldn't have to worry about the files themselves.

Answer 6 · 2017-12-18T03:16:23.000Z

Yes roms - my apologies. Must take a while to download them all. I will let u know...thanks again!

…

Sent from my iPhone

On Dec 17, 2017, at 8:35 PM, Chris Franco ***@***.***> wrote: I assume you mistyped roms? The script will download everything it needs to the 'requirements' folder each time it runs so you shouldn't have to worry about the files themselves. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 7 · 2017-12-18T13:09:02.000Z

Deleted the folder, still hanging up. It does not appear to be downloading the retroarch.exe file. I can download separately - do I extract directly to the systems\retroarch folder or cores? Thanks

…

Sent from my iPhone

On Dec 17, 2017, at 8:35 PM, Chris Franco ***@***.***> wrote: I assume you mistyped roms? The script will download everything it needs to the 'requirements' folder each time it runs so you shouldn't have to worry about the files themselves. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 8 · 2017-12-18T15:11:59.000Z

Also just wondering if there are some regional issues - I am in the US...

…

Sent from my iPhone

On Dec 17, 2017, at 8:35 PM, Chris Franco ***@***.***> wrote: I assume you mistyped roms? The script will download everything it needs to the 'requirements' folder each time it runs so you shouldn't have to worry about the files themselves. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 9 · 2017-12-19T00:30:34.000Z

Can you post a screenshot of your downloaded folder 'requirements'.

Answer 10 · 2017-12-19T12:43:44.000Z

It creates the folder, but it is empty.

Answer 11 · 2017-12-19T12:50:22.000Z

Ahh ok. Could I get you to re-download the zip file then extract everything in THAT folder.

C:\requirements

Then from there, go to the script in an Admin window of power shell and give it a run.

I suspect it may have been due to problems with extra Admin permissions being required when you're running scripts directly from the root of the C: drive.

Let me know how that goes!

Answer 12 · 2017-12-19T13:08:03.000Z

To clarify, extract retroarch zip file to requirements folder?

…

Sent from my iPhone

On Dec 19, 2017, at 6:50 AM, Chris Franco ***@***.***> wrote: Ahh ok. Could I get you to re-download the zip file then extract everything in THAT folder. C:\requirements Then from there, go to the script in an Admin window of power shell and give it a run. I suspect it may have been due to problems with extra Admin permissions being required when you're running scripts directly from the root of the C: drive. Let me know how that goes! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 13 · 2017-12-19T13:09:33.000Z

Sorry didn't explain properly. The entire repository:

Answer 14 · 2017-12-19T13:41:29.000Z

Ok - I will give it a shot tonight. Thanks again

…

On Dec 19, 2017, at 7:09 AM, Chris Franco ***@***.***> wrote: Sorry didn't explain properly. The entire repository: — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 15 · 2017-12-19T22:41:15.000Z

Same result...may have to call this one

Answer 16 · 2017-12-19T22:48:55.000Z

What's your email mate? I'll PM you there.

Answer 17 · 2017-12-20T03:37:29.000Z

Working well now - thanks!

Answer 18 · 2018-02-17T15:36:51.000Z

What was resolution on this? I've got the exact same issue on my machine. I've deleted the .emulationstation and requirements folders and still get the loop on "Checking for config file..."

Edit: Looking at the script, we're waiting for emulationstation.exe to create a config file. This reminds me that before I came here, I had tried to install ES myself. Maybe I should let the script install it instead? So I uninstall ES from Apps and Features and try the script again. Still fails. Apparently, choco thinks it's still installed, so it doesn't reinstall.

So I ran the choco install with --force. And now the script gets past the config bit!

Conclusion: Step 3 needs work. ES can be missing, or ES can be present, but for whatever reason does not generate a config file. Both conditions should be handled.