Whether you are building a ROM with or without a 'kitchen' there are lots of .DSM files. Some of these are 0Bytes, others are tiny (2-3Bytes). What are they? I understand the .RGU files (registry entries), but the .DSM files I don't yet understand. I thought they were referenced by the 'option.xml' file in the \SYS folder (in most kitchens anyway?), however some are, others aren't.
Anyone have any details on this?
Thanks
Andy
ADB100 said:
Whether you are building a ROM with or without a 'kitchen' there are lots of .DSM files. Some of these are 0Bytes, others are tiny (2-3Bytes). What are they? I understand the .RGU files (registry entries), but the .DSM files I don't yet understand. I thought they were referenced by the 'option.xml' file in the \SYS folder (in most kitchens anyway?), however some are, others aren't.
Anyone have any details on this?
Thanks
Andy
Click to expand...
Click to collapse
I dont know what they are, but i do know 100%, that you delete these and you will kill your rom! These holder data that is needed in some case but in other not!!
funman said:
I dont know what they are, but i do know 100%, that you delete these and you will kill your rom! These holder data that is needed in some case but in other not!!
Click to expand...
Click to collapse
I don't want to delete them, however I am trying to resolve my L2TP/IPSec issue and I am now grasping at straws......
Andy
Good morning class, today we will be learning about dsm files...
Q:What are dsm files?
A:dsm files are thought to contain important encrypted information about file association.
eg What files are associated with the bluetooth function of your device? Well there's btdrt.dll, bthlink.dll, bthutil.dll, configmanager.dll, configmanager2.dll and so forth. We know this because we've researched the functioning of bluetooth with much detail, using such high tech methods as "What happens if i remove this file...**** my bluetooth doesnt work anymore...."
But how does your device know what files are associated with bluetooth functioning? Well in addition to the info contained in the .exe files it looks inside associated dsm files and decrypts the info thats in there.
Q: This seems confusing, is there some organised way of knowing what dsm files i have? or are they all just randomly put in my rom?
A:.dsm files are referenced by packages.sof. All of them are inside packages.sof
Q: packages.sof looks like a mess, how on earth do i read that?
A:the dsm filenames are just rearranged,
eg
9a6a05e1-cfde-4d32-9a82-85052c4d9de7.dsm appears as
E1 05 6A 9A DE CF 32 4D 9A 82 85 05 2C 4D 9D E7
So basically starting from the left side of the file name you split the first section of the dsm file name into pairs then swap the outside pair, then swap the inside pair.
eg 9a6a05e1 = 9a 6a 05 e1 = E1 05 6A 9A
Then you take the next section and swap the order of the pairs.
eg cfde = cf de = DE CF
Leave the next section alone
eg 9a82 = 9A 82
The last section isnt rearranged either. Its just split into pairs.
eg 85052c4d9de7 = 85 05 2C 4D 9D E7
So adding up all our sections we see that 9a6a05e1-cfde-4d32-9a82-85052c4d9de7.dsm is represented by E1 05 6A 9A DE CF 32 4D 9A 82 85 05 2C 4D 9D E7 inside packages.sof
Q: But how do i know what files are associated with my .dsm files?
A: A mysterious and clever man known only as bepe, gave us some tools. Some say that bepe fell from heaven, others say he was raised by a pack of wild german ladies with boobs as big as car tyres. Ask your history teacher about bepe.
Homework
Write a two-page report detailing why some dsm files (eg b50d833e-7d3f-44ac-615f-2da2c715cd93.dsm) appear in packages.sof but apparently dont reference any files....
Class dismissed, if anybody wants to ask me any questions, i'll be at the bar drinking beer.
Disclaimer: I wrote this with my best intentions, just a bit of fun. This is what i know about dsm files, it is immensely far from being 100% proven theory yet. I know the theory is flawed but it is a work in progress. If you think im wrong then feel free to correct me.
peter petrelli said:
Good morning class, today we will be learning about dsm files...
Q:What are dsm files?
A:dsm files are thought to contain important encrypted information about file association.
eg What files are associated with the bluetooth function of your device? Well there's btdrt.dll, bthlink.dll, bthutil.dll, configmanager.dll, configmanager2.dll and so forth. We know this because we've researched the functioning of bluetooth with much detail, using such high tech methods as "What happens if i remove this file...**** my bluetooth doesnt work anymore...."
But how does your device know what files are associated with bluetooth functioning? Well in addition to the info contained in the .exe files it looks inside associated dsm files and decrypts the info thats in there.
Q: This seems confusing, is there some organised way of knowing what dsm files i have? or are they all just randomly put in my rom?
A:.dsm files are referenced by packages.sof. All of them are inside packages.sof
Q: packages.sof looks like a mess, how on earth do i read that?
A:the dsm filenames are just rearranged,
eg
9a6a05e1-cfde-4d32-9a82-85052c4d9de7.dsm appears as
E1 05 6A 9A DE CF 32 4D 9A 82 85 05 2C 4D 9D E7
So basically starting from the left side of the file name you split the first section of the dsm file name into pairs then swap the outside pair, then swap the inside pair.
eg 9a6a05e1 = 9a 6a 05 e1 = E1 05 6A 9A
Then you take the next section and swap the order of the pairs.
eg cfde = cf de = DE CF
Leave the next section alone
eg 9a82 = 9A 82
The last section isnt rearranged either. Its just split into pairs.
eg 85052c4d9de7 = 85 05 2C 4D 9D E7
So adding up all our sections we see that 9a6a05e1-cfde-4d32-9a82-85052c4d9de7.dsm is represented by E1 05 6A 9A DE CF 32 4D 9A 82 85 05 2C 4D 9D E7 inside packages.sof
Q: But how do i know what files are associated with my .dsm files?
A: A mysterious and clever man known only as bepe, gave us some tools. Some say that bepe fell from heaven, others say he was raised by a pack of wild german ladies with boobs as big as car tyres. Ask your history teacher about bepe.
Homework
Write a two-page report detailing why some dsm files (eg b50d833e-7d3f-44ac-615f-2da2c715cd93.dsm) appear in packages.sof but apparently dont reference any files....
Class dismissed, if anybody wants to ask me any questions, i'll be at the bar drinking beer.
Disclaimer: I wrote this with my best intentions, just a bit of fun. This is what i know about dsm files, it is immensely far from being 100% proven theory yet. I know the theory is flawed but it is a work in progress. If you think im wrong then feel free to correct me.
Click to expand...
Click to collapse
OK, thanks for that. That is the first time I have seen that........
Another couple of questions then if you will oblige me?
1. In the various Kitchens that are out there, there is usually an 'option.xml' file in the \SYS directory that describes the various system packages that can be included in the ROM so they can be selected or excluded. The file is broken up into sections - transcriber, Enterprise, Games, Office etc. Listed in each of these sections are GUID's with a type and a GUID. Type is either 'p' or 'i'; 'p' references the .RGU file containing the registry settings. However the entries with the type 'i' don't seem to reference any GUID-named files I can see? I have applied the conversion logic you detail and the .DSM files don't tie-up with the GUID references, these may be unrelated though? For example the Autoupdate section:
Code:
<Item name="Autoupdate" group="System" checked="true">
<Guid type="p">8be73c02-3437-4c06-88c9-0a2e25bfaf2c</Guid>
<Guid type="i">c05687f7-7d0a-4738-9ecd-e043658f40cd</Guid>
</Item>
I can see the .RGU file (8be73c02-3437-4c06-88c9-0a2e25bfaf2c.rgu), however the second .DSM file is '89fc53c1-ec65-4648-9972-24afb3dcad3c.dsm', if the conversion logic you list is correct it should begin with c153fc89? Unless of course these are unrelated, however the number of GUID's listed always ties-up with the number of .DSM/.RGU files in each package (in different folders - e.g. Autoupdate, Autoupdate_Lang_0409).
2. How do you read the packages.sof? It just appears as few lines of unreadable characters in either Notepad or Wordpad?
3. Can .DSM files be transferred between ROM sources? In my quest to get L2TP/IPSec VPN working in the 5.2.1413 ROM I have been transferring the Enterprise files (ipsec.dll, ipsecsvc.dll, scard.dll & winscard.dll) from earlier ROMs (and other device ROMs) but have not had any (much?) success. Is there some logic to transferring files between ROMs?
Thanks
Andy
1. At this point in time I have no explanation as to why there are absent dsm's. I cant locate the dsm file you describe in any rom, i can only locate references to it. I can only speculate about why this is so.
2. Use a hex editor.
3. Yes you can trasfer dsm files but with mixed results. I have swapped some dsm files but when i did i moved the files associated with them as well. I had mixed success doing this.
I have exams on at the moment so I will look into this matter further towards the end of the month. Sorry my answers to your questions are so short. Good luck with your L2TP/IPSec VPN.
How to fix the button issue with games like worms world party on pocket pc
Install buttonfinder (freeware) on ppc and use it to get the codes for each button, when you press them one by one. (codes are like oxC1, just write down the last 2 digits.)
Install Skhexed (trial) and open it. open wwpsave.dat file from the worms directory on your pda.
the file need to be edited to make the game understand device buttons.
Find line 104 (or 109 for some devices especially hp). the line would seem like that:
---> 104 00 00 C1 C4 C4, (if line 104 seems like that: ''104 00 01 00 00 00'', then you have to search for an other line with the codes C1 etc ,and that would usually be the line 109. In that case the line 109 looks like this: 109 00 C1 C3 C3 00)
the 3 codes (Cx, x=number) would be usually in the last 3 colymns but maybe in the inner 3 ,like above. Those codes represent the buttons codes, used for fire, jump and jump2. (from left to right) and we have to change those codes with the codes we had written down from buttonfinder.
Save the changes and enjoy!
On some devices (especially HP like mine, but other brand also) that may dont work, or work for one or two buttons. in that case,the codes need to be changed with CC instead of C1, CD instead of C2 etc.
Click to expand...
Click to collapse
I have uploaded the .dat file modded for Universal,simply download it and replace the one you have on pda.
Feel free to post for other devices as well.
New Core of WM6.1 Pro - CE OS 5.2.19900 (Build 19900.1.0.2) with "12.5 MB Flashdisk".
There are so many ROM's (from the different builds) are floting around. But few of them I discovered has less database mess (i.e. Build 18188, 19400 and 19900). Finally, I decided to build my next rom based on 19900 and I would stick on that for some time (until I find another).
Changes and Features of v7.7:
-- New WM6.1 Core + OS (Build 19900)
-- New Memory Manager / Auto hibernate
-- New Advanced Config tool (by Schap) with custom config
-- New System Tray (delete link from startup if you don't like)
-- New Enhanced OEM Drivers and DirectShow filters
-- New (replaced) 6-button CommManager
-- New (replaced) Calculator
-- Fixed IRDA issue
-- Fixed ActiveSync over BT
-- Fixed external connection creation issue (e.g. BT under connection menu)
-- Fixed SMS backup/restore problem (by PIM Backup)
-- Updated DF's Task Manager / Registry Editor 3.0
-- Increased Glyph cache and Filesystem cache
-- GPRS call timer (on Connection bubble)
-- SD/SDHC support and driver switch-over tool (thanx OllieD for coding support)
-- ArcSoft MMS Composer 4.2 (max. MMS size set to 2MB)
-- TCPMP 0.72
-- BT FTP explorer
-- WkTask 1.1.7.3c (by waku) Task manager
-- Camera Application (Build 25626)
-- TodayAgenda 1.10 today plugin
-- WM5torage 1.78 (USB HDD Emulation)
-- Total Commander 2.5
-- Adobe Reader LE 2.0 (optimized)
-- Performance/overclocking applet (default 624 MHz)
-- DF's PIM Backup 2.8 (for contact, sms/mms etc. backup)
-- SynchroTime (by Grachov) for Internet time sync
-- PocketRAR 3.71 (with .zip/.rar association)
-- File-Dialog changer (for file browser enhancement)
-- Voice notification & ringtones
-- Improved Video renderer (game play should be OK now)
-- NetCF 3.5 and SQLCE 3.5
-- Improved Phone response
-- PIE hi-res support
-- Source filter issue resolved
-- SMS mode set to Threaded (no more back/restore issue)
-- Image size and compression issue of MMS Composer resolved
-- Managed Program applet removed (due to Class not registered error)
-- STK srvice and all the common utilities
-- SMS delivery fix (by Saman)
-- Set default search to Google (desktop) search
-- PIE cache (temp, cockies & history) relocated to the root (\IE Cache) for easy cleaning
-- PIE cache limit set to unlimited and tweaked to get best performance
-- Enhanced wifi driver with WPA workaround
-- Set default dev-id and BT name to "Universal"
-- Disabled incoming beams (to save battery)
-- Disabled today plugins - Date, Appointments & Tasks (replaced by TodayAgenda)
-- Almost all the Today item set to hidden (Unhide from Today settings, if needed)
-- Exe's & Dll's transformed to module (wherever possile)
-- Registry type set to file-based (instead of buffer-based)
-- Some performance tweaks
-- Unlock/Unhiding tool for extROM
-- Should work on G3/G4 both devices
-- 12.5 MB Flashdisk (for G3/G4 both devices)
-- PagePool - 5.6 MB
-- 128 MB RAM Support (may need to set PP => 0)
*Cab on Flashdisk (need to be installed manually, if required):
-- Windows Live
-- Transcriber
[Delete the "Software" folder under flashdisk if you don't need the provided CAB's]
I would appreciate a little DONATION.
Current Build v7.7:
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_v77_WM61_19900_19900_1_0_2.exe
Old Build v7.6:
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_v76_WM61_19209_19209_1_0_2.exe
Empty ExtROM (optional):
http://vidmes.com/xda/Uni/ROMs/Tomal/Tomal_ExtROM.rar
Special thanx to:
Bepe, Mamaich, Misar, DFT team, thingonaspring, TehPenguin and all other friends for their support in different areas.
Again, special thanx to the beta testers for their support for catching bugs.
Cheers,
//Tomal
Useful Information
I'm having so many email's and PM's to provide the info for building the ROM using Flashdisk (FD) and I thought I would provide some general info so that it would help our friends to get at least the preliminary questions answered.
What is Flash disk (FD)?
FD is the additional space usually un-utilized in the ROM (nk.nba). FD has no effect to the space allocated for regular storage (36 - 40 MB). Having FD means, your net storage is: Regular storage + FD. i.e. 40 + 15 = 55 MB.
How to make FD working?
Anyway, my (v7.x) ROM has a 15 MB FD; if you look on the nk.nba then you should find it the offset between 03060000 - 03EFFFFF.
There is a 512 bytes MBR starting from the beginning and then the FAT table. This is just like a physical disk and formatted using regular FAT12 ensuring the device compatibility issue. You need to be bit careful during the ROM building process. Overwriting/overlapping can damage the MBR/FAT header and disk won't be recognized by the OS. The best or easiest idea is to verify the mentioned offset by a hex editor before the ROM getting encoded or flashed.
03060000h: EB 3C 90 4D 53 44 4F 53 35 2E 30 00 02 08 02 00 ; ë<MSDOS5.0.....
03060010h: 02 00 02 00 75 F8 0B 00 3F 00 FF 00 00 83 01 00 ; ....uø..?.ÿ..ƒ.
...
...
...
03EFFFF0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
XIP of this ROM is very important or you may completely loose the FD functionality. Last but not least, most of the (OEM) drivers of this ROM are inter-dependant and exchanging may cause an unstable or non-functional ROM. You need to be careful during exchange.
Please note that, I have a few PM’s that the Hypercore kitchen is somehow unable to handle the FD but I don’t know why as I don’t use this kitchen so I’m sorry to answer.
How to configure MMS?
Create a blank MMS and tap on Menu, Options>Message Options>Servers. Now, tap on New and you can enter the servers parameters here.
Why I can't receive files over BT?
Tap on Start and then Settings>Connections>Beam, check on "Receive all incomming beams". Now, open BT setting under Comm Manager and enable file sharing under FTP tab. I hope you would be able to send/receive files over BT. But please note that, BT Explorer may not work on some cases so the best possible option is to send the files directly from other (paired) device and you should find the files under "\My Documents".
How to RESET / SUSPEND device?
Tap or Tap+Hold on the top-right of the today bar and then Functions>Reboot ...
Best of luck.
ENJOY!!!
//Tomal
nice release
Snapvue
Hi Ranju,
First off all thanks, testing now ...
first thing I noticed, no snapvue ;(
can you post a cab ?
further,
camera ok.
email creation after starting camera ok.
fast ok
some nice little extras.... very ok !
will test further,
again thank you,
greetings,
Wout
yes 128MB
Downloading now....
Will report all bugs found...
Cheers
WM 6.1 pro
These roms are nice and slick,thanks for your efforts. What memory is left at start up on this one please. What makes you think it will be buggy?
Regards
Jay
Update......
OK! So I couldn't wait!
Memory at first start is 39.45 mb storage and 21.94 mb programs, only bug found till now is tapping on wireless today plugin doesn't do anything (if it was supposed to)
Take care
Jay
htc .commanager fix. download it itll do the job
thanks ranju this rom looks like a good cook,ive been tryn to cook my own rom but i dont hav enough ram on my laptop
nice release
Will it work with 64 Mb Ram ?
Thanks Ranju for your permanent efforts in creation of stable ROMs. Your latest ROM is the fastest and stable for me. Very good job. Thanks.
QTEK9000
64 RAM
Very nice rom.Thanks.Works perfect with 64MB RAM
hotchillypepper said:
nice release
Will it work with 64 Mb Ram ?
Click to expand...
Click to collapse
Yep! It works very well indeed, About 39mb storage and 20mb programs. it all works very well, no hangups up to now!
Jay
sms/mms
very cool image, no hang up yet
very fast
PERFECT!!!!!
but
it would be nice, if sms/mms have separate folders! (i try to install arcsoft composer again)
after softreset, programhistory won't be cleared, is there any way to change this?
How much ram avilable on 64mb devices after reboot?
This the best ROM version or 128 MB Universal...
Congratulation!
Excusi me, I do not speak on behalf, ot englis...
Well done Ranju. Whilst I have not done any significant testing on this ROM, I trust it's just as fast as your previous ROMs.
One thing worries me though. I noticed that the Potocol Version is still 42.42.P8 and the ExtROM version is still 1.30.162 WWE and conseqyuently installing the Old O2 programs like "Active " and "HotSpots Directory".
Available free Program memory is down to 25.75MB. Is there a way I can Erase the ExtROM and re-flash this ROM?
Thx for this release.
Almost got my 1st heartache. flash error at 99%, 1st time!!!!
2nd try worked OK.
I changed SD drivers, to use my old SD.
1st try didn't work. Reverted to SDHC drivers, and SD didn't work after sleep ( that's normal ).
Switched back to SD again and on the 2nd try, worked ok. SD works after sleep.
As usual I will decode the ROM to learn a bit more.
DFT was also nice, but the ROM structure isn't the best. Lots of files and apps in OEMAPPS, which makes customize a hard job.
I was surprised by some apps in extended rom. Opera is not launching.
GSM is not default mode. It is set to auto.
Tomorrow I'll post more information about the ROM experience.
ultravox said:
Thx for this release.
Almost got my 1st heartache. flash error at 99%, 1st time!!!!
2nd try worked OK.
I changed SD drivers, to use my old SD.
1st try didn't work. Reverted to SDHC drivers, and SD didn't work after sleep ( that's normal ).
Switched back to SD again and on the 2nd try, worked ok. SD works after sleep.
As usual I will decode the ROM to learn a bit more.
DFT was also nice, but the ROM structure isn't the best. Lots of files and apps in OEMAPPS, which makes customize a hard job.
I was surprised by some apps in extended rom. Opera is not launching.
GSM is not default mode. It is set to auto.
Tomorrow I'll post more information about the ROM experience.
Click to expand...
Click to collapse
Interestingly, I got the failure at 99% first time, and it worked second time around.
I've had a single hang so far, but that could be down to the default overclocking. I've switched that off for now, so that should give a better indication of the general stability. So far though, it looks great, although I prefer SMS and MMS to be in separate folders.
The reworked IE for VGA is better than the version (in my opinion) than in the DarkForce release, and the "bug" listed that zoom in the context menu doesn't work, seems to work fine for me.
[Bug Report]
One issue I've noticed is that the width of the editors in Pocket Outlook (in common with a few other ROMs I've tried) seems to be a little bit too wide, and this causes a horizontal scrollbar to appear unnecessarily.
Cheers,
Steve.
Only 21 mb free after soft reset??
Day 1 Report
After 16 hours of use, no problems and no crashes/freezes... 1st time syncing is much much faster...
Good job,
Just highlight a few points of improvement.
1. Set the all SDHC block transfer rate to 64kbyte as it will give better and balanced performanced in TCPMP (played 1.5 hours DVD resolution movie, never paused at all) Windows Media Player...
2. Set the performance overclocking to 520MHz to better stability. Power users can manually set it to 624MHz
Cheers,
Will have more to report soon.
Hey guys!
Just figured out that with the new Android Developer page, Google made all the oooooold releases of the SDK available, including the ancient Milestone 3 and Milestone 5 (Astro Boy and Bender) releases. These are the ones what had the original Cylon style boot animation, and I decided to grab it.
Problem is: none of the current APK reverse tools support or even recognize the old magic header. The dex header is the following:
Code:
64 65 78 0A 30 31 33 00
This is for Milestone 5.
I really want to reverse this, only for the Cylon code, so if ANYONE knows a solution, please, post it!