Bill Medland wrote:> On May 2, 2004 09:06 am, Duane Clark wrote: > >>Bill Medland wrote: >> >>>On May 1, 2004 08:50 am, Duane Clark wrote: > > > Thanks for the continued help, Duane > > >>> > Bill Medland wrote: >>> >>>>>(Yes, I know 20031118 is a little old) >>>>> >>>>>Anyone any ideas what is going on here or any simple tests I can do? >>>>> >>>>>I am trying to get our company's software running on Red Hat Enterprise >>>>>Linux 3 Update 1. >>>>> >>>>>I am using the wine-20031118-1rh8winehq.i686.rpm >>>>> >>>>>I am printing to a SMB printer elsewhere on the computer. >>>>>I can print the test page from the printconfgui >>>>>I can print a text file from the command line (lp /etc/passwd) >>>> >>>>Wine expects to print with lpr and the corresponding syntax. Can you >>>>print on the command line with lpr instead of lp? >>> >>>Yes >> >>Then the next test is that Wine expects to be able to print a postscipt >>file via lpr, so the next thing to try is printing a postscript file via >>lpr. > > > Yep. /usr/share/apps/kdeprint/testprint.ps > > >>Hmm, and is printconfgui something other than CUPS, I take it? > > > Sorry; I guess I was being lazy. No. RHEL uses CUPS (and they appear to have > dropped LPRng so I can't try that which is my usual next step). By > printconfgui I meant redhat-config-printer-gui (which I believe used to be > called something like printconfgui or something close back in the old RH6 > days) > > >>You might want to post the contents of /etc/printcap, windows/win.ini, >>and the sections of ~/.wine/system.reg that begin with: >>[System\\CurrentControlSet\\Control\\Print\\Printers > > ...Hmm, everything there looks fine. I take it the printer does show up in the Wine printer dialog as "lp", and you are selecting "lp"? What happens when you try to print? Does the printer activity light flash? In general, for remote queues, you should be setting the queue type to "raw" regardless of the actual printer type. I don't really know for sure whether this is the case for SMB queues, especially since you say that you can print Postscript files ok from the command line. It might be worth trying a raw queue, assuming the lp one is not.
On May 3, 2004 11:05 am, Duane Clark wrote:> Bill Medland wrote: > > On May 2, 2004 09:06 am, Duane Clark wrote: > >>Bill Medland wrote: > >>>On May 1, 2004 08:50 am, Duane Clark wrote: > > > > Thanks for the continued help, Duane > > > >>> > Bill Medland wrote: > >>>>> > >>>>>(Yes, I know 20031118 is a little old) > >>>>> > >>>>>Anyone any ideas what is going on here or any simple tests I can do? > >>>>> > >>>>>I am trying to get our company's software running on Red Hat > >>>>> Enterprise Linux 3 Update 1. > >>>>> > >>>>>I am using the wine-20031118-1rh8winehq.i686.rpm > >>>>> > >>>>>I am printing to a SMB printer elsewhere on the computer. > >>>>>I can print the test page from the printconfgui > >>>>>I can print a text file from the command line (lp /etc/passwd) > >>>> > >>>>Wine expects to print with lpr and the corresponding syntax. Can you > >>>>print on the command line with lpr instead of lp? > >>> > >>>Yes > >> > >>Then the next test is that Wine expects to be able to print a postscipt > >>file via lpr, so the next thing to try is printing a postscript file via > >>lpr. > > > > Yep. /usr/share/apps/kdeprint/testprint.ps > > > >>Hmm, and is printconfgui something other than CUPS, I take it? > > > > Sorry; I guess I was being lazy. No. RHEL uses CUPS (and they appear to > > have dropped LPRng so I can't try that which is my usual next step). By > > printconfgui I meant redhat-config-printer-gui (which I believe used to > > be called something like printconfgui or something close back in the old > > RH6 days) > > > >>You might want to post the contents of /etc/printcap, windows/win.ini, > >>and the sections of ~/.wine/system.reg that begin with: > >>[System\\CurrentControlSet\\Control\\Print\\Printers > > > > ... > > Hmm, everything there looks fine. I take it the printer does show up in > the Wine printer dialog as "lp", and you are selecting "lp"?I'll have to get back to you on that. (I am currently trying to get the freshly compiled Wine to run for me and it is being a pain)> > What happens when you try to print? Does the printer activity light flash? > > In general, for remote queues, you should be setting the queue type to > "raw" regardless of the actual printer type. I don't really know for > sure whether this is the case for SMB queues, especially since you say > that you can print Postscript files ok from the command line. It might > be worth trying a raw queue, assuming the lp one is not. > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users-- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed
On May 3, 2004 11:05 am, Duane Clark wrote:> Bill Medland wrote: > > On May 2, 2004 09:06 am, Duane Clark wrote: > >>Bill Medland wrote: > >>>On May 1, 2004 08:50 am, Duane Clark wrote: > > > > Thanks for the continued help, Duane > >I don't think there is much you are going to be able to help me with here, Duane. Sounds like another basic incompatibility with RedHat Enterprise Level.> >>> > Bill Medland wrote: > >>>>> > >>>>>(Yes, I know 20031118 is a little old)(It happens with current source too, freshly compiled)> >>>>> > >>>>>Anyone any ideas what is going on here or any simple tests I can do? > >>>>> > >>>>>I am trying to get our company's software running on Red Hat > >>>>> Enterprise Linux 3 Update 1. > >>>>> > >>>>>I am using the wine-20031118-1rh8winehq.i686.rpm > >>>>> > >>>>>I am printing to a SMB printer elsewhere on the computer. > >>>>>I can print the test page from the printconfgui > >>>>>I can print a text file from the command line (lp /etc/passwd) > >>>> > >>>>Wine expects to print with lpr and the corresponding syntax. Can you > >>>>print on the command line with lpr instead of lp? > >>> > >>>Yes > >> > >>Then the next test is that Wine expects to be able to print a postscipt > >>file via lpr, so the next thing to try is printing a postscript file via > >>lpr. > > > > Yep. /usr/share/apps/kdeprint/testprint.ps > > > >>Hmm, and is printconfgui something other than CUPS, I take it? > > > > Sorry; I guess I was being lazy. No. RHEL uses CUPS (and they appear to > > have dropped LPRng so I can't try that which is my usual next step). By > > printconfgui I meant redhat-config-printer-gui (which I believe used to > > be called something like printconfgui or something close back in the old > > RH6 days) > > > >>You might want to post the contents of /etc/printcap, windows/win.ini, > >>and the sections of ~/.wine/system.reg that begin with: > >>[System\\CurrentControlSet\\Control\\Print\\Printers > > > > ... > > Hmm, everything there looks fine. I take it the printer does show up in > the Wine printer dialog as "lp", and you are selecting "lp"? > > What happens when you try to print? Does the printer activity light flash? > > In general, for remote queues, you should be setting the queue type to > "raw" regardless of the actual printer type. I don't really know for > sure whether this is the case for SMB queues, especially since you say > that you can print Postscript files ok from the command line. It might > be worth trying a raw queue, assuming the lp one is not.Basically: 1. If I modify Wine to create a temp file and then print the temp file, rather than all that file descriptor/pipe/fork stuff, and then print the file in the close job, it still fails. However I can print the file using exactly the same command from the command line. 2. I can print to the printer using the same scheme of pipe/for/dup/system in a small test program. I'll add it to the bug log.> _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users-- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed