1 Oct 21:57
Re: Execution Mode Configuration for Network Installation
Branden Ohlinger <bohlinger <at> alb.edu>
2008-10-01 19:57:34 GMT
2008-10-01 19:57:34 GMT
Thank you for your response, but I'm afraid I am still not able to resolve this issue. I apologize if I am missing something. I logged in to the server as the local administrator, launched WinEdt, and disabled auto-detect for the items in the Tex System tab of the Execution Modes-MikTex window. I then manually entered the Tex Root, Bin, Help, and Dvi Viewer paths and hit Apply. In my first attempt, I wrote the paths according to how they were available on the server (e.g. D:\Applications\Math\MiKTeX 2.7 ). In my second attempt, I wrote the paths as they would be available while the \\server\Applications share is mapped by a client (e.g. O:\Math\MiKTeX 2.7 ). After each attempt, I ran the Configuration Wizard -> User Profiles, and pressed Enable/Update Automatic Profiles. Then I logged in on a client computer as a domain user, mapped \\server\Applications as O:\ and then deleted the WinEdt folder in my Application Data. After those steps, I launched WinEdt and in both attempts I found that my changes as administrator on the server seemed to have no bearing on the client's settings. I apologize, but I need help understanding what it is that I am missing. Is it necessary that the client computer have registry entries or a path entry for the software? I had assumed that since it was a network installation this would be unnecessary.(Continue reading)
RSS Feed