Re: [MiNT] Problem with FVDI (?)

[Johan Klockars <johan@klockars.net>]

> code stops right after displaying the MiNT's welcome message, waits for 4
...
> Everything is OK, if there is no fVDI loaded. After fVDI has been loaded (I

Is this on a standard Falcon, under ARAnyM or perhaps with an Eclipse/RageII?

> load it before MiNT) all the Cconws() output stops immediately and nothing
> appears on the screen until some point near the end of MiNT initialization,
> i.e. apparently before the MiNT generates enough messages; all gets then
> printed to the screen. It looks as if fVDI bufferred the Cconws() output and
> flushed the buffer just after it had become full. The effect is, that if the

fVDI does not touch GEMDOS or BIOS at all. It does hook onto the XBIOS
vector, but only to deal with Physbase, Logbase and Getrez (and that only
if 'xbiosfix' is active), and the lineA vector to (mostly) disable it.

That is, fVDI itself can not affect GEMDOS/BIOS text output in the way
you are describing. It can, however, make such output crash the machine
(since fVDI can be told to modify various lineA variables, and the screen
address, which will cause the TOS text output routines to become confused).

Personally, I usually keep the GEMDOS/BIOS text output going to my
SM124 monitor while the VDI displays via the RageII on another monitor.
This is what you'll get if you don't specifically tell fVDI to do
otherwise ('lineafix' and 'xbiosfix'), or run some kind of Bconout
redirecting program (like my BCONOUT.GTP, for example).

-- 
                        | Why are these |  e-mail:   johan@klockars.net
                        |  .signatures  |
                        | so hard to do |  WWW:      http://www.klockars.net
                        |     well?     |            (fVDI, MGIFv5, QLem)