Hi folks, tracked down a problem I mentioned last week with printing. When you use the rpcclient adddriver command as follows:
adddriver "Windows NT x86" name:NULL:NULL:NULL:NULL:NULL:NULL:NULL you get a NT_STATUS_UNSUCCESSFUL error, which further investigation reveals to be caused by an Access Denied error upstream. Further investigation of /that/ reveals that get_correct_cversion in printing/nt_printing.c is attempting to open the W32X86 directory as a file. This is, as far as I can tell, because the second field in the second parameter above is the driver file; setting it to NULL is somehow causing this problem. Setting the driver file to a valid printer driver file cures the problem. I don't know if this is a bug or just misuse on my part of the rpcclient command :) Cheers, Waider. -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. Some people just don't know which side of the good/evil thing to side with, despite the obvious "fun now, pay later" advantages of the evil side for those of us who need instant gratification.
