Software tip: GAGEpack printer issue

David ShattuckShortly after GAGEpack 9.0 was released last fall, we began to get calls from users who were having trouble printing labels after upgrading to the new version. Naturally, our GAGEpack development team grew concerned, and launched an investigation to track down the problem and resolve it. Our findings surprised us.

After talking with users who were experiencing these problems and doing a hefty bit of testing internally, we were eventually able to isolate the trouble to those systems that were using all three of these components: GAGEpack 9.0, Windows XP, and Brother printers. Any user running a different version of GAGEpack, a different version of Windows, or a different type of printer would have no label problems at all.

This was an extremely peculiar conclusion, because we knew that each of those three components will work correctly on its own or combined with just one of the others. If GAGEpack 9.0 works fine with Windows XP and it works fine with a Brother printer, why do we see problems when GAGEpack 9.0 tries to work with both Windows XP and a Brother printer at the same time? It was quite a mystery.  Our tech sleuths were all over it.

As it turns out, the trouble lies with the drivers that Brother has published to enable their printers to communicate with Windows XP. These drivers were last updated in March 2002. In software terms, they are ancient. This was not a problem in GAGEpack 8.5 because every version of GAGEpack released since the early 1990s had been written in Microsoft’s VB6 programming language. However, VB6 has been officially unsupported as a software development language since March 2008. GAGEpack 9.0 is written in the new, which was extremely young and not commonly used the last time the Brother Windows XP printer drivers were updated.

Windows XP is going to be around until at least April 2014, and we hope that Brother will update its antiquated drivers before then. In the meantime, if you are a GAGEpack 9.0 user struggling with this problem, we offer two solutions. The first option is to upgrade your operating system to a newer version of Windows. Windows Vista and Windows 7 both work great with the label printing. If you decide to go that route, I recommend Windows 7, for reasons far too numerous to discuss here. The second option is to replace your label printer. During our testing on this issue, we purchased a Dymo printer to replace the Brother p-touch that we’ve been using for many years. The new Dymo hasn’t given us any trouble.

Based on these findings, we’re recommending non-Brother printers to our customers who may be in the market for replacement printers.

Software tip: GAGEmail – The secret treat included with GAGEpack

David ShattuckWhen I do a product demonstration of GAGEpack and I arrive at the segment where I talk about GAGEmail, I often find myself introducing it by saying, “I wish more people knew about this.” In fact, it is not uncommon for me to come across veteran GAGEpack users who are unaware that they have a program like GAGEmail at their disposal.

GAGEmail is a tiny program designed to run in the background and continuously scan GAGEpack databases to watch for upcoming gage servicing events. When it finds an event, it will e-mail a reminder to the person responsible for that gage. This proactive approach to calibration reminders makes GAGEmail unique amongGAGEpack‘s notification methods. Normally, users must remember to remind themselves of upcoming events by checking their reports or filtered gage lists. With GAGEmail, the reminder is entirely automated.

In addition to being automated, these reminders are also quite flexible. The user can specify which types of events trigger e-mails, how far in advance of the event they should be sent, who should receive them, and what they should say.

In order to use GAGEmail, customers simply need to install it by contacting a PQ support representative.

As always, I am available to offer assistance with setting up GAGEmail. You can call me at 800-777-5060, e-mail me at, or leave questions for me below.

Software tip: Concurrent-user licensing or not concurrent-user licensing? That is the question!

David ShattuckLast year we deployed a new licensing option for all three of our major software applications. Up until that point, our customers licensed the software on a “per-computer” basis, meaning every computer terminal being used to run the program required its own unique license. As the software industry shifted towards enterprise and network licensing options, we received a steady stream of requests for more flexible “roaming” licenses. Thus, the concurrent-user license was born.

A concurrent-user license allows an organization to install our software on an unlimited number of computers on the same network, giving them the freedom to put these applications into the hands of any/all of their employees without the cost and hassle of managing individual licenses. The only restriction in the concurrent model is the number of people who can access the program simultaneously; when the sixth person attempts to log into a five-user license, they will get a message saying that the server is full.

We still offer the per-computer licenses, but the concurrent-user licenses have been steadily growing in popularity since they were launched.  Consequently, I routinely find myself answering the question “Should I switch to a concurrent-user license?”  My response is always the same:  “It depends.”

The value of a concurrent-user license versus the traditional per-computer license depends heavily on what sort of traffic to the program is anticipated. If you expect infrequent and fairly brief access from many computer terminals, a concurrent-user license would meet your needs for a fraction of what it would cost to license all of those terminals individually. On the other hand, if you have only a few terminals that need near-constant access to the program, it would likely be more cost effective to invest in per-computer licenses. In both scenarios, both licensing options could be applied to grant the required access, but selecting the appropriate license would save a pretty penny.

Please feel free to contact your account representative if you have questions about your specific application or contact me via e-mail at We would be happy to discuss different licensing options with you.