Quote:
Originally Posted by eric12341
with opera its best to use a ROM with it cooked insomething always doesn't work right when installing it via cab. .
|
There is no difference between cooking it in and installing it in a cab. You probably should understand how to make a rom before making claims like that... I can cook a version of opera in my rom and have it not work with the zoombar if I choose to. I can also install a version via a cab that works just fine with the zoombar. You can change the splash screen to whatever you want either via cab or cooking.
The zoombar not working via cab install is because the cab was made incorrectly/not for your device. You only update the .exe's in the opera package from your device's shipped ROM if you want a new version and everything to work correctly.
A cab is nothing more than a compressed file containing files that get placed in certain directories on your phone and contains certain registry entries. It's the same as a package that gets cooked into a ROM - packages contain an rgu for registry entries, the files themselves, and an initflashfiles.txt to have those files be moved from \windows to whatever directory during the first boot of your phone. Coincidentally, cooking in Opera takes up more space on the Storage Memory (is that what you mean by device memory?) because everything is cooked into \windows (ROM) and copied to \Windows\Opera9\ (effectively doubling the amount of space it takes up in Storage Memory).