Thanks, Jeremy. Question...does the ini "snip" require any header
text or the bracketed heading of the section, or can I just include a
single line and that will get referenced. For example, for the

;DCL .ini file created Thu Mar 02 10:01:51 2006
; for C:\Documents and Settings\John Posada\My



can I just use gif=bmp or must I include the [GraphFiles] part also
do I need to include the header portion with the ;

--- "Jeremy H. Griffith" <jeremy at> wrote:

> On Thu, 2 Mar 2006 08:56:43 -0800 (PST), John Posada
> <jposada01 at> 
> wrote:
> >I'm trying to convert 15 books to Word using MIF2GO. A recent
> feature
> >added to M2G is the ability to place a path in the INI to variable
> >changes so that instead of making changes in each INI, the path
> >brings them in to the default ini.
> Yes, we use that ourselves constantly.  You can chain these
> references too...  ;-)
> >I've been unable to find how to implement this in the help. Can
> >someone point me to the topics or give me the steps that implement
> >this?
> It's in the Automation chapter, in par. 27.2, "Importing settings 
> from configuration templates".  Basically, you make an .ini
> file that has the settings you want your config template, give
> it a new name, and reference it in:
>   [FDK]
>   ; ConfigTemplate = path to configuration template file
>   ConfigTemplate=D:/path/to/MyTemplate.ini 
> Any settings in your mif2htm.ini (or mif2rtf.ini) will override
> the settings in your config template, so you will want to strip
> your local .ini down to the minimum you need in it.  Par. 27.2.1
> gives the details on which settings to use where.
> -- Jeremy H. Griffith, at Omni Systems Inc.
>   <jeremy at>

John Posada
Senior Technical Writer

"So long and thanks for all the fish."

Reply via email to