Kon/Min Firmware

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • copyman
    Owner / Technician

    Site Contributor
    2,500+ Posts
    • Sep 2005
    • 4213

    Kon/Min Firmware

    Could never get a straight answer for this question. Even from K/M instructors at schools......

    "When you download SPECIAL firmware is all the previous Special Firmware's included in the download or just for the issues in the title?"

    Thanks
  • Woxner
    Senior Tech

    500+ Posts
    • Jul 2011
    • 808

    #2
    Re: Kon/Min Firmware

    I was told at school is has the prev as well not just the fix

    Comment

    • copier tech
      Field Supervisor

      5,000+ Posts
      • Jan 2014
      • 7931

      #3
      Re: Kon/Min Firmware

      Originally posted by copyman
      Could never get a straight answer for this question. Even from K/M instructors at schools......

      "When you download SPECIAL firmware is all the previous Special Firmware's included in the download or just for the issues in the title?"

      Thanks

      This was discussed recently.

      Simply install the latest available firmware it includes all previous bug fixes.

      Some sites call it "special" others call it "intermediate" basically these are releases in-between each mass production release.
      Let us eat, drink, and be merry, because tomorrow we may die!

      For all your firmware & service manual needs please visit us at:

      www.copierfirmware.co.uk - www.printerfirmware.co.uk

      Comment

      • emujo2
        Service Manager

        1,000+ Posts
        • Mar 2017
        • 1580

        #4
        Re: Kon/Min Firmware

        From the way I have learned..Special f/w is used to correct certain issues under certain conditions. Special f/w is not generally used in a typical situation. Regular F/W addresses issues that are common across the line.

        Comment

        • tsbservice
          Field tech

          Site Contributor
          5,000+ Posts
          • May 2007
          • 7635

          #5
          Re: Kon/Min Firmware

          My underastanding is going like that.
          You have mass production lets say M1 then after year M2 etc. In between you have some special FW versions lets say S1, S2, S3 fixing bugs, issues and adding features sometimes.
          That it is then M1-S1-S2-S3-M2. So for this example S3 is special FW based on M1 mass FW and including S1 and S2 fixes plus some more fixes. M2 FW will include all S1+S2+S3 and so on.

          Special note for customized FW versions which are designed for some very specific client/environment scenarios and unless your machine isn't in exactly the same position shouldn't be considered in the field.

          Well, I may be wrong
          A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
          Blessed are they who can laugh at themselves, for they shall never cease to be amused.

          Comment

          • Synaux
            Service Manager

            Site Contributor
            1,000+ Posts
            • Mar 2012
            • 1224

            #6
            Re: Kon/Min Firmware

            Originally posted by tsbservice
            My underastanding is going like that.
            You have mass production lets say M1 then after year M2 etc. In between you have some special FW versions lets say S1, S2, S3 fixing bugs, issues and adding features sometimes.
            That it is then M1-S1-S2-S3-M2. So for this example S3 is special FW based on M1 mass FW and including S1 and S2 fixes plus some more fixes. M2 FW will include all S1+S2+S3 and so on.

            Special note for customized FW versions which are designed for some very specific client/environment scenarios and unless your machine isn't in exactly the same position shouldn't be considered in the field.

            Well, I may be wrong
            I brought this up myself not terribly long ago.
            This is my logical conclusion and as I recall, the general consensus.
            (But I wouldn't put money on it being reality.)

            The only way to confirm this is to install a special firmware on a machine that meets the criteria for that specific SFW (and have it actually fix the issue).
            Then install the newest base FW and see if the issue comes back.
            If anyone takes the time to actually do this, I would would welcome the results

            (FW is a lot simpler and less finicky nowadays, but I still have a little voice in the back of my head asking "are you sure you really want to risk a power outage or I/O corruption" so I probably wont ever do it myself).

            And I wouldn't put it past KM to be inconsistent in implementing all special FW into all base FW. Furthermore, there might be instances where the special firmware must be a standalone FW. For instance, it might need to bypass some base FW code to fix a specific issue.

            Comment

            Working...