Path: utzoo!attcan!telly!lethe!torsqnt!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!aablue!jb From: jb@aablue.UUCP (John B Scalia) Newsgroups: comp.sys.ibm.pc Subject: Re: IBM-AT BIOS ROMS Summary: Yeah, but get the right version Keywords: 3085 Disk Manager Message-ID: <603@aablue.UUCP> Date: 22 Sep 89 02:17:45 GMT References: <1989Sep19.021545.8110@NCoast.ORG> <[2058.1]comp.ibmpc;1@point.UUCP> <1658@psuhcx.psu.edu> Reply-To: jb@aablue.UUCP (John B Scalia) Distribution: na Organization: A A Blueprint Co., Inc. - Akron, OH Lines: 30 In article <1658@psuhcx.psu.edu> wcf@psuhcx.psu.edu (Bill Fenner) writes: >In article <[2058.1]comp.ibmpc;1@point.UUCP> wek@point.UUCP (Bill Kuykendall) writes: >|>in the BIOS tables (only 14 are in the tables). I prefer not to use >|>a TSR such as Disk Manager. Fortunately (or unfortunately) I have a >| >|Huh? DM isn't a TSR, but it doesn't cover miniscribes so it won't help >|anyway. >Sure it does. Just get the miniscribe version. Anyone know of any versions > [deletions...] As someone who's had to go through this with a very unhelpful OnTrack techie, just make sure you've got DM Version 3.6 or higher. One of my glorious distributors sent me a 3085 (which I should mention is what the original poster is using) enclosed with DM Version 3.3. It appeared to format the drive perfectly, but after logical format and software loading, it wouldn't do anything on reboot. We even tried it 3 times before we called. Anyway, OnTrack just claimed the drive was probably defective, until I prodded them about "What's your current version numbers up to?" PS. I don't normally even bother with 3rd party stuff like DM. Sneer as I might at some of Everex's botched attempts, their Disk Utility package is pretty robust. It permits using the CMOS numbers or defining on-the-fly. Of course, we only discovered this AFTER our first 3085 :-) :-) jb@aablue -- A A Blueprint Co., Inc. - Akron, Ohio +1 216 794-8803 voice UUCP: {uunet!}aablue!jb Sometimes they do let me speak for the company, not today though.