Jump to content

problems with office xp


moo

Recommended Posts

Hi guys.

All installations work well, but office xp generate error 1622. When I using just RunOnceEx it working fine.

[Office XP]

command.0 = %SRCDRIVE%\soft\officexp\setup.exe TRANSFORMS=Custom.mst /qb-

selected.0=1

What's wrong?

Thanks.

moo

Link to comment
Share on other sites


Could be just that wihu doesn't find the Custom.mst.

Try to had the path of the file in the command line, something like

command.0 = %SRCDRIVE%\soft\officexp\setup.exe TRANSFORMS=%SRCDRIVE%\soft\officexp\Custom.mst /qb-

let us know the result

XPect

Link to comment
Share on other sites

  • 11 months later...

i had the same problem, this is the way i solved it:

WIHU Install CFG:

___________________________________________________________

description.0=Microsoft Office

selected.0=0

collapsed.0 =0

command.0=cmd.exe /C @echo off

/user:DOMAIN\USER

help.0=%wihu%/office.rtf

Group.0=1

; Sub command 0.0

description.0.0=Office XP Standard

command.0.0=%systemdrive%\Install\CMD-Install\OfficeXP-STD.cmd

selected.0.0 =0

; Sub command 0.1

description.0.1=Office XP Full

command.0.1=%systemdrive%\Install\CMD-Install\OfficeXP-FULL.cmd

selected.0.1 =0

; Sub command 0.2

description.0.2=Office XP Standard + Access

command.0.2=%systemdrive%\Install\CMD-Install\OfficeXP-STD-AC.cmd

selected.0.2 =0

; Sub command 0.3

description.0.3=Office XP Standard + Frontpage

command.0.3=%systemdrive%\Install\CMD-Install\OfficeXP-STD-AC.cmd

selected.0.3 =0

___________________________________________________

And in the commands file Wihu calls up contains:

-------------

cmdow @ /HID

@echo off

call %PATH-TO-OFFICE%\INSTAPLS.EXE TRANSFORMS=standard.MST /qr

exit

-------------

only different MST files for each command file tough..

I think the error occours because wihu has a log variable and office might have the same variable so they crash, if you run office instapls.exe without any switches you get the error message that it can not write to log file. :huh:

changing the LOG variable in WIHU might do the trick?? :wacko:

Edited by mastrboy
Link to comment
Share on other sites

  • 2 months later...

i have written a Auto-IT script to fix this problem, it's not perfect but it does the job.

;written by mastrboy
#include <GUIConstants.au3>
;includes MST files (have them in the same folder as the script when compiling)
FileInstall("FULL.MST", @TempDir&"\FULL.MST")
FileInstall("STANDARD.MST", @TempDir&"\STANDARD.MST")
FileInstall("STDAC.MST", @TempDir&"\STDAC.MST")
FileInstall("STDFP.MST", @TempDir&"\STDFP.MST")

;error if parameter is wrong
Func error()
MsgBox(0+48, "No such parameter", "Use /? to se options")
Exit
EndFunc

If $CmdLine[0] = 0 Then
Call ("error")
EndIf

Select
Case $CmdLine[1] = "/?"
$Form1 = GUICreate("Office Installation Help", 420, 157, 192, 125)
GUICtrlCreateLabel("Following parameters are supported:", 8, 8, 141, 18)
GUICtrlCreateLabel("STANDARD = (Word, Excel, Powerpoint og Outlook", 8, 32, 402, 17)
GUICtrlCreateLabel("FULL = Full Installation", 8, 56, 163, 17)
GUICtrlCreateLabel("STDAC = Standard + Access", 8, 80, 148, 17)
GUICtrlCreateLabel("STDFP = Standard + Frontpage", 8, 104, 160, 17)
$ok_button = GUICtrlCreateButton("OK", 24, 128, 89, 25)
GUISetState(@SW_SHOW)
While 1
$msg = GuiGetMsg()
Select
Case $msg = $ok_button
Exit
Case $msg = $GUI_EVENT_CLOSE
Exit
Case Else
;continues
EndSelect
WEnd

Case $CmdLine[0] = "1"
If FileExists(@TempDir&"\"&$CmdLine[1]&".MST") Then
;starts the installation
RunWait("c:\OFFICE_XP_SP3\INSTAPLS.EXE TRANSFORMS="""&@TempDir&"\"&$CmdLine[1]&".MST"" /qr");change out with our own location of office installation files
;Deletes all mst file in tmp dir
FileDelete(@TempDir&"\*.mst")
Exit
Else
call ("error")
EndIf

Case Else
Call ("error")
EndSelect
Exit

feel free to try it out or modify it to your needs... :hello:

Edited by mastrboy
Link to comment
Share on other sites

Hello

I have this in my install.ini file :

; Sub command 0

description.0=Microsoft Office 2003

command.0=%srcdrive%\Applications\Office2003\setup.exe TRANSFORMS=Unattended.MST /qb-

selected.0 = 0

And it works fine..the method is in the msfn unattended guide

Link to comment
Share on other sites

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...