Problems with corrupted hv-files generated from regcomp during makeimg

Hello together,

we have serious problems with corrupted hv-files generated from regcomp
during makeimg. For building our Windows CE 4.2 image we call cepb from a
batch file during our automatic build process. For a couple of builds (about
30%) the resulting nk.bin does not boot correctly on the target device (the
filesystem does not start up correctly and the device hangs). The difference
between a "good" and a "corrupt" image is only within the .hv-file within
the flat release directory (boot.hv, default.hv and user.hv). These are
generated from regcomp.exe during makeimg from the reginit.ini file.

The difference of the binary hv-files is not only in the beginning part of
the file (where there seems to be some random information (mostly the
environment variables from the build machine), which are used for padding
the files) but also in the back of the file, where the essential information
seems to be.

We have this difference even if we call regcomp.exe in the flat release
directory ("regcomp reginit.ini .") as opposed to calling makimg (from the
same build command line).

Anyone ever had similar problems? Any idea on how to avoid these problems?
In the meantime we have changed the registry settings a little bit, so that
we have a different reginit.ini as input. The first tries worked, but who
knows if the problem appears again.

We can provide our reginit.ini and even the whole flat release directory to
Microsoft for further investigation.

Regards,
Thomas Hensler

BTW: We use PB 4.2 with the QFEs installed (which once patched regcomp.exe
already).


.

Relevant Pages

  • Re: [Q] How to speed up build process
    ... files that also get copied to the flat release directory. ... >> won't see the DLL in you Flat Release DIr (FRD) because it wasn't copied ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How to add my registry entries in the image?
    ... you can modify the .bib and .registry files and then run Makeimg. ... Manually copy the changed .bib and .reg files to the flat release ...
    (microsoft.public.windowsce.platbuilder)