100 Basics

200 Prog-Support

300 Drivers Audio
310 Drivers Disk
320 Drivers Display
330 Drivers Modem
340 Drivers Network
350 Drivers Other

400 Files

500 Anti Virus
510 Burning
520 Clone + Copy
530 Disk Utilities
540 Editor
550 Explorer
560 Image
570 Multimedia
580 Office
590 Picture
600 Recovery
620 Registry
650 Securety
670 Web Browser
680 Zipper

700 Network
780 Other Utilities

790 Games

800 free (reserved)

 

900 Custom Settings

Naming of BartPE plugins and the consequences on the

"Processing Sequence" and "Display Sequence"

The processing sequence is ruled by folder name

and within a folder by INF-name.

 

pebuilder.inf -> pluginFolder -> INF-name -> next pluginFolder etc.

So only in case of multible INFs in one pluginFolder, the INF-name matters for the processing sequence (example=XPE).

 

The display sequence is ruled by plugin name (inside the INF).

 

Adding the category number to the names, gives you a logical display sequence,

it has no impact on the processing sequence.

 

If, for example, all names of your "Disk Utilities" would start with "530", they are all displayed together in PE-builder,

listed alphabethically within this category.

The categories jump at least in steps of 10, to

allow for your own sub-categories

in areas, where you may need a finer split.

 

Only the first two digits are actually used for the category,

the last digit is to identify particular plugins, if you want to force a sequence (other than alphabethical) within a category.

 

Examples of plugin names
using these categories:

Name="310     Adaptec ASPI"
Name="400     Office 2003 viewers"
Name="500     AntiVirus Personal"
Name="510     Ahead Nero Burning Rom"
Name="580     Open Office"
Name="590     XnView"


I use 5 blanks between number and text, because the overall look in the plugin display is better.

 

For a visual break between main categories, I use devider dummies (plugins with only a devider line).

Here some examples: download deviderDummies

 

Suggested naming example for the INF itself: 310_ASPI.inf

 

It is all personal taste and this is just the system I am using.