Convert Ranger Packages

[alan-d]

Not looked into this too deeply yet but ....

 

Has anyone who has used the Ranger Packager to distribute software found an easy way to convert them to an MSI without going through the whole process of creating it from scratch using the original CDs or floppies?

 

Most of our 200 plus titles are stored on the local hard drive and can be reimaged from a hidden partition, but if we need to redistribute any software for any reason we would have to rebuild the image, which is a shame if we could use the one that Ranger has already created.

[alan-d]

Attached is an example package - problems with over zealous filtering prevent me sending it by email in any shape or form

[russdev]

i see it is using simlair methord to old rm connect 2.4 package builder

 

hmm

 

going to have think about this one...

 

russell

[russdev]

might have something

 

what drives does it store packages on ...

 

so say it is q drive

 

does it sote that zipped file

 

like this

 

q:\Fields and Matter (XP)

 

with Fields and Matter (XP).lock being at root of q:

 

Russ

[alan-d]

Yep - that's it exactly

[russdev]

ok try this create a file called copypack.cmd on q drive with following code in it

 

 

REM Copys Contents Of Ranger Package Over To C Drive

REM Writen By Russell Dyas 2005

REM No Support If This Blows Your Server/pc/network it ant my fault guvECHO is on.

q:

cd\

cd %1

cd CopyRoot

cd C

xcopy *.* c:\*.* /s /e /Y

cd..

cd..

copy *.rrg *.reg /Y

regedit HKCU.reg /S

regedit HKLM.reg /S

regedit HKUdefault.reg /S

 

 

login into a machine that has not got package installed on..

 

run msi creating tool of your choice run for the before snapshot

 

then from command prompt run file using q:\copypack nameofpackagefolder..

 

in case of above package

 

q:\copypack.cmd Fields and Matter (XP)

 

now that should copy contents over to harddrive run program make sure it works

 

then run after snapshot

 

test the msi

 

see how that goes

 

Russ

[ChrisH]

If the package is in the bare format of just the files and reg entries you could build your package from scratch and add the files and reg entries. This would give you a cleaner package.