Well, if you didn't delete it completely, you can restore it from recycle bin, but not sure if that's the case. Otherwise you may need to reinstall NVDA, or someone needs to give you that file from his / her NVDA.
hmm, reinstalling would be angry, I made a lot of custom settings, I made a lot of words for my voice in the that were pronounced not correctly. It would be better if someone could give me the file again.
No, if the file is deleted, it will always be deleted from that copy and the portable copies created from it. User configuration is only your user-specific changes to the settings and addons.
Yes, but it's how I said anyway. After all, I just tested it. So if you delete that file out of the running copy, portable copies created from that copy won't have that file included. I don't know if it's the same with portable versions that you install, but it's certainly the case with installed versions you create a portable copy from.
I luckily had a portable copy on my external hard drive where the file builtin.dic exists. I copied this file and now it pronounces all words correctly again! I'm so happy about that.
Oh, now I got your point, Karl. So I had suggested that she make a portable copy by running the installer if she already had it, without having to reinstall the app if she was worried risking losing anything.
Ah right! Now I got yours too. But why would that happen, if it's just a reinstall without uninstalling it first, like an update? Ok, maybe if the installation gets cancelled for some reason, but this can also happen with creating a portable copy. Well anyway, the problem is fixed now, and that's good.
Well, who knows what could happen. A reinstallation may involve overwriting some files, whereas a separate portable copy does not, under normal circumstances. It should have no effect on the installed copy even if things do not go as expected. In any case, as you said, the problem is fixed now. -- (hozosch): Ah right! Now I got yours too. But why would that happen, if it's just a reinstall without uninstalling it first, like an update? Ok, maybe if the installation gets cancelled for some reason, but this can also happen with creating a portable copy. Well anyway, the problem is fixed now, and that's good.
