I know this might be considered OT, but still...  
  
Using the delivered MSI, what would be the "magic MSIEXEC command line" to:  
  
- upgrade ("upgrade all components") an existing DTW installation?  
  
- install DTW on a machine where it's not present, to the default location  
  
(hope it uses the "Program Files" location from the registry, and doesn't  
  
hardcode c:\Program Files...)?  
  
- install DTW on a machine where it's not present, to a specified location?  
  
FWIW, for MSDN, we have found out we need to use:  
  
msiexec /l*v c:\msdn_Jan2006_upgrade.log /passive /i  
  
\\mwgstore\msdn\Jan2006\msdn.msi QUICKINSTALL=1 SETUP_EXE=yes  
  
by looking into the MSI using Orca and surfing the net...  
  
TIA

I know very little about the setup, but I think INSTDIR=<dir> can be used to  
  
set the install location.  /i would be the debugger MSI, such as  
  
dbg_x86.msi.  I think /qn is the quiet flag.  
  
msiexec /i dbg_x86.msi /qn INSTDIR=<dir>  
  
I don't know how to control upgrade vs. install.  
  
"Stephane Barizien" <steNphOane.SbarPizien@oAcMe.com> wrote in message  
  
news:ejDGyHKKGHA.4068@TK2MSFTNGP10.phx.gbl...

BTW, I just discovered the package is distributed as an EXE, not a MSI. How  
  
do I "properly" extract the MSI from the EXE?  
  
Drew Bliss [MSFT] wrote:

Found the answer by surfing...  
  
dbg_x86_6.6.03.5.exe /t:j:\\tmp /c  
  
will extract the .msi from the .exe  
  
Now back to square one: I'm able to open the .msi in Orca, and probably the  
  
answer is there: name of the variables (strings, booleans...) that need to  
  
be set for /qn to do the setup/upgrade the way I want it...  
  
Where can I find info on how to reverse-engineer the MSI (specifically: the  
  
way the UI works by setting the values the core MSI engine later uses to  
  
perform the actual actions)?  
  
Stephane Barizien wrote:

The command line I gave should allow for an unattended install.  What does  
  
it do when you use it?  
  
"Stephane Barizien" <steNphOane.SbarPizien@oAcMe.com> wrote in message  
  
news:eAGsJnwKGHA.720@TK2MSFTNGP14.phx.gbl...

Try using msizap.exe to delete the old install.  
  
--  
  
This posting is provided "AS IS" with no warranties, and confers no  
  
rights.  
  
"Stephane Barizien" wrote:

It worked... silently (expected) -- after I found out where to put the  
  
quotes in  
  
INSTDIR="D:\Program Files\Debugging Tools for Windows"  
  
;-)  
  
But then the nightmare hit me...  
  
I wanted to make sure it would work on a machine w/o DTW installed, and  
  
decided (for whatever reason) to uninstall the just installed DTW with  
  
"msiexec /x" instead of using Control Panel / Add/Remove Programs. That  
  
uninstall worked.  
  
But then I discovered I still had an old DTW visible in Control Panel /  
  
Add/Remove Programs, whose uninstall failed, even with msiexec /x: "This  
  
action is only valid for products that are currently installed." Still,  
  
MSIINV reports:  
  
...\bin\msiinv  2006\02\07  18:05:03  
  
Debugging Tools for Windows  
  
Product code: {C1533BB9-7359-4226-AC47-25409ED863AD}  
  
Product state: (5) Installed.  
  
Package code: {C1533BB9-7359-4226-AC47-25409ED863AD}  
  
Version: 6.1.17.2  
  
AssignmentType: 1  
  
Publisher: Microsoft Corporation  
  
Language: 0  
  
Installed from: \\mwgstore\mwg\Conferences\Printing & Imaging 2003\Test  
  
Tools - Printing\  
  
Package: \\mwgstore\mwg\Conferences\Printing & Imaging 2003\Test  
  
Tools - Printing\  
  
Help link: http://www.microsoft.com/ddk/debugging  
  
Local package: <missing>  
  
Install date: 2005\07\05  
  
Registered to:  LYRA, Océ Print Logic Technologies S.A.  
  
Serial Code: 12345-111-1111111-45917  
  
23 features.  
  
0 features are not used.  
  
0 features are advertised.  
  
0 features are absent.  
  
23 features installed to run local.  
  
0 features installed to run from source.  
  
0 features installed for default.  
  
0 features in some other state.  
  
201 components.  
  
0 qualified.  
  
0 permanent.  
  
0 shared.  
  
0 patch packages.  
  
any clue?  
  
Drew Bliss [MSFT] wrote:

unfortunately this doesn't fit the bill  
  
the old 6.1 still shows up both in A/RP and in msiinv...  
  
Pavel Lebedinsky [MSFT] wrote: