Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,090 of 9,834    |
|    Zal Dabhoiwala to All    |
|    Re: Command-line options -e & -f    |
|    27 Jan 07 10:58:15    |
      From: dabhoiwala@no.spam.com              I would guess that you would mostly use them with a Runtime distribution       of an application to ensure that registry settings never/always change.       -e prevents writes to the registry, so if your install script has done       all the work you don't want end-users changing anything       -f forces writes to the registry, so maybe useful if you want your       end-users to be able to customize settings for themselves.              It would be interesting to know which one is higher in the hierarchy if       you use them both!              On 27-01-2007 08:31 Anne Wainwright wrote the following email:       > Hi,       >       > Why would I want or need to use these?       >       > Just curious       >              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca