Does anyone have any ideas on how to best to include the i386 folder to a Windows XP scripted installation?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
use a batch file to copy it from a network share?
Answered 01/20/2011 by: dyehardfan
Second Degree Blue Belt

Please log in to comment
0
sdillane,

You can copy it right from the kbox.

It'll be in \\ikbox\\peinst\source_cds\{xp cd number}\i386
Answered 01/20/2011 by: dchristian
Red Belt

Please log in to comment
0
To followup on dchristian, you should do this as a mid-level tast (a post installation task with KBE as the selected environment). xcopy would work well. This would minimize the space on the K2.
Answered 01/20/2011 by: cserrins
Red Belt

Please log in to comment
0
Nice trick, didn't realize that could be done.


ORIGINAL: dchristian

sdillane,

You can copy it right from the kbox.

It'll be in \\ikbox\\peinst\source_cds\{xp cd number}\i386



ORIGINAL: cserrins

To followup on dchristian, you should do this as a mid-level tast (a post installation task with KBE as the selected environment). xcopy would work well. This would minimize the space on the K2.



And to get rid of a little more of my k2000 ignorance, how does this save space on the appliance?
Answered 01/21/2011 by: dyehardfan
Second Degree Blue Belt

Please log in to comment
0
the files are already on the K2, so by copying them from where dchristian stated works without uploading anything new to the K2000. Some may take the i386 folder, zip it up and upload it as a mid or post installation task, but that would take up more space.
Answered 01/21/2011 by: cserrins
Red Belt

Please log in to comment
0
I gotcha. Misunderstood what you were saying. I thought you were saying doing it as a mid-level task would free up space, but you were actually saying that copying the files from the kbox is what saves the space. Good to know. New trick for my server installs.


ORIGINAL: cserrins

the files are already on the K2, so by copying them from where dchristian stated works without uploading anything new to the K2000.  Some may take the i386 folder, zip it up and upload it as a mid or post installation task, but that would take up more space.


Answered 01/21/2011 by: dyehardfan
Second Degree Blue Belt

Please log in to comment
0
David thanks for the information, this helped out a lot. I was not aware that the source files were copied to the peinst folder. Once I took a closer look I also noticed that during the install I was already mapped to the location. This is what worked for me:
xcopy y:\source_cds\1\i386 c:\i386 /y /i /s /e /h
Answered 01/24/2011 by: sdillane
Senior Yellow Belt

Please log in to comment
0
Glad it helped!

Just kinda curious, what do you need the i386 folder for?

If your computers are going to be staying in a network that has communication with the KBOX you can map peinst as the default location for i386.

Take a look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup.

There are a couple of registry keys (installation sources, servicepacksource patch, and sourcepath) in here that set the location of i386 when adding or removing windows components.

If this works for you maybe all you'll need is to set these to point to peinst.

Example bat script:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v ServicePackSourcePath /t REG_SZ /d \\{your kbox here}\peinst\source_cds\{source cd number here} /f
Answered 01/25/2011 by: dchristian
Red Belt

Please log in to comment
0
now that is an interesting idea. I've always kept a copy of the source files on each computer. Something to think about.

Thanks
Answered 01/25/2011 by: sdillane
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity