 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Applications / Virtual PC / March 2006virtual PC version 7 will not print to Epson photo RX 620
I am hoping that one of your readers might be able to help me with a very difficult problem which I am having with Virtual PC on my AlPB. The problem is that I can't print to my new Epson RX620 printer from Virtual PC. I used to be able to do so when I first got the printer, but now I can only print to my old Epson C60. This problem first occurred after I ran the Mac OSX Combo Updater 10.3.9 again, which I had to do to cure a problem with the PB taking a very long time to go to sleep. Prior to that, I could print to the RX620 or to the C60, either from the Mac OS or from Windows XP running in Virtual PC 7. Now, I can print to both printers from the Mac OS, but only to the C60 from VPC. Now, even though the RX620 shows up in the PC printer list normally, as the default printer, when I try to print something, the Printer window in the Printer Setup Utility in the Mac OS pops open, the print job seems to process normally, and then suddenly, the job is 'stopped.' No amount of trying has gotten me past this point. So far, I have tried all of the following (and then some!)... - deleted the Epson printer driver and all printer preferences, and reinstalled the drivers. - deleted Virtual PC and reinstalled it. - checked and rechecked every setting, to no avail. - worked my way through the entire VPC and Windows XP Printer Troubleshooting Guide (it ended by saying it couldn't solve my problem). - spoke with Epson support (they were unable to help). - consulted Microsoft's VPC support site, but no help. - asked my Mac-savvy friend, but he couldn't find the problem either. - asked the store were I bought both products, but they couldn't help. I don't know who to turn to, and I am at my wit's end with this. I am self-employed, and I depend on this printer for my work. I am not a computer whiz, and I really don't know what to try next. I am so hoping that someone out there can guide me through this conundrum. Thank you for your help, Best regards, Marlene Swider, Kitchener, Ontario. How are you setting the printer up? Are you installing the Windows drivers within VPC, or are you installing the Mac drivers and making use of VM Additions Printing? I'd recommend the latter... much less work. 1) Make sure that the printer prints from the Mac side and is selected as the default printer. 2) In Windows, confirm that you have the additions installed (if the drive image came with VPC, they should be). 3) Select the VM Additions printer and make that the default within Windows. 4) Print from a Windows application... it should work. And FYI, you are entitled to one free support call and the PSS team for Virtual PC is actually pretty good. The print job spools on the Windows side and sends the print job to the Mac side for processing. If the job shows up on the Mac side as 'stopped' and you are not able to restart the job, it usually means that VPC does not recognize the printer as a 'printer'. This happens a lot with all-in-one printers. The way to resolve thsi issue is to set up an 'emulated' printer. The steps to do thsi are included in the knowledgebase article below: http://support.microsoft.com/default.aspx?scid=kb;en-us;824366 Make sure you use the Epson AP-3260 ESC/P2 printer drivers I would argue with your assessment of HOW VM additions printing works... it's not that VPC doesn't recognize the printer as a printer. All VPC does is pass a PDF/PS file over the wall for the Mac to print. If it fails to print on the Mac side, it's not because of how the printer is "seen"... because at that point, it's all Mac based. It's far more likely to either be some sort of permissions problem with the file, or perhaps the PDF/PS that VPC passed over the wall is malformed. And, of course, the Mac has to be able to print to said printer to begin with... if there are no Mac drivers, VM Additions Printing won't work. Not quite. In my experience, when printing from VPC to an all-in-one printer using VM Additions, the print job spools fine and passes over to the Mac side....OK so far. However, the print status on the Mac side shows 'job stopped'. All attempts to start the job fail. Setting up an emulated printer using the Epson AP-3260 print drive and bypassing the VM Additions print driver succeeds. So, the only logical conclusion would be the way VM Additions packages the job (no, uninstalling and re-installing VM Additions does not fix it). The Mac side does not know what to do with it and stops the job from printing. Nothing to do with permissions. And 10-15 print jobs in a row from at least 4 different applications cannot ALL be malformed. No, I think you misunderstand me... there may be something about the way that the PS file is constructed that causes it to fail on SOME printers, or again, a permissions issue... not that the file is occasionally formed incorrectly. The effect is the same, but I doubt that it has anything to do with whether VPC recognizes the printer, as VPC is not involved after the file is passed to the Mac. >And 10-15 print jobs in >a row from at least 4 different applications cannot ALL be malformed. I was referring here to several different files in several different formats from several different applications in Windows (Word, Excel, Powerpoint, Notepad, Adobe) My conclusion: there could not be anything wrong with the way all of these documents are formed. If it was permissions, why would an emulated print driver work when VM Additions and the installing the printer's own drivers directly into Windows would BOTH fail with exactly the same symptoms and results? > [B]Not quite. > [quoted text clipped - 3 lines] > worked!!! > Fred Jagg - fred jaggi |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.