cohabiting Windows and OS/2 printer driver download

Gerald Carter gcarter at
Tue Mar 13 17:42:31 GMT 2001

On Tue, 13 Mar 2001 11:26:52 Jim McDonough wrote:
> >> OS/2 uses a DosPrintQGetInfo call, and gets its info
> >> in a PRQINFO_3 struct, like windows.  The driver file itself
> >> has to be in the PRINTDRV share on the server.  So, like,
> >> NT/95, if the OS/2 driver has the same name (on OS/2,
> >> the pszDriverName field of PRQINFO_3 is parsed as <driver file
> >> name>.<device name>, where <device name> can be blank), the
> >> driver download should work fine.
> >
> >So it shounds like you are ok now?  Am I right?
> Mostly.    If I read the docs right,  NT and 95 just 
> simply can't have two drivers with different names.  Period.  
> Right?  Does Imprints actually solve this?  Or am I 
> totally misunderstanding this...?

Basically, that is correct.  Have you looked at 
What happens is that a Windows NT x86 driver must be installed 
first.  When you add a driver for another OS, the Windows 
NT drivername is used for storing (remember that it has already 
been associated with the printer).

I think you've got the idea already, so apologies for any 
redundancy here.

> And there's a minor bug in the download on OS/2, but I'll 
> chase that down.  It takes two shots to download a driver and 
> create the object on OS/2. The first time, it downloads the 
> driver, but OS/2 gives an error saying the driver isn't 
> available.  The second time, it works.  I've just got to
> find out what's different from an OS/2 server that keeps 
> this from happening.

Good luck :-)

Cheers, jerry
   /\  Gerald (Jerry) Carter                     Professional Services
 \/  VA Linux Systems   gcarter at       SAMBA Team          jerry at                     jerry at

       "...a hundred billion castaways looking for a home."
                                - Sting "Message in a Bottle" ( 1979 )

More information about the samba-technical mailing list