nitro322

By manual I just mean doing everything directly via dism and whatnot, as opposed to using something like rt7lite to automate it. Ie: mount the wim file, manually unpack, patch, and apply the service pack, manually apply other packages, etc. It's been kind of a pain in the rear to get everything setup, but I have a pretty good process worked out now that I've automated with an autoit script. I'll be happy to share the autoit script if you're interested, but it really wasn't developed with redistribution in mind, so it's rather specific in how it does things.

Huh. I just did yet another complete rebuild, and now the sysprep and everything works, even with IE9 slipstreamed. Not that I'm complaining, but man, weird. Now to figure out why Windows Update is prompting me to install IE9 again even though it's already installed via slipstream...

Because I'd rather slipstream it and not waste the extra time to install it after the OS is installed. That's kind of the whole point to all of this. For stuff I can't slipstream I do exactly that, but if it can be slipstreamed, then that's the goal.

I have this sysprep problem as well. The process described by SmokingRope seems sound, but something about the sysprep step is rather fragile. I initially started looking into this because I had the same issue with preinstalled apps/configuration settings not being applied to the default user. I was using rt7lite originally as well, and couldn't get the sysprep step to take; it'd just fail in the same way as described above. I then tried switching to a manual build process, and that worked! ... until I tried slipstreaming IE9. Then it failed again. I've since rebuilt my image without IE9, and it still fails, no matter what I do. This really rather sucks. It shouldn't be so difficult to apply default user settings. This is my last major stumbling block, so I'd be really interested to hear any workarounds or alternative solutions. I've been hammering away at this myself on-and-off for about three weeks now, but I've not had any (reliable) success.

Cool, thanks. That's what I was thinking based on the screenshot, but I wanted to verify I wasn't missing anything else.

InstallShield issue comes from TrID - it has an extremely high false-positive rate, and I haven't been able to find a good programmatic way to deal with it. Thanks. This is actually the better thread for this kind of request, but I saw it in the bug reports thread first so I commented there.

Support is there, but it's not detecting the file properly. It's trying to unpack it as a FEAD file, same as the other commenter posted about the Firefox installer. This is another consequence of shuffling around 7-Zip. Confirmed - thanks for the report. I'm always up for checking out newer/better alternatives. Thanks for the links. I can't find a legit download source now, but the binaries themselves, best I can tell, are freely redistributable. As a result, there shouldn't be a problem keeping them included. That's 7-Zip's new generic .exe resource extraction at work. It doesn't seem to work all that well, though, and it's definitely causing me other problems with file type detection and extraction order, as discussed previously. You might be able to extract files from the 0 file by renaming it to include a few different extensions (0.exe, 0.cab, etc.) and running UniExtract on i. I have seen that work once before, but mostly not. Thanks for the installer examples. I'll add them to the list to check out.

Noted. Can you clarify point 1? You say the file name is not located, but I don't know what file you're referring to. From the image it looks like the text is too wide for the screen, which would be more difficult to fix in Inno Setup than UniExtract itself. 2,4 - noted 3 - this is a known problem. Unfortunately, there's no easy fix (best I can tell) as it'll require completely rewriting that custom Inno Setup options page. I'm going to try to get that fixed for the next release. adblockpro.exe seems to work for me, but it suffers from the problem described here, where Install Explorer isn't being used instead of 7-zip to extract it. others - same problem, but Install Explorer is failing, and it's not falling back to 7-zip like it should. Definitely needs to be fixed.

This is two bugs in one: 1. It [em]should[/em] work in 1.6.1. To be honest, I'm not sure why it's failing. It should attempt to extract with unzip first (which it's doing), then, if it fails, attempt to extract with 7-zip (which it's not). I don't know why that's failing at the moment; the condition logic looks correct. 2. I (thought I) modified that same condition logic to try 7-zip if unzip's exit code was anything other than a 0 or 1. I even added this change to the changelog. However, I must have inadvertently undid that change at some point and didn't catch it, as the release version is only looking for an exit code of 0. Don't know what happened there, but I'll need to fix it. This is a more general problem, though - unzip reports and exit code of 9 for the winzip file you posted, which should trigger 7-zip regardless. Thanks for the report. Adding these issues to my todo file.

It works for me. I did notice a potential problem, though. As mentioned in the changelog, I now have 7-zip try extracting files last, as recent versions can incorrectly unpack some .exe files that other utilities correctly unpack. A side-effect is that Install Explorer is used to extract NSIS files by default now rather than 7-zip. InstExpl can better support NSIS 1.x files, but 7-zip, from what I've seen, better supports newer NSIS 2.x files. I'll need to shuffle some things around again to make 7-zip default for NSIS without affecting other file types. Will add to my todo file. I don't know what you mean by this. Can you please clarify?

Awesome, thanks for the update.

1.6.1 is done. Download links and final changelog for the release version is available in the announcement thread. Thanks to everyone that provided feedback. gora, I'm afraid I still can't replicate this, or even offer an explanation as to why it happens. You should never see that second _temp log; it only gets written very briefly in the event of a failed extraction, then gets moved back to the main debug file. This should happen pretty much instantly, and it happens before the Extraction Failed prompt is even displayed. That it doesn't happen with 1.6 is even weirder, because I didn't change anything at all in that part of the script. Maybe I'm having trouble replicating your problem because I changed something between beta2 and the final version. I did make a few more tweaks, but nothing in particular that I can think of that might cause this. Go ahead and try the final version and let me know if you see any difference at all. If you do still have the problem, please provide the contents of your UniExtract.ini file (so I can try to match your environment as much as possible) and let me know what specific file you're trying to extract (direct download link would be a big help). Everyone else - are you experiencing the same behavior gora reported? Please let me know.

Weird. I tried downloading adblockpro.exe, but I can't replicate the problem. Repeated extractions exit successfully. Regardless, though, there will be cases where this fails; as I mentioned in the changelog, detection isn't perfect due to a number of factors. As for the "file does not exist" problem, I can't think of what may cause that. The file should always be there. Even for formats that I can't log (including 7-Zip now) it should at least contain a line stating something like "Extraction of 7-Zip archives cannot be logged." Can you do me a favor? Repeat the test that failed, then manually check to see if the debug file exists. Maybe it's an issue with the path (are you using an environmental variable in the debug location?), or maybe your editor isn't liking the way it's being called. Edit: The debug file is launched with a ShellExecute command, which should open it in whatever edit Windows opens .txt files in by default. If the debug file does exist, try pasting the full path of it into the run box (just the file path, no editor command) and verify that Windows opens it properly in your editor. I agree that this can be less convenient, but it's safer and more accurate. This is actually how I intended extractions with 7-Zip to function all along, the previous behavior was implemented because of this bug in 7-Zip. Since I couldn't log, I told 7-zip to force skipping existing files. After giving that decision a lot of additional thought, plus with the need to better handle overwrite detection, for the release I decided that it's more important to have full feedback and overwrite prompts for 7-Zip than debug logging. Once Igor fixes the issue in 7-Zip I'm going to add logging again, but the user prompt behavior will stay. It's a feature, not a bug, although it may annoy some people. Until I get a better system in place of handling i/o, the separate cmd Windows are the best option available. The primary goal for v2.0, whenever that may happen, is a revamped UI that integrates cmd output and prompts into the main UniExtract window. At that point the inconvenience factor will drop significantly, but until then the cmd windows are here to stay.

Alright, I'll look into this. Merge modules (in this context) are Windows Installer components. Details: http://msdn.microsoft.com/en-us/library/aa369820%28VS.85%29.aspx

If you're referring to the splash text windows (eg., "Extracting files from: NullSoft Installer installer"), I actually increased the width of these last night. I don't remember if it was before or after I released the beta, though. Give it a shot with beta2 and let me know how it looks. It seems ok to me.