nuhi

@Alanoll, you amaze me...you here support this nlite-copy but nlite can't be what it is already becoming. @mjc, as far as I see here this is only to spite me because I didn't gave source to you when you asked me and because of nlite-corporate limitations. Fine but to go in public like this and talk low of my work with arrogant smile, that is simply childish. Only way I see you remove components so fast is to copy nlite....low, very low indeed. @others, If someone wants to help him earn his paycheck then please stop discussing nlite, this is [sarcasm]tooootally different program[/sarcasm].

hehe to demolish all other. Good luck, you'll need it.

Did you copied your CD into hdd partition root ? If you have then recopy fresh from CD into some subfolder. In short that folder is not part of normal Windows package.

Smoothly cool...we luv ya ! You know those GANT icons...you should make your pack too (outside resources)...it will be popular like Christmas tree

Heh finally I have double posted...it's my first !

Davelicious, good info there, finally some help. Now, ignore that syssetup thing, it's dealt with after setup automatically, the problem is with that Frontpage extension file. Tell me did you removed Frontpage Extension ? If not then how can that file be unsigned. Have you maybe deleted Dllcache somehow...check in system32\dllcache is it full, around 300mb. Nlite doesn't add SfcSetting, it ads SfcDisable like it should...which version are you using.

Davelicious, is it possible to see which file WFP is trying to replace ?

I'll see what happens if SFC is disabled and then reenabled after install, that should help you.

heh, koitsu after you report a bug then you have to wait that I fix it. I already said in another thread that I'll skip patching if one doesn't select patching page or component removals...there.

Yeah you don't have to be worried, it's just cosmetic but still a bug. This was reported before but when I asked how can I replicate that no one replied. So I ask...how can I replicate that problem...run sysprep...reseal it, what ?

nəʊ I will state that in changes when it's available. Problem is only with my connection speed, can't download anything that big to test.

If you applied usbport patch then rewrite usbport.sys with original in system32\drivers folder.

RogueSpear, don't think I missed your post...just wanted to say thanks and one day I'll deal with this, saved your instructions.

camoman, have you tested it with nlite 1.0b1 ?

RogueSpear, when you at it next time please test RIS with Manual Install removed, should work now. So you need to copy only tag files, like WIN51IP ?, not nlite.inf and such new ones ?

fdv, yeah, good point, i could put it to execute certain section of syssetup, why the hell not , no need for whole extra file. Gonna dwell on it for a year or so, thanks

slippykillsticks, this doesn't have anything to do with nLite, it's a separate project. This is where I stop because still haven't tried it.

Even if you manage to bypass that there is a problem with 2-3 files which nlite adds, like nlite.inf, it won't be copied with RIS. So basically I will need to make it compatible with RIS. For start from this beta1 it keeps all RIS files, that's a start...but I can't promise the deadline for full support.

@erukian, do you have gold edition, i mean without any service packs...then just apply sp2, don't apply sp1 first. If you have tried that already then I think that problem lies in that that expand skips all after error while windows during install expand file by file and by that you can get all files around the error. Thats why some user had idea that i expand file by file which is possible and I may add it into beta 2...if you're interested in testing in 2 days, when i'll be done, send me PM. @rivimey, uh, if your iso was too small, below 90mb then something was wrong, it would help if you try to make it again, use latest version and delete nlite before second try, reinstall it. Did you removed any drivers...maybe your cab was corrupted too but lets not think that, your asms error is different. That shouldn't happen, ever...maybe sata/raid integration went bad...which driver is it...

Do me a favor...integrate without nlite, then extract driver.cab to some folder and sp2.cab to some other...check if you have those files missing in any of those folders. Use expand.exe If you confirm that these files are there then we can talk further. But I'm telling you many people tested it before you and they confirmed that even without nlite it's messed up. I wish it's nlite and that i can fix it...believe me.

Aegis, can't wait to try this, thanks.

erukian, I don't know were you reading this topic carefully but you missed the part where we conclude that it's your CAB, it's corrupted...you can try extracting it yourself and you'll find those files missing. Unless you experience some other problem then name your files.

Fixed it...you need to selected in Compatibility Wizard Windows Activation and I added few more files to keeping...changed the title...all in all wait next version and thank you

I never tried sysprep so it would speed things up if you explain to me how to reproduce the problem in short. Thanks

XpZorro nLite support comming right up.