Tomcat76 Posted May 13, 2008 Author Share Posted May 13, 2008 I also noticed the nLite'd file is in ANSI and that it's broken.As far as the one modified by HFSLIP is concerned... If the original wbemoc.inf is in UNICODE, HFSLIP will use FIND.EXE to remove the instances of napclientprov.mof and napclientschema.mof from that file (because FINDSTR.EXE can only be used for ANSI files). There's no other option. I'm in the process of creating an HFSLIP plugin that includes edited wbemoc.inf files for both Professional and Home, and for all languages, but that's still going to take some time.Either way, the resulting file is in UNICODE and Windows installs fine if you don't use nLite after that, so I don't understand why nLite has a problem with it. Is it that "FF FE binary string"? Does the lack of it prompt nLite to treat is as an ANSI file? Whatever it is, I don't have another option right now. Link to comment Share on other sites More sharing options...
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
Already have an account? Sign in here.Sign In Now