old cooked Opera Mini
 

The current PPC_kitchen_OEM.rar has a slightly older Opera Mini 4. It doesn't have the auto-complete URL feature which I like (in v4.1).

I know I can install the new version, but here's my question. Isn't the "cooked" version in the ROM read-only (can't write)?

If so, can I even upgrade it or do I have to have have 2 versions side-by-side? One in ROM and one in Main Memory - thus taking up my precious Main Memory.

I'm sure I can read the tutorials on "baking" my own ROM, and add the lastest Opera Mini, but I'd still like to know if the "baked" Opera Mini files can be overwritten if I download the latest version.

I think the ROM is read-only, but I could be wrong.

Re: old cooked Opera Mini
 

This fooled me once too when I upgraded Mobile Live Search. It was originally cooked to ROM and you will notice that it will not be in your removable program list. Then when you upgrade it will show up as a removable program. So, you are right, you will have two installations, the ROM (unchangeable, read-only) and the upgrade in storage memory (the one the PPC will work off of).

Re: old cooked Opera Mini
 

Looks like I need to bake my own ROM with the latest Opera then.
I already found where the Opera is located in BuildOS - namely the APP_OperaMini folder in PPC_Kitchen_OEM.rar
I see the java files s0_suite.jar,s0_d2.db, s0_d4.db, s0_d5.db, selector.utf, etc. which get copied to \windows\appdb\
I can copy over my versions I guess from my other WM6.1 phone running Opera 4.1.
but I also see these two files that I'm not sure what they are/do:
ffffffff-2f4d-475f-976e-690884992550.dsm
ffffffff-2f4d-475f-976e-690884992550.rgu

Looking at initflashfiles.txt it doesn't even copy these 2 files. This file has this:
Directory("\Windows\Appdb"):-File("selector.utf","\Windows\selector.utf")
Directory("\Windows\Appdb"):-File("s0_suite.jar","\Windows\s0_suite.jar")
Directory("\Windows\Appdb"):-File("s0__d5.db","\Windows\s0__d5.db")
Directory("\Windows\Appdb"):-File("s0__d6.db","\Windows\s0__d6.db")
Directory("\Windows\Appdb"):-File("s0__d7.db","\Windows\s0__d7.db")
Directory("\Windows\Appdb"):-File("s0__d4.db","\Windows\s0__d4.db")
Directory("\Windows\Appdb"):-File("s0__d2.db","\Windows\s0__d2.db")
Directory("\Windows\start Menu\Programs"):-File("Opera Mini.lnk","\Windows\Opera Mini.lnk")
Directory("\Windows\Appdb"):-File("s0_.obj","\Windows\s0_.obj")
Directory("\Windows\Appdb"):-File("s0_suite.utf","\Windows\s0_suite.utf")

As seen about the .dsm and .rgu aren't copied.

Maybe they're not needed?

How do I got about creating this s0_ files and other files?

One method I could do is to install Opera Mini 4.1 on another WM6.1 device and then copy these files into PPC_Kitchen_OEM.rar (specifically the APP_OperaMini folder)

Re: old cooked Opera Mini
 

Are you really that strapped for storage space? I suppose you could try installing to miniSD and running from there. Some programs don't work well from the card, though. Don't know about Opera. I suppose you could OEM it and use OEMizer:
http://wiki.xda-developers.com/index.php?pagename=OEM%20Package%20Tutorial
Edit: Look here, too..
http://forum.xda-developers.com/showthread.php?t=398567