mnkonar@gorby.SRC.Honeywell.COM (Murat N. Konar) (01/28/89)
Help! I'm having difficulty with my <1 yr. old Jasmine InnerDriveII 90 in my Mac II. Here are some of the symptoms I have experienced. They changed as time went on: - when booting in the morning, the drive would spin up, but the Mac wouldn't boot. All I got was the floppy icon with the flashing "?" in the center of the screen. Pressing the programmer's reset button would usually get the boot process started from the hard drive. Things would then work normally for the rest of the day. - Once or twice, the Mac booted off the drive WITHOUT RUNNING ANY OF MY INITS! Rebooting put things back to normal. - Occasionally, booting would start out ok, but after a few INITs had loaded it would crash. - Before my problems started, I had about 45 Megs used. After my problems began, this figure jumped to 58 Megs! I ran Apple's Disk First Aid and sure enough it said that repairs were needed. After repair, I was back down to 45 Megs. - I backed up my disk to tape and reformatted it using Jasmine's formatter. When I tried to reboot from this Empty disk (no system or anything, just desktop file) It got as far as putting up the happy Mac before deciding it couldn't boot. Installing a system (6.0.2 from an Apple Diskette, no virii) allowed it to boot (surprise) until I tried again the next morning (bummer). - Once or twice the drive did not spin up on power up. Hitting the programmer's reset switch caused the drive to spin up. - Sometimes when I boot off of a floppy, the Innerdrive will not show up. Jasmine's Mount program is able to get the Innerdrive to show up. - Once while booting I got a "Couldn't load needed resource" error. - Once while booting I got an err=15 error. (Segment loader error, I think) - Zapping the PRAM seems to have no effect. - I tried re-seating the power and SCSI cables but this didn't help. I'm stumped. Most of my problems happen after the Mac has been off for 6 hours or so. Once it starts geting warm, the symptoms begin to get less severe and finally stop. This leads me to suspect that the problem is in hardware and not software. This is the first time I've had this persistent a problem. I suspect it's a hardware problem. If any one can help me out I'd really appreciate it. Murat N. Konar Honeywell Systems and Research Center (612)782-7466 3660 Technology Dr., Minneapolis, MN 55418 Internet: mnkonar@src.honeywell.com