Design and content by 4-Tech-Engineering © 2021
Unix, DOS, Windows 7/8/10,Server and Android are trademarks under CopyRight of the relevant companies.
K1: AutoPrint does not print when running as Windows service. As a desktop application everything works fine.
K2: Windows10 Update bug in March 2021 (empty pages, memory and/or GDI resources lack, application crashes)
The following messages may show up during the setup procedure or while in active operation modus. You may also check the AutoPrint.log file for recent error messages.
This message is issued if a printer that was successfully set up before, is no more accessable while AutoPrint in active modus, especially when running as Windows service.
These or similar messages may show up on newly installed Windows systems and with AutoPrint versions up to 7.01 published until Nov 2017.
Although AutoPrint comes with its own FreeImage32.dll, it needs the system MSVCR100.dll to properly handle it.
The MSVCR100.dll is part of the Microsoft Visual C++ 2010 Redistributable Package (x86) which is normally installed and registered by many other applications, which usually live on a today’s Windows computer.
You may close the gap by downloading and installing the MS Visual C++ 2010 Redistributable Package (x86) through the related Microsoft support link: http://www.microsoft.com/en-au/download/details.aspx?id=5555
Some users reported related issues, especially when AutoPrint is installed on Windows Vista, 7 or higher. The problem is usually caused by the fact that the designated printer is not accessible for the owner of the service. By default the service owner is a local system account with no printers. This gap can be closed easily by the following steps.
(1) If AutoPrint Professional is yet running as Windows service: first Stop service and then...
(2) Uninstall the service through the AutoPrint General setup tab.
(3) Now re-install the service: before klicking the Install service button enter
the Account name and Password of local Windows user, who owns all necessary
privileges to use the designated printer and to modify its driver settings. You may double-check the privileges on the printer properties side (Windows).
The later change of the service owner settings may alternatively be performed by using the standard Windows Services management console.
K2: Windows10 Update bug in March 2021 (empty pages, system overload conditions, app crashes)
Mid of March 2021 a few users reported sudden issues after AutoPrint has been operating smoothly for years. Typical observations were:
- sudden “printing” of blank pages without any error messages
- continuously increasing, very high memory loads during printing, lack of GDI resources
- system error messages, exception error messages
- freezing of AutoPrint GUI, crashing of the application or running service
- only one printer is affected, while print channels with other printers seem to work correctly
- the situations can be “repaired” temporarily by restarting the application or the service
Until now (March-20-2021) the affected users reported, that the problems started over-night after a regular Windows OS update.
Meanwhile there are already first public news, that refer to a system bug transported with the March 2021 OS update.
Watch for and apply the latest OS patches from Microsoft.
In a 1st-aid-action 4-Tech-Engineering has added a resource-monitoring modul to a new AutoPrint version release 7.07. As a workaround it continuously watches the system resource demand during the printing process and stops the application, before any severe side-effects may develop. Finally the application will restart automatically.
Recommendation for PDF-printouts
For printing PDF-files there are two alternative options in the print channel layout setup: a direct print and an intermediate bitmap method. Although the direct method is the fastest one, it can happen that the resources-overflow is triggered by complex or huge multi-page document files. Here you may better activate the intermediate bitmap processing option, which is set as a default now.