View Full Version : Users Not able to access custom menus
Borgster
2010-11-03, 01:37 PM
I've been asked to help out a former employer update their custom menus to Acad 2008/2010. I had no problems with that. I was given administrator access in order to accomplish it.
After I completed the menu updates, I stored all of the custom files on the Windows server. I created a batch file that copies all of the custom files to the appropriate Acad support folders.
To test my new set up I went to another station, logged on as administrator, ran my batch, imported the new profile and Acad was ready to rock. The test was to see if my updates would carry over to another user on that system. When the person that normally uses that computer logged on he didn't get the updates. However, a different user, who doesn't normally sit there logged on and they worked fine.
We are running XP on the workstations. The to ppl I spoke of do not have admin rights.
Is this a rights issue or something else?
Borgster
2010-11-04, 07:31 PM
This issues has been resolved.
I've been asked to help out a former employer update their custom menus to Acad 2008/2010. I had no problems with that. I was given administrator access in order to accomplish it.
After I completed the menu updates, I stored all of the custom files on the Windows server. I created a batch file that copies all of the custom files to the appropriate Acad support folders.
To test my new set up I went to another station, logged on as administrator, ran my batch, imported the new profile and Acad was ready to rock. The test was to see if my updates would carry over to another user on that system. When the person that normally uses that computer logged on he didn't get the updates. However, a different user, who doesn't normally sit there logged on and they worked fine.
We are running XP on the workstations. The to ppl I spoke of do not have admin rights.
Is this a rights issue or something else?
Borgster
2010-11-18, 04:47 PM
This issues has been resolved.
Well, I have to back pedal. The same thing happend on another users computer. Any suggestions?
irneb
2010-11-19, 02:36 PM
Not sure about administrative rights. From your original description I think there's a problem with where the CUI (and other) files are copied to.
If you're not fiddling with ACad's support paths, but simply copying the files to each user's Documents and Settings\Application Data\AutoDesk\......... folders you should note each user has his own copy of these. Thus you may have copied it to the Default one which is used when creating a new user on the PC, but not the existing user(s)'s folder.
I have a different setup, since we have quite a few PCs and have one or two swapping users on a daily basis. I have a single folder made on each user's PC (directly under the C:\ ). Then in my CUI's MNL file I have some lisp to check the (getenv "ACAD") if that folder's already in the support paths, otherwise it simply prefixes it with a ";" separator into the (setenv "ACAD" newpaths).
Another solution is to have your lisps not expect everything to be in a support folder. Here I've made a lisp function which checks where the CUI was loaded from and search in that folder when another lisp want's to load something like a DCL file. This way is the best when you have no clue about where the custom stuff is. As long as every custom thing's in that one folder (or with some more fiddling subfolders of it) all that needs to be done is to load the CUI as partial / enterprise.
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.