Win7 OS will not print to 5035

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Geo
    Senior Tech

    500+ Posts
    • Nov 2010
    • 662

    #1

    Win7 OS will not print to 5035

    Trying to set up printing for a 5035 on a pc running Win 7 with a 15' USB cable. Windows 7 is not finding the 5035,it only finds a unknown printsys(u). Pluged the USB into a XP pc and it reconized the copier and installed it.
    Does Win7 OS have problems installing Falcons with a USB cable or is it me?
  • blackcat4866
    Master Of The Obvious

    Site Contributor
    10,000+ Posts
    • Jul 2007
    • 22997

    #2
    Windows7 definitely has problems with the USB ports. I don't know if there's a patch or OS upgrade, but it's the Windows7 for sure.
    I've been lucky. In the few situations I encouraged the user to use the network connection. =^..^=
    If you'd like a serious answer to your request:
    1) demonstrate that you've read the manual
    2) demonstrate that you made some attempt to fix it.
    3) if you're going to ask about jams include the jam code.
    4) if you're going to ask about an error code include the error code.
    5) You are the person onsite. Only you can make observations.

    blackcat: Master Of The Obvious =^..^=

    Comment

    • jmaister
      certified scrub

      Site Contributor
      500+ Posts
      • Aug 2010
      • 755

      #3
      Win 7 definitely has problems.


      Idling colour developers are not healthy developers.

      Comment

      • Geo
        Senior Tech

        500+ Posts
        • Nov 2010
        • 662

        #4
        Ohh Joy !

        Comment

        • Geo
          Senior Tech

          500+ Posts
          • Nov 2010
          • 662

          #5
          Does anybody have a fix or workaround for this?

          Comment

          • denden4h
            Technician
            • Mar 2006
            • 31

            #6
            Are you using the Windows 7 driver or the KX? The Windows 7 drivers for KM seem to be problematic so I would recommend downloading the latest from KMA.

            Comment

            • ignacio.cortez
              Trusted Tech

              100+ Posts
              • Jul 2010
              • 176

              #7
              Re: Win7 OS will not print to 5035

              "This messages does not make any assumptions about you knowing anything about Windows"
              --- So I'm Making it as Basic as possible ---

              OK I had a similar issue, where it wouldn't find the USB Print port, so here is what I did:

              get the following text (between the dotted lines):

              ---------------------------------------------------------------------------------
              Windows Registry Editor Version 5.00

              [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Monitors\USB Monitor]
              "Driver"="usbmon.dll"

              ---------------------------------------------------------------------------------

              Paste it into a notepad document, save it as [WHATEVER YOU WANT TO CALL IT].reg, make sure you have your extensions visible (chances are notepad will try to save it as [NAME].reg.txt (make sure you get rid of the .txt)

              Once you see a Registry Key icon (white page with a broken green rubik cube icon)
              double click on the link, it will add the Registry key to the system, Restart the computer (have the user log in) then try to add the printer again, you'll probably will get through and be able to install the driver using USB)

              If you cannot create the file, download this txt file, rename it [NAME].reg and then run it and restart.
              Attached Files

              Comment

              • kkendric
                Trusted Tech

                250+ Posts
                • Apr 2009
                • 301

                #8
                Re: Win7 OS will not print to 5035

                Definately download the newest drivers. If it found a print System "U" it found the print system for the 5035 copier, it just does not recognize it possibly due to wrong drivers on the system. Just a guess.

                Comment

                Working...