Did MS DOS itself ever use blinking text? Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar ManaraWhat character is the MS-DOS cursor?How did Windows ME “cripple” DOS?Do you need to allocate memory before you use it in MS-DOS?Where did DOS store graphics fonts?Is DOS being shipped with or as an installed OS?Where was MS-DOS used?Why did MS-DOS choose percent symbol to designate variable?Why did DOS use dollar-terminated strings?Is there a reason why MS-DOS didn't use more English words for commands?How to convert .ttf to .fnt for use with M10_SCR.COM DOS font driverAlternatives for TurboVision on DOS
What *exactly* is electrical current, voltage, and resistance?
Are these square matrices always diagonalisable?
What is ls Largest Number Formed by only moving two sticks in 508?
Implementing 3DES algorithm in Java: is my code secure?
Raising a bilingual kid. When should we introduce the majority language?
c++ diamond problem - How to call base method only once
What is the term for a person whose job is to place products on shelves in stores?
Split coins into combinations of different denominations
Need of separate security plugins for both root and subfolder sites Wordpress?
How long after the last departure shall the airport stay open for an emergency return?
How would I use different systems of magic when they are capable of the same effects?
What is the ongoing value of the Kanban board to the developers as opposed to management
PIC mathematical operations weird problem
Function to calculate red-edgeNDVI in Google Earth Engine
Where did Arya get these scars?
Trumpet valves, lengths, and pitch
Visa-free travel to the US using refugee travel document from Spain?
Did the Roman Empire have penal colonies?
What do you call the part of a novel that is not dialog?
Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?
What is /etc/mtab in Linux?
How to use @AuraEnabled base class method in Lightning Component?
Justification for leaving new position after a short time
"Rubric" as meaning "signature" or "personal mark" -- is this accepted usage?
Did MS DOS itself ever use blinking text?
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraWhat character is the MS-DOS cursor?How did Windows ME “cripple” DOS?Do you need to allocate memory before you use it in MS-DOS?Where did DOS store graphics fonts?Is DOS being shipped with or as an installed OS?Where was MS-DOS used?Why did MS-DOS choose percent symbol to designate variable?Why did DOS use dollar-terminated strings?Is there a reason why MS-DOS didn't use more English words for commands?How to convert .ttf to .fnt for use with M10_SCR.COM DOS font driverAlternatives for TurboVision on DOS
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 Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
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 Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
2
It obvioulsly used a blinking cursor - That was about the amount of blinking the OS used.
– tofro
Apr 18 at 7:42
1
I thought the blinking cursor was a hardware function, not operating system, but I might be wrong.
– manassehkatz
Apr 18 at 15:07
1
@manassehkatz see this question.
– Stephen Kitt
Apr 18 at 17:05
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 Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
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 Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
asked Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
asked Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
asked Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
asked Apr 17 at 20:08
KlaymenDKKlaymenDK
27829
27829
2
It obvioulsly used a blinking cursor - That was about the amount of blinking the OS used.
– tofro
Apr 18 at 7:42
1
I thought the blinking cursor was a hardware function, not operating system, but I might be wrong.
– manassehkatz
Apr 18 at 15:07
1
@manassehkatz see this question.
– Stephen Kitt
Apr 18 at 17:05
add a comment |
2
It obvioulsly used a blinking cursor - That was about the amount of blinking the OS used.
– tofro
Apr 18 at 7:42
1
I thought the blinking cursor was a hardware function, not operating system, but I might be wrong.
– manassehkatz
Apr 18 at 15:07
1
@manassehkatz see this question.
– Stephen Kitt
Apr 18 at 17:05
2
2
It obvioulsly used a blinking cursor - That was about the amount of blinking the OS used.
– tofro
Apr 18 at 7:42
It obvioulsly used a blinking cursor - That was about the amount of blinking the OS used.
– tofro
Apr 18 at 7:42
1
1
I thought the blinking cursor was a hardware function, not operating system, but I might be wrong.
– manassehkatz
Apr 18 at 15:07
I thought the blinking cursor was a hardware function, not operating system, but I might be wrong.
– manassehkatz
Apr 18 at 15:07
1
1
@manassehkatz see this question.
– Stephen Kitt
Apr 18 at 17:05
@manassehkatz see this question.
– Stephen Kitt
Apr 18 at 17:05
add a comment |
2 Answers
2
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 INT 10h 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
edited Apr 18 at 11:59
john_e
2,439620
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
6
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
Apr 17 at 21:41
11
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
7
@Raffzahn howeverCOMMAND.COMdoes check forANSI.SYSand will use it if it’s available, e.g. forCLS.
– Stephen Kitt
Apr 18 at 11:35
1
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
add a comment |
Did MS DOS itself ever use blinking text?
What exactly does "itself" mean?
The OS kernel (io.sys or msdos.sys) would of course not do anything which is not requested by the currently running program (e.g. command.com); the kernel cannot know if some text message has the meaning: "Highly critical" or "Operation successful" so the request to change the text attributes must come from the program.
In MS-DOS consists of multiple programs. Most of them just wrote out text to the console while the text cursor was only moved implicitly because of printing the text.
However, there were also some "GUI-like" programs (fdisk, edit, GW or Q Basic, scandisk, the DOS-Shell and some backup program) being part of MS-DOS, which modified the content of the the entire text screen and explicitly moved the text cursor to certain positions.
As far as I know, the first type of programs (only printing text) never changed the text attributes. Neither color, nor blinking, nor bold. If the user selected blinking green text on blue background using ansi.sys (see supercat's comment), all of these programs would output all text green and blinking on blue background. If the user did not use ansi.sys, all text was gray, not blinking on black background.
The "GUI-like" programs used different screen attributes (such as different colors, bold or blinking). fdisk for example used bold text; edit used different colors. I'm not sure if one of these programs used blinking text.
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
1
I have vague recollections of an MS-DOS pack-in program (it could have even beenfdisk) that did use blinking text as a warning to the user before erasing all data on-disk.
– Dai
Apr 18 at 14:26
1
I have similar very vague recollections, but that it was one of the OEM-added programs, possiblyfxparkorfxprep.
– JdeBP
Apr 18 at 17:57
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
2 Answers
2
active
oldest
votes
2 Answers
2
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 INT 10h 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
edited Apr 18 at 11:59
john_e
2,439620
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
6
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
Apr 17 at 21:41
11
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
7
@Raffzahn howeverCOMMAND.COMdoes check forANSI.SYSand will use it if it’s available, e.g. forCLS.
– Stephen Kitt
Apr 18 at 11:35
1
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
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 INT 10h 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
edited Apr 18 at 11:59
john_e
2,439620
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
6
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
Apr 17 at 21:41
11
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
7
@Raffzahn howeverCOMMAND.COMdoes check forANSI.SYSand will use it if it’s available, e.g. forCLS.
– Stephen Kitt
Apr 18 at 11:35
1
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
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 INT 10h 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
edited Apr 18 at 11:59
john_e
2,439620
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
[...] 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 INT 10h 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
edited Apr 18 at 11:59
john_e
2,439620
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
edited Apr 18 at 11:59
john_e
2,439620
edited Apr 18 at 11:59
john_e
2,439620
edited Apr 18 at 11:59
john_e
2,439620
2,439620
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
answered Apr 17 at 21:29
RaffzahnRaffzahn
57.4k6140234
57.4k6140234
6
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
Apr 17 at 21:41
11
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
7
@Raffzahn howeverCOMMAND.COMdoes check forANSI.SYSand will use it if it’s available, e.g. forCLS.
– Stephen Kitt
Apr 18 at 11:35
1
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
add a comment |
6
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
Apr 17 at 21:41
11
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
7
@Raffzahn howeverCOMMAND.COMdoes check forANSI.SYSand will use it if it’s available, e.g. forCLS.
– Stephen Kitt
Apr 18 at 11:35
1
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
6
6
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
Apr 17 at 21:41
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
Apr 17 at 21:41
11
11
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
@supercat Jup, another optional add-on, nothing a cor OS can rely on.
– Raffzahn
Apr 17 at 22:08
7
7
@Raffzahn however
COMMAND.COM does check for ANSI.SYS and will use it if it’s available, e.g. for CLS.– Stephen Kitt
Apr 18 at 11:35
@Raffzahn however
COMMAND.COM does check for ANSI.SYS and will use it if it’s available, e.g. for CLS.– Stephen Kitt
Apr 18 at 11:35
1
1
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
Can't imagine that working well with an actual printer, either.
– Lightness Races in Orbit
Apr 18 at 17:20
add a comment |
Did MS DOS itself ever use blinking text?
What exactly does "itself" mean?
The OS kernel (io.sys or msdos.sys) would of course not do anything which is not requested by the currently running program (e.g. command.com); the kernel cannot know if some text message has the meaning: "Highly critical" or "Operation successful" so the request to change the text attributes must come from the program.
In MS-DOS consists of multiple programs. Most of them just wrote out text to the console while the text cursor was only moved implicitly because of printing the text.
However, there were also some "GUI-like" programs (fdisk, edit, GW or Q Basic, scandisk, the DOS-Shell and some backup program) being part of MS-DOS, which modified the content of the the entire text screen and explicitly moved the text cursor to certain positions.
As far as I know, the first type of programs (only printing text) never changed the text attributes. Neither color, nor blinking, nor bold. If the user selected blinking green text on blue background using ansi.sys (see supercat's comment), all of these programs would output all text green and blinking on blue background. If the user did not use ansi.sys, all text was gray, not blinking on black background.
The "GUI-like" programs used different screen attributes (such as different colors, bold or blinking). fdisk for example used bold text; edit used different colors. I'm not sure if one of these programs used blinking text.
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
1
I have vague recollections of an MS-DOS pack-in program (it could have even beenfdisk) that did use blinking text as a warning to the user before erasing all data on-disk.
– Dai
Apr 18 at 14:26
1
I have similar very vague recollections, but that it was one of the OEM-added programs, possiblyfxparkorfxprep.
– JdeBP
Apr 18 at 17:57
add a comment |
Did MS DOS itself ever use blinking text?
What exactly does "itself" mean?
The OS kernel (io.sys or msdos.sys) would of course not do anything which is not requested by the currently running program (e.g. command.com); the kernel cannot know if some text message has the meaning: "Highly critical" or "Operation successful" so the request to change the text attributes must come from the program.
In MS-DOS consists of multiple programs. Most of them just wrote out text to the console while the text cursor was only moved implicitly because of printing the text.
However, there were also some "GUI-like" programs (fdisk, edit, GW or Q Basic, scandisk, the DOS-Shell and some backup program) being part of MS-DOS, which modified the content of the the entire text screen and explicitly moved the text cursor to certain positions.
As far as I know, the first type of programs (only printing text) never changed the text attributes. Neither color, nor blinking, nor bold. If the user selected blinking green text on blue background using ansi.sys (see supercat's comment), all of these programs would output all text green and blinking on blue background. If the user did not use ansi.sys, all text was gray, not blinking on black background.
The "GUI-like" programs used different screen attributes (such as different colors, bold or blinking). fdisk for example used bold text; edit used different colors. I'm not sure if one of these programs used blinking text.
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
1
I have vague recollections of an MS-DOS pack-in program (it could have even beenfdisk) that did use blinking text as a warning to the user before erasing all data on-disk.
– Dai
Apr 18 at 14:26
1
I have similar very vague recollections, but that it was one of the OEM-added programs, possiblyfxparkorfxprep.
– JdeBP
Apr 18 at 17:57
add a comment |
Did MS DOS itself ever use blinking text?
What exactly does "itself" mean?
The OS kernel (io.sys or msdos.sys) would of course not do anything which is not requested by the currently running program (e.g. command.com); the kernel cannot know if some text message has the meaning: "Highly critical" or "Operation successful" so the request to change the text attributes must come from the program.
In MS-DOS consists of multiple programs. Most of them just wrote out text to the console while the text cursor was only moved implicitly because of printing the text.
However, there were also some "GUI-like" programs (fdisk, edit, GW or Q Basic, scandisk, the DOS-Shell and some backup program) being part of MS-DOS, which modified the content of the the entire text screen and explicitly moved the text cursor to certain positions.
As far as I know, the first type of programs (only printing text) never changed the text attributes. Neither color, nor blinking, nor bold. If the user selected blinking green text on blue background using ansi.sys (see supercat's comment), all of these programs would output all text green and blinking on blue background. If the user did not use ansi.sys, all text was gray, not blinking on black background.
The "GUI-like" programs used different screen attributes (such as different colors, bold or blinking). fdisk for example used bold text; edit used different colors. I'm not sure if one of these programs used blinking text.
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
Did MS DOS itself ever use blinking text?
What exactly does "itself" mean?
The OS kernel (io.sys or msdos.sys) would of course not do anything which is not requested by the currently running program (e.g. command.com); the kernel cannot know if some text message has the meaning: "Highly critical" or "Operation successful" so the request to change the text attributes must come from the program.
In MS-DOS consists of multiple programs. Most of them just wrote out text to the console while the text cursor was only moved implicitly because of printing the text.
However, there were also some "GUI-like" programs (fdisk, edit, GW or Q Basic, scandisk, the DOS-Shell and some backup program) being part of MS-DOS, which modified the content of the the entire text screen and explicitly moved the text cursor to certain positions.
As far as I know, the first type of programs (only printing text) never changed the text attributes. Neither color, nor blinking, nor bold. If the user selected blinking green text on blue background using ansi.sys (see supercat's comment), all of these programs would output all text green and blinking on blue background. If the user did not use ansi.sys, all text was gray, not blinking on black background.
The "GUI-like" programs used different screen attributes (such as different colors, bold or blinking). fdisk for example used bold text; edit used different colors. I'm not sure if one of these programs used blinking text.
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
answered Apr 18 at 6:39
Martin RosenauMartin Rosenau
732127
732127
1
I have vague recollections of an MS-DOS pack-in program (it could have even beenfdisk) that did use blinking text as a warning to the user before erasing all data on-disk.
– Dai
Apr 18 at 14:26
1
I have similar very vague recollections, but that it was one of the OEM-added programs, possiblyfxparkorfxprep.
– JdeBP
Apr 18 at 17:57
add a comment |
1
I have vague recollections of an MS-DOS pack-in program (it could have even beenfdisk) that did use blinking text as a warning to the user before erasing all data on-disk.
– Dai
Apr 18 at 14:26
1
I have similar very vague recollections, but that it was one of the OEM-added programs, possiblyfxparkorfxprep.
– JdeBP
Apr 18 at 17:57
1
1
I have vague recollections of an MS-DOS pack-in program (it could have even been
fdisk) that did use blinking text as a warning to the user before erasing all data on-disk.– Dai
Apr 18 at 14:26
I have vague recollections of an MS-DOS pack-in program (it could have even been
fdisk) that did use blinking text as a warning to the user before erasing all data on-disk.– Dai
Apr 18 at 14:26
1
1
I have similar very vague recollections, but that it was one of the OEM-added programs, possibly
fxpark or fxprep.– JdeBP
Apr 18 at 17:57
I have similar very vague recollections, but that it was one of the OEM-added programs, possibly
fxpark or fxprep.– JdeBP
Apr 18 at 17:57
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
2
It obvioulsly used a blinking cursor - That was about the amount of blinking the OS used.
– tofro
Apr 18 at 7:42
1
I thought the blinking cursor was a hardware function, not operating system, but I might be wrong.
– manassehkatz
Apr 18 at 15:07
1
@manassehkatz see this question.
– Stephen Kitt
Apr 18 at 17:05