nuhi

I just saw the topic, no reason to call me. Error 2 means The system cannot find the file specified. Is it WinBETA AIO? If not then just recopy the source and try again, if again happens the same let me know. Probably first Apply method will work but the ISO won't get smaller.

Thanks for the report, saved it. Gonna try it these days and ask you for more info if it all goes too smoothly for me.

Oh, that was fixed in 1.3beta...try the 1.3RC, it's better than 1.2.1.

Bitter...very bitter...I'll shut up now you can dream on.

prathapml, I have a problem...can't reproduce that BSOD and I know it's true in rare cases because one other person reported it too. Do you maybe have any pointers? Or maybe someone else got the same issue? BSOD on image selection.

Heh what coincidence, didn't know that...well if I see more of these doubts I'll change the name.

I appreciate the warm welcome, thank you all. @ricktendo64, do you mean that as a bug in the RC or as the solution for previous version? @janerik, thanks gonna do that but I did clean RunAs, on which file do you see it? About German translation, Sereby is now in charge and I presume he doesn't take it seriously enough. @datalife, I'll write it down for 1.4 but I can't promise anything.

Would you leave those 2 files alone, it's not like a spyware or something Yeah of course change the ISO engine before using it...

Well you could have searched. mkisofs is a freeware command-line utility used to make ISO images. Boot.bin is same, boot.catalog is auto-generated by the mkisofs and they are both needed and both should be invisible on the CD when burned. I have put the mkisofs in 1.3rc so you can switch to it when you Create ISO in ISO Engine combo.

Many fixes in this one, some of which are quite serious. All in all I recommend this version over any other. Give it a few days in the wild if you don't test. Changelog and download Isn't it great this new thing of no betas and rcs forever? Live and learn... So lets focus only on fixes until the 1.3 final is out. updated to RC2: fix: Correct MSI Installer registry permission fix: txtsetup_files_pro/home addon entry support fix: Txtsetup.sif End of line char cleanup fix: Various ISO page correction

Wireless Configuration and Event Log has it in their descriptions. Then just guessing Internet Authentication (IAS). But I think that by selecting the Ethernet DHCP compatibility will take care of it.

Clint, I bust my a** figuring out, I'm not pulling anything...show me another nlite or vlite. I always answer when it's appropriate, when not asked by a copycat...but your rude tactics are not my thing.

bledd, probably because he likes Source sorted at the top. I use that for music --- like you put [New] and then i always know where is the new folder...at the top...because of the first char [.

Yeah I knew this, some of the alpha testers reported it. It is not dangerous nor the defender is there, it's just a missing reg entry which is tricky to catch. How to tell the Windows update that the Defender isn't there...if someone knows do tell, thx. And I'll try to see if maaybe something is actually left in the registry.

It's not your fault, just push cancel and yes. If it repeats too much then consider disabling SFC. But you did more than service pack integration, just to be clear on that.

Promised I said it may be released today. If I don't see any new critical bugs it's out in 10 hours from now.

nLite compresses them and doesn't need Unattended (sif file with appropriate entries) so it's up to you. I find nLite better of course BUT it is easier to update the other method. I do a clean start on every reinstall so it's again not an issue.

But I already answered...it's to make it better, more sleek...but as every new thing it could broke, that's why we have betas. Popups...well those black screens when it's deleting a file or something similiar, you may notice them in older nlite versions during Registering Components or at the first user logon. Also nhelper can delete used files and stuff like that. I can add whatever is needed in it and it's written in c++.

Ok, gonna adjust it a little. If you put some weird unicode characters then cab file compression fails.

Looked at this and nlite.inf is there but you are removing some files through RemoveFiles box. Clean it out and see if that helped in your case, that box is kinda advanced and not so perfect. I would remove it if some people aren't actively using it with success.

I'm affraid you'll have to keep whole Help component then or play with the msinfo32.inf from the full install copy and trigger it to reinstall...

Help and Support removes it. Gonna check about that shortcut leftover.

cpumemhd, nice find about the hivesys, correcting. Even though it didn't cause any issues because nlite inf overwrites it during install with the correct line. However after reading your post twice do you mean I shouldn't edit the System Temp variable even though the user selects another folder for it or that just applies when it actually changed it for no reason (also a bug) ?

Madhits45, try 1.3 RC when it comes out and let me know how it behaves for you. Also write down exact errors you get next time, failing every install is kinda weird, may meant that your MSI installer is broken...anyway try the next one.

alexgit, seems like preset ISO engine in nLite has issues with some machines so I'll be adding the optional old mkisofs engine for you to choose from in the next version. You can put it in the nlite root yourself...just read the help popup next to the ISO Engine in the Make ISO page.