Re: colorforth 2.0a for stand-alone and Windows use

Dear Ray, 

In answer to my present problem (the screen is 2X too
big) you wrote:  

Quoting "Ray St. Marie" <[email protected]>:

>... " 
>... " There seems to me to be another place in the
>... " kernel where the display is sized.
>... " 
>... " When you changed to 0x4117 vesa you may have
>... " also had to contend with
>... " sizing the screen as well. As I recall, there is
>... " a different sizing
>... " for Windows ( longer screen ) then in the
>... " native.
>... " 
>... " We still don't have a good picture of the kernel
>... " at this point.
>... " 
>... "  Much fun to you.
>... " Ray
>... " 
>... " 

Nick here:  I agree that the solution to my problem
might be found in the kernel - probably around "emit". 
Because when I redefined "5x" and hence "cf" in block
26, to use "emit" (instead of "2emit") and rebooted,
the words "color forth" in the logo still came out
double size - even though blocks 26 and 28 were now
printing "cf" with "emit" instead of "2emit". So
somewhere in the new kernel (or in the Win wrapper?) is
a scale factor of 2.  I don't see how it could be
associated with my VESA call 4117 because that never
caused trouble in CF01 or CF05; also, "emit" itself is
unlikely to have been redefined in the new kernel - so
I guess it might have something to do with Windows, as
you suggest.

The Win-version is smoooth, and your proposals would
make it even smooooother, but (until a SeaForth 
pendrive comes my way) I want to stick to native stand
alone CF because it gives "privileged I/O" (as the
Instruction doc says).  One needs all the "privilege"
one can get, when one is trying to synthesize Play and
Display in four-part harmony without using DMA.

Caritas,

Nick