wrote:
> The files required to remotely connect a driver from one machine to
> another should be under
> C:\Windows\System32\spool\drivers\
Thank you for helping me and others out answering this printer driver
archival question for drivers that are getting harder and harder to obtain
on the fly.
The 64-bit system is brand new so it only has the default 64-bit Windows 10
printers, plus the HP 2100TN printer driver uploaded from the hour-long
printer "windows update".
- Fax
- Microsoft Print to PDF
- Microsoft XPS Document Writer
- HP LasterJet 2100 PCL6
In C:\Windows\System32\spool\drivers\ are four directories
- color
- IA64
- W32X86
- x64
Here is a screenshot of the above:
http://www.bild.me/bild.php?file=6986137Clipboard02.jpg
The "IA64" directory is empty, and the HP Laserjet 2100 is not a color
printer, so I assume the driver I need to archive is somewhere inside
either of the two remaining folders, each of which contains 3 and 4 folders
but some are empty such that they each contain only these two populated
folders:
- 3
- PCC
Where the files inside each PCC directory are all "cab" files, but inside
the W32X86 "3" folder are the following 4 files, all dated 9/29/2017:
- mxdwdrv.dll
- PrintConfig.dll
- unishare.gpd
- unishare-pipelineconfig.xml
And inside the X64 "3" folder are far more files of mostly the same date
but a couple of which start with HP:
- HPLJ21P6.BUD
- HPLJ21P6.GPD
Here is a screenshot of that X64 "3" directory, sorted by file type:
http://www.bild.me/bild.php?file=4489340Clipboard03.jpg
The HP BUD file is abinary but the HP GPD file is text, which confirms in
its header that it's related to the HP printer driver that the temporary
Microsoft Windows update process must have installed.
*%% HP LaserJet 2100 Series PCL
*%% Copyright 1998 - 1999, Microsoft Corp.
*%% All Rights Reserved.
*%% Model Specific Global Entries
*GPDFileName: "HPLJ21P6.GPD"
*ModelName: "HP LaserJet 2100 PCL6"
*MaxCopies: 32767
*PrintRate: 10
*PrintRatePPM: 10
*PrintRateUnit: PPM
etc.
From that, do you think this is the directory to archive?
C:\Windows\System32\spool\drivers\X64\3\
> aka \\hostname\print$
I couldn't get that command to work, so I will ignore it for now.
> The added wrinkle is for variations between 64 and 32 bit machines
> (thankfully the old wrinkle of differences between intel/alpha/mips/ppc
> machines went away).
I am all 64 bit as far as I know (although I have no idea what the driver
was that Microsoft uploaded during that special manual printer-related
Windows Update when I tried to install the printer driver.
> You should be able to make use of the remote install by sharing the
> printer via networking, then the other machine will work out which
> driver files it needs and copy them for itself
I would rather just /save/ just the necessary printer drivers that the
special printer-setup Microsoft Update uploaded, which I could do if I knew
what to save to my backup media.
> With a bit of detective work you can do it all manually, copying the
> files like for like, running regsvr32 on the DLLs, it's a long time
> since I had to stoop to doing it that way ...
I'm not familiar with "regsvr32" but a quick search shows it's a way to
"register" DLLs using the command syntaqx:
regsvr32 /u myfile.dll
https://www.lifewire.com/regsvr32-what-it-is-how-to-register-dlls-2623958
> Or you might find the relevant C:\Windows\INF\OEM*.?nf files
> a manual process that involves hunting down any related files
That directory has almost a thousand items, only one of which starts with
hp:
- hpsamd.inf
This HP inf text file is 202 lines long, where the header indicates it's
related to HP in some manner.
;Copyright (c) 2004-2011 Hewlett-Packard Development Company, L.P. ALL
RIGHTS RESERVED.
;HP Confidential.
[version]
Signature="$WINDOWS NT$"
etc.
I'm not sure what I would do with this file though.