[Touch Pro2, Tilt 2 Windows Mobile General] papo:
no, and I don't understand why you asking when you already have fixed ideas about this stuff.

cab is not a magic tool. it's like a 'zip' file, containing all files going to be installed, which JUST means a controlled copying. plus you have xml file there included which is holding info about where which file is supposed to go plus is holding registry entries, which are just converted from reg to xml, plus version and some more info which is irrelevant. No other magic stuff is included. only maybe setup.dll which could (don't need to) contain program which could in addition copy more files and add more registry entries WITH more controllable way (checking if entry already exists and it that case make a backup of it a create its own.) the same setup.dll then can uninstall files and registry entries. because it knows where it did created backup, in case, of existing files and registries.

NOW I suppose you won't to go into trouble of creating your own setup.dll there is no tool for it, you would need to crack open c++ or something and create a whole project for it.

let's take a case where there is no special setup.dll in cab, more common. in this case all what is done is reverse of copying and importing registries. which means deleting.

what's holding you to delete files and registries if you know which ones?

to delete registry you just need to put - (minus) in front of every key in reg

I don't see a creating cab more convenient that just deleting couple of files, when you just want to do it once or twice.

Just in addition. If you don't have a user friendly not free software like ocp cab manager to create cabs, and there is no more then one another choice, you are left with microsoft basic tool to do so, there is a whole book about how to prepare inf for creating cab. and still no magic included there and even not a setup.dll or code compiler.

messaging is NOT a module.

what problem you have with s000, imageinfo.bin AND dsm, package.ini files and which of txt you mean. there is more different types of txt. I am not getting it all. And what kind of problem you have with all of them. Why you just not leave them alone and forgot them?

Again, if you don't exactly know what and why you want to twiggle with them that means you not need to be concerned with them at all. the folder name in which they are is the name of dll in which they will be converted to. Look at the whole folder as if it was a file, that's all you need to know and do about them.

the same goes for package.ini - it's only in certain case you can have problem with it. that is if you would want to use them 'the old way' as oems in 6.1 rom, but 6.1 rom can be done 'the new way' as well so I don't know why you need to bother with them? as well all dsm files in EXT group.

oem2ext tool is not creating them, and as I know there is no other tool so far. Means that if you wanted them, you would need to create them manually. and we are back to the same point. WHY you need to care about stuff you don't know about and don't need to know because you don't even know there is a way how would you possibly be in need of them.

For your own goodness and your and mine sanity, please just ignore all those problems you just created yourself :)

delete all package.ini and dsm you find in EXT if you can't stand looking at them. nothing will change.

it's all different in SYS OEM and ROM, there dsm have their role. But why would you want to bother to know what?

If you follow instructions I gave you before, you don't need to do nothing to them as well. and though they are copied to pda, they don't have any real function there. Just work with whole package folders, if you don't touch any file inside, you need to rebuild dsm. if you don't you don't need to. that's all about them. That they hold all info about package, used files, dependencies, certificates, that's still not important for you to know. Because you don't have use for knowing that.

no. they convert itself there and back. ignore them.

of course I assumed you WOULD disable the older version in case there is.

sorry I should have say so and not confusing you more.

that's as well a nice example how it could go wrong once you start messing with all the stuff you are now concerned with. Forgot modules (at least for now) forgot packages.ini, if you want to cook on your own, forgot cabs too, and everything you mentioned so far too.

in OEM SYS if you want to, replace, or delete whole folders only. don't touch ROM, and in EXT do what you want, add, move, delete. either whole folder or just a file if you know it's not necessary. e.g ringtone.

this way you'll not likely run into trouble like you mentioned.

As the next thing, but only when you'll have some of your own roms already working, you can try to go into individual files in OEM or SYS and rebuilding dsm. Again in EXT - no dsm, no package.ini are to worry you.

now sorry about my, in places, little upset mood. It's just I felt like I need to write the same thing twice. Please ask again if you run into trouble or are not sure about something, but please not about those, for you now useless, files again. :)

If you want to cook your rom, just do it. dump tmobile, add fm radio, change some themes, disable some pkgs, burn it and see how it goes. then change some more. do little steps, so you'll know when something goes wrong what it was. It's really not easy to brick htc, so just keep on trying.