Dear,
Some feedbacks
- way of using registry is indeed a good alternative. We see three possible problems
- the HKCU-hive isn't available by W9x logging on. An alternative can be that you put
those informative to the HKLM hive.
- by using mandatory profiles the registry information we will gone during each logging
on. So each time the installation package will reinstall itself on the client with
the necessary to do it.
- with the general DOS commands you can't check the registry content. - about IF Len($destdir)=0 $destdir=@lanroot ENDIF has to deal with the possibility
that the environment variable %windir% doesn't exist. Normally it is not a
problem, but we have to deal with all kind of possibilities. - with the current network speed and with the required execution times of iexpress package
runs it isn't necessary to check each time you control file kix???.ok.
Also for a modem connection it is acceptable. - for testing the control-file in a DOS environment we are restricting to the available
DOS commands. f.e. it's size isn't such function. - we are missing the part of removing unwanted kixtart binaries, when they were implemented
with an older edition of iexpress packages. Specially when the current location isn't the
same as previous locations.
f.e.
c:\scripts\kix32.exe
c:\scripts\kx16.dll
c:\scripts\kx32.dll
c:\scripts\kx95.dll
c:\windows\kix32.exe
c:\windows\kx16.dll
c:\windows\kx32.dll
c:\windows\kx95.dll
Do you know which version it will use, when this will be the result. So removing them can
be necessary to prevent unexpected errors during using kixtart.
The reduction effort of different guys contains all kind of interesting elements.
greetings.
