• Reinstalling may be safer because you are not changing where Microsoft Word looks for its Temples. However, running the installer again may take longer. If you are using other templates, or have modified your Normal template, this would be the best choice.
• Re-pointing Microsoft Word to your existing installation of Script Werx templates may be quicker, depending on how long it takes your computer's Search or Find tool to locate the Script Werx templates.

Cause:
This is caused by one of those "Microsoft knows best" features that overrides what you--or in this case, our software--fully intends to do, without any warning.

Solution:
Turn off the feature and try again. The Script Werx template will remember all of the character names that you have already entered.

• On the Word menu, select Preferences (on Windows, from the Tools menu, select Options); then select Edit.
• Deselect (click to remove the check mark in front of) Smart Cut and Paste.
• Click OK to close all open dialog boxes.

This has been corrected in our current maintenance update and on all versions of our software beginning with version 11.1.

Cause:
Problem in the computer code that runs when creating a new script.

• On the Script Werx menu, select Preferences.
• In the Script Werx Preferences dialog box, locate the Opening Tutorial area.
• Click the radio button for Don't give tutorial option.
• Click OK.

Cause:
An AutoOpen macro (computer code that runs automatically when a document opens) uses the Windows name of the Normal template (Normal.dot) rather than the Macintosh name (Normal). This macro normally helps a script find and attach to the appropriate Script Werx template when the script is moved among different computers.

Solution:
This needs a two-step solution: Fix existing scripts; stop the problem from happening again.

Fix existing scripts –The immediate solution is to hold down the Shift key when opening the script. The more lasting solution is to delete the AutoOpen macro:

1. Open the script (holding down the Shift key if the appropriate Script Werx template is not installed)
2. On the Tools menu, select Macro and then from the pop-out menu, select Macros...
3. In the Macros dialog box that opens, make sure the Macros in: field displays the file name of the script from which you want to delete a macro. A single macro, AutoOpen, should display.
   
4. Click to select the AutoOpen macro and then click the Delete button

The name of the macro (AutoOpen) should disappear.

Stop the problem from happening again – obtain a free maintenance update or replace the currently installed template file named Template Attach Tool.dot with one of the following downloads (appropriate to your computer).

• For Macintosh this is the copy of Template Attach Tool.dot to download.
• For Windows this is the copy of Template Attach Tool.dot to download.
  

Once downloaded, replace the existing template (Template Attach Tool.dot) with the download
1. Find the Script Werx templates on your hard drive: On Macintosh use Sherlock. On Windows, click Start, then Find (or Search). Then locate a file named Template Attach Tool.dot.
2. Replace this with the new version of this file (which may need to be extracted from the file you download, in which case it can be extracted directly into the folder you identified in step 1). The file names should be identical, so if dragging (or extracting) the new file into the Templates folder, you will be asked if you want to replace the existing file. Click OK.

Cause:
Script Werx installers prior to v10b2 do not know to look for the 2003 version of Word.

Solution:
Obtain a free Script Werx maintenance update.

Cause:
Some keyboard shortcuts were lost during an early revision of v10.

Solution:
Obtain a free Script Werx maintenance update.

Cause:
On Macintosh, Microsoft Word's Page Border feature does not work correctly with many printers when the option is chosen to measure the border from the edge of the page.

Solution:
Either obtain a free Script Werx maintenance update or use the following, fairly easy, work-around to remove or modify the page border:

1. Place your cursor on the cover sheet
2. From the Format menu, select Borders and Shading
3. Click the Page Border tab
4. Either remove the border by clicking None (in the upper left corner under Setting ), or to move the border within the printable area, click the Options button.
5. In the Border and Shading Options box that opens, in the drop-down list next to the field labeled Measure from, select Margin.
   
6. Enter the numbers for distance from the different margins. This will take some experimentation. Try starting with 20 pt for all four measurements.
7. Click OK to close out of all boxes.

Cause:
Script Werx templates have different names for their Macintosh and Windows versions (done to keep the Windows version backwardly compatible with earlier version of Windows which would accept file names with no more than eight characters). So when a script created on one platform is moved to the other, it tries to attach itself to a template name that does not exist, and by default attaches itself to the Normal template.

Solution:
Attach the script to the appropriate Script Werx template:

1. On the Tools menu (File menu for versions of Word older than Word 97 or 98) select Templates and Add-Ins. A dialog box will open.
2. Click the Attach button. A browse dialog box will open.
3. Use the browse dialog box to select the appropriate Script Werx template.
4. Click Open to close the browse dialog box.
5. Click OK to close the Templates and Add-Ins dialog box

• Installation Option : Word 2001 now provides a My Templates folder within its Templates folder as a place to store templates you create or purchase (such as Script Werx ). We recommend that you do not use it for Script Werx templates. Although there is no technical reason not to store Script Werx templates in this new folder, doing so creates an extra step when starting a new script and our Script Werx documentation assumes that our templates are kept loose in the Templates folder rather than stored in a folder within this folder.
• File Menu Change : On the File menu for 2001, a Project Gallery menu item has replaced the New menu item. This means that when starting a new script, you need to choose Project Gallery in order to get access to Script Werx templates.

The current maintenance update of Script Werx for Macintosh includes all revisions needed to work correctly with Word 2001. It is available for download by any registered owner of Script Werx.

Cause:
On occasion, some virus protection programs, especially from lesser-known companies, mistake some of the more complex macros within Script Werx for a virus. A reason behind this is that Microsoft Word macros are a common means of spreading viruses. In an effort to err on the side of caution, false positives are fairly common.

In three instances, Script Werx has triggered false positives. At no time has any Script Werx template actually carried a virus. Before release, Script Werx software is checked using the most current virus detection software from Virex or McAfee and at no time has a virus been detected.

Solution:
Reinstall Script Werx from your original master disk or installer. Then see if the presence of a virus is still indicated. If so, contact the maker of the virus detection program (or check their web site) to see if they are aware of false positives being triggered by Microsoft Word macros. If not, contact technical support here at Parnassus Software (818) 952-8102. We will follow up with the maker of the virus detection software to determine why it is indicating the presence of a virus.

Multiple scripts open --If scripts in more than one format are open at the same time (example: a two-column script and a four-column script) features common to both may not work. This means that it is good practice to have only one script open at a time.

Disabled macros --Macros have been disabled during installation of Word. In the interest of preventing the spread of viruses carried by macros, Microsoft now makes it possible to render Word 98 and above incapable of running any Macro; furthermore, the language that presents this option during the installation makes this sound like a pretty good idea.

On Macintosh, this problem can also be caused by corrupted preference files ( see below ).

Solution:

Multiple scripts open --Make sure that all scripts that are open are attached to the same template (example: all open scripts use the feature film format). The use of features is lost only when scripts attached to different templates are open at the same time. Although this can be frustrating enough, no other problems are caused by having different-format scripts open and in no case is there any damage to the files themselves.

Disabled macros --Test to be sure that the macro functionality has been disabled; and if so, reinstall Microsoft Word, being sure to enable macros:

Steps		Details
• Create a new blank document		• From the File menu, Select New and then click OK. By default, this new document will be based on the Normal template, meaning that Script Werx is now in no way affecting the behavior of Word. To be sure, on the Tools menu, select Templates and Add-Ins. In the dialog box that opens, in the field for Document Template, the word Normal should appear.
• Try to create a new macro.		Within MS Word: From the Tools menu, select Macro, then Macros from the popup menu. Type in a name for the macro (such as "test"). Click the Create button. If this does not allow you to create this test macro, the macro functionality for Word has been disabled.

Macintosh Only:
Problems running macros may also be caused by a corruption in any of several preference files. To test for and rectify this situation:

• Quit out of Microsoft Word
• From the Preferences folder (within the System folder), drag onto the desktop the following files (they will be recreated when MS Word is launched again; all files may not be present). Note that with Office 2001, there is a Microsoft folder within your Preferences folder, within which some of these files reside (although not all, The Holy Redmond Empire makes its own standards):
  1. Embedding Preferences
  2. Microsoft Office
  3. PPC Registration Database
  4. VBA Preferences
  5. Word Settings (8) [or the version number of the copy of Word being used]
• From the Extensions folder (within the System folder), drag onto the desktop the following files (they will be recreated when MS Word is launched again; all files may not be present):
  1. Microsoft Component Library
  2. Microsoft OLE Automation
  3. Microsoft OLE Library
  4. Microsoft Structured Storage
• From the Microsoft Office Templates folder delete Normal

If this fixes the problem, delete the above files that have been left on the desk top. Restore them to their initial locations if the problems worsen.

If you have not done so within the past three months, you should also rebuild the desktop:

• Restart your Macintosh while holding down the two modifier keys option + command (the apple key).

If you are still having problems of a general nature, such as your Macintosh not starting up properly, "zap" the p-ram:

• Restart your Macintosh while holding down the four keys: option + command (the apple key) + r + p. You may need help, or hold down one of the keys by holding a pencil in your mouth. Continue holding down all four keys until your Macintosh restarts (you hear the startup sound) at least twice.

Cause:
Problems associated with earlier versions of Script Werx.

Solution:
obtain a free maintenance update .

Cause:
The installer for the Windows version (Mac version was not affected) posted on our Update Download page from 7/10/01 through the morning of 7/24/01 included a Feature Film Template (-FetrFlm.dot) that would not allow the typing of a capital P. The problem has been fixed. If you are using this template, please download the currently posted update to avoid this problem. Downloads from our online order page were not affected.

Solution:
obtain a free maintenance update .

Cause:
The upgrade to version ten of Script Werx for Windows included changing the names of the templates from eight-character names to more meaningful names (example: -2Column.dot to -Two-Column Template.dot). The code in some of the first version ten installers was not appropriately updated to the new file name.

Solution:
Either obtain a free Script Werx maintenance update or use the following, fairly easy, work-around:

1. Find the Script Werx templates on your hard drive: Click Start, then use find (or search) to locate a file named -Two-Column Template.dot.
2. Copy this file (right click and from the pop-up menu, select Copy ).
3. Paste the copy into the same folder (with the same folder still open and no file selected, right click, then from the pop-up menu, select Paste) .
4. Rename the file -2Column.dot (right click the new file [copy of -Two-Column Template.dot] and from the pop-up menu, select Rename. Then type in -2Column.dot). Do not forget the hyphen in front, this is critical.

Close the folder and all should now work fine when creating a two-column version of a four-column script.

Cause:
Problem associated with version 9.0 of Script Werx when running on the Windows NT operating system.

Solution:
Obtain a free Script Werx maintenance update to version 9.0a or above.

Cause:
Problem associated with version 9.0a of Script Werx for Windows.

Solution:
Obtain a free Script Werx maintenance update to version 9.0b or above.

Cause:
Problem associated with version 9.0 of Script Werx when running on a Windows operating system.

Solution:
Obtain a free Script Werx maintenance update to version 9.0a or above.

Cause:
A single row is longer than a page in length and Cell Breaking is turned off; so the computer is being told to print more than a page of material on a single page. This may be a function of the writer pressing the Return key rather than the Tab key to create new visuals.

Solution:
Always press the Tab key to create a new visual.

Also, as a general rule, shorter rows are better. They certainly should be shorter than a page in length.

You can also set Script Werx to allow page breaks within a row, but be aware that this will place some audio on the page following the accompanying visual (rather than keeping all audio on the same page with its visual). You can do this by turning Cell Breaking on: From the Shortcuts toolbar or Script Werx menu, choose Cell breaking and then click on.

Cause:
The Storyboard template includes a font style named Character, which conflicts with the paragraph style used by screenplay formats called Character.

Solution:
Download and install the current maintenance update or delete the existing Character style from the Storyboard template:

Steps		Details
• Open the Storyboard template.		From the File menu, Select Open. In the browse box that opens, locate the Templates folder within the folder for Microsoft Office and double click on the Storyboard template: -Strybrd.dot (-Storyboard Template in Macintosh) The Script Werx Storyboard Template should open.
Delete the style named Character.		On the Format menu, select Style.... On the scrolling list of styles, click once to select the style named Character. Click the Delete button to delete the style. Click Close to close the dialog box. Close the template file, saving changes.

After completing this work around, when creating a storyboard from a screenplay format script that includes dialogue, the name of the character speaking should appear in front of, and set off by a colon from, every block of dialogue.

To create a storyboard from a script, on the Script Werx menu, select Storyboard.