The math department at our university has asked the library (me) to add TeXnic onto the existing miktex installation in our public computing lab, Windows XP.
Installing TeXnic goes fine, however, on launch TeXnic does not automatically detect MikTex. I am prompted into an "Output Profile" wizard and navigate to what (I think is) the MikTex "Tex executable" that the wizard is looking for. (C:\Program Files\Miktex 2.6\bin). The Wizard closes and states it has created the Output Profiles.
However, each subsequent user of the machine is again prompted with the Output Profile wizard. Looked in all the usual places (Documents and Settings Appdata or Local Settings, etc) but can't find where the profile might be stored. There is a nicely labeled XML file called "Output Profiles" in the TeXnic program files folder, but it does not seem to change with completion of the Output Profile wizard.
So -- what am I missing/doing wrong?
In case it's not obvious, I don't even really know what Latex is -- my job is just to get it running in the lab.
Thanks for any advice, suggestions, or pointers or even random thoughts.
General ⇒ TeXnic in a public computing lab
Re: TeXnic in a public computing lab
Update: RESOLVED.
Solution:
1. Installed TexNic and did output profile configuration as a user with permission to do registry edits.
2. Exported HKEY_CURRENT_USER registry keys relating to "ToolsCenter." Modified keys to refer to HKEY_USERS\DummyName.
3. Imported Windows Default User's ntuser.dat hive into registry as HKEY_USERS\DummyName.
4. Added edited ToolsCenter registry keys into the Default User's ntuser.dat.
5. Unloaded the Default User Hive.
This avoided the lengthy process of having to create a new default user, which would also work.
Solution:
1. Installed TexNic and did output profile configuration as a user with permission to do registry edits.
2. Exported HKEY_CURRENT_USER registry keys relating to "ToolsCenter." Modified keys to refer to HKEY_USERS\DummyName.
3. Imported Windows Default User's ntuser.dat hive into registry as HKEY_USERS\DummyName.
4. Added edited ToolsCenter registry keys into the Default User's ntuser.dat.
5. Unloaded the Default User Hive.
This avoided the lengthy process of having to create a new default user, which would also work.