[REQUEST] Paint.net 3.0

Questions or comments on the switchless installers? Want to create a new one? Talk about it here.
Post Reply
arepie
Posts: 16
Joined: Tue Dec 26, 2006 3:11 pm

[REQUEST] Paint.net 3.0

Post by arepie » Tue Feb 06, 2007 3:20 pm

Would anyone make an addon for this paint.net ver 3??
more information you can find it here

thanks

crocodilechris
Posts: 65
Joined: Tue Jan 09, 2007 12:10 pm
Location: Berlin, Germany

Post by crocodilechris » Fri Feb 09, 2007 3:03 pm

you easyly can do it by yourself.
I do it the following way:
- download PaintDotNet_3_0_BetaNews.exe
-> extract files from PaintDotNet_3_0_BetaNews.exe
-> take PaintDotNetSetup.exe
-> make a selfextracting exe-file with WinR
I used this parameters, you can lookup the installer-parameters in the helpfile, the rest have to be as showed:
Setup="PaintDotNetSetup.exe" /auto DESKTOPSHORTCUT=0 PROGRAMSGROUP="Zubehör"
TempMode
Silent=1
Overwrite=1
--> at last you have to install the file via GuiRunOnce (Winnt.sif) or via RunOnceEx($OEM$\cmdlines.txt -> RunOnceEx.cmd).
I do it via RunOnceEx, but you have to decide at your own, or somebody else will help, because I don't know which method is better.
greetz crocodilechris
using nLite

crocodilechris
Posts: 65
Joined: Tue Jan 09, 2007 12:10 pm
Location: Berlin, Germany

Post by crocodilechris » Sun Feb 11, 2007 8:19 am

okay doublepost, but it have to be ;)

here is an archive with the important files for RunOnceEx-Installation:
http://home.arcor.de/crocodilechris/Add ... tories.rar

Archive contains following structure (for experienced clear and unnecessary):
$OEM$
|-$1
_|-Install
__|-PaintDotNet.x86.exe
|-cmdlines.txt
|-RunOnceEx.cmd
PaintDotNet.x86.exe install-parameters
Setup="PaintDotNetSetup.exe" /auto PROGRAMSGROUP="accessories"
TempMode
Silent=1
Overwrite=1
a shortcut is not set in "program files", but in ->"accessories" like Paint.

@arepie
the $OEM$ folder have to be copied in the root directory of your xpcd. If you already have one than copy just the files or edit already existing ones.
You have to activate OEMPreinstall.
In nLite you find it in "Unattendend Setup" or you write it manually in Winnt.sif:

Code: Select all

[Unattended]
OemPreinstall="Yes"
if you have any questions then it is allowed to ask. ;)
Last edited by crocodilechris on Mon Feb 12, 2007 5:40 pm, edited 1 time in total.
greetz crocodilechris
using nLite

User avatar
5eraph
Site Admin
Posts: 4621
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Sun Feb 11, 2007 9:07 am

If you're clever with switchless installers, crocodilechris, then you can create a SVCPACK preinstaller for any RunOnceEx-only installer that does the following at T-13:
  • Extracts the RunOnceEx executable to a predefined directory (bypassing WINNT.SIF edits and $OEM$ distribution folders), and
  • Adds the necessary registry entries to execute the installer at RunOnceEx from the predefined folder (including any clean-up code necessary for the specific installer).
Benefits:
  • Less complicated to implement if you already know what order everything needs to be installed.
  • Easier to add and remove RunOnceEx installers "as needed" (no need to edit anything except SVCPACK.INF).
  • Preinstallers can be out-of-order in SVCPACK.INF while guaranteeing that the ROE installers will execute in their intended order. (Requires preplanning when building your preinstallers.)
  • Does not require a WINNT.SIF file or any type of unattended setup.
Drawbacks:
  • You must know beforehand what order everything needs to be installed in.
  • Very hard to change ROE install order after creating the preinstallers.
  • Cleanup code must be included in each preinstaller.
  • A preinstaller must be created for each (group of) ROE installer(s).

crocodilechris
Posts: 65
Joined: Tue Jan 09, 2007 12:10 pm
Location: Berlin, Germany

Post by crocodilechris » Sun Feb 11, 2007 11:14 am

okay I'll try to make an addon, but i have to learn it by myself, but i think a cmd will copy the file and also can register the runonceex-registries, but i think there is one big PROBLEM:
- the numbering of the runonceex-thing. does it matter if i use same numbers as someone else or does this evoke an error?
greetz crocodilechris
using nLite

User avatar
5eraph
Site Admin
Posts: 4621
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Sun Feb 11, 2007 4:22 pm

If you use the same numbers that somebody else uses then the entries written last take precedence (they'll overwrite the previous ones).

RogueSpear typically uses ROE 010-030 for his dotNET installers, so anything after that range should be fine. 990 is used ty thuun in his avast! ROE addon (which uses the method I described above).

crocodilechris
Posts: 65
Joined: Tue Jan 09, 2007 12:10 pm
Location: Berlin, Germany

Post by crocodilechris » Mon Feb 12, 2007 10:54 am

okay 5eraph everything works, but 1 thing is still a problem:
uses RogueSpear
REG ADD %KEY%\ROE 010
or
REG ADD %KEY%\010
I have to mind, because PDN3 have to be installed after FRMWRK... and its listed in the registry alphabetically, or are my thoughts wrong?
greetz crocodilechris
using nLite

User avatar
5eraph
Site Admin
Posts: 4621
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Mon Feb 12, 2007 1:08 pm

After looking through his latest ScriptPack, RogueSpear uses the following numbers:
  • 005
    010 - for dotNET 2.0
    015
    020
    030
    040
    050
    060
    070
    080
    100
    110
    120
    135
    145
    150
    160
    170
    190
    - System Reboot
    200
    215
    225
    235
    245
    250
    300
Gaps in the sequence seem to be intentional.

You are correct concerning the alphanumeric execution order. RogueSpear uses "010," not "ROE 010." ;)

crocodilechris
Posts: 65
Joined: Tue Jan 09, 2007 12:10 pm
Location: Berlin, Germany

Post by crocodilechris » Mon Feb 12, 2007 5:41 pm

greetz crocodilechris
using nLite

Post Reply