I told you exactly what I did...
1) boot windows 2000
2) insert XP CD with integrated driverpacks
I know it basically has already been said, but I need to stress this once again:
Both nLite as well as the DriverPacks, besides being created for the UNattended installation (yes, we all are that lazy ), are intended ONLY to be booted from the disc you created with (reason why nLite allows you to directly brun a bootable disc, btw).
Because of entries in the Windows setup information files, WHEN booting fro mthe disc, an upgrade installation is no longer possible!
This is done so deliberately and is an option provided by MS themselves (tells you that you probabaly shouldn't mess with it).
If you still do an in-place upgrade as you did, you do not have to be surprised it did not work as intended.
Firstly, as has been said, you need to boot from the disc you want to install, and secondly, I know NOONE around here or any other unattended install forum, that would actually even just CONSIDER doing an in-place upgrade.
It simply has just NEVER been done so we wouldn't even know what could happen.
This brings me to the next point: Backup.
Because you are venturing into the great dark unknown with that in-place stuff, you desperately NEED to backup (or you do not value the data, in which case you could have just formatted and properly and unattended installed...).
Well, and if you run a backup anyway, what's then still keeping you from installing from scratch, thereby avoiding any conflicts, incompatibilities or useless legacy files taking away space from the drives...?
Point is, I couldn't think of a case were an in-place upgrade would be justified or even practical.
I simply want to "clean up the mess" at this point. A simple list of files to delete from the root of my hard drive would have sufficed instead of a verbal assault.
In this case, if you really want to clean up, reformat.
Who know what else has been messed under the hood and has just not shown itself.
You may encounter further issues down the road, then you will have to reinstall anyway, just my advise is to do that now so you get a clean start.
Also, as to files you can delete from %systemdrive%, let's go the other way round, list those that you MUST keep:
bootfont.bin
NTDETECT.COM
AUTOEXEC.BAT
IO.SYS
MSDOS.SYS
config.sys
ntldr
boot.ini
hiberfil.sys
pagefile.sys
Those files should be hidden by default (and marked as system files!) anyway so if you delete everything that's visible, you are save to go.
What I did, while not officially supported, does seem like something people might want to do.
As I said, I know of noone who would ever want to do an in-place upgrade, so I doubt that...
Even then, if they want to do it, we aren't stopping them, we just don't support it.
If I had encountered that, I would have known what to do. As an end user, I never expected it to dump all the files into the root of my hard drive and it caught me off guard. As it was, I had no way of knowing what went wrong or how to solve it.
The DriverPacks are mainly for experienced and/or power users that want to increase their possibilities with an unattended install.
That means, they already know what an unattended install is, have read the guides and msfn.net and have a basic knowledge about system setup.
MSFN.net guide tells you how to manually add selected drivers to your install (quite close to M1 in our case), DP adds support for virtually any device, so it's a step to the next level (or over-next rather).
Folks that do this usually KNOW what files are needed in %systemdrive% and what can be deleted, so it's a non-issue.
Also, it is rather known around here what the Finisher does (cleanup, among other), so, it should be kind of logical that a manual execution of the Finisher, during an attended install no less, could possibly bring the desired results...