nuhi

DigeratiPrime, but I already did that, that's how those sizes got there. Thing is for the ISO size you got to rebuild the image and make ISO for every single component removed. I find that hard to maintain and unproductive. Even if someone gives me the whole list I would need to do the same whenever the component is changed or the new one is added. Maybe I could add some sort of rounded value by dividing the file size, like if 4GB will be removed, and that is 4/7 of the whole size then the ISO might be 4/7 too. What if someone integrates drivers...oh c'mon people just quit with this...

Objectively while we don't do anything illegal like cracking protections it's ok, but as far as I know in some states you can't even backup your own Windows CD. Majority of enthusiasts edit their installation cds today, it is silly to ask us not to do it. And just look at the Microsoft WAIK tool, which essentially answers your question. We probably can have 1 backup CD, it's now different with Vista than it was with XP...it's up to you to obey those things if you must.

Now you really got my attention. But you know I use XP SP2 too and never got that issue...well it was there during development when WIM of Manager weren't working properly. Do you install all critical updates (hotfixes) ?

Stead, ok noted pallavsuri, lol, so you expect me to actually rebuild and make ISO for every single component removed, then do the same for every Vista version out there...good one, very grateful you are my young padawan.

Since it is also a scanner WIA is a must. Start reading descriptions.

How about you start reading descriptions. You can also start installation from the hard disk, that way you don't have to remove what you don't want, unless you have DVDRW.

Don't sweat around it any more, if the reinstall didn't help once then it won't. Do you have some antivirus resident, try disabling it...but that helps in other scenarios, this one is bizzare. Oh I forgot the basic question, which Vista it is, the exact version (you can read it on the vLite Start page after browsing) and language.

No, not the Tablet, at least not since last few versions, that was the bug in the first versions. pallavsuri, did you remove Windows Mail? And why do we have to guess, attach the preset.

Which is that? Don't tell me HTML Engine?

1. Administrator. 2. That DWM service is quite heavy. Also you might get tired of the glass and want the old snappy forms. I change themes every now and then and eventually go back to classic since then I don't need to think what is what. (micro seconds, micro seconds!) 3. x64 supports more than 4GB of ram which will soon become standard. 4. Biggest languages are removed, other left are tiny in comparison. 5. Tcp yes, DX no.

Weeird...but anyway I'm glad it works.

Beta nVidia driver, like newest leaked, not on their official site...they are quite often. Well Windows usually skip those while installing Windows and install Standard VGA driver instead. Then we remove it and thus force it to take the beta.

Great. Silently updated it to block spaces in computer name. You may redownload or simply skip spaces, nothing else updated.

Dynaletik, why would I be annoyed by that. It is weird to post bug report here, makes more clutter...lock new version topics next time? I'll think about it. Anyway tell me what does it pops up or how do you experience the issue?

No problem.

I just read it. Ok noted. Since nLite needs a critical fix or two it will be out in wednesday probably. I'll try to check this too. But you could also use nlited x64 and install IE7 after, I don't see why you think that the whole deal is off if one thing doesn't work, it's luxury if you ask me. Anyway don't get me wrong I appreciate the report and will try to fix.

http://www.msfn.org/board/index.php?s=&amp...st&p=164361 ?

By all means do that, just no need for multiple folder, it's single driver, select any inf from it while inserting. If it is not WHQL signed then remove default Windows Display Drivers and it will install the betas as well.

Extract nlite.in_ it's in there, just search your name and remove lines with it. Then delete nlite.in_ and just put extracted nlite.inf there, no need to compress.

pallavsuri, you posted here again, oh man you test my patience. Anyway here is something that may interest you: http://www.msfn.org/board/index.php?showtopic=97327 Clint, hi, you're right on the money.

Ok it seems it's the Computer Name, shouldn't contain spaces, but maybe it's doable with some other way. Anyway try some Computer Name with one word, or like AMD641800+ Do you understand? I tested it moment ago and it did help by removing spaces. edit: I just saw your post, try first this without spaces then we'll see about that.

Thank you for reporting, checking. If you don't want to wait then you can skip Unattended by deleting Autounattend.xml from the folder and just remake ISO.

Aaa you have File Protection enabled. Well then I don't believe it's Filter Manager problem, should be only WIM. It didn't help I presume...well then try searching on this forum, people with this error just say: "I reinstalled my Windows and now it works". Very weird bug.

You should reinstall WIM and Filter Manager for starters. Then are you Administrator on that xp sp2 machine? Anyway first delete C:\WINDOWS\system32\drivers\WimFltr.sys and restart vlite. Then tell it to install WIM if it prompts (it should). If it fails again the same then delete C:\WINDOWS\system32\drivers\fltMgr.sys and WimFltr.sys and restart vlite. After installing both reboot the computer before usage. Btw when Filter Manager installation asks you for the XP CD make sure it's the same version as the one you're using, meaning that it has SP2 in it.

You have to start it with setup /unattend:Autounattend.xml if you don't boot.