ayrani Posted May 17, 2012 Posted May 17, 2012 (edited) Hi,My first question is: Can i integrate All Office update.exe files using Msp Extractor tool in WinKit? I think this can be done. However, there is a problem i have:It processes "ogl2007-kb2596672-fullfile-x86-glb or wordconv2007-kb2596880-fullfile-x86-glb" type update.exe files Without a Problem. These are Office Compatibility Pack for Word, Excel and PowerPoint File Formatscreates update .exe files and WinKit msp files in different folders for each.While it processes "office2003-KB2553111-FullFile-TRK" type Office update .exe files, i get the below error in the picture and it creates empty folders. Full Visual C+ AIO is installed on system and admin login. Edited May 22, 2012 by ayrani Quote
oguz Posted May 17, 2012 Posted May 17, 2012 In English it means:Command line option syntax error. Type command /? for help. Quote
Legolash2o Posted May 28, 2012 Posted May 28, 2012 Assuming this issue only happens with this update then the problem is now solved. Quote
ayrani Posted May 29, 2012 Author Posted May 29, 2012 (edited) Assuming this issue only happens with this update then the problem is now solved.Thank you for the Fix.But the problem does not only exist in KB2553111 file. It exists in all KBxxxxxxx.exe these type files in the picture.I put KB2553111 as an EXAMPLE of the error message. The same error message is given in the all KBxxxxxxx.exe these type files.I am surprised that you only focused on one :confused02: Edited May 29, 2012 by ayrani Quote
Legolash2o Posted May 29, 2012 Posted May 29, 2012 (edited) I focused on one because I have used many updates with the EXE to MSP Converter and they all worked fine, KB2553111 is the only file which i've seen your mentioned problem so I assumed it was a one off.EDIT 1: Seems to be a common problem with Office 2003 updates, do you have the names of any other updates it affects?EDIT 2: Fixed this so it works with all 2003 updates, however please still list a few other updates it had affected just for testing purposes. Edited May 29, 2012 by Legolash2o Quote
oguz Posted May 29, 2012 Posted May 29, 2012 Hi, @LegoHow can we integrate these updates to the image? Is it neccesary to have office.exe slient file? Or does it integrate to the image without office.exe slient? Quote
Legolash2o Posted May 29, 2012 Posted May 29, 2012 (edited) You don't integrate them into the image, you add them to an 'Updates' folder with your Office setup sourcei.e. "Z:\Software\Office 2010\x86\Setup.exe""Z:\Software\Office 2010\x86\Updates\*.msp" <<< go in Updates folder. Edited May 29, 2012 by Legolash2o Quote
ayrani Posted May 30, 2012 Author Posted May 30, 2012 I focused on one because I have used many updates with the EXE to MSP Converter and they all worked fine, KB2553111 is the only file which i've seen your mentioned problem so I assumed it was a one off.EDIT 1: Seems to be a common problem with Office 2003 updates, do you have the names of any other updates it affects?EDIT 2: Fixed this so it works with all 2003 updates, however please still list a few other updates it had affected just for testing purposes.Msp Extractor in V19 runs perfect with all office 2003 update.exe files..You are the best VC++ coder in the world :prop: Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.