Well, no. I did not do that. But that doesn't explain why it freezes up in the disk menu. Once youre in it you apparently can't get out of it. I would assume that you would assign the SCSI and disk preferences as you suggest, from this menu. Or is there another route? I thank for your interest so far, Dan. Maybe this reply helps clarify the problem. I definately get you on the idea of an address conflict, which is why I unplugged the hard drive again. But it still doesn't do anything. I won't even load floppies anymore. This was all apparently a result of unplugging and plugging that hard drive in again. So maybe the previous owner did have a reason. --- In vintagesynthrepair@yahoogroups.com, Daniel Forró <dan.for@...> wrote: > > Have you set different SCSI address for each of SCSI devices? Maybe > there's just device address conflict. > > Daniel Forro > > On 25 Nov 2010, at 10:57 AM, brofjw wrote: > > > Hi. I've had this Kurzweil K2000R for about a year now and I'm > > starting to think it's jinxed. It seemed to have a dead internal > > battery, something I knew when I bought it. I found out later that > > the battery holder had cracked (as many K2000R's have). While I had > > the cover open, I also noticed that this unit actually had a hard > > drive inside but someone had disconnected both the power and the > > ribbon cable. Until then I had been using floppies and an SCSI cd- > > drive. I plugged the hard rive in and was thrilled to find it > > worked perfectly. (Why would someone unplug it if it worked fine?) > > Anyway sent away to Hong Kong for a generic battery holder and > > replaced the factory one with it. That also worked perfectly. > > Here's where the trouble starts: > > > > After ascertaining that the hard drive worked, I also plugged back > > in my SCSI CD-drive. For some reason the K2000 didn't pick it up. I > > figured the internal hard drive must have replaced the SCSI drive. > > So I uplugged the hard drive again and tried to boot the CD-drive. > > No dice. At this point when I hit "disk", the K2000 only > > acknowledges the flopy drive and there is no list of either the > > hard drive or SCSI. What's more, it seems to get stuck on the > > "disk" menu and refuses all commands thereafter. Does anyone have > > any idea what is wrong with this thing? I can still play the > > internal RAM sounds, no problem. But this is the tip of the iceberg > > for this machines capabilities, in theory. Should shoot this thing > > and put it out of its misery? Or should I sell it for a measly $100 > > and move on? Or is there some simple solution I am not seeing? Any > > help is appreciated. Thanks! :-) >
Message
Re: Save a Kurzweil K2000R from being shot
2010-11-25 by brofjw
Attachments
- No local attachments were found for this message.