nuhi

Quite weird INF is in the root and 32/64bit folders are separated...couldn't they separate the INF as well...ah anyway I expect it to be ok, let me know if it doesn't work as expected. Also if it isn't part of detected device then don't expect it to install. Do you understand what I mean. If this is some driver simply present only after running setup then it's to be ran after setup. If it is something that installs the detected component which is "unknown" in the device manager prior installing this driver, or it updates the existing driver, then integrate it.

It should be ok. Can you please post a link to that driver.

Since vLite currently doesn't support hotfix integration you can simply search for the information regarding Vista, it will work the same. Keyword is peimg tool.

Yes.

neuro42, great, just in time while I was thinking is it worth pursuing this weird bug. Thx.

Did you integrate chipset drivers (intel inf update) but only folders related to the system, for example "All", not "Vista" folder? Also keep Intel IDE hardware support, see if you removed some other from the HW support that might be needed as well. Btw I use this textmode driver and it worked, usually when it BSODs on the first logon it's because IDE/SATA PNP drivers didn't stick. They are automatically added once textmode is integrated. Do you have administrator privileges on that machine where you integrated the driver, nLite didn't popup any warnings?

godlike73, try this: [HKEY_CLASSES_ROOT\exefile\DefaultIcon] @="%1" @ means Default on the right in the regedit. String type (REG_SZ). You may need to reboot for it to take effect.

Reason why I still use Nero is because of the multisession DVD, it has that great refresh on "continue multisession" and it updates only the changed files so backup becomes fast and easy without the specialized backup software.

Great, keep them coming. - Nero Micro - VMWare Lite edit: anoymous_person beat me to it for the Nero

That sounds weird and I don't think that vLite caused this. You don't even remove anything if that is the real preset. I will wait if anyone else has the same issue, nothing seems to could have caused it from the preset.

ripken204, ah yes that's the only driver causing the trouble...gotta compensate for it.

killerb255, thank you. crwagner, you should not get a popup because of nLite with that configuration no matter the version, you must have done something more or at least left pages selected which you didn't use?

blaatmans, how did you conclude that? Sounds to me you simply turned off the autorun feature.

ripken204, what problem? I integrated latest nvidia into Vista x64 and it didn't popup anything, did you used 158 WHQL or 160 beta?

Yes that's what I meant. Once you put in the nLited CD from which you installed that Windows does it help or it asks for another CD?

maxkohl, you will be fine, there are some new tweaks (select all in 1.3.5, open with 1.4 and see which are unselected, they are new ones, unless some renamed), you decide if it's worth it. I reinstalled only because of the new removals. powerup, never managed to repeat that issue, open a new topic with the preset attached if you get that error. But test your driver.cab and sp2.cab with Winrar for corruption first.

Probably counters, try keeping that component in vLite.

NeoZeruel, thx. Btw. have you tried providing it with that nlited CD so that it recopies those "missing" files? You can reinitiate that with sfc /scannow

Haven't decided yet because the to-do list and the reports folder are full. I don't see what difference does it make. It is very stable, I'm currently on Vista and I haven't experienced a single issue...except that it's slower than XP nLited

wmi-core? Then no way Hose...until the WMI is component by itself gonna keep the loadperf.

railmaster7, install Vista or XP, modify the image, burn it and reinstall. Just don't activate the OS in the process until you're satisfied with the result. Just to notify you that it's possible to capture your current install, modify that image and redeploy it...haven't tried it yet but someone told me that he does it without the problem. This could be very useful, especially when new component removals are added, but not recommended in general...because if some old removal is fixed there is no easy way to adapt the change without the full reinstall from the scratch.

fede777, I meant when like with what kind of usage. Only preset in this thread is by kepademus and he don't want to even test if it is the RVM integrator incompatibility. Sivok, ok, please attach the preset with which you can get that error on a clean Windows installation files...clean, not previously nLited or by using any other tools after or before it...at least until we figure out what combination causes this.

dexter.inside, I was just planning to keep loadperf in the next one but I'll see about the possibility to remove that with it instead, thx.

I presume that's only for the selfextracting version. If Rarsoft (Winrar) had a nickel for every false report it got they would have a bunch of nickels. But this sure gives ideas...too bad I'm a good boy...or am I?

NeoZeruel, thanks for the list. But c:\windows\system32\winar30.ime, what the hell This will be tough, there was nothing to filter out since you didn't remove anything, but why is sfcfiles.dll reported as tampered, please attach your preset as well.