We released a new version of APFill 5.8, an ink and toner coverage calculation tool.
In this version:
Continue reading ‘New version of APFill 5.8’ »
TimeToPhoto 2.7 has been released.
APFill 5.6 allows users to use MS Excel files as templates for processing the results of document coverage measurements.
Continue reading ‘Using MS Excel templates in APFill for processing results.’ »
A new version of Universal Desktop Ruler 3.6, a program for measuring on-screen objects, has been released
Continue reading ‘New version of Universal Desktop Ruler 3.6’ »
Once the main backup file has been created, APBackup enables you to save it to 3 additional folders (on a local disk, on a portable drive and in a network location) and upload it to an FTP server (in this case, the server acts as the fourth additional folder).
You can specify unique file names using a date stamp and the nesting depth of the backup files for each of the additional folders (3+FTP folder). This allows you to implement flexible backup storage scenarios – for instance, a current backup file and monthly backups.
Continue reading ‘Additional backup folders.’ »
In Windows, the maximum length of a file name is defined as MAX_PATH = 260 characters. In the APBackup copy mode, however, the resulting length of an archived file can exceed this limit – and this can cause a problem. Continue reading ‘The problem of long paths in backups (Copy mode in APBackup).’ »
APBackup allows you to run backup tasks using both the built-in Zip64 archiver and the majority of external archivers. To configure an external archiver for use with APBackup, you need to create/edit an external archiver configuration file (*.EMC). The APBackup distribution package contains configuration files for the most popular tools: WinRar, WinZip, Arj, 7-Zip, etc. However, you can add a custom configuration file for any other archiver. The process is described in detail in the program documentation (where WinRar is used as an example).
When a task is executed using an external archiver, APBackup creates a command line to start it using the information from the corresponding configuration file, creates a process for executing this command line and waits for the process to end. In this case, an archiving task is considered completed if the return code of the created process is 0 and the program finds a newly-created volume after the external archiver has finished working. If the external archiver returns a code different from 0, it means that the task has been completed with an error. Unfortunately, APBackup cannot identify what’s causing the error, as it is related to a different process it has no access to. So what can you do to find the source of the problem?