H
Henry Markov
I followed the "How to Create, Build, and Debug a Windows XP Embedded Image"
tutorial. The tutorial uses the C: partition as a development partition and D:
as an image test partition. Therefore the "Program Files Folder" must be
configured as D:\Program Files in TD. However the tutorials also instruct one
not to use absolute path names when creating components, e.g. Program Files is
%16426%. When the image is transferred to the test partition, FBA'd, cloned,
etc. and prepared for remote boot the image boots up inside a C: ramdisk.
However registry entries for a test service I built have an image path of D:\
.... as a consequence of using %16426% as recommended. The service fails.
Is there a clean way to correct this problem or does one simply need to use
absolute paths when building components in order to avoid this scenario?
HM
tutorial. The tutorial uses the C: partition as a development partition and D:
as an image test partition. Therefore the "Program Files Folder" must be
configured as D:\Program Files in TD. However the tutorials also instruct one
not to use absolute path names when creating components, e.g. Program Files is
%16426%. When the image is transferred to the test partition, FBA'd, cloned,
etc. and prepared for remote boot the image boots up inside a C: ramdisk.
However registry entries for a test service I built have an image path of D:\
.... as a consequence of using %16426% as recommended. The service fails.
Is there a clean way to correct this problem or does one simply need to use
absolute paths when building components in order to avoid this scenario?
HM