![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Printing, Faxing and Scanning with Vista A forum for using printers, scanners and fx with Windows Vista. (microsoft.public.windows.vista.print_fax_scan) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I have the above printer and am trying to use it on RC1. It uses the Lexmark
510 driver to run. I initially had problems installing the driver, but finally was able to do so. When I plug in the printer via the USB cable, Windows recongnizes it. The printer shows up in the Printer section of control panel as well. However, when I try to print a test page, I get a communication error saying Windows cannot communicate with the printer. It worked fine in Windows XP, so I don't think it is a cable issue per se. Does anyone have a workaround for this or can point me in some direction where I can resolve this? Thanks for any help. |
|
|||
|
Same problem as i do..i have a z605...dumping the printer for a different
company isn't a sollution..hopefully someone has an answer for you... "Sir Myles" wrote: I have the above printer and am trying to use it on RC1. It uses the Lexmark 510 driver to run. I initially had problems installing the driver, but finally was able to do so. When I plug in the printer via the USB cable, Windows recongnizes it. The printer shows up in the Printer section of control panel as well. However, when I try to print a test page, I get a communication error saying Windows cannot communicate with the printer. It worked fine in Windows XP, so I don't think it is a cable issue per se. Does anyone have a workaround for this or can point me in some direction where I can resolve this? Thanks for any help. |