Hello.
First of all thanks to all addon makers for providing the absolute way of customizing of windows.
Now i request to all addon makers that you should mention in your addon, weather it is compatible with nlite or RVMi.
I am so much confused about lot of addons, whether these are compatible with nlite or RVMi....
A polite request to addon makers.....
- Jamshed_11946
- Posts: 67
- Joined: Sun Aug 24, 2008 12:34 pm
- Location: Pakistan
- Contact:
Any addons on this forum should be compatable with the RVM Integrator. If they are not then they do not belong here.
You can also find RVM Integrator Addons on the official integrator site as well:
http://integrator.siginetsoftware.com
You can also find RVM Integrator Addons on the official integrator site as well:
http://integrator.siginetsoftware.com
- Jamshed_11946
- Posts: 67
- Joined: Sun Aug 24, 2008 12:34 pm
- Location: Pakistan
- Contact:
-
- Posts: 64
- Joined: Sat Apr 26, 2008 9:13 pm
Unfortunately, Kel's add-ons have a problem with RVMi.
Dunno if its changed, but check out: http://www.wincert.net/forum/index.php?showtopic=4126
Dunno if its changed, but check out: http://www.wincert.net/forum/index.php?showtopic=4126
Kelsenellenelvian wrote:Apparently the way I produce my addons now is not liked or understood by the RyanVMintegrator!!!
So when using ANY current Package made by me YOU MUST USE nLite!
At least untill this gets righted.
For the curious ones:
I am now building my addons in vista and using TugZip. For some unknown reason RVMi does not like the result therefore causing final install errors.
The same is showing for ricktedo64's addons also...
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
- Jamshed_11946
- Posts: 67
- Joined: Sun Aug 24, 2008 12:34 pm
- Location: Pakistan
- Contact:
i was facing problems almost all kels addons
Oh.Now i have understand that why i was facing problems in addons.Are Ricktendo's addons moved from RVMi to nlite?Any other addon maker addons?
addons should be compatible with integrator besides a few that are intended for nlite only using the following commands in entries* file:
same for rvmintegrator ( using different other commands that nlite cant intercept ) besides some undocumented ones like [filecopy] ...
http://integrator.professorcpu.net/inde ... al&entries
as you see, the the differences between nlite to RVMi addons are relative to what the entries file holds.
other then the listed commands that are unique to each tool the basic addons should be compatible with both (using other basic commands that are supported by both.)
http://www.nliteos.com/addons/index.html* neededcomponents (uncheck or warn about the needed component)
* keepfiles (protect needed files from removal)
* updatecabs (update a cab file)
* guirunonce (lines to write inside winnt.sif - guirunonce)
* registry_addreg (add registry entries, INF syntax)
* registry_delreg (remove registry entri
# txtsetup_remove (lines to remove from txtsetup.sif)
# dosnet_remove (lines to remove from dosnet.inf)
same for rvmintegrator ( using different other commands that nlite cant intercept ) besides some undocumented ones like [filecopy] ...
[WinntSif]
The WinntSif section allows you to change anything within an existing winnt.sif file.
Section\Key=Value
;This section contains entries that need to go into the winnt.sif file
[WINNTsif]
Shell\DefaultStartPanelOff=No
[FileCopy]
This allows you to copy a file which exists in the I386 directory to another location within I386.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
FileToCopyInI386.ext,ToCopyTo\FileToCopyInI386.ext
You can copy from or to the outside of the I386 directory as well if you use ..\ to represent go back one directory.
Like:
filename.exe,..\newfile.exe
;This section allows you to copy a file to another place in your destination.
[FileCopy]
Eula.txt,rvmtemp\Eula.txt
Eula.txt,@Plugins\Eula.txt
[FileMove]
FileMove does the same thing as FileCopy except it moves the file.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
FileToMoveFromI386.ext,ToMoveTo\FileToMoveFromI386.ext
;This section allows you to move a file to another place in your destination.
[FileMove]
RUN_ME.cmd,..\RUN_ME.cmd
RUN_ME2.BAT,@Plugins\RUN_ME2.BAT
[DirCopy]
DirCopy is the same concept as FileCopy except it is dealing with entire directories.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
DirToCopyFromI386,ToMoveTo\DirToCopyFromI386
;This section allows you to copy a directory to another place in your destination.
[DirCopy]
WINNTUPG,rvmtemp\WINNTUPG
WINNTUPG,@Plugins\WINNTUPG
[DirMove]
DirMove Is the same as DirCopy except it moves the directory instead of copying it.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
DirToMoveFromI386,ToMoveTo\DirToMoveFromI386
;This section allows you to move a directory to another place in your destination.
[DirMove]
DPfiles,..\DPfiles
M2,..\M2
WINNTUPG,@Plugins\WINNTUPG
[FileDelete]
FileDelete Will delete a file in the I386 Directory.
FileToDeleteInI386.ext
This is a simple method to delete a file from the I386 directory. You can also use ..\filename.exe to delete a file from the root as well.
;This section allows you to delete a file in your destination.
[FileDelete]
Eula.txt
..\Readme.htm
[DirDelete]
DirDelete will remove a folder from the i386 directory.
DirToDeleteInI386
This is a simple method to delete a folder from the I386 directory. You can also use ..\FOLDERNAME to delete a directory from the root as well.
;This section allows you to delete a directory in your destination.
[DirDelete]
WINNTUPG
LANG
WIN9XMIG
[RunFile] *New*
This section allows you to Run a file before driver.cab is or is not repackaged.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
I also made it so you can use parameters in the [RunFile] section as well.
*New* in v1.5.4 Beta6 you can use these special variables to return certain info to your scripts:
@ROOT = The path to Root Of Destination: @ROOT\I386
@DESTINATION = The Path To The Main working dir. I386 for x86 and AMD64 for x64.
@SP = Returns the ServicePack info. (SP1, SP2, SP3...)
@WIN = Returns the type of windows. (pro, home, 2k3, 2000 or other)
@LANG = Returns the Localized Lang of the disk according to PRODSPEC.INI
*New* in 1.5.4 Beta7 This Variable is added as well:
@RVMiLOG = The Path To The Current log file.
You can place ,HIDE at the end of the file to have a batch file run hidden.
[RunFile]
RUN_ME.cmd
REGEDIT.cmd,HIDE
AdAware_AutoUpdater.exe
MYBATCH.BAT:/silent /log:"@PLUGINS\mylog.log",HIDE
[HexEdit]
HexEdit allows the integrator to patch files on the fly.
Now you can patch the file on the fly!
Other benefits to this are that you can put all of the patching information to take care of multiple file versions. The integrator makes sure you are patching the correct file version with the correct info.
Path\to\file|FileVersion|OffsetToEdit|BeforeHexCode|AfterHexCode
The BeforeHexCode can be * which is wild. If you use * then it doesn't matter what the before code is. The integrator will edit that offset anyways.
[HexEdit]
I386\sfc_os.dll|5.1.2600.2180|320|C812|E2E0
I386\uxtheme.dll|6.0.2900.2180|113548|81EC88000000A118|33F68BC6C9C20800
I386\uxtheme.dll|6.0.2900.2180|218622|0000|7272
I386\uxtheme.dll|6.0.2900.2523|320|C01204|19FF03
I386\uxtheme.dll|6.0.2900.2523|105084|81EC88000000A118|33F68BC6C9C20800
I386\uxtheme.dll|6.0.2900.2523|218622|0000|7272
I386\uxtheme.dll|6.0.2900.2845|104746|83EC1C568D4DE4|33C0C9C2040090
I386\uxtheme.dll|6.0.2900.2845|320|634C|E33E
[ExpandCab]
The ExpandCab Section is used to Expand Archives or files.
This used in conjunction with the new [CreateCab] section will be useful for recompressing files other than driver.cab. These new sections can be used in UpdatePacks and Addons.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
[ExpandCab]
PathToCabToExpand,PathToDirectoryToExpandTo
[ExpandCab]
CMPNENTS\MEDIACTR\I386\MEDIACTR.CAB,CMPNENTS\MEDIACTR\I386\MEDIACTR
CMPNENTS\MEDIACTR\I386\SONIC.CAB,CMPNENTS\MEDIACTR\I386\SONIC
CMPNENTS\MEDIACTR\I386\SONIC.CAB,@PLUGINS\ExpandedCabs\SONIC
[CreateCab]
The CreateCab Section is used to Compress CAB Archives or files.
This used in conjunction with the new [ExpandCab] section will be useful for recompressing files other than driver.cab. These new sections can be used in UpdatePacks and Addons.
*New* in RVM Integrator v1.5 there is a new @PLUGINS variable that can be used in this section which represents the integrators .\Plugins\ directory located alongside the RVMIntegrator executable.
[CreateCab]
PathToDirectoryToCreateCabFrom,PathToCabToCreate
[CreateCab]
CMPNENTS\MEDIACTR\I386\MEDIACTR,CMPNENTS\MEDIACTR\I386\MEDIACTR.CAB
CMPNENTS\MEDIACTR\I386\SONIC,CMPNENTS\MEDIACTR\I386\SONIC.CAB
@PLUGINS\ExpandedCabs\SONIC,CMPNENTS\MEDIACTR\I386\SONIC.CAB
[DeleteLinesWith]
The DeleteLinesWith Section is used to remove lines of text from files that contain the specified string.
[DeleteLinesWith]
FileToEditInI386,StringToSearchAndRemove
[DeleteLinesWith]
I386\drvindex.inf,31x5
[KeyDelete] ..........
http://integrator.professorcpu.net/inde ... al&entries
as you see, the the differences between nlite to RVMi addons are relative to what the entries file holds.
other then the listed commands that are unique to each tool the basic addons should be compatible with both (using other basic commands that are supported by both.)