I think the workaround will not work. I can�t predict which user on which machine will use which printer. Our users have in most case max. two networkprinters connected - for our luck long physikal ways prevent the "need" to connect to more printers. We have created a small script which erases all printerrelated registry-entries and files on the client. A user or admin can run this script and the client is clean for a new printer-installation. This way we work around the naming-problem on the client. (The users *theoretical* know which printers cannot be installed at the same time). Of course this works not on the printserver :)).
If there is no other solution, we have to "fight" another skirmish with HP ... maybe we can convince them to take more care when naming there files.......... ... on the other hand maybe someone is happy to implement the needed variables to the samba-core?? :) The moto would be: Power is nothing without control Simo: Thanks for your answer. Have a nice day. Ralf > -----Urspr�ngliche Nachricht----- > Von: Simo Sorce [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 28. November 2002 11:34 > An: K�tzler, Ralf > Cc: [EMAIL PROTECTED] > Betreff: Re: 2nd attempt: Modify location of printerdriverfiles > > > That would change nearly nothnig, because the printer drivers will be > copyed in the same structure on the client and there you will find the > same naming problem. > > It is a known windows problem (just faces some day ago with > drivers for > 2 HP laser printers on a windows 98 :-/) > > If the Printer Manufacturer tell you so she is both right an wrong. > > Right it is an OS problem, A windows OS problem. > > Wrong the manufacter must know this issue and try not to make drivers > with overlapping names. > > > However you may try just a workaround. If any of your clients will use > only one printer, you may try some symlink + macro expansion tricks to > use different directories, but it may not work or corrupt badly your > printer settings and prnting related tdb file, so at your own risk: > > - you may use a macro expansion on the print$ share path and > then make a > number of directories that match that macro expansion > > eg: > path = /usr/share/samba/%G/drivers > > and have a pool of printers per group or other parameter. > > Simo. >
