[visaversa]

Did anyone had success installing it at T9 yet?
Would like to know it cause it fails with my install.
Starting normal seems to copy all files but at the end it start a uninstall, strange?!
Result; no office

w

[bombtrack]

i have planned to install office at t12 (cmdlines-method) later on, i will post my result

[Alanoll]

T9 is after T12.

I have not tried to install Office from T9, but I know it works from GUIRunOnce/RunOnceEX

[bombtrack]

cmdlines method; result: no office

guess ill switch back to the "[GuiRunOnce]" (winntsif) method and try that later

[prathapml]

o2k3 installs fine at t12 (cmdlines).
The uninstall starts because the install encountered an error, and so wants to restore the system to its previous state.

At T-13 and T-12, setup is logged in as "Default User" and invokes all processes done at that time in the name of "Default User". That's when it registers dll/ocx'es and generates ALL_USERS registry values. At the 10-min stage setup evacuates the logged-in space, and does all things from there on to Local_Machine or to the file-system (no user-specific processes), effectively looking at itself from above (like probably, a Near-Death-Experience). Office2k3 installs itself for the user installing/calling the setup - and at T-9, things aren't called in the context of any user.

I suppose this colourful explanation makes it clear about what will/will-not work.

[GreenMachine]

prathapml, on Feb 22 2004, 10:50 AM, said:

o2k3 installs fine at t12 (cmdlines).
The uninstall starts because the install encountered an error, and so wants to restore the system to its previous state.

At T-13 and T-12, setup is logged in as "Default User" and invokes all processes done at that time in the name of "Default User". That's when it registers dll/ocx'es and generates ALL_USERS registry values. At the 10-min stage setup evacuates the logged-in space, and does all things from there on to Local_Machine or to the file-system (no user-specific processes), effectively looking at itself from above (like probably, a Near-Death-Experience). Office2k3 installs itself for the user installing/calling the setup - and at T-9, things aren't called in the context of any user.

I suppose this colourful explanation makes it clear about what will/will-not work.

I thought that was such a good explanation, I'm going to quote it my own post!

Nice, prathapml.

It doesn't however, explain why bombtrack did not get it to work. No Office error log?

[bombtrack]

nope, no ofice folder at all, nothing. really wierd, i used this @t12 (cmdlines runs my xpinstall.)

 <item display='Microsoft Office 2003'>
  	<execute display='Installiere Office...'
  	program='#XPLODE#\APPS\OFFICE\setup.exe'
  	arguments='/noreboot /q PIDKEY=KEY_REMOVED' />
  </item>

i used this argument to install office sliently on an allready installed windows, and it worked fine. i just dont understand why it wont work there. all other apps works fine. only office isnt installed.

[visaversa]

Nice, prathapml
now things are clear to me atleast the T9 stage.
Good next thing to try is at T12 and see what happens next.
Keep you guy's informed

[prathapml]

@GreenMachine

Quote

It doesn't however, explain why bombtrack did not get it to work. No Office error log?

I would have thought that post would explain why bombtrack did not get it to work..... 'coz you get to know why it won't run at that stage, and you get to know when the right time is.

As for the o2k3 install's error log, look in "%systemroot%\temp" for a log (C:\Windows\Temp, when considering normal paths). If you ran the install after a reboot (logging in as user ABC), the log is to be found in %temp% (or C:\Documents and Settings\ABC\Local Settings\Temp, to be simpler).

[prathapml]

@bombtrack-
modifying your XPlode code for the relevant section,

<item display='Microsoft Office 2003'>
  <execute display='Installiere Office...'
  program='#XPLODE#\APPS\OFFICE\setup.exe'
  arguments='/QB-! /noreboot PIDKEY=KEY_REMOVED' />
 </item>

There, now that should work.

I would still say creating an MST file using ork (Office Resource Kit), and adding the switch

/QB-! /noreboot /TRANSFORMS=%systemdrive%\any-location\APPS\OFFICE\automate.mst

is the way to go, and should give better results than you currently are getting.

[visaversa]

or from the cd/dvd drive for that matter i use

<item display='Office 2003'>
<execute display='Installing Office 2003...' program='%SOURCEDRIVE%\Apps\office2003\setup.exe' arguments='TRANSFORMS=%SOURCEDRIVE%\apps\office2003\Unattended.MST /qb-' />
</item>

[bombtrack]

i hope im not stressing you guys too much now never used the ORK b4. downladed htem installed, and got my MST-file created. i copied it into the office directory (which also contins the setup.exe file). now i would like to know if the "argument" has to contain the the path to the mst file, or will this work to ?

 <item display='Microsoft Office 2003'>
  	<execute display='Installiere Office...'
  	program='#XPLODE#\APPS\OFFICE\setup.exe'
  	arguments='TRANSFORMS="silent.MST" /qb-' />
  </item>

trying this at the moment (cmdlines method), hope it works, will erply as soon as vPC gets done

(hope my english is good enough for you guys to understand what i meen)

[GreenMachine]

But ...

prathapml, on Feb 22 2004, 10:50 AM, said:

o2k3 installs fine at t12 (cmdlines). ...

bombtrack, on Feb 22 2004, 10:44 AM, said:

cmdlines method; result: no office ...

Did I miss something?

I still think the explanation was superb, but I suspect a different problem, no?

[visaversa]

Yes it need the path

<item display='Office 2003'>
<execute display='Installing Office 2003...'
program='%SOURCEDRIVE%\Apps\office2003\setup.exe' arguments='TRANSFORMS=%SOURCEDRIVE%\apps\office2003\Unattended.MST /qb-' />
</item>

vv

btw, no luck with cmdlines.txt to
trying "guirunonce" now

[Alanoll]

I would suggest opening up a commandprompt through XPLode, then type in the the line to install Office without silent switches, then you might be able to see an error message

[visaversa]

can anybody tell me why XPlode won't start from cmdlines.txt if i refer to xplode with %systemdrive%\install\xplode.exe.
The folder 'install' exist on the C drive

works, ofcourse this req. the xplode files under the $OEM$ folder

[COMMANDS]
"REGEDIT /S hkcu.reg"
".\XPlode.exe"

does not works

[COMMANDS]
"REGEDIT /S hkcu.reg"
"%systemdrive%\pinstall\XPlode.exe"

vv

[Alanoll]

well, is the folder pinstall or install on the harddrive?

perhaps they are different XML files? open them and see if syntax is correct. XPlode won't work if there is a single error in syntax

[visaversa]

well, its install checked again. Good you saw there was a difference but a copied the path from a previous txtfile thats the reason for the difference..
Yes xml is working caus its the same that is running in VMWare now from cmdlines.txt.
Still find it strange...
maybe i need to remove the leading slash
"%systemdrive%pinstall\XPlode.exe"?
edit:
nah, not posible that could work...
btw, office seems to install fine from cmdlines.txt at T12
edit:"NO it does not install" from cmdlines

[Alanoll]

try adding /log: to the line and see if the log is created. If it is, atleast XPlode starts

[visaversa]

ok il do that, just found the logs from office not as prathapml said in c:\windows\temp but in C:\Documents and Settings\Administrator, strange to cause it was not even rebooted at that stage.

Setup ende with error code 1603