integrate instead of install
#1
Posted 11 February 2010 - 07:33 PM
Thanks
#2
Posted 11 February 2010 - 09:38 PM
Phariset, on 11 February 2010 - 07:33 PM, said:
Thanks
#3
Posted 12 February 2010 - 12:57 AM
imho, this feature could be left to those that does that since always, like nlite
[]s
#4
Posted 12 February 2010 - 08:31 PM
Cristiano, on 12 February 2010 - 12:57 AM, said:
OK - I stand corrected but I, for one, have never used nLite but I do use the RyanVM Integrator or the Siginet Office Integrator whenever I deem it necessary to create new CDs for Windows XP or for Office XP/2003.
#5
Posted 19 February 2010 - 06:55 PM
I dont want to use nlite or any other program because if you "integrate" too many sources into one project, things get messed up. I alreayd have my own unattended script that uses integrated and auto-installed programs, combined with auto-it scripts and autopatcher. I'm worried if i have to add more software to make it work, something is going to go wrong. Oh and all this from a flash drive
#6
Posted 19 February 2010 - 11:33 PM
most of them have and all the ones that has can be integrated with autopatcher due that. but the problem isn't integrate, autopatcher does that. the problem is that autopatcher doesn't rebuild the files that was compressed and the integration process from the files also doesn't that. so, if you choose the integration option from autopatcher and deploy only the critical updates, the result will be bigger than 700mb. if you choose the remaining ones it will be far worst. of course, you can burn that into an dvd media that will work. it will even install faster, because the files will not be compressed, but not all machines has an dvd drive. another issue: you will be unable to integrate ie8/7 and wmp11 and also all their updates with autopatcher
i don't remember right now the string, i just remember that this was part of an talk that i had with James long ago, but since i'm not sleeping well since long ago, my memory isn't the same anymore. but i can find the string again (i did once and i'm sure that i'm able to find again), but i don't have time right now. so, if despite all those issues you still wanna choose the integration mode, let me know that i will look for it. but an advise: it isn't an good idea
[]s
#7
Posted 12 March 2010 - 04:52 PM
#8
Posted 12 March 2010 - 06:11 PM
you will have the same issue than with autopatcher. personally, i advise nlite to that. with that, you can integrate msie and wmp without worries and the install media will not become oversized
[]s
#9
Posted 13 March 2010 - 09:53 PM
These are the instructions I wrote for myself to gain space during the process:
First thing to do is to copy the XP Home or Pro with SP3 CD to the hard drive (assume over 700Gb of space will be required).
To save space when integrating the following folders can be deleted as sub-folders under \I386 as they are only used for an upgrade of an older version of Windows: \WIN9XMIG, \WIN9XUPG, \WINNTUPG.
Also delete \LANG if English only is to be used.
The above listed files/folders are not updated/modified/changed using the RyanVM Integrator which is why they can be deleted. If the user wants to later install/reinstall a program from one of these folders they can just use the original XP Home or Pro with SP3 CD.
The above actions are done to have an increase in space when the final WinXP w/SP3 Integrated ISO is to be created because of the additional Addons and/or Driver Packs space requirements.
#10
Posted 14 March 2010 - 04:56 AM
DesertJerry said:
#11
Posted 14 March 2010 - 06:21 AM
gUiTaR_mIkE, on 14 March 2010 - 04:56 AM, said:
#12
Posted 14 March 2010 - 09:01 AM
DesertJerry said:
I thought maybe what you meant to write was 700mb / not 700gb, sorry, didn't mean anything by it.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












