Hi everyone, especially the experts ,

I've got a very strange complication with my unattended installation.

When the text-mode portion of setup starts to copy the main files, not much (2-10) different files (most of dlls and sys-s), are just can't be copied from the source, the setup halts and displays an error message. Retry (ENTER) doesn't work, jut the skipping (ESC). This indicates that my unattended Windows won't start the GUI part of setup, because there are missing, important files.

The interesting thing is, that these "cant-be-copied" files are not the same. They differ from time to time, but, I've noticed that from, for example, 5 times out of 10, oembios.bin and ks.sys are parts of the "bad ones".

I tried to make my unattended ISO with CdImageGui and Nero Burning Rom, each time with the same effect.

I have tested it only with MS Virtual PC 2004, but I think the situation would be the same in "real-life"(=burned out CD).

What should I do? Is my source corrupt; or the slipstreamed service pack(s) were corrupt and that made the whole thing wrong? Or I just have to try it with different iso making apps?

Thanks, if anyone can help in this matter.

Nobody has ever met with this type of problem?

I think most has had this problem especially ones that mod there OS. This is not a serious problem but can be frustrating. To correct this just copy down on paper the names of the missing files. Do a search of the sif and inf on the cd for the missing filenames then edit the names out.

OK, and thanks a lot, but I think that main drivers, oembios.bin and such are not those files whom just can be ignored. Or I misunderstand the thing?

oembios is needed for acivation, not much of a problem for corporate version.