Hi, Markus Nagel wrote: > Hello Tomasz, > thanks for the fast reply. > The script I presented here was just an example, so I don't know if a > batch-script would do all the things I want, especially handling the > commands as packages, filling them into wpkg.xml etc. > I guess I need to create two packages then checking one condition each > and putting them together in a profile, for instance. This is one possibility. Another one is (what I usually do) - create one single package and call a batch script within the instlal/upgrade commands. This batch script can do any sort of checking and then execute the command required to apply the right software. This way you can also call external tools or programs to do additional checks. Please note that package checks are not there to check if a package should be applied to the system actually - this is something which should be handled by the profile. The checks are there to verify if the package got installed correctly on the system. So remember if you're writing a bat script whichi is copying "file1.txt" on SP1 machines and "file2.txt" on SP2 machines you need to create two checks. One which checks for "file1.txt" and another one which checks for "file2.txt". Then you can group these checks using the OR operator so the check will yield true on SP1 and SP2 machines. br, Rainer |