How to unattendedly use the RyanVM Integrator.

[Siginet]

How to unattendedly use RyanVM's Integrator.

Three methods.
Latest Method
Now you can control just about every aspect of the integrator from a batch file. for detailed information check out this thread:
http://siginetsoftware.com/forum/showthread.php?t=283

There will be more parameters added as well.

The Second and Third Methods are no longer reccommended and are going to be phased out. So please start using the latest methods.

============================================

Second METHOD:
First off you will want to make a custom settings.ini file. This ini file can be named anything you like.
The easiest way to create it would be to make a batch file with this in it:

RVM_Integrator_v1.0RC13.exe "X:\RyanVM\settings.ini"

This will create your fresh new settings.ini file in the x:\RyanVM directory and open the gui window.

Now just select all of the options that you will want to use. They will be saved in your settings.ini file.

When you are finished close the gui window and go back to your batch file and add this switch to the end: /integrate

It should now look like this:

RVM_Integrator_v1.0RC13.exe "X:\RyanVM\settings.ini" /integrate

Execute the new batch file and you did it!
Pretty simple huh?

**New for integrator v1.1**
With v1.1 of the integrator you can now compile an iso as well... so it would have been stupid not to have created a way to unattendedly create an iso.

It is very simple. It uses a new switch:

Code: Select all

/iso

So call the integrater then the path and filename of your settings file for parameter 1. Parameter 2 will be /iso.

Example:

Code: Select all

RVM_Integrator_v1.1.exe "X:\RyanVM\settings.ini" /iso

==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====

OLD METHOD:
If you want to Integrate RyanVM's update packs 100% unattended all you need to do is create a batch file.

Inside of the Batch file you will need to put something like this:

C:\RyanVM\RVM_Integrator_v1.0RC8.exe /u "C:\MYXP DISK" "C:\RyanVM Cabs\RVMUpdatePack1.3.1.cab" "C:\RyanVM Cabs\RVMAddonsWMP10_1.0.cab"

To break it down I color coded each section.

1. The first section (In White) represents the path and file to execute. In this case it is the RVM_Integrator_v1.0RC8.exe
If the path contains any spaces in it you must put quotation marks at the beginning of the path and at the end of the file name.

2. The second section (In Sky Blue) represents the unattend switch. This must be /u or /U (You can put quotes around it as well... but you don't need to.)
*New in v1.0 RC13*
You can now use /u:NoCats instead of /u if you want to turn off Windows File Protection and stop the integrator from integrating some of the cat files.

3. The third section (In Orange) Represents the path to the directory containing the I386 directory you wish to integrate.

4. The fourth section (In Yellow) represents the path and filename of the RVM_Update*.cab file you wish to use. (Again make sure you use Quotes if your path contains any spaces.)

5. The fifth and final section (In Lime Green) represents the path and RVM_Addon*.cab file(s) you will be using. If you wish to use more than one Addon then make sure all of the addons reside in the same directory. If you are using 2 addon packs the fifth section would look simular to this...

"C:\RyanVM|RVMAddonsWMP10_1.0.cab|RVMAddonsFull_1.0.cab"

Make sure you look at the above example very carefully. Each Addon.cab file has a | (Pole) in front of it to seperate each Addon.cab. Also the path does not have a \ (Backslash) at the end of it.

The easiest way to make sure you are getting your syntax correct would be to open the exe file itself, browse to the files and select them. In the inputbox just copy the text and paste it into your batch file.

You can now have a source and destination as well. Just in case you want to leave your source files untouched.

C:\RyanVM\RVM_Integrator_v1.0RC8.exe /u:NoCats "C:\MYXP DISK" "C:\MYXP DESTINATION" "C:\RyanVM Cabs\RVMUpdatePack1.3.1.cab" "C:\RyanVM Cabs|RVMAddonsWMP10_1.0.cab|Kel_Royale_Addons_3.cab"

[dgelwin]

pay close attention to the multiple addon install sintax it gave me a headacke for a half adday just to notice you dont use \ u use |

[RogueSpear]

Just out of curiosity.. the command line syntax handles spaces within paths without a problem? So does this mean you can eliminate the quotes if there are no spaces in the paths?

[Siginet]

Yeah the quotes are only needed if you have spaces in your path.

[Siginet]

I've updated this post with some new Unattended features introduced in RyanVM_Integrator1.0RC13Beta2.exe

[fluid]

I'm new to this Integrator stuff. Do I still need to follow the first post with 1.0.4?

[Siginet]

If you want to create your install cd unattendedly... yes.

[fluid]

What do you mean by unattended exactly?

[Siginet]

It will integrate The updatePack and/or addons to your cd without user interaction. All you will need to do is create a batch file and execute it. You could make a batch file that would integrate a bunch of different XP disks. It is also compatable with winxp powerpacker as well... so it helps users create a complete xp multiboot disk unattendedly.

[ual747-400]

How do you apply multiple addons to the new way of integrating that is shown?

[Siginet]

You open the gui window. Select all of the options that you want. Close the gui window. Then put this in a batch:

Code: Select all

RVM_Integrator_v1.0.5.exe "X:\RyanVM\integrator.ini"

[ual747-400]

I read that.. I want to know in the ini file how to get the integrator to apply all of the addons I have automatically? I see one addon in the integrator.ini but each additional one is just replaced in the ini file. is there a way to concatenat the files in the ini file?

[Siginet]

Hold Ctrl while selecting addons to highlight multiple addons.

[ual747-400]

OH good grief. I do not know why I did not try that to begin with. sorry..

[fluid]

How do I create a batch file?

[RyanVM]

http://www.fuckinggoogleit.com/search?q ... batch+file

[ual747-400]

Dude that is freeakin awesome. I will use that for other forum stuff.

[fluid]

I got owned.

[RyanVM]

. Don't take it personally, fluid

[fluid]

I didn't.

[Kelsenellenelvian]

I got owned.

hahahahahahahahahhaahahahahahha best laugh all day.

[bellsprout]

hey sry if this is a newbish question but these update packs are compatible with nlite right? and if i'm using nlite, i dont need to use the integrator do i?

[RyanVM]

hey sry if this is a newbish question but these update packs are compatible with nlite right? and if i'm using nlite, i dont need to use the integrator do i?

OK, you're really not off to a good start here. You have two posts so far, and both are questions which could have been easily answered had you bothered to do any looking around whatsoever.
http://www.ryanvm.net/msfn/nlite.html

Not only that, but this post is completely off-topic to the thread topic.

[Siginet]

Updated the post above to represent RVM_Integrator_v1.1.exe. Soon to be released.

[Siginet]

@cutie pyie
I had to take your reply out of this thread because it does not belong in here. It doesn't have anything to do with this thread.

Your new threwad is here:
http://www.ryanvm.net/forum/viewtopic.php?t=1842

[katpasin]

hey guys,
tis is my first post. i am a complete newbie here. making a unattended installation of win xp for the first time. i was following msfn's guide to make the unattended cd, had slip streamed sp2 and was about to manually integrate all hotfixes, thn saw ryan's integrator. used it to integrate ryan's update pack and a wmp10 addon pack. but i am not able to figure out wat to do next??

also wat oes tis thread mean? wich part of making the unattended cd is tis thread used?

and wen i did as told in tis thread, i got a settings.ini file wich has text like

[Settings]
Source=F:\Win_XP_Saptak_Ganguly
Destination=
UpdatePack=I:\unattended\RVMUpdatePack2.0.6.cab
ExternalRun=
ParametersRun=
IsoFile=
IsoBinFile=
IsoVolume=
IsoExtTool=
IsoExtCmd=
IsoIntExt=Internal
IsoCmdLine=mkisofs

[Switches]
IKnowWhatImDoing=4

[AddonPacks]
RVMAddonsWMP10_2.5.cab=I:\unattended

wat do i do after this??

sorry if i posted tis in a wrong thread, but culdnt find a help forum.

[vier]

A forum exist for RVM Integrator : here

[katpasin]

thnx for the link, but thr r no threads in RVM integratot!!

[vier]

I know, The forum is new !

[ENU_user]

may b sometime you can add new switches to integrator for addons in dir's

Code: Select all

C:\RyanVM\RVM_Integrator.exe "C:\MYXP DISK" "C:\Addons\"*.cab" "*.7z"
C:\RyanVM\RVM_Integrator.exe "C:\MYXP DISK" "C:\Addons\*.cab|*.7z

or like this :

Code: Select all

C:\RyanVM\RVM_Integrator.exe "C:\MYXP DISK" "C:\Addons1\*.cab" "C:\Addons2\*.7z"

or in integrator gui hold control select a few dir's >>integrate<<

just an idea

[gabo]

@Siginet

I'm looking to auto most of my integrations, and I'm looking for the batch file automation switches, but the link to your site is broken.

Is it posssible to include the instructions here on this thread, or better yet, to include them in the integrator itself?

If I write at the command prompt:

RVM_Integrator_1.5.3.exe /?

the integrator displays the switches it supports. For examplo Boooggy's WMP11 slipstreamer does this.

Thank you very much.

[Siginet]

@Siginet

I'm looking to auto most of my integrations, and I'm looking for the batch file automation switches, but the link to your site is broken.

Is it posssible to include the instructions here on this thread, or better yet, to include them in the integrator itself?

If I write at the command prompt:

RVM_Integrator_1.5.3.exe /?

the integrator displays the switches it supports. For examplo Boooggy's WMP11 slipstreamer does this.

Thank you very much.

Sorry about that. My forum should be up sometime soon. I keep forgetting to add the /? switch. It has been requested many times as well.

[gabo]

Siginet

Thank you very much!! I'll be waiting for the new version with the switch in it. In the meantime, while you create the /? switch, is there somplace where I can look for the switches the integrator supports? Or, is there a text file or someting that shows what switches to use?

[Zephyr]

The Siginet Software Forum is dead, so to find out what is the latest method here is a snapshot taken by the Wayback Machine https://web.archive.org/web/20081228131 ... .php?t=283

As of RVM Integrator v1.5RC4 there are many new Parameters that can be used. These Parameters are useful for batch files or scripts that can control just about any portion of the integrator when it is executed.

Enjoy!

/Load: Allows you to specify a settings file to use when the integrator is opened. You can show the entire path or just the ini file. If the path is not specified then the integrator looks in it's own directory.

Code: Select all

/Load:"X:\PathTo.ini"
Or
/Load:settings.ini

/Save: Will save the current settings file to a new settings file that can be Loaded at a later time. You can show the entire path or just the ini file. If the path is not specified then the integrator looks in it's own directory.

Code: Select all

/Save:"X:\PathToNew.ini"
Or
/Save:SaveSettings.ini

/Wipe: When you use the "Wipe" switch it will delete the settings file (if it exists) before opening the integrator. This is useful if you wish to only use the settings you specify from your parameters. If you do not use the "Wipe" switch then the integrator will use the current settings file and change it with the specified parameters.

Code: Select all

/Wipe

/Source: This is where you specify the "Source" directory which contains the I386 directory you wish to start with.

Code: Select all

/Source:"X:\PathToYourSource\My\WinXP Source"

/Destination: This is where you specify the "Destination" directory where you wish to copy the "Source" to. You do not have to specify a "Destination" but it is reccommended. If you do not specify a "Destination" then the integrator will integrate files to the source instead of copying the source to the "Destination" and integrating files to the "Destination".

Code: Select all

/Destination:"X:\PathToYourSource\My\WinXP Source"

/CMPNENTS: This parameter is only needed when dealing with a Media Center or Tablet edition of Windows XP. The integrator requires you to point to the location of the CMPNENTS folder so that it knows where to copy it from. The reason this is required is because the CMPNENTS dir is usually kept on a seperate disk.

Code: Select all

/CMPNENTS:"X:\PathToCMPNENTS\WinXP\MCE\CMPNENTS"

/ServicePack: This parameter is used if you wish to specify a Service Pack file to be used during an integration.

Code: Select all

/ServicePack:"X:\PathToSP\windowsxp-kb936929-sp3-x86-enu.exe"

/UpdatePack: You can specify an UpdatePack to be used during integration with this parameter.

Code: Select all

/UpdatePack:"X:\PathToUPck\RVMUpdatePack2.2.1.7z"

/Addons: You can specify a directory with a wildcard "*" to specify all addons to be added to the integration or you can specify specific Addons within a directory seperated by a comma ",".
This parameter can actually be used multiple times in your script. You can specify diferent directories with each instance. This is useful if you wish to add all addons in one directory, all addons in a second directory, and a few addons from a third directory, ... and so on...

Code: Select all

/Addons:"X:\PathToAddons\Dir1\*" /Addons:"X:\PathToAddons\Dir2,ThemeAddon1.7z,ThemeAddon2.zip,PatchAddon_UXTheme.rar,AdobeReader.exe,Entries_WINNTUPG_Removal.ini"

/Optimize: This will choose whether to use "Optimize System Files" during integration or not. If you use a + then it activates it. If you use a - then it deactivates it.

Code: Select all

/Optimize:+
or
/Optimize:-

/OptimizeOnly: This will force the integrator to unattendedly "Optimize system Files". Make sure your setting specify a destination or source so that it knows what to optimize. You can specify it by either the settings file or the batch parameters /Source or /Destination.

Code: Select all

/OptimizeOnly

/Advanced: This will choose wether to use "Advanced Options" during integration or not. If you use a + then it activates it. If you use a - then it deactivates it.

Code: Select all

/Advanced:+
or
/Advanced:-

/Cache: This will choose wether to use "Cached Driver.cab" during integration or not. If you use a + then it activates it. If you use a - then it deactivates it.

Code: Select all

/Cache:+
or
/Cache:-

/advDebug: This will choose wether to use "Advanced Debug Mode" during integration or not. If you use a + then it activates it. If you use a - then it deactivates it.

Code: Select all

/advDebug:+
or
/advDebug:-

/ShowWindows: This will choose wether to use "Show External Windows" during integration or not. If you use a + then it activates it. If you use a - then it deactivates it.

Code: Select all

/ShowWindows:+
or
/ShowWindows:-

/BreakDriver: This will choose wether to use "Break Before driver.cab Repacking" during integration or not. If you use a + then it activates it. If you use a - then it deactivates it.

Code: Select all

/BreakDriver:+
or
/BreakDriver:-

/RunFile: This is how you specify if you wish to "Run a Program After Integration". If you specify a path to a file to run then it will activate it. If you specify a - then it will Deactivate it.

Code: Select all

/RunFile:"X:\PathToFile\myfile.exe"
/RunFile:-

/RunParams: If you "Run a Program After Integration" and you wish to specify Parameters for that file then you would use this parameter to do it. If you specify parameters in this one then it will place them in the "Enter Parameters For The Above Program" inputbox in the integrator. If you specify a - then it will delete and parameters from that inputbox.

Code: Select all

/RunParams:"/s /NoRestart"
/RunParams:-

/LeaveOpen: This will leave the integrators window open after it executes a "Run a Program After Integration". (I personally have never found a need for this option in the integrator... and I may remove this option later if no one claims to have any use for it.) It is activated with a + and deactivated with a -.

Code: Select all

/LeaveOpen:+
/LeaveOpen:-

/ISODir: You can specify a directory which will be used to compile into an iso file with this parameter. If you are making an iso and this is not specified then the integrator will check if a Destination exists instead. If no Destination exists then the integrator will attempt to use the Source when creating an iso.

Code: Select all

/ISODir:"X:\PathToMakeISOFrom\WinXP Updated"

/ISOFile: This is where you specify the path/name of the iso file you wish to create.

Code: Select all

/ISOFile:"X:\PathToImage\mynew.iso"

/ISOLabel: You will need to specify a label for your ISO with this parameter.

Code: Select all

/ISOLabel:"MY_WINXP"

/UseMKISOFS: This specifies that you wish to use the internal mkisofs when creating your iso file.

Code: Select all

/UseMKISOFS

/MKISOFSParams: This specifies that you wish to use the internal code for mkisofs.

Code: Select all

/MKISOFSParams

/UseExternal: If you wish to specify an external tool for iso creation then you can specify it with this parameter. This will Activate this option and place the program in the inputbox.

Code: Select all

/UseExternal:"X:\PathToExternalTool\cdimage.exe"

/CDImageParams: If you specify cdimage.exe as your external tool for use when creating an image then you can use this parameter to use the integrators built in code for cdimage.exe

Code: Select all

/CDImageParams

/ExternalParams: If you wish to use your own parameters for iso creation then you can specify it here. Remember to use double % if you do not want certain EnvVars to be parsed.
Also remember you must have the string after /ExternalParams: enclosed in quotes! So in your string instead of using quotes Wrap areas in <>. The integrator will change each < or > into a quote. This is needed to simplify passing external params within this param. Without doing this it would probably be impossible.

Code: Select all

/ExternalParams:"-l<%%3> -g -h -j1 -b<%%2> -x -yd -m <%%0> <%%1>"

/AutoDelete: When copying files from Source to Destination a msgbox pops up if there are files that allready exist which asks if the user would like to delete or overwrite files. This switch will tell the integrator to delete the files.

Code: Select all

/AutoDelete

/AutoOverwrite: When copying files from Source to Destination a msgbox pops up if there are files that allready exist which asks if the user would like to delete or overwrite files. This switch will tell the integrator to overwrite the files.

Code: Select all

/AutoOverwrite

/Integrate: This will put the integrator into unattended mode and automatically begin to start an integration once the integrator is opened.

Code: Select all

/Integrate

/MakeISO: This will put the integrator into unattended mode and automatically begin to compile an ISO when the integrator is opened.

Code: Select all

/MakeISO

You can also use /Integrate /MakeISO in the same script to unattendedly integrate files and compile an ISO in one go.

The order of each parameter does not matter. It is also not case sensitive.

Here is an example script:

Code: Select all

"%CD%\RVM_Integrator_1.5.exe" /UseExternal:"%CD%\files\CDIMAGE.EXE" /ExternalParams:"-l<%%3> -g -h -j1 -b<%%2> -x -yd -m <%%0> <%%1>" /Wipe /Load:"%CD%\LoadedSettings.ini" /Save:"%CD%\SavedSettings.ini" /Source:"X:\ROOT\XPHO" /Destination:"%CD%\My New Windows Files" /UpdatePack:"X:\ADDONS\RVMUpdatePack2.2.17z" /Addons:"X:\ADDONS\1\*" /Addons:"D:\ADDONS\2\*" /Optimize:+ /Advanced:+ /Cache:+ /ISOFile:"c:\autotest.iso" /ISOLabel:MyLabel /Integrate /MakeISO

As of now I have also implemented code to attempt to detect older unattended parameters. I will probably remove the old unattended parameters from a later version of the integrator... So I reccommend anyone using old methods to begin using the new methods in this post.