<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1">Something like this...<br>
<br>
<br>
</font> <profile id='default'>
<br>
<package package-id='AdobeReader' os="windows 7"
architecture="x64" />
<br>
<package package-id='pidgin' os="windows xp" />
<br>
</profile>
<br>
<br>
<br>
or <br>
<br>
<host name='host-x'
<br>
profile-id='profile-reference'
<br>
os="windows 7"
<br>
ipaddresses="^192\.168\.1\..*"
<br>
domainname="^domain$"
<br>
groups="^group.*$" />
<br>
<font size="-1"><br>
<br>
<br>
See below :<br>
<br>
</font>Complete list of changes since WPKG 1.1.2 release:
<br>
<br>
===============================================================================
<br>
= CHANGES FOR 1.2 release
<br>
===============================================================================
<br>
<br>
Change notes
<br>
============
<br>
WPKG Version: 1.2
<br>
Author: : Rainer Meier <skybeam (at)
users.sourceforge.net>
<br>
Date : 2011-07-16
<br>
Status : release pending
<br>
<br>
Changes/fixes visible to the user:
<br>
<br>
Summary:
<br>
- Fixed IP-address match in case 3 "." are used in host matching
string.
<br>
- Fixed package removal procedure exception in case of /noremove
flag is used.
<br>
- Fixed removal of settings entry in case of /noremove and no
package checks.
<br>
- Allow folders to be checked with file checks.
<br>
- Allows recursive search for uninstall entries in registry
<br>
- Enhance wrapper.js to use sysnative cmd.exe.
<br>
- Disabled recursive registry uninstall checking again due to slow
execution.
<br>
- Closing STDIN when executing commands.
<br>
- Extended host matching for OS, IP, domain and groups.
<br>
- Fix for crash if interface has no IP bound to it.
<br>
- Fix for registry exist checks not returning true.
<br>
- Fix for execute test writes null values to the logs.
<br>
- Fix included aesthetic break.
<br>
- Extended host attribute match for host architecture.
<br>
- Extended host attribute match for environment variables.
<br>
- Support for host attribute matches in <package/> definitions
within profiles.
<br>
- Small fixes and optimizations.
<br>
- New /noDownload switch.
<br>
- Fixed debug mode (broken since introduced advanced host checks).
<br>
- Added extended host attribute match for package commands.
<br>
- Added package pre-check attributes to package nodes.
<br>
- Fixed ignore of lcid in package variables.
<br>
- Cosmetic fix in extended host matching debug output.
<br>
- Allow multiple packages to be installed/removed/upgraded in
one-shot.
<br>
- Allow variable expansion in file size checks.
<br>
- Fix for null-reference exception if package variable did not
specify lcid.
<br>
- Added tabular output to report.pl
<br>
- Fixed references to wpkg.org in profiles.xsd
<br>
- Fixed change log typos.
<br>
- Fixed invalid read of "uninstalldate" attribute.
<br>
- Fixed typos in comments within wpkg.js.
<br>
- Fixed additional typos in README.
<br>
- Minor usage message formatting fixes.
<br>
- Added printing of expanded command-line in debug message.
<br>
- Fixed adding of packages to local DB if precheck-upgrade=always
succeeds.
<br>
- Added extended host matching in variables.
<br>
- Added lcid matching for all extended host match supported nodes.
<br>
- Added host information to local <wpkg /> settings node.
<br>
- Using "hostname" now for extended host attribute matching instead
of "host".
<br>
- Fixed LCID extended host matching variable clash.
<br>
- Fixed termination of commands which run into timeout.
<br>
- Fixed classic host name matching.
<br>
- Added support for IA64 architecture.
<br>
- Fixed handling of failed commands with variables in path.
<br>
- Fixed process termination when command times out.
<br>
- Added sample package templates.
<br>
- Included updated Firefox example package.
<br>
- Included updated sample profile.
<br>
- Final release as version 1.2.
<br>
<br>
NEW: Updated IP matching algorithm to prevent accidental matching if
regexpor
<br>
host name is used which uses exactly 3 "." within the string.
<br>
Thanks to Stefan Pendl for reporting.
<br>
FIX: Fixed package removal procedure in case /noremove flag is set.
WPKG would
<br>
have failed (exception thrown) in case /noremove was used and a
package
<br>
is detected NOT to be installed.
<br>
FIX: In case /noremove is used and the package does not define any
checks WPKG
<br>
is unable to detect if the package is still installed or not.
Previously
<br>
WPKG was assuming that the package is not installed and removed
it from
<br>
the local settings file. This has been changed. The package
will now only
<br>
be removed from the settings file if it defines some checks
which allow
<br>
WPKG to clearly detect that the package is not installed on the
system.
<br>
So if the package does not define any checks WPKG assumes it's
still
<br>
installed on the system and does not remove its entry from the
local
<br>
settings file (wpkg.xml).
<br>
FIX: Updated "file" type checks to match folders too. Now a check of
type file
<br>
for condition exist yields true for a patch referring either a
file or
<br>
a folder.
<br>
Thanks to Joe for reporting.
<br>
NEW: WPKG now allows uninstall entries to be defined in sub-nodes of
the
<br>
uninstall registry key. I was unable to verify that Windows
supports such
<br>
entries but as reported RationalPlan Viewer seems to add such a
sub-node:
<br>
Uninstall\RationalPlan\Viewer.
<br>
There might be other programs doing the same.
<br>
During tests Windows XP and Windows 7 were ignoring such
entries but now
<br>
WPKG supports these entries now. (NOTE: Disabled again, read
below)
<br>
NEW: Enhanced wrapper.js to use sysnative directory. The sysnative
directory
<br>
allows 32-bit programs to access the 64-bit binaries within
<br>
%SystemRoot%\system32\. This way it is not necessary any more
to copythe
<br>
64-bit version of cmd.exe to the 64-bit\ sub-folder since the
wrappercan
<br>
launch the locally available 64-bit cmd.exe.
<br>
MOD: Disabled recursive uninstall checks again. Reading registry
keys
<br>
recursively is very slow with WSH and since there are typically
<br>
many sub-keys within the uninstall locations this causes a very
long
<br>
delay each time an uninstall check is used.
<br>
It's recommended to use a registry value check instead of an
uninstall
<br>
check in order to check for the status of an application which
puts its
<br>
uninstall entry within a sub-key of the uninstall keys in the
registry.
<br>
MOD: WPKG now closes STDIN when executing external commands. Some
applications
<br>
seem to wait for STDIN to be closed before they exit. Microsoft
PowerShell
<br>
seems to be one of the affected applications.
<br>
Since closing STDIN should not have negative effects (WPKG will
not write
<br>
to STDIN) it's supposed to be safe to close it.
<br>
Thanks to Stéphane Bilqué for reporting.
<br>
NEW: Many extensions in host matching. Now a host entry in hosts.xml
is allowed
<br>
to include the following attributes:
<br>
<host name='host-x'
<br>
profile-id='profile-reference'
<br>
os="windows 7"
<br>
ipaddresses="^192\.168\.1\..*"
<br>
domainname="^domain$"
<br>
groups="^group.*$" />
<br>
Note: All special parameters (os, ipaddresses, domainname,
groups) are
<br>
specified as regular expressions. Especially keep this in mind
when
<br>
specifying IP-addresses or any parameter including periods (.).
As a
<br>
period in regular expression means "any character". So keep in
mind to
<br>
escape special regular expression characters.
<br>
Note that the group attribute refers to regular Windows NT
group
<br>
membership and not to Active-Directory organization units.
<br>
Many thanks to Daniel Dehennin for continued support of this
changes.
<br>
It just almost took as long as finishing DNF to include it. <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>sigh<span
class="moz-txt-tag">*</span></b>
<br>
FIX: Included fix for bug 196 which could make WPKG crash in case no
IP
<br>
address is assigned to a network card.
<br>
Thanks to Daniel Dehennin again.
<br>
FIX: Included fix for bug 199 where registry exist checks did not
return true.
<br>
Thanks to Daniel Dehennin again.
<br>
FIX: Included fix for bug 200 where execute test fallback to
'exitcodeequalto'
<br>
in 'execute' tests writes null values to the logs.
<br>
Thanks to Daniel Dehennin again.
<br>
FIX: Included aesthetic break statement in check condition for
uninstall checks.
<br>
Thanks to Daniel Dehennin again.
<br>
NEW: Extended host attribute match now allows to match architecture
using
<br>
architecture="<arc>" attribute. The following
architectures are currently
<br>
supported:
<br>
x86 32-bit operating system
<br>
x64 64-bit operating system
<br>
Note: You will have to match x86 also if you run Windows 32-bit
on
<br>
AMD64/EMT64/x64 hardware.
<br>
NEW: Extended host attribute match allows to match environment
variables using
<br>
environment="variable1=^regexp$|variable2=regexp..." attribute.
<br>
Please note that regular expressions are matched
case-insensitive and
<br>
multiple variables have to be separated by the pipe ('|')
character.
<br>
Please also note that in case you use WPKG-client the
system-user
<br>
environment might differ from the environment you see when
opening a
<br>
command prompt and typing 'set'. Some variables might be
missing and
<br>
others might have different content. So use with caution.
<br>
NEW: Extended use of host matches. Now WPKG supports host matches
from previous
<br>
update not only in <host /> definitions but also in
<package />
<br>
definitions used within <profile /> nodes. This allows
profiles where
<br>
certain packages are applied only if specific host-conditions
match.
<br>
For example:
<br>
<profile id='default'>
<br>
<package package-id='AdobeReader' os="windows 7"
architecture="x64" />
<br>
<package package-id='audacity' />
<br>
<package package-id='pidgin' os="windows 7" />
<br>
<package package-id='firefox'
environment="NUMBER_OF_PROCESSORS=^4$" />
<br>
</profile>
<br>
This example would install "AdobeReader" only on systems with
Windows7
<br>
64-bit edition running while "pidgin" is installed on all
Windows 7 hosts
<br>
regardless of the architecture. The "firefox" package would be
installed
<br>
only if WPKG runs within an environment which defines the
<br>
NUMBER_OF_PROCESSORS environment variable to the value "4".
<br>
The "audacity" packages would be installed on any host which
gets the
<br>
'default' profile assigned.
<br>
MOD: Some smaller fixes and optimizations.
<br>
NEW: Added /noDownload option (and noDownload property in
config.xml) to
<br>
disable downloads globally. When the switch is used then WPKG
just ignores
<br>
any download specification. Use with caution as your
install/upgrade/...
<br>
commands might depend on downloaded files. So make sure that
you fetch
<br>
the files which would be downloaded prior to WPKG execution.
<br>
Thanks to Marco Gaiarin.
<br>
FIX: Fixed using of lcid="<lcid>" attribute within variable
definition in
<br>
packages. It was documented in packages.xsd but not implemented
in wpkg.js.
<br>
Fixes bug 206.
<br>
Thanks to Stefan Pendl.
<br>
FIX: Fixed bug when using /debug switch (or implicit enable of
/debug by using
<br>
/dryrun switch or config.xml flag). The issue was introduced
with newhost
<br>
attribute matching and advanced host identification in debug
messages.
<br>
Fixes bug 210. Thanks to Stefan Pendl for reporting.
<br>
NEW: Extended host attribute verification is now allowed to be used
in package
<br>
commands too. Commands which specify additional host attributes
are
<br>
ignored if one of the extended attributes do not match the
executing host.
<br>
e.g.
<br>
<install cmd="command"
<br>
...
<br>
os="windows 7"
<br>
ipaddresses="^192\.168\.1\..*"
<br>
domainname="^domain$"
<br>
groups="^group.*$"
<br>
architecture="x86" />
<br>
Note: All special parameters (os, ipaddresses, domainname,
groups) are
<br>
specified as regular expressions. Especially keep this in mind
when
<br>
specifying IP-addresses or any parameter including periods (.).
As a
<br>
period in regular expression means "any character". So keep in
mind to
<br>
escape special regular expression characters.
<br>
As a result you can use extended host check attributes in the
following
<br>
locations:
<br>
- host matching
<br>
<host name="hostname"
<br>
profile-id="profile"
<br>
...
<br>
architecture="x64"
<br>
...
<br>
/>
<br>
- profile packages
<br>
<package package-id="package"
<br>
...
<br>
architecture="x64"
<br>
...
<br>
/>
<br>
- package commands
<br>
<install cmd="command-line"
<br>
...
<br>
architecture="x64"
<br>
...
<br>
/>
<br>
<remove cmd="command-line"
<br>
...
<br>
architecture="x64"
<br>
...
<br>
/>
<br>
<upgrade cmd="command-line"
<br>
...
<br>
architecture="x64"
<br>
...
<br>
/>
<br>
<downgrade cmd="command-line"
<br>
...
<br>
architecture="x64"
<br>
...
<br>
/>
<br>
NEW: Added attributes to package nodes which allow to control
whether checks
<br>
shall be execute before install/upgrade/downgrade/remove. By
default WPKG
<br>
only executes checks before first installation in order to
prevent re-
<br>
installing a package which is already installed. Using the new
attributes
<br>
it allows you to enable these checks before
upgrade/downgrade/remove too.
<br>
For example if you use precheck-upgrade="always" and upgrade a
package,
<br>
then WPKG will first run the checks and if they succeed WPKG
will skip
<br>
the execution of upgrade commands and just assume this version
is already
<br>
installed.
<br>
Be careful when using these attributes as it might lead WPKG to
skip
<br>
upgrades/downgrades if your checks are not sufficiently
specific. For
<br>
example if your check just checks for an uninstall entry
existence which
<br>
is true for the old and the new version, then
precheck-upgrade="always"
<br>
would make WPKG believe that the upgrade has been performed
already as
<br>
the uninstall check from the updated package succeeds. So make
sure to
<br>
include some checks which are true for the new package, but not
for the
<br>
old one.
<br>
Here is some documentation on the attributes (all of them are
optional):
<br>
<package ...
<br>
precheck-install="never|always"
<br>
precheck-remove="never|always"
<br>
precheck-upgrade="never|always"
<br>
precheck-downgrade="never|always"
<br>
/>
<br>
Notes on "precheck-install":
<br>
Defines how package checks are used during package
<br>
installation.
<br>
<br>
Currently supported values:
<br>
<br>
"always" (default): When a package is new to the
<br>
host then first the checks are run in order to
<br>
verify whether the package is already installed. If
<br>
the checks succeed then it is assumed that no
<br>
further installation is needed. The package is
<br>
silently added to the host without executing any
<br>
commands.
<br>
<br>
"never": When a package is new to the host then the
<br>
install commands are run in any case (without doing
<br>
checks first). Note: Checks will still be done after
<br>
package installation to verify whether installation
<br>
was successful.
<br>
<br>
Notes on "precheck-remove":
<br>
Defines how package checks are used during package
<br>
removal.
<br>
<br>
Currently supported values:
<br>
<br>
"always": When a package is removed from a
<br>
host then the checks will be executed before removal
<br>
is processes. If the checks fail this potentially
<br>
means that the package has been removed already. In
<br>
such case the package remove commands will be
<br>
skipped.
<br>
<br>
"never" (default): When a package is about
<br>
to be removed from the host then WPKG will execute
<br>
the remove commands in any case without executing
<br>
the checks first. Note: Checks will still be done
<br>
after package removal to verify whether the removal
<br>
was successful.
<br>
<br>
Notes on "precheck-upgrade":
<br>
Defines how package checks are used during package
<br>
upgrade.
<br>
<br>
Currently supported values:
<br>
<br>
"always": When a package is upgraded the
<br>
checks specified will be be executed before the
<br>
upgrade takes place. If checks succeed, then the
<br>
upgrade will not be performed (WPKG just assumes
<br>
that the new version is already applied correctly.
<br>
Please note that your checks shall verify a specific
<br>
software version and not just a generic check which
<br>
is true for all versions. If your checks are true
<br>
for the old version too then WPKG would never
<br>
perform the upgrade in this mode.
<br>
<br>
"never" (default): When a package is about
<br>
to be upgraded then WPKG will execute the upgrade
<br>
commands in any case without executing the checks
<br>
first. This is the recommended behavior. Note:
<br>
Checks will still be done after package upgrade to
<br>
verify whether the upgrade was successful.
<br>
<br>
Notes on "precheck-downgrade":
<br>
Defines how package checks are used during package
<br>
downgrade.
<br>
<br>
Currently supported values:
<br>
<br>
"always": When a package is downgraded the
<br>
checks specified will be be executed before the
<br>
downgrade takes place. If checks succeed, then the
<br>
downgrade will not be performed (WPKG just assumes
<br>
that the old version is already applied correctly.
<br>
Please note that your checks shall verify a specific
<br>
software version and not just a generic check which
<br>
is true for all versions. If your checks are true
<br>
for the new/current version too then WPKG would
<br>
never perform the downgrade in this mode.
<br>
<br>
"never" (default): When a package is about
<br>
to be downgraded then WPKG will execute the
<br>
downgrade commands in any case without executing the
<br>
checks first. This is the recommended behavior.
<br>
Note: Checks will still be done after package
<br>
downgrade to verify whether the downgrade was
<br>
successful.
<br>
This implements a change request reported in Bugzilla report
180.
<br>
FIX: Fixed using of lcid="<lcid>" attribute within variable
definition in
<br>
packages. It was documented in packages.xsd but not implemented
in wpkg.js.
<br>
Fixes bug 206.
<br>
Thanks to Stefan Pendl.
<br>
FIX: Fixed cosmetic issue in host matching output.
<br>
Fixes bug 211. Thanks to Stefan Pendl for reporting.
<br>
NEW: Allow to specify multiple packages to be
installed/removed/upgraded on
<br>
command-line. Just specify a comma-separated list of packages:
<br>
cscript wpkg.js /install:package1,package2,...
<br>
Implements bugzilla 204. Thanks to Michael Croes for reporting.
<br>
NEW: Allowing use of environment variables in file size checks:
<br>
<check type="file"
<br>
condition="sizeequals"
<br>
path="%ProgramFiles%\%PKG_DST%"
<br>
value="%PKG_SIZE%" />
<br>
Fixes bug report 212. Thanks to Stefan Pendl for reporting.
<br>
FIX: Fixed additional issue in package variable LCID matching in
case variable
<br>
was defined but no lcid attribute was present (which should be
fully
<br>
supported).
<br>
Support for multiple comma-separated LCID values added.
<br>
Fixes bug 206.
<br>
NEW: Added tabular output for the listing to report.pl script.
<br>
Thanks to Stefan Pendl for providing the update.
<br>
Fixes bug 213.
<br>
FIX: Fixed profiles.xsd reference to example.org instead of
wpkg.org.
<br>
Thanks to Stefan Pendl for reporting. Fixes bug 214.
<br>
FIX: Fixed typos in change log files.
<br>
Thanks to Stefan Pendl for review. Fixes bug 215.
<br>
FIX: Fixed minior formatting errors in usage message.
<br>
Fixes bug 220. Thanks to Stefan Pendl.
<br>
NEW: Printing command + expanded command in debug message when
executing
<br>
commands.
<br>
Fixes bug 221. Thanks to Stefan Pendl.
<br>
FIX: Packages which were already updated by the user (detected by
<br>
precheck-update=always) were not added to the local package
database.
<br>
As a result such packages were checked over and over again for
upgrade
<br>
on each WPKG-run.
<br>
Fixes bug 219. Thanks to Heiko Helmle.
<br>
NEW: Supporting extended host matching in variables.
<br>
Fixes bug 209. Thanks to Stefan Pendl.
<br>
NEW: Added generic lcid matching for all XML elements which support
extended
<br>
host matching. Now the following attributes can be matched:
<br>
<br>
os="windows 7"
<br>
ipaddresses="^192\.168\.1\..*"
<br>
domainname="^domain$"
<br>
groups="^group.*$"
<br>
architecture="x86"
<br>
lcid="407,c07,1407,1007,807"
<br>
<br>
These matches can be used within the following XML elements
now:
<br>
<br>
In hosts.xml:
<br>
<host name="..." proifile-id="..." os="..." ... />
<br>
<variable name="..." value="..." os="..." ... />
<br>
<br>
In profiles.xml:
<br>
<variable name="..." value="..." os="..." ... />
<br>
<package package-id="..." os="..." ... />
<br>
<br>
In packages.xml:
<br>
<variable name="..." value="..." os="..." ... />
<br>
<install cmd="..." os="..." />
<br>
<upgrade cmd="..." os="..." />
<br>
<downgrade cmd="..." os="..." />
<br>
<remove cmd="..." os="..." />
<br>
<br>
Implements request filed in bug 209. Thanks to Stefan Pendl.
<br>
NEW: Added host attributes to <wpkg /> node of local settings
file (wpkg.xml).
<br>
This allows analysis tools to get some more host information
without
<br>
having to parse the log files. Example node:
<br>
<wpkg
<br>
hostname="admin-pc"
<br>
architecture="x64"
<br>
os="microsoft windows 7 professional, , , 6.1.7600"
<br>
ipaddresses="192.168.1.30"
<br>
domainname=""
<br>
groups=""
<br>
lcid="807"
<br>
/>
<br>
Fixes bug 217. Thanks to Stefan Pendl.
<br>
Update: This change did have a huge impact on test cases as
wpkg-test
<br>
performs 1:1 comparison to expected wpkg.xml files. As a result
all checks
<br>
fail. To work-around this issue unless the tests are updated I
have
<br>
introduced a configuration switch in config.xml:
<br>
settingsHostInfo=true
<br>
If set to false, then WPKG will not write host attributes to
local
<br>
wpkg.xml database.
<br>
FIX: Extended host attribute matching uses "hostname" now for host
name
<br>
matching to prevent collision with name attributes in
<variable />
<br>
nodes. Moreover this allows now to use classical "name="
attribute
<br>
in <host /> nodes as wel as the "hostname" extended match
attribute.
<br>
In addition the "name=" attribute in <hosts /> have been
declared as
<br>
optional now. This allows to use either legacy "name" matching
which
<br>
does direct literal-match, IP-address match and regexp matching
as well
<br>
as it allows to use extended host match attributes instead.
<br>
<br>
E.g. the following constructs are valid...
<br>
Classial host matching:
<br>
<host name="hostname" profile-id="p" />
<br>
<br>
IP-matching using classical name attribute:
<br>
<host name="192.168.1.1-255" profile-id="p" />
<br>
<br>
Alternative matching using extended host attributes omitting
name
<br>
attribute:
<br>
<host ipaddresses="192\.168\.1\..*" profile-id="p" />
<br>
<br>
Combining classical matching with extended host matching:
<br>
<host name="hostname" os="windows 7" profile-id="p" />
<br>
Fixes additional bugs found in implementation for bug 209.
<br>
Thanks to Stefan Pendl.
<br>
FIX: Worked around a WSH issue of variable scopes in for loops.
<br>
Fixes LCID handling of extended host matches.
<br>
FIX: Fixed termination of processes if timeout is reached.
<br>
Fixes bug 222. Thanks to Stefan Pendl.
<br>
FIX: Fixed bug that "name" attribute in host node was completely
ignored in
<br>
previous commits. Fixes classic host-name matching.
<br>
NEW: Added support for IA64 Itanium architecture. Basically this
adds
<br>
the possibility to use os="ia64" in extended host attribute
matching.
<br>
So the current list of supported architectures is:
<br>
<br>
x86: 32-bit Windows operating system running on x86
instruction set
<br>
x64: 64-bit Windows operating system running on x86-64
instruction set
<br>
ia64: 64-bit Windows operating system running on IA64
instruction set
<br>
<br>
Fixes bug 224. Thanks to Stefan Pendl for requesting.
<br>
FIX: Fixed error handling in case command execution fails AND
command includes
<br>
variables. In such case WPKG did not properly return code -1 so
the
<br>
<exit code="any" /> tag did not have any effect.
<br>
Fixes bug 226. Thanks to Bruno Choquet for reporting.
<br>
FIX: Fixed call of Terminate() method when command times out in
order to
<br>
properly shut down the child process.
<br>
NEW: Added sample package templates which might help users to build
their own
<br>
packages.
<br>
Fixes bug 225. Thanks to Stefan Pendl for sharing the
templates.
<br>
MOD: Modified included sample packages for firefox and added adobe
flash player
<br>
example. The new packages give some more insight on new WPKG
features
<br>
as provided in WPKG-1.1.3.
<br>
Fixes bug 227. Thanks to Stefan Pendl.
<br>
MOD: Modified included example profile to show os attribute.
<br>
Fixes bug 228. Thanks to Stefan Pendl.
<br>
NEW: Final release of WPKG 1.1.3-RC16 as WPKG 1.2. No further code
changes.
<br>
<font size="-1"><br>
</font>
<pre class="moz-signature" cols="72">Bruno CHOQUET, responsable du service informatique de l'IUT d'Alençon.
correspondant informatique du site universitaire d'Alençon.
<a class="moz-txt-link-freetext" href="http://www.unicaen.fr/iutalencon">http://www.unicaen.fr/iutalencon</a>
Tel : 02.33.80.85.10
</pre>
<br>
Le 21/09/2011 04:49, Mikhail Joseph Salviejo a écrit :
<blockquote
cite="mid:CAPCdMSPim+MxH=esxx2a6aGkJz-MWbUj43nzyVsaM05cy+JJ=g@mail.gmail.com"
type="cite">
<pre wrap="">Good day to all,
Does anyone knows how am I going to test whether the OS is Windows
2000, XP or 7?
The scenario is like this.
I am going to install Firefox yet some features of the package must
be not be read
if its on 2000 system (like for example 2000 does not accept taskkill)
, yet it must be read by XP & 7.
Computers here are mixed OS some still on 2000, some on 7, and many on XP.
Can anyone help me.
Thank you in advance.
Your Truly
Mikhail Joseph Salviejo
-------------------------------------------------------------------------
wpkg-users mailing list archives >> <a class="moz-txt-link-freetext" href="http://lists.wpkg.org/pipermail/wpkg-users/">http://lists.wpkg.org/pipermail/wpkg-users/</a>
_______________________________________________
wpkg-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wpkg-users@lists.wpkg.org">wpkg-users@lists.wpkg.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wpkg.org/mailman/listinfo/wpkg-users">http://lists.wpkg.org/mailman/listinfo/wpkg-users</a>
</pre>
</blockquote>
</body>
</html>