Mike Martin/Geosync K2500 OS/object boot

[BBach]

Turns out the K2500 I got on ebay has a broken floppy

drive. The scusi chain has a K2000, cd rom, syquest

removable, and the K2500. The synths are on either end of the chain. So, I dowmload the latest OS and

object files, unzip them to a floppy, put the floppy

in the K2000 and copy them to the syquest. I then

attempt to install the files to the K2500, but the

syquest is not recognized. When the disc mode is

called up, it has no problem recognizing and loading

from the syquest. But in the boot mode, no luck.

Any ideas ? I was thinking about getting KDFX, but

it won't be of much use if I can't update the

OS/objects. It sure is nice to have you guys to whine

to everytime I can't get something to work.

[Mike Martin]

If all three are on the same SCSI chain. Change the SCSI ID of the K2000 (MIDI XMIT page I think) to something other than 6 as the K2500 will also be on ID#6. Hope this helps,

[BBach]

No scusi # conflict in this situation. The K2000

scsi id# was changed when the K2500 was added.

Does the K2500 need to see these files in the uppermost hierarchy to recognize the drive ?

Maybe I'll try putting the files on a CD-RW and

reading them off the cd-rom drive. All of this

DOS/Almost DOS and ISO specification stuff is

perplexing. Maybe I'll have to get the floppy drive repaired.

[Mike Martin]

I'll have to check with R&D, but I'm pretty sure that there are issues with loading OS files from some SCSI devices (mainly CD-ROMs but maybe your hard drive too). Since the ability to access these drives is in the OS, not he boot loader, this is likely the problem.