You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
I don't like the last sentence. It sounds like the text mode did not make full use of the 480 lines, which could be considered a bad thing. Actually, it is a good thing! The VGA monitor has a fixed horizontal frequency, so more lines means lower refresh rate. At 400 lines, it ran at 70 Hz, and at 480 lines, the refresh rate dropped to 60 Hz, which was flickery back in the time on many contemporary monitors. The 350-line EGA compatible mode ran at 70 Hz too (with longer blanking), because there was no need for higher refrehs rates at that time.– Michael KarcherCommented May 18, 2020 at 19:09
-
In my experience, the problem with 60Hz refresh was often related to interaction with fluorescent lighting. In a dark room, a 60Hz monitor was fine :-) I didn't mean 400 out of 480 was bad, rather that it was good compared to 350 (of MDA) and it fit real well in terms of a x16 character cell. There just wasn't any need to go all the way to 480 since most text software would never use more rows at the time and graphics got the 480 anyway.– manassehkatz-Moving 2 CodidactCommented May 18, 2020 at 19:34
-
I used to be annoyed as child by the 60Hz flicker during daylight in a 50Hz country, so it definitely was not an AC interference thing. But the amount of flicker depends very much on the phosphor type, and my first VGA monitor definitely was on the cheap end of the spectrum. May I suggest to change the last sentence to "This resolution fully utilized the capabilites of the VGA monitor at 70Hz, and finally brought the horizontal resolution of MDA text to color monitors"? It's not that 400 and 480 lines are just "close enough" - those are dedicated different modes of the monitor.– Michael KarcherCommented May 18, 2020 at 19:44
-
OK. FYI, I am fully in favor of the collaborative nature of Stackexchange - i.e., unless something is contrary to my statements (which your comments are not) there is nothing wrong with editing it yourself.– manassehkatz-Moving 2 CodidactCommented May 18, 2020 at 20:12
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. ms-dos), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you