run the MSI and any transform I might have You can *sometimes* guess which these are because the stub EXE will be disproportionately large compared to the extracted MSI (MSIs don't compress much) Thus, I make it a practise to: if it's an MSI-based install, there'll be an MSI with a name composed of random alphanumeric (0-9 and A-F) characters.Ī word of caution though: some vendors are too stupid or lazy to build all the functionality into the MSI and sometimes add calls to scripts created by the tool used to author the MSI. at the first 'Welcome to our crappy product' dialog, check the %temp% folder's content ![]() clear out the contents of your %TEMP% folder If your setup stub can receive arguments via the '/V' switch, that means that ultimately it extracts an MSI and (probably) executes MSIExec.EXE against that MSI. ![]() ![]() IIRC you can only capture executables and not work on them directly but I'd love to be wrong about this!!Matt, yer man was referring to using the MSI directly. ![]() How do I do this then Anki? Which tool do I need to use in Package Studio to open the setup.exe file - I've had a quick look and cannot see anything obvious.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |