So for the remainder of the publishing info, we have to execute win32 code.
I don't see a real way around it.  What I've checked in so far covers
pretty much all of the DsSpooler stuff that win2k would normally fill in.

To get things like bin names and paper sizes, we can't really rely on a
DEVMODE being set, because that only represents one configuration, not the
complete set (unless I'm totally misunderstanding the DEVMODE, which is
possible).  What I'm proposing is a small win32 app like the attached one
that takes a printer UNC name and writes back the DsDriver key values, then
tells the server to publish it (via setprinter info level 7).

This example just sets the printBinNames value, but it does work correctly.

(See attached file: prtinfo.c)

Whaddaya think?

----------------------------
Jim McDonough
IBM Linux Technology Center
Samba Team
6 Minuteman Drive
Scarborough, ME 04074
USA

[EMAIL PROTECTED]
[EMAIL PROTECTED]

Phone: (207) 885-5565
IBM tie-line: 776-9984

Attachment: prtinfo.c
Description: Binary data

Reply via email to