Asmer Posted December 22, 2007 Share Posted December 22, 2007 Everything works great! nuhi, thank you very much!!! Link to comment Share on other sites More sharing options...
nuhi Posted December 22, 2007 Share Posted December 22, 2007 Oh great So now gotta see why. Didn't look like a big mistake at first glance so it's probably some new file or they added it to some other INF.chris, in setuperr.log. Link to comment Share on other sites More sharing options...
ricktendo Posted December 22, 2007 Share Posted December 22, 2007 Im having the same issueOh great So now gotta see why. Didn't look like a big mistake at first glance so it's probably some new file or they added it to some other INF.chris, in setuperr.log.Correct I think so also, because the error ocurs during "Copying Files" part of the install (it jumps straight to Start Menu Items) which tells me its probably a CopyFiles error in a INF or a missing INFIt happens pretty early in the Copying Files too, so it should be easy to find Link to comment Share on other sites More sharing options...
chris.b Posted December 22, 2007 Share Posted December 22, 2007 Hmm in setuperr.log there was only the usernv.dll thing. Should be something in setup.log too? Link to comment Share on other sites More sharing options...
nuhi Posted December 22, 2007 Share Posted December 22, 2007 chris.b, you tell me. I haven't fixed it yet. Gonna try tonight. Link to comment Share on other sites More sharing options...
chris.b Posted December 22, 2007 Share Posted December 22, 2007 Maybe you missunterstand me I kow you can not fix this over night. I just wanted to know where in the setup.log or setuperr.log you see that the security center causes the problem? You see what I mean? Link to comment Share on other sites More sharing options...
nuhi Posted December 22, 2007 Share Posted December 22, 2007 I just saw common components in the presets and tried it until the error log was clean. No magic. Link to comment Share on other sites More sharing options...
clavicle Posted December 24, 2007 Share Posted December 24, 2007 (edited) @nuhiI also seem to have a lot of problems while nliting sp3 3264. The comodo firewall addon v.276 didn't work and many other things were broken, like no iexlporer, no quick launch etc. (Addons may need a more refining as you said).But when I replicated same lastsession.ini with earliest sp3, ie, 3205 (as I have deleted my 3244 sp repository), I found I had no problem whatsoever which I faced using sp3-3264.I even tried not using IE7 and WMP11 addons also.Last_Session_3205_.ini Edited December 24, 2007 by clavicle Link to comment Share on other sites More sharing options...
boooggy Posted December 24, 2007 Share Posted December 24, 2007 clavicle u have to keep security centerdont remove it and all probs will be gone Link to comment Share on other sites More sharing options...
clavicle Posted December 25, 2007 Share Posted December 25, 2007 @nuhiThanks, firstly I missed your earlier advisory, but later I used it with security centre selected. But still I found my bits of problems like, my raid drives keep getting installed even after second reboot and theme not getting applies. I think these are minor problems, which will be taken care of.Thanks and merry christmas! Link to comment Share on other sites More sharing options...
xnguard Posted January 15, 2008 Share Posted January 15, 2008 (edited) Hi, I'd just like to add that I'm experiencing issues with 3264 and nLite as well. I used nlite and 3244 with no problems, but I can't make a working 3264-slipstreamed install (en_US). I've tried with and without the 3244 presets; I've tried with and without integrated drivers; I've tried with and without integrated hotfixes.What I keep getting is an XPSP3 install that works fine -- no errors at all during nLite's run -- until I try to get sound working on the XP install. The drivers (Sigmatel HD audio on Intel G945) insist that there's no supported hardware present, and the Windows device manager claims that there's an "Unknown PCI" device that I can't install any drivers for.About the only thing I haven't tried is a slipstream of SP3 with no nLite usage whatsoever. That's next.ETA: I'd like to provide logs/presets, but I'm using this in a corporate environment with some sensitive things in the presets, including the corp product key, and I don't have the time to go through the logs or presets and remove the things that corporate security wouldn't want me giving out. Sorry. Edited January 15, 2008 by xnguard Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted January 15, 2008 Share Posted January 15, 2008 ETA: I'd like to provide logs/presets, but I'm using this in a corporate environmentNLITE IS NOT FOR CORPORATE USE!!! Link to comment Share on other sites More sharing options...
xnguard Posted January 15, 2008 Share Posted January 15, 2008 (edited) ETA: I'd like to provide logs/presets, but I'm using this in a corporate environmentNLITE IS NOT FOR CORPORATE USE!!!Yep, that's why I haven't told Desktop Support that I'm using it. ETA: Actually, I should clarify that: personal laptop. Edited January 15, 2008 by xnguard Link to comment Share on other sites More sharing options...
xnguard Posted January 15, 2008 Share Posted January 15, 2008 Well, I haven't figured out why nLite isn't integrating hotfixes or drivers properly with SP3 3264, but I found my own answer for why I couldn't install sound drivers. There's no UAA support in SP3, none planned before RTM, and the existing UAA hotfix that's included with most HD audio drivers (like the Sigmatel HD) refuses to install on SP3.So, that, at least, isn't nLite's fault.(I'd like to know why SP3 includes SDHC reader support, but not UAA, considering how many more systems have UAA audio devices than SDHC readers hanging off a native system bus.) Link to comment Share on other sites More sharing options...
deda Posted January 15, 2008 Share Posted January 15, 2008 Guys, like Vista SP1, this Service Pack has some "tools" against piracy. There are a file, wscenter.mo_, that isn't updated by the Slipstream if you're using a known bad key. Try to see if it's present on i386 folder after the update. I discovered this because I use IIS and when I tried to install it, the file was missing. Link to comment Share on other sites More sharing options...
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