Re: error if texmf.fndb and mpm.fndb are not writable, even if no write is occuring
Ulrike Fischer <[email protected]>
| Newsgroups | gmane.comp.tex.miktex |
|---|---|
| Message-ID | <[email protected]> |
Am Tue, 23 Apr 2013 15:20:45 -0700 schrieb Rick Pember: > > I think you should give more informations > > regarding the accounts and > the installation. > > Here's what I did in detail: > > 1) create restricted user account "user1" and log in to that account. > (restricted = non-administrator) > > 2) download MiKTeX Portable 2.9.4757 to desktop > -- we're using the portable package because we want to create a portable > folder containing MikTeXwhich we can then give to our customers and > which they can then use in a restricted account > > 3) create a folder miktex and move installer into it > > 4) open folder miktex and double click extractor. > -- extract to C:\Documents and Settings\user1\Desktop\miktex > --twoofthefilestheextractorinstallsare .... > > 9) Now right click texmf.fndb and mpm.fndb again and click "Deny" on > Write access for user1. > > Recall this is what our customer is requiring for an installation in > Program Files. Imho this sort of installation doesn't make sense. You are trying to move a portable installation - meant for users which can't write to program files - to this very place. Naturally the portable miktex assumes that it has full writing access to its data - what do you expected? The main point of a portable application is that it doesn't use user profiles but its main folder. In my opinion your user1 has these options: 1. He installs a normal miktex in his restricted account in some folder outside program files where he has writing rights. This will give him a single user installation for this account. This works without any problems - I have such installations on various PC including one where I have very restricted rights. This won't need writing rights for program files at all - neither during installation nor when using miktex. 2. If he has writing rights during the installation: - He could also try to make a single user installation in program files. It *could* work and need writing rights only if new packages need to be installed afterwards. But I never tried this. - Or he installs a multiuser installation. User1 can that use this miktex in his account without writing rights for program files. New packages will be installed to his user profile. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr