All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frantisek Hanzlik <franta-8CMi+4rsZoHtwjQa/ONI9g@public.gmane.org>
To: DOSEmu developers
	<dosemu-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	DOSEMU/FreeDOS
	<linux-msdos-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: VESA mode 0x10B - 132 columns × 50 rows - is it possible?
Date: Tue, 08 Apr 2014 07:39:58 +0200	[thread overview]
Message-ID: <53438BAE.7030107@hanzlici.cz> (raw)

Hello all DOSEMU enthusiasts,

first, thanks for developing and evolving this powerfull SW piece!
And now my current research (so far in vain): I want my DOS text app
run in text mode with resolution 132 columns × 50 rows - which should
be VESA 2.0 (maybe as early as VESA 1.2) mode 0x10B, according e.g.:

http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Modes_defined_by_VESA

but so far I'm unsuccessfull (except in the case when I run DOSEMU in
console mode in console/X window with this resolution, but this is
perhaps obvious).
Nevertheless, modes 0x10A (132 x 43) and 0x010C 132 x 60 are working
fine under xdosemu. Problem I have only with this 132 x 50 mode.

I'm using DOSEMU + FreeDOS 1.0, and thus potentially may be problem
in FreeDOS, but I suspect rather DOSEMU, as:

1) when I run commands 'mode con cols=132 lines=43', resp. 'mode con
cols=132 lines=60', I will get responses:

VESA 2.0 'DOSEMU VGA/VBE 2.0 Emulator', mode 0x0003, 4096k for BIOS, 57 modes.
VESA mode 0x010A: 132 x 43 with 8 x 11 font.

resp.

VESA 2.0 'DOSEMU VGA/VBE 2.0 Emulator', mode 0x0003, 4096k for BIOS, 57 modes.
VESA mode 0x010C: 132 x 60 with 8 x 8 font.

and right mode is set.
But after 'mode con cols=132 lines=50' command, resolution changes to
80 cols x 50 lines (i.e. not 132x50, as I want) and command output is:

VESA 2.0 'DOSEMU VGA/VBE 2.0 Emulator', mode 0x0003, 4096k for BIOS, 57 modes.
Using VGA 400 line resolution.
(this second line is totally different than in previous two cases)

2) When I grep DOSEMU source codes to '132' string, there is something
what may bear on 132xNN text mode in 'src/env/video/vgaemu_modelist.h'.
But it seems as 132x50 mode there isn't present... or am I wrong?
Maybe because Trident 8900, it seems, could not do 132x50 mode? But
what some VBE modes at vga_mode_table end? It would be possible for this
to be used?
Thanks in advance, Franta Hanzlik


------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees

             reply	other threads:[~2014-04-08  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  5:39 Frantisek Hanzlik [this message]
2014-04-08  6:40 ` VESA mode 0x10B - 132 columns × 50 rows - is it possible? Felix Miata
2014-04-08  9:34   ` Frantisek Hanzlik
2014-04-08  9:47   ` Frantisek Hanzlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53438BAE.7030107@hanzlici.cz \
    --to=franta-8cmi+4rszohtwjqa/oni9g@public.gmane.org \
    --cc=dosemu-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-msdos-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.