Yahoo Groups archive

Kawai K5000 series

Index last updated: 2026-04-28 23:05 UTC

Thread

OS 4.03 or 4.04

OS 4.03 or 4.04

2005-03-23 by Al

Hi all,
I must be blind!!! 
I've owned a K5000s since 1998 & it is still in mint
condition.
I also thought that OS 4.03 was the last os update
released.
Yet, I found myself loafing around the KAWAI US site &
low & behold there's an os 4.04 for the k5000s!!!

Can anyone please enlighten me as to what was fixed/
tweaked/added/altered from 4.03 to 4.04?  
Should i upgrade?
Will i notice a difference with anything?

Look forward to your answers
Al


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: [K5000-1] OS 4.03 or 4.04

2005-03-27 by Atom Smasher

On Wed, 23 Mar 2005, Al wrote:

> Hi all, I must be blind!!! I've owned a K5000s since 1998 & it is still 
> in mint condition. I also thought that OS 4.03 was the last os update 
> released. Yet, I found myself loafing around the KAWAI US site & low & 
> behold there's an os 4.04 for the k5000s!!!
>
> Can anyone please enlighten me as to what was fixed/ 
> tweaked/added/altered from 4.03 to 4.04? Should i upgrade? Will i notice 
> a difference with anything?
==================

IIRC....

OS 4.04 fixes a bug in the 5000r and the 5000s. the 5000w is not affected 
by the bug.

anyway, the bug that is fixed is that the controllers don't respond the 
right way in multi mode and 4.04 fixes it.


-- 
         ...atom

  _________________________________________
  PGP key - http://atom.smasher.org/pgp.txt
  762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
  -------------------------------------------------

 	"It is well enough that people of the nation do not
 	 understand our banking and monetary system, for if
 	 they did, I believe there would be a revolution before
 	 tomorrow morning."
 		-- Henry Ford

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.