RVMRVM Screenshot
RVM
official website
News Info Changelog Downloads Manual Forum Nav bottom


Manual

The main section.

screenshot

Pack: Whenever I reffer to the word "Pack" I am usually meaning each set of OS files we are using. So if you are adding a [Windows XP Professional Retail Edition With DriverPacks] that would be considered a "Pack." Then if you added another [Windows XP Professional Retail Edition Unattended Without DriverPacks] that would be a second "Pack" [Windows Home OEM Edition With DriverPacks] would be a third... and so on and so fourth.

PowerPack: This would be the complete package containing all of the packs that you want to have on one bootable disk.

Root: This normally means I am talking about the front most directory of your destination. (This is the "Root" of your disk / The "Root" of your PowerPack destination.)

INPUT: Source XP Files
This is where you will browse to the folder containing the "I386" directory you want to use for the current pack. (Do not select the "I386" directory... you need to select the drive or directory that the "I386" directory resides in.)

OUTPUT: PowerPack Destination
This is where you will browse to a directory on your hard drive that you wish to have the PowerPack created. Every pack that you add to this PowerPack should be pointed to the same directory.

Unattended Verses User Attended
This is a pretty important section. If you choose "User Attended" you can not add driverpacks. "User Attended is mainly used as a pack that will allow you to do Windows XP Repairs. When you choose "Unattended" you can not perform a repair... but you can do many other things. "Unattended" allows you the ability to add "BTS DriverPacks" (which will be explained later) and also you can use an answer file (winnt.sif) which will answer most or all of the windows setup questions, making everything "Unattended."

Winnt.SIF File Directory
Here you will need to browse to a folder containing the winnt.sif file you wish to use for this pack. The winnt.sif file is crucial to an unattended setup. The program does not create this file for you, (maybe someday), so you should do some research on how to do this. Each different pack may need a different winnt.sif file... so I make it a habit of having a directory called "WINNT" somewhere on my hard drive which has sub-directories of each different Version/Edition of XP. Then I place each different winnt.sif file in it's specific directory. This makes it easy for whenever I go to make a new PowerPack. A great site I recommend is: MSFN.ORG Creating a Basic Unattended Setup 

Grab the $OEM$ directory for this pack
Here you need to grab the $OEM$ directory that you wish to use with this pack. The $OEM$ directory is not completely needed to make an unattended setup... but it allows you to do some pretty cool things. You can use it to copy files to your XP installs, run batch files to install applications, and many other things. Another great site I recommend is: MSFN.ORG Batch Scripting

DriverPacks Verses No DriverPacks
This is where you choose whether or not you want to use B‚shrat the Sneaky's DriverPacks or not. These driverpacks integrate many drivers into your Unattended Windows XP install that would normally not be there. For more information you can go to Driverpacks.net.

Browse to the DriverPack BASE settings file
Browse to a settings file you exported in the DP_Base.exe file you downloaded.

Custom Pack Name
This instructs PowerPacker to use a specific directory name and assigns a descriptive name for the pack.

Create A Tri-Pack
PowerPacker will automatically create 3 versions of the OS in the Boot menu. For instance if you are using windows XP Pro Retail it would make:
Windows XP Professional Retail - Unattended With DriverPacks
Windows XP Professional Retail - Unattended
Windows XP Professional Retail - Attended (Perfect for repair option)

Windows XP Version and Edition
The Windows XP Version, which is initially guessed when you select an input source using the browse button, tells PowerPacker where to put your installation in its menu system. Same thing for the Edition. Simply select the correct one if it was not correctly detected.

Extra Files (Optional)
Extra Pack files are files you wish to add to this pack. For instance if you have modified files that you want overwritten or a custom setup.exe etc. There are also tips in the help file for running batch files etc in this area.

Extra Root Files are the basic same concept as Extra Pack files except they do not pertain to the individual pack. They pertain to the root of the disk.

Pack These Files Into The Destination
This is the button where most of the magic happens. After you make all of your selections you would click this button. It grabs all of the files/directories that you selected and puts them into the destination you selected. Then it will install the DriverPacks (if selected). It will create the Boot directory for this pack and it will hex edit the specific files needed to allow this pack to be booted to when it is selected from the boot menu.

Package ISO
When you are completely finished adding packs to the destination then it is time to package the ISO. This will ask you a couple of questions then it will run cdimage to create your optimized ISO file.
 

Weblinks Signet Software RVM Forum msfn.org ProfessorCPU

Betanews Softpedia
NGZ Webdesigns