Which search.ini?
-
hopk1ns last edited by
Which search.ini should I edit, if I were to add entries manually? The one in "C:\Program Files\Opera x64\defaults" or "C:\Program Files\Opera x64\defaults\region[region code]"? I have tried changing both (with Opera closed, saving and then reopening Opera) to no avail.
An additional note: I was attempting to change the shortcut for Bing from "b" to "bing", which the user interface does not permit. I understand that some elements of the default searches are locked, but in that case I would have expected to see my edited search.ini file change back after I closed and reopened Opera again. This did not happen.
Many thanks.
-
hopk1ns last edited by
Thanks for the reply. I am indeed trying to add something else with a "b"! I don't use Bing at the moment but at some point I'll give it a go, hence trying to rename rather than remove it.
There is a search.ini at "C:\Users[username]\AppData\Roaming\Opera\Opera x64\search.ini" but it relates to my Opera 12.17 installation. No other files called "search.ini" seem to exist on my computer. Does the new Opera save user preferences inside some other file?
-
hopk1ns last edited by
Thanks for the reply, sorry for my delay. If there is no such file in my profile then, to return to my original question, any idea where are my preferences stored?
-
sgunhouse Moderator Volunteer last edited by
I am not aware of any way to modify the built-in defaults ...
There is a file in the directory for Opera resources (opera program directory, then current version, then resources ... on my system C:\Program Files (x86)\Opera\23.0.1522.77\resources ) named default_partner_content.json which contains this information, but I'm pretty sure that number at the start of the file is a checksum so that if someone (especially malware) were to modify the file it would be ignored, and of course if you did get past that you also lose your changes after every update. I could be wrong about the checksum - feel free to try and change it, but backup the original first - but as it is in the directory for the current version the update issue is unavoidable.