Related
I have been attempting to add Interenet Calling to Faria's WM6 ROM by adding the necessary files and registry changes and re-cooking the ROM but I am getting nowhere fast. I have managed to add some files to the original ROM, make a couple of registry changes fine and change some settings in the initflashfiles.dat file to remove some shortcuts I don't want and I can get this to work fine, however re-adding the IP Phone stuff is a bit more of a task.......
I have extracted the files (or modules) from the MB ROM and added the regsistry changes and the ROM cooks just fine. When I flash the Wizard though it completes sucessfully and then reboots. I get the 1st splash screen but then when the 2nd splashscreen should appear I get a white screen. The Wizard is working as I can hear the bleep when it asks you to 'tap the screen to set up the device'. It also powers on and off OK, but I only ever get this white screen.
I have tried this about 4 times now and I am convinced the registry changes and required files are correct, but each time I get this white screen. Any ideas?
Andy
http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.
trojan9x said:
http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.
Click to expand...
Click to collapse
Already read it..... I can get Internet Calling back if I launch the VoIP.CAB that is included in that thread after installation, however I want these to be integrated into the ROM like they were originally (Faria has removed them). As I said I have had some sucess with adding other files and other registry changes it is just this bit that I am stuck on.
I did manage to get a bit further but ended up with a corrupt Today screen, no idea what happened there though
Andy
What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?
Faria has said that his rom takes up almost the entire space alotted. Have you tried removing some files from the rom to clear up room for the VoIP files?
trojan9x said:
What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?
Click to expand...
Click to collapse
I want to restore the Internet Calling option in Faria's WM6 ROM - pretty simple to understand really
I can add it manually via the VoIP.cab file but this obviously takes up RAM and can be removed via 'Remove Programs'. I would like to add the files that are missing and make the necessary registry changes then re-cook the ROM. I would prefer to keep Faria's base ROM.
I haven't tried removing anything from Faria's ROM so far, I didn't realise it was near the limit - I thought we had 128MB to play with on the Wizard, are we near that already?
Andy
Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept
trojan9x said:
Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept
Click to expand...
Click to collapse
Yep, already done that, hence my original post.....
I have added the necessary registry changes/additions and proof-read them several times, however once the ROM is cooked and installed the thing reboots, I get the 1st splash screen OK, then the white screen when the 2nd splash screen should appear and that's it.
I will have a look at how bloated the DUMP directory is with the additional files in there and see if I am going over 128MB.
Andy
The DUMP folder is apparently 122MB (128,512,401 Bytes) but is taking up 132MB (139,141,120) on the disk on my PC. Does anyone know if this is too big? If it is what is safe to remove?
Thanks
Andy
Done it.......
If anyone is interested I managed to get Internet Calling back into Faria's ROM.....
What I did originally was correct, however the file (or modules) that are needed for Internet Calling total about 3.5MB, which I think was slightly too much and would make the ROM bigger than 128MB (I think Faria must have realised this when developing his ROM and removed them to save space). I have been through the installed applications and files and have removed some stuff that I don't use. I then re-built the ROM and low and behold it worked first time and Internet Calling is now an option...
It still doesn't work however but that is just because it needs a provisioning XML file from a provider. Hopefully when WM6 devices appear we will be able to extract a provisioning XML file and dig deeper........
And no, the ROM is not available since this is Faria's work and not mine.
Andy
Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
joad said:
Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad
Click to expand...
Click to collapse
I have exactly the same intentions, joad. I've got wm6 on my O2 XDA mini so I can try and connect to my Asterisk server as well!
Let's hope his eventually works.
N
joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
You need to add the following files into the ROM (the 1st 3 are actually modules and are in directories with the same name):
dnsapi.dll
rtcdll.dll
voipphonecanvas.dll
ipdialplan.xml
ringback.wma
You also need to add the registry entries to the default.hv and user.hv that are contained in the '_setup.xml' file from the VoIP.CAB file (or extract them from another ROM that already contains Internet Calling).
HTH
Andy
joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
Joad,
I agree with you. The 3.5 Mb footprint is inflated.
It's only 1.75 MB (remember if you are using recmod when you are unpacking the ROM with viewimgfs, you have two copies of the files that are stored as modules: the module version and a file copy!.
--eluth.
eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003
Pleaaaaaaaaaaaaase !!!!!!
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
gio2003 said:
eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003
Click to expand...
Click to collapse
ckolibab said:
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
Click to expand...
Click to collapse
This .CAB worked on my Wizard with Faria's WM6 real thing ROM that had the VoIP stuff removed:
http://forum.xda-developers.com/showpost.php?p=1147821&postcount=138
I then added the files and registry settings back and re-cooked the ROM.
HTH
Andy
Is there instructions on creating a post-flash (or hard reset) install script? I'd like to have it run the cingular WAP cab, and maybe a couple others. I think I've been all over, but haven't seen anything...
Thanks!
Also - does anyone have a package or cab for camera 3.3???
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
JoelC said:
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
Click to expand...
Click to collapse
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
mattk_r said:
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
Click to expand...
Click to collapse
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
notyourdaddy said:
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Click to expand...
Click to collapse
I just found this link that has an extended rom in it. It makes a lot of sense, especially the txt file that directs the installation and then initiates a reset. Getting warmer!
http://forum.xda-developers.com/showthread.php?t=309922
So here's what I'm thinking - just initial thoughts:
Have a folder with the base applications that are used every time like AutoRun.exe.
The user places the cab(s) in the "add files to ext rom" folder.
They run an exe that reads the directory file contents, verifies file type, copies the files to the extended rom folder, and displays the list. I'd write it in VB, since I'm most comfortable with file system operations in that language...
They change the list based on the order they want them installed using up and down arrows to sort priority.
The click OK, and it creates the config.txt file, including all necessary commands such as reset and whatnot.
That way when they build, it's all good to go.
Any thoughts?
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
JoelC said:
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
Click to expand...
Click to collapse
That's really good info, because I'm climbing the learning curve as fast as I can here to get a good grasp on what the extended rom is, as well as how to use it. I appreciate the conditional warnings... better to know ahead of time than find out following a problem.
I'd rather use the true extended rom (as I understand it anyway), so I don't loose any additional space for the BuildOS programs. That is, assuming the extended rom is a seperate memory location than the base...
In another thread, someone is going to post that tool. I'm really interested in how it works.
If I can get all the concepts together, I hope to get a solid tool that will improve functionality in the ROM, without adding complexity or trouble... and I greatly appreciate the help!
Interesting thread...guys, you just gave me some new ideas.
Before that...there's one thing that's bothering me...
Can we use ExtendedRom on a G4 or not...lol I thought not, until me an Boto made a clean one from a G4 ExtRom and when Boto flashed it it worked , and he has a G4. Why we always say that we don't use an Extended Rom for G4 users ?
Normaly, a G4 should/would brick when flashing IPL/SPL not Extended Rom, am I right ?
We are shrinking the OS space to integrate features of the ExtendedRom in order to all people use it but is it that true ?
Ok, now back to my idea .. I want that in my next rom to include an extended rom, of course and make it that way so when you first start your PDA, it will act like when installing windows on the PC , asking you which apps or what options you want to use. I think i can manage to do that...still the question remains ...will G4 users be able to use it ?
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
JoelC said:
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
Click to expand...
Click to collapse
I took the Ext Rom from the Wizard Love Rom and i edited the config.txt and deleted cabs ...that's it
Well, if it flashed OK... sounds like it might be usable after all But tell me, is Boto's G4 CID locked or unlocked? It's all very uncertain, but some of the G4 posts lead me to believe this may make a difference
ADB100 said:
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Click to expand...
Click to collapse
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
wizzzard said:
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
Click to expand...
Click to collapse
Thanks for that but it isn't what I was really after.... I am just trying to automate everything. I have flashed my ROM that many times recently and going through the install of TomTom each time is a bit of a pain. I have got a couple of .CABs in the Extended ROM OK and these work fine, I just thought it would be nice if I could get TomTom in there as well.
Andy
I didn't want this to turn into a "how-to" thread, but I'm still scratching for hard info on the extended rom, and as many questions out there, it might be a good one to clarify some details...
As I understand it now, there's two forms of "extended ROM":
1. The true extended rom "similar to the radio ROM"
There is some "trigger" that runs the contents of the extended rom, such as AutoRun.exe?
2. The 'psuedo' extended rom that is basically a post install script to run cabs.
The contents of the folder under windows are run from a trigger that resides in the startup folder - similar to a runonce in Windows on first boot?
Does this sound close?
Also, where does the 'true' extended rom reside? Does it use the portion of memory reserved for the OS, or is there another portion just for it? (so if by adding applications to the extended rom, your available storage memory will remain unchanged - less the installed application?)
I'm presuming then by the 'psuedo' extended rom, that it does consume ROM space, but simplifies post-flash cab installations - assuming you follow the rules...
From what I see, by using the 'psuedo' ER, you waste space by keeping the installation files in addition to the installed application files.
If I'm wasting space and time by asking these questions and you know of a good extended rom tutorial, please direct me to it. I have spend some time tonight searching, but a definitive guide still eludes me... Thanks!
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
mfrazzz said:
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
Click to expand...
Click to collapse
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
mattk_r said:
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
Click to expand...
Click to collapse
Yeah, never figured out why that one was never made a sticky. I just know to go look at Faria's sig and it (and a few other good links) are in there
I've been struggling for the past few days to convert my (working) Voice Command UK cab into an OEM. I've taken the OEM for the US Voice Command from Alex's ROM Kitchenfor reference, but I'm having problems. I've tried:
- Replacing the files inside the US OEM with those from the UK cab, and changing the file names in the reg file,
- Making an OEM from the files and registry entries in the cab
- Making an OEM from the files in the cab, and the registry entries that show as changed in a reg dump before and after installation
So far, the best I can manage is for Voice Command to be assignable to a button, but then she doesn't speak! It understands some commands (for example, pressing and saying "Open Windows Media Player" will open WMP, but without her being able to talk the applications 90% useless).
I'm sorry to be asking to take up the time of our experts, but I'm at a serious brick wall and don't know which way to go now. Could anyone suggest where I'm going wrong? I can't seem to attache the working US OEM, the working UK cab, and the non-working UK OEM (keeps saying Upload Failed), so I've stuck them on MegaUpload: http://www.megaupload.com/?d=210FSFHW
Thanks for reading, and for any help everyone.
No entries in initflashfiles.dat (for startup, or files to a specific dir)?
Just a taught
I will have a look at your files later.
Laurentius26 said:
No entries in initflashfiles.dat (for startup, or files to a specific dir)?
Just a taught
I will have a look at your files later.
Click to expand...
Click to collapse
Thanks for the reply Laurentius.
The initflashes file has the same two entries as the original US OEM version, a link going to the helpfile, and a link to Voicecmd.exe going into the Startup folder. I'm not saying that's NOT where my problem lies (haven't got a clue where it is!) but I've even checked the links through Notepad and they're pointing to the right files.
Should probably say, don't try installing any Voice Command on your ROM, as the VC program doesn't play well with the Vodafone 3.08 ROM. It works fine on the 3.02 ROM, so I'm using a custom version of Slueth's 6.1 ROM at the moment. It works fine with the cab installed, so I don't think the ROM is the reason my OEM's not working.
Thanks again for the reply, any and all help is very greatly appreciated for my little problem.
What I usualy do is....
Install the cab and check the directory's and shortcut directory's!
In your case you have the US cab already, so next one is easy!
I use Registry Workshop to Explore and dump registry entry's on the device!
So if you compare the values with the US one's it should be easy!
I just released my V4 ROM, but I promise I will look into it later
Regards,
Leo
Confused Stu said:
Thanks for the reply Laurentius.
The initflashes file has the same two entries as the original US OEM version, a link going to the helpfile, and a link to Voicecmd.exe going into the Startup folder. I'm not saying that's NOT where my problem lies (haven't got a clue where it is!) but I've even checked the links through Notepad and they're pointing to the right files.
Should probably say, don't try installing any Voice Command on your ROM, as the VC program doesn't play well with the Vodafone 3.08 ROM. It works fine on the 3.02 ROM, so I'm using a custom version of Slueth's 6.1 ROM at the moment. It works fine with the cab installed, so I don't think the ROM is the reason my OEM's not working.
Thanks again for the reply, any and all help is very greatly appreciated for my little problem.
Click to expand...
Click to collapse
I have a working OEM package for UK VC 1.60.4622.0. There is one annoyance however and that is if you open the Voice Command settings and then hit OK you get two error bleeps and a window titled 'Voice Command' with a red cross and the text 'Cannot save all changes'. Voice Command does work though, however I have only had my Kaiser a few days and I haven't done any extensive testing - I probably need to go for a drive with my Bluetooth Headset and call a few people....
I created this package previously for my HTC Wizard and with WM6 running on that I don't get the same error.
To get this working on the Kaiser all I have done is changed the Key mapping in the .RGU registry file so the top left button (6) activates VC.
If I install the VC UK Cab the error I described does go away.
Andy
Just a quick update. I rebuilt my ROM with VC 1.60.4622.0 US (this is the original OEM package I found that I based my UK OEM one on, I can't quite remember where I got this?) and you get the same results with the two error bleeps and the 'Cannot save all changes' dialogue box.
Andy
i'm just quickly looking at it. Theres some missing files like comt3s51.dll, conveng.dbr and some random dlls here and there. Not sure what they do, but missing couple files here and there could be it. i have to get going, but decide to help with that.
Hi,
I am using in my ROM the normal process to start the customization after burning the ROM.
File \OEM\OperatorPKG\mxipupdate_zzPIED_101.provxml:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Comm" >
<parm name="AutoRunCFG" value="\windows\config_operator.txt" datatype="string" />
<parm name="AutoRun" value="\windows\AutoRun.exe" datatype="string" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
In my config_operator.txt I am installing some CABs - which works fine.
My idea was to delete all CABs after installation automatically. For that reason I have changed a *.rgu under \SYS\Shell:
from
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /delete 1"
to
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /nodelete"
In normal cases @="wceload.exe \"%1\" /delete 1" makes sure the a CAB will be deleted after installation.
If I install a CAB after customization the CAB is gone - so far so good - means the entry in the registry is fine.
Unfortunately, during the customization (which works fine) the CABs are still under \windows. It seems that the above change does not work with customization.
Question:
Does the autorun process (during the customization) after burning a ROM also using the wceload.exe to install a CAB ?
Regards
kuzco1
I was going to ask a very similar question, but I think I'll just bump yours instead
'Burn' the ROM
Yes, really like it rather than 'flash'.
If u want the cab deleted after autorun, just remove the read-only attributes & vice-versa. (if cabs in SD)
/nodelete switch wont work as it still delete the cab if the cab is not with read-only attr.
i think autorun doesnt use wceload but let the experts confirm it first. Just my guess.
So you want to delete a file from the ROM during customization (wont work) or off the MicroSD (would work), however I don't think I would include something from the SD in the customization XML I would use an auto installer first.
Thanks
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
bengalih said:
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
Click to expand...
Click to collapse
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
mbarvian said:
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
Click to expand...
Click to collapse
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
bengalih said:
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
Click to expand...
Click to collapse
wow, another good post
that is basically what I am trying to accomplish. I have my registry tweaks, files that don't get updated (Office, etc.) cooked in, but for some reason I cannot change the look of the dialer (I wanted to use poorlyduck's diamond dialer) by converting it to an OEM package with Ervius' Package Creator. Same with the comm manager skin. Therfore, I have resorted to installing these two through their default cabinet files during initial customization.
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
mbarvian said:
wow, another good post
....
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
Click to expand...
Click to collapse
Well dutty is by far a better cook than I... I'll stick to the scripting. I understand the basics of cooking...I just don't have the temperment for it.
However, I don't fully agree with all those points. I think his conclusions are correct, but I don't think the reasoning behind them are.
First off with space. Windows machines (be they PCs or WM devices) are basically made up of two things. File system and Registry (the registry just being a special file on the system). If I remove 2MB worth of an app from a ROM before I cook it, and then create a .CAB that contains those 2MB of files, the same amount of space is going to be taken up.
I have ripped quite a few apps to compile CABS from ROMs, and I know this to be the case.
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other point regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
bengalih said:
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other poing regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
Click to expand...
Click to collapse
can't argue with this post
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
hi,
yes you are right .. I have done the other wy. My fault in my first post. I have changed /nodelete to /delete.
But anyway, I understood that it is not possible to delete cabs during customization.
Many thanks to all
kuzco1
alright..i upgraded to opentouch 6 some time ago and realized that it was really awkward to use when i tried to use my paint program...it would scroll about the screen annoyingly. then i realized that there was a simple kinetic function that was added when i upgraded my rom. although a nice feature, is there a way to disable it? its so hard to draw when my work runs away from me after every flick of my stylus. XD
any help would be greatly appreciated. thank you very much!
1. This is the development sub forum. This is not a development question. This needs to be moved to the Herald section.
2. No. There isn't a way, per say, short of extracting the touch.dll from the default ROM, turning the module into a file and inserting it into the ROM.
3. OpenTouch 6 is an old ROM, but even with it, the scroll shouldn't be causing the problems you're describing as long as you draw with your finger tip, not with a wide area of your finger.
i dunno how to move stuff...just sayin..
well do you have any idea where i can find the original touch.dll from the factory settings for my htc wing?
avel7the7hated said:
i dunno how to move stuff...just sayin..
well do you have any idea where i can find the original touch.dll from the factory settings for my htc wing?
Click to expand...
Click to collapse
You'll have to download the default RUU, then open the exe with a zipping program (like 7zip), then extract the NB out of the NBH. Then extract the files from the os.nb. Then convert the touch.dll from a module to a file. It's a relatively simple process, it just takes a while to do and requires some work.
Although, now that I think about it, if he makes his ROMs anything like I do, go to:
[HKEY_LOCAL_MACHINE\Software\OEM\TFLOSettings]
with a registry editor and change:
"EnableScroll"
from 1 to 0.
If you're not sure what a registry editor is, please read up on it. You don't want to mess with the registry unless you understand it. Search around and you'll see quite a bit of information for it.
I suggest using PHM Regedit or CeRegEditor.
it worked...thanks alot!