On March 30, [EMAIL PROTECTED] said:
> Why is it that smbd tries to open the directory as a regular file?
This would be the point at which I say "works for me!" and fail to
understand what's happening on your end. Sorry!
Cheers,
Waider.
--
[EMAIL PROTECTED] / Yes, it /is/ very personal of me.
"
I am sorry for the late reply - have been doing other things, and
trying to figure this out a bit further.
On Wed, Mar 19, 2003 at 05:30:18PM +, Ronan Waide wrote:
> On March 19, [EMAIL PROTECTED] said:
> > >
> > >
> > > adddriver "Windows NT x86" "HP LaserJet 5Si/5Si MX
> > > PS":pscript5.
On March 19, [EMAIL PROTECTED] said:
> On March 19, [EMAIL PROTECTED] said:
> >
> > I put all the files in the print share at (\\dev\print$\w32x86). The
> > files are from Windows XP Professional SP1. The files are, as
> > reported by the printer test page:
> >
> > pscript.ntf
> > pscript.hlp
>
On March 19, [EMAIL PROTECTED] said:
>
> Firstly, you first said that it expects the files in the w32x86/win40
> directories.
Oh, hmm, you're right. Sorry. The files go into the w32x86/win40
directories, but not into the 2/ or 0/ subdirectories of those. My
mistake.
Cheers,
Waider.
--
[EMAIL P
Hi there.
Thank you for your reply. Please read my comments below:
On Wed, Mar 19, 2003 at 10:43:14AM +, Ronan Waide wrote:
>
> The adddriver rpc expects to find the files in \\dev\print$; it will
> move them to the w32x86 or win40 directory as appropriate.
Firstly, you first sai
1.ppd
> pscript5.dll
>
> I issued the following command from rpcclient:
>
> adddriver "Windows NT x86" "HP LaserJet 5Si/5Si MX
> PS":pscript5.dll:hplj5si1.ppd:ps5ui.dll:pscript.hlp::pscript.ntf
The adddriver rpc expects to find the files in \\dev\print$; it will
I am sending this again here, as I did not get any reply for some
time, and haven't yet figured it out by myself:
Hi there.
Leaving the idea of not providing driver files on the server for a
while (only specifying the name, as in my previous thread here), I was
trying the SPOOLSS adddrive
On March 12, [EMAIL PROTECTED] said:
> adddriver "Windows NT x86" "HP LaserJet 5Si/5Si MX
> PS":pscript5.dll:hplj5si1.ppd:ps5ui.dll:pscript.hlp::pscript.ntf
Don't leave unused parameters blank. use the word "NULL" instead.
Cheers,
Waider.
--
[EMAIL PROTECTED] / Yes, it /is/ very personal of me.
Hi there.
Leaving the idea of not providing driver files on the server for a
while (only specifying the name, as in my previous thread here), I was
trying the SPOOLSS adddriver RPC from rpcclient with Samba.
The server runs Samba 3.0 post-HEAD from CVS checked out on the 3rd of
March. rpcclient
