nuhi

RJARRRPCGP, oh c'mon stop your whining...you can't expect nlite to work with other tools, what you can expect is to ask us to sync our incompatibilities and hope for the best.

Shall I sticky this topic and replace that old one ?

Has anyone tried not to remove any languages or keyboards until the next version ?

Warez talk...I gotta close.

gramiche, It would be great to just integrate your tool with other applications, not inside nlite package, and then automatically generate appropriate config depending on integrated programs. To simplify: run nlite, go to application integration page, insert your tool, insert apps...nlite generates all what is needed and recognizes custom installer thingy. Hypothetical scenario aka don't do this at home.

This will probably help in debugging that problem, thanks.

Yup I know that sysprep bug is still there on reseal. All you "need" to do is to point it to the CD or windows subfolders for missing files, they are there, it's just it don't see it...signature issue. Since sysprep is mainly used in companies and other commercial branches and they never donated me anything I don't care either. Don't get me wrong, it's not like I'm holding the fix, it is hard, I tried many times and decided it's not worth the hassle...like the dos winnt.exe bug. (winnt32 works ok)

Does normal integration works, this is only a direct integration question ?

That installation failed bug is silly, don't worry about it, it's IE thing in the reg, fixed in next one. Best is RC5 for now.

Beppe, fixed in rc5, try it.

jcarle, c#. Dont' forget that xml suggestion, there is really a CAB file which you can download and parse from MS...I was planning to do that but I simply don't have time. edit: yeah and the link http://download.microsoft.com/download/xml...us/mssecure.cab

jcarle, nice. If you ever develop command line or .net integration options, as a DLL or something, let me know and we'll work something out. But I too don't see anything bad to run this separately. One bug which isn't so important: when I blocked it with a firewall 2 times it just exited the program, try that in debug mode and see what happens. Maybe it would be good to first ping the Microsoft.com and note that I'm offline or Firewall is blocking.

Do you seriously think it does it randomly It goes how they are sorted on the Hotfix page. With only the rule I stated in last post, first CAB packs then Hotfixes then Xpize. Meaning when you click BuildDate it will integrate first oldest CAB pack then others as they are sorted...same goes for Hotfixes. But I do agree that moving individual hotfixes manually would be a good addition, like in GuiRunOnce tabpage. Gonna add that.

nLite integrates Update packs (RVM and others) first then regular hotfixes (which you may choose to be installed by build date by clicking on that Column header) then it integrates XPize last.

RogueSpear, that's the weird part, it works for majority but there are very few people with this gdiplus problem and problems are always louder. frenchy75, bsods are probably because there are many files that are compressed in that ASMS folder, not just that gdiplus subfolder. Why not simply use nlite AFTER integration of RVM pack with Siginet Integrator, also found on Ryan's page...at least until this is fixed for your case.

Ahh...ok then I'll put this cabbing into optinal action...thank you for playing.

It was bug in nlite, silently fixed few hours after release...just redownload rc4 and remake cd or contact me for instructions how to solve it without remake.

Nightlord, just use it normally after nlite on same folder before you make iso.

frenchy75, please attach (not post) your preset used when that happened.

Ok I searched a little and found out that this is not nLite problem. Here is the solution, if someone confirms we could arrange some option... http://forum.abit-usa.com/showpost.php?p=428277&postcount=17

This problem goes way back and I would really like to know if it's fixable...anyone ?

Attach Preset.

I just read this fast but "D-Object reference not set to an instance of an object" is fixed in just uploaded RC3. Finally managed to repeat the error...once you see it it's dead

Known limitation because these drivers do some extra registering after reboot. Since there is reboot when installing before expected it's broken.

Check that installed windows\setuperr.log file and tell us what's in it. edit: Tried it and it was because you disabled DCOM Server Process Launcher