nuhi

Last one may be disabled with unattended winnt.sif

myxa, and please attach preset (last session.ini on that cd)

Fixed in next version.

Will check it but can't promise when. Thanks for reporting.

Problem is that nlite edits few infs and breakes signatures, then while sysprep installs it asks for files already there...just point it to your installed windows folder, files are there for sure. Or...don't use nlite until in changelog says sysprep fixed.

That one inf is just there to point nlite to pick up that folder. It's all in. *Someone move this to nlite forum.

It's on the cd i386 folder. Nlite doesn't patch nor removes it.

It's not SCSI drivers that are connected, it's the IDE drivers. Best would be to remove both.

dale5605, you are onto something, by removing BUS Driver nlite breaks default Windows signature for their IDE drivers and by that it makes it equal to other third party txtmode drivers...thus nvraid gains priority...now if Fernando 1 you can confirm ?

Ah...this wfp is eluding me but it should be easy to fix for few of your specific issues. You with post-install wfp popup on the first boot please attach your preset. Thanks

Fernando 1, huh still didn't work for you guys...weird...for some it helped fully. Ok, I hope we will solve this soon ... but without $oem$ if possible. Gonna contact you when I'm ready, thanks.

Here is how the things are, find driver which has nvatabus.inf in it or copy it from some subfolder when driver expanded (and all files within that folder) and just integrate, it will work. No need for $oem$, nlite already makes nldrv which is for same PNP purpose. Some users tested without any tweaking and it worked...so maybe you should all compare which nvraid versions do work "from the box".

code_blue, also for you to use winnt.sif for that you must be sure your VGA drivers are installed...if you have newer graphic adapter Windows don't have drivers in it so you must integrate it.

When you choose driver integrate and that inf withing expanded driver does it asks is it Textmode driver ?

Ok, now I would need a link to that exact driver and tell me which textmode section you choose when prompted ? Extracted driver to some folder and nothing more ?

Revo, nah not these drivers. Gonna try your preset these days and will reply if solution found...if nothing else try next version. Now rest.

It's ok to use RVM pack but then it seems you lost one of the CAT files...that's why signatures couldn't be right (for files which nlite doesn't modify). Have you repeated this, used RVM pack with nlite in one processing or RVM then nlite or vice versa ?

This log shows that you do much than nlite...first try only nlite then report if error found. And don't edit winnt.sif

I'm kinda sceptic with your reports. Especially with last statement that Xpize and rvm doesn't work...while it works for everyone else. What to say other than sorry and please report to us if you get same or similiar issue with next version (beta6), it has multiple fixes. Don't know exact date.

I see you ment that I said all hotfixes at once ? What I ment was do all at once, meaning make nlited install kit together with hotfixes all in one go...one processing, don't rerun nlite on same folder...this rule applies only in few situations, hotfixes are one.

Well that may be the cause of the problem...if I understood correctly. Do all at once...removal and hotfixes...than nlite patches few hotfixed files. And use direct integration.

razvannh,Tried before seeing your meessage and it was ok. Well why did you remove hotfixes from preset. Can you tell me which ones cause the issue and if you turn on Reports what it reports ?

Checking your preset...

For integration can't talk now...trying to introduce other method as well. As for F6...if you use Unattended be sure to turn off Oem Preinstall, it's on first page of it.

Ok then we can continue. How about ACPI 2.0 switch in BIOS, as far as I know that is needed for CPU throttling. My bios has it...gonna try as soon as Vista show all it's bits.