Re: Seeing the Vesa mode on start-up/changeing same.

Hi Nick, All!
It's Ray... go to bottom :-)

On Thu, Jul 3, 2008 at 8:44 AM, Nick Maroudas
<[email protected]> wrote:
> Quoting "Ray St. Marie" <[email protected]>:
>
>>... " Hi colorForth fans
>>... " Ray here...
>>... "
>>... " I've been offline a couple of weeks... recent
>>... " blog entry about that at
>>... " http://colorforth.net
>>... " I've been busy in my offline time working with a
>>... " [snip]
>>... " ... few of  the problems that I've seen pop up
>>... " recently in this
>>... " mailinglist. .... Also, I've created
>>... " a couple words to aid
>>... " in the display debugging process. Nick, I was
>>... " thinking of you. :-)
>>... "
>>... "
>
> Nick here,
>
> Dear Ray,
>
> Thanks for thinking of me, though I've been off line
> even longer than you; and missed a lot of good stuff -
> including the CF Community website above.
>
> Reason for absence was to prepare a ms and submit it
> for
> publication, on the hex scale of music notation for
> which I've been using CF lately.  I mailed you a floppy
> with my CF program a few months ago, now the ms is
> available for anyone who might be interested in a hex
> alternative to the usual MIDI scale in logarithmic
> cents.
>
> Your work on vesa and LOGO display is certainly of
> interest to the "Play and Display" part of my program.
>
> So is Jason's on how to set a pixel.  Should lead to
> even smaller lag between displaying the score and
> playing the notes.
>
> Will need some time to absorb all this new stuff:  at
> my
> age short term memory becomes as volatile as RAM - and
> much, much slower to refresh.
>
> Caritas,
>
> Nick
>
> Also Quoting:  Wed, 28 May 2008 14:01:23 +0100
> Jason Kemp <[email protected]>
> Re: [colorforth] Setting a pixel on the screen
>
> ****************************
>
> A better world is not only possible but on the way.  On
> a quiet day you can hear her breathing.  - Arundhati
> Roy
>

I've been annotating a listing of the MASM generated colorForth 1 that
I did form the Pentium 4. I got to the part about int 10 -- the
display set-up interrupt and had a thought.

The monitor that I had seemed to recreate Nick's display problem is
EGA/XGA. Nick, please check yours as well. In the case that it is, we
will need to enter a new display mode setter other than 0x4F02H, which
is specifically VBE, the Vesa superVGA setting setter. VESA monitors
seem to be set to 0x117h, 0x118h, and 0x123h successfully.

I don't believe anyone has tested the EGA/XGA settings.
Wikipedia has this to say: http://en.wikipedia.org/wiki/XGA

My projects are many and I keep flipping from one to the next. I do
have an XGA monitor, and if we can get some concensus on how to
preceed here, I'll try out some of those ideas.

BUT, I suggest a VESA-VBE superVGA monitor. Used, they are cheap. Bet
you can find one in a friends garage if not your own. :-)

Getting the superVGA means not having to worry about hacking the
already well tested code.

Much luck!
Ray
-- 
Raymond St. Marie ii,
http://colorforthray.info
http://colorForth.net
http://ForthWorks.com/c4th