"Setup cannot copy the file" errors on XP Slipstream disk

[webgrunt]

I created a slipstream disk with a working XP install CD and downloaded SP3. It's set up for unattended install (once you select the partition to install to.)

While attempting to use it, I get the following messages:

Setup cannot copy the file: clipbrd.chm

Setup cannot copy the file: clipbrd.hlp

Setup cannot copy the file: igames.inf

Setup cannot copy the file: mag_hook.dll

Setup cannot copy the file: magnify.chm

Setup cannot copy the file: magnify.hlp

And on and on.

Any ideas as to what I might be doing wrong? Let me know what other info I can supply which may help...

[Ponch]

I created a slipstream disk with a working XP install CD

"working" is OK, in the case of integrating SP3, "original MS" is better. Is it ?

[webgrunt]

I created a slipstream disk with a working XP install CD

"working" is OK, in the case of integrating SP3, "original MS" is better. Is it ?

No, I think I used the slipstream CD that I made from the original. I take it I should try using the original as the source, then?

[RJARRRPCGP]

This had been a common problem with nLite in the past, but, usually only occurs when installing with the "winnt.exe" method. (from the DOS prompt)

IIRC, Nuhi said that it's a Microsoft bug when installing from the DOS prompt.

Edited August 14, 2008 by RJARRRPCGP

[Ponch]

I take it I should try using the original as the source, then?

Yes. And please report.

[webgrunt]

I take it I should try using the original as the source, then?

Yes. And please report.

I will, as soon as I try it. However, the light bulb finally switched on. If I removed some windows components when I created the old slipstream disk, those files wouldn't be on the old slipstream disk, would they? And didn't remove those same components when I created the new slipstream disk from the old one, why then that would explain why the install from the new slipstream disk is missing certain files, wouldn't it?

[Ponch]

Removing files in successive nLite sessions is not a problem usually, but in my (short) experience with SP3, it seems to reset something and complains about files that have been removed previously.