Live data from Hacker News

VGA ROM Fonts (2020)

alexandrugroza.ro

41–46 of 46 posts

Re: VGA ROM Fonts (2020)

#41
post #38

Earlier quoted context omitted.

Do you recall "DOSBLOOD.EXE", a font loader TSR that made the letters look like they were dripping?

This sounds fascinating, although "DOSBLOOD.EXE" only returns one Google result, being this comment. I assume it would work by constantly modifying the bitmap font?

lol. that's funny. no it wasn't animated, just drippy letters. and it was 1995 so i might have misspelled it, memory and all.

Re: VGA ROM Fonts (2020)

#42
post #23
post #18

Earlier quoted context omitted.

Luckily, that’s changing. C# 10 is converting namespace blocks into directives like Java. That means one fewer indent.

Do people indent namespaces in C#? In C++ it's common practice to not indent.

Yes, it's traditional with C# to indent every multi-line block. There are teams and individuals who opt for some exceptions (like switch/case), but none of them are universally adopted. I haven't seen a single example over the last two decades where namespaces aren't indented. The defaults go a long way.

Re: VGA ROM Fonts (2020)

#43
post #19
post #17

Earlier quoted context omitted.

Not on PC though.

It was available, but quirky and sometimes app specific. I do remember running Wordstar in 132 columns and some TSR to have DOS in 132 columns. There was "MODE CON COLS=132 LINES=50" also.

That's interesting, I haven't seen that. I don't think MODE CON magically changed text mode resolution beyond 80 or 40 cols either. It was mostly about having proper line wraps with INT 21h output, IIRC.

Re: VGA ROM Fonts (2020)

#44
>"Thus I began designing the font of my dreams. Some might find it beautiful, some might find it ugly. But I love it. It is the first iteration of the font and I'm happy with it. I did a lot of work on these fonts and I find then usable for now. The base font for my design was the original one that I recovered from the ET4000/W32i ROM. Then I tried hard to remember what the old fonts looked like. I also drew inspiration from the ATI VGA Wonder 16 ROM font."

PDS: I think they're awesome!

>"This is my Micro-Labs Tseng Labs ET4000/W32i ISA card. I find it very beautifully laid out.' [...] "The card clocks are built around the CHRONTEL CH9294 dual PLL graphics clock generator integrated circuit. These are still available on various sites. The RAMDAC is an AT&T ATT20C490-80 part. These are also available on-line. The ET4000/W32i chip is also available on-line. Which makes me think: what if I'd build my own VGA card? I still have the Tseng Labs datasheets catalog and this VGA controller along with a sample schematic is described in depth. I could improve that design by using modern memories which would be cheaper and easier to source. But this is another topic. For the moment it is only food for thought."

PDS: I think it's a great idea!

Excellent article, all in all!

Well worth re-reading in the future!

Re: VGA ROM Fonts (2020)

#45
post #27

Earlier quoted context omitted.

Really? I started college using VT100s in the lab to access the mainframe, and 80 columns was taxing enough to stare at hours on end. Can't imagine a 65% increase in horizontal density!

On a vt320, which does have a larger 14" CRT, couldn't find a good picture of a 132 column on 12": https://i.imgur.com/IYULtxAh.jpg

I had a vt320/vt420 on my desk for years. YMMV...but 132 column mode was a bit cramped even when my eyes weren't aged.

Re: VGA ROM Fonts (2020)

#46
post #43
post #19

Earlier quoted context omitted.

It was available, but quirky and sometimes app specific. I do remember running Wordstar in 132 columns and some TSR to have DOS in 132 columns. There was "MODE CON COLS=132 LINES=50" also.

That's interesting, I haven't seen that. I don't think MODE CON magically changed text mode resolution beyond 80 or 40 cols either. It was mostly about having proper line wraps with INT 21h output, IIRC.

If you're talking MS-DOS, 132 column mode was very common on apps where it made sense (wordstar, visicalc), but was usually invoked with an app-specific driver of some sort, not BIOS calls.
Post reply on HN