- #3 - QT/Snipper incompatibility revealed November 14, 1997 (Mac)
- #2 - Missing characters on printouts from older laser printers August 5, 1997 (Windows)
- #1 - Incomplete printer driver installation may crash Solo April 10, 1997 (Windows)
#3 - QT/Snipper incompatibility revealed
November 14, 1997 (Mac)
Axon Technical Support has identified a compatibility problem when running Solo under Mac OS 8.0 with the shareware utility QT/Snipper (v 1.0) installed.
Solo freezes or crashes after the second or third consecutive use of any of the attribute pop-ups ( i.e. fill color, pen color or pen width) in the Page Editor view.
The problem has been determined to be caused by the way the QT/Snipper utility patches certain Mac Toolbox traps. Advanced Software (the maker of QT/Snipper), has been notified of the problem.
Remove or "hide" the QT/Snipper Control Panel, restart the computer.
#2 - Missing characters on printouts from older laser printers
August 5, 1997 (Windows)
Some users of older PCL printers have reported problems with characters missing from printed output.
Some first or last characters in labels or table cells fail to print, although they are correctly displayed on the screen, when printing to older LaserJet, or Lexmark Optra, printers using the standard printer drivers supplied with Windows 95.
The problem is due to these printers only supporting "character" clipping when imaging text instead of the more precise "stroke" clipping available on most newer laser printers.
Axon is currently testing a work-around for this limitation which will be made available with the next release of the software. In the short term, the only solution is to upgrade to a newer printer.
#1 - Incomplete printer driver installation may crash Solo
April 10, 1997 (Windows)
After having installed Solo under Windows 95, some users have reported numerous crashes when performing simple operations, particularly when placing and working with chart templates.
Solo crashes frequently or every time a user attempts to place a chart template or while editing chart data.
The problem has been traced to calls to the currently selected printer driver which cause the processor's floating point error handling flags to be cleared. Subsequent floating point errors (e.g. overflow, divide by zero) causes a hard crash instead of being reported back to the calling software. Solo normally looks for and handles these situations without problem.
Axon support has not been able to determine the reason why this problem manifests itself on some machines, but evidence suggests that it has something to do with how the particular machines hard disk was configured either at the factory, or by an IT department. Specifically, we suspect machines which systems were installed from a standard "disk image" file, and where the default printers Properties dialog was never explicitly opened.
In the Printers folder, open the Properties dialog by right-mouse clicking on the default printer driver icon. Close the dialog. Restart the computer.