cohabiting Windows and OS/2 printer driver download

[Jim McDonough]

>> 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...?

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.

Thanks,
JIm

----------------------------
Jim McDonough
Linux Technology Center
IBM Boulder

Notes: Jim McDonough/Boulder/IBM @ IBMUS
VNET: JMCD at IBMUSM54
Internet: jmcd at us.ibm.com

Phone: (303) 924-5822
T/L: 263-5822


Gerald Carter <gcarter at valinux.com> on 03/13/2001 10:22:50 AM

To:   Jim McDonough/Boulder/IBM at IBMUS
cc:   samba-technical at samba.org
Subject:  Re: cohabiting Windows and OS/2 printer driver download



On Mon, 12 Mar 2001 16:55:57 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?

> You just have to manually copy the files from the
> OS/2 driver into whatever directory you share as PRINTDRV.
> Problem is, just like NT/95, the driver often has a different
> name...  Oh well...
>
> Also, driver upload doesn't work from OS/2->NT, so you have
> to just manually copy the files.  The OS/2 client does the
> work searching in the PRINTDRV share.




Cheers, jerry
----------------------------------------------------------------------
   /\  Gerald (Jerry) Carter                     Professional Services
 \/    http://www.valinux.com/  VA Linux Systems   gcarter at valinux.com
       http://www.samba.org/       SAMBA Team          jerry at samba.org
       http://www.plainjoe.org/                     jerry at plainjoe.org

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