[tex-live] [siepo at cybercomm.nl: Re: Error on TexLive 2013 installation - Can't spawn "cmd.exe"]

[Helge Knoop]

Sorry, I didn't get the last emails. Thank you very much for helping me!
Calling set gives me: Path=C:\Perl64\site\bin;C:\Perl64\bin  (full set 
call below)
under Control panel > user accounts > change my environment variables 
the system side PATH is the same and for the user Helge the only env 
vars are TEMP and TMP.
I did already reboot. How is the PATH env var supposed to look like?
could it be, that an update messed these env var up?
to be honest, I am a bit scared to change these, cause afterwards I 
might have more problems than now. :-(
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Helge>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Helge\AppData\Roaming
asl.log=Destination=file
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=HELGES-XMG
ComSpec=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Helge
IDL_DLM_PATH=C:\Program Files\NCAR\VAPOR\bin
LOCALAPPDATA=C:\Users\Helge\AppData\Local
LOGONSERVER=\\HELGES-XMG
NUMBER_OF_PROCESSORS=8
OS=Windows_NT
Path=C:\Perl64\site\bin;C:\Perl64\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=3a09
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
PYTHONHOME=C:\Program Files\NCAR\VAPOR\lib\python2.7
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\Helge\AppData\Local\Temp
TMP=C:\Users\Helge\AppData\Local\Temp
USERDOMAIN=Helges-XMG
USERNAME=Helge
USERPROFILE=C:\Users\Helge
VAPOR_HOME=C:\Program Files\NCAR\VAPOR\
VAPOR_SHARE=C:\Program Files\NCAR\VAPOR\share
windir=C:\Windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Am 12.10.2013 18:43, schrieb Siep Kroonenberg:
> Did you get this message?
>
> ----- Forwarded message from Siep Kroonenberg <siepo at cybercomm.nl> -----
>
> Date: Fri, 11 Oct 2013 16:51:38 +0200
> From: Siep Kroonenberg <siepo at cybercomm.nl>
> To: tex-live at tug.org
> Subject: Re: [tex-live] Error on TexLive 2013 installation - Can't spawn
> 	"cmd.exe"
> Reply-To: Siep Kroonenberg <siepo at cybercomm.nl>
>
> On Fri, Oct 11, 2013 at 04:44:09PM +0200, Siep Kroonenberg wrote:
>> On Fri, Oct 11, 2013 at 03:13:03PM +0200, Helge Knoop wrote:
>>> Hello,
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>> PATH=D:\Users\Helge\Desktop\install-tl\install-tl-20131011\tlpkg\tlperl\bin;C:\s
>>>
>>> trawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin
>> Your path looks messed up.
>>
>> What is your path in a regular command prompt?
>>
>> Also look in Control panel > user accounts > change my environment
>> variables. What are the system- and user settings for path there (if
>> any)?
>>
>> If your system path is messed up, then you can reboot and try
>> whether the system path is covered by windows' autorepair function.
>>
>> -- 
>> Siep Kroonenberg
> On second thought, do NOT reboot. If the system path is indeed
> messed up then it may be possible to manually pluck a backup from
> the registry, and a reboot may overwrite the good backup with the
> bad current value.
>