effgee Posted October 16, 2007 Share Posted October 16, 2007 (edited) My Build Order for a Customized XP CD1. Copy source files from XP source media, to a location on disk. ex. C:\src \i386\ \WIN51 \WIN51IP \WIN51IP.SP2 \SETUP.EXE \AUTORUN.INF2. Windows Media Player 11 integrator. a. Select windows source. b. Select media player source c. Select media player hotfixes.3. RVM Integrator a. Update pack, RVMUpdatePack2.1.11.7z b. Other updates dotnetaio.exe jre6u1.exe NOD32_2.7.exe NR_EUEfontUpdate_Addon_1.1-ReCabbed.7z ProgramAddons_Firefox_2.0.0.6.cab RUPUpdates-2.1.11.13-Addon.7z RVMAddons_1.8.2.7z RVMAddonsDX9_1.4.7z WScript57-1.0.0-Addon.7z (Update- install last after IE7 integration, or do everything with NLITE) Xable_Foxit_v3.0_addon.cab4. Nlitea. Hotfixes, Addons and Update Packs IE7,OnePiece_IE7AddOn_1.8.0_ENU.7z IMPORTANT NEWBIE NOTE: INTERNET EXPLORER 7 ADDONS (IE7) NEEDS TO BE THE LAST INTEGRATED ADDON WITH ANY OF THE INTEGRATION PROGRAMS. THAT MEANS IF YOU ARE INTEGRATING ANOTHER ADDON SUCH AS WINRAR, INTEGRATE IT FIRST, THEN RESTART THE NLITE PROCESS WITH ONLY IE7. ALSO I AM AWARE THAT IE7 CAN BE INTEGRATED WITH RVMI b. Unattended Settings These settings removed, but can be used as a printable checklist for your use.5. Driver Packs a. Driverpacks Chipset 7.09 CPU 7.04.1 LAN 7.09.1 MassStorage 7.09.1 3rd Party Driverpacks DP_Virtual_wnt5_x86-32_708.7z DP_Monitor_wnt5_x86-32_070827.7z DP_Input_wnt5_x86-32_070113.7z DP_Modem_wnt5_x86-32_709.7z DriverPack MassStorage text mode b. Driverpacks Method - Method 2 c. KTD - Keep the Drivers Enable KTD for ALL slipstreamed DriverPacks KTD cache location (Is there a problem with the %systempath% environment variable? It doesnt work on my DriverPack Base 7.05.2 I have to set it manually.) C:\windows\DriverPacks d. Quickstream Cache - Disabled6. OEM Branding a. Copy the $OEM$ to the modified source. ex. C:\src\$OEM$ The files located here, should be automatically copied to c:\windows\system32 during the install process. Of course this is dependent on the OEMPREINSTALL checkbox in NLITE. There is a workaround though. I can't find my notes though $OEM$\$$\system32\KeyUpdateTool_enu.exe - Key Changer - very useful, allows changing of VLK into valid OEM license.oeminfo.ini oemlogo.bmp7. Nlite a. Select modified source, then Bootable iso. Direct Burn. Volume Label - VRMPVOL_ENWith these settings, everything fits onto a 700MB cd.I am aware that some of these may be out of date, if someone that knows of newer version of these files could copy any paste their files into this same post, possibly we can keep an up to date list of this process?I am also having a problem with the OnePiece_IE7AddOn_1.8.0_ENU.7z integration. Windows update doesn't seem to work. ActiveX installation of the plugin on that site doesn't proceed. I never get the ActiveX popup. I'm going to try it again a little later.Hope this is useful for someone. Edited October 17, 2007 by effgee Link to comment Share on other sites More sharing options...
neo Posted October 16, 2007 Share Posted October 16, 2007 Nice work... I hope the topic should be pinned. Link to comment Share on other sites More sharing options...
anonymous_user Posted October 16, 2007 Share Posted October 16, 2007 Why should IE7 be integrated last? I integrate it after RyanVM's update pack and Code's update addon. Link to comment Share on other sites More sharing options...
effgee Posted October 17, 2007 Author Share Posted October 17, 2007 (edited) Why should IE7 be integrated last? I integrate it after RyanVM's update pack and Code's update addon.Well there are several reasons.1. In my personal experience, not integrating it last causes some simple but strange problems. Such as empty desktop.ini thrown everywhere etc. As well as the occasional non functional IE7.2. After much hard work, I found a single post in the Ryan VM forums that also confirmed my findings. Actually it could be the other way around. I think I was having problems until I found the post that said IE7 must be integrated alone, and last.*** UPDATE ****According to this post...http://www.ryanvm.net/forum/viewtopic.php?...ghlight=wscriptIn some cases, the order of integration is also important! Usually, you will need to worry about this only when using this update addon with another addon that updates built-in Microsoft components. * If you use an IE7 addon, the IE7 addon must be integrated after this update addon, but before Windows Script 5.7 (if installing WS5.7)This is possibly why I am having issues with the IE7 addon pack, since I am install Windows Script 5.7 Edited October 17, 2007 by effgee Link to comment Share on other sites More sharing options...
boooggy Posted October 17, 2007 Share Posted October 17, 2007 considering that u post in nlite area i dont see the need for so many steps....u can do everything in one step via nlite. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now