Path: utzoo!attcan!uunet!mailrus!wuarchive!decwrl!ucbvax!UREGINA1.BITNET!CRONEJP From: CRONEJP@UREGINA1.BITNET (Jonathan Crone) Newsgroups: comp.sys.amiga Subject: The latest in the Microbotics-Maxtor Saga Message-ID: <8911220047.AA14002@jade.berkeley.edu> Date: 22 Nov 89 00:37:46 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Well lets see.... you can all recall that I've posted several messages detailing difficulties with getting a Maxtor LXT-100S to work with the Microbotics HardFrame controller. Now we can get the thing to mount, more or less... Specifically what we've done is to set the unit number to 6 (supposedly the HardFrame is unit 7) and instead of just straight executing binddrivers, we RUN BINDDRIVERS (thanks dt@..... for the hint) The Binddrivers never completes executing, but the hardFrame device driver gets into memory... Thus, at least the system doesn't Guru at this point... At this point, we execute FORMATHF... which gurus as soon as it tries to Low Level the drive.... 0000004 etc. etc. etc. We tried low leveling the drive with my personal Comspec SA1000 (which incidently, has FAR MORE ROBUST software.... (We've done dozens of drives with it... and its NEVER smoked itself EVER) (Hell of a lot more reliable than the MicroBotics stuff...))) ((((Editorial off....))))) and it low leveled ok... the drive was reinstalled on the Hard Frame, and RDPREP was executed.... and it promptly Gurued. Its no wonder that people get annoyed with amigas some times.... Software shouldn't just quit and guru if it runs into something it isn't expecting.... Someone offered me a Beta Version of RDPREP.... i'd appreciate it if possible please.... (along with any beta Device driver s/w as well, as the damn thing never does return from BindDrivers....) thanks all.... If you can come up with some ideas i'd appreciate it.... JpC -------------------------------------------------------------------- Jonathan P. Crone CRONEJP@UREGINA1.BITNET Amiga-L@uregina1.bitnet List moderator. Heisenberg might have been here...