Reviving K2000 software development

Hello to everybody,
 

 I am new on this list, although I have been reading it now and then - so let me present myself quickly.
 

 I have bought a used K2000 around 1998, and equipped it straight away with an internal hard drive and sample RAM. I stopped using it in July 1999, one reason being the frustration with the limitations of the system in ROM, particularly the inability to edit the ROM samples; and also the trouble of having to load the samples into RAM at each startup, despite the impression that programs are there and ready to run, since they are properly displayed in the banks in Program mode. There were other personal reasons which led me to abandon music completely at the same time, but I gave up on the K2000 before I gave up on music.
 

 Now two years ago, I got interested in making music again, and took my K2000 from my cellar. After some revision, it is in great shape, except for an issue with the volume slider.
 

 I am a beginner in digital electronics; but since my background is a good familiarity with computers, I am getting interested with updating the system software ("ROM", actually it sits in EPROM chips). I would like to know whether there is some interest in this list in the following tasks and objectives:
 * understanding the working of the boards, especially the engine board;
 * understanding the system software;
 * improving the performance of the overall system, especially through software only updates (that is, releasing new EPROMs contents for the engine ROMs);
 * backporting improvements that later K2500 software revisions include;
 * and why not, improve on the sound generation possibilities, according to the user community interests?
 

 One of my main goals would be to improve overall performance, especially SCSI read times, and memory handling code.
 

 Of course, it would be worthwhile first to ask courteously people at Young Chang whether they want to do such themselves; and if not, how they may help, perhaps by releasing information like schematics, development documents, code source, or whatever information would help getting forward with the project.
 

 I am not too optimistic with this step, expecting that nothing would come out of it - but I would love to be proven wrong on that count!
 

 It feels to me that despite YC's discourse that "they always improve their product", which you can see prominently displayed with each K2500 ROM updates, they gave up on the K2000 quite early, in favor of k2500 development and sales. It seems to me - but I would need to double check - that K2000 and K2500 hardware is not much different; and that this decision is mainly an economic (human resources) and marketing (sales of the new line of products) one, not a purely technical one.
 

 But I believe a community of K2000 users and aficionados is still alive and well; and I hope they wouldn't mind dreaming, asking for, and perhaps help manifest a new life to K2000 software development and enhancement.
 

 I would like to know your feelings about this; and whether anybody would like to embark on this wonderful journey of exploration and realizations.
 

 Thank you for reading!
 

 Yann