[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] fVDI issues



Hi,

  you can probably use natfeat "DEBUGPRINTF".
  Joy, why did you remove something and nobody knows it?
  Btw. a documentation (a list of natfeats) is still very bad :-(
  Johan and Konrad, sorry. Joy is very busy and he works on many things
simultaneously.
  Best regars,

           Milan Jurik

On Mon, 9 Feb 2004, Johan Klockars wrote:

> > > By default, Cconws to the screen is used, which would perhaps run into
> ...
> > > port. Or, perhaps even better, to the ARAnyM console (via NatFeat).
> >
> > Well, I finally had an occasion to do it. I set debug device to -1 and
> > uncommented the "debug" directive inside the fvdi.sys. The result:
> >
> > FATAL: EMUL_OP called with bogus opcode 00007135
>
> Apparently support for the 0x7135 (M68K_EMUL_OP_DEBUGUTIL) illegal
> instruction handler has been removed from ARAnyM (on December 15, 2003,
> according to the CVS).
> The definition is commented out in the current version of emul_op.h.  :-(
>
> > Ideas?
>
> The fVDI engine needs to be modified and recompiled.
> It looks like it should be possible to use 0x712a (M68K_EMUL_OP_PUT_SCRAP)
> to do the same job.
>
> These special illegal instructions really should have a bit more
> descriptive names, IMO.  ;-)
> It's not exactly obvious that DEBUGUTIL is a console text output
> function, or that PUT_SCRAP is a limited character by character
> console VT52 output function.
>
> --
>   Chalmers University   | Why are these |  e-mail:   rand@cd.chalmers.se
>      of Technology      |  .signatures  |
>                         | so hard to do |  WWW:      http://www.klockars.net
>    Gothenburg, Sweden   |     well?     |            (fVDI, MGIFv5, QLem)
>
>
>