1. SVGA
- Posted by CHARN1407 at AOL.COM
Jun 11, 1998
[Rob]
Would you consider adding support for higher resolution/color graphics
modes in Euphoria? Right now I can access better graphics modes in QBasic
than in Euphoria, which seems kinda funny (I can't seem to get Pete's mode-
setting routine to work on my computer).
2. SVGA
Have you tried graphics_mode(261)? To get into SVGA mode, =
-----code begins-----
atom g_mode -- an atom is required by graphics_mode to indicate success
g_mode =3D graphics_mode(261)
-----code ends-----
This is supposed to get you into SVGA mode. However, my problem is that =
I
can't seem to use the entire screen in this mode.
--Alan
=
3. Re: SVGA
Alan Tu wrote:
[snip]
>This is supposed to get you into SVGA mode. However, my problem is that I
>can't seem to use the entire screen in this mode.
If I understand the problem you describe correctly, then you should try to
add:
use_vesa(1)
to your code before you change to the svga graphics mode. This does the
trick for me, at least.
Einar Mogen
4. Re: SVGA
Sorry to but into this conversation...
>Have you tried graphics_mode(261)? To get into SVGA mode, =
>
>This is supposed to get you into SVGA mode. However, my problem is
that =
>I
>can't seem to use the entire screen in this mode.
>
>--Alan
> =
I have this same problem in modes 256, 257 and on up:
The graphics only appears on a strip of stcreen at the top only
about an inch and a half wide (about 4 or 5 cm) and wraps vertically
over itself.
for this reason most of my programs are in mode 18 or 19.
just thougt I would mention this: is there anything I can do
about it?
Lewis Townsend
|\ ____ _ _ _ _ __
| \ | __/ || / | // || / __ \
| \ ||_ || //|| // || ||__\|
| \ | _| || // || // || \___ \
| |\ \ ||__ ||// ||// || |\__||
| | \ \|___\ |_/ |_/ || \____/
| | \ \ _____ ________
| | \ \ | __ \ | __ __ |
| | \ \ ||__|| |/ || \|
| | \ \ | __ / ||
| |______\ \ || \\ ||
|___________\ || || ||
Keroltarr at hotmail.com
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
5. Re: SVGA
- Posted by CHARN1407 at AOL.COM
Jun 12, 1998
Lewis: It seems to me that your SVGA programs are not switching banks
correctly. Since SVGA modes use higher resolutions and more colors than VGA,
they use more memory. The video memory on a computer starts at #A000 and goes
either 64 or 128 KB. When the graphics mode needs more than that, it needs to
switch banks of memory so it can write to a different part of the screen.
Euphoria's graphics routines will handle this automatically but if you are
using a graphics library that is fast because it copies memory to #A000 it
might not support that and keep on writing to the same bank over and over.
Either use Euphoria's built - in routines or DOS interrupt #104F05. To use
this, I set AX to #4F05, BX to 0, and DX to the 64KB window I want to change
to, then call Interrupt #10. It is successful if AX returns #4F. This is
copied off my QBasic routine, so if there need to be any changes for 32 bit
ASM, would someone please help me out?
TIA,
CHARN
6. Re: SVGA
- Posted by Michael Raley <mjronline at IT-WORKS.COM>
Jun 12, 1998
-
Last edited Jun 13, 1998
This could also be because the refresh rate settings for your video card do
not match what your monitor uses...
-----Original Message-----
From: Lewis Townsend <keroltarr at HOTMAIL.COM>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: Friday, June 12, 1998 8:17 AM
Subject: Re: SVGA
>Sorry to but into this conversation...
>
>I have this same problem in modes 256, 257 and on up:
>The graphics only appears on a strip of stcreen at the top only
>about an inch and a half wide (about 4 or 5 cm) and wraps vertically
>over itself.
>
>for this reason most of my programs are in mode 18 or 19.
>just thougt I would mention this: is there anything I can do
>about it?
>
>Lewis Townsend
>|\ ____ _ _ _ _ __
>| \ | __/ || / | // || / __ \
>| \ ||_ || //|| // || ||__\|
>| \ | _| || // || // || \___ \
>| |\ \ ||__ ||// ||// || |\__||
>| | \ \|___\ |_/ |_/ || \____/
>| | \ \ _____ ________
>| | \ \ | __ \ | __ __ |
>| | \ \ ||__|| |/ || \|
>| | \ \ | __ / ||
>| |______\ \ || \\ ||
>|___________\ || || ||
>Keroltarr at hotmail.com
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
7. Re: SVGA
The higher rez modes run at different sync rates than the
normal VGA. If your monitor is not equipped to handle these
rates, don't use these modes! Apparently, some monitors can
be damaged - I guess by overheating. Anyway, If you get
the narrow band on the screen, either do a MODE CO80 or
ctl-alt-del to get out before the smoke curls up.
Irv
At 10:44 PM 6/12/98 -0700, Michael Raley wrote:
>This could also be because the refresh rate settings for your video card do
>not match what your monitor uses...
>
>>Lewis Townsend wrote:
>>Sorry to but into this conversation...
>>
>>I have this same problem in modes 256, 257 and on up:
>>The graphics only appears on a strip of stcreen at the top only
>>about an inch and a half wide (about 4 or 5 cm) and wraps vertically
>>over itself.
>>
>>for this reason most of my programs are in mode 18 or 19.
>>just thougt I would mention this: is there anything I can do
>>about it?
>>
8. Re: SVGA
>The higher rez modes run at different sync rates than the
>normal VGA. If your monitor is not equipped to handle these
>rates, don't use these modes! Apparently, some monitors can
>be damaged - I guess by overheating
I have read that it is maybe not overheating but forcing the guns in your
monitor that fire the electrons at the screen to do things they should not
be doing, and this maybe bends them, or puts them out of whack somehow.
Monty in Oregon
9. Re: SVGA
- Posted by Falkon <Falkn13 at IBM.NET>
Jun 13, 1998
-
Last edited Jun 14, 1998
From: Alan Tu
>This is supposed to get you into SVGA mode. However, my problem is that
>I can't seem to use the entire screen in this mode.
From: Lewis Townsend
>I have this same problem in modes 256, 257 and on up:
>The graphics only appears on a strip of stcreen at the top only
>about an inch and a half wide (about 4 or 5 cm) and wraps vertically
>over itself.
1. call use_vesa(1) before making any graphics calls
if that doesn't fix it,
2. Run a pc diagnostics program to find out what company brand/chipset of
video card you have. (if you don't already know) Go to that manufacturer's
web page and look for a DOS-mode VESA VBE driver for that chipset/card.
A lot of svga cards require driver programs to use svga modes in DOS.
Since computers come with Win95 now, which has built-in drivers, most pc
makers don't bother including the DOS drivers, hoping that you'll never try
to use DOS and discover that they left out important system software. Most
video-card makers have the necessary drivers freely available for download
though.
Alternatively, you could use Sci-tech's Display Doctor, it works with a lot
of different cards. Or if you've got a DOS-mode SVGA game that works fine
on your system, you probably already have the driver you need somewhere in
the game's disk/directories.
Hope that helps...fixed the problem for me.
10. Re: SVGA
I ran the older MSD program. This is what I got.
Video Adapter Type: VGA
Manufacturer: Phoenix
Model:
Display Type: VGA Color
Video Mode: 3
Number of Columns: 80
Number of Rows: 25
Video BIOS Version:
Video BIOS Date: 06/20/97
VESA Support Installed: Yes
VESA Version: 1.02
VESA OEM Name: Trident TGUI96xx
Secondary Adapter: None
Could the video adapter type being "VGA" mean I couldn't use SVGA properl=
y?
I doubt it (the card is a new one), but one never knows these days. (My=
monitor is two years old). Would I try to find "Phoenix"'s web site or
"Trident"'s? I am running a DOS session under Win95. Does the VESA bein=
g
installed mean anything?
--Alan
=
11. Re: SVGA
Thanks CHARN, for the help...
>Lewis: It seems to me that your SVGA programs are not switching banks
correctly.
Is this a Euphoria problem or Dos or something else?
Or my hardware?
>Either use Euphoria's built - in routines or DOS interrupt #104F05.
How do I do this? I've never used interupts or assembly.
Do I do this at a command prompt?, use system(), or call
a machine function or what?
To use
>this, I set AX to #4F05, BX to 0, and DX to the 64KB window I want to
change
>to, then call Interrupt #10. It is successful if AX returns #4F.
This is
>copied off my QBasic routine, so if there need to be any changes for 32
bit
>ASM, would someone please help me out?
>
>TIA,
>
>CHARN
Sorry I can't help you in return but thanks again anyway.
Lewis Townsend
LewisArt
PS Sorry about this being kind of a late reply, I still
have over 200 email messages from my summer vacation.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
12. Re: SVGA
Hello again,
>The higher rez modes run at different sync rates than the
>normal VGA. If your monitor is not equipped to handle these
>rates, don't use these modes! Apparently, some monitors can
>be damaged - I guess by overheating. Anyway, If you get
>the narrow band on the screen, either do a MODE CO80 or
>ctl-alt-del to get out before the smoke curls up.
>
>Irv
Hmm... My monitor is SVGA and I've ran lots of high res and
high color programs without any problem...
except for programs written in Euphoria... and even those
have never caused any damage to my monitor that I could tell.
I've even tried to ignore this problem in some progs and have
ran them for a minute or more before I gave up because I
couldn't find the buttons to click and other inconveiniences
that acommpanies the equivalent of reading a paper document
that is still folded up ;)
I would really like to use some of the higher graphic modes
if at all possible in the games I am working on, so if there
is a solution please let me know. If one has already been
posted then I just haven't got to it yet. CHARN's sounded
plausable but I just don't know how to impliment it.
TIA,
Lewis Townsend
LewisArt
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
13. Re: SVGA
>1. call use_vesa(1) before making any graphics calls
>if that doesn't fix it,
>2. Run a pc diagnostics program to find out what company brand/chipset
of...
Thanks Falkon, I'll try that
Lewis Townsend
LewisArt
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
14. Re: SVGA
From: Alan Tu
> Video Adapter Type: VGA
> Manufacturer: Phoenix
> VESA Support Installed: Yes
> VESA Version: 1.02
> VESA OEM Name: Trident TGUI96xx
>Could the video adapter type being "VGA" mean I couldn't use
>SVGA properly?
No, SVGA is merely an extension of VGA. Type VGA means
that it is indeed backward compatible with VGA.
>Would I try to find "Phoenix"'s web site or "Trident"'s? I am
>running a DOS session under Win95.
Phoenix makes the video cards, and the BIOS for standard
VGA. Trident makes the chipset on the card which handles
SVGA, modes greater than 19. I think that's how it works
anyway. I'm not really into the corporate politics. I just know
they make a mess for us end users.
This page gives the details about the relationship.
The FAQ page will give you more answers.
According to the FAQ you need a TSR called VESA.EXE
which they evidently forgot to put on their website. I did
find it at
A.EXE
But that's made for another chipset. Of the same company
and to the same VESA version, though, so it might work.
It's 12.5k.
Or, possibly better, is ftp://ftp.netcom.com/pub/ac/accolade/vesa/uvesa.exe
That's a universal VESA VBE driver that uses VESA 1.2 and might work
better. It's 22.4k
>Does the VESA being installed mean anything?
That means it's capable of using VESA...if you write your program
specifically for that video card using machine code. In which case the
program wouldn't work with any other video cards. Or if you use
Windows drivers which only work in Windows. Or if you use a TSR
driver to translate standard VESA VBE codes into that card/chip's
specific codes. That's what you need for DOS-mode SVGA.
Some newer cards have the driver built into the card's ROM chips,
unfortunately most don't.
BTW, if other DOS-mode programs run in SVGA okay, it's because
they have a built-in driver or they came with one that they load up as
the program starts.
Falkon, wishing the creators of SVGA hadn't made such a mess of
the whole thing...
15. Re: SVGA
- Posted by CHARN1407 at AOL.COM
Jun 21, 1998
Alan,
your program has to tell the computer to switch the SVGA banks. Look at
Pete's SVGA.E to see how to do it, it'll work pretty well but is a bit
complicated. to just call the dos interrupt like i said earlier, i believe
you would use dos_interrupt(). I don't know how to implement this in Euphoria
yet because i'm new to the language and am more comfortable with QBasic.
Maybe someone else can post a solution (ahem, hint, hint)
--CHARN
