Uwe Stöhr schreef op 28-3-2014 0:02:
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
To solve your MiKTeX recognition error, can you please send me the
content of your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment "Path"
Well, I assure you that miktex is in the path
I wanted to assure with that question that the PATH you see is stored
in that registry setting (there is a PATH for each user which is
stored under HKCU instead).
but I've debugged the problem myself.
The problem is that NSIS has a maximum string length of 1024
characters (including \r\n). My Path
variable is longer than 1024, so ReadRegStr returns an empty string.
Shit, I feared that this would happen sooner or later. I am aware of
this problem and tried last yeas NSIS 3.0a0 and also the stand-alone
extension. But there were too many strange other errors. Now it seems
that NSIS 3.0a2 is more stable and I can give it a try.
Hmm. you should have mentioned that to the reporters in bug #8570 ;).
Vincent
