Path: utzoo!attcan!uunet!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.hardware Subject: Re: MSH, PcPatch, Omnitool fail on my 2000 Message-ID: <15807@cbmvax.commodore.com> Date: 12 Nov 90 19:34:52 GMT References: <08Oct90.151432.944@ckctpa.UUCP> <1285@tardis.Tymnet.COM> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 39 In article liberato@dri.com (Jimmy Liberato) writes: >>In article <08Oct90.151432.944@ckctpa.UUCP> crash@ckctpa.UUCP (Frank J. Edwards) writes: >>I'm not sure where the problem with this is, but the MSDOS-compatibility >>programs don't like my 3000... > >There seem to be certain B2000s that have problems also. MSH, Werner Guenther's >PcPatch 3.5", Project D's Omni Tool (makes diskcopies in PC format), and heavily >CPed games like Shadow... all fail on my system, even when in stock configuration >I had some correspondence with two others with exactly the same symtoms (a hang >requiring a cold boot). I was never able to narrow down what the common factor >was but it definitely seems hardware related. I would be interested in hearing >from any others with similar problems on a 2000. Was there more than one >manufacturer used for the floppy drives? Yes, many different vendors have been used. Some drives meet the spec better than others. At least one doesn't (for example) move the change line until 12ms after the select line goes active, and then moves it slowly. Others pull the change line in a few dozen ns. It's possible that a batch of drives might have an index-sync problem, or be a bit too variable, since normal AmigaDos doesn't use index we might not notice. However, I have checked A3000's and they DO get index pulses, and they look good. Also, some people have reported this problem only exists (for them) under 2.0 on an A3000. I have a theory: Some of these programs aren't specifying the length argument to RAWWRITE correctly, and they're getting rejects on bad length. Under 1.3, it checks an absolute memory location instead of an absolute value, and that memory location usually has a bizarre value in it. This is the cause of some of the a2000/1.3 msdos disk problems. Normally, the problem only shows if you have 1 floppy drive, and doesn't show if you have two or more (due to how memory gets allocated). The alternate theory is that some drives in amigas don't support index sync (properly). Until I get my hands on such a drive, I don't believe it. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"