400ci USB printing error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dave10
    Trusted Tech
    100+ Posts
    • Jul 2008
    • 198

    400ci USB printing error

    Bad situation. We were doing a demo for a potential customer on a CS-400ci and they brought in a usb flash drive with some pdf files on them to test print. We have never had trouble with this before. This time, we put the drive in the front usb port and it said to format the drive. We loaded the files from the drive to a computer and tried to print and the machine kept showing a JAM 80 where there was no paper. Any other flash drive would print, and any other file from the computer is fine, but these files kept saying jam 80. Anyone seen this?
  • blackcat4866
    Master Of The Obvious
    Site Contributor
    10,000+ Posts
    • Jul 2007
    • 22599

    #2
    J80 is a finisher jam..
    No never seen anything like that. =^..^=
    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

    • n25an
      Service Manager
      Site Contributor
      1,000+ Posts
      • Jul 2008
      • 1030

      #3
      try updating the firmware... next check if the document type is somehting that that machine can print... third... open the document and save it as a newer form of itself... ( example say the document was a word 6.0 try upgrading it to a word 2007)
      Sad To Say I Don't Have a Life
      I do this stuff on the weekends too

      Comment

      • mike*
        Technician
        50+ Posts
        • Jun 2010
        • 58

        #4
        firmwares the most current. the document was just a PDF file, and adobe opened it just fine on the computer. went to print the PDF out and the job spooled to the machine and before the paper was even fed it called for a jam 80. no paper was anywhere in the machine. deleted the job out of the machine queue and made a copy just fine. went to print it again bam same error before the paper was even fed out of the cassette. strangest thing ive ever seen. other pdf's from the same computer, not on the thumb drive, printed just fine too. Im at the conclusion it was something with there file or the actual thumb stick but you try explaining that to someone who your trying to sell a machine too....

        Comment

        • LNorris
          Senior Tech
          500+ Posts
          • Sep 2008
          • 646

          #5
          i've seen thumbdrives that are running a program on them i.e. cruizer or something similar, stop the mfp from seeing the data to be printed. i dont use those for firmware updates either for the same reason.

          Comment

          • n25an
            Service Manager
            Site Contributor
            1,000+ Posts
            • Jul 2008
            • 1030

            #6
            excellent

            thanks for the info...
            Sad To Say I Don't Have a Life
            I do this stuff on the weekends too

            Comment

            • mike*
              Technician
              50+ Posts
              • Jun 2010
              • 58

              #7
              Originally posted by LNorris
              i've seen thumbdrives that are running a program on them i.e. cruizer or something similar, stop the mfp from seeing the data to be printed. i dont use those for firmware updates either for the same reason.
              heres where i have questions and correct me if im wrong....most of the usb sticks that have that "cruizer" software have to have some kind of autorun.inf or autostart depending on which OS people run. The autostart file is for the macs but only on OS 9 and previous (before they went back to some type of linux based?). so my question is the kyocera machines are linux based so how could any .exe file or .inf or autostart for that matter run on the machines and cause problems? linux wont execute a .inf file or .exe file without some type of emulation to run them so how do these programs have an affect on the machines? this is probably more of an in depth question and i am fully willing to accept just a because but i would like to know the more technical details of this occurence

              Comment

              • aragul
                Trusted Tech
                100+ Posts
                • Dec 2007
                • 128

                #8
                Linux systems generally won't autostart anything from a removable device. I think some desktop environments (GNOME, KDE) might for audio CDs and the like, but embedded systems definitely won't unless the manufacturer wanted it. And like you said, Linux won't run .exe files natively, and these embedded systems aren't going to mess with Wine.
                I think the issue may be from weird partitioning on those USB sticks, but it's hard to say since I haven't seen the problem (yet).

                Comment

                • LNorris
                  Senior Tech
                  500+ Posts
                  • Sep 2008
                  • 646

                  #9
                  i think the issue is the partitions, the cruizer software is on one "letter drive" and the contents are on another. so the MFP is looking for one drive that has nothing on it for it to read. or thats the way i'm looking at it. it just solved so many problems to ensure the thumbdrive didnt have those things on it. dont know why the manufacturers put that on there in the first place.

                  Comment

                  • mike*
                    Technician
                    50+ Posts
                    • Jun 2010
                    • 58

                    #10
                    Originally posted by aragul
                    Linux systems generally won't autostart anything from a removable device. I think some desktop environments (GNOME, KDE) might for audio CDs and the like, but embedded systems definitely won't unless the manufacturer wanted it. And like you said, Linux won't run .exe files natively, and these embedded systems aren't going to mess with Wine.
                    I think the issue may be from weird partitioning on those USB sticks, but it's hard to say since I haven't seen the problem (yet).
                    yea the audio cds i can understand but for the removable media i didnt think it would be a problem. we installed two of the usb readers into two konica machines and the usb sitcks had the u3 software on them and it caused all sorts of issues and problems for us. im gonna have to take a closer look into the partitioning of the usb sticks with this software to actually see whats really going on with it. even if the usb sticks were partitioned into two letter drives and it only finds the one with the software on it theres no reason for ANY autostart launcher or autoexe type file to run under the OS's they use in the machines. worst case scenario i would think would be a format error on the machine....this is unlikely but what if the machine did use some type of emulation like WINE to open the file types. (pdf,bmp,tiff) I dont see any reason they would but sometimes you never know how the programmers did it.

                    Comment

                    • mike*
                      Technician
                      50+ Posts
                      • Jun 2010
                      • 58

                      #11
                      TAKEN FROM WIKI ON U3

                      U3 disk mounting: hardware emulation

                      A U3 flash drive presents itself to the host system as a USB hub with a CD drive and standard USB mass storage device attached.[1]
                      This configuration causes Windows disk management to show two drives:
                      A read-only ISO 9660 volume on an emulated CD-ROM drive with an autorun configuration to execute the U3 LaunchPad, and;
                      A standard flash drive (FAT formatted) that includes a hidden "SYSTEM" folder with installed applications.
                      U3 compliant applications can be (optionally) preloaded by manufacturers.
                      [edit]
                      U3 Launchpad

                      U3 Launch Pad example.

                      The U3 Launchpad (LaunchU3.exe) is a Windows program manager that is preinstalled on every U3 smart drive.[2]

                      The U3 Launchpad automatically starts at insertion of a U3 enabled device, except on Windows 7.
                      Freezing with certain CD writing software
                      There is a possibility of slowing down or freezing Windows XP Pro if certain Windows drivers that are associated with high-volume data transfers to CD writers using certain CD/DVD burning software installed (Nero v7 and Roxio DirectCD[7])
                      Proprietary format / closed platform
                      The U3 platform is a "closed" platform / proprietary format, and unavailable for developers.[8] SanDisk, the rights holders for U3, ask for a 5% royalty from USB flash drive manufacturers who wish to implement the platform on their products.
                      Two drive letters
                      As a work-around to the lack of Auto-Play for Flash drives on older versions of Windows, the U3 software creates two drive letters (one which presents itself as a CD to allow Windows' auto-play to start the launcher, and another for storing user data). Although this is the only way to implement auto-start functionality on pre-Windows XP systems, it could be considered a kludge, and the extra drive letter created can be an annoyance. However, it is possible to prevent Windows from allocating a drive letter for the "CD drive" via the Windows "Disk Management" tool -- as long as the user has the appropriate rights/authority to do so.
                      Incompatibility with certain embedded systems
                      Some host systems – such as photo kiosks, consumer electronics, and other embedded computing devices – cannot correctly mount U3 "smart drives." The problem may arise because the emulated CD-ROM is the first drive presented to the host system. As such, the device is detected as a CD-ROM drive or not at all. Although some newer photo kiosks are U3 aware[9] and can overcome this limitation, it still exists on many platforms. In embedded systems, where program memory is limited, it may be very costly in terms of system resources to make a device U3 aware. In such cases it is far more logical to leave this functionality out.


                      __________________________________________________ __________________________________________________ _____________________

                      So basically the usb stick is partitioned into two different drives..one acting as an cd containing an ISO which will allow autorun to perform on MOST OS platforms and the other as a media storage. Now i see how this can and will cause problems. its a creative work around for the autostart functions on the usb stick. i know that on the konica machines we did after we put the usb in with the U3 software we were told to flash the firmware to fix it but image some accounts where youll be going out there every otherday to flash firmware because people will just put there stick in. not to mention the fact that they wont be able to find there documents because its reading the wrong drive...

                      Edit: but the autostart program is an .exe? so basically its just reading the wrong drive letter and the documents will never be found on the usb but it in theory should not have any adverse effect on the machines...

                      Comment

                      • cmpelser
                        Trusted Tech
                        • Jan 2008
                        • 173

                        #12
                        I've been using a 8gig cruzer (u3) memory stick formated in FAT32 to do my firmware upgrades... no problems so far.
                        any comments as to wether I should just continue.. or is it not recommended???
                        Is there a way to get rid of that annoying cruzer u3 program? (formating will not work.)

                        Comment

                        • mike*
                          Technician
                          50+ Posts
                          • Jun 2010
                          • 58

                          #13
                          Originally posted by cmpelser
                          I've been using a 8gig cruzer (u3) memory stick formated in FAT32 to do my firmware upgrades... no problems so far.
                          any comments as to wether I should just continue.. or is it not recommended???
                          Is there a way to get rid of that annoying cruzer u3 program? (formating will not work.)
                          How to Uninstall U3 from USB Flash Drive | kombitz.com

                          i would uninstall it if your not using it for anything else but doing firmware. its could potentially cause future problems....if it tries reading from the wrong partition when it boots it. what model machines do you use it to do the firmware?

                          Comment

                          • cmpelser
                            Trusted Tech
                            • Jan 2008
                            • 173

                            #14
                            i use it to upgrage on almost all the machines... no problems so far...

                            Comment

                            • mike*
                              Technician
                              50+ Posts
                              • Jun 2010
                              • 58

                              #15
                              well in theory it shouldnt....but im still going to look into how the machine actually reads the sticks. if it can be partitioned and what not

                              Comment

                              Working...