What are the .dsm and .rgu files in WM5 windows directory? THere seems to be a lot of them. they have names like
992ed1cd-7c37-4c19-928c0435e457a125d.dsm
Any ideas?
I was wondering this myself, new to WM5, that's for sure!
WinBackup File Extension Library
DSM ( .DSM ) - File Extension Information
Extension: DSM ( . DSM )
Description:
DSM is the file extension for music modules associated with MOD, DSI and DSIK.
Format Category: Audio
Actions: Open,Play
thats pretty much all i could find out about it, rgu couldnt find anything relating
how we can remove it ?
all this file have the propriety's with rom file
sacaman
Beyond the Tech answered my question at hofo. And the rgu files are registry keys that are run at reset. The rgu files can be read by any text editor. There seems to be a dsm file for each rgu. So i don't hink deleting them is a good idea.. I almost deleted them myself.
Hi all,
I'm trying to edit ROM on a new device (FSC Loox T830) using the provided tools for the Scoter Kitchen.
First thing that I'm trying to do is unpacking the ROM, repacking again and flashing to see if everything is working.
1) I have already a ROM image, by using the following commands I have the dump:
* prepare_imgfs myrom.rom -n
* viewimgfs imgfs_raw_data.bin
2) Then I repacked everything again with the reversed tools and flashed the device -> Result was OK
--
as the result was ok, now the second try starting again from the beginning:
This time I've dumped the ROM again with the same tools and then run DMP2PKG program, which highlighted yellow as missing the following:
d92a4f0a-378a-4482-8fd3-bd127a05e4de
723fb954-d931-4348-b672-82a188e587b5
but worked error free, then I've copied into ROM\XIP folder boot.rgu (taken from my device) and run PKG2DMP. It worked and halted with an error "initflashfiles.dat not found"
I have then compared the original default.hv user.hv and packages.sof files (converted to .txt) with the unpacked/repacked by PKG2DMP program. Here are the differences:
differences on user.hv:
Original Dump:
[HKEY_CURRENT_USER\Software\Microsoft\Windows]
"LangDbPath"="\\mxip_lang.vol"
"DbPath"="\\mxip_initdb.vol"
Repacked:
[HKEY_CURRENT_USER\Software\Microsoft\Windows]
*missing line*
"DbPath"="\\mxip_initdb.vol"
Difference on default.hv:
Original Dump:
[HKEY_LOCAL_MACHINE\System\ObjectStore\RegistryUpdate]
"packages.sof"=hex:C6,E4,A2,C5,90,21,C8,D4,C0,BD,B5,B2,6D,1E,12,D5
"6461d201-3f67-9f90-77bf-e6f0a2bfed3b.rgu"=hex:3B,EC,29,3E,E8,6B,48,B1,B0,85,CA,55,C4,EB,58,B3
"boot.rgu"=hex:47,C0,24,EC,58,60,53,AA,38,48,F0,BB,50,91,44,E6
Repacked:
[HKEY_LOCAL_MACHINE\System\ObjectStore\RegistryUpdate]
"packages.sof"=hex:9E,EE,79,81,ED,31,54,86,5E,0F,0F,A9,78,4F,28,3B
*missing line*
"boot.rgu"=hex:F8,AB,E2,1C,48,C7,75,A3,1B,8F,E6,69,B0,25,EA,14
This is very strange IMO as I've made no changes to the packages...Just unpacked/repacked to test...Obviusly the flash with the above changes blocked the device prior to boot.
Any help is really appreciated! (Bepe , JKR?)
PS: I've opened the same topic on buzzdev.net forums
Thanks & BR
Hi, you have to find that 6461d201-3f67-9f90-77bf-e6f0a2bfed3b.rgu... is in on your device?
bepe said:
Hi, you have to find that 6461d201-3f67-9f90-77bf-e6f0a2bfed3b.rgu... is in on your device?
Click to expand...
Click to collapse
Hi Bepe, first of all thanks for lightning fast reply!
Yes, both .dsm and .rgu are on the device, but not present in the dump.
.rgu content is the missing line from user.hv:
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Windows]
"LangDbPath"="\\mxip_lang.vol"
Why boot.rgu, initflashfiles.dat and this file are present on the device but not in the dumped Rom (which I downloaded from the official web page of FSC) ?!
I have now looked and found also the other missing files which I'm attaching for you to have a look.
There is no .rgu file and they're not present in the dump as well as the previously mentioned files...
read your PMs ...
I'm still learning here and have been looking into registry settings. I've tried editing the default.hv, and while rgucomp says it builds fine, this results in the ROM not booting.
If I look at the rgu from the modified default.hv, its in a different order than the original.
Just wondering if I need a different app, or if there is a kitchen that will build a new default.hv with the rgu's from the imgfs dump.
Da Mafia said:
I'm still learning here and have been looking into registry settings. I've tried editing the default.hv, and while rgucomp says it builds fine, this results in the ROM not booting.
If I look at the rgu from the modified default.hv, its in a different order than the original.
Just wondering if I need a different app, or if there is a kitchen that will build a new default.hv with the rgu's from the imgfs dump.
Click to expand...
Click to collapse
You may ask to l3v5y for his kitchen. I'm using it if i need to re-arrange packages. For simple files modify I use my tgtool set.
Does Visual Kitchen use *.hv files to build the registry or are boot.hv , use.hv , default.hv ignored?
In what order are *.hv, rgu, *.reg processed?
And which folders are processed first? ROM>SYS>OEM>EXT
I know that *.provxml are processed after first boot and *.xml have to be invoked during customization.
It seems that EVK uses the rgus to make the hives thats why you dont need to play with them anymore.... then it tooks the XIP hv's and add them too
First XIP then OEM then SYS then EXT and EXT are arranged alphabetically so if you want a reg to be changed at the end of the cooking process you need to rename the EXT pkg with ZZZZ_blablabla
OK. Thank you. I will try and delete *.hvs then and see what happens...
delete them?
I didnt say you can delete them, even worst idea is to delete the OEM or and XIP ones...
I just said you dont need to touch them anymore
Haha..
@Diagrafeas
.hv files are rebuilded during cooking process they contain all registry.
It depends which kitchen you use but the packages have a file with a extension *.reg or *.rgu
You can open them with a tekst editor but if you edit them you need to save them in UTF8 and first
line must be 'REGEDIT4' (without the quotes) and a empty last line.
Make only small edits and test because registry files are very sensitive, if you forget one ' your whole kitchen won't work.
If you edited succesvol and it works as it should be I recommend to make a backup of your kitchen before you edit the next one, this way your always save.
+ Que PPC said:
delete them?
I didnt say you can delete them, even worst idea is to delete the OEM or and XIP ones...
I just said you dont need to touch them anymore
Click to expand...
Click to collapse
OK I will not delete then, but i have another question.
Inside OEMXipKernel there is a boot.hv and a boot.rgu.
The original ones had the same keys.
But now i have made some changes inside boot.rgu.
Which keys will be used boot.hv or boot.hv ones?
EVK recompiles the boot.hv from the boot.rgu, so if you tweak the boot.rgu, you're good to go. You don't need to rebuild the boot.hv yourself.
OK. Thank you all.
I've searched forums and I found tomcug WM6.1 for this pda. I wanted to make my own ROM, but cannot find any helpful tips regarding cooking for this device. The most important thing I wanted to add is new OS build and language. I've dumped it, but cannot sort with PKGTool for use with EVK and I got just Dump with all files, but I added and replaced mui, registry to get my language on this Dump folder without sorting out xip and sys. When I choose to build with tools included in latest tomcug release, no files are created. I should get WMUPDAT.DIP file, but Dump folder is deleted instead and none files are created. I tried on Win7 and WinXP and same problem persists.
WMUPDAT.DIP is 1kb file+OS.NB converted to BIN then dumped.
I also wanted to try HyperCore kitchen but I don't know how to configure ACK for JAQ3