Path: utzoo!mnetor!uunet!husc6!m2c!ulowell!page From: page@swan.ulowell.edu (Bob Page) Newsgroups: comp.sys.amiga Subject: Re: Fix for empty drives which still clicck AFTER using Klickstart? Message-ID: <6943@swan.ulowell.edu> Date: 9 May 88 12:57:13 GMT References: <12738@tut.cis.ohio-state.edu> Reply-To: page@swan.ulowell.edu (Bob Page) Followup-To: comp.sys.amiga.tech Organization: University of Lowell, Computer Science Dept. Lines: 29 [followups to .tech] erd@tut.cis.ohio-state.edu (Ethan R. Dicks) wrote: >Was a fix ever invented (hardware or software) which corrects the problem? A couple of alternative schemes were proposed (all by Bryce, I think), but weren't too desirable. The best one I heard was to keep a disk in your drive. >Also: will this be fixed under KS1.3? No, as it requires specific drives to work (as you know). I've patched my KS1.3 to not click. I don't use Bryce's code; he does at least 3 things incorrectly for my taste, but his has the advantage of a program you can run, whereas my fix requires DiskZap (sadly, Sectorama, DiskX and DiskCraft can't help) and doesn't check to make sure you're not munging a different version of KS. Let me know if you want to perform the surgery on your KS1.3. Of course it must be disk-based; it would be tough to patch your ROM. Aside to old-time KS hackers ... I purposely munged the checksum to see what the A1000 would do with an invalid KS ... nothing! As if it didn't even check it. So I munged more blocks (ASCII text, not code) and it still booted fine. Whazzup? ..Bob -- Bob Page, U of Lowell CS Dept. page@swan.ulowell.edu ulowell!page