yeah you lied... Every single tutorial we have says in big bold print "no changes after DriverPacks".
I asked and confirmed this with you several times... you were adamant you made no changes after DriverPacks. (a lie)
Please realize that Helmi's directions are spot on Identical to what you originally told us you were doing.
I will say it again: If you would have done what you told us you did...
It WOULD have worked without issue, and you would not have needed to post here at all...
the fact is you did made changes (with nLite) after you slipstreamed DriverPacks and you definitely lied about it several times.
had you told the truth from the beginning (I run DriverPacks first then nLite...)
We would have solved this issue in one post 
but you simply refused to admit (until post #20) that you did not follow the directions.
please note: Your issue was solved in post 21. (the very first post after you told the truth)
edit....
Please consider...
There was no need for Helmi, or anyone else, to explain the steps to you like you were a child...
NOT UNTIL AFTER You finally admitted that you made changes to your source after slipstreaming the DriverPacks.
Helmi's simple instructions have been posted, verbatim, by me personaly many times.
There was simply no need to do so until you stated that you made changes with nLite after DriverPacks.
Also consider...
Had you done something else, other than nLite, after DriverPacks Helmi's instructions would not have helped at all.
It was only your admission that IT WAS nLite that you ran after DriverPacks that made his instructions useful...
please also note you can run nLite after DriverPacks as long as the ONLY thing you do is create ISO.
If you make ANY changes at all with nLite after DriverPacks then your source is FUBAR.
In this case because nLite deleted and replaced the winnt.sif after DriverPacks edited the winnt.sif.
Had you done your steps in the proper order (per our tutorial)... you would have been successful every time.
We already knew that nLite will delete an existing winnt.sif... Therefore we must always be after nLite 
.
DriverPacks last is plastered everywhere for a reason. Actually lot's of reasons... but this one is as good as any.
That is why we provide our tutorials, in order to avoid support issues.
end edit...
We have been doing this for many years, I knew from the very start you had to have changed something after DriverPacks.
We were at a loss to be able to help, until you told us what you did after DriverPacks.
The truth is that you absolutely DID make changes after you ran DriverPacks.
(And it only took twenty posts to discover that it was with nLite)
ANY one or all of our users could have solved it after that revelation...
Statistically speaking there was only one possable answer - ID ten T + PEBKAC
Last edited by OverFlow (2009-12-11 20:06:39)
