wine printer
basti...@googlemail.com
print" succesfull, but when i start it, it says that no supported
printer was found. I've configured my Canon printer under Linux
(Ubuntu 7.10). I think wine doesn't "transport" the linux printer
configuration. How can i fix this? Is there any way to configure a
"wine printer"?
Thanks in common!!!
Bamm
If you're using KDE like I do, then here's a fix involving two steps.
If you're not using KDE, then ask around if there is something similar
for your desktop environment. So here goes:
Step 1:
In the file WIN.INI found in ~/.wine/drive_c/windows/ add the
following lines:
[devices]
KDE Print System=WINEPS.DRV,KDE:
Wine PostScript Driver=WINEPS.DRV,LPT1:
[windows]
device=KDE Print System,WINEPS.DRV,KDE:
device=Wine PostScript Driver,WINEPS.DRV,LPT1:
Step 2:
Copy the code below into a file called "printing.reg". Then in a
terminal run
"wine regedit" without the quotes. When Registry Editor opens, import
the
file "printing.reg" that you just saved. Close all wine programs, then
type
"wineboot" in a terminal, and you're all set.
REGEDIT4
[HKEY_CURRENT_USER\Software\Wine\Printing]
[HKEY_CURRENT_USER\Software\Wine\Printing\Spooler]
"KDE:"="|kprinter --stdin"
"LPT1:"="|lpr"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print
\Environments]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments
\Windows NT x86]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments
\Windows NT x86\Drivers]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments
\Windows NT x86\Drivers\Version-3]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments
\Windows NT x86\Drivers\Version-3\KDE Print System]
"Configuration File"="wineps.drv"
"Data File"="wineps.drv"
"Dependent Files"=hex(7):77,69,6e,65,70,73,2e,64,72,76,00,00
"Driver"="wineps.drv"
"Manufacturer"="Wine"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments
\Windows NT x86\Drivers\Version-3\Wine PostScript Driver]
"Configuration File"="wineps.drv"
"Data File"="wineps.drv"
"Dependent Files"=hex(7):77,69,6e,65,70,73,2e,64,72,76,00,00
"Driver"="wineps.drv"
"Manufacturer"="Wine"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers
\KDE Print System]
"Attributes"=dword:00000000
"Default Devmode"=""
"Name"="KDE Print System"
"Port"="KDE:"
"Print Processor"="WinPrint"
"Printer Driver"="KDE Print System"
"Priority"=dword:00000000
"Start Time"=dword:00000000
"Status"=dword:00000000
"Until Time"=dword:00000000
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers
\Wine PostScript Driver]
"Attributes"=dword:00000000
"Default Devmode"=""
"Name"="Wine PostScript Driver"
"Port"="LPT1:"
"Print Processor"="WinPrint"
"Printer Driver"="Wine PostScript Driver"
"Priority"=dword:00000000
"Start Time"=dword:00000000
"Status"=dword:00000000
"Until Time"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion
\Ports]
"COM1:"="9600,n,8,1"
"COM2:"="9600,n,8,1"
"COM3:"="9600,n,8,1"
"COM4:"="9600,n,8,1"
"FILE:"="9600,n,8,1"
"LPT1:"="9600,n,8,1"
"LPT2:"="9600,n,8,1"
"LPT3:"="9600,n,8,1"
basti...@googlemail.com
has an fix for gnome, otherwise I'm going to use kde.
I've heard that crossover is good for office applications, so it
should support printers, does anybody use crossover and could tell me
if it works?
Bamm
with HKEY_LOCAL_MACHINE should not wrap. If you copy and paste the
code into your editor please check for wrapping and fix it manually
before importing it.
I have also used crossover and printing works at least for me. However
I prefer wine because it is updated more often.
Duane Clark
I am not sure what you mean by "transport" a printer. Do you mean it is
not showing up in the print dialog? If you run "wine notepad", and
select the print dialog, does the printer show up there?
Did you install a binary Wine package, or did you compile it yourself?
What Wine version? Are you printing (in Linux) using CUPS?
Wine should automatically find printers if you are using CUPS, and there
is no configuration to do.
Bamm
I understand bastianb's predicament because I went through the same
problems, and my above reply is the result of a lot of trial and error
to get printing to work in Wine. My experience is that although
printing in wine notepad works, installed applications do not
necessarily "see" the printer unless it is in the wine registry and
win.ini files. It is frustrating to see an app complaining that it
cannot continue because no printer is installed, even though you can
print in Linux and wine notepad.
Unfortunately the solution I came up with was KDE-centric, and I do
hope someone with sufficient Gnome experience can post something that
works with Gnome and/or other desktop environments.
Bamm
Duane Clark
Wine "should" create the correct registry/win.ini entries by itself.
Typically in a case like this, if printing is not working, I would
suggest renaming the .wine directory to something like .wine.old, and
allowing Wine to regenerate a complete fresh .wine, and see if that
fixes printing. If that doesn't, then we should find out why not, and
perhaps file a bug.
It is worth noting that for me with a current wine, neither the builtin
notepad nor the builtin wordpad will actually print anything. In fact,
notepad actually crashes if I try to print. But other Windows apps print
just fine.
basti...@googlemail.com
> Typically in a case like this, if printing is not working, I would
> suggest renaming the .wine directory to something like .wine.old, and
> allowing Wine to regenerate a complete fresh .wine, and see if that
> fixes printing. If that doesn't, then we should find out why not, and
> perhaps file a bug.
>
> It is worth noting that for me with a current wine, neither the builtin
> notepad nor the builtin wordpad will actually print anything. In fact,
> notepad actually crashes if I try to print. But other Windows apps print
> just fine.
Hi again, I am using a pre-compiled version of wine (0.9.51).
I tried using kde with your how-to. Now I am able to print with some
applications! But it doesn't work with the program I need... I think
it's that "cd label print" just supports canon printers, so maybe it
doesn't detect my "canon as an canon", because it's another driver(?)
(in german treiber)...
I'll hang on it...
basti...@googlemail.com
> I tried using kde with your how-to. Now I am able to print with some
> applications! But it doesn't work with the program I need... I think
> it's that "cd label print" just supports canon printers, so maybe it
> doesn't detect my "canon as an canon", because it's another driver(?)
> (in german treiber)...
> I'll hang on it...
*edit: I'm using cups
Duane Clark
If this software installs its own canon print driver and uses that, or
is otherwise attempting to access the printer directly, then it is
unlikely to work in Wine. Does the program actually say that it only
works with Canon printers? I guess this program came with the printer?
In which case, this might be the case. Canon might be deliberately
preventing the use of the sofware with other printers.
If it is merely detecting available features on the printer, then maybe
Wine just lacks the correct reporting of printer features.
Unfortunately, determining this probably would require someone with a
copy of the software and good Wine debugging skills.
jhan...@gmail.com
> I tried using kde with your how-to. Now I am able to print with some
> applications! But it doesn't work with the program I need... I think
> it's that "cd label print" just supports canon printers, so maybe it
> doesn't detect my "canon as an canon", because it's another driver(?)
> (in german treiber)...
> I'll hang on it...
gLabels has CD templates:
http://glabels.sourceforge.net
basti...@googlemail.com
I tried to install the windows canon drivers but it failed. The next
thing I'll try is to use my whole Windows registry and windows folder
under wine(just a try, i think it'll fail^^)
@jhansonix: I tried glabels and I think it's a nice program, but I'm
not able to print out CD-Labels because maybe the Linux Canon drivers
aren't that good (I want to print CD labels !On an printable CD! I'm
going to look for an extended canon driver which supports the feature
i need.
Thanks for your help!!!
Duane Clark
> Yes, I think Duana Clark is right.-.-
> I tried to install the windows canon drivers but it failed. The next
> thing I'll try is to use my whole Windows registry and windows folder
> under wine(just a try, i think it'll fail^^)
The Windows driver will not work no matter how you install it. The
program must print with "standard" Windows printing, and then it should
work in Wine.
That is, if in Windows the software can print to any printer (not just
the Canon), then it should work in Wine. If the program is deliberately
written so that it will only work on the Canon printer, then it will
most likely not work in Wine.
Michael and Nicole Freeman
> Wine should automatically find printers if you are using CUPS, and there
> is no configuration to do.
This doesn't seem to be true on my system. I'm using Wine 0.9.53 from
the WineHQ.org Debian repository on Debian Lenny AMD64. I'm also running
CUPS 1.3.5 with two installed printers (one local, and one SMB
networked). Anytime I want to print from a program running on Wine (even
wine notepad), it says, "Before you can perform printer-related tasks
such as page setup or printing a document, you need to install a
printer. Please install one and retry."
I have also tried the suggestion of renaming my .wine file and letting
Wine re-create a new one, and I still get the same result. None of my
CUPS printers are apparently recognized.
As there are no configurations that can be done for CUPS printers, I
haven't found any config file workarounds for this problem anywhere.
My wife has some items she needs to be able to print from a
Windows-based CD for a class she's taking. The program on the CD runs,
but again complains about not having an installed printer.
Any suggestions?
Mike Freeman
mike [at] freeman-studio [dot] com
Michael and Nicole Freeman
KDE-centric won't work for me, either. But any help would be very much
appreciated!
Bamm
> KDE-centric won't work for me, either. But any help would be very much
> appreciated!
Try the demo version of crossover. If printing works, then just find
the registry entries that crossover uses, then export them and import
them into wine. Once you get it to work in Wine, then you can
uninstall crossover. That was how I found the KDE solution I posted.
If you get it to work, please share your solution here. I am
interested in finding out a Gnome counterpart to my solution.
Michael and Nicole Freeman
Well, I've tried Crossover, which can see my printers just fine. I
checked the win.ini and registry files, and copied over anything related
to printing or my specific print drivers. It didn't work. Maybe I'm not
understanding how this all works?
A side note, I liked the little extras that Crossover has. I don't like
that it doesn't run some software that Wine (sort of) does.
I just wish this stuff would just work as advertised! It's incredibly
annoying, time consuming/wasting, and prohibiting me from doing what I
need to do.
Bamm
> checked the win.ini and registry files, and copied over anything related
> to printing or my specific print drivers. It didn't work. Maybe I'm not
> understanding how this all works?
Maybe you missed some entries? Try this on a clean .wine profile (with
nothing installed):
1) Export the entire Wine registry as wine.reg
2) Export the entire Crossover registry as cx.reg
3) Import the cx.reg into Wine.
4) Import the wine.reg into Wine.
5) Copy win.ini from crossover to Wine (but backup your original).
This will give you the original Wine registry with additional entries
from Crossover. I did it this way just in case there are conflicting
entries in Crossover and Wine.
Now install your program and test print. If it works, then try to
isolate which entries are needed. Remove those which are not needed.
Do this until you end up with a small reg file that is all you need to
enable printing on a clean .wine profile.
> A side note, I liked the little extras that Crossover has. I don't like
> that it doesn't run some software that Wine (sort of) does.
That's because Crossover is based on Wine 0.9.34 which is quite old.
However the tweaks they did were very good.
> I just wish this stuff would just work as advertised! It's incredibly
> annoying, time consuming/wasting, and prohibiting me from doing what I
> need to do.
They do. Wine and Crossover are among the most honest software I have
encountered in telling which works and which doesn't. There is even an
extensive Applications Database which is updated by users, ranking
apps as gold, silver, bronze, or even garbage depending on how they
work in Wine. As for Crossover, they have an official list of
supported applications, all of which are guaranteed to work. If you
use Crossover for other apps not in their supported list, you're on
your own.
Regards,
Bamm
David Rowell
Crossover and Wine 0.9.53 - in Crossover the display is clear, printing
can be configured and it will print very nicely. Setting the margins
for the printer is not transparent but possible (see my old note in
WineHq application database).
I ran diff on the reg files for both:
** user and userdef differences don't seem to apply to printing
** there are enormous differences between the printing related keys in
system.reg as expected. Far too many seemingly significant differences
to to be useful for simple modification.
From an ethics standpoint I'm not comfortable in using Crossover's reg
file in Wine or in copying the results of the search. Suffice it to say
there is a lot of work to be done here!
Dave Rowell
Bamm wrote:
...
Bamm
> ** user and userdef differences don't seem to apply to printing
> ** there are enormous differences between the printing related keys in
> system.reg as expected. Far too many seemingly significant differences
> to to be useful for simple modification.
I understand. I spent an entire weekend trimming down the huge diff to
get just what is needed. It has helped me a lot afterwards, as I only
have to import a small reg file into any new wine profile I create.
But in your case, since you are after only a single app, it might not
be worth the trouble.
> From an ethics standpoint I'm not comfortable in using Crossover's reg
> file in Wine or in copying the results of the search. Suffice it to say
> there is a lot of work to be done here!
If that is the case, then it might be best to just buy a copy of
Crossover. It's a good way to thank them for getting printing to work
in your favorite app. :)
David Rowell
display PAF reasonably well and it would let me print. I can't find my
post on WineAPDB so I can't tell what version of Wine or Ubuntu that was.
If I wanted to use PAF as a primary program I would buy Crossover but I
only use it to make files for my Palm and to try to help other folks.
Dave Rowell
Robert M. Riches Jr.
Hi David,
I'd be happy to help to the extent I can. At your option,
please email me and/or post a bit of detail so I can try to
find your AppDB comment that may have the information you're
looking for. I may have the old comments archived.
--
Robert Riches
spamt...@verizon.net
(Yes, that is one of my email addresses.)
David Rowell
> On 2008-01-29, David Rowell <djrp...@cfl.rr.com> wrote:
>> Funny thing is that at one time I coaxed an old version of Wine to
>> display PAF reasonably well and it would let me print. I can't find my
>> post on WineAPDB so I can't tell what version of Wine or Ubuntu that was.
>>
>> If I wanted to use PAF as a primary program I would buy Crossover but I
>> only use it to make files for my Palm and to try to help other folks.
>
> Hi David,
>
> I'd be happy to help to the extent I can. At your option,
> please email me and/or post a bit of detail so I can try to
> find your AppDB comment that may have the information you're
> looking for. I may have the old comments archived.
>
I think I have found the old comment at WineHQ, dated 19 Jun 2006. On
Ubuntu 6.06 with Wine 0.9.15 my comment says that it printed BUT had to
have usp10.dll from Windoze XP as native and a bit of fiddling with fonts.
Gramps has improved by a couple of quantum leaps since then tho!
Thanks for making me look!
Dave Rowell