OK nono tell onepiece that there is a better way to copy the msxml files to winsxs, no need for using txtsetup to copy the msxml's cat, man and dll files... I figured out how Ryan does it
Delete these files and entries from your addon and use this asms folder I uploaded/made from the files in your pack
Code: Select all
42098490.cat = 100,,,,,,,278,0,0,4.20.9849.0.cat
42098490.pol = 100,,,,,,,278,0,0,4.20.9849.0.policy
..........................
MSXML242.cat = 100,,,,,,,125,0,0,x86_Microsoft.MSXML2_6bd6b9abf345378f_4.20.9849.0_x-ww_1c078e1b.cat
MSXML242.man = 100,,,,,,,125,0,0,x86_Microsoft.MSXML2_6bd6b9abf345378f_4.20.9849.0_x-ww_1c078e1b.manifest
..........................
MSXML441.cat = 100,,,,,,,125,0,0,x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_x-ww_29c3ad6a.cat
MSXML441.man = 100,,,,,,,125,0,0,x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_x-ww_29c3ad6a.manifest
http://www.mediafire.com/?8jscuvtd99k
Im sure you can figure out how I did it, just use a MD5 tool to figure out which files I renamed and put in which subfolders, you will later find after integration and install that the files are copied to winsxs and renamed perfectly
BTW I am making a updatepack and I would like to use some examples from your IE addon in mine I hope its OK with you