Re: Mockingboard emulator (was: Late night musings...)

[hochstrasse@ubaclu.unibas.ch (Urs Hochstrasser)]

In article <50itqc$9bt@news.bconnex.net>, jefbla@bconnex.net (Jeff
Blakeney) wrote:

[snip]
 
> I was thinking along the lines of "dissassembling" the code opcode by
> opcode and checking to see if that instruction will cause an access to
> a special area, such as the slots or softswitches, or is a branch or
> jump instruction.  If the instruction is NOT one of the above, it
> would be placed into an "execution" buffer and the next instruction
                           ^^^^^^^^^^^^^^^^^
What do you think of the following method: 
1. You scan the code in place with your disassembler-like program for
   'special cases'
2. You patch the program directly in memory with a JSR into your own
   code when such a "special case" is encountered
3. You execute the modified program at full speed
This way there may be a little delay on launch, but the program itself
should execute at a fairly high speed.

Just my 3 cruzeiros

Cheers
--Urs

_____________________________________________________________________
Urs Hochstrasser   ('Cody')    internet: hochstrasse@ubaclu.unibas.ch
Official Computer Wizard (CV) of the Botanical Institute Hebelstrasse
                  University of BASEL (Tel int. 7 23 32)
                webmaster of http://www.unibas.ch/bothebel
_____________________________________________________________________