17 Dec
2007
17 Dec
'07
6:47 p.m.
Not likely - as
far as I know there are no standard PC text
video modes that give 132 columns.
Long ago I had a 132char driver for the Hercules/TTL mono video card.
I was based on the 720x348 mono graphics mode.
I also remember the several of the SuperEGA bios that supported the
extended MDA modes:
46h Text 132x25 (8/9x14)
47h Text 132x29 (8/9x12)
48h Text 132x32 (8/9x11)
49h Text 132x44 (8/9x8) 
17 Dec
17 Dec
9:30 p.m.
On Dec 17, 2007 6:47 PM, Dave Dunfield <dave06a at dunfield.com> wrote:
As far as I know there are no **STANDARD** PC text video modes that give
132 columns.
There's certainly no such mode on the MDA/CGA/EGA/VGA cards as used in the
PC and PS/2.Yes, at 720 dots, you can do a 5 point wide font for 132 columns
on a Herc.,
Does anyone know if any of the more modern (ie: VGA)
cards support
enhanced
132 column text modes?
I think this is a "maybe". At [
http://www.columbia.edu/~em36/wpdos/textmode.html ], there's a link to a
program that scans for a series of 132-column VESA text modes. It couldn't
find any on the laptop I tried it on (no surprise), but apparently there are
a number of NVIDIA cards that support these modes. I don't know what how
the layout compares to the character/attribute pairs for 80-column modes,
but here's the Pascal code they use to try entering the modes:
PROGRAM VesaTest;
USES Dos;
VAR ok : Boolean;
Reg : Registers;
i : Word;
BEGIN
i := 0;
IF ParamStr (1) = '132x60' THEN i := 268;
IF ParamStr (1) = '132x50' THEN i := 267;
IF ParamStr (1) = '132x43' THEN i := 266;
IF ParamStr (1) = '132x25' THEN i := 265;
IF ParamStr (1) = '080x60' THEN i := 264;
Reg.ax := $4F02; Reg.bx := i;
Intr (16, Reg); {VesaTextmodus einschalten}
ok := (Reg.ah = 0);
Reg.ax := $0003;
IF ok THEN Intr (16, Reg) {auf 80x25 zur?ckschalten}
ELSE Halt (1);
END.
9:44 p.m.
As far as I know there are no **STANDARD** PC text
video modes that give
132 columns.
That's right.
No **STANDARD** 132 column modes.
My Wyse 700/Amdek 1280s would do 50 lines of 160 characters per line.
I had a MDA board (Matrox? MBI? ??) that did 132 x 25, 43?, 50?
The DOS box in XP can be set to 132 cols.
18 Dec
18 Dec
3:32 a.m.
Hi,
Fred Cisin said:
Most of the vga cards I've used support at least one 132 column text mode.
Certainly the S3 card in my Forth PC does, I run Forth in 132 columns.
It uses mode 55(hex) for 132x43.
An older DFI vga card in another box runs the following modes:
Mode(Hex) Format Char size
53 132x25 8x14
54 132x30 8x16
55 132x43 8x11
56 132x60 8x8
57 132x25 9x14
58 132x30 9x16
59 132x43 9x11
5A 132x60 9x8
According to the manual.
--
Cheers,
Stan Barr stanb at dial.pipex.com
The future was never like this!
As far as I
know there are no **STANDARD** PC text video modes that give
132 columns.
That's right.
No **STANDARD** 132 column modes.
My Wyse 700/Amdek 1280s would do 50 lines of 160 characters per line.
I had a MDA board (Matrox? MBI? ??) that did 132 x 25, 43?, 50?
The DOS box in XP can be set to 132 cols. 
19 Dec
19 Dec
12:16 a.m.
Mark Meiss wrote:
IF ParamStr (1) = '132x60' THEN i := 268;
IF ParamStr (1) = '132x50' THEN i := 267;
IF ParamStr (1) = '132x43' THEN i := 266;
IF ParamStr (1) = '132x25' THEN i := 265;
IF ParamStr (1) = '080x60' THEN i := 264;
Just a quick note that you shouldn't actually implement VESA this way,
because the mode numbers are not guaranteed from card to card. The
proper way is to use VESA to query all of the modes, stuff results into
an array, iterate through the array to find what you're looking for, and
then set the mode with what you come up with.
--
Jim Leonard (trixter at oldskool.org) http://www.oldskool.org/
Help our electronic games project: http://www.mobygames.com/
Or check out some trippy MindCandy at http://www.mindcandydvd.com/
A child borne of the home computer wars: http://trixter.wordpress.com/
9:40 a.m.
Jim Leonard wrote:
Mark Meiss wrote:
... so long as there's a user override for when it goes wrong. There were some
really broken VESA implementations out there back in the day!
The last time I did anything serious with PC graphics programming under DOS, I
ended up going the loadable driver route - it was the driver which translated
requests to actual things happening on screen (and the reporting of board
modes) via a common API.
My main focus was graphics though, so I think the text APIs that I came up
with were reasonably primitive and didn't support attributes other than colour.
Implementation-wise, it wasn't too difficult to do - I tend to find that most
code (aside from things designed to be as fast as possible) naturally provides
API-like boundaries anyway, so it's not hard to abstract that out and parcel
it up into some sort of runtime-loadable module.
cheers
Jules
IF ParamStr (1) = '132x60' THEN i :=
268;
IF ParamStr (1) = '132x50' THEN i := 267;
IF ParamStr (1) = '132x43' THEN i := 266;
IF ParamStr (1) = '132x25' THEN i := 265;
IF ParamStr (1) = '080x60' THEN i := 264;
Just a quick note that you shouldn't actually implement VESA this way,
because the mode numbers are not guaranteed from card to card. The
proper way is to use VESA to query all of the modes, stuff results into
an array, iterate through the array to find what you're looking for, and
then set the mode with what you come up with.
6094
days inactive
6096
days old
5 comments
6 participants
participants (6)
-
chaosotter76＠gmail.com -
cisin＠xenosoft.com -
dave06a＠dunfield.com -
jules.richardson99＠gmail.com -
stanb＠dial.pipex.com -
trixter＠oldskool.org