samba - Aug 2003 - Different Printer Model for different Arch

Here is a problem I posted to HP's forum on the DesignJet drivers for the
755cm, but something tells me someone clever here has already hacked
around this or a similar printer and might know how to solve my problem:

---
When installing drivers on a remote Samba server (ie. Windows NT
emulation, and perhaps real NT as well), you are able to install printer
drivers for a printer for various architectures. The requirement, however,
is that the model string for each driver be the same. However, HP has "HP
DesignJet 755CM (3198B)" for the Windows 9x driver, and "HP DesignJet
755CM(3198B)by HP" for the Windows 2000 model string. I hacked the
OEMSETUP.INF to make the Win2k model string identical to the '9x model
string, but apparently this broke the paper sources in your driver. I
removed the driver, restored the stock Win2k model string (with the "by
HP") and the driver started working again.

The problem, then, that remains unresolved is that HP has improperly
labeled one of their drivers. To work properly in an NT environment, one
needs to be changed and re-released.
---

Anyone have a workaround -- I'm not holding my breath for a driver
re-write.

---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  |  | Ryan Novosielski - Jr. UNIX Systems Admin
|$&| |__| |  | |__/ | \| _|  | novosirj@umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630

I have used an XP Pro machine to add the other drivers, which seems to
work just fine.
-Chris

On Mon, 2003-08-11 at 19:17, Ryan Novosielski wrote:
> Here is a problem I posted to HP's forum on the DesignJet drivers for
the
> 755cm, but something tells me someone clever here has already hacked
> around this or a similar printer and might know how to solve my problem:
> 
> ---
> When installing drivers on a remote Samba server (ie. Windows NT
> emulation, and perhaps real NT as well), you are able to install printer
> drivers for a printer for various architectures. The requirement, however,
> is that the model string for each driver be the same. However, HP has
"HP
> DesignJet 755CM (3198B)" for the Windows 9x driver, and "HP
DesignJet
> 755CM(3198B)by HP" for the Windows 2000 model string. I hacked the
> OEMSETUP.INF to make the Win2k model string identical to the '9x model
> string, but apparently this broke the paper sources in your driver. I
> removed the driver, restored the stock Win2k model string (with the
"by
> HP") and the driver started working again.
> 
> The problem, then, that remains unresolved is that HP has improperly
> labeled one of their drivers. To work properly in an NT environment, one
> needs to be changed and re-released.
> ---
> 
> Anyone have a workaround -- I'm not holding my breath for a driver
> re-write.
> 
> ---- _  _ _  _ ___  _  _  _
> |Y#| |  | |\/| |  \ |\ |  |  | Ryan Novosielski - Jr. UNIX Systems Admin
> |$&| |__| |  | |__/ | \| _|  | novosirj@umdnj.edu - 973/972.0922
(2-0922)
> \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630
--

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 11 Aug 2003, Ryan Novosielski wrote:
> When installing drivers on a remote Samba server (ie. Windows NT
> emulation, and perhaps real NT as well), you are able to install printer
> drivers for a printer for various architectures. The requirement,
> however, is that the model string for each driver be the same. However,
> HP has "HP DesignJet 755CM (3198B)" for the Windows 9x driver,
and "HP
> DesignJet 755CM(3198B)by HP" for the Windows 2000 model string. I
hacked
> the OEMSETUP.INF to make the Win2k model string identical to the '9x
> model string, but apparently this broke the paper sources in your
> driver. I removed the driver, restored the stock Win2k model string
> (with the "by HP") and the driver started working again.
> 
> The problem, then, that remains unresolved is that HP has improperly
> labeled one of their drivers. To work properly in an NT environment, one
> needs to be changed and re-released.
Same thing here.  This is a design limitation in the printing system.
there is a single namespace for drivers across all architectures. :-(





cheers, jerry
 ----------------------------------------------------------------------
 Hewlett-Packard            ------------------------- http://www.hp.com
 SAMBA Team                 ---------------------- http://www.samba.org
 GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
 "You can never go home again, Oatman, but I guess you can shop
there."
                            --John Cusack - "Grosse Point Blank"
(1997)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE/OLO2IR7qMdg1EfYRAjU2AJ9XFJYXJeWtIJ2yvMM/YQTeafnv1QCfaQ08
NxeEfjkUnYquCeKuos6J4cc=ixiZ
-----END PGP SIGNATURE-----