Invalidity dossier
US 5687301
Field correction of application specific printer driver problems
Current assignee: Hewlett Packard Development Co LP
Added 9/24/2026, 1:20:52 AM
Active provider: DeepSeek · deepseek-flash
Patent summary
Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.
Patent Overview — US5687301A
Title: Field correction of application specific printer driver problems
Patent number: US5687301A
Application number: US08/528,589
Filing date / priority date: 1995-09-15
Publication (grant) date: 1997-11-11
Inventor(s): DeVerl N. Stokes; Terry P. Mahoney
Original assignee: Hewlett Packard Co. (listed current assignee: Hewlett Packard Development Co LP)
Legal status (as listed): Expired – Lifetime; anticipated expiration 2015-09-15
Purpose: The patent addresses correcting printer-driver problems discovered in the field — that is, after the driver has been released. Because printer drivers typically hardcode special handling for known problematic applications, drivers released earlier cannot accommodate newly discovered "special need" applications. The invention provides a method and system for changing a function of a printer driver for a particular application.
Plain-language scope (from the supplied text): In a system of a host computer (e.g., a personal computer) and a connected printer, a password-protected utility called "AppFlag" is run. A user selects an application, and the utility verifies it is an executable, locates its internal module name and version resource, and displays that information. The user sets flags (check boxes) representing known problems; changes are saved only when "Apply" is pressed. The flag and associated application information are stored in an AppFlag database on a permanent storage device. Flags described include: No Abort Procedure; 300 DPI only; report printing technology as raster; No Font Engine Rotation; support bandinfo; ignore model change; no scaling support; use logical port name; no manual feed first; and swap paper dimensions. On power-up, local memory is scanned for an entry for the application; if found, a driver function is changed to accommodate it. The driver accesses the external database in addition to a hardcoded list of known applications.
Source: https://patents.google.com/patent/[US5687301](/patent/US5687301)/en
What the excerpt does not establish: It does not provide the full claims, complete specification, or drawings; it omits portions of text (noted in the source). It does not establish the accuracy of the listed assignees or legal status (Google states these are assumptions, not legal conclusions). It does not establish validity, enforceability, prior art, or litigation history. Detailed implementation of the SetupAppFlags() function and the data structure definitions are referenced but not fully reproduced in the excerpt.
Generated 10/1/2026, 9:31:29 PM
Cases on file (0)
Specific litigation cases in our database that name US patent 5687301. The free-form analysis below may also discuss cases beyond this list.
No cases on file mention this patent. Upload a CSV or add a case manually in Admin → Manage litigation cases.
Litigation summary
Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.
Proceedings on file (0)
All PTAB activity →AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.
No PTAB proceedings on file. This patent has not been challenged via IPR, PGR, or CBM. The absence is itself a signal — well-asserted patents eventually attract IPRs. The LLM analysis below may surface filings the ODP feed hasn’t indexed yet.
PTAB challenges
AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.
Assignment history
Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.
Prior art
Earlier patents, publications, and products that may anticipate or render the claims unpatentable.
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Extensions
Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.