Jump to content

nlite and driverpacks compatability


Recommended Posts

Posted

I had a quick question...

After looking around on these forums it seems to be the general consensus that if you want to use driverpacks and nlite together you run nlite first, then driverpacks second. However, when I do this I consistently get the windows textsetup asking for missing drivers, fonts, and other components that I removed in the nlite component's section. Usually says something like, "Setup cannot copy the file: xxxxxx.dll". Obviously, nlite has removed this dll and that is why it cannot find the dll to copy.

My question is this: is it possible that driverpacks is putting entries for these dlls back into dosnet.inf and layout.inf? Are these two files the files that the textsetup looks at to see which dlls it should be copying? Should I be integrating the driverpacks first and then nlite second if this is the case? Is there some other way to handle this other than waiting for each prompt and then deleting the proper entries?

I know that previously a lot of the active members here referred people to the driverpacks.net website. Just to clarify I'm only asking here to see if anyone here has heard of something similar, or had a similar experience that they might be able to draw from and help me. I feel like you guys might have a better idea of how nlite and the other tools integrate together than other people and other sites.

Thanks for your time!


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...