[Windows Mobile Software Development] ervius:
ok, the platformrebuilder by bepe, is quit different from all you know,

1st: external packages don't have dsms and rgu, but only a "app.reg" (is the rgu renamed!), so you cannot insert all of them, but only an app.reg, that is last that overwrites all previous, for dsm, so, nothing to do, maybe you can use \oem folder to insert also all external packages, and have all dsm and rgu ready to be copyed, (so, with a modified bat, or inserting the flag into my visualkitchen!), you can reinsert all dsms and rgus into before launch platformrebulder.exe, but,

2nd: the platformrebuilder.exe, uses the xip 72xxx-xxxxx-xxxxx dsm from xip, moveing it into imgfs part and inserting into it all files and modules of dumped rom, so you'll have one big dsm into: 72xxx-xxxxx-xxxxx, and all other dsm like files of the same packages, so, maybe probally you'll have same result, also becouse tool new and old by bepe to build packages use the "packages.sof" file, that is a kind of databases that contains all dsms present into dumped rom, and in this case, the platformrebuilder.exe modifyes it inserting only 72xxx-xxxxx-xxxxx dsm into, so all tools reading it recognize only that dsm like package and rebuilding rom packages, only 1 will be created, I thinked to an otther way, a kind of my own dsm: I explayn:

in ever package, oem\ sys\ and ext\, inserting a file, like pack_000, pack_001 pack_003 ecc, that contains all files stored into the package, so, with a new tool by me, reading them, you will have:

1st into list: the name of package, and from 2nd to end, all files/modules like:

oemdrivers (name of packages and its position in rebuilded dumped!)

asyncmac.dll

atadisk.dll

bthamb.dll

etc... etc...

so, having a list of "Pack_xxx", and reading them, you can have all original packages, with all structured files into, but remains the problem of dsms and rgus, maybe like an ini files, you can have:

into pack_xxx file:

..................................................

[package]

oemdrivers (name of packages and its position in rebuilded dumped!)

[files]

asyncmac.dll

atadisk.dll

bthamb.dll

etc... etc...

[registry]

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\PCMCIA]

"Name"="PCMCIA/Compact Flash Device"

"Folder"="Storage Card"

[HKEY_LOCAL_MACHINE\Drivers\Builtin\SDBusDriver]

"Order"=dword:15

.................

[initflashfiles]

Directory("\windows\start menu\programs"):-File("Esplora risorse.lnk","\windows\Esplora risorse.lnk")

..................................................

and maybe all can have your rom , structured, redumpeable, and rebuildable, and ready to be changed by "someone" into his own rom, without any kind of greetings for real "creator", for me is useless...... and don't like spent more time about, also becouse;

3rt: platformrebuilder.exe by bepe, use a strong protection against rom porting, if you use that tool to build a rom for diamond, and also if you have all my "pack_XXX" inside, so, you can easly reconstruct all packages, ig you want to rebuild the rom for raphael, it never boots on a raphael, becouse that rom, builded for "diamond", only on a diamond boots, seems that bepe deletes all relocking references into modules, so they cannot be never reallocated for other devices, only for diamon.

So, finally, the ideas about are present, and not few (the idea of pack_xxx, like a kind of new dsms generations, is genial!), are useles (for you!), for me, is genial that bepe shared his new, platformrebuilder.exe tool, so, with my multilangual visualkitchen, you can easly build your own rom, and nobody can change some graphical parts on it and share like his work, not yours ;)

bye!!!