J> Has anyone tried to slipstream the VPC 2004 additions into a Windows
J> 2000 or
J> Windows XP setup so they will already be included in the setup?
I haven't tried this, and I won't make any guarantees, but you could look
for a program called AutoStreamer. It's used to slipstream SP's into
Windows XP for creating Barts PE CD's. If I remember correctly, it asks for
the file that you want to slipstream and the folder where the OS is.. so it
may work.. But, I don't know how you'd hack the setup to install it as well.
With best regards, Patrick Dickey. E-mail: pd1ckey43**RemoveThis**@msn.com
--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"Jordan" <nojunk_...@nospam.com> wrote in message
news:esAIj1N...@TK2MSFTNGP09.phx.gbl...
Jordan, maybe you could look into differential disks. I don't remember if I had
to install the additions for each child disk I created off the parent differential
base image. I think I just installed vm additions on the parent and all children
had it by default. I could be wrong though, I had a few other things on my mind
at the time I was doing my builds.
--
-callahan
"Colin Barnhorst" <colinbarharst(nojunk)@msn.com> wrote in message
news:eVE%23%233ZMF...@TK2MSFTNGP10.phx.gbl...
>I think what he meant was he thought, like a service pack, that the vm additions
>could be slipstreamed into a XP and 2000 install so the extra step can be
>eliminated during the setup process.
The Additions need to be installed post-OS, since they need to
determine the actual OS running for the performance enhancements.
>
>Jordan, maybe you could look into differential disks. I don't remember if I had
>to install the additions for each child disk I created off the parent differential
>base image. I think I just installed vm additions on the parent and all children
>had it by default. I could be wrong though, I had a few other things on my mind
>at the time I was doing my builds.
If the parent image had the Additions installed, any child images
linked to it will also.
--
Cheers,
Steve Jain, Virtual Machine MVP
Website: http://www.essjae.com
"This posting is provided "AS IS" with
no warranties, and confers no rights.
You assume all risk for your use.
I am not am employee of Microsoft."
Create a new folder, c:\xpcd, and copy your whole Windows XP with SP2 CD
into that directory. You should now have "c:\xpcd\i386", etc listed as
files.
Now create "c:\xpcd\$OEM$" and then a folder named "$1", in it, and finally
a folder named "VMADD" inside "$1", so you now have a folder structure like
so:
c:\xpcd\$OEM$\$1\VMADD
There is nothing special about the $ folders, the dollar sign is a valid
character, and it doesn't stand for anything.
Now, from the VPC Additions CD/ISO, copy the contents of "\Windows" into
"VMADD". Also create a file, "run.cmd" inside of the VMADD folder.
Load "run.cmd" in Notepad, and enter the following line:
"C:\VMADD\setup.exe" /S /V/qn.
Leave all of the quotes, etc.
OK, if you're still with me, now we're going to tackle the Windows
Unattended Install file, winnt.sif. I'm going to assume you've made basic
answer files before, so I will only bring up the things you need to make the
install go smoothly. If the pointers aren't enough, post back with where
things aren't going the way you'd want. The way I have things, I don't need
to partition or format - Setup uses the whole disk as an NTFS partition
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=yes
(The last line is new in SP2, and avoids the "Help protect your computer"
screen)
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\WINDOWS
Filesystem=NTFS
Repartition=Yes
UnattendSwitch="yes"
(Standard disclaimer - you still need to read the EULA, and if you
distribute the VPC image, you need to have the appropriate licenses, and
give a printed copy of the EULA with the image). UnattendSwitch="yes" makes
Setup skip the mini-setup, which includes creation of users, etc. You need
to have OemPreinstall set to Yes or the $ folders won't copy
And finally, at the bottom you'll want to throw in:
[SetupParams]
UserExecute = "%systemdrive%\VMADD\run.cmd"
This will tell the Additions to install right before it does the last 9
minutes of install. When the machine reboots, VPC Additions will be there
for the first start. When you create the ISO/burn the CD, make sure you
burn with c:\xpcd as your root - such that \I386 and \$OEM$ appear in the
first level
--
--Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site :-)
http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find out
here
Only reply by newsgroup. I do not do technical support via email. Any
emails I have not authorized are deleted before I see them.
"Jordan" <nojunk_...@nospam.com> wrote in message
news:esAIj1N...@TK2MSFTNGP09.phx.gbl...
--
-callahan
"Steve Jain" <essj...@Spam-hotmail.com> wrote in message
news:35sb41heot6up7mtb...@4ax.com...