summaryrefslogtreecommitdiff
path: root/doc/faq.html
diff options
context:
space:
mode:
authoreinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2006-09-20 05:08:49 +0000
committereinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2006-09-20 05:08:49 +0000
commit7047263496292fb8295533256ade7c987126a120 (patch)
tree43ae2818dac6dfcc51c665859d2b26bbd448a827 /doc/faq.html
parent32b7fc6468fc3aed808b8c32ac73a66e69676891 (diff)
Updated documentation for 1.1
git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@121 4979c152-3d1c-0410-bac9-87ea11338e46
Diffstat (limited to 'doc/faq.html')
-rwxr-xr-xdoc/faq.html19
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/faq.html b/doc/faq.html
index 80e68a2d..12da05dc 100755
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -1,4 +1,23 @@
<ul>
+<li><h4>Printing to a Printer from a Windows Server</h4><p>
+There are several obstacles to printing from a web appliction that was written
+for Linux or UNIX in Windows.
+These include:</p><ul>
+<li>Lack of Postscript support in the printing subsystem. To resolve this, you
+ must install Ghostscript and Gsview. The latter package provides a utility
+ called gsprint that will allow you to print Postscript on your Windows
+ printer.</li>
+<li>The fact that most Windows software, including gsprint, tends to print
+ output that will cause the web server to crash. The winprint.bat included
+ with this distribution corrects this problem. To use the winprint.bat
+ solution, configure your printers in your ledger-smb.conf as
+ "winprint.bat printer-name." If you omit the printer name, the default
+ printer will be used.</li>
+<li>Windows does not allow you to set up system printers that all users can
+ access. Thus the web server often doesn't have access to the printers you
+ have set up. To correct this issue, follow the steps at
+ <a href="http://support.microsoft.com/kb/q184291/">
+ http://support.microsoft.com/kb/q184291/</a>.</li></ul></li>
<p><li><h4>Error on converting from SQL-Ledger:
ERROR: column "chart_id" contains null values</h4>
SQL-Ledger does not enforce a NOT NULL constraint on the chart_id field in the