I have previously reported some windows updates changed some of the performance of the 0.1.4 version... but I got mistaken by the fact that I am using the second GPU for my monitor... and the AMD driver has a "flaw" (in my opinion...) that when the first card to be detected over the PCIe has no Display adapter connected to the RAMDAC... it does not "turn on the full potential of the GPU"...

Workaround:
Simple connect a display there.. you don't use.. or plug-in and plug-out the other card display just to "activate" the RAMDAC...

I had no time to investigate further yet... just reporting.
My drivers are 13.12 (win 7 x86_64)

Just to be sure it's not related to my GPU type, i am using:
PCIe 1: R9 270X
PCIe 2: nothing
PCIe 3: R9 290X (monitor connected)

MOtherboard: ASUS GENE II


NOTE: I guess that while there is no way to say to old BIOS (like X58 chipsets like mine) which is the "main" adapter... where you use your display screen... this will be a problem. But it lacks fixing... as for my logic.. it's considered a driver bug.. to identify the GPU as non-fully-functional...

ASUS R9-290X 1050 core.. default RAM.. 3150 col/m (+28% from 2450 col/m)! catalyst 13.251-131206a-165817C-ATI over windows 7 64 bit.. over XEON overclocked 35% (I know it does not matter.. lol).

Best time to loose internet connection ever =) happy birthday...

  = 25%! :=)

New pub-key... 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK (last one was 5kKsqBdtpiStC3Ww9GG9SfF4ecqBV9FpHwPpDtcTd4iHJayRMe)

Quote from: bytemaster on January 04, 2014, 03:05:44 pm

Quote from: JustHayden on January 04, 2014, 10:37:52 am

Quote from: zhrmghgsc on January 04, 2014, 09:11:20 am

Thanks for update. What if one person own two Keyhotee IDs, is it OK if he use the same identity?

This actually raised another question in my mind. If I have another persons information, what's stopping me from posing as someone else through Keyhotee? I mean like if I had my friends License and Passport/Social Insurance number and created a Keyhotee ID under his name? This would be easily done since you are aloud to have multiple identities.

There is still the brain wallet key which you would not know.

I have a question on having multiple Keyhotee ID's. I have several for various purposes, one for personal, one for business, and one for the wife. Is is best to create a separate profile for each ID so that a unique Brain Wallet Key Phrase is created for each plus a public key?

Then for example on my personal profile, I can add the company Identity so that I can manage both ID's from one profile, but the company ID could be separated to a different system in the future if needed by using the original profile information and Brain Wallet Key Phrase that was created for it.

Am I understanding this correctly? I just want to get it right before submitting it all to the Founder ID Registration site. Thank you.

I think things are like this (for now):
The public key is created along with the profile information (brain wallet key phrase) and your password for the profile. So if you use the same profile information for more than one ID, you will have profile dependent IDs... each one of that IDs will be represented by that profile.

Probably there will be a way to generate a new public key to change password or even to move you ID to another profile (example.. when you want to change some info for your profile, as for example... you drivers license). As for now.... I think you just need to think that everything you attach to a certain brain/profile passwords... it will be generating dependent pub keys.

OK,

Not very successful but here it is all the tests I made (saved all info to make tests reproducible):

Current keyhotee (A) = C:\keyhotee_0.5.0
Profile password for A - (A.1)
New keyhotee (B) = C:\keyhotee_0.5.2
Profile password created with B - (B.1)
Profile information (C) = C:\Users\<user>\AppData\Local\KEYHOTEE

- Test 1:
Set B and open KEYHOTEE.EXE with A.1
Result: My profile opens without errors and I am able to see everything I had before except that my Keyhotee ID is now "Unregistered". Apart from that everything shows up as before. The language of my country also appears as I translated (maybe add an option in future to change language). I still have to make some adjustments to translated values. I have also used "http://invictus-innovations.com/founder-sign-up/" with the information I had before and the first pub-key. And if I try to create a new identity for the same keyhotee ID it will show the same original public-key.

- Test 2:
Deleted C
Created a new profile with A and using the same information that I had previously entered when creating A in first place.
Results: It was possible to load the same profile with A or B, and both generated the same pub-key for a certain keyhotee ID. Although the key is not the same as the one I have created in first place. For example... my first key is 5kKsqBdtpiStC3Ww9GG9SfF4ecqBV9FpHwPpDtcTd4iHJayRMe and with a new generated profile it is 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK.

- Test 3:
Deleted C again.
Created a new profile with B and using the same information that I had previously entered when creating A in first place.
Results: It was possible to load the same profile with B only, but it generated the same pub-key as in Test 2 for a certain keyhotee ID (and profile password): 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK

Error generated in Test 3 when I try to open with version 0.5.0:
#########################################################
3431762ms th_a       LoginDialog.cpp:57            onLogin              ] error
assert
fc::exists( file ):
    {}
    th_a  aes.cpp:295 fc::aes_load

    {"file":"C:/Users/<user>/AppData/Local/KEYHOTEE/profiles/<my profile with spaces>/.s
tretched_seed"}
    th_a  aes.cpp:311 fc::aes_load

    {"profile_dir":"C:/Users/<user>/AppData/Local/KEYHOTEE/profiles/<my profile with spaces>"}
    th_a  profile.cpp:124 bts::profile::open

    {}
    th_a  application.cpp:341 bts::application::load_profile
#########################################################

Other notes:
- Using different profile passwords generated different Public-keys.
- Noticed that over creation in A the middle name is not used for profile creation and in B it is.

Question?
What should be done now? Should I re-register the new pub-key I have with my key in "http://invictus-innovations.com/founder-sign-up/" I found it strange because when in Test 2 or 3 i use my Keyhotee ID (the pub-key is then 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK) and Founder Code... it says "invalid"... But before it did say the correct stuff.

Hi all..

I am trying to achieve 2 goals.. first is to "get a clean" simplest miner possible for PTS and second add support/optimize for big-endian processors.

Any help/info would be welcome.

Regards