On Thu, 11 Jun 2015 14:22:03 -0400, Rugxulo wrote:
>
>
> No, I don't think so. You'd (usually) have to use raw assembly. Maybe
> you could do limited stuff with debug, dunno. (Obviously you can call
> interrupts with debug or do a few other arcane things, but it's not
> nearly as good as a full
Hi,
On Thu, Jun 11, 2015 at 12:52 PM, Dale E Sterner wrote:
>
> Most of my best dos software requires vesa. Your link was extremely good.
There's a lot of (defunct?) legacy out there, especially for DOS. So
we're really only scratching the surface.
> I wish it was in a nice text book that I cou
Most of my best dos software requires vesa. Your link was extremely good.
I wish it was in a nice text book that I could sit down and read.
Not very much into windows stuff even if it is better.
I miss the vic 20 where I could poke into the video and make it
look like anything I wanted. Question co
Hi,
On Tue, Jun 9, 2015 at 3:50 PM, Dale E Sterner wrote:
>
> Another dumb question; are there any good books out there about Vesa.?
You mean actual physical books? Just documenting the spec or
demonstrating use or example programs or ... ? I could be wrong, but I
assume you mean the DOS-oriente
Hi,
On Wed, Jun 10, 2015 at 1:50 PM, John Hupp wrote:
> On 6/10/2015 10:28 AM, John Hupp wrote:
>
> I am nonetheless happy to have a few things to work with to better match
> an LCD's aspect ratio: Eric's trick, for instance, on cards that support
> it. And I can also report that Japheth's setmx
On 6/10/2015 10:28 AM, John Hupp wrote:
> It seems like I still have some things to try, however. Rugxulo
> suggested two utilities that may or do use other methods: setmxx and
> svgatextmode.
>
An important discovery -- the Oak ISA card that was the source of so
much of this discussion appear
On 6/9/2015 6:31 PM, Eric Auer wrote:
> Hi John,
>
>> ... Does "mode con lines=34" require anything besides VESA support? I
>> concluded from my reading that it did not need DISPLAY.SYS or [ANSI]
> Here is a quick trick with mode:
>
> MODE CON LINES=1
>
> (or any other weird value) lists possible v
Every search I've done for Vesa book came up empty.
Libraries just don't keep books for long. If the copyright
is over 5 years old they toss it - really dumb. There's alot
of good old stuff.
cheers
DS
On Tue, 09 Jun 2015 17:11:06 -0400 Felix Miata
writes:
> Dale E Sterner composed on 2015-06-09
Hi John,
> ... Does "mode con lines=34" require anything besides VESA support? I
> concluded from my reading that it did not need DISPLAY.SYS or [ANSI]
Here is a quick trick with mode:
MODE CON LINES=1
(or any other weird value) lists possible values in the error message.
MODE CON LINES=30
d
Does "mode con lines=34" require anything besides VESA support? I
concluded from my reading that it did not need DISPLAY.SYS or
N/ANSI.SYS, but if it does, then I've been tripping over fundamentals.
--
_
On 6/9/2015 5:20 PM, John Hupp wrote:
> On 6/9/2015 1:08 PM, Felix Miata wrote:
>> John Hupp composed on 2015-06-09 12:46 (UTC-0400):
>>
>>> To fix that I suppose I would need to come up with a Vesa driver for
>>> the
>>> card, and would welcome any suggestions.
>> Pull the Oak and put in a Triden
On 6/9/2015 1:08 PM, Felix Miata wrote:
> John Hupp composed on 2015-06-09 12:46 (UTC-0400):
>
>> To fix that I suppose I would need to come up with a Vesa driver for the
>> card, and would welcome any suggestions.
> Pull the Oak and put in a Trident or ATI, best the latter, which would work
> well
Dale E Sterner composed on 2015-06-09 16:50 (UTC-0400):
> Another dumb question; are there any good books out there about Vesa.?
I had one. I loaned it to a nephew. He donated it to the Clearwater Florida
Public Library. :-(
If it's still there, one could probably get it through the lending prog
On 6/9/2015 4:05 PM, Felix Miata wrote:
> John Hupp composed on 2015-06-09 15:42 (UTC-0400):
>
>> Rugxulo also suggests this in a follow-up post. I have now tried univbe
>> 6.7 and sdd 6.53. Both explicitly support the Oak chipset. Both report
>> that they provide this card with VESA 3.0 support
Another dumb question; are there any good books out there about Vesa.?
cheers
DS
On Tue, 9 Jun 2015 13:57:05 -0500 Rugxulo writes:
> Hi,
>
> On Tue, Jun 9, 2015 at 11:46 AM, John Hupp
> wrote:
> >
> > It seems that "mode con lines=34" should display text mode nicely
> on the
> > 4:3 LCD.
John Hupp composed on 2015-06-09 15:42 (UTC-0400):
> Rugxulo also suggests this in a follow-up post. I have now tried univbe
> 6.7 and sdd 6.53. Both explicitly support the Oak chipset. Both report
> that they provide this card with VESA 3.0 support including 3 graphics
> modes (though so far
On 6/9/2015 1:01 PM, Mateusz Viste wrote:
> On 09/06/2015 18:46, John Hupp wrote:
>> To fix that I suppose I would need to come up with a Vesa driver for the
>> card, and would welcome any suggestions.
> The obvious one that comes immediately to mind is SciTech Display
> Doctor, it supports plenty
Hi,
On Tue, Jun 9, 2015 at 11:46 AM, John Hupp wrote:
>
> It seems that "mode con lines=34" should display text mode nicely on the
> 4:3 LCD. And reading up on MODE, I saw that 34 lines requires VESA
> support. This vintage setup has a circa 1991 16-bit ISA video card,
> manufacturer unknown, b
Hi,
On Tue, Jun 9, 2015 at 12:01 PM, Mateusz Viste wrote:
> On 09/06/2015 18:46, John Hupp wrote:
>
>> To fix that I suppose I would need to come up with a Vesa driver for the
>> card, and would welcome any suggestions.
>
> The obvious one that comes immediately to mind is SciTech Display
> Docto
John Hupp composed on 2015-06-09 12:46 (UTC-0400):
> To fix that I suppose I would need to come up with a Vesa driver for the
> card, and would welcome any suggestions.
Pull the Oak and put in a Trident or ATI, best the latter, which would work
well if you want to boot Linux on that machine. Tri
On 09/06/2015 18:46, John Hupp wrote:
> To fix that I suppose I would need to come up with a Vesa driver for the
> card, and would welcome any suggestions.
The obvious one that comes immediately to mind is SciTech Display
Doctor, it supports plenty of graphic cards, and provides a standard
VESA
On 6/7/2015 7:46 PM, Eric Auer wrote:
> Hi John,
>
>> Though I cited Edit, and the mode suggestion might improve that, I
>> imagine that the improvement would be lost if I started a game or
>> anything else that runs in a graphical mode.
> As long as the game lets you make a CHOICE between several
Hi John,
> Though I cited Edit, and the mode suggestion might improve that, I
> imagine that the improvement would be lost if I started a game or
> anything else that runs in a graphical mode.
As long as the game lets you make a CHOICE between several resolutions,
you will again have the possi
Thanks, Eric.
Though I cited Edit, and the mode suggestion might improve that, I
imagine that the improvement would be lost if I started a game or
anything else that runs in a graphical mode.
In the meantime, I found this very dense thread on vogons.org:
http://www.vogons.org/viewtopic.php?f=9
Hi! If you are sure that this is not an issue of your
VGA or HDMI or DVI cable to the monitor, then I assume
that what you are seeing is an artifact of your screen
trying to zoom from the default resolution of DOS text
mode to the native resolution of the screen. You could
use the MODE tool of DOS
With FreeDOS 1.1 installed directly on real hardware, and testing with
two different LCD monitors and at least half a dozen different video
cards, I find that in every case there are vertical bands or fat lines
across the screen, visible as fuzziness on the black & white display
during boot, an
26 matches
Mail list logo
