floyd8673 Posted February 1, 2007 Posted February 1, 2007 HelloI am trying to integrate the Intel Graphics Drivers into my XP install. I downloaded the file Graphics Driver [WIN2K_XP142550.EXE] from Intel's website that supports a wide range of integrated graphics. It has a single .inf file that handles everything. The actual n-lite process goes without a hitch however when I goto install Windows (using a VM) at about 98% I get a bunch of errors about corrupt/missing files on the cd. All of the missing files are actually language files (i.e. igfxrara.lrc 'Arabic language resource file', etc.....)Has anyone encountered this error?Thanks!
hulkviper Posted February 1, 2007 Posted February 1, 2007 same here!edit the inf file and keep the lang you need and english
floyd8673 Posted February 1, 2007 Author Posted February 1, 2007 When you say edit the inf, I take it you mean either delete or comment out all references to the languages that I don't need, right?Been there, done that, no go, I still get the same error. I also tried commenting out the 'Generic language reference file'I use a fresh, virgin copy of the XP files every time I mess with it.
hulkviper Posted February 1, 2007 Posted February 1, 2007 if Ir remember correctly the lang file extension is lrcsearch for .lrc in the inf, remove all you do not need.........
floyd8673 Posted February 1, 2007 Author Posted February 1, 2007 Ah ha!Removing all references of *.lrc (except for the enu one, as its the english file) from the INF didnt fix the issue.However, removing those lines AND removing the files themselves seems to have cleared it up.Odd, eh?
hulkviper Posted February 2, 2007 Posted February 2, 2007 I thought that was obvious but yes it is odd!English only is ok, most of us don't use the intel software anyway
MatthiasGoodman Posted February 22, 2007 Posted February 22, 2007 I have the same problem and I think it must be due to how nlite compresses the files.
nuhi Posted February 24, 2007 Posted February 24, 2007 It was PE header checksum, they didn't have it corrected in those files but nlite can do that for you automatically.Fixed in next version.
Gladiac Posted March 1, 2007 Posted March 1, 2007 It was PE header checksum, they didn't have it corrected in those files but nlite can do that for you automatically.Fixed in next version.I also had that problem... You can fix it manually using modifype.exe
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