On 2018-06-05 08:00, NagyMusic wrote:
Thanks, Aaron. I really appreciate you taking the time to help me with
this.
The Windows 10 built is 17134.81
I was able to locate the lilypond.exe file in the bin; there's also
lilypond-windows.exe (not sure why; this is the .exe file included in
the
Frescobaldi path).
I copied the lilypond.exe path into CMD as you suggested: "C:\Program
Files
(x86)\LilyPond\usr\bin\lilypond.exe" and got: GNU Lilypond 2.19.80
(this is
the correct version that I installed and use with Frescobaldi).
I included the same path in Environmental Variables (removed the
quotes),
restarted the computer, attempted again to call lilypond --version, but
got
the same message:
'lilypond' is not recognized as an internal or external command,
operable
program or batch file.
Let me know if there's anything else I can do. I can certainly
uninstall-install Lilypond if needed.
Glad to hear that we got at least one good result. But it is looking
like this is not really a LilyPond issue in particular, though. If we
cannot suss out the underlying issue, it might be better to move the
conversation to another forum.
Just to make sure, when you included the path, did you also strip
`lilypond.exe` as well? The path should only ever contain folder names.
So, for instance, yours should start with...
C:\Program Files (x86)\LilyPond\usr\bin;
...with the remainder of the path afterwards.
Also, I am not sure you need to reboot the machine after an environment
change anymore. In my experience, you can just close and reopen a
program (like the console window) and it will see the new setting. Of
course, you can easily verify that by printing out the current
environment and ensuring the folder you want is in there.
Otherwise, I am not sure an uninstall/reinstall of LilyPond will fix
things. If you want to try it, it shouldn't make things worse. But
this issue is sounding deeper than LilyPond, and I would be hesitant to
suggest anything more drastic (i.e. a system reset). Other
possibilities to look into:
- User account issue... Are you running the console window elevated by
any chance? If you are setting the "USER" version the PATH variable, it
might not be applying when the console is running as admin. Granted, I
would normally not recommend changing the "SYSTEM" PATH, but it might be
worth trying.
- Some console autorun messing with the path... There is a registry key
that lets you auto-run programs when you start a command window.
Perhaps this is configured on your machine, and it is overriding the
normal path. If you run `cmd /d`, it will disable any autoruns. You
can then run `path` from that window and you should see the values as
you configured through the Windows UI if they were not showing up
before.
- Virus/malware... Some folks online tend to jump the gun and proclaim
any odd behavior as an infection. But if we make it this far in the
troubleshooting, it would be prudent just to make sure your AV software
is up-to-date and you have a good clean system.
And that just about hits the limits of my IT helpdesk knowledge. If you
are still hitting an issue, I apologize I wasn't able to offer more
help. Though, if you go back to searching online, you can at the very
least widen your search by looking for similar issues with other
programs.
-- Aaron Hill
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
