ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (05/18/88)
Since I got my C. Ltd. hard disk last week, I have had a small problem booting my Amiga 1000. When I first power on, power up the hard drive, and insert the Kickstart1.2 disk, my Amiga does not recognize my disk as Kickstart. The drive light flashes briefly, and the "insert Kickstart" picture reappears. So, I pop out my disk and re-insert it. Voila... no problems. Does anybody understand this? Sometimes, the computer takes 5-10 attempts before it recognizes my Kickstart disk. Yes, I am letting the hard drive completely spin up before I insert Kickstart. Amiga 1000, KS1.2, Microbotics StarboardII (2meg), CLtd SCSI controller & 50-meg hard disk. -- Dan Barrett ins_adjb@jhunix.UUCP barrett@cs.jhu.edu
carl@step.UUCP (Carl Tichler) (05/19/88)
From article <6456@jhunix.HCF.JHU.EDU>, by ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett): > > Since I got my C. Ltd. hard disk last week, I have had a small > problem booting my Amiga 1000. When I first power on, power up the hard > drive, and insert the Kickstart1.2 disk, my Amiga does not recognize my > disk as Kickstart. The drive light flashes briefly, and the "insert > Kickstart" picture reappears. > I have the same problem with my Amiga 1000, and I do not have a hard disk (just the original Amiga with monitor and internal disk drive). I had a feeling it was just some minor problem with the disk drive. Carl Tichler
ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (05/26/88)
My problem that I posted has since disappeared. Here's what I did... even though it doesn't seem to make sense. Bob Page suggested that my Kickstart disk might be corrupt, so I should try Diskcopy-ing it; Diskcopy would complain if there were errors. Guess what... the Diskcopy DID fail. Couldn't read the source disk. Thinking that this might have been an error on my part, I did the Diskcopy again. And it WORKED WITHOUT COMPLAINT. The old Kickstart disk (not the copy) has never failed since then. From the outside, it looks like my original Diskcopy attempt somehow corrected some small problem on the ORIGINAL disk. This doesn't make any sense to me... but the problem IS gone. -- Dan Barrett ins_adjb@jhunix.UUCP barrett@cs.jhu.edu