It would be very helpful if the file kaos.bin, which is already included in the OS, would be so named that you can see on the file name which version it is (eg 2.1.1_8853). That would probably not a big job for the programmer.
If you have this file on a USB stick, it is impossible to see what FW it is.
File name "kaos.bin" too imprecise
-
WS -
October 22, 2013 at 10:56 AM -
Closed
-
yeah!
and by the way: if spoken the name of the file does not bring the best associations ...
-
and by the way: if spoken the name of the file does not bring the best associations ...
It always reminds me of Kaossilator and Kaoss Pad (http://en.wikipedia.org/wiki/Kaoss_Pad). Confusing - yes, bad association - no.
-
And what's the benefit?
When you plug your stick into your kemper it shows the version-nr on the screen, when it asks to install the firmware.As an alternative just create a copy of the file in the folder and rename it to your desire. If you want to install a particular version, copy/rename kaos_2.1.1_8853.bin to kaos.bin and you're ready to go.
by the way, checking the date of the file may helps you to identify the right version.
-
I see no need for that.
The zips have all the "naming" info one could want.
The "autoplay" function on the Kemper, when you plug the stick in works fine as it is and would become difficult to maintain.
Not certain if there are more references to the file name in the code.Kaos.bin would be Kemper.exe oder Kemper.app on WIN/OSX.
-
That would probably not a big job for the programmer.
If you have this file on a USB stick, it is impossible to see what FW it is.
There is a minimal firmware loader that allows the recovery procedure in case a firmware doesn't boot for any reason. To keep this very small and lean, it only supports FAT16/32 with 8.3 filename convention. So the firmware filename needed to match these criteria.KAOS means "Kemper Amp Operating System".
That it sounds like "chaos" is an intended, yet funny (at least from my POV) co-incidence.
Timo
-
Maybe it should be controlledchaos.bin......
-
And what's the benefit?
I always have a USB stick with an older FW thereby when I'm at gigs. If I look up at the PC trying to see what version it is, it is impossible, since all versions have the same name kaos.bin. Thus, an assignment of the exacte version number is not possible and therefore I must every time copy the desired version of the USB stick to make sure that it is the desired version of me. -
you could just copy the file and rename it how you wanted and store it on your usb drive in another folder (or maybe even the same folder if that doesn't cause issues).
-
I always have a USB stick with an older FW thereby when I'm at gigs. If I look up at the PC trying to see what version it is, it is impossible, since all versions have the same name kaos.bin. Thus, an assignment of the exacte version number is not possible and therefore I must every time copy the desired version of the USB stick to make sure that it is the desired version of me.Create a directory on the stick - call it zip and put the files there. The zips have "tale-telling" filenames.
-
Can't see the need of renaming. It's an individual and unique name. Don't stop thinking and organize your IT ...
-
kaos.bin
Kemper Amplifier Operating System .bin (.bin because I presume its a binary file? (Makes me wonder if the Kemper OS is UNIX based, but I digress....))oh and +1. I can see this as being useful in a pinch
-
Bottom line:
The KPA boot loader needs to find a fixed filename in order to automatically upgrade. I doubt they will change this.
Solution:
Keep separate USB sticks if you want to recover to more than one FW version. Surely nobody needs more than 2. One would be beta and the other trusted.
On the user's PC, zip files named to reflect each FW can be kept in an archive folder and extracted to one of the USB sticks as needed.
-
(Makes me wonder if the Kemper OS is UNIX based, but I digress....))
It isn't.Timo
