They're irrelevant to their target market. Same as Target Canada announced they're going bankrupt because their prices absolutely suck in Canada and their choice of merchandise is much more limited.
This is the annual January Clean-out of white elephants.
Wrong - read this post and then do some research and you'll find that several manufacturers sold computers with it.
A tsr is no more multitasking than a bios service call. Would you say that old 8086 was multitasking because it could read the keyboard only when you pressed a key, or a serial port being read only when it generated an interrupt? Nonsense. Those are simple background services that, once installed, the system has no way of controlling when they are called.
The disk buffer never reads just 2 or 4 bytes, so the poster is wrong. You can read text files in binary mode and skip all the code that reads "one line at a time". As for the purported advantage of keeping a large chunk of data in ram all the time, that's not an "advantage".
Additionally, when the registry gets corrupted, it's usually too late to"restore." I had to load it into linux and use a hex editor to remove the crap. An ini file would be simplicity itself.
I see from the links that it was using the standard 18.2 ticks/second clock, and that it was supposed to run on an 80186. I remember a friend of mine had a dual-cpu 80186 with what he said was a weird os...
Yes, but whose lives are ruined? The lives of the people who choose to take such drugs.
My guess is you haven't had to deal with a family member who is permanently paralyzed on one side from several strokes during heart surgery which was needed after decades of doing crack and abusing prescription drugs, who will never get better and will die a premature death.
Cocaine use kills over 15,000 people each year in the United States due to overuse or related accidents. Additionally, cocaine use can cause damage to the heart, which leads to many more deaths each year.
Several cardiovascular complications are closely related to cocaine use. They include chest pain syndromes, heart attacks, heart failure, strokes, aortic dissection, and fatal and nonfatal arrhythmias.
Others include:
myocarditis (inflammation of the heart muscle)
endocarditis (inflammation of the inner lining of the heart)
pulmonary edema (fluid in the lungs)
vascular thrombosis (blood clots in blood vessels)
dilated cardiomyopathy (an enlarged heart)
Some of these potentially fatal complications can occur in a first-time user. Older people with abnormal coronary arteries and diseased blood vessels in the brain are at even greater risk.
Today law enforcement agencies and the medical community recognize cocaine as one of the most dangerous illicit drugs in common use. Because it's increasingly popular and easily bought, the number of cocaine-related cardiovascular disabilities and deaths may be expected to rise. Furthermore, smoking crack cocaine, which is cheaper, more potent and widely available, will lead to even more strokes and heart attacks in younger people not normally "at risk."
It's going to cost taxpayers at least $70k a year (on top of the 6-figure sum already spent last year for quintuple bypass, physiotherapy to try to restore function, etc) because she needs 24/7 care in an institutional setting and frequent doctor's visits, so it affects everyone. And that's not factoring the impact on family and friends.
So would I, but it was a limited release, and when I went to buy Novell Dos (remember that) it was no longer available at the local stores... bummer, even though its' "multitasking" was limited.
Just because RMS says it doesn't make it true. The GPL is only "compatible with selling your work" for a one-time sale, because after that, they buyer can just give it away for free. That's the difference between the freetard view and reality.
First, again, Im not talking about dosshell. I'm referring to the preemptive version of dos that had a limited release years before that, and was promptly buried - so yes, you NEED to follow the link instead of basing it on wrong assumptions. You do NOT "know this stuff cold." I was surprised myself - learn something new every day. And yes, I lived it at that time as well as for a decade before that. So tear it up if you can.
And no, tsrs don't work via timeslicing. They work by an interrupt taking control of program flow to, for example, print a line, then restoring the normal program flow. That is not time-slicing, which is using a task scheduler to divvy up slices of time driven by the timer interrupt. I wrote tsrs as practical jokes. There was no timer tick involved.
If you think that reading text is longer, it's because you're doing it wrong. You can open text files in binary mode and bypass the whole cr/lf and readline() overhead. In fact, if the file is corrupt, you have no choice except to open it in binary mode. The scanning for a key will be the same in either case.
Then why do they always insist on flying the stupid fucking Puerto Rican flag at their houses (and some even get it tattooed on their skin)? If they want to be americans, they should have american pride, not Puerto Rican pride.
I dare you to tell that to all the Texans to their faces.
Ordinary dos didn't have pre-emptive multitasking. There was only one small release, called European Dos (see the link above). But yes, dos had interrupt handlers, and you could hook your own into the chain.
NO, it wasn't DosShell. Did you even follow the links? Obviously not. DosShell was not a pre-emptive multi-tasker, and TSRs also were not preemptive multitaskers. If it ain't pre-emptive, it's not true multi-tasking, as another process can steal 100% cpu and require a hard reboot. But usually what happened is that the TSR was badly written and would lock up the machine at some point.
No, it's not "moving the goalposts." Read the post above mine complaining about "scattered ini files".
The ini file format makes it pretty clear what you're editing - it's plain text. The registry - even with a front end - is pretty opaque.
And when you write "Put a front-end onto any binary file, the ease is as simple as (or simpler, no texteditor summoning needed as for text) editing an.ini file." you've got to be kidding. You need a custom front end rather than any old text editor you have hanging around, or even copy con > stuff.ini.
And no, code for scanning through a gigantic binary file is not going to be as fast as loading a 1k text file.
Considering that Microsoft did a limited release of a multi-tasking dos back in 1987, complete with preemptive multitasking, and that later extensions allowed dos to access up to 3 gig of ram for 32-bit programs, or 4 gig in unreal mode, I'd say emacs and systemd can't beat dos as an os.
It's quicker to process a small text file than a humongous binary file, especially when you have a small list of valid keys in the ini file.
It's also easier to manually change the values in a small text file. Or back it up and give it a name that makes it evident that it's ONLY for that one program.
The hive is stupid. Complication for complication's sake. A great place to hide malware instructions.
Slashdot Mirror
They're irrelevant to their target market. Same as Target Canada announced they're going bankrupt because their prices absolutely suck in Canada and their choice of merchandise is much more limited.
This is the annual January Clean-out of white elephants.
Except that the damage is not just limited to her, which is what the poster contended - everyone pays.
Wrong - read this post and then do some research and you'll find that several manufacturers sold computers with it.
A tsr is no more multitasking than a bios service call. Would you say that old 8086 was multitasking because it could read the keyboard only when you pressed a key, or a serial port being read only when it generated an interrupt? Nonsense. Those are simple background services that, once installed, the system has no way of controlling when they are called.
The disk buffer never reads just 2 or 4 bytes, so the poster is wrong. You can read text files in binary mode and skip all the code that reads "one line at a time". As for the purported advantage of keeping a large chunk of data in ram all the time, that's not an "advantage".
Additionally, when the registry gets corrupted, it's usually too late to"restore." I had to load it into linux and use a hex editor to remove the crap. An ini file would be simplicity itself.
"they" is plural. Using it to refer to a single person is grammatically wrong.
I see from the links that it was using the standard 18.2 ticks/second clock, and that it was supposed to run on an 80186. I remember a friend of mine had a dual-cpu 80186 with what he said was a weird os ...
Yes, but whose lives are ruined? The lives of the people who choose to take such drugs.
My guess is you haven't had to deal with a family member who is permanently paralyzed on one side from several strokes during heart surgery which was needed after decades of doing crack and abusing prescription drugs, who will never get better and will die a premature death.
linky
How does cocaine affect the heart?
Cocaine use kills over 15,000 people each year in the United States due to overuse or related accidents. Additionally, cocaine use can cause damage to the heart, which leads to many more deaths each year. Several cardiovascular complications are closely related to cocaine use. They include chest pain syndromes, heart attacks, heart failure, strokes, aortic dissection, and fatal and nonfatal arrhythmias.
Others include:
myocarditis (inflammation of the heart muscle)
endocarditis (inflammation of the inner lining of the heart)
pulmonary edema (fluid in the lungs)
vascular thrombosis (blood clots in blood vessels)
dilated cardiomyopathy (an enlarged heart)
Some of these potentially fatal complications can occur in a first-time user. Older people with abnormal coronary arteries and diseased blood vessels in the brain are at even greater risk.
Today law enforcement agencies and the medical community recognize cocaine as one of the most dangerous illicit drugs in common use. Because it's increasingly popular and easily bought, the number of cocaine-related cardiovascular disabilities and deaths may be expected to rise. Furthermore, smoking crack cocaine, which is cheaper, more potent and widely available, will lead to even more strokes and heart attacks in younger people not normally "at risk."
It's going to cost taxpayers at least $70k a year (on top of the 6-figure sum already spent last year for quintuple bypass, physiotherapy to try to restore function, etc) because she needs 24/7 care in an institutional setting and frequent doctor's visits, so it affects everyone. And that's not factoring the impact on family and friends.
So would I, but it was a limited release, and when I went to buy Novell Dos (remember that) it was no longer available at the local stores ... bummer, even though its' "multitasking" was limited.
Just because RMS says it doesn't make it true. The GPL is only "compatible with selling your work" for a one-time sale, because after that, they buyer can just give it away for free. That's the difference between the freetard view and reality.
First, again, Im not talking about dosshell. I'm referring to the preemptive version of dos that had a limited release years before that, and was promptly buried - so yes, you NEED to follow the link instead of basing it on wrong assumptions. You do NOT "know this stuff cold." I was surprised myself - learn something new every day. And yes, I lived it at that time as well as for a decade before that. So tear it up if you can.
And no, tsrs don't work via timeslicing. They work by an interrupt taking control of program flow to, for example, print a line, then restoring the normal program flow. That is not time-slicing, which is using a task scheduler to divvy up slices of time driven by the timer interrupt. I wrote tsrs as practical jokes. There was no timer tick involved.
If you think that reading text is longer, it's because you're doing it wrong. You can open text files in binary mode and bypass the whole cr/lf and readline() overhead. In fact, if the file is corrupt, you have no choice except to open it in binary mode. The scanning for a key will be the same in either case.
The thing i never understood was
how your post didn't end with
Burma shave
What exactly is a burma shave anyway? Is that anything like a brazilian wax? Really want to know cuz it's often repeated but never defined.
It's an old Troll Tuesday tradition. It's a long story.
Not only is it a complete waste of time and ruins people's lives
Because crack and illegal abuse of prescription drugs also ruin people's lives.
Why is living in Puerto Rico 'unfortunate'?
Because the article says that anyone who has more than 1 camera in their phone is crazy?
FTFA:
Google will include an Ara Manager app that lets you manage the modules — for example, if you were crazy enough to load two cameras onto your phone
If you're in Puerto Rico, no selfies for YOU!
Then why do they always insist on flying the stupid fucking Puerto Rican flag at their houses (and some even get it tattooed on their skin)? If they want to be americans, they should have american pride, not Puerto Rican pride.
I dare you to tell that to all the Texans to their faces.
You forgot that the massage list is also now fixed-maximum-width, glued to the left side, which looks stupid on larger monitors
Ordinary dos didn't have pre-emptive multitasking. There was only one small release, called European Dos (see the link above). But yes, dos had interrupt handlers, and you could hook your own into the chain.
NO, it wasn't DosShell. Did you even follow the links? Obviously not. DosShell was not a pre-emptive multi-tasker, and TSRs also were not preemptive multitaskers. If it ain't pre-emptive, it's not true multi-tasking, as another process can steal 100% cpu and require a hard reboot. But usually what happened is that the TSR was badly written and would lock up the machine at some point.
I guess that's what you get with a hive mind :-)
No, it's not "moving the goalposts." Read the post above mine complaining about "scattered ini files".
The ini file format makes it pretty clear what you're editing - it's plain text. The registry - even with a front end - is pretty opaque. And when you write "Put a front-end onto any binary file, the ease is as simple as (or simpler, no texteditor summoning needed as for text) editing an .ini file." you've got to be kidding. You need a custom front end rather than any old text editor you have hanging around, or even copy con > stuff.ini.
And no, code for scanning through a gigantic binary file is not going to be as fast as loading a 1k text file.
I looked at the article you linked to - no mention of emacs ...
Short version: All your mail are belong to US.
Considering that Microsoft did a limited release of a multi-tasking dos back in 1987, complete with preemptive multitasking, and that later extensions allowed dos to access up to 3 gig of ram for 32-bit programs, or 4 gig in unreal mode, I'd say emacs and systemd can't beat dos as an os.
It's quicker to process a small text file than a humongous binary file, especially when you have a small list of valid keys in the ini file.
It's also easier to manually change the values in a small text file. Or back it up and give it a name that makes it evident that it's ONLY for that one program.
The hive is stupid. Complication for complication's sake. A great place to hide malware instructions.
Just ask Google to translate it.