Search the Community
Showing results for tags 'mcamx.config'.
Found 1 result
-
Hi Everyone, If you are looking for something cool to do with mastercam go to the next post. I did a search and I couldn't find a solution to this so I’ll throw this out there; We are considering converting over to Nethasps within our organization. We have a location that already has a license server running so we had users test the connection. Everything went smooth and we didn’t see a single issue. One of the testers was already on a nethasp so all he did was change the nethasp.ini file. The other person had a hard hasp and it caused a huge headache. After the testing I think the user ran the nethasp.exe utility and selected Hasp. He started Mastercam again and it fired right up. I thought everything was fine – now I found out that all of his user settings changed? At first I thought there was no way – the nethasp.ini file only has the connection settings. I started digging and I saw that some of the stuff is stored in the registry. So today I conducted a little experiment. I changed one of the registry settings for the shared directory and reverted to a standard hasp. I opened up the directory I created for the test and inside was a file - mcamx.config. I looked at the registry value and it had returned to the default folder for shared documents?? I guess they were right – changing back and forth between a hasp to a nethasp can have some unexpected changes. I’m not sure what his settings were before the test, but I definitely didn’t consider this as a potential problem. Has anyone else run into this? Any recommendations on making the conversion smoother next time, or knowledge of what changes when running the nethasp.exe utility. Thanks in advance, Dan
