Submitted by Dave Brooks on Sat, 07/01/2017 - 13:16
Hint: it had nothing to do with the database
I started up the RPM Remote Print Manager® (RPM) user interface one morning, and instead of the usual list of queues and jobs, I saw this instead:
Submitted by Dave Brooks on Thu, 06/29/2017 - 12:42
Introduction
A number of years ago we decided to host the database for RPM Remote Print Manager® (RPM) in an external process. If for whatever reason we had a database problem, we didn't want to affect print job processing.
Naturally, we wanted to use some method of communication which was lightweight and reliable. We considered using the network like we did with the user interface (UI), but decided against that as the UI conversation can get very busy when there are a lot of jobs coming and processing. It seemed like a good plan to keep those two channels separated.
Submitted by Dave Brooks on Tue, 06/27/2017 - 16:24
One of the changes we added recently in RPM Remote Print Manager® (RPM) was to make your print jobs launch faster.
Whenever you receive a print job from the network, of course the aim is to process that job as soon as possible, and I believe we have been doing that all along. However, there are many other situations which result in jobs needing printing right away. We did it before, but now we do it more proactively, I believe to good result.
Submitted by Leroy Powell on Fri, 09/16/2016 - 16:00
I fielded a call today from a potential new customer who had been using another product to convert ASA Carriage Control files, commonly found in older Fortran-based systems, for printing to a Windows-based printer. Our application, RPM Remote Print Manager, has been able to do this conversion for many years. The legacy program, called Uniprint, was registered on a computer that recently crashed and recovering Uniprint's files and moving them to a new computer failed because the software needed t
Submitted by Leroy Powell on Thu, 09/15/2016 - 12:42
I have Windows 10 on my office computer, and I awoke this morning to find a new Windows version had been installed last night. I now have Windows 10 version 1607 OS build 14393.105, so that must be the one installed. Most people using our software, RPM Remote Print Manager, use it for receiving print jobs via the LPR/LPD protocol on port 515. If the Windows LPD Print Service feature is installed (and running), it conflicts with RPM's LPD functionality and prevents RPM from receiving print jobs on port 515.
Submitted by Dave Brooks on Sat, 05/07/2016 - 11:16
A customer told us recently that if they knew we did customization on our print server product, RPM Remote Print Manager, their search for a specific PDF solution would have gone more quickly. This page gives an overview of the problems we have solved for customers since 2010.
Submitted by Dave Brooks on Tue, 03/08/2016 - 12:16
USAIG provides aircraft insurance worldwide and maintains a huge network of underwriters and field offices. They rely on RPM to automatically email invoices, reports and worksheets generated by Redwood Software's Report2Web product. This should be of interest to anyone who prints and mails documents.
Submitted by Dave Brooks on Tue, 12/22/2015 - 15:50
Cosmo Corporation already had a sophisticated IT system but needed to add features to PDF documents they were creating daily. These documents were in English and Chinese. Cosmo contracted with Brooks to customize their RPM product, which satisfied their needs and boosted performance.
Submitted by Dave Brooks on Tue, 10/27/2015 - 11:27
Applied Data Consultants (ADC) created a software system that works with auto dealership management software, to manage dispatch and delivery. We talked about our integration with the ADC software in this blog post. In the following I'd like to describe how we used existing features in RPM Remote Print Manager® (RPM) without modification to investigate exactly what we needed to do to facilitate this integration with a new dealership management system, and then deliver a working solution which was replicated at other sites.
Submitted by Dave Brooks on Fri, 10/09/2015 - 15:51
I learned something important recently, just in time for the company’s twentieth anniversary.
I was listening to a recorded customer interview regarding a case study. The customer, a federal law enforcement agency (which of course we can’t identify), was describing how they sent print jobs from their mainframe to our RPM Remote Print Manager® (RPM), which converted the print jobs to PDFs and routed the documents to users in various ways.
Pages
Newsletter signup