Files
admin
base
basedrv
boot
busdrv
cluster
cmd
crts
ddk
dload
dloadhandler
efiutil
eventlog
firmware
fs
fsrec
hals
headless
inc
mspatch
mvdm
ntdll
ntdllsym
ntos
ntsetup
_winnt
basewin
billbrd
bmps
bom
books
bootent
cfgmgrf
complnce
ansiuser
comptest
asrv.dat
asrv51.dat
comp.dat
compconv.pl
compfile.cpp
compfile.h
comptest.cpp
dtc.dat
dtc51.dat
makefile
per51.dat
per51cn.dat
per51raw.dat
pro.dat
pro51.dat
pro51cn.dat
pro51raw.dat
readme.txt
section.cpp
section.h
sources
srv.dat
srv51.dat
strutil.h
template.dat
kernel
pidinit
uniuser
compchk.c
compliance.c
crcmodel.c
crcmodel.h
dirs
sources.inc
encrypt
eulas_etc
excppkg
hives
hwdb
hwlog
inc
inf
legacy
libmsg
localinf
migdlls
moricons
mpk
msoobci
ntcab
ntoc
ocmanage
oeminf
oempre
oemtools
oobe
opktools
patch
patchdll
patching
pencrypt
pidgen
pnpsif
readme
setexts
setupapi
setuplog
setupmsi
srvpack_binary_release
stripinf
svcpack
syssetup
testtool
textmode
tools
undostub
updatemsi
win95upg
winbrand
winnt32
dirs
sources.inc
pnp
published
qfe
remoteboot
screg
seaudit
strsafe
stublibs
subsys
testlockout
tools
urtl
wdmdrv
wdmlib
win32
wmi
wow64
xip
zlib
dirs
prerelease.inc
project.mk
com
developer
drivers
ds
enduser
inetcore
inetsrv
loc
mergedcomponents
multimedia
net
printscan
public
published
sdktools
shell
termsrv
tools
windows
dirs
makefil0
2025-04-27 07:49:33 -04:00
..
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00
2025-04-27 07:49:33 -04:00

This test harness helps in testing the compliance
matrix without creating the actual media.

It parses a text file which specifies the matrix
in sections. 

Each section name starts with '[' and ']'. The '#' 
character is used as string separator.

Some well known sections are [type#values], [var#values],
[suite#values] and [error#vaules] etc. These sections 
define keys which can be used in the actual testcase.
For e.g. [type#values] defines "pro=0x40" which indicates
that product type professional's internal representation
using DWORD is 0x40.

The value sections need to be at the start of the
test matrix text file. The other kind of sections 
which can be present in this test case matrix file are
called "Test Sections". These sections contain the actual
test cases.

For e.g.

[test#pro#5.0#2031#none#retail#fpp]
win3x#3.1#950#none#any=typeerr,no
win9x#9.5#950#none#any=none,yes
ntw#3.1#1057#none#any=vererr,no


indicates that the sections is for testing professional, 
version 5.0, build 2031, with not product suites and is
of type FPP retail variation. Each line in this section 
indicates the target platform for which this media needs
to be tested for upgrade. 

For e.g.

win9x#9.5#950#none#any=none,yes

Indicates that Windows 9X, version 9.5 and build number 950
with no product suites and of type any variation needs to
pass on upgrade with this professional media. 

Another e.g.

ntw#3.1#1057#none#any=vererr,no

Indicates that NT workstation version 3.1, build number 1057,
with no product suites and of type any variation, needs to
fail on upgrade with version error with the given professional
media.