The JVM/TI demo libraries are missing execute permissions:

$ umask 0

$ unzip /java/re/jdk/1.8.0/latest/bundles/windows-i586/jdk-8-ea-bin-b25-windows-i586-demos-09_feb_2012.zip 'jdk1.8.0/demo/jvmti/*/lib/*.dll'
Archive: /java/re/jdk/1.8.0/latest/bundles/windows-i586/jdk-8-ea-bin-b25-windows-i586-demos-09_feb_2012.zip
  inflating: jdk1.8.0/demo/jvmti/compiledMethodLoad/lib/compiledMethodLoad.dll
  inflating: jdk1.8.0/demo/jvmti/gctest/lib/gctest.dll
  inflating: jdk1.8.0/demo/jvmti/heapTracker/lib/heapTracker.dll
  inflating: jdk1.8.0/demo/jvmti/heapViewer/lib/heapViewer.dll
  inflating: jdk1.8.0/demo/jvmti/hprof/lib/hprof.dll
  inflating: jdk1.8.0/demo/jvmti/minst/lib/minst.dll
  inflating: jdk1.8.0/demo/jvmti/mtrace/lib/mtrace.dll
  inflating: jdk1.8.0/demo/jvmti/versionCheck/lib/versionCheck.dll
  inflating: jdk1.8.0/demo/jvmti/waiters/lib/waiters.dll

$ ls -l jdk1.8.0/demo/jvmti/*/lib/*.dll
-rw-rw-rw- 1 ddaugher green 28576 Feb 9 09:45 jdk1.8.0/demo/jvmti/compiledMethodLoad/lib/compiledMethodLoad.dll
-rw-rw-rw- 1 ddaugher green 27528 Feb 9 09:45 jdk1.8.0/demo/jvmti/gctest/lib/gctest.dll
-rw-rw-rw- 1 ddaugher green 45456 Feb 9 09:46 jdk1.8.0/demo/jvmti/heapTracker/lib/heapTracker.dll
-rw-rw-rw- 1 ddaugher green 28048 Feb 9 09:46 jdk1.8.0/demo/jvmti/heapViewer/lib/heapViewer.dll
-rw-rw-rw- 1 ddaugher green 151432 Feb 9 09:46 jdk1.8.0/demo/jvmti/hprof/lib/hprof.dll
-rw-rw-rw- 1 ddaugher green 42376 Feb 9 09:46 jdk1.8.0/demo/jvmti/minst/lib/minst.dll
-rw-rw-rw- 1 ddaugher green 44936 Feb 9 09:46 jdk1.8.0/demo/jvmti/mtrace/lib/mtrace.dll
-rw-rw-rw- 1 ddaugher green 26520 Feb 9 09:46 jdk1.8.0/demo/jvmti/versionCheck/lib/versionCheck.dll
-rw-rw-rw- 1 ddaugher green 30600 Feb 9 09:46 jdk1.8.0/demo/jvmti/waiters/lib/waiters.dll

Windows requires execute permissions on the .dll files in order
for the library to be executable.

When I run a JDK build, the JVM/TI demo libraries have the
right permissions in the build area so this has something to
do with the process that zips up the files into the bundle.

Update: The ZIP bundle is fine. It is the process that is
extracting the bundle and or staging the bundle into the
/java/re/jdk/1.X.Y path that is mucking with the permissions.