Virtual PC 2004 SP1

[prathapml]

Someone at MS is in celebration or what?

Yet another candidate for slip-stream, go here for the download - news link.

Anyone tried this yet?

(No, I'm not asking this in fond hopes of a speed increase in VPC - I gave up that as hopeless long ago). It adds better compatibility - and since anyway we do want to update it, we might as well slip-stream it in.

[Asky]

Well, I personally don't have much experience doing this, but I don't see how to make the MSP from the service pack, so I can't figure out how to do it by administrative install point

[prathapml]

There is an MSI and a few MSTs in the ZIP that you can download - for VPC2k4 SP1. Must be some way to merge this MSI and the one in the original VPC2k4 package?

[1chaoticadult]

prathapml I have you tried using the method used with SAV9 to patch the original msi?

[oioldman]

Ths SAV9 stuff is.msp - Installer Patch

VPC2k4SP1 is .msi - Installer file

I tried last night to integrate and it would n't have it. In end looked like an insall of the original and then an install of the SP1.

[prathapml]

VPC2k4SP1 is .msi - Installer file

Yup.

That's why I still haven't tried experimenting with it.

[RyanVM]

I created an AIP of 2004 SP1. Gonna try integrating it with an AIP of 2004 as soon as I get some free time.

EDIT: It's going to require a lot of heavy MSI editing, though.

[oioldman]

@RyanVM - sounds like fun!

Enjoy and don't forget to keep coffee cup full.

Let us know how you get on, as i'll install VPC2k and the SP1 for now.

[prathapml]

EDIT: It's going to require a lot of heavy MSI editing, though.

Okay... make it an MST, for being able to distribute it. I wouldn't like to see billy boy snapping at your heels.

[RyanVM]

Can I do that with Orca?

[totoymola]

Windows ® Installer. V 3.00.3790.2180

msiexec /Option <Required Parameter> [Optional Parameter]Install Options

</package | /i> <Product.msi>

  Installs or configures a product

/a <Product.msi>

  Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

  Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

  Uninstalls the product

Display Options

/quiet

  Quiet mode, no user interaction

/passive

  Unattended mode - progress bar only

/q[n|b|r|f]

  Sets user interface level

  n - No UI

  b - Basic UI

  r - Reduced UI

  f - Full UI (default)

/help

  Help information

Restart Options

/norestart

  Do not restart after the installation is complete

/promptrestart

  Prompts the user for restart if necessary

/forcerestart

  Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

  i - Status messages

  w - Nonfatal warnings

  e - All error messages

  a - Start up of actions

  r - Action-specific records

  u - User requests

  c - Initial UI parameters

  m - Out-of-memory or fatal exit information

  o - Out-of-disk-space messages

  p - Terminal properties

  v - Verbose output

  x - Extra debugging information

  + - Append to existing log file

  ! - Flush each line to the log

  * - Log all information, except for v and x options

/log <LogFile>

  Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

  Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>

  Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

  Repairs a product

  p - only if file is missing

  o - if file is missing or an older version is installed (default)

  e - if file is missing or an equal or older version is installed

  d - if file is missing or a different version is installed

  c - if file is missing or checksum does not match the calculated value

  a - forces all files to be reinstalled

  u - all required user-specific registry entries (default)

  m - all required computer-specific registry entries (default)

  s - all existing shortcuts (default)

  v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

I saw this on the Microsoft Virtual PC 2004.msi. So how do we use these switches to integrate this thing to the original installer?

[oioldman]

@totoymola - right in the middle it says this;

Update Options
/update <Update1.msp>[;Update2.msp]
  Applies update(s)

So, it needs to be a .msp to integrate and as it's an .msi you can't and a .mst is a transform to install specific options.

So we await RyanVM, efforts or we install the main program and then install SP1

[RyanVM]

, I haven't even had a chance to try integrating it yet. I've got Administrative Install Points for both 2004 and the 2004 SP1 update sitting on my desktop just waiting to be manipulated.

How do I make an MST file with Orca?

[Joe User 99]

, I haven't even had a chance to try integrating it yet. I've got Administrative Install Points for both 2004 and the 2004 SP1 update sitting on my desktop just waiting to be manipulated.

How do I make an MST file with Orca?

You don't make a MST file with orca. You use MSITRAN (also in the SDK).

Use Orca to make your changes, then save as a new MSI. Then use MSITRAN, like this:

MSITRAN -g "X:\Microsoft Virtual PC 2004.msi" X:\Custom.msi X:\VirtualPC.mst

(The quotes are only due to spaces in the name of the MSI.)

Here is more info on MSITRAN:

http://msdn.microsoft.com/library/default....msitran_exe.asp

[RyanVM]

Thanks for the info. How does MSITRAN work with AIPs?