Re: [MiNT] v_clrwk() doesn't work with fVDI

[Eero Tamminen <oak@helsinkinet.fi>]

Hi,

Paul, you mailed these to emutos devel list, was that by accident?

	- Eero

On keskiviikko 05 syyskuu 2012, Paul Wratt wrote:
> bah - there are no files in it yet .. should have checked first..
> trying to get it sorted now
> 
> On Wed, Sep 5, 2012 at 4:37 PM, Paul Wratt <paul.wratt@gmail.com> wrote:
> > ok after much mucking around, I found FVDI on SourceForge, as of May
> > 2012 (I think)
> > http://sourceforge.net/projects/fvdi/
> > 
> > its SVN now, but at least it is accessable. If someone (or a couple)
> > on this list were to use SF to request repo access, commits should be
> > possible too
> > 
> > Johans website is down, incl. the IP address, and the last dns update
> > is May 2011, so it may be permanant (altho it is homepage link on FVDI
> > project page)
> > http://www.klockars.net/
> > 
> > Anyway, it good to know where it is now
> > 
> > Paul
> > PS Helmut can you post ur FVDI source patch/fix somewhere, even attach
> > it to SF tracker for FVDI
> > 
> > On Wed, Sep 5, 2012 at 3:48 PM, Paul Wratt <paul.wratt@gmail.com> wrote:
> >> If Helmut is still reading the list maybe he can supply his fixed
> >> source version fvdi [1] and one of us can get it up on AtariForge
> >> 
> >> I did have the last cvs copy, and altho in the past the cvs was not
> >> available, it was up the last time I check it (Jan/Feb 2012)
> >> 
> >> when (if) the FVDI source is in a repo, the ARAnyM list should be
> >> notified too, and some access given immediately
> >> 
> >> At least it would be done and some people can start working on it (and
> >> video card drivers)
> >> 
> >> Paul
> >> 
> >> [1] fixed for open workstation and (properly/actually) close from auto
> >> folder, and before MiNT runs
> >> 
> >> On Wed, Sep 5, 2012 at 9:47 AM, Eero Tamminen <oak@helsinkinet.fi> 
wrote:
> >>> Hi,
> >>> 
> >>> I found another issue when running with fVDI
> >>> (in Aranym AFROS).
> >>> 
> >>> Calling v_clrwk() doesn't clear the screen like
> >>> it does without fVDI, with all the TOS versions
> >>> and also with NVDI (v2.5).
> >>> 
> >>> Attached test program demos that and also the previous
> >>> v_exit_cur() crash.
> >>> 
> >>> Without fVDI:
> >>> - it clears screen
> >>> - after key press it calls v_exit_cur()
> >>> - after another key press it exits.
> >>> 
> >>> With fVDI:
> >>> - screen isn't cleared i.e. instruction text is printed
> >>> 
> >>>   on top of what's on screen
> >>> 
> >>> - after pressing the key, the program crashes to bus error.
> >>> 
> >>>         - Eero
> >>> 
> >>> PS. Next step will be building my EmuTOS VDI testers without
> >>> v_exit_cur() call to see whether there are drawing bugs like
> >>> EmuTOS had.
> 
> -------------------------------------------------------------------------
> ----- Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Emutos-devel mailing list
> Emutos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emutos-devel