[TIP!] Link RVMIntegrator and WinXP PowerPacker together...

[Siginet]

This is a really cool tip.

You need to use the latest Beta for it to work.

What I do is I use the RVMIntegrator first... but in the advanced tab I select Run External File, Browse to PowerPacker, then in the parameters box I put:

"X:\Path\To\A\Settings\File\powpack.ini" -PACK

This will utalize both programs. First integrating everything with the integrator then calling powerpacker unattendedly and packaging everything. Then you can use the Run External File feature in powerpacker as well to call the integrator in the same way:

Select the integrator file, Then in the parameters put this:

/Load:"X:\Path\To\A\Settings\File\integrator.ini" /INTEGRATE
For more Unattended parameters you can use with the integrator you can look HERE (http://siginetsoftware.com/forum/showthread.php?t=283)

This is a cool way to chain link the programs together so everything is unattended. ;)

You can actually create your entire multiboot disk fully unattended when you have all of your settings files created. :D

[rkillcrazy]

This is a really cool tip.

You need to use the latest Beta for it to work.

What I do is I use the RVMIntegrator first... but in the advanced tab I select Run External File, Browse to PowerPacker, then in the parameters box I put:

"X:\Path\To\A\Settings\File\powpack.ini" -PACK

This will utalize both programs. First integrating everything with the integrator then calling powerpacker unattendedly and packaging everything. Then you can use the Run External File feature in powerpacker as well to call the integrator in the same way:

Select the integrator file, Then in the parameters put this:

"X:\Path\To\A\Settings\File\integrator.ini" /INTEGRATE

This is a cool way to chain link the programs together so everything is unattended. ;)

You can actually create your entire multiboot disk fully unattended when you have all of your settings files created. :D

Does this app have command line functionality? I know I can daisy chain them but I'm not sure that will work for what I am doing. However, if I'm wrong, let me know.

I'm making a multi-boot DVD using PowerPacker. I use RVMIntegrator first to get the update pack in place for XPHO, XPHU, XPPO & XPPU. After that, I use PowerPacker to create the multi-boot DVD and add DriverPacks. I have a batch file that copies the source files to a temp folder and a few other things up to the point of using your apps. I'd like to take it further and automate the whole process. What's the easiest way of doing that?

[Siginet]

You can incorporate your batch file into the process. There are actually a few ways to do it. You can use the method I show you above to call a batch file. Or you can also use the legacy method of placing a batch file called PREPACK.BAT or AFTERPACK.BAT in your ExtraPackFiles to be run before your "Pack" is copied to the destination (PREPACK.BAT) or After your "Pack" is copied to the destination (AFTERPACK). The same can be done with ExtraRootFiles as well using PREROOT.BAT and/or AFTERROOT.BAT. ;)

[compstuff]

This is a really cool tip.

This will utalize both programs. First integrating everything with the integrator then calling powerpacker unattendedly and packaging everything. Then you can use the Run External File feature in powerpacker as well to call the integrator in the same way:

This is a cool way to chain link the programs together so everything is unattended. ;)



This may be a stupid question and I may be missing something... I use Ryan's Integrator often with no real issues but this will be my 1st time using the driver packs and the powerpacker:

After I integrate and the call the powerpacker, why would I need to recall and rerun the integrator? Wouldn't it be ready to just burn at that point?

[Siginet]

Well... you would need to run the integrator to integrat for instance xp home retail then powerpack it... then have powerpacker run the integrator to integrate xp home oem... and so on.

chain linking.

[ENU_user]

removed

[compstuff]

Well... you would need to run the integrator to integrat for instance xp home retail then powerpack it... then have powerpacker run the integrator to integrate xp home oem... and so on.

chain linking.

Oh yes I get it now DUH :rolleyes:

I don't actually do that so for me a single integrate/powerpack instance would serve perfect... thanks!!!

[rkillcrazy]

I know it's late but I have a working batch file that does this stuff for me. It may be a bit bloated for the average user, but it was designed with my needs in mind. It's here for anyone who would like to customize it to their needs.

MK-MULTI-BOOT-DVD.CMD


@ECHO OFF
TITLE COPY XP SOURCE FILES


:::::::::::::::::::::::::::::::::::::::::::::::::: :::::::::::::::::::::::::
::This script uses Daemon Tools, RoboCopy, RyanVM Integrator & PowerPacker.
::
::REVISED: 10:57 06/04/2008
:::::::::::::::::::::::::::::::::::::::::::::::::: :::::::::::::::::::::::::


:BEGIN

:: Make sure Daemon Tools is running
tasklist | findstr "^daemon.exe"
IF %ERRORLEVEL%==0 GOTO DAEMON_RUNNING
IF %ERRORLEVEL% GTR 0 START "" "%ProgramFiles%\DAEMON Tools Lite\daemon.exe"
:DAEMON_RUNNING
CLS


::FLUSH EXISTING SOURCE FILES


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DEST01="D:\MultiBoot\XPs\XP-H-OEM-SP2"
SET DEST02="D:\MultiBoot\XPs\XP-H-UPG-SP2"
SET DEST03="D:\MultiBoot\XPs\XP-P-OEM-SP2B"
SET DEST04="D:\MultiBoot\XPs\XP-P-OEM-SP2B"
SET DEST05="D:\MultiBoot\XPs\XP-P-UPG-SP2"
SET DEST06="D:\MultiBoot\XPs\XP-P-OEM-SP3"
SET PACKED="D:\MultiBoot\PACKED"


::DELETING OLD DIRECTORIES
ECHO DELETING OLD STUFF...STAND BY
IF EXIST %DEST01% (RMDIR /S /Q %DEST01%)
IF EXIST %DEST02% (RMDIR /S /Q %DEST02%)
IF EXIST %DEST03% (RMDIR /S /Q %DEST03%)
IF EXIST %DEST04% (RMDIR /S /Q %DEST04%)
IF EXIST %DEST05% (RMDIR /S /Q %DEST05%)
IF EXIST %DEST06% (RMDIR /S /Q %DEST06%)
IF EXIST %PACKED% (RMDIR /S /Q %PACKED%)


::CREATING NEW DIRECTORIES
IF NOT EXIST %DEST01% (MKDIR %DEST01%)
IF NOT EXIST %DEST02% (MKDIR %DEST02%)
IF NOT EXIST %DEST03% (MKDIR %DEST03%)
IF NOT EXIST %DEST04% (MKDIR %DEST04%)
IF NOT EXIST %DEST05% (MKDIR %DEST05%)
IF NOT EXIST %DEST06% (MKDIR %DEST06%)
IF NOT EXIST %PACKED% (MKDIR %PACKED%)


ENDLOCAL


::################################################ ##########################################
TITLE COPYING XP HOME OEM SP2 SOURCE FILES USING ROBOCOPY
::When using this script, you may want to disable "Secure Mode" in Daemon Tools as it will throw up message boxes that will slow your progress.
::Disable "Secure Mode" via right-clicking the tray icon > OPTIONS > SECURE MODE.


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DAEMON="C:\Program Files\DAEMON Tools Lite\daemon.exe"
SET XPHOSP2="D:\ISOs\Microsoft\Windows\XP\WINXPHOME-SP2(OEM).iso"
SET DEST="D:\MultiBoot\XPs\XP-H-OEM-SP2"
SET WHAT=/mir
SET OPTIONS=/R:2 /W:2 /LOG+:COPY_XPs_LOG.TXT /TEE /NP


::Mounting the ISO
%DAEMON% -mount 0,%XPHOSP2%


::Setting up the DVD variable and copying the data
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\KEYCODE.TXT SET DVDROM=%%i:
::COPYING DATA WITH ROBOCOPY
ROBOCOPY %DVDROM% %DEST% %WHAT% %OPTIONS%
ENDLOCAL


::################################################ ##########################################
TITLE COPYING XP HOME UPG SP2 SOURCE FILES USING ROBOCOPY
::When using this script, you may want to disable "Secure Mode" in Daemon Tools as it will throw up message boxes that will slow your progress.
::Disable "Secure Mode" via right-clicking the tray icon > OPTIONS > SECURE MODE.


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DAEMON="C:\Program Files\DAEMON Tools Lite\daemon.exe"
SET XPHUSP2="D:\ISOs\Microsoft\Windows\XP\WINXPHOME-SP2(UPG).iso"
SET DEST="D:\MultiBoot\XPs\XP-H-UPG-SP2"
SET WHAT=/mir
SET OPTIONS=/R:2 /W:2 /LOG+:COPY_XPs_LOG.TXT /TEE /NP


::Mounting the ISO
%DAEMON% -mount 0,%XPHUSP2%


::Setting up the DVD variable and copying the data
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\KEYCODE.TXT SET DVDROM=%%i:
::COPYING DATA WITH ROBOCOPY
ROBOCOPY %DVDROM% %DEST% %WHAT% %OPTIONS%
ENDLOCAL


::################################################ ##########################################
TITLE COPYING XP PRO OEM SP2B SOURCE FILES USING ROBOCOPY
::When using this script, you may want to disable "Secure Mode" in Daemon Tools as it will throw up message boxes that will slow your progress.
::Disable "Secure Mode" via right-clicking the tray icon > OPTIONS > SECURE MODE.


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DAEMON="C:\Program Files\DAEMON Tools Lite\daemon.exe"
SET XPPOSP2B="D:\ISOs\Microsoft\Windows\XP\WINXPPRO-SP2B(OEM).iso"
SET DEST="D:\MultiBoot\XPs\XP-P-OEM-SP2B"
SET WHAT=/mir
SET OPTIONS=/R:2 /W:2 /LOG+:COPY_XPs_LOG.TXT /TEE /NP


::Mounting the ISO
%DAEMON% -mount 0,%XPPOSP2B%


::Setting up the DVD variable and copying the data
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\KEYCODE.TXT SET DVDROM=%%i:
::COPYING DATA WITH ROBOCOPY
ROBOCOPY %DVDROM% %DEST% %WHAT% %OPTIONS%
ENDLOCAL


::################################################ ##########################################
TITLE COPYING XP PRO OEM SP2C SOURCE FILES USING ROBOCOPY
::When using this script, you may want to disable "Secure Mode" in Daemon Tools as it will throw up message boxes that will slow your progress.
::Disable "Secure Mode" via right-clicking the tray icon > OPTIONS > SECURE MODE.


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DAEMON="C:\Program Files\DAEMON Tools Lite\daemon.exe"
SET XPPOSP2C="D:\ISOs\Microsoft\Windows\XP\WINXPPRO-SP2C(OEM).iso"
SET DEST="D:\MultiBoot\XPs\XP-P-OEM-SP2C"
SET WHAT=/mir
SET OPTIONS=/R:2 /W:2 /LOG+:COPY_XPs_LOG.TXT /TEE /NP


::Mounting the ISO
%DAEMON% -mount 0,%XPPOSP2C%

::Setting up the DVD variable and copying the data
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\KEYCODE.TXT SET DVDROM=%%i:
::COPYING DATA WITH ROBOCOPY
ROBOCOPY %DVDROM% %DEST% %WHAT% %OPTIONS%
ENDLOCAL


::################################################ ##########################################
TITLE COPYING XP PRO OEM SP3 SOURCE FILES USING ROBOCOPY
::When using this script, you may want to disable "Secure Mode" in Daemon Tools as it will throw up message boxes that will slow your progress.
::Disable "Secure Mode" via right-clicking the tray icon > OPTIONS > SECURE MODE.


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DAEMON="C:\Program Files\DAEMON Tools Lite\daemon.exe"
SET XPPOSP3="D:\ISOs\Microsoft\Windows\XP\WINXPPRO-SP3(OEM).iso"
SET DEST="D:\MultiBoot\XPs\XP-P-OEM-SP3"
SET WHAT=/mir
SET OPTIONS=/R:2 /W:2 /LOG+:COPY_XPs_LOG.TXT /TEE /NP


::Mounting the ISO
%DAEMON% -mount 0,%XPPOSP3%

::Setting up the DVD variable and copying the data
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\KEYCODE.TXT SET DVDROM=%%i:
::COPYING DATA WITH ROBOCOPY
ROBOCOPY %DVDROM% %DEST% %WHAT% %OPTIONS%
ENDLOCAL


::################################################ ##########################################
TITLE COPYING XP PRO UPG SP2 SOURCE FILES USING ROBOCOPY
::When using this script, you may want to disable "Secure Mode" in Daemon Tools as it will throw up message boxes that will slow your progress.
::Disable "Secure Mode" via right-clicking the tray icon > OPTIONS > SECURE MODE.


::BEGINS LOCALIZATION OF ENVIRONMENT CHANGES IN A BATCH FILE.
SETLOCAL
SET DAEMON="C:\Program Files\DAEMON Tools Lite\daemon.exe"
SET XPPUSP2="D:\ISOs\Microsoft\Windows\XP\WINXPPRO-SP2(UPG).iso"
SET DEST="D:\MultiBoot\XPs\XP-P-UPG-SP2"
SET WHAT=/mir
SET OPTIONS=/R:2 /W:2 /LOG+:COPY_XPs_LOG.TXT /TEE /NP


::Mounting the ISO
%DAEMON% -mount 0,%XPPUSP2%


::Setting up the DVD variable and copying the data
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\KEYCODE.TXT SET DVDROM=%%i:
::COPYING DATA WITH ROBOCOPY
ROBOCOPY %DVDROM% %DEST% %WHAT% %OPTIONS%
ENDLOCAL


::FOR SOME REASON YOU WILL NORMALLY HAVE AN ERRORLEVEL OF 1
::IT MAY BE BECAUSE ROBOCOPY ALWAYS SKIPS A DIRECTORY
IF %ERRORLEVEL%==1 (GOTO INTEGRATE) ELSE (GOTO ERROR)

::################################################ ##########################################
:INTEGRATE
CLS
TITLE RyanVM Integrator
ECHO INTEGRATING VIA RYANVM INTEGRATOR
CALL "C:\Documents and Settings\robs\My Documents\Batch Files\INTERGRATOR.CMD"
IF %ERRORLEVEL%==0 (GOTO PACK) ELSE (GOTO ERROR)

:PACK
TITLE PowerPacker
ECHO PACKING TO LOCATION VIA POWERPACKER.
ECHO YOU'LL HAVE TO CREATE THE ISO LATER.
CALL "C:\Documents and Settings\robs\My Documents\Batch Files\POWERPACKER.CMD"
IF %ERRORLEVEL%==0 (GOTO END) ELSE (GOTO ERROR)


:ERROR
ECHO SOMETHING BAD HAPPENED. CHECK THE PATH(S) AND SCRIPT(S).
PAUSE


:END
ENDLOCAL


INTERGRATOR.CMD


@ECHO OFF

::VARIABLES
::INTEGRATOR EXECUTABLE
SET INTEGRATOR="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\RVM_INTEGRATOR_1.5.1.EXE"

::INTEGRATOR INI FILES
SET INTEGRATOR_INI_XPH1="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\INTEGRATOR-XP-H-OEM-SP2.INI"
SET INTEGRATOR_INI_XPH2="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\INTEGRATOR-XP-H-UPG-SP2.INI"
SET INTEGRATOR_INI_XPP1="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\INTEGRATOR-XP-P-OEM-SP2B.INI"
SET INTEGRATOR_INI_XPP2="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\INTEGRATOR-XP-P-OEM-SP2C.INI"
SET INTEGRATOR_INI_XPP3="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\INTEGRATOR-XP-P-OEM-SP3.INI"
SET INTEGRATOR_INI_XPP4="D:\MULTIBOOT\SIGINET\RYANVM INTEGRATOR\INTEGRATOR-XP-P-UPG-SP2.INI"

::INTEGRATOR SWITCH
SET INTEGRATOR_SW=/INTEGRATE

ECHO INTEGRATING XP HOME OEM SP2
%INTEGRATOR% %INTEGRATOR_INI_XPH1% %INTEGRATOR_SW%
ECHO.
ECHO INTEGRATING XP HOME UPG SP2
%INTEGRATOR% %INTEGRATOR_INI_XPH2% %INTEGRATOR_SW%
ECHO.
ECHO INTEGRATING XP PRO OEM SP2B
%INTEGRATOR% %INTEGRATOR_INI_XPP1% %INTEGRATOR_SW%
ECHO.
ECHO INTEGRATING XP PRO OEM SP2C
%INTEGRATOR% %INTEGRATOR_INI_XPP2% %INTEGRATOR_SW%
ECHO.
ECHO INTEGRATING XP PRO OEM SP3
%INTEGRATOR% %INTEGRATOR_INI_XPP3% %INTEGRATOR_SW%
ECHO.
ECHO INTEGRATING XP PRO UPG SP2
%INTEGRATOR% %INTEGRATOR_INI_XPP4% %INTEGRATOR_SW%


POWERPACKER.CMD


@ECHO OFF

::VARIABLES
::POWERPACKER EXECUTABLE
SET POWERPACKER="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER_V1.0R C9.EXE"

::POWERPACKER INI FILES
SET POWERPACKER_INI_XPH1="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER-XP-H-OEM-SP2.INI"
SET POWERPACKER_INI_XPH2="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER-XP-H-UPG-SP2.INI"
SET POWERPACKER_INI_XPP1="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER-XP-P-OEM-SP2B.INI"
SET POWERPACKER_INI_XPP2="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER-XP-P-OEM-SP2C.INI"
SET POWERPACKER_INI_XPP3="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER-XP-P-OEM-SP3.INI"
SET POWERPACKER_INI_XPP4="D:\MULTIBOOT\SIGINET\POWERPACKER\POWERPACKER-XP-P-UPG-SP2.INI"

::POWERPACKER SWITCH
SET POWERPACKER_SW=-PACK

%POWERPACKER% %POWERPACKER_INI_XPH1% %POWERPACKER_SW%
%POWERPACKER% %POWERPACKER_INI_XPH2% %POWERPACKER_SW%
%POWERPACKER% %POWERPACKER_INI_XPP1% %POWERPACKER_SW%
%POWERPACKER% %POWERPACKER_INI_XPP2% %POWERPACKER_SW%
%POWERPACKER% %POWERPACKER_INI_XPP3% %POWERPACKER_SW%
%POWERPACKER% %POWERPACKER_INI_XPP4% %POWERPACKER_SW%


10-22-08
0942 EDT

[Siginet]

I don't see INTERGRATOR.CMD and POWERPACKER.CMD but your batch calls them.

[rkillcrazy]

I don't see INTERGRATOR.CMD and POWERPACKER.CMD but your batch calls them.

You're right. Sorry 'bout that! I'll edit my post and drop those in there for you guys.

[Siginet]

Actually you can improve on the integrator params a lot by using this thread. ;)
http://siginetsoftware.com/forum/showthread.php?t=283

There are many new possabilities you can implement. The old method in this thread will be obsolete someday.

But your batch is great for the old method. :)

[rkillcrazy]

Actually you can improve on the integrator params a lot by using this thread. ;)
http://siginetsoftware.com/forum/showthread.php?t=283

There are many new possabilities you can implement. The old method in this thread will be obsolete someday.

But your batch is great for the old method. :)

Ooooooooooooooo.....more toys to play with! I'll have to set asside some time to play with these and see what damage I can do. ;)

10-23-08
2121 EDT

[Siginet]

Have fun. I'm sure you will. It was a huge update when I added all of those. ;)

I plan on doing the same thing with PowerPacker some time in the future.

[rkillcrazy]

Have fun. I'm sure you will. It was a huge update when I added all of those. ;)

I plan on doing the same thing with PowerPacker some time in the future.

I'm part of a small OEM. Regarding PowerPacker & Integrator, with the ability to purchase XP quickly coming to an end, how much longer will you be working on these projects? Will you be working on something similar for Vista?

10-24-08
0818 EDT

[Siginet]

I don't see the need for xp going away anytime soon. But I plan on doing the same for vista... or at least helping out. I personally hate vista and have not had a need for these types of things for vista. I actually get many customers who would rather have xp then vista.

I think XP will be around for a while. At least until microsoft fixes vista or maybe windows 9 will be better. ;)

[rkillcrazy]

I don't see the need for xp going away anytime soon. But I plan on doing the same for vista... or at least helping out. I personally hate vista and have not had a need for these types of things for vista. I actually get many customers who would rather have xp then vista.

I think XP will be around for a while. At least until microsoft fixes vista or maybe windows 9 will be better. ;)

I fully agree! I use Vista at home mainly 'cause I have to learn it. However, I can do so much more on XP in the ways of scripting and automation.