Did MS DOS itself ever use blinking text?
I know that it was possible to create blinking text, but did the operating system itself (I mean, in output from functions of command.com and similar executables) ever make use of blink formatting?
You'd think it would be useful for confirmations of really dangerous things like format C: and such, but perhaps also seen as "over the top" and or just not necessary.
ms-dos
asked 3 hours ago
KlaymenDKKlaymenDK
22817
add a comment |
I know that it was possible to create blinking text, but did the operating system itself (I mean, in output from functions of command.com and similar executables) ever make use of blink formatting?
You'd think it would be useful for confirmations of really dangerous things like format C: and such, but perhaps also seen as "over the top" and or just not necessary.
ms-dos
asked 3 hours ago
KlaymenDKKlaymenDK
22817
add a comment |
I know that it was possible to create blinking text, but did the operating system itself (I mean, in output from functions of command.com and similar executables) ever make use of blink formatting?
You'd think it would be useful for confirmations of really dangerous things like format C: and such, but perhaps also seen as "over the top" and or just not necessary.
ms-dos
asked 3 hours ago
KlaymenDKKlaymenDK
22817
I know that it was possible to create blinking text, but did the operating system itself (I mean, in output from functions of command.com and similar executables) ever make use of blink formatting?
You'd think it would be useful for confirmations of really dangerous things like format C: and such, but perhaps also seen as "over the top" and or just not necessary.
ms-dos
ms-dos
asked 3 hours ago
KlaymenDKKlaymenDK
22817
asked 3 hours ago
KlaymenDKKlaymenDK
22817
asked 3 hours ago
KlaymenDKKlaymenDK
22817
asked 3 hours ago
KlaymenDKKlaymenDK
22817
asked 3 hours ago
KlaymenDKKlaymenDK
22817
22817
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
[...] did the operating system itself [...] ever make use of blink formatting?
No.
MS-DOS was, at the core, machine agnostic. It only used the most basic features provided by the BIOS. While function 09h would have provided the ability to set attributes (via BL), its meaning already varies across video cards offered by IBM and even more so with third party cards or non IBM machines. Not to mention that MS-DOS was intended to work with terminals as well, where attributes are even more diverse.
MS-DOS only used the most basic characters for output control:
- CR
- LF
- FF (clear screen)
- BEL
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
2
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "648"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f9724%2fdid-ms-dos-itself-ever-use-blinking-text%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
[...] did the operating system itself [...] ever make use of blink formatting?
No.
MS-DOS was, at the core, machine agnostic. It only used the most basic features provided by the BIOS. While function 09h would have provided the ability to set attributes (via BL), its meaning already varies across video cards offered by IBM and even more so with third party cards or non IBM machines. Not to mention that MS-DOS was intended to work with terminals as well, where attributes are even more diverse.
MS-DOS only used the most basic characters for output control:
- CR
- LF
- FF (clear screen)
- BEL
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
2
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
add a comment |
[...] did the operating system itself [...] ever make use of blink formatting?
No.
MS-DOS was, at the core, machine agnostic. It only used the most basic features provided by the BIOS. While function 09h would have provided the ability to set attributes (via BL), its meaning already varies across video cards offered by IBM and even more so with third party cards or non IBM machines. Not to mention that MS-DOS was intended to work with terminals as well, where attributes are even more diverse.
MS-DOS only used the most basic characters for output control:
- CR
- LF
- FF (clear screen)
- BEL
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
2
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
add a comment |
[...] did the operating system itself [...] ever make use of blink formatting?
No.
MS-DOS was, at the core, machine agnostic. It only used the most basic features provided by the BIOS. While function 09h would have provided the ability to set attributes (via BL), its meaning already varies across video cards offered by IBM and even more so with third party cards or non IBM machines. Not to mention that MS-DOS was intended to work with terminals as well, where attributes are even more diverse.
MS-DOS only used the most basic characters for output control:
- CR
- LF
- FF (clear screen)
- BEL
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
[...] did the operating system itself [...] ever make use of blink formatting?
No.
MS-DOS was, at the core, machine agnostic. It only used the most basic features provided by the BIOS. While function 09h would have provided the ability to set attributes (via BL), its meaning already varies across video cards offered by IBM and even more so with third party cards or non IBM machines. Not to mention that MS-DOS was intended to work with terminals as well, where attributes are even more diverse.
MS-DOS only used the most basic characters for output control:
- CR
- LF
- FF (clear screen)
- BEL
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
answered 2 hours ago
RaffzahnRaffzahn
56.7k6137228
56.7k6137228
2
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
add a comment |
2
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
2
2
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
MS-DOS 2.0 to 5.x included a driver called ANSI.SYS which provided support for escape codes to control character attributes; I'm pretty certain escape-leftbracket-5m was supported as a means of enabling blinking, along with ...[1m for bright text, ...[30m to ...[37m for foreground color, etc.
– supercat
2 hours ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
1 hour ago
add a comment |
Thanks for contributing an answer to Retrocomputing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f9724%2fdid-ms-dos-itself-ever-use-blinking-text%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
