Linked by Thom Holwerda on Tue 5th Jul 2011 21:46 UTC, submitted by mpxlbs
OSNews, Generic OSes No, your eyes aren't deceiving you - we have actually have not one, but two news items on hobby/small operating systems on the same day! You thought the day would never come again, but hey, here we are. You're welcome. Now, what are we talking about? FreeDOS - a test release has been, uh, released for FreeDOS 1.1.
Thread beginning with comment 480018
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Its a shame, in a way.

It seems that most OS choices that have been developed offer two (yes, with grey areas) paths... use an outdated, unsupported version or suffer vast amounts of what I will call "bloat." I put that in quotes, because I don't mean bloat in the usual or even negative sense. I use the word in this case to denote features that were not required before, and without which plenty of work was done with computers.

To get back to the point, when I install an older operating system on new hardware (which I almost always do before installing the intended target OS, just to see) if I can get it to run than it SCREAMS. Click and go - literally. No hourglass. But that's if it will run at all. And of course most of the new hardware is not supported. In the end, the outdated nature of the system and drivers, and NOT the missing features and bling, are what ruins the experience.

In short, I would love to see an OS crop up that stuck with older design (like FreeDOS) but updated that design to support new hardware and newer processors and components. Kind of like how I would love to see a mfg come out with a 0 latency system. No bottlenecks whatsoever. It would be fun to use and play with.

Just daydreaming out loud, I guess. Thanks for reading :-)

Reply Parent Score: 1

by zlynx on Fri 8th Jul 2011 19:18 in reply to "RE: Real DOS / Real hardware / VT-x"
zlynx Member since:

Every system will have bottlenecks. It depends entirely on what is being done with it.

You could design a system without any bottlenecks but only if it only did one single thing, like operate a robot arm.

A robot arm realtime control system has no bottlenecks. The computer operates exactly as fast as the arm motors and sensors support.

A car's engine control computer or its anti-lock brake or dynamic stability control has no bottlenecks. It works just exactly as fast as it can.

But when you introduce a programmable system, the bottlenecks appear and change depending on what program is being run.

If you are downloading network files, a lot of CPU and RAM is being wasted while the network is the bottleneck.

If you're playing an arcade game, the RAM and network is going to waste while the CPU or GPU is at 100% use.

If you are processing giant databases in random access, the CPU is being wasted while the RAM or storage system is maxed out.

Reply Parent Score: 2