buroja Posted October 15, 2005 Posted October 15, 2005 For my first post, I hope I've posed this question to the right sub-forum.I have a Dell OEM disc of Windows XP MCE 2005 that came on a DVD. Naturally, the desktop also came with 1001 pre-installed programs that I wanted nothing to do with. So, the first thing I did was to format & reinstall with the Dell MCE disc (which specifically noted the lack of pre-installed third-party content.) Well, it was ALMOST, but not quite, free of material that I didn't want automatically dumped on my hard drive. ESPN Motion and almost two gigs of example audio/video files were present after a fresh install. I decided to go to work. After doing some homework, reading some posts, and studying some FAQS, I found almost all the answers I needed. With nLite 1.0 RC1 by my side, I sliced and diced my OEM MCE disc, creating a fully unattended install disc that went down from ~3.5GB to 702MB. And, when all was said and done, it was a successful endeavor. The disc boots, Windows installs, and I don't have any unwanted content upon install.So, what am I here asking about? One, tiny, little, annoying issue. After partitioning and formatting the drive, while copying files to the hard-drive, XP wants to copy three OEM files which are not present on my retail copy of XP Pro: !DELL_XP.CAB, !DPCHFEN.CAB, and !PCVENXP.CAB. These three files are 7K, 20K, and 7K respectively. Additionally, they seem to be completely unnecessary and unimportant to the installation and function of Windows. When Windows asked for these files (which I had intentionally removed,) I told it to skip them and everything continued just fine from there. So, ultimately, it's just something that bugs me. I'd like to recreate my stripped-down disc in such a fashion that the Windows installer doesn't look or ask for these three files. Any ideas, folks?
Shark007 Posted October 15, 2005 Posted October 15, 2005 Edit TXTSETUP.SIF (use notepad)Find these files within txtsetup.sif and remove references to them.shark.
buroja Posted October 15, 2005 Author Posted October 15, 2005 Found and removed.Thanks very, very much.
Kelsenellenelvian Posted October 15, 2005 Posted October 15, 2005 Don't forget to look in dosnet.inf too.
Shark007 Posted October 15, 2005 Posted October 15, 2005 Don't forget to look in dosnet.inf too.This isnt required to solve the problem.yes, they are there, but wont cause an error if left there.shark
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now