Windows command line parameter /Settings broken?

Windows command line parameter /Settings broken?

Can anyone else confirm that the /Settings command line switch under Windows does not work in Opera 10 builds (not just the latest one)?

Steps to do the test:

1. Create a new temporary folder, for example C:\OperaTemp
2. In that folder create a new text file named "operaprefs.ini"
3. Put this text in the file (replace the paths with the folder you made):

[User prefs]
Opera Directory=C:\OperaTemp
Oprea Local Directory=C:\OperaTemp

4. Create a new shortcut for Opera and add /Settings C:\OperaTemp\operaprefs.ini to the command line.
5. Start Opera from the shortcut.

Expected behavior is that Opera starts with a clean profile located in that temporary folder.

What happens in my case: Opera uses the existing user profile from Application Data.

If others can reproduce the issue that Opera 10 opens their regular user profile even if started with different profile using /Settings parameter, I'll file it as a bug. I just want to make sure it's not something specific to my computer before filing it.

Why are you using operaprefs.ini ?
You need to use: /settings "...\opera6.ini"

Opera6.ini was renamed to operaprefs.ini almost two months ago. In any case, the file name has no relevance, both should do the exactly same thing as you are giving the file name as parameter, not just location.

Sorry about that. I completely forgot that change when they announced it because I'm still with build 1285.

Originally posted by godjonez:

Can anyone else confirm that the /Settings command line switch under Windows does not work in Opera 10 builds (not just the latest one)?

It works w/o any problems with build 1285, so before they changed that.
I have two profiles, one en-EN and one pt-PT and since I haven't upgraded yet from 1285, I'm only installing new snapshots for test runs.
But I've just tested build 1535 and yes, it seems to be broken, even changing paths in opera:config doesn't solve it.

reported:

bug [DSK-254011]

Thanks for confirming and reporting it.

Up.

Seems still broken in Opera 10 b1601. Multi-User profiles are disabled and all necessary lines have been added in a operaprefs.ini of the target directory.

Opera still want use the profile folder of the executable folder.

Broekn too in Opera 10 b1606.

Mostly fixed in Opera 10 b1615.

Mostly, since Opera still wants to store the vps, icons and thumbnails folders in profile folder of the executable folder. (It also creates a bookmark and speeddial file in that folder, but those are never used).

I've added these lines to operaprefs.ini

Opera Directory=D:\Settings\Opera100\profile
Opera Local Directory=D:\Settings\Opera100\profile
Cache Directory4=D:\Settings\Opera100\profile\cache
Operator Cache Directory4=D:\Settings\Opera100\profile\opcache

Is there any lines I can add so that the vps, icons and thumbnails folders are created in the D:\Settings\Opera100\profile\ folder?

I don't know if there are some lines for the VPS/Icons problem :/

So yes, it is MOSTLY fixed.

But the VPS/Icons/Bookmarks.adr/Speeddial.ini problems still exists in Opera b1631.

Still broken in 1703

Works for me in 1703.

I made a shortcut "C:\Archivos de programa\Opera 10 Beta\opera.exe" /settings "C:\Archivos de programa\Opera 10 Beta\profile\operaprefs.ini"

That was fine in 9.x (replacing operaprefs.ini with opera6.ini) but I can´t make it work in Opera 10. I download opera unite version. Is the same?

Definitely not working in 1703

Now updated to 1724 and it's no longer working for me either.

Indeed, it's still broken. The current bug is DSK-262068, just for reference (unless there are duplicates).

Yep, broken. So I've worked around it by created a sym-link, using Junction from http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx.

This way I can point Opera at any location I want without it having a clue. If you want to switch profiles, just delete one symlink and create a new one in a batch/cmd file first.

Of course I'd prefer Opera have the feature.

Is anything happening with this issue? I hate having my Opera files on C: drive.

Still broken in the latest nightly? Damn. :/

I didn't try the latest nightly. I was just hoping some of the more knowledgeable around here can tell me more about this. *hint hint* Tamil ::- D.

Still broken in the 10.10 beta. And in the following development release (1750) too...

I hope you mean 1840, 1750 was some time ago ...

Originally posted by sgunhouse:

I hope you mean 1840, 1750 was some time ago ...

You're right I had the wrong window open when I checked the build number. Thanks for pointing it out.

Sadly, it's still broken in 1857.

With it still being broken in 10.10 build 1893 and in all pre-alphas and alphas of 10.50 that I've tested, I'm starting to wonder if this will ever get fixed. Maybe it's a feature and not a bug? Obviously I have no idea about what the opera code looks like, but surely, the remaining bit shouldn't be that hard to fix? Either make these folders adhere to the locations specified in the operaprefs.ini or let the user override them?

Is there actually anyone with that knowledge reading this thread?

Still broken in the Opera 10.5 beta (build 3248).

STILL BROKEN !

Originally posted by paulchanseaud:

STILL BROKEN !

Negative. Been working fine in all 10.50 snapshots so far for me.

Originally posted by godjonez:

Originally posted by paulchanseaud:

STILL BROKEN !

Negative. Been working fine in all 10.50 snapshots so far for me.

I've just tried builds 3261 and 3263, and /settings is still broken. The vps, thumbnails, and icons folders still don't end up in the folder I've specified through /settings, and I haven't been able to find a setting for operaprefs.ini that would allow me to decide where they end up.

But it works for you?

EDITED:

Yes, seems like Opera does not care about the Opera Local Directory setting. But that's irrelevant to /settings command line parameter being broken.

EDITED 2: Opera does follow the Opera Local Directory setting also, the cache folder defaults just do not use that setting. You need to specify their locations separately.

Not workign for me

Originally posted by godjonez:

EDITED:

Yes, seems like Opera does not care about the Opera Local Directory setting. But that's irrelevant to /settings command line parameter being broken.

EDITED 2: Opera does follow the Opera Local Directory setting also, the cache folder defaults just do not use that setting. You need to specify their locations separately.

You're correct.

in 9.64 (build 10487):

The thumbnails folder adheres to the Opera Directory setting.
The images and vps folders adheres to the Opera Local Directory setting, if it's not set then they adhere to Opera Directory if set.
The Cache4 and opache folders adhere to the same rules as images and vps.
Images, vps, thumbnails (or cache4 and opcache) do not adhere to "/settings" if Opera Directory isn't set instead they will end up in their default locations.

in 10.5 (build 3263):
None of cache, opcache, icons, thumbnails or vps adheres to either the Opera Directory or the Opera Local Directory setting.
Cache and Opcache can be set by Cache Directory4 and Operator Cache Directory4.
The only directory to adhere to the Opera Local Directory setting is mail.

So you're correct that the /settings is no longer broken.

Instead the three folders thumbnails, images and vps do not adhere either the Opera Directory or the Opera Local Directory
setting, as they did in 9.64, and they end up in their default locations.

If there's one or more settings that can be used to specify their locations, like for the caches, then for all I know those are not known outside of the Opera team.
And if there currently aren't any settings that can't do this, then those really should be added.

I don't know if command line parameter /setting in 10.00 and up is totally broken. It works for me, provided I have prepared an operaprefs.ini with some entries in the target directory. I quote myself from http://my.opera.com/community/forums/findpost.pl?id=3172870

Originally posted by mimi_s_mum:

This is how I did it with 10.00 in XP3:

1 Alongside the regular one created a new Opera profile directory"C:\Documents and Settings\USER NAME\Application Data\Opera\Opera2\". Also create a desktop shortcut with

"C:\Program Files\Opera\opera.exe" /settings "C:\Documents and Settings\USER NAME\Application Data\Opera\Opera2\operaprefs.ini"

2. Create operaprefs.ini in the new profile folder with:

Opera Preferences version 2.1
; Do not edit this file while Opera is running
; This file is stored in UTF-8 encoding

[User Prefs]
Opera Directory=C:\Documents and Settings\USER NAME\Application Data\Opera\Opera2
Opera Local Directory=C:\Documents and Settings\USER NAME\Local Settings\Application Data\Opera\Opera2
Cache Directory4=C:\Documents and Settings\USER NAME\Local Settings\Application Data\Opera\Opera2\cache
Operator Cache Directory4=C:\Documents and Settings\USER NAME\Local Settings\Application Data\Opera\Opera2\opcache
Temporary Download Directory=C:\Documents and Settings\USER NAME\Local Settings\Application Data\Opera\Opera2\temporary_downloads

3. (same as 2 above) While keeping the regular Opera profile running, clicked on the newly created shortcut for "Opera2".
4. Check opera:about and opera:config to make sure everything is pointing to the new profile folder

Without a prewritten operaprefs.ini, the cache directories and temp download folder would be pointed to:

Operator Cache Directory4={LargePreferences}opcache
Temporary Download Directory={LargePreferences}temporary_downloads
Cache Directory4={LargePreferences}cache

And these {LargePreferences} things seem somehow need manual editing.

Originally discussed here.

Please note I've standard multi-user installation and it is a limited user account (no admin right) I created an additional profile in. ...

To me, what might be broken seems, not /settings parameter per se, but the Opera installation's ability to detect or even understand the{LargePreferences} in the new profile is not set in the standard location.

Just my 5 cents.