From:	"A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Allegro bank switching -- Please read
Date:	Wed, 06 Nov 1996 10:38:05 -0500
Organization:	Cornell University
Lines:	52
Sender:	asu1 AT cornell DOT edu (Verified)
Message-ID:	<3280B0DD.37A8@cornell.edu>
NNTP-Posting-Host:	cu-dialup-0052.cit.cornell.edu
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii said:

" Will somebody with a few minutes to spare please change these two
offending lines in Allegro distribution and upload the fixed zip file to
DJ's /incoming directory?  Please??  This threatens to become a FAQ, but
I'm too ashamed to put it there, since it's a ridiculous problem.  
Thanks. "

and Roger Thompson followed up with:

" The two lines are in the MACH64 procedures. easy to find and fix,
works fine once those two lines are edited.. "

eli, i don't understand your attitude ... and roger, did you actually
run any of the tests or the demo programs to see if those programs
worked after making the change?

here is my "ridiculous" problem: i thought everyone around here knew
that successful compilation does not mean you have a working program.
obviously everything compiles fine once you change the lines from
incl %ah to incb %ah. however, the same is true if you change them to
incw %ax or incl %eax. the catch is, no matter which one of the changes
i make, both the demo program and the test program crash (usually with a
blank screen but sometimes with a narrow band of garbage pixels on the
screen. i even got a SIGSEV once after i built the whole thing using
incl %eax.) all the programs seem to run without problems under the vbe
2.0 emulator from ati.

i could not try this out yesterday because i did not have a machine with
a mach64 around. but i posed the same question then, too: which one of
these is correct? and the correctness does not depend on matching the
opcode and operand, it depends on what is correct for the given video
hardware.

so, it seems to me, however retarded i may sound, there is another bug
in the mach64 routines. but, i just do not know what.

to conclude, i would REALLY appreciate if someone who has access to the
hardware and who got the demo and test programs to run successfully on a
mach64 comments on this and enlightens me. under normal circumstances, i
would ask shawn directly but i recall that he does not have an e-mail
account these days.

sinan.
-- 
*******************************************************************
 A. Sinan Unur                                WWWWWW
                                              |--O+O
 mailto:asu1 AT cornell DOT edu                      C   ^ 
 mailto:sinan AT econ DOT cit DOT cornell DOT edu             \  ~/ 
 http://www.bqnet.com/sinan/
*******************************************************************

- Raw text -