ScriptPack and PowerPacker?

[scott.laptopguy]

I seem to be having some issues figuring out how to get RogueSpear's ScriptPack and power packer to work together nicely.

I have already created a standalone ISO that works perfectly. Upon using power packer it never initialized DP finisher or .net 3.0 framework. I figured out that power packer doesn't copy the $OEM$ directory. Now I got DP finisher to run, however still no .net framework.

My structure is:

\Root\XXXX\OEM\500_SETTINGS.INI
\Root\XXXX\OEM\CMDLINES.VBS
\Root\XXXX\OEM\DOTNET35.EXE

\ROOT\XXXX\$OEM$\CMDLINES.TXT
\ROOT\XXXX\$OEM$\ROE.EXE

CMDLINES.TXT:


[Commands]
"ROE.exe 937"
"cscript cmdlines.vbs"

500_SETTINGS.INI:


[cmdlines]
Custom005Title=.Net 3.0 & 3.5
Custom005File=dotNET35.exe
Custom005Args=

I have also tried putting OEM and $OEM$ in the root directory of the ISO along with the above and it doesn't change anything.

[Siginet]

I seem to be having some issues figuring out how to get RogueSpear's ScriptPack and power packer to work together nicely.

I have already created a standalone ISO that works perfectly. Upon using power packer it never initialized DP finisher or .net 3.0 framework. I figured out that power packer doesn't copy the $OEM$ directory. Now I got DP finisher to run, however still no .net framework.

My structure is:

\Root\XXXX\OEM\500_SETTINGS.INI
\Root\XXXX\OEM\CMDLINES.VBS
\Root\XXXX\OEM\DOTNET35.EXE

\ROOT\XXXX\$OEM$\CMDLINES.TXT
\ROOT\XXXX\$OEM$\ROE.EXE

CMDLINES.TXT:


[Commands]
"ROE.exe 937"
"cscript cmdlines.vbs"

500_SETTINGS.INI:


[cmdlines]
Custom005Title=.Net 3.0 & 3.5
Custom005File=dotNET35.exe
Custom005Args=

I have also tried putting OEM and $OEM$ in the root directory of the ISO along with the above and it doesn't change anything.

You should be selecting your $OEM$ directory in the option that asks for it in the PowerPacker window. ;)

I haven't heard of Roguespears ScriptPack. What is it used for?

[scott.laptopguy]

http://www.doitrightconsulting.net/forum/viewtopic.php?f=3&t=4

basically a bunch of VB scripts. I use it to take care of runonceex and configure accounts.

I have only tried putting OEM in the root. (OEM was already in the root since it was copied) I didn't put $OEM$ in the root because DP finisher was running. I will give this a try tomorrow morning for kicks.

[Siginet]

The $OEM$ dir does not need to be at the root of your disk unless you have made your files specifically look there. I tend to use my $OEM$ directory very lightly. I usually use batch files that reffer to my own "INSTALL" directory that I keep at the root of my disk.

You can also use the "Extra Root Files" section to copy specific things to the root of your disk. ;)

[scott.laptopguy]

I just manually used runonceex and it worked great. Everything else I was using from script pack I just made a clean-up script to take care of it. Now it works perfect.

[karol]

I just manually used runonceex and it worked great. Everything else I was using from script pack I just made a clean-up script to take care of it. Now it works perfect.


hello,,,,,,,,,,,
not only good but fantastic also unique material present in this post.........
Thanks for giving out this....................