Q: I try to install Factsmith, but I get a message about not being able to write a file or a permission error.
A: The most likely cause is that you've selected an installation directory that you do not have permission to modify. Most commonly, this results from an unpriviledged user trying to install to the default directory (usually C:\Program Files\Factsmith). Solution: Select an installation directory you have write access to, such as your documents folder, or run the installer as an administrator.

Q: I get a message saying the installer failed its integrity check when I run it.
A: The installer is corrupted, probably as a result of a download error. Re-download the installer and try again.

Q: How do I run Factsmith on Windows 98?
A: Factsmith requires the Microsoft .NET Framework. While newer versions of the .NET framework are no longer compatable with Windows 98, Factsmith will run fine on the original version of .NET 2.0 (the last version for Windows 98). Microsoft no longer offers this version for download, but you can find it archived on sites such as OldApps.com.

Q: What will happen if I don't actually read the license, just like most other users?
A: You will have agreed to terms of use that, for all you know, could require you to use the phrase "weasel tuxedo" at least once every minute in each constructive speech.

Q: Factsmith won't run - it shows the splash screen, but exits without ever showing the main window.
A: Three things could be to blame:

1. The INI file (the file that stores user preferences) is corrupted or incorrect. You can reset your settings by deleting the file Factsmith.ini in your Application Data directory (usually C:\Users\YOUR_USERNAME\AppData\Roaming\Factsmith; in Windows 2000 and XP, C:\Documents and Settings\YOUR_USERNAME\Application Data\Factsmith; in Windows 98 and ME, C:\WINDOWS\Profiles\YOUR_USERNAME\Application Data\Factsmith.) This may be a hidden folder depending on your operating system. Your settings will reset to the "factory default", including the root folder.
2. One (or more) styles are corrupted. Solution: You can fix the problem by reinstalling Factsmith, or if you know which style is causing problems, you should be able to fix the problem by deleting or moving the offending file. This problem shouldn't occur if you stick to the internal style editor for any style modifications, but manually editing the style files can easily corrupt them.
3. One (or more) plugins are corrupted. Solution: Unless you feel like monkeying around with plugin declarations, you'll probably need to reinstall Factsmith.

Q: Factsmith won't run at all - it gives me a ".NET Framework Initialization Error" (or something similar.)
A: You need the Microsoft .NET Framework. This is easily obtainable from the Microsoft website.

Q: Factsmith won't run at all - I have a 64-bit computer.
A: Some users have reported manifest errors on computers running certain 64-bit versions of Windows. Try moving, renaming, or deleting the file Factsmith.exe.manifest in the directory you installed Factsmith to (usually C:\Program Files\Factsmith). (On Windows XP, this may change the visual appearance somewhat, but Factsmith will run fine.)

Q: How do I edit an evidence card? (or section, or text)
A: In the standard EcoView evidence view, just double-click the item you want to edit. In the classic grid view, click the item and click Edit on the toolbar.

Q: How do I add images and fancy formatting to my evidence cards?
A: Right-clicking the evidence body in the Evidence Editor will bring up some advanced options, including images and formatting.

Q: How do I copy text from Google Books (or other images?)
A: Right-click the text box you want to paste the text into (for example, the evidence body) and select "Paste from Screen..." Click and drag to select the portion of the screen to copy. (You'll get better conversion quality if you zoom in first.)

Q: How do I underline parts of my sources?
A: In sources, you can turn underlining on and off with caret marks (^ symbols; usually Shift+6.) For example, if an author's credentials were "former director of the ^National Society of Experts^, Maryland Chapter" the text "National Society of Experts" would be underlined. Alternatively, if you consistently want certain parts of the source underlined (say, the date and author names) you can edit the styles to underline them (see the Style Guide.) Plain-text sources can use standard formatting codes (see the Formatting Code Reference.)

Q: I can't see the entries on the table of contents (usually in Microsoft Word).
A: In some versions of Word, the table of contents will only display if the document is in Print Layout view. Usually, however, this is a result of the fields not updating automatically. This is nothing to worry about; if you try to print the document, the table of contents will magically appear. (If you want to see them from the moment you open the document, you can turn on "Update Automatic Links at Open" in Word's options.)

Q: If I modify an exported brief with my word processor, the next time I open it (with the word processor), it looks funny. Is there any way to prevent this?
A: Due to the RTF-embedding technique used by the Word and ODT export plugins, some word processors will attempt to save the document as pure RTF - which doesn't always work correctly. This is easily avoided by clicking Save As instead of Save (on the File menu of your word processor) and manually setting the file type to the correct option.

Q: How do I export to PDF?
A: Factsmith does not currently support PDF exports natively, but you can easily create them using other software. The free office suite LibreOffice can export documents straight to PDF; export your brief to Word or ODT, open it up in LibreOffice, and use the PDF export tool to make a PDF of it.

Q: What is a "Factsmith export file (*.fsx)" (one of the options for exporting), and what can read them?
A: FSX files are a standard intermediate format that is read by the export plugins. When you export a brief, it is converted into FSX code which is passed to the export plugin. Factsmith also offers an option to export directly to FSX without passing it to a plugin; this is mostly used for debugging purposes, and it is unlikely you will ever need to use it.