nuhi

These kind of questions are forbidden by the state of California. Gotta lock it or they'll lock us

Thank you for the compliments, I'm glad you like it.

Great, thanks for the update.

WFP is solved in the next one to some extent. About INF files without comments causing signature issues it's just because the file was altered, not because of the missing commented line. I'll see about it to be sure, maaybe they use comments in that file but I seriously doubt it, it's just signatures issue.

So explain to me how did you manage that please? Clean Windows installation files? Then RVM integrator or what? Then nlite with what preset, attach it...

I tried it and it does ask, I presume you just extracted the inf file. You have to extract the all files from that driver archive into some empty folder prior integration selection.

Well one day it is, one day it isn't...I don't think that's caused by something removed, it's either Vista, drivers or hardware.

MarcLister, thanks for the info.

No they are not. Well if you had those files in the root then I don't know why it would ask you for the floppy. Try making the ISO with some other tool after nlite processing. Or retry nLite from the scratch, just load your preset on the full windows again.

Probably Windows Mail, more precisely the Address Book part of it.

I think this is due to the Remote Desktop removal. And the reg entry for that call couldn't be found. I hope it's not hard-coded in some service. But are you sure about that stutter being only because of this, this shouldn't be that hard on the cpu?

nLite doesn't do that on it's own. Check if there is eula.txt in the i386\ folder and see that the content is intact.

Have you read the guide regarding the referrer linked on that 403 page?

Did you copy the root files from the installation CD, not just i386? Files like: WIN51 WIN51IP WIN51IP.SP2

Thank you. Now that you reminded me that issues was solved by reseting the temp folder to the default for some...uh how could I forget. Enjoy and feel free to report any issue once you confirm that it doesn't happen on the full Vista.

If you make ISO with the vLite it's always bootable no matter what image size...if it's compatible but those issues are rare.

How about attaching some presets folks.

printui.dll Printer support tpvmmon.dll don't know. While installing VMware tools I too get only printui.dll missing even if all removed. That's not a big problem just press Ok or put that file in the Keep box or don't remove printer support. As for not working NIC drivers keep the Ethernet Drivers.

It's the same image unless there is more than 2GB in a single file, it's DVD UDF then (I could be wrong with the specifics). Only the size is what limits the CD image, 700MB usually. So just go to the ISO page and make an ISO, if it's larger than 700 then use the Split function, or remove more or integrate less drivers.

You are not the first one to report it, try some searching. But I must admit we actually don't have a clue why it happens. What seems to help is a host Windows reinstall, but that's extreme.

Don't be too hard on yourself, it's not weird to choose AlwaysOn, what's weird is that it makes so much trouble. I meant who would do that intentionally, so maybe it's best to remove the option. But year we'll start with the warning then if someone blames vLite for corrupting the memory again I remove it.

Ok thanks. I will be ready if someone reports it, meanwhile reinstall the full Vista with the same drivers and you also be on the lookout.

Thank you both, I will put this into the appropriate descriptions.

Vista install fails because of less than 256RAM if you used that limit option in vLite, not because the limit is 256. There is not a single reason except hype that you want to use Vista on such a weak machine. Even XP is borderline compatible let alone Vista. I would recommend Windows 2000.

Great. Now I'm thinking of removing that particular option, don't know why would someone use it intentionally...maybe for safe servers...hm.