Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!cornell!vax5!q4kx From: q4kx@vax5.cit.cornell.edu (Joel Sumner) Newsgroups: comp.sys.apple2 Subject: Re: Two questions Message-ID: <5409.26ea382b@vax5.cit.cornell.edu> Date: 9 Sep 90 16:40:11 GMT References: <1990Sep8.073212.2278@wrkof.incom.de> Distribution: comp Lines: 30 In article <1990Sep8.073212.2278@wrkof.incom.de>, spock@wrkof.incom.de (Martin Georg) writes: > 2) Recently, another friend of mine bought a Seagate ST-1096N SCSI > harddisk (3,5", 85MByte, 18ms) and planned to use that driver with > his old Revision C Apple SCSI card on his IIgs. Formatting and parti- > tioning with the Advanced Disk Utilities worked fine, and even in- > stalling the System Softwar with the Installer caused no problem. Then > he copied AppleWorks 3.0 onto the harddisk and launched that from a > 8Bit program launcher. That also worked OK. But when he tries to boot > the harddisk into GS/OS the system crashes on bootup after 3/4 of the > red boot thermometer into the monitor. I think that Apples SCSI driver > must have some timing problems with that very fast harddisk... Does > someone know more about that problem??? Perhaps Dave or Matt, haven't > you got some reports on that??? Does he have the INNERDRIVER driver installed? He will have to remove it. I experienced this problem when I got my hard drive. The INNERDRIVER and Apple's SCSI driver are incompatible. I don't know why the INNERDRIVER was shipped already in the */SYSTEM/DRIVERS subdirectory on the System 5.0.2 disks but that was a MAJOR headache for me until I finally figured it out. Then again, if he doesn't have the Innerdriver installed, I don't know what the problem is. (The symptoms sound exactly like the problems I had though) -- Joel Sumner GENIE:JOEL.SUMNER These opinions are q4kx@cornella.ccs.cornell.edu q4kx@cornella warranted for 90 days or q4kx@vax5.cit.cornell.edu q4kx@crnlvax5 60,000 miles. Whichever .................................................... comes first. Never test for an error condition that you can't handle.