Thread: Re: [MiKTeX] Error message with PATH in MiKTeX Settings
MiKTeX source code moved to GitHub
Brought to you by:
csc
From: David A. <dra...@me...> - 2009-12-31 09:47:11
|
Bah, that bug's not a bug - my start menu still contained a MiKTeX 2.7 Settings icon which was what was causing the problem. More coffee required, clearly! Sorry for the noise - though my question still stands... David > -----Original Message----- > From: David Allsopp [mailto:dra...@me...] > Sent: 31 December 2009 09:32 > To: MiKTeX Users List (mik...@li...) > Subject: Error message with PATH in MiKTeX Settings > > Thanks to the useful pointers in Christian's update notes for MiKTeX > 2.8, I've just easily transferred from MiKTeX 2.7 to MiKTeX 2.8. I have > one question and one bug (and one security issue but I'm posting that > separately)... > > The question - when updating maps after using initexmf --admin --edit- > config-file I presume that I do have to run with the --admin variant > when using initexmf --mkmaps (I did, but anything to save on keystrokes > if possible!). In MiKTeX 2.9, would it be possible for initexmf to > assume --admin if it detects that it's being run elevated? UAC is > essentially fixed in Windows 7, so the only reason to be in an elevated > command prompt is because you need to be. Perhaps initexmf could have - > -user added to force user mode from an elevated command prompt? > > The bug - MiKTeX has always added its bin to the start of PATH which is > itself a security risk as no application should ever override the > Windows and System32 items at the start of path (it's almost like a > sysadmin adding "." to his/her PATH under Unix). Therefore my own > instructions for installation of MiKTeX have always included a step to > move that item further down the PATH (also because I use my own > installation of GhostScript for some commands which MiKTeX's bin > directory would otherwise override). When I start the *user* variant of > Settings I'm presented with a message "MiKTeX is not correctly > configured: the location of the MiKTeX executables is not known to the > operating system. Click OK to repair the MiKTeX configuration.". This > message is not only wrong but also shouldn't be displayed - if I click > OK then I get a predictable error because the Settings program is not > elevated. The admin variant does not produce this error message. > > Other than that, everything seems to fine to me - but then it's taken a > while for me to upgrade! > > > David |