nuhi

You can make network installation but you can search for the missing file in the iso to see where it should be...weird. What's wrong...well how did you make that ISO, that tool doesn't accept 3rd party added files.

Ok, just a link please.

When you make that network install, is there iaStor.sys/iaStor.sy_ file in i386? And first check if that installation works properly.

It says you don't have or corrupted txtsetup.sif file...did you delete it or something. Check if it's existant in i386 folder. If not redo from clean files and use only nlite without addons to see if it's doing that. If it is there then compress and attach it please.

It's ok then. 1.0.1 is just proven 'stable' while I consider 1.2 to be better in all aspects. But thanks for reporting this anyway, fixed in 1.2 beta.

Are we talking about 1.2? Try to delete the value in TCPIP patch...for me it automatically fills with value 10. That's why I asked how could you leave it blank? edit: uh now i saw in your report the nlite.exe version 1.0.0.16 (aka 1.0.1)...please try new 1.2

Lets stop taunting anyone, this is relatively old topic and two of them resolved it. Should have locked it...

Ok, np.

Just copy them as they are from the original cd. As I said no need for 1.0.1 just do the mkisofs thing, it has auto upcasing.

Fight, fight, fight!

Lamer, nice find, but how did you manage not to enter something? I mean it's set to reset to 10 if you delete all values, I can't repeat this, please check exactly what is it, thx.

I hear you but there are issues with regular .NET, let alone Mono. However I'm interested in something, do I need to compile with Mono or it can run .NET compiled programs? If it does run then what does it report when nLite is started? I mean if there needs to be 2 separate versions then the answer is no.

Wait, wait How is it solved if new version doesn't work for you? 1.2 has better driver integration, I'm sure you did something wrong with all that editing, or chosen the wrong driver at first if you say that older one worked fine.

It remembers last before red, which was letter away, kinda lame at first but when you get used to it it's quite fast and intuitive. Why red...did you had any other with the full name Administrator? Point is that only one unique full name is allowed.

Ok, I'll see about UDF too then automate it if absolutely needed. Thing is in Nero that I need to enable UDF only if there is file larger than 2GB or so in the compilation.

Just to be absolutely sure in this: see if WIN51IP, WIN51 and WIN51IP.SP2 are in the cd root AND upcased? Also try to copy makeiso.exe from nlite 1.0.1 into 1.2 folder and rename it to mkisofs.exe now you can change iso engine while creating ISO.

It's not very clear to me why integrate, why not keep instead?

emodel, thank you for the info, gonna review it but at the end it may be normal to receive event log errors if something is missing, question is is it possible to disable that particular logging. Also no need to double post every conclusion, I do read all relevant posts, it is appreciated.

Verify reports failed or it instantly finishes and reports success (this second thing is solved in next ver to check whole cd, but that doesn't affect this issue) ?

Does this happens right on the ISO page loading or when pushed make iso or something? Gonna test without optical drives anyway, thx for the info.

martinss, does this from the screenshot always happens in certain setup or it was one time only, please retry? This was reported once or twice as a random happening before so it was almost impossible to resolve.

chris.b, how can I see that msagent popup? Jeremy, simplest way to solve RVM pack language leftovers is just to extract intl.inf from it (check if yours is home or pro subfolder in the 7z) into the i386 and overwrite, before loading into nlite of course. Plasma, besides compression rate be sure to enable Merging CABs in Options page and ASMS compression in Hotfixes page - Advanced options. Lemonzest, that means there was some critical error and all was skipped. Try once in virtual without any addon and build from that. Let me know what causes it. SINFIN, important thing is to report what was needed so it gets saved into compatibility option next time? jmbattle, gonna review your reports in more detail, thx but in essence i'm glad that network is fine. Weed, ok gonna check why

Ok bug was next: If you integrate only one .theme file it would skip the directory entry creation. So the temporary solution until the next version would be to integrate at least one theme with msstyles file.

Ok lets review this little closer. Thing is that symmpi.sys has it's older brother in Windows SCSI removal component, that was the issue here. Now tell me did you maybe integrated, then restarted nlite then removed components or it was all in one go, if so then we have a problem which needs fixing? I presume you remove SCSI drivers? And you should, don't worry about that.

First don't copy any files manually, leave the default directory structure just to be sure. Then be careful is it actually 64bit or 32bit drivers and windows you're trying to connect. Then see if there is lsi_sas.sy_ in i386 in case of 32bit or amd64 in case of 64bit driver. And if all of this is "yes i know what i'm doing" then compress and attach txtsetup.sif from the broken install, thx. Oh and post a link to that exact driver just in case.