1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Windows Vista and my quest to install a printer!

Discussion in 'General Software' started by newtekie1, May 26, 2008.

  1. newtekie1

    newtekie1 Semi-Retired Folder

    Joined:
    Nov 22, 2005
    Messages:
    19,801 (6.20/day)
    Thanks Received:
    5,919
    Ok, first of all I would like to say that I have actually managed to get everything working, after spending the better part of my 3 day weekend working one it, so this isn't a request for help. I started dealing with this problem Friday evening, and just now got it solved Sunday evening! This is just me venting my frustration and possible making a post that might help others with similar issues. Anyway, on to my story:

    I installed Vista Business Premium x64 on my main computer(specs to the left). It is the only computer I expected to have Vista installed on. Everything seemed to go smoothly, with the exception of me having a few older programs that would not install on a 64-bit OS, but downloading the latest version fixed the issue.

    Then I went to install my Lexmark X6150 All-in-one printer, which is actually connected to Rig 3, which is running Windows XP Professional(32bit). I download the Vista x64 driver from Lexmarks site, I install the printer, everything seems to go fine until I tried to print. BAM! "Problem communicating with the Printer" WTF!!!

    I go into Printer and sure enough the printer status is listed as "error". I go into the properties and everything looks normal. I try uninstalling the printer and installing it manuall, and this is where the real fun begins. I get the error that the operation could not be completed after finding the printer on the network and trying to connect to it. The error string is (0x0000000d). I google the string and see MANY people having the same problem.

    The first solution I came across was to map the printer to LPT2 using the net use command, then add the printer pointing it to the LPT2 port. It seemed to work! That was easy... Until I tried to print, Lexmark's drivers will not use an LPT port, the printer HAS to be connected to a USB port!:banghead:(Fuck you lexmark for making shitty drivers!:banghead:)

    More googling revealed that the problem is usually caused by the drivers being corrupted. So I spend an hour trying to clean up all the Lexmark's crap. Re-install of the drivers and same problem. So I say fuck it and re-install vista entirely. Doesn't work.

    The next solution seems to be to install a Vista driver on the XP machine, which doesn't make a whole lot of sense to me and I didn't think it would even work. However, for some reason it did. Even though it was a 64-bit driver for a completely different OS, when I manually updated the driver through Windows it took the Vista x64 driver and actually still worked. I could print from the XP machine just fine. I hop on the Vista machine, and no go though.:mad:

    So I just starting playing around, creating ports, pointing them at my XP machine's printer share, deleting ports, creating them, installing the printer, uninstalling the printer, and magically it seems to start working. Honestly, I completely lost track of what I did, and I was damn tired when I did it. It is now 1:30AM, I had been up since 6AM and I had to get up at 8AM to go up to Indiana Dunes State Park. I print a test page, it worked, I go to bed.

    I wake up the next morning. Try to print again, and NOTHING. FUCK!!!! Everything looks good on the Vista machine, so I head to the XP machine. It seems the print job from last night was stuck in the queue. A power cycle of the printer fixes that, and I print another test page, it works, I go to the State Park.

    When we got back in the afternoon I try to print again, and no go.:banghead: Same issue, the last print job is stuck in the printer queue. I tried disabling the print spooler and printing directly to the printer on both machine, didn't work. I try changing the print processor, and it didn't work.

    After some googling, I find out that this is also a common issue, and basically it boils down to the fact that Lexmark's 64-bit driver doesn't like to work with XP's Print Spooler, and even if it is diabled, it still screws up.:banghead:

    So I finally give up and install Vista x64 on Rig 3. I finally get it install, and map the printer just fine. Then I try to print from Rig 3 and it works. I walk into the other room and print from the remote Vista machine, and nothing.:banghead:

    Back to the same issue, any print job I send to the printer gets stuck in the queue until I power cycle the printer.

    I do some googling and find out that this is also a known issue of Lexmark's drivers.:banghead:(Again, fuck you Lexmark!) However, there is a simple known solution, switch the print processor from Lexamark's to WinPrint and switch the data type to RAW. I do this on both machines, and FINALLY both are working perfectly.

    I go to install the new shared printer on my other machines, all running XP, and the printers install, but for some reason only partially. When I try to go into their properties it says there is no driver installed. However, I can print to the printer, and everything prints normally, including pictures. I just can't adjust any settings(quality setting being the most important). I assume this is Lexmark's fault also, but I really don't have the will to research this damn issue any further. All my computers can print, and that is good enough for me right now.

    Sorry about the rant, but I just had to get it off my chest. Now off to figure out why my monitor on Rig 3 only wakes from sleep half the time(I love Vista SOOOOOO much!:banghead:)
    Crunching for Team TPU 50 Million points folded for TPU
  2. philbrown23

    philbrown23 New Member

    Joined:
    Dec 22, 2007
    Messages:
    1,231 (0.51/day)
    Thanks Received:
    147
    Location:
    vermont
    Had this same problem! I just quick and sai f it
  3. magibeg

    magibeg

    Joined:
    May 9, 2006
    Messages:
    2,000 (0.66/day)
    Thanks Received:
    203
    That looks like quite the time you were having. Really don't think its vista's fault so much as lexmark making crummy drivers.
  4. DaedalusHelios

    DaedalusHelios

    Joined:
    Feb 21, 2008
    Messages:
    4,920 (2.07/day)
    Thanks Received:
    812
    Location:
    Greensboro, NC, USA
    Lexmark is an all around shitty company. I have had 6 out of 6 Lexmark printers die on me. :(
  5. newtekie1

    newtekie1 Semi-Retired Folder

    Joined:
    Nov 22, 2005
    Messages:
    19,801 (6.20/day)
    Thanks Received:
    5,919
    It is really a combination of both. Actually, I think it is actually a problem with XP more than Vista. The Print Spooler on XP doesn't seem to like accepting jobs from Vista 64-bit. I think the problem is the mixing of 64 and 32 bit OSes. And through my googling I found that the issues I was having original(the 0x0000000d error) were a common problem with Vista and printers, HP printers seem to be having the same issue.

    I've been pretty happy with my Lexmark printer until now. I usually buy cheap printers, my last printer cost me $50 and it was a Lexmark, and yes it died after 4 years of use, but again it was only $50, I wasn't expecting quality. I've had plenty of HP printers die also. My current printer wasn't exactly a cheap printer, and it works great. I find the trick with any company it so not go cheap. Cheap printers break, if you spend a little money, you get a much better printer that will last a lot longer.
    Crunching for Team TPU 50 Million points folded for TPU

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page