Epson Artisan 810 issues - can scan and communicate but not print!

I gave that a try and had the exact same result. Literally the instant it sends the document to the printer the printer queue on the computer pops up that error and the printer itself almost immediately says it is canceling the print. The printer is quite clearly receiving information because it acts as if it is about to start printing something (makes the whole getting ready to print noises, acts as if it is about to load some paper) before the cancellation occurs. I am printing fine from a laptop running Windows 7 (wireless connection to the router) and a desktop running Windows XP (wired connection to the router).

Unfortunately I have seen other peoples posts and none of the things they try seem to be working.

I truly don't understand what else I can try to do; I can scan documents, I can check the ink level, when I try to print a test page it actually prints something - a group of different colored parallelograms with lines in the middle and underneath it says "LWO298 QP110A29". I don't know if that is what the test page is supposed to say or not but something at least is being printed.

I've tried uninstalling using the original installer and then reinstalling and it doesn't make a difference.

John, I deleted the printer and deleted those folders and reinstalled the printer using the printer menu. When I tried the apple software update it said my software was up to date and didn't offer an option to get updated print drivers. I tried printing again and the same thing happened.

Syd,

I am trying to print from the Macbook to the Artisan entirely over a wireless network. The Macbook has not been plugged directly into the printer or to the router at any point in this. I did try what you suggested, resetting the printing system, and as earlier it did not offer any software updates when I looked for one. I tried printing again and the same result.

I dug around some more directories and found some more files with the epson name in there and deleted those and then attempted to reinstall using the printer setup page, and then again tried a software update and again it didn't find any new drivers, and of course the same printing error occurred again.

It sure appears that the MacOS is holding onto drivers somewhere that I cannot discover because when I reinstall the printer it takes it all of 3-4 seconds to install, and when I try to do the software update it is not finding any new drivers anywhere.

Syd, I agree that there seems to be something specifically corrupted about the printer driver itself, however, but is there another way to remove drivers?

Should I try uninstalling everything and attempting a USB installation to see if prints that way?

I have deleted every Epson file I can find and reinstalled using the control panel and the epson website drivers and it still is happening.

I'll give this a try next, but I spent an hour on the phone with Epson yesterday and they couldn't figure it out. I am on the phone w/Apple tech support and they are going to elevate me to a new tech support level because the first guy cannot figure it out.

I have tried installing wirelessly only using the Bonjour and IP options and both keep giving me the same error. I have reset the printing system, deleted files and directories off the HD, re-downloaded the newest drivers, run the apple update to get any downloads, and no matter what I do I still get the same error when I print.

I can scan fine, I can see the ink levels, but I just can't PRINT w/o this message appearing. I have two Windows computers that print fine, one of which is a wireless laptop, so I feel there must be something specific in the MacOS for me that is causing this repeated error that is unrelated to the driver installation itself, because everyone else seems to be able to solve this problem by doing these trouble shooting steps.

I tried plugging in the printer via USB to the Macbook and when I try to add a printer the USB option doesn't even show up, just the Bonjour and TCPIP option.

What could cause that? And I am still on hold w/apple technical support as apparently no one has any ideas...