|
General | PageScript 32 | PageScript | Mail2
General questions
| Every time I try to download something from my private download section, my browser tried to download an executable file. What can I do ? |
| Simply click on th links provided. Don't right click and choose "Save ..." because you'll try to save the CGI script related to this link. |
PageScript 32 questions
| Is PageScript 32 compatible with Clipper ? |
| No. PageScript 32, as its name states, is compatible only with 32 bits Windows programming languages. |
| Which files do I have to redistribute along with my application ? |
| The only file that needs to be redistributed is PSCRIPT.DLL. Make sure you always have the latest version of the .DLL. |
| Which files do I have to include in my xHarbour projects when using PageScript 32 ? |
| Two files must be included : TPScript.prg and DllCall.c. The first one contains all PageScript 32's classes and procedures and the second one is necessary to call the functions stored in the .DLL. |
| Which files do I have to include in my Delphi projects when using PageScript 32 ? |
| The only file you need to include is TPageScript.pas. It contains all PageScript 32's classes and procedures. |
| Which files do I have to include in my Xbase++ projects when using PageScript 32 ? |
| The only file you need to include is TPScript.prg. It contains all PageScript 32's classes and procedures. |
| Is PageScript 32 compatible with Windows Vista ? |
| Yes, PageScript 32 is compatible with the 32 bits version of Windows Vista. |
PageScript for Clipper questions
| Is PageScript for Clipper compatible with Windows Vista ? |
| Starting with version 4.2.0, PageScript for Clipper supports Microsoft's latest operating system; Windows Vista. |
| When I print from my Clipper program, the print job starts more than 1 minute later. But when I quit my program, the print job starts immediately. What's wrong with PageScript ? |
Nothing's wrong with PageScript. The problem comes from the Clipper program itself. You MUST include some kind of Time Slice mechanism to your Clipper program in order to reduce the CPU utilization of your program. This is especialy true when running a NT based version of Windows (NT, 2000, XP, server 2003). When no time slice mechanism is used, the Clipper program uses more than 99% of the CPU, leaving almost no CPU time for PageScript to spool its print jobs. When your Clipper program includes a Time Slice mechanism, it shouldn't take more than 3-5% of the CPU while in idle more, therfore leaving up to 97% of the CPU for other tasks running in the background. This is true for PageScript but it is also true for all other tasks, running in the background.
There are ways to make your Clipper program, CPU friendly. Here are a few that we're aware of :
1) Use Nanforum's FT_OnIdle() / FT_IAmIdle()
2) Use OSLib's OL_AutoYield()
3) Use Blinker's 7 BliCpuRel() function
4) Use PatchA
By linking or using any of these functions, your Clipper program won't be hogging the CPU anymore. PageScript's spooler will have enough CPU time to spool its print jobs and your entire system will benefit from this CPU time. |
| I can't seem to get PageScript working. It always report a 999 error. |
This error means that your Clipper program can't communicate with the printer spooler. Here are some things to check out :
a) Make sure the print spooler is loaded and idle (small PS icon in the system tray).
b) Make sure you linked the correct library. PageScript comes with a library for Clipper 5.3 and another library for Clipper 5.0 through 5.2e. Check also the library version. It must match the spooler version (i.e. Lib = 3.0.x Spooler = 3.0.x).
c) Try changing the link order. For unknown reasons, PageScript may refuse to work correctly if linked before, or after some third party libraries.
d) If you specify the spool path in PSInit(), make sure the print spooler points to the same path. PScript.ini must be set accordingly.
e) If you don't specify a spool path in PSInit(), leave blank the "[Path] Spool" entry in PScript.ini.
f) If using the "Automatic Spool Path Detection System", PageScript uses an hidden file named PSPath.ini, located at the root of drive C:\. The Spool entry must point to a valid directory (the same pointed by the print spooler). |
| Can I use PageScript without changing my existing Clipper code ? |
| Starting with PageScript 4, you'll be able to use PageScript with almost no code change if you use the Raw print mode or the Emulation mode. If you want to take advantage of all PageScript's capabilities, then you'll have to rewrite all your print routines. |
| Which files are required when redistributing PageScript on customers computers ? |
PSCRIPT.EXE and PSCRIPT.INI only. Places those two files in a folder (Normaly PSCRIPT), on drive C:\ (or another drive). You may create the necessary folders from within an installation procedure, such as InstallShield or from your own Clipper program. We suggest the following folder structure :
[C:\]
[PSCRIPT]
PSCRIPT.EXE
PSCRIPT.INI
[SPOOL] |
| Can PageScript's print spooler be installed on a network drive (as a print server) ? |
| No. PageScript must be installed on every computer using your Clipper program. PageScript builds its printers list from the devices installed on the computer on which it's running and keeps some informations about those devices in a printer definition file. Again, all those settings are specific to the computer on which PageScript is running. |
| Can PageScript calculate the length of a string using the selected print unit ? |
| No. PageScript is a deferred printing system. That means it can't report the size of a given string because when you are sending print commands, by calling PSxx() functions, PageScript records the calls in a spool file. When PSEndDoc() is called, the spool file is closed and sent to the print spooler. It's only at this stage that PageScript is able to calculate the placement of strings, based on the current unit of mesurement. |
| Is PageScript compatible with Windows Vista ? |
| Yes, starting from version 4.2.0, PageScript is compatible with the 32 bits version of Windows Vista. |
| Can I use PageScript with Clipper prior to version 5.0 ? |
| No. PageScript works only with Clipper version 5.0 and up. Clipper 5.2e and Clipper 5.3b are recommended. |
Mail2 questions
| May I send emails with Mail2 ? |
| No. Mail2 is a in-house only messaging system. Its purpose is to give you a small, yet very powerful multi-media messaging system for you and your co-workers. |
| Under what format are kept the messages ? |
| Messages are kept in a file format used on computers world wide: the .DBF format. The body of the text is stored in a .FPT file. The joined files, are stored in temporary files that indicates the type of document (image, sound or video). |
| I am a programmer. May I insert my own messages into these files ? |
| No. Mail2 use standard files, but the techniques used for storing the data are optimized to reduce the disk space used. It would not be possible to insert messages directly into these files without risking data corruption. |
| How can I insert my own messages into Mail2 files ? |
Programs other than Mail2 can send messages with the help of the post office program. The designers of Mail2 created a tool for software developpers so that they can use the post office program to send messages to Mail2 users.
With this SDK, available as an application program for Windows 9x, Me, NT, XP, 2000 and 2003 or as a service for Windows NT, 2000, XP and 2003, other programmers can easily add new messages to Mail2's post office database files. To find out more about the SDK, please contact the sales department at salesdep@abeelabs.com. |
|
This section provides a list of frequently asked questions. Before asking for technical support, please take a few minutes to review this section, it may contains the answer you're looking for. |
