none
Installing Epson LQ-590 32-bit driver on Server 2008 R2 64-bit

    Pregunta

  • Hello,

    I have a 64-bit server that also operates as the print-server in our domain (Win Server 2008 R2). 

    In our domain, I have 32-bit and 64-bit machines. For all printers I can install 32-bit and 64-bit drivers on my server, except for the Epson LQ-590 (and the LQ-2090). 

    I've tried to install the driver by pushing it from a workstation (32-bit) to the server (64-bit), but it doesn't work.

    I've tried to copy the 32 bit drivers from a workstation to the server (as described on another thread*) but then I get the error: The given location doesn't contain the driver for EPSON LQ-590 ESC/P 2 for the requested processor - translated from Dutch)

    Also Epson doesn't provide downloadable drivers for these printers as they come "in the box" with  server 2008 en Windows Vista/7.

    Does anyone has an idea/suggestion on how it can be done? 

    I found some workarounds online, but the one that "worked" actually installed the printer locally on the workstations. (what I don't want to)

    One thing I've noticed is that the name of this printer(driver) is differtent in a 32 and 64-bit Win7. Could this be the problem, as Mr Allan Morris suggests in the same thread* as mentioned above? Cause the printer can work with each driver and it is the standard driver delivered with Windows.
    32 bit => EPSON LQ-590 ESC/P 2 Ver 2.0

    64 bit => EPSON LQ-590 ESC/P 2

    And if this is the problem, what are my options?

    Thx for your suggestions!

    * http://social.technet.microsoft.com/Forums/en/winserverprint/thread/fadd236f-5264-4f32-aba9-684c850315f0

    martes, 06 de noviembre de 2012 21:45

Respuestas

  • Hi BertBXL,

    I had checked both my x64 versions of WIN7 ENT and W2k8 ENT, and both of them has 'EPSON LQ-590 ESC/P 2 Ver 2.0' drivers embedded for x64.. Are you sure it was not replaced by downloaded files?


    check your prnep004.inf_amd64_neutral_63b22bfb6b93eaba
    miércoles, 07 de noviembre de 2012 8:18
  • I actually helped someone else with a problem like that. Like you tell, the real problem is epson didnt named 32 and 64's driver the same.

    If you are sure both match you could edit the 32b .inf and directly change the driver name in it.

    Else your only option there is to use a generic's driver or use a 32bit server to share it from there for 32bit computer and a 64bit printqueue on your 2008r2 server...

      


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Want to follow me ?  |  Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    miércoles, 07 de noviembre de 2012 3:46
  • Hey Sergey,

    You are right, but let me quickly explain what happened:

    We have one Win2008 server, but this wasn't a R2 version and there the problem exists. No way of getting the 2 drivers installed on that version (it was a the SBS version - my mistake)

    We were removing a 2003 server from the domain and adding a 2008 R2 server to it. Because I was adding 64-bit workstations to our domain (for the first time), I wanted to install all printers on the SBS server (2nd server) to keep the printermanagement simple. Now the 2008 R2 is operational I can install all printers on that one, what solves my problem as well or even better.(already done btw!)

    So Sergey, thx for pointing this out, otherwise I would have kept looking for a solution on the SBS.

    Grtz,

    Bert

    Maybe small summary:

    Win2008 & Win7 32+64 bit => EPSON LQ-590 ESC/P 2 Ver 2.0 => all okay

    Win SBS2008 64 bit => EPSON LQ-590 ESC/P 2 => will give compatibility issues with Win7 32-bit

    • Marcado como respuesta BertBXL miércoles, 07 de noviembre de 2012 23:10
    • Editado BertBXL miércoles, 07 de noviembre de 2012 23:24
    miércoles, 07 de noviembre de 2012 23:06

Todas las respuestas

  • I actually helped someone else with a problem like that. Like you tell, the real problem is epson didnt named 32 and 64's driver the same.

    If you are sure both match you could edit the 32b .inf and directly change the driver name in it.

    Else your only option there is to use a generic's driver or use a 32bit server to share it from there for 32bit computer and a 64bit printqueue on your 2008r2 server...

      


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Want to follow me ?  |  Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    miércoles, 07 de noviembre de 2012 3:46
  • Hi BertBXL,

    I had checked both my x64 versions of WIN7 ENT and W2k8 ENT, and both of them has 'EPSON LQ-590 ESC/P 2 Ver 2.0' drivers embedded for x64.. Are you sure it was not replaced by downloaded files?


    check your prnep004.inf_amd64_neutral_63b22bfb6b93eaba
    miércoles, 07 de noviembre de 2012 8:18
  • Hey Sergey,

    You are right, but let me quickly explain what happened:

    We have one Win2008 server, but this wasn't a R2 version and there the problem exists. No way of getting the 2 drivers installed on that version (it was a the SBS version - my mistake)

    We were removing a 2003 server from the domain and adding a 2008 R2 server to it. Because I was adding 64-bit workstations to our domain (for the first time), I wanted to install all printers on the SBS server (2nd server) to keep the printermanagement simple. Now the 2008 R2 is operational I can install all printers on that one, what solves my problem as well or even better.(already done btw!)

    So Sergey, thx for pointing this out, otherwise I would have kept looking for a solution on the SBS.

    Grtz,

    Bert

    Maybe small summary:

    Win2008 & Win7 32+64 bit => EPSON LQ-590 ESC/P 2 Ver 2.0 => all okay

    Win SBS2008 64 bit => EPSON LQ-590 ESC/P 2 => will give compatibility issues with Win7 32-bit

    • Marcado como respuesta BertBXL miércoles, 07 de noviembre de 2012 23:10
    • Editado BertBXL miércoles, 07 de noviembre de 2012 23:24
    miércoles, 07 de noviembre de 2012 23:06
  • Thx Yagmoth555 for your reply. Like you can read, I found a solution.

    Fyi: I tried your suggestion as well (namechange), but it didn't work. I got the same error-message. Your other suggestions would work, I guess, but doesn't really solve the problem of course, but is more a workaround :-)

    Grtz,

    Bert



    • Editado BertBXL miércoles, 07 de noviembre de 2012 23:29
    miércoles, 07 de noviembre de 2012 23:09
  • Iam happy it worked  ! Renaming the driver can work, but not always, but that way in the final is more clean :)

    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Want to follow me ?  |  Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    jueves, 08 de noviembre de 2012 1:33
  • Can you explain this solution? I have the same problem but i don't understand. My english is basic. Thanks
    miércoles, 18 de septiembre de 2013 14:47