[ColorForth] Graphic compability
- Subject: [ColorForth] Graphic compability
- From: "Jimmy Söderman" <hiraganagos@xxxxxxxxxxx>
- Date: Sun, 16 Jun 2002 20:11:37 +0000
- Bcc:
Regarding hints on that Graphics modification, ill have to get back to you,
becuase i havnt understood the complete source myself, far from it, so i
rather not mess with it yet, also a problem i code in NASM, not MASM (lots
of names there), timeconsuming.
I just wante to get some wheels turning while im trying aswell.
The more the merrier ;)
But what i do know is this, that snippet has never ever failed me this on
setting a graphics mode, even portables from 1999+ no problems, so its
defintly worth a shoot, & indeed opens up who can use ColorFORTH if its the
graphics thats the problem.
Btw. while im at it i want to mention a MASM2NASM converter wich i
unfortunly couldnt get to work as i wanted, anyone else up for it?
NASM is nicer, cleaner, simpler syntax, and open source , wich follows FORTH
philosphy more too imho.
With this said i hope many others than me would like to see a NASM
conversion of ColorFORTH.
Link: http://strawberry.cs.uwyo.edu/~cosc2150/files/m2nasm/
for the heck of it ill post other translators, those allways gets handy:
http://www.niksula.cs.hut.fi/~mtiihone/intel2gas/
http://membres.lycos.fr/placr/a2i.html
http://www.bumba.net/~hmaon/a2i/
From: Bob Shafer <bobsh@xxxxxxxxx>
Reply-To: ColorForth@xxxxxxxxxxxxxxxxxx
To: "ColorForth List Member" <ColorForth@xxxxxxxxxxxxxxxxxx>
Subject: [ColorForth] Graphic compability
Date: Sun, 16 Jun 2002 12:21:18 -0700
I've made a couple of quick attempts at fixing up the source to do things
like you describe. Unfortunately, I really don't know what I'm doing,
assembler-wise (more hints would be appreciated :-). It would be really
neat if this modification would open colorForth up to more people. Has
anyone tried this technique, got it working where colorForth already works,
and then taken it to a machine where the original doesn't work, with
success?
At 09:46 AM 6/16/02 +0000, you wrote:
As i discovered there is more or less serious incompability with
graphiccards & ColorFORTH, and i hope ive spotted the "problem",
i might be wrong though., Ok im now going rather technical, so here we go:
It seem to use (VESA) VBE BIOS to set its graphicsmode, but hardware
probing for getting the actual startaddress of grahics.
VBE utilizes a standarzed way to get to that, without probing, ill post a
snippet ill used succesfully in my own projects, and Chuck, or someone
else might wanna test it.
As its a standard way since 1996-1998 and now works on 99.9% graphics
cards (S3 and onwards).
Put into Boot.asm (i guess would need other changes too, so its just an
suggestion.)
mov di,ModeInfoTable ; 256 byte table needs reserved anywhere in memory.
mov ax,04f01h
mov cx,4114h ; 800x600 ( use 4117h if you want 1024x768 )
int 10h
mov ax,04f02h
mov bx,4114h ; 800x600 ( use 4117h if you want 1024x768 )
int 10h
And now, later when in 32bit mode, and you want to have the
graphicaddress, just fetch 32bit-address at ModeInfoTable+20h, no
hardwarespecific probing needed.
_________________________________________________________________
Skicka och ta emot Hotmail-meddelanden på din mobilenhet:
http://mobile.msn.com
------------------------
To Unsubscribe from this list, send mail to Mdaemon@xxxxxxxxxxxxxxxxxx
with:
unsubscribe ColorForth
as the first and only line within the message body
Problems - List-Admin@xxxxxxxxxxxxxxxxxx
Main ColorForth site - http://www.colorforth.com
------------------------
To Unsubscribe from this list, send mail to Mdaemon@xxxxxxxxxxxxxxxxxx
with:
unsubscribe ColorForth
as the first and only line within the message body
Problems - List-Admin@xxxxxxxxxxxxxxxxxx
Main ColorForth site - http://www.colorforth.com
_________________________________________________________________
Skicka och ta emot Hotmail-meddelanden på din mobilenhet:
http://mobile.msn.com
------------------------
To Unsubscribe from this list, send mail to Mdaemon@xxxxxxxxxxxxxxxxxx with:
unsubscribe ColorForth
as the first and only line within the message body
Problems - List-Admin@xxxxxxxxxxxxxxxxxx
Main ColorForth site - http://www.colorforth.com