-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Points Needing Clarity & Direction [Help Wanted] #157
Comments
Hi rxcube, Sorry things are confusing and not working out sofar. We are still in a beta phase, already for too long. With the next version a few path names will change again... About all those admin or non admin things, I am not very confident to answer, but you seem to have Natlink running, so that is probably no issue any more. Let me go over point by point:
Hope this helps. Be prepared for changes with new upcoming (pre) releases. But when this works, you probably can go forward until a stable release is there. |
I understand your pain about corporate environments. Administrator privileges as required to provide write access to the two following files
You can read into a lot more detail in the following NatlinkSource/readme.md |
Hi, Thank your reply, and I understand you’re probably a very busy person, but the shortened answers provided did not actually answer the questions asked, and I still need understanding and help. For Question 1: I have been using Windows since the mid 90’s and I’m considered a more advanced computer user than most people I know but even I did not know how to set a windows variable before asking so providing a link or instructions could have saved me time and I’m sure other users in the future would appreciate this information. Can you verify these instructions to set the NATLINK_USERDIR variable are correct: INSTRUCTIONS TO ADD NATLINK_USERDIR WINDOWS ENVIRONMENT VARIABLE It appears I was successful in changing the location of where the natlink.ini file goes using this method to add the NATLINK_USERDIR variable, but it may require being made temporarily admin (I was already admin temporarily to do the install, so I can't remember for sure if admin was required for this part for sure - I cannot get permission to be an admin permanently in this enterprise environment). Question: Are these above instructions correct? Is that correct to make this a user variable instead of a system variable? There are both "System variables" and "User variables" and that’s another reason why clear instructions are helpful to people who have never tinkered with environment variables before to make it clear all the steps to follow so they don’t mess anything up and can enjoy the full benefit of the Natlink program options. Please verify. Thank you. I am pretty sure that using this variable helped me to eliminate one of the warning messages I was getting, so that's another reason helping people to figure this out is good. I go into more detail on that later in this comment. For question 2 and 3: We have these 4 variables that I’ve seen appear:
If there is only 1 single purpose – "to identify a folder where grammar files exist" – then why would there be a need for these 4 separate variable names? The variable ‘dragonflyuserdirectory’ has the phrase ‘userdirectory’ at the end – does that make that variable function different than the ‘Dragonfly’ variable that doesn’t have the phrase ‘userdirectory’ at the end? How is ‘natlinkuserdirectory’ different from ‘userdirectory’ in its purpose? If they all have one purpose then there should only be one variable so the question is important because I’m trying to ensure the program is running 100% correctly and well with no error messages and become educated on when a user would want to use these 4 variables so I understand the full capabilities of the program and am educated enough to successfully be able to manually edit the .ini file in a meaningful way and understand all my options available. For Question 4: b. The second part to my question 4 was unanswered and I wanted the program to run with no warnings to ensure it’s configured correctly and running smoothly. I used the CLI to configure Natlink but was still getting a warning message when Dragon loads of:
I had thought that was set using CLI.exe dragonfly and user directory commands but this warning still showed. I wanted it to run with no warnings showing also to ensure it's 100% configured and working right. The custom directory for Natlink grammars was not being recognized properly. However, I think this was resolved by me doing the following:
g. click next
Note: The above example would show whatever the folder is that you used for d and n commands if they are both the same - this is just an example but your path will be different depending on what your folder is you pick and your username which wouldn't be rxcube. Side Note: Grammar files must start with underscore _ and end with .py which I didn't know and read somewhere.
How do we get rid of this DPI error message? Thank you for your help for the points where questions still remained. rxcube |
Context: I am on windows 10 in an enterprise controlled environment on a non-admin account where only approved software here can run and I cannot actively change my account from "non-admin" to "admin" because to do that requires admin which I don't have. I can get another admin account to install stuff as needed for installation purposes, but I cannot run stuff from my account as admin ever and this is not flexible. That's not how things work when you work in an enterprise windows version managed by others who are admin. I have a bad hand injury and it's critical I can get Natlink and Dragonfly to work properly and configured properly to be able to do my job hands free via voice only and my job is complicated and difficult now that I'm injured. I have Dragon Naturally Speaking pro purchased version 15, python 3.10-32, natlink 5.4.4, natlinkcore 5.3.5 and dragonfly2 0.35.0 showing as installed in the pip list using the 'py -m pip list' command in the cmd windows console. My user account will always be a non-admin and this is out of my control. My use of Natlink is only for Dragonfly at this time which I am still trying to configure and learn also.
Questions For Clarity:
Documentation says "When you want another directory for your file natlink.ini to be in, you can set this in the environment variable 'NATLINK_USERDIR'. For example, when you want your config files (especially natlink.ini) in a subdirectory of your Documents folder, set this environment variable to '~/Documents/.natlink'."
But documentation doesn't say where or how to set the variable. Where can a user set variables? In what .exe console or program? With what command?
Using Natlink's GUI to configure it to work with Dragonfly adds an entry to the natlink.ini file as:
dragonflyuserdirectory = ~\Documents\Natlink but in the default config version of the .ini file, it has Dragonfly = ~\Documents\Natlink - so which is correct? dragonflyuserdirectory = or Dragonfly = ? It's confusing that there is not consistency to understand things. A similar lack of clarity exists when I see 'userdirectory =' and 'UserDirectory =' both being used in different places based on what a user does with the config tools or in default installed files. Are these both the same or is this case sensitive? How is this 'userdirectory' or 'UserDirectory' different from the 'natlinkuserdirectory =' entry I've seen included at the end of .ini files?
When would a person need a folder for 'Dragonfly' folder or a 'user directory' folder or a 'natlinkuserdirectory' folder specified? Are these all the same thing just written three different ways? It's confusing to not understand the different unique purposes of these various folder options for the .ini file with a real life practical example of using all three to see in practice the purpose.
I made the .ini file in both the user\ .natlink\ folder and the default config folder identical so there's no possibility the .ini is the issue - and when Dragon Naturally Speaking loads, Natlink info window that loads with Dragon Naturally Speaking still says "Warning, no directories specified for Natlink grammars, falling back to default configuration "C:\Program Files (x86)\Python310-32\lib\site-packages\natlinkcore\DefaultConfig"" What am I doing wrong? Seems overly complicated if all the .ini files show I've picked directories and it still doesn't get recognized when Dragon loads.
I noticed the Default Config installed .ini file for natlink configuration has a few helpful comments that some auto-generated .ini file in the user\ .natlink\ folder doesn't contain - not sure if that's due to the GUI or the command line interface program or the copying of a .ini from default config by the code, but basically two .ini files exist and before I edited them to make them identical the one in the user directory didn't have all the helpful comments the other default config one had. When you do testing you should be making sure the command line interface, GUI, and any auto-copied version contain all the same helpful info as comments because this is not happening somewhere along the way and the program or programs or something it did produce two different .ini files initially before I forced them both to be the same. One had the helpful comments, one did not.
It is unclear if the '~\Documents\UserDirectory' format is supported in the version I'm running? In one of your comments on this website you stated that the full direct userpath such as C:\User\X\ would have to be used instead of ~\ due to some issue - is that still correct and do the paths have to be fully written in the .ini files as C:\User\X\somefolder or can a person use the format of ~\somefolder ???
I can only respond 4 work days a week that I work and I would not bother you to respond on any weekend at all please, but I appreciate your response on those 4 days I work. Thank you for your assistance, it is greatly appreciated. Thank you for developing this program and your efforts. Below is my current configuration in my natlink.ini file for your examination and comments as well. Thanks,
rxcube
#natlink.ini contents:
The text was updated successfully, but these errors were encountered: