#72765 - 2003-01-28 10:13 PM
Re: SETM problem in 4.12?
|
Glenn Barnas
KiX Supporter
   
Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
|
Yes. My account is a Domain Admin, and I'm in the Admin group on my PC - where I've been testing this today.
I've seen the failure on my XP workstation at home this weekend as well. This is a standard server/workstation customization script that I've used for some time on better than 100 servers here at work. Only after upgrading our deployment copy of Kix did this problem arise.
Here's what we do:
A "Customize" folder has a kixtart.kix file that performs some simple customizations.. edits boot.ini for a 5-second boot delay, creates C:\usr\local\bin folder, copies the contents of CUSTOMIZE\TOOLS there (kix, xnet, blat, psinfo, pslist, pskill), adds that directory to the system path, and defines the prompt. There are a few simple registry additions as well, associating .KIX with notepad, and updating the PATHEXT to include .KIX.
There is a bat file - INST.BAT - that invokes TOOLS\kix32.exe - this automatically invokes the copy of Kix32 that will be copied to the server to perform the copy, and defaults to the kixtart.kix in the same directory as the INST.BAT. It's really simple, and consolidates several functions that used to be done manually.
Ever since I replaced the CUSTOMIZE\TOOLS\kix32.exe with the latest version, the environment values no longer updated properly. Today is the first time I've had a chance to look into the behavior. It's clear that SETM is updating the HKCU\Environment key instad of the HKLM\SYSTEM\CurrentControlSet\Control... key. I've updated my test script to write similar values to the same registry key and that works (wrote TEST_PATH instead of PATH). Registry security is NOT an issue.
Glenn
PS - here's the test script I'm running.. ? "@KIX" set "TEST1=one" setl "TEST2=two" setm "TEST3=three" shell "cmd /c set > x.log"
$ENVKEY = "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment"
$TMP = "%SYSTEMDRIVE%\usr\local\bin;" + %PATH% $RTN = WriteValue($ENVKEY, "TEST_PATH", $TMP, "REG_EXPAND_SZ")
After running it, you should see the TEST1 / TEST3 variables in the HKCU\Environment key, when TEST3 should be in the HKLM path. The TEST_PATH is created in the proper location.
_________________________
Actually I am a Rocket Scientist!
|
Top
|
|
|
|
Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 1574 anonymous users online.
|
|
|