I could not find anything on this topic anywhere (including searching the forum). So I am sorry if this is dup topic but I would like some assistance on this.. thanks in advanced
Full Version: Virtual PC 2004 Slipstreamed with SP1
I am having problems with slipstreaming SP1 into Virtual PC. They didn't use a MSP file it is a MSI for the SP1. Is their anyway that you can sliptream SP1 into the install of VPC 2004?
I could not find anything on this topic anywhere (including searching the forum). So I am sorry if this is dup topic but I would like some assistance on this.. thanks in advanced
I could not find anything on this topic anywhere (including searching the forum). So I am sorry if this is dup topic but I would like some assistance on this.. thanks in advanced
I don't know of any way to do it other than creating an adminstrative install point and manually updating all the files in it with the newer ones. Sorry 
QUOTE (RyanVM @ Jan 13 2005, 02:33 PM)
I don't know of any way to do it other than creating an adminstrative install point and manually updating all the files in it with the newer ones. Sorry
Yep you are right. I tried this earlier when someone first mentioned this in another thread. I think they asked if you could do Ryan? Anyway the only is the method you just said, I can confirm this.
I figured as much..but I though I would ask anyways just so I could try to kill two birds with one stone but it looks like that is not going to happen, whoever, that is cool! thanks for the quick reponses 
No problem. Anytime I can help.
2 questions, first, how do you create the administrative point, /a didnt work for me, and when i try adding the vpc2k4 install package (msdn version) when it installs it says the product key is invalid, what give?
QUOTE
how do you create the administrative point, /a didnt work for me
It should. But there are some msi's that doesn't accept that. So try this instead.
msiexec /a /i filename.msi
that doesnt seem to work either the universal switch program says that the exe is an Installshield 2003 installer, try to retrieve the msi file from the temp folder then install with msiexec /i setup.msi /qb, that didnt work, and this is the message the installer gives me.
CODE
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.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
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.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
any ideas?
If you are in a school that has an Academic Licensing agreement with MS, otherwise known as MSDNAA, then find out what you will need to either check out or burn a copy of the .iso. The current version available in that manner is already update to include SP1.
MSDN Disc 2428.3
Virtual PC 2004,
thats what im installing from, and i still cant seem to integrate this into my batch file for a silent install
Virtual PC 2004,
thats what im installing from, and i still cant seem to integrate this into my batch file for a silent install
QUOTE
the universal switch program says that the exe is an Installshield 2003 installer
Is it an exe? It should be an msi.QUOTE
msiexec /i setup.msi /qb
I wonder why it's not working.. Because theoretically, it should.
ok let me clarify the install dir of virtual pc 2004
setup.exe just runs, Microsoft Virtual PC 2004.msi, if you rename mvpc2004.msi to something without spaces and run the above command on it, it installs and says sumthing about product key cannot be found, but if you just run the setup.exe everything installs fine. I think the setup.exe has directions for the Microsoft Virtual PC 2004.msi file or sumthing. I also tried running /s on the setup.exe and its not silent, i tried all the tags on setup.exe and nothing works, any other ideas?
setup.exe just runs, Microsoft Virtual PC 2004.msi, if you rename mvpc2004.msi to something without spaces and run the above command on it, it installs and says sumthing about product key cannot be found, but if you just run the setup.exe everything installs fine. I think the setup.exe has directions for the Microsoft Virtual PC 2004.msi file or sumthing. I also tried running /s on the setup.exe and its not silent, i tried all the tags on setup.exe and nothing works, any other ideas?
Is there another msi that comes with it? Also, have you tried not renaming the msi?
I want to try it myself. But unfortunately, I lost my copy of the sp1. Can you post the download link here? So I can try it when I get home.
Here's your link to dl the VPC2004 SP1 - http://download.microsoft.com/download/3/8...04SP1Update.zip
Get it and post the solution in double-quick time, lol.
Get it and post the solution in double-quick time, lol.
Hahaha! I will try, but I don't know if I can do it now. Several months ago, I was one of those who asked for the solution for this on the old thread.
For now, this is the switch to get the AIP.
msiexe /a "Microsoft Virtual PC 2004.msi"
I still need to know how the setup.exe works. Because I noticed that there are a lot of mst's.
edit: we don't have to worry about those mst's. those are for the language only.
msiexe /a "Microsoft Virtual PC 2004.msi"
I still need to know how the setup.exe works. Because I noticed that there are a lot of mst's.
edit: we don't have to worry about those mst's. those are for the language only.
when i install using that code it seems to work, but the folder is empty, also, when i run msienc /i "Microsoft Virtual PC 2004.msi" /qn it installs perfectly, but when you run it it says no product key was found. Now i def think that the .exe has something to do with how the msi file works.
QUOTE (twizt3d @ Feb 10 2005, 07:17 AM)
but when you run it it says no product key was found.
Well, that is perfectly logical!
You need to provide the key - I think the MSI property is "PRODKEY=XXXXX"
About the serial number, try these too.
PIDKEY=
or
PRODUCTKEY=
Be sure to include the dashes.
About the setup.exe for the sp1, it does nothing.
What do you mean by that? Which folder is empty? That's what I did yesterday and it worked ok.
I even tried replacing the files in aip of the original installer with the files from the aip of the sp1, but it's no good. It installs but the program doesn't run.
I'm thinking of editing the msi of VPC2004 to apply the contents of the sp1 msi. But I still don't know how to do that.
PIDKEY=
or
PRODUCTKEY=
Be sure to include the dashes.
About the setup.exe for the sp1, it does nothing.
QUOTE
when i install using that code it seems to work, but the folder is empty
What do you mean by that? Which folder is empty? That's what I did yesterday and it worked ok.
I even tried replacing the files in aip of the original installer with the files from the aip of the sp1, but it's no good. It installs but the program doesn't run.
I'm thinking of editing the msi of VPC2004 to apply the contents of the sp1 msi. But I still don't know how to do that.
Im new to msi files, could someone post what a batch should look like to install this silently?
thnx totoymolo, but im not looking to download any software just to build a batch script, waste of harddrive space if you ask me, and if all newbies, )yes im calling myself a newb, and ive been here almost a year and have 87 posts, but hey, we all still learn) use programs like these to build their scripts they never actually learn how to build a batch or similiar, they have programs do it for them. I just want to know the code to install an msi and include a product key.
QUOTE
thnx totoymolo, but im not looking to download any software just to build a batch script, waste of harddrive space
The softwares there are REALLY small and don't need installation. You missed the point of using the tool Windows Installer Command-line Builder. It doesn't just build the commands for you, but it also lets you see all the availabe public property of your msi.
QUOTE
and if all newbies use programs like these to build their scripts they never actually learn how to build a batch or similiar, they have programs do it for them.
I totally understand what you mean. You want to do it the hard way, just like what I did.
But give at least the command line builder a try and play with the properties. You will understand what I mean. 
Hey, I'm a newb too!And another thing is, I don't think you can see ALL the available public properties (and of course even the hidden properties!) of an msi without using a software. Like I said on the other thread, not all msi's are the same. So they don't have the same properties. I understand that you don't wan't to install another software just to do this, but unfortunately, there is no way for that (or at maybe I'm just not aware of it..)
Just for info, the PIDKEY or PRODUCTKEY are properties. And not all msi's use them. Every developer can create their own properties so you can't easily guess what they are.
By the way, did the PIDKEY or PROODUCTKEY worked?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.