All wizards receive the following built-in arguments when run:

Dir=absolute path to wizard directory
Inf=absolute path to the wizard INF file
Blocking=0 or 1 (1 if caller is blocked)
Editing=0 or 1 (1 if wizard is being invoked as an editor)

A page wizard’s INF file should contain the key/value “editor=1” if it can be launched as an editor (like the Frames wizard in version 1.1); otherwise the Editing key will always be set to 0.

When a wizard is run with Blocking=0 (the typical non-blocking case), it should delete the parameter file mentioned on the command line before exiting, to avoid cluttering up the temporary directory. When a wizard is run with Blocking=1, the launching program is expecting to pick up some output parameters from the wizard; in this case, the launching program will take care of deleting the parameter file when the wizard exits. If a page wizard is launched with Blocking=1, it must not make any Web object calls to FrontPage or it will hang. Finally, if a wizard is run with Editing=1, it should delete the PageFile when it exists, since this is a temporary file created by FrontPage.

A few additional parameters have special meaning to a page wizard:

Destination=editor | web | disk
PageURL=URL where page should be saved
PageTitle=title for new web page
PageFile=path to file being edited (only set if Editing=1)

Each page wizard has a default destination. The default destination is usually FrontPage; but if a wizard generates content that cannot be edited by FrontPage, the wizard should load it to the current web instead.

If Destination=editor, the generated file should be loaded directly into FrontPage through Web objects. If Destination=web, the generated file should be loaded directly to the current web through Web object. If Destination=disk, the wizard should generate its output into temp files and return a list of filename/URL pairs via the Output section (see below). However, if the custom wizard creates any non-HTML files, then it must upload them to the web by itself, rather than returning it locally on the hard drive (even when the INF file it receives has a destination of disk.)

• PageURL is the web-relative path to the page being created (such as “index.htm”).
  
  
• PageTitle is the title of the page being created (such as “My Home Page”).
  
  
• PageFile is an absolute path to the file being edited, which has typically just been downloaded by FrontPage.

For backward compatibility, the following arguments are still passed to wizards by FrontPage: WebName, ServerName, Proxy, User.