Database Users

n00b question about adding my own programs

Okay I understand you have to use mkrom and Linux (or cygwin on Windows) to roll your own ROM my question is regarding how one could say remove one program from the SE ROM and include something else, for instance take off the byte counter and put another different counter on or such, would you just copy the necessary files (.exe and dll's) to the files1 or files2 folder and that's it ? What more is involved? Thanks in advance!

for simple programs, that is all there is to it.
some might need more research, as to which registry settings need to be tweaked to get te program to run from the windows directory. and what settings it needs to run at all.

You copy the files to either files1 or files2. Both sets of files end up in the \Windows subdir. So if you do not want to copy the files to RAM (see below), you should make sure the program is set to run from \Windows. Then you add any necessary registry keys to "default.reg", and any file-copy or directory creation commands to initobj.txt. Then run "mkrom <ROMfile>" and hey-presto.

Thanks so much for all your guys awesome work!!

entropy1980 said:
ok sounds good, what would one need to do to mod the registry for the programs (By that I mean prior to booting) I don't want to be mucking around with a reg editor after the device boots just to get the progs to work...
Click to expand...
Click to collapse
Not sure I understand the question. Default.reg just holds the entire registry as present after a cold restart. So if you put something in there, this will be in the registry when the device wakes up.

I think we wrote at the same time , so you answered my question before I posted it !!! What you said made complete sense! Thanks!

entropy1980 said:
[...]so you answered my question before I posted it !!! [...]
Click to expand...
Click to collapse
I installed the phpBB telepathy mod a couple of days ago, so I guess it's working.

Hey I knew you were going to say that.... :lol: :lol:

hi,
i want to add the skelmir java virtual machine (thats default installed in windows\ceej) and copy the swingall.jar in the windows\ceej map.
I have the cab file of the virtual machine but i can't find out which files are in it (when i open it with cabextract is shows .001 files and not the files that i find back in the device)
please help me

Using Special Edition ROM, Tthe CabInst tool will run CAB files on the device if you move it there manually and double-tap it. It allows to set a new directory to install in.
Also the System Snapshot tool will write a file in the root of the device which holds a list of the entire filesystem and registry contents, so you can compare and see what changed. UltraEdit for the desktop has a compare function.
Good luck...

hi,
i installed it to a seperate directory and zipped the files. i also took a snapshot when the xda was fresh and after install. i only can't find where the xda's gets is files from in:
43 <! [\Windows\AppMgr]
8544 <! 31/12/2002 12:31 1632 FC0E9EE1 Skelmir CEEJ Virtual Machine.DAT
8576 <! 16/02/2003 23:10 27 AEBB1DF3 CEEJ.lnk
8587 <! 16/02/2003 23:10 40 1EAF4EB3 CEEJ Examples.lnk
8588 <! 16/02/2003 23:10 27 AEBB1DF3 CEEJ.lnk
because these are not in the map where i extracted the cab file too. maybe you can take a look for me and tell me what i have to change in mkrom to have ceej by default installed
the extraced cab map:
http://www.devosjansen.nl/xda/java installed.rar
the snapfiles:
http://www.devosjansen.nl/xda/xda snapshots files.rar
thanks in advance

laurens0619 said:
hi,
i installed it to a seperate directory and zipped the files. i also took a snapshot when the xda was fresh and after install. i only can't find where the xda's gets is files from in:
43 <! [\Windows\AppMgr]
Click to expand...
Click to collapse
These files are generated during the install process, and contain uninstall information. You do not need to write them if you install in ROM, since you don't need/want your programs to show up the in the 'Add/Remove Programs' dialogue.

ah i understand,
so i just put the files in the files1 or files2 directory and add this reg files to the default.reg? i dony really understand the readme file

ah little kick,
isn't also good for the next SE rom? because you have finally a java virtual machine on the xda and the app is freeware (got it from www.skelmir.com)

laurens0619 said:
isn't also good for the next SE rom?
Click to expand...
Click to collapse
Noted...

nice but can you please help me out for the moment? i dont know which part i must add to the default.reg file

laurens0619 said:
I dont know which part i must add to the default.reg file
Click to expand...
Click to collapse
default.reg holds the registry that is present when the system wakes up from cold-boot. So any registry entries your installer (or first run of the app) has made that you would like to have present should go in there. Clear enough?

almost
so i just copy paste the **** at the end of the reg file? and the files in the files 2 map
but how will the rom know where to put the files??
sorry if i'm stupid but i don't want to f*ck my rom so i can use me xda's as a frisbee

Yes, the registry entries can be pasted at the end of default.reg. It doesn't matter if there's earlier entries with the same values, since the latter ones override.
All files in files1 and files2 will end up in \Windows, and if you want them somewhere else, (where they'll take up RAM), you must manually copy them (or pre-made links pointing to them) by issueing commands in initobj.txt.
Take a real close look at initobj.txt, and you'll get the picture.

-------> Is POSSIBLE to put ADOBE and POWERPOINT in MEMORY CARD to increase space??

-------> Is POSSIBLE to put ADOBE and POWERPOINT in MEMORY CARD to increase space??
Is possible to cut Power Point (2,29 mb) and AdobePDFreader(1,91mb) from the main memory and put them into the memory card??
It would increse a lot main memory space...
Experts, let me know if it's possible....
And what about all the files called "HH_WEATHER...", I have an other program fot meteo forecasts, so I don't use the original one... Is it possible remove all these files?? (I think that they are all images, I only opened a few, and they were all forecast images...)
BYE BYE......

the things you mentioned is probably burned into rom - you won't be able to remove it.

ww2250 said:
the things you mentioned is probably burned into rom - you won't be able to remove it.
Click to expand...
Click to collapse
Yes, I know..
But I lose the warranty if I install a cooked rom....
If my device in future won't work correctly (or don't work at all) I wouldn't be able to put the original rom back??

Alternative Solution
You could compress the two executables with UPX and use Resco Explorer to overwrite them in the ROM. That won't save you as much space as moving them to external memory, but by compressing the files, you will save a decent amount of space.

tyr0ne said:
You could compress the two executables with UPX and use Resco Explorer to overwrite them in the ROM. That won't save you as much space as moving them to external memory, but by compressing the files, you will save a decent amount of space.
Click to expand...
Click to collapse
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!

flykthewiz said:
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
Click to expand...
Click to collapse
Are you sure about that??
Do you mean that, if I compress these files, when I replaced the originale ones with the newest, the pocket pc places them into the ram and not the rom??
How is possible it??
So I can do this operation or not?
I would be happy if only I had 2/3 mb more....

flykthewiz said:
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
Click to expand...
Click to collapse
Anyone know this inconveniet??

the only thing is with anything that you add to your ppc after initialization... it stores it to the ram, not the rom, you would have to actually cook a similar rom to your original rom to have the new stuff in there, and all you would have to do is get the official ruu for your device before you call back in, and you are good to go, thats what i do!

MrGalione973 said:
the only thing is with anything that you add to your ppc after initialization... it stores it to the ram, not the rom, you would have to actually cook a similar rom to your original rom to have the new stuff in there, and all you would have to do is get the official ruu for your device before you call back in, and you are good to go, thats what i do!
Click to expand...
Click to collapse
Ok, perfect...
I think that in the future I'll try a cooked rom, I know that it increase the space, a lot!
The only thing that worried me is the following:
If I have to repair the device, I must put the original rom back, but if I can't do it (ex my device doesn't start correctly)?
I had a Nokia N73 brand with my operator Tim, I have unbrand it (knowing to lose the warranty), but some months ago I must bring it to a Nokia Center, to repair.
And they don't see nothing about the difference between the original Imei and the actual one (that are different because you must do that to update yur firmware)....

flykthewiz said:
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
Click to expand...
Click to collapse
So u mean it's possible to replace a ROM file in the windows dir with another?
If so, HOW... i want to replace smartdialing.dll in my htc elf with another one that's patched containing another language(greek) but it doesn't seem to work.
Any help on this one?

larryg4 said:
So u mean it's possible to replace a ROM file in the windows dir with another?
If so, HOW... i want to replace smartdialing.dll in my htc elf with another one that's patched containing another language(greek) but it doesn't seem to work.
Any help on this one?
Click to expand...
Click to collapse
He talks about replace the file with resco explorer....
I think that you only have to copy the new file and paste it into the windows directory with resco....

Isnt it possible just to copy the program files to memory card and change the registry settings for those apps to point to new location?

jem777 said:
Isnt it possible just to copy the program files to memory card and change the registry settings for those apps to point to new location?
Click to expand...
Click to collapse
I would want know exactly this thing....
Anyone know??

jem777 said:
Isnt it possible just to copy the program files to memory card and change the registry settings for those apps to point to new location?
Click to expand...
Click to collapse
Some programs are hardcoded with paths in "\windows" directory - by moving stuffs around, things may break. Many programs that are expected to be in ROM fall in this class.
But then even if you are successful in "copying" it elsewhere, you won't be able to delete what's already in ROM. Overwriting it is just an masking action. ROM is ROM - follow me, Read Only Memory. Thus no memory is saved whatsoever.
Unless you flash it somehow.

ww2250 said:
Some programs are hardcoded with paths in "\windows" directory - by moving stuffs around, things may break. Many programs that are expected to be in ROM fall in this class.
But then even if you are successful in "copying" it elsewhere, you won't be able to delete what's already in ROM. Overwriting it is just an masking action. ROM is ROM - follow me, Read Only Memory. Thus no memory is saved whatsoever.
Unless you flash it somehow.
Click to expand...
Click to collapse
Ok, I understand the problem..
Tell me only the last thing....
If I copy the files to the memory card and then I create some shortcuts to these files, and replace them into the windows folder, do you think that they'll work or not??
When the pocket pc try to use them, It'll find the shortcut(and not the program itself) but this will direct the pocket pc to the program itself....
Would it work??

If I copy the files to the memory card and then I create some shortcuts to these files, and replace them into the windows folder, do you think that they'll work or not??

flaviopac said:
If I copy the files to the memory card and then I create some shortcuts to these files, and replace them into the windows folder, do you think that they'll work or not??
Click to expand...
Click to collapse
Noone know if it would run??

re-read my earller post. the answer is there already. if you find it difficult to understand, why don't you try it out yourself? it's incredibly simple.

Save 6 megs on the UK O2 Oribit ROM

For those who want to save a little space, you may notice that there are some useless pictures and HTML files built into the ROM that you can't delete with Resco or any other File Explorer. Well you can replace these useless files with ZERO byte files if you don't mind having zero byte files on your device.
Just Unzip and copy the stuff over to the Windows Folder on your device with Resco Explorer, this should be enough.
I've backed the original crap up and will upload these if anyone wants them back.

doubt it will work - those files are still in ROM - Try 2 do HardRST and they'll be back - only one way how 2 remove them fysically is to remove them directly from rom(so U have to cook one). Other think is if files are copyied during first boot(iniflashes.dat) then they can be removes-usually branding rubbish, tsk, lnk...

No it overwrites the ROM files.

again i doubt it - it doesnt owerwrites them. they only appears in Fexplorer || Resco as 0sized. Only one way how can i imagine to owerwrite them physically is using pdocwrite (maybe, not sure about it) did U try to HR UR device, and they appeared there with 0b size? Try it - files are still there. If editing ROM would be so easy, why anyone will spend time with building NBH.... Flashing....

delete a file in rom

is it possible to delete a file in rom memory? for exapmle a sound file

No. Not unless you are cooking your own ROM.
Even if you could somehow do it, it would not free up any memory you can use.

Wel you can't delete a file without cooking it. But you can overwrite it with a different file. So it should be possible to gain some memory. Look at http://forum.xda-developers.com/showthread.php?t=358803 for a dummy file to replace executables in the rom.
Good luck

rikkiepikkie said:
Wel you can't delete a file without cooking it. But you can overwrite it with a different file. So it should be possible to gain some memory. Look at http://forum.xda-developers.com/showthread.php?t=358803 for a dummy file to replace executables in the rom.
Good luck
Click to expand...
Click to collapse
even if you overwrite a rom file with a smaller file you will still not have access to the saved space. there is a certain amount of space reserved only fo the rom images and you can not access it. unless you cook your own rom.

tom108 said:
even if you overwrite a rom file with a smaller file you will still not have access to the saved space. there is a certain amount of space reserved only fo the rom images and you can not access it. unless you cook your own rom.
Click to expand...
Click to collapse
True, but you can prevent it from loading into the RAM memory by overwriting for example biotouch.exe ore some other program loading in to Ram memory

[Solved][Q] EXT packages + app.dat = duplicates of files in \windows\

I tried to keep the title as descriptive and short as possible, I hope it makes sense
I picked up the kitchen of nhathoa (a retired Topaz cook) hoping to get it customized to make it exactly the way I want but I'm running into some issues.
Long story short, I'm using Ervius Visual Kitchen (1.8.2) and I noticed that the EXT packages I added end up leaving two copies of the files, a copy under \windows\ and another one in the places I specified using app.dat using:
Code:
Directory("\Program Files\bla\"):-File("bla.exe","\Windows\bla.exe")
Is there some way to get rid of the copy under \Windows\ ??
I know that I could simply leave everything there and discard the app.dat files but I would really prefer having everything organized properly (I have a bit of an OCD when it comes to organizing everything neatly ).
I'm pretty sure that this is a rather simple and noobish issue but I couldn't find anything relevant by searching and I took a look at some ext packages by various cooks and noticed the same behaviour.

MusikMonk said:
I tried to keep the title as descriptive and short as possible, I hope it makes sense
I picked up the kitchen of nhathoa (a retired Topaz cook) hoping to get it customized to make it exactly the way I want but I'm running into some issues.
Long story short, I'm using Ervius Visual Kitchen (1.8.2) and I noticed that the EXT packages I added end up leaving two copies of the files, a copy under \windows\ and another one in the places I specified using app.dat using:
Code:
Directory("\Program Files\bla\"):-File("bla.exe","\Windows\bla.exe")
Is there some way to get rid of the copy under \Windows\ ??
I know that I could simply leave everything there and discard the app.dat files but I would really prefer having everything organized properly (I have a bit of an OCD when it comes to organizing everything neatly ).
I'm pretty sure that this is a rather simple and noobish issue but I couldn't find anything relevant by searching and I took a look at some ext packages by various cooks and noticed the same behaviour.
Click to expand...
Click to collapse
No, it's call Read-Only-Memory (ROM) and is the reason you can hard-reset your phone. Every file you cook into the ROM is in \windows. Two ways I know of to reduce the amount of files would be to zip them and have a mortscript unzip them to the proper location during customization or cook in a cab containing all of the files and have it run during customization.

That makes a lot of sense, I really feel ashamed that I didn't figure it out earlier
EXT packages seemed easier than bothering to read about customization but I guess it's time to start reading about this kind of stuff.
Thread marked as solved.
Thanks for the quick reply!

Yup, files in rom are in rom forever, or until you flash again, lol. The trick is to just run bla.exe from \windows. I would say that 90% of the time, bla.exe runs just fine out of the windows directory (especially if it's the only file in the package). When people create cabs, they naturally install the app in \program files, but in general apps don't need to be in a specific folder. If there are other files present, usually an .exe will search within its own folder for those files. So, if you just cook everything straight into windows, you'll be good to go. It's easy enough to test: just move all the files from program files to windows after installing a cab, fix the shortcut in the start menu, and then try to run the app. It's always a good idea to do a soft reset and try again (found this out the hard way many times). The one thing you have to watch out for is settings files, like .dat files. These files frequently have to be archived (not read-only). Particularly with apps that use net 3.5, if there's a setting file that is read-only, the app won't boot and you'll get an error message. The fix is to name the file settings-1.txt (or whatever) and have an app.dat rename it to settings.txt (and keep it in \windows).
Also, remember to fix the shortcut path in the start menu, and examine the registry entries to see if there are any paths for files present-you may need to change them to point to \windows (this could also be true in settings files).

mwalt2 said:
No, it's call Read-Only-Memory (ROM) and is the reason you can hard-reset your phone. Every file you cook into the ROM is in \windows. Two ways I know of to reduce the amount of files would be to zip them and have a mortscript unzip them to the proper location during customization or cook in a cab containing all of the files and have it run during customization.
Click to expand...
Click to collapse
This actually made me think a little bit. When you think about read only, I always thing can't delete or overwrite. Obviously I can run a cab and replace a file that is located in the \Windows directory, that leads me to believe there is a way to delete a file or maybe even replaced with an empty file of the same name.

You can over-write a rom file, but the rom file is still there. The file system just flags it somehow or another and tells the device to ignore it and instead use the new file.

TMartin03 said:
This actually made me think a little bit. When you think about read only, I always thing can't delete or overwrite. Obviously I can run a cab and replace a file that is located in the \Windows directory, that leads me to believe there is a way to delete a file or maybe even replaced with an empty file of the same name.
Click to expand...
Click to collapse
The new file you copy over goes into the "user" partition of the file system and windows knows to use that file instead. Once you delete this newly copied file from \windows, the old one from the ROM will take its place back in the filesystem.

Farmer Ted said:
Yup, files in rom are in rom forever, or until you flash again, lol. The trick is to just run bla.exe from \windows. I would say that 90% of the time, bla.exe runs just fine out of the windows directory (especially if it's the only file in the package). When people create cabs, they naturally install the app in \program files, but in general apps don't need to be in a specific folder. If there are other files present, usually an .exe will search within its own folder for those files. So, if you just cook everything straight into windows, you'll be good to go. It's easy enough to test: just move all the files from program files to windows after installing a cab, fix the shortcut in the start menu, and then try to run the app. It's always a good idea to do a soft reset and try again (found this out the hard way many times). The one thing you have to watch out for is settings files, like .dat files. These files frequently have to be archived (not read-only). Particularly with apps that use net 3.5, if there's a setting file that is read-only, the app won't boot and you'll get an error message. The fix is to name the file settings-1.txt (or whatever) and have an app.dat rename it to settings.txt (and keep it in \windows).
Also, remember to fix the shortcut path in the start menu, and examine the registry entries to see if there are any paths for files present-you may need to change them to point to \windows (this could also be true in settings files).
Click to expand...
Click to collapse
First of all, a small question about the underlined part, just to make sure that I got it right: it won't be exactly a rename just a copy with a different name, correct?
Some of the apps I use need a specific directory structure for the resources and files they use, so just dumping them in one big folder won't work.
Another possible issue that I think I'll run into is having two files sharing a generic name (let's say settings.xml) while each belongs to a different app. I didn't personally encounter such a situation just yet but my packages are still a work in progress and I did see a post or two about this while searching.
I was still hoping there would be a simple way to arrange the files in folders while keeping them under \windows\ but I can't find such a method either. Doesn't seem like I have other options than to decided on a firstboot customization method: Runcc, autorun, xda_uc or something that I haven't read about yet...
"Runcc" is currently used in the base kitchen so that gives it an edge right now.
Edit:
Remembered that I had another question, and it's probably not worth a new thread.
I was looking at how to manually create .lnk files and I noticed something that I didn't understand and couldn't find info about.
For example:
Code:
21#"\Windows\MSDict.htm"
What exactly does the "21" refer to?? I tried changing it randomly to other values a couple of times and it didn't effect anything.

NRGZ28 said:
The new file you copy over goes into the "user" partition of the file system and windows knows to use that file instead. Once you delete this newly copied file from \windows, the old one from the ROM will take its place back in the filesystem.
Click to expand...
Click to collapse
Ok now that makes a lot of sense. I guess I'm just use to Android and being able to see that separate partition. Thanks for the explanation.
That sort of leaves me to another question. Can't someone develop a way to overwrite directly to the "system" partition? It would almost be like a root/superuser for WinMo.
Sent from my HTC Evo 4G!

MusikMonk said:
First of all, a small question about the underlined part, just to make sure that I got it right: it won't be exactly a rename just a copy with a different name, correct?
Click to expand...
Click to collapse
Yup, that's correct. Another approach is to take all similar files that go into windows and stick them in a zip file that unzips to the windows directory. I do that in a few cases (power radio comes to mind; it has an ini file). What I do in most cases though is use a backup/restore mortscript. The backup copies all settings files (and similar things) on my device to my sd card. During customization, the restore copies them back. It's convenient for apps where I change the settings a lot and I don't want to have to constantly fuss with the packages.
Some of the apps I use need a specific directory structure for the resources and files they use, so just dumping them in one big folder won't work.
Click to expand...
Click to collapse
What you do in that case is move the sub-folders into windows. In this case, I'll use a zip file to unzip those folders into windows. Using app.dat files to copy large numbers of files blows. It increases the rom file count as well as the storage used. A zip file is a single file, and usually it saves space.
Another possible issue that I think I'll run into is having two files sharing a generic name (let's say settings.xml) while each belongs to a different app. I didn't personally encounter such a situation just yet but my packages are still a work in progress and I did see a post or two about this while searching.
Click to expand...
Click to collapse
In that case, you're screwed unless there's a registry key that lets you change the name. I've run into a few complications; tcpmp and OMarket both use a common.dll. My solution was to buy Core Player, lol.
I was still hoping there would be a simple way to arrange the files in folders while keeping them under \windows\ but I can't find such a method either. Doesn't seem like I have other options than to decided on a firstboot customization method: Runcc, autorun, xda_uc or something that I haven't read about yet...
"Runcc" is currently used in the base kitchen so that gives it an edge right now.
Click to expand...
Click to collapse
Using cabs or zip files is the way to go if you want to copy large folders in one shot (with a mortscript; you can also un-rar rar files, but I don't know how. Yet, lol). Zips are easier to make and edit than cabs, but you need to have mortscript cooked in and know how to write the simple script (aka cut-and-paste).
Edit:
Remembered that I had another question, and it's probably not worth a new thread.
I was looking at how to manually create .lnk files and I noticed something that I didn't understand and couldn't find info about.
For example:
Code:
21#"\Windows\MSDict.htm"
What exactly does the "21" refer to?? I tried changing it randomly to other values a couple of times and it didn't effect anything.
Click to expand...
Click to collapse
The 21 is the number of bytes after the #. It doesn't matter. I usually just change the first number to 1. It works fine. Counting bytes blows.

That was extremely helpful. Too bad these boards don't use a rep system
Farmer Ted said:
Yup, that's correct. Another approach is to take all similar files that go into windows and stick them in a zip file that unzips to the windows directory.
Click to expand...
Click to collapse
Well, if I'm going to follow this method, and it seems like I am, I don't see why I would still have to limit myself to the \windows folder. I can just put everything the way I originally wanted to do. I only looked at arranging files under \windows when I found out that there's no way to get rid of the duplicates.
Farmer Ted said:
Using cabs or zip files is the way to go if you want to copy large folders in one shot (with a mortscript; you can also un-rar rar files, but I don't know how. Yet, lol). Zips are easier to make and edit than cabs, but you need to have mortscript cooked in and know how to write the simple script (aka cut-and-paste).
Click to expand...
Click to collapse
I haven't tried writing mortscripts yet but I've seen enough to figure out the basic and notice how easy it is. I'm gonna check how usable is the WM version of 7zip, as long as it accepts arguments combining it with mortscript will be easy and perfect for me.
7z archives can get smaller in size than half of the zip archives for the same files. And cabs are too annoying to work with and keep updated later on.
Only issue remaining now is checking whether I should put the archived files under \windows or use the sdcard for customization. I'm leaning toward the first but I'll have to wait and see how much memory I would be sacrificing that way.
Farmer Ted said:
The 21 is the number of bytes after the #. It doesn't matter. I usually just change the first number to 1. It works fine. Counting bytes blows.
Click to expand...
Click to collapse
Ah! I thought about counting bytes/characters and noticed that it works sometimes. But I thought it was a coincidence after I experimented in changing the value and noticed that it wasn't always the right count in the .lnk files that I found.
[rant]
Nice, I was messing around with some packages to free up ram and storage and I seem to have ended up with a rather b0rked up xTask. And then there's still convincing Resco Explorer that the registry add-in IS in fact there.
Figuring out the causes should keep me happily busy for a while (and probably heavily pissed for another while afterwards).
[/rant]
Edit:
Just for the record, I ended up using xda_uc it's a lot easier than doing things manually. Although it would help if there was some kind of documentation available, took me a while to understand what .xda, xdai, xdas & .xdaz files are supposed to be.

hi by the way is it possible to convert ext packages of QVGA phones to one another?