Memory is not always a reliable tool. Sometimes you are absolutely sure you remember something correctly, even when you don't. I have wasted a phone by entering the wrong PIN-code three times; at the time I was absolutely sure it was the right code, but a day later I realised what my code really was. I recommend meditating before going to sleep; clear your mind of what you currently think is the correct passphrase and ask your mind what the real passphrase is. Even if you don't "get an answer" during your meditation, since you have been focusing your mind on it, the next morning you may suddenly get it. Also stop re-entering the same passphrase that isn't working, you are only confirming an incorrect memory and making it stick.

When trying to change my emailadress via my profile, I enter the new emailaddress, my current password and press Change profile, I get the error:
The following errors occurred when trying to save your profile:
    The password you entered was not correct.
I confirmed by logging out and in that my password is correct. How can I change my profile?

Keep in mind the 5PLN (~1.23EUR) fee the Polish bank of Intersango charges. https://intersango.com/fees.php

I would like to be whitelisted, so I can:

• reply to the Intersango EUR SEPA thread and make a comment about the 1.23 EUR fee from the bank
• raise my issue with changing my profile in the Technical Support area

https://bitcointalk.org/index.php?topic=10264.msg154986#msg154986

Moved: https://bitcointalk.org/index.php?topic=50434.0

It seems phoenix.exe is launched with incorrect parameters (i.e. lacking a space) when fastloop is disabled. In Process Explorer on phoenix.exe (Properties > Image):
phoenix  -u http://user:pass@bitcoinpool.com:8332 -k poclbm VECTORS BFI_INT FASTLOOP=falseAGGRESSION=7 DEVICE=0 WORKSIZE=512 -q 2
This probably causes both the fastloop and aggression settings to not be parsed. For some reason when launching like this (also when launched manually in a command-prompt), on my system the miner only uses up to 82% GPU and thus a lower hashrate.

Tested on: Phoenix Rising 1.3c
Hardware: Radeon HD 6850
Workaround: enable fastloop

EDIT:
On second inspection it seems that FASTLOOP=false is still parsed even if another argument is directly attached to it, so only the aggression argument is ignored. Apparently my card needs fastloop to run at full-speed, so I should have just enabled it in the first place.