Comment 1 by jteh on 2010-11-10 17:36
Possibly a duplicate of #918.

Works fine for me on 64 bit Win7. Did you install NVDA to the default directory? Do you have a systemConfig folder in your NVDA program dir?
Changes:
Milestone changed from None to None

Comment 2 by elliott94 (in reply to comment 1) on 2010-11-10 17:47
Replying to jteh:

Possibly a duplicate of #918.

Works fine for me on 64 bit Win7. Did you install NVDA to the default directory? Do you have a systemConfig folder in your NVDA program dir?

Yes, I installed NVDA to the main directory (C:\Program Files (x86)\NVDA). I don't actually have a SystemConfig directory in the root of the NVDA folder, and going to a Secure Desktop screen (for example, locking my machine) default settings are used.

Comment 3 by elliott94 on 2010-11-13 10:07
Very strange. Just tried this again, and I now have a SystemConfig directory in the root of my NVDA folder. I can confirm that this does now in deed work, any ideas why it didn't before?
Unfortunately, the log doesn't give any useful info at all.

Comment 4 by jteh on 2010-11-17 02:18
Damn. I understand why this happened now.

Str:

1. Delete your NVDA systemConfig folder. (This is how it is when you clean install.)
2. Immediately try to use the "Use currently saved settings on the logon and other secure screens" button in NVDA's General Settings.
3. Actual: Success, but nothing is actually done.
4. Expected: The settings should be copied to systemConfig.

This does work if systemConfig already exists, which it does as soon as you start the system copy at least once.
Changes:
Milestone changed from None to 2011.1

Comment 5 by jteh on 2010-11-17 02:29
Fixed in efbf419.
Changes:
Changed title from "Unable to copy settings to secure screens when using Windows 7 64-bit" to "Unable to copy settings to secure screens immediately after a clean install"
State: closed

Comment 6 by jteh on 2010-11-17 02:31
Not a duplicate of #918, as that bug indicates an error occurred on the first attempt.

Comment 7 by elliott94 on 2010-11-17 11:43
Glad this has been fixed.
Just out of interest, why didn't this work the first time?
You say that the folder is created after th first press of the button, but how is this the case when it can't be seen in the NVDA directory?

Comment 8 by jteh (in reply to comment 7) on 2010-11-17 12:09
Replying to elliott94:

You say that the folder is created after th first press of the button, but how is this the case when it can't be seen in the NVDA directory?

No, the folder was created after the system copy of NVDA (i.e. the one that runs on secure screens) first runs. Thus, if you installed and hit a secure screen before using that button, it would have worked.

Comment 9 by elliott94 (in reply to comment 8) on 2010-11-17 14:53
Replying to jteh:

Replying to elliott94:

You say that the folder is created after th first press of the button, but how is this the case when it can't be seen in the NVDA directory?

No, the folder was created after the system copy of NVDA (i.e. the one that runs on secure screens) first runs. Thus, if you installed and hit a secure screen before using that button, it would have worked.

That's very strange; after my first attempt of pressing the button and getting the success message, I then did a Windows plus L to lock my desktop and then re-entered my password, but the folder still wasn't in the root of the NVDA directory.
Doi you have any idea as to why this was the case?

Comment 10 by jteh (in reply to comment 9) on 2010-11-17 20:48
Replying to elliott94:

That's very strange; after my first attempt of pressing the button and getting the success message, I then did a Windows plus L to lock my desktop and then re-entered my password, but the folder still wasn't in the root of the NVDA directory.

Doi you have any idea as to why this was the case?

No. If it's working now, let's leave it alone. However, feel free to comment again if it breaks after this fix (or in the next release version).