Originally Posted by kancrutt

dear chriskay, can u upload WMP Skins (like in ur ROM) in cab file?
thanx in advance

there you go. i just extracted them and put them in a cab. i hope it will work. they will be installed to the windows folder. if anything goes wrong, you can just uninstall them. let me know how it went.

There is also an MUI which is commonly used for the keyboard skin...

This one contains some colour information... msim.96.dll.0409.mui

Any way... Great looking ROM although I need to charge my battery before I can use it ...

Also... The way I used Neokit to replace modules etc was to use one of the tools to turn it into a DLL and not a module, and then swap that DLL for the modified/upgraded one. Not sure if it should work, but it does!

Originally Posted by l3v5y

There is also an MUI which is commonly used for the keyboard skin...

This one contains some colour information... msim.96.dll.0409.mui

yeah, i came across that, too. but since there is no such file in cloudyfa's rom, i only replaced the other dll, which seems to have work.

The thing I discovered, is that if that file is there, the keyboard skin is of that file regardless of what the DLL does.

Although I did some simple add/remove cooking, the concept of module is not quite clear to me. Does one of you know a source for detailed information?

And yes, hunger for perfection IS genetic.....

Originally Posted by rondol1

Although I did some simple add/remove cooking, the concept of module is not quite clear to me. Does one of you know a source for detailed information?

And yes, hunger for perfection IS genetic.....

this might be a starting point http://forum.xda-developers.com/showthread.php?t=331094.

what i have noticed so far:
each module folder contains the file itself PLUS an image file (.bin) and some image-part files (s000, s001 etc). if you now just replace the file itselft which differs in size, the information in the image file and image-part files won't match the new file inserted (just calculate the total size of all image-part files and you will see it is the same as the size of the file itself). ALSO, if you replace the entire module folder, the new file will most likely not work as i experienced in several experiments with the touch.dll. so, i assume that the image files also contain information about the file with respect to the entire rom (part-whole ratio). therefore you HAVE to use g'reloc.exe to fix the newly inserted file or module. another tool from the link above is called "m'reloc.exe" which is described to be used for single modules only (have not tried it yet though). and if you want to build a module right from the scratch, you first have to convert the file by the help of reversmode.exe and then copy the original file itself into the new module (and finally fit it in by g'reloc.exe).

this is what i have learnt by experimenting. but since i am not a programmer, i cannot tell you more. but these approaches seem to work as you can see in my first rom mod here.

i at least am quite proud of my work and enjoy this pseudo-official wm6.1 release.


p. s.: what do you think about the "new" commmanager? found out how to strip off the skin keeping all functions availble; not like korand's old 7-function commmanager.

With NeoKit, you can make the modules automatically which saves a bit of time.

Originally Posted by l3v5y

With NeoKit, you can make the modules automatically which saves a bit of time.

really?? how? i use neokit and never found a way other than the one with g'reloc.

Downloading, thank you for your good job~

In neokit, go to the "files" tab, right click on a file and select "Use Module" or "Use DLL" that may not be exactly what it says, but I don't have Nekit to check atm.