Path: news.uiowa.edu!chi-news.cic.net!newsfeeder.sdsu.edu!hookup!news.mathworks.com!hunter.premier.net!news.uoregon.edu!cie-2.uoregon.edu!nparker From: nparker@cie-2.uoregon.edu (Neil Parker) Newsgroups: comp.sys.apple2.programmer Subject: Re: Q: Ensoniq & mouse softswitches Date: 5 Jul 1996 09:15:35 GMT Organization: University of Oregon Campus Information Exchange Lines: 29 Distribution: world Message-ID: <4rimfn$q3o@pith.uoregon.edu> References: <4re2sb$ahk@elna.ethz.ch> NNTP-Posting-Host: cie-2.uoregon.edu In article <4re2sb$ahk@elna.ethz.ch> GUDATH@EZINFO.VMSMAIL.ETHZ.CH (Henrik 'Ratte' Gudat) writes: >[...] >b) The Firmware Ref and the Hardware each state exactly the opposite. When >reading C024 (X/Y mouse deltas), which value comes first? Is it.. > > i) C027: first bit 1 is 0 and C024 contains X data, then > bit 1 is 1 and C024 contains Y data, or > > ii) C027: first bit 1 is 0 and C024 contains Y data, then > bit 1 is 1 and C024 contains X data ? The Firmware Reference is correct, i.e. your choice number 1. I verified this by disassembling the READMOUSE call. I've usually found that the Firmware Reference is much more reliable than the Hardware Reference (I can't testify about the second edition of the Hardware Reference, but the first edition is crawling with errors, not all of which are fixed by IIGS Technical Note #30). But even the Firmware Reference isn't perfect...there are a handful of facts that are wrong in both manuals, such as the descriptions of the DISKREG ($C031) and CLOCKCTL ($C034) I/O locations. - Neil Parker -- Neil Parker | No cute quote, no cute ASCII art, no cute nparker@cie-2.uoregon.edu | disclaimer, no deposit, no return.... nparker@cie.uoregon.edu | (This space intentionally left blank: http://cie-2.uoregon.edu/~nparker | )