[wpkg-users] checking for 0xFFFFFFFF on a 64bit machine

Joe Konecny joe at freakyacres.com
Fri Apr 4 14:22:25 CEST 2014

We set up a package that creates a registry entry value of 0xFFFFFFFF which
regedit shows a dec value of 4294967295 on a 64bit machine.  WPKG reports
that it found -1 instead of 4294967295.  4294967295 is too large for a
32bit number so is this a limitation of WPKG assuming WPKG is running 32bit
mode?  The registry has the correct value of 0xFFFFFFFF or 4294967295.
If this is a limiation, what would be the proper way to do a check of
a 64bit number?

<?xml version="1.0" encoding="UTF-8"?>
	<package id="ipv6"

	<check type="registry" condition="equals" 
path="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters\DisabledComponents" value="4294967295" />
	<install cmd="regedit /s %SOFTWARE%\ipv6\ipv6disable.reg" />
	<remove cmd="regedit /s %SOFTWARE%\ipv6\ipv6enable.reg" />

---reg file---
Windows Registry Editor Version 5.00


2014-04-04 08:04:30, DEBUG   : The registry path 
'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters\DisabledComponents' did not contain the value: 
'4294967295'. Instead it contained '-1'. the check failed.

More information about the wpkg-users mailing list